Convert locked epics and scope into personas, screens, flows, and wireframes.
npx skills add https://github.com/kapilvirenahuja/garura --skill garura-design
Please help me install this Agent Skill. Skill: garura:design Source: https://github.com/kapilvirenahuja/garura/tree/main/core/components/plays/design Command: npx skills add https://github.com/kapilvirenahuja/garura --skill garura-design
It transforms locked specify outputs into complete, developer-implementable experience design with explicit structure, coverage, and interaction specs.
Run the design stage after specify by invoking the play as garura:design on your locked product artifacts to generate personas.md, screens, flows, design-system.md, and design-spec.md.
High-intent search queries and answers about installing and using this skill.
To generate structural wireframes and user flows, you provide locked intent epics and scope quality profiles to produce a complete experience design package containing state-complete screen inventories, mapped recovery scenarios, and machine-parseable layout specifications.
A state-complete screen inventory is a mapped screen set where every product capability corresponds to at least one screen, and each screen explicitly enumerates its minimum viable states, ensuring full coverage of success and recovery paths.
You create UX personas aligned to product capabilities by synthesizing JTBD personas mapped directly to primary MVP use cases and selected scope capabilities, ensuring persona relevance to locked intent and validation constraints.
Yes, you can build a design system with separate tokens and inspirations by authoring a product-level design system artifact that enforces design-system separation of tokens from structural wireframes for implementation readiness.
Yes, experience design generation requires locked artifacts because it enforces locked-artifact preconditions and decision surfacing with manifests for inferred work, ensuring MVP focus and validation constraints are maintained throughout the design run.
The best way to document interaction pattern specifications and recovery paths is by compiling a consolidated design-spec file that maps success and recovery scenarios into user flows alongside low-fidelity structural wireframes and explicit interaction pattern specifications.
sumilee-pcuTranslate game design documents into bounded architectural epics with ADRs and engine risks.
deangilmoreremixTranslate Figma nodes into React components using design system tokens.
asalhamedAnalyze user needs into personas, journey maps, and usability requirements.
sizukutamagoGenerate screen inventories and Mermaid transition diagrams from user stories in docs/requirements.
