Framework for running design reviews using feedback hierarchy and structured critique.
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
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add refoundai/lenny-skills --skill running-design-reviewsCompatible with
Supported agents
Prioritize feedback by value first (does it solve the problem?), then usability, then delight; defer aesthetic concerns until core value is validated
Assign senior leaders as project sponsors to oversee quality through live demos and review 100% of shipped screens before launch
Structure reviews around specific feedback requests; ask presenters exactly what type of input they need rather than openi
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionrunning-design-reviewsExecute the skills CLI command in your project's root directory to begin installation:
epx add refoundai/lenny-skills --skill running-design-reviewsFetches running-design-reviews 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:
.cursor/skills/running-design-reviews
Restart Cursor to activate running-design-reviews. Access via /running-design-reviewsin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
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.
tui-design
hyperb1iss/hyperskills · Frontend · tag: design
design-taste-frontend
bnd-1/taste-skill · Frontend · tag: design
stitch-design-taste
leonxlnx/taste-skill · Frontend · tag: design
frontend-design
buildermethods/design-os · Frontend · tag: design
ui-design-brain
carmahhawwari/ui-design-brain · Frontend · tag: design
web-artifacts-builder
anthropics/skills · AI/ML · tag: design
Keeps context tight: running-design-reviews is the kind of skill you can hand to a new teammate without a long onboarding doc.
running-design-reviews has been reliable in day-to-day use. Documentation quality is above average for community skills.
running-design-reviews is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
running-design-reviews is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
running-design-reviews reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in running-design-reviews — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
running-design-reviews reduced setup friction for our internal harness; good balance of opinion and flexibility.
running-design-reviews is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
I recommend running-design-reviews for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
running-design-reviews reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 68