reference
Reference kits
/kits/<name>/. They predate the Nuxt repo and were carried over as design source: the AggieUX component catalog, three application shells (Landscape, tti-docs, tti-ai-chat), and a deck-stage slide system. All five render in vanilla CSS + React via Babel-in-the-browser — no build step — and pull /colors_and_type.css so they reflect the live tokens. Use them to see how patterns compose; the production-grade equivalents live in the Tux* components. component catalog
AggieUX
Exhaustive ~57-family catalog organized into Foundations, Navigation, Components, Specialized, Templates. Mirrors the Texas A&M Marcom + TTI structure. Most families have all three style variants (default / bold / elegant) demonstrated. The richest reference; consult before designing a new pattern.
/kits/aggieux/ ↗
app shape
Landscape
The institute's sensitive-data classifier (Landscape) — sidebar nav, scans/classifiers/indices pages, compliance alerts, status badges, classifier catalog cards. The data-density end of the system: how tux composes into a research-IT product surface.
/kits/landscape/ ↗
app shape
tti-docs
The living style guide itself, rebuilt as a click-thru artifact — display-italic hero, foundations grid, BigStat institutional brag-numbers, a footer-mounted high-contrast (tti-hc) toggle. The editorial / marketing end of the system.
/kits/tti-docs/ ↗
app shape
tti-ai-chat
Internal LLM chat for research staff — conversation list grouped by day, ITAR-tier compliance banner over the composer, citations block on every assistant turn, right-rail context panel with corpus / retrieval / usage stats. Shows tux primitives in a chat product context.
/kits/tti-ai-chat/ ↗
deck system
Slides kit
A deck-stage slide system in plain HTML — title slide, content slides, factoid slide, quote slide, closer. Use as a starting point for TTI presentations that need to look like the rest of the system, not like generic PowerPoint.
/kits/slides/ ↗
when to use
Reference kits vs Tux components
The kits are frozen reference — they encode design decisions but they're not what you import in production. New consumers pull from the live Vue components under app/components/Tux*.vue; designers and reviewers consult the kits to see what an end-state surface should feel like. If a kit and a Tux component disagree, the Tux component wins — the kits date from the portable-download phase and don't get line-by-line updates.