Document design decisions, interfaces, constraints, and edge cases for software architecture.
npx skills add https://github.com/rjroy/vibe-garden --skill design-rjroy
Please help me install this Agent Skill. Skill: design Source: https://github.com/rjroy/vibe-garden/tree/main/lore-development/skills/design Command: npx skills add https://github.com/rjroy/vibe-garden --skill design-rjroy
This design skill helps teams decide how to implement complex software by focusing on the "how" in the problem — algorithms, data structures, system boundaries, performance, and security. It guides structured decision-making to avoid premature implementation.
Use the design skill to outline architecture and interfaces for a complex feature, and save the result to the lore design repository.
High-intent search queries and answers about installing and using this skill.
Software architecture design explorations evaluate multiple approaches by documenting trade-offs, performance targets, and security considerations. Comparing these structured options clarifies system boundaries and algorithm choices, preventing premature implementation while providing traceable rationale for complex feature decisions.
Use a structured design process before coding when implementing complex software features requiring algorithm choices, data structures, and security planning. It satisfies requirements to explore multiple approaches and document constraints, avoiding premature implementation by clarifying system boundaries first.
Software architecture design handles edge cases and failure modes by capturing performance targets, security constraints, and risk considerations during the decision-making process. Documenting these constraints ensures complex systems remain resilient by evaluating failure scenarios before implementation begins.
Yes, you can use this design approach to explore trade-offs for algorithm choices and data structures. It applies structured option exploration to evaluate performance considerations and system boundaries, documenting the rationale for each architectural decision to avoid premature implementation.
jwyniaDiagnose requirements problems to separate stated wants from true needs.
OzeroHAXCapture architecture decisions, constraints, and contracts for software projects.
MoisesAldasDefine service boundaries and API contracts for backend architectures.
brandonburrusGenerate software diagrams from Mermaid text-based syntax.
