gear-foundation/gear-architecture-planner
skills/gear-architecture-planner/SKILL.md
Use when an approved Gear or Vara spec must be mapped onto program boundaries, services, message flow, and integration surfaces. Do not use when the feature is still undefined or when the task is already reduced to code edits.
$ install --global
skillsauthnpx skillsauth add gear-foundation/vara-skills gear-architecture-plannerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 23, 2026, 2:39 AM33.2s1 file scanned
SKILL.md
- name:
- gear-architecture-planner
- description:
- Use when an approved Gear or Vara spec must be mapped onto program boundaries, services, message flow, and integration surfaces. Do not use when the feature is still undefined or when the task is already reduced to code edits.
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 Sails Header-aware 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.
Related Skills
gear-foundation/sails-ethexe-implementer
development
VerifiedTrustedCommunity
Use when approved tasks require Rust code changes in a Sails ethexe workspace with the ethexe feature enabled. Do not use for standard Gear/Vara Sails apps without ethexe, or when the spec or architecture is still unsettled.
17SKILL.mdUpdated May 23, 2026
gear-foundation/sails-ethexe-architecture
development
VerifiedTrustedCommunity
Use when a builder needs to design or review architecture for a Sails ethexe app with dual-transport, payable methods, Solidity interface generation, or Ethereum-style events. Do not use for standard Gear/Vara Sails apps without ethexe.
17SKILL.mdUpdated May 23, 2026
gear-foundation/gear-builtin-actors
development
VerifiedTrustedCommunity
Use when a builder needs to design or debug calls from a standard Gear/Vara Sails program into runtime builtin actors such as BLS12-381, staking, proxy, or ETH bridge, including ActorId derivation, request encoding, reply decoding, and gas or ED budgeting. Do not use for regular program-to-program messaging, Vara.eth or ethexe-only work, non-Sails repositories, or runtime-maintenance tasks inside the Gear repo.
17SKILL.mdUpdated May 16, 2026
gear-foundation/sails-indexer
development
VerifiedTrustedCommunity
Use when a builder needs a read-side indexer and query API for a standard Gear/Vara Sails app using program events, IDL-driven decoding, projected read models, and optional on-chain query enrichment. Do not use for command-side backends, generic Node APIs, non-Sails repositories, Vara.eth or ethexe-first work.
17SKILL.mdUpdated May 13, 2026