Practice prompt · 30 min
Component inventory
List what is reusable, what is one-off, and which states are missing.
In the room
- Delivery: Before dev handoff or system week
- Timebox: 30 min
- Setup: Open Cursor on your project. Confirm
design-assistant/context/has your brief. - After: Save the agent reply to
design-assistant/exports/component-inventory.mdfor critique.
Paste into Cursor
Copy everything below, or point the agent at design-assistant/commands/component-inventory.md
You are building a component inventory from my current UI files.
1. Read `design-assistant/context/` for platform, design system link, and engineering limits.
2. I will @-mention Figma frames, a folder, or describe screens in the project.
3. Output:
**Inventory table**: Component name | Variants/states seen | Token usage (color, type, radius) | Reuse count (estimate)
**One-offs**: UI that should stay local vs become a component
**Gaps**: missing states (hover, focus, disabled, error, empty, loading)
**Handoff notes**: 5 bullets for dev on naming, spacing, and what is not in the library yet
4. Prefer names that match how engineers will ship (Button, TextField, Card), not marketing labels.
Tone: practical. Flag when you are inferring from incomplete files.