Framework-driven guidance for writing specs and design documents from seven product leaders.
Works with
Determine fidelity level upfront: low-fi sketches for alignment, high-fi specs for implementation details
Favor prototypes over static documentation; test the feel with real software rather than screenshots
Use fat marker sketches and breadboarding to avoid getting stuck on UI details like colors or spacing
Recognize that temporary design shortcuts often become permanent product decisions;
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionwriting-specs-designsExecute the skills CLI command in your project's root directory to begin installation:
Fetches writing-specs-designs from refoundai/lenny-skills 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 writing-specs-designs. Access via /writing-specs-designs 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
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
616
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
616
stars
Help the user write effective specs and design documents using frameworks and insights from 7 product leaders.
When the user asks for help with specs and design docs:
Christina Wodtke: "If I got on the whiteboard and drew really badly, somebody else will go, 'No, no, no, it doesn't work that way. Give me this pen.' It gets you so fast to a shared vision." Drawing 'badly' invites participation and corrections, accelerating alignment.
Ryan Singer: "The output of the shaping session is some kind of drawing or diagram where engineers, product, and design are all saying, 'I know exactly what to go build.'" Aim for a level of detail where the team sees the 'electricity in the walls' without prescribing UI details.
Tamar Yehoshua: "I can't tell you if this is going to work. I have to feel it. I have to try it. A mock-up doesn't tell you what it's going to feel like." Push for prototypes with real data to test experience, not just static screenshots.
Noah Weiss: "We stopped spending cycles on design explorations of static mocks and said, 'How quickly can we get into prototyping the path in real software, even if it's messy and throwaway?'" Move to real software prototypes as quickly as possible.
Nikita Bier: "You should be designing the hierarchy, the pixels, the flows, everything. Products live and die in the pixels." For zero-to-one products, own the granular design details; every tap is precious.
Nikita Bier: "Every tap on a mobile app is a miracle. Users will turn and bounce to their next app very quickly." Design with extreme efficiency; each interaction must provide immediate value.
Ryan Singer: "Use breadboarding and fat marker sketching. We're going to hit this button, go to here, this calculation runs, then we get this answer." Fat markers prevent getting bogged down in UI details like colors or spacing.
Tom Conrad: "Temporary design shortcuts often become permanent product legacies that persist through multiple technical rewrites." Be mindful that early implementation details may define long-term user expectations.
Ravi Mehta: "Learn how to sketch, learn Balsamiq. Having that ability to think at a conceptual level about how UI and UX works is a critical part of being a PM." Develop self-sufficiency in creating conceptual wireframes.
For all 10 insights from 7 guests, see references/guest-insights.md
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
davila7/claude-code-templates
anthropics/claude-code
mblode/agent-skills
github/awesome-copilot
sickn33/antigravity-awesome-skills
leonxlnx/taste-skill
Useful defaults in writing-specs-designs — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
writing-specs-designs is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: writing-specs-designs is the kind of skill you can hand to a new teammate without a long onboarding doc.
writing-specs-designs has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: writing-specs-designs is the kind of skill you can hand to a new teammate without a long onboarding doc.
writing-specs-designs has been reliable in day-to-day use. Documentation quality is above average for community skills.
writing-specs-designs reduced setup friction for our internal harness; good balance of opinion and flexibility.
Keeps context tight: writing-specs-designs is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for writing-specs-designs matched our evaluation — installs cleanly and behaves as described in the markdown.
I recommend writing-specs-designs for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 36