Plugins
6 plugins@voltagent
DESIGN.md Design Systems
Ready-to-use DESIGN.md design systems extracted from real products, from VoltAgent's awesome-design-md.
74 skills · plugin
@alirezarezvani
Product Team
13 product skills with 17 Python tools: product manager toolkit (RICE, PRDs), agile product owner, product strategist, UX researcher, UI design system, competitive teardown, landing page generator, SaaS scaffolder, product analytics, experiment designer, product discovery, roadmap communicator, code-to-prd, research summarizer, apple-hig-expert.
10 skills · plugin
curated
Design System Audit and Remediation
Identify design debt, audit tokens, and enforce consistency across a product.
14 skills · plugin
curated
Validate Product Idea
Validate a product idea by clarifying intent, identifying risky assumptions, and designing experiments to test them.
4 skills · plugin
curated
Validate New Product Idea
Stress-test assumptions, design experiments, and validate a new product idea using lean startup methods.
3 skills · plugin
@alunadev
Ald Skills
Adrian Luna Díaz personal skill library — product management, engineering, design, and operations skills.
57 skills · plugin
Results for “product-design”
326 skillsBleu
Use this skill whenever a developer wants to turn an idea into a complete, production-ready, end-to-end system plan BEFORE writing any code. Trigger on 'plan this system', 'design the architecture for', 'help me blueprint', 'deep plan for X', 'break this idea into components', 'expand into action points', 'full implementation plan', or when the user pastes a project idea wanting architecture, components, pipelines, and file-level execution mapped out. Casual phrasing also triggers: 'help me think this through end-to-end', 'plan before coding'. Also covers living-workspace patterns: self-improving knowledge bases, reflection loops with auditor agents, four-agent teams, schema-as-code, wiki health scoring. **Resume triggers**: 'where did we leave off', 'continue this plan', 'resume my blueprint' - rehydrates state from disk via SESSION.md/NEXT.md/decisions/. Web research is mandatory every invocation.
0 · bundle
Page Brief
Create OR review a page-brief — the artifact BETWEEN a wireflow and the full PRD. It turns each unique page/screen of a product into documented requirements TIED TO JOBS: a self-contained board card per page (what the page is accountable for, the job-tagged checklist of what it must let you do, the journeys it appears in, what it connects to, and the acceptance criteria that say how you'd know it's right). It is the "PRD per page", not a sitemap — and it stops ABOVE the screen: no components, no layout, no hierarchy. Use whenever the user wants to "spec the pages", "document each screen", turn a wireflow + live design into per-page requirements, or asks "what does this page need to do / which jobs pass through it" — even if they never say "page-brief". Natural NEXT STEP after the wireflow skill. ALSO use it to REVIEW an existing page-brief / screen catalog. In the A-Team pipeline this is a definition-phase skill: output lands in docs/features/<slug>/briefs/pages/, job codes are the durable [[NN]] ids from doc
0 · bundle