System-design thinking before any doc or code: goals/non-goals, back-of-envelope numbers, components and contracts, failure modes, operability, security, trade-offs. Use for "design this system", "architecture for X", "trade-offs for X", "how should we architect", "API design", "data model for", "service boundaries", or before an ADR. Hands off to /ship:write-docs to record the decision. Not implementation planning (/ship:design — that turns a decided design into stories).
$npx -y skills add heliohq/ship --skill arch-designInstalls into the current project.
Run `npx skills use "https://github.com/heliohq/ship" --skill "heliohq/ship/arch-design"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/heliohq/ship" that are relevant to the current task. Run `npx skills add "https://github.com/heliohq/ship"` and select the relevant skills, then follow their instructions.