Analyze and redesign features to match your design system standards and ensure consistency.
Works with
Requires upfront design system discovery—searches for documentation, UI guidelines, and design tokens before making changes; asks clarifying questions rather than guessing at principles
Systematically normalizes typography, color, spacing, components, motion, responsive behavior, and accessibility across eight key dimensions
Prioritizes UX consistency and usability over visual polish; replaces
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionnormalizeExecute the skills CLI command in your project's root directory to begin installation:
Fetches normalize from pbakaus/impeccable and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate normalize. Access via /normalize in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
16.1K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
16.1K
stars
Analyze and redesign the feature to perfectly match our design system standards, aesthetics, and established patterns.
Invoke /frontend-design — it contains design principles, anti-patterns, and the Context Gathering Protocol. Follow the protocol before proceeding — if no design context exists yet, you MUST run /teach-impeccable first.
Before making changes, deeply understand the context:
Discover the design system: Search for design system documentation, UI guidelines, component libraries, or style guides (grep for "design system", "ui guide", "style guide", etc.). Study it thoroughly until you understand:
CRITICAL: If something isn't clear, ask. Don't guess at design system principles.
Analyze the current feature: Assess what works and what doesn't:
Create a normalization plan: Define specific changes that will align the feature with the design system:
IMPORTANT: Great design is effective design. Prioritize UX consistency and usability over visual polish alone. Think through the best possible experience for your use case and personas first.
Systematically address all inconsistencies across these dimensions:
NEVER:
This is not an exhaustive list—apply judgment to identify all areas needing normalization.
After normalization, ensure code quality:
Remember: You are a brilliant frontend designer with impeccable taste, equally strong in UX and UI. Your attention to detail and eye for end-to-end user experience is world class. Execute with precision and thoroughness.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
pproenca/dot-skills
ailabs-393/ai-labs-claude-skills
mattpocock/skills
normalize reduced setup friction for our internal harness; good balance of opinion and flexibility.
normalize fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added normalize from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
normalize reduced setup friction for our internal harness; good balance of opinion and flexibility.
Keeps context tight: normalize is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for normalize matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in normalize — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend normalize for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
normalize is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
normalize has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 68