| name | terminal-component |
| description | Change Terminal UI or behavior. Use when working with the Terminal component, command registry, terminal commands, terminal hooks, or terminal cookie state. |
Terminal component
Guidance for the Terminal feature (interactive CLI-style UI on the home page).
Entry and loading
Command system
- Registry: components/mate/terminal/command-registry.ts — singleton
registry; registerGroup(name, commands), getAllCommands(), getCommandMap() (name + aliases, lowercased).
- Registration: components/mate/terminal/commands/index.ts — registers groups: System, Personal, Social, Navigation (links, site), Fun (ait). Add new commands here or in the appropriate group file.
- Command groups: components/mate/terminal/commands/system.ts, components/mate/terminal/commands/personal.ts, components/mate/terminal/commands/social.ts, components/mate/terminal/commands/navigation.ts, components/mate/terminal/commands/ait.ts.
- Types: components/mate/terminal/types/commands.ts —
Command, CommandGroup, CommandRegistry. Commands have name, aliases?, description, run (and optionally UI).
Hooks
UI pieces
Cookie state
- lib/utils/cookies/terminal.cookie.ts —
terminalCookie: get(), set(), remove(), hasVisitedRecently(). Schema: hasVisited, lastVisited. Used to remember if the user has visited the terminal (e.g. for onboarding or banners). Max age 72 hours.
Accessibility
- The terminal or carousel may use
biome-ignore for a11y exceptions (e.g. focus management in custom interactive regions). Document any exception and keep keyboard navigation and screen reader behavior in mind; see CLAUDE.md for project a11y standards.
Adding a new command
- Define the command in the appropriate group file (e.g.
commands/personal.ts) with name, description, run, and optional aliases.
- Register the group (or add the command to an existing group) in components/mate/terminal/commands/index.ts.
- Ensure
run returns output compatible with the line renderer (e.g. string or structured output the UI understands).
