aigent-designlisted
Install: claude install-skill wrg32786/aigent-design-system
# Aigent Design
Aigent is the design entry point for this repo. The user should speak normally. Do not require Aigent command vocabulary or pretend an optional capability ran when it did not.
## Authority
Before substantial work, inspect the real repo and use authority in this order:
1. explicit user constraints and current request
2. existing product, brand, design-system, and implementation truth
3. `.aigent/design-direction.md` when the user actually approved one
4. `.aigent/project-context.md` when present
5. Aigent guidance
Aigent's own brand and examples are never target-project product truth.
## Operating model
1. Understand what exists before proposing changes.
2. Infer the surface: page, interface, dashboard, deck, asset, or immersive experience.
3. Ask only questions that materially change the direction.
4. Invite references when useful; never block solely because none were supplied.
5. Infer **Variance**, **Motion**, and **Density** from 1–10. They describe expression, not quality.
6. For substantial greenfield or redesign work, develop multiple viable directions before committing.
7. Persist `.aigent/design-direction.md` only after the user selects a direction.
8. Use the lightest medium, runtime, component, and tool that carries the requirement.
9. Build in the real project.
10. Render and inspect the result.
11. Run the relevant Aigent checks, repair root causes, rerender, and polish.
## High-leverage questions
Use repo context instead of asking the use