Shape architecture, API, and service boundaries through phased analysis of requirements and trade-offs.
npx skills add https://github.com/heliohq/ship --skill arch-design-heliohq
Please help me install this Agent Skill. Skill: arch-design Source: https://github.com/heliohq/ship/tree/main/skills/arch-design Command: npx skills add https://github.com/heliohq/ship --skill arch-design-heliohq
This Skill helps you reason through architecture decisions before implementation, so system plans are grounded in requirements, constraints, and trade-offs instead of assumptions.
Ask the AI to analyze your architecture problem, work through the design phases, and hand off the final design to write-docs.
High-intent search queries and answers about installing and using this skill.
Design system architecture by performing a phased analysis of functional needs, non-functional constraints, component interactions, and data flow. This approach defines clear service boundaries and API plans by working through requirements and trade-offs before any code is written.
The best way to prepare an Architecture Decision Record (ADR) is to compare architectural alternatives, explicitly recording why one approach wins and what constraints it gives up. This trade-off thinking ensures system plans are grounded in documented requirements rather than assumptions.
Plan APIs and component interactions by analyzing system-level design elements like data flow, storage choices, and scaling requirements. This phased process clarifies how components communicate and handle failures, ensuring the API design supports complex system scalability.
Yes, this system design approach works for architecture reviews and adapting changing systems. It applies to API planning and service boundary definition by re-evaluating non-functional goals, constraints, and failure handling against the new requirements.
You need to analyze non-functional requirements before writing architecture docs because they define the constraints and scaling capabilities of the system. Reasoning through these goals early ensures that component interactions and storage choices can handle expected loads and failures.
Document assumptions and failure handling by working through a phased analysis of component interactions and system-level design. This process explicitly records what must be revisited later, ensuring architecture documents capture the full context of data flow and trade-offs.
Modular-Earth-LLCDesign scalable system architecture with diagrams and Well-Architected guidance.
ldk-hubTranslate product requirements and UX into technical architecture decisions with trade-offs.
hpsgdGenerate system design artifacts including requirements, components, data flows, and storage strategies.
Eigo-Mt-FujiDesign scalable, secure architectures with C4 diagrams, ADRs, and trade-off analysis.
