Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/data-wise/craft/frontend-designernpx skills add Data-Wise/craft --skill frontend-designergit clone --depth 1 https://github.com/Data-Wise/craftWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00052 | $0.01081 |
| Opus 5 | $0.00026 | $0.00541 |
| Sonnet 5 | $0.00010 | $0.00216 |
| Haiku 4.5 | $0.00005 | $0.00108 |
Grade A, and why
frontend-designer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Designer Skill
Auto-activated when: User discusses UI/UX, component architecture, accessibility, or frontend design decisions.
Core Capabilities
1. Component Architecture
- Component composition patterns
- Props vs state decisions
- Component reusability strategies
- Folder structure (colocation vs separation)
- Design system integration
2. UI/UX Patterns
- Layout patterns (grid, flexbox, responsive)
- Navigation patterns (tabs, drawer, breadcrumbs)
- Form design (validation, error handling, multi-step)
- Loading states and skeletons
- Empty states and error boundaries
3. Accessibility (A11y)
- WCAG compliance checklist
- Semantic HTML
- ARIA labels and roles
- Keyboard navigation
- Screen reader compatibility
- Color contrast (ADHD-friendly palettes)
4. Performance
- Code splitting strategies
- Lazy loading images/components
- Virtual scrolling for long lists
- Debouncing/throttling user input
- Bundle size optimization
ADHD-Friendly Design Patterns
Visual Hierarchy:
- Clear focus states (bold borders, high contrast)
- Reduce visual clutter (progressive disclosure)
- Consistent spacing (8px grid system)
- Limited color palette (3-5 colors max)
Interaction Design:
- Immediate feedback (loading spinners, success states)
- Undo/redo capabilities
- Auto-save (reduce "did I save?" anxiety)
- Confirmation dialogs for destructive actions
- Keyboard shortcuts for common actions
Cognitive Load Reduction:
- One primary action per screen
- Hide advanced options behind "Advanced" toggle
- Use wizards for multi-step processes
- Provide templates/presets
- Clear error messages with next steps
Design Philosophy: Solid Indie
Ship Fast Principles:
- Start with Tailwind/Bootstrap, customize later
- Use proven component libraries (shadcn/ui, Headless UI)
- Mobile-first responsive design
- Accessibility from day one (easier than retrofitting)
Anti-Patterns to Avoid:
- ❌ Custom design system before 10K users
- ❌ Over-abstraction (generic
<Button>with 20 props) - ❌ Premature animation (ship functionality first)
- ❌ Pixel-perfect designs (80% is shipping)
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 158 lines · 52 tokens per session scan A 02a5ba9d1859
frontend-designer is a skill published in the GitHub repository Data-Wise/craft (4 stars, last pushed 17d ago), licensed MIT. It adds 52 tokens to every session and 1,081 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
architecture-review
Conducts a comprehensive multi-perspective architecture review using ALL architecture team members. Use when the user requests "Start architecture review", "Full architecture review", "Review architecture for version X.Y.Z", "Conduct comprehensive review", or when they want assessment from multiple perspectives. Do…
architecture-status
Reports on the health and state of architecture documentation (counts of ADRs, reviews, activity levels, documentation gaps). Use when the user asks "What's our architecture status?", "Show architecture documentation", "How many ADRs do we have?", "What decisions are documented?", "Architecture health check", or wants…
pragmatic-guard
Enables and configures Pragmatic Guard Mode (YAGNI Enforcement) to prevent over-engineering. Use when the user requests "Enable pragmatic mode", "Turn on YAGNI enforcement", "Activate simplicity guard", "Challenge complexity", or similar phrases.
specialist-review
Conducts a focused review from ONE specific specialist's perspective (e.g., Security Specialist, Performance Expert). Use when the user requests "Ask [specialist role] to review [target]", "Get [specialist]'s opinion on [topic]", "Have [role] review [code/component]", or when they want deep expertise in ONE specific…
create-adr
Creates a NEW Architectural Decision Record (ADR) documenting a specific architectural decision. Use when the user requests "Create ADR for [topic]", "Document decision about [topic]", "Write ADR for [choice]", or when documenting technology choices, patterns, or architectural approaches. Do NOT use for reviews (use…
list-members
Displays the roster of architecture team members with their specialties and expertise areas. Use when the user asks "Who's on the architecture team?", "List architecture members", "Show me the architects", "What specialists are available?", "Who can I ask for reviews?", or wants to discover available experts. Do NOT…