gear-architecture-planner
Gear Architecture Planner
Overview
Turn an approved spec into a concrete Gear/Sails architecture note.
Start Here
Read ../../references/vara-domain-overview.md, ../../references/sails-cheatsheet.md, ../../references/sails-program-and-service-architecture.md, ../../references/gear-messaging-and-replies.md, and ../../references/sails-idl-client-pipeline.md.
If the architecture choice depends on what Gear programs can express through gstd, review ../gear-gstd-api-map/SKILL.md before locking the design.
Use ../../assets/architecture-template.md as the output shape.
Write the result to docs/plans/YYYY-MM-DD-<topic>-architecture.md.
Workflow
- Confirm the spec artifact exists and is approved.
- Choose program constructors and service boundaries.
- Map state ownership, routing, messages, replies, and events.
- Record generated-IDL or generated-client implications.
- Capture off-chain components, failure paths, and explicit non-goals.
Guardrails
- Keep
#[program]thin and push business logic into services. - Make the constructor shape and storage pattern explicit instead of leaving them to implementation guesswork.
- Treat generated clients or equivalent route-prefixed encoding as the default Sails message contract.
- Treat actor boundaries and async flow as design constraints.
- Call out remote-call failure policy instead of leaving it implicit.
- Do not collapse architecture into a file-by-file coding checklist.
More from gear-foundation/vara-skills
vara-skills
Use when a builder needs the top-level router for the provisional standard Gear/Vara Sails skill pack across Codex, Claude, or OpenClaw. Do not use for Vara.eth or ethexe work, non-Sails programs, or broad protocol research.
197sails-new-app
Use when a builder is starting a new standard Gear/Vara Sails app and needs the correct greenfield sequence before implementation. Do not use for edits to an established repo, Vara.eth or ethexe targets, or non-Sails templates.
2sails-dev-env
Use when a builder needs to prepare or repair a local macOS, Linux, or Windows machine for standard Gear/Vara Sails Rust development before building, testing, or running a local node. Do not use for live-network deployment, app-specific feature work, or Vara.eth/ethexe-only setup.
2vara-wallet
Use when an agent needs to interact with Vara Network on-chain — deploy programs, call Sails methods, manage wallets, transfer tokens, monitor events. Not for building Sails programs (use vara-skills for that).
2sails-gtest
Use when a builder needs the standard Gear/Vara Sails gtest loop for feature verification, debugging, or regression coverage. Do not use for live-network-only validation, deployment-first workflows, or non-Sails programs.
2task-decomposer
Use when approved spec and architecture artifacts must become an ordered implementation plan for Gear or Vara work. Do not use when the architecture is still unsettled or when the request is only asking for a high-level idea.
2