One-time setup that gathers design context and persists it to your AI config file.
Works with
Scans your codebase to discover existing design patterns, brand assets, tech stack, and design tokens before asking questions
Asks targeted UX questions about users, brand personality, aesthetic preferences, and accessibility needs, skipping what's already clear from exploration
Synthesizes findings into a Design Context markdown section saved to .impeccable.md in your project root for all future sessi
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionteach-impeccableExecute the skills CLI command in your project's root directory to begin installation:
Fetches teach-impeccable 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 teach-impeccable. Access via /teach-impeccable 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
6
total installs
6
this week
16.1K
GitHub stars
0
upvotes
Run in your terminal
6
installs
6
this week
16.1K
stars
Gather design context for this project, then persist it for all future sessions.
Before asking questions, thoroughly scan the project to discover what you can:
Note what you've learned and what remains unclear.
ask the user directly to clarify what you cannot infer. Focus only on what you couldn't infer from the codebase:
Skip questions where the answer is already clear from the codebase exploration.
Synthesize your findings and the user's answers into a ## Design Context section:
## Design Context
### Users
[Who they are, their context, the job to be done]
### Brand Personality
[Voice, tone, 3-word personality, emotional goals]
### Aesthetic Direction
[Visual tone, references, anti-references, theme]
### Design Principles
[3-5 principles derived from the conversation that should guide all design decisions]
Write this section to .impeccable.md in the project root. If the file already exists, update the Design Context section in place.
Then ask the user directly to clarify what you cannot infer. whether they'd also like the Design Context appended to .github/copilot-instructions.md. If yes, append or update the section there as well.
Confirm completion and summarize the key design principles that will now guide all future work.
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
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
I recommend teach-impeccable for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: teach-impeccable is the kind of skill you can hand to a new teammate without a long onboarding doc.
teach-impeccable has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in teach-impeccable — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
teach-impeccable is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for teach-impeccable matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: teach-impeccable is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend teach-impeccable for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for teach-impeccable matched our evaluation — installs cleanly and behaves as described in the markdown.
teach-impeccable fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 59