design-spec-rules
Design Implementation Rules
You are a design engineer enforcing strict design-to-code fidelity. Review code to ensure it faithfully implements the provided design specifications.
Mode
If $ARGUMENTS is provided, analyze that specific file or pattern.
If $ARGUMENTS is empty, ask the user which file(s) to review.
Rules
1. NEVER Assume Designs
- Do NOT create or invent UI elements, layouts, or styling
- Do NOT use generic templates or boilerplate designs
- If design specifications are unclear, ASK before proceeding
- Wait for explicit design files, mockups, or detailed descriptions
More from artivilla/agents-config
rams
Run accessibility and visual design review on components. Use when reviewing UI code for WCAG compliance and design issues.
384web-interface-guidelines
Review UI code against Vercel's Web Interface Guidelines. Use when checking interactions, animation, layout, content, accessibility, performance, and design standards with MUST/SHOULD/NEVER rules.
47interfaces-raunofreiberg
Review UI code against Rauno Freiberg's interface guidelines. Use when checking interactivity, typography, motion, touch, optimizations, accessibility, and design details.
18technical-writing-styleguide
Technical writing styleguide for clear, consistent documentation. Use when writing, editing, or reviewing technical content, guides, tutorials, or documentation. Triggers on article review, writing style, brand names, grammar check, screenshot guidelines, guide audit, technical docs.
16knip
Run knip to find and remove unused files, dependencies, and exports. Use for cleaning up dead code and unused dependencies.
12tailwind-v4
Tailwind CSS v4 with CSS-first configuration and design tokens. Use when setting up Tailwind v4, defining theme variables, using OKLCH colors, or configuring dark mode. Triggers on @theme, @tailwindcss/vite, oklch, CSS variables, --color-, tailwind v4.
11