SkillsAdd

gear-foundation/vara-skills

sails-feature-workflow

Use when a builder is changing behavior inside an existing standard Gear/Vara Sails app and needs the correct stage-by-stage workflow. Do not use for greenfield scaffolding, Vara.eth or ethexe paths, or non-Sails repositories.

First seen Apr 4, 2026

Installation

$ npx skills add gear-foundation/vara-skills --skill sails-feature-workflow
View on skills.sh ↗ GitHub repository ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

agent-browser Shared topics
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Shared topics
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Shared topics
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Shared topics
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-hosted-copilot-sdk Shared topics
microsoft/azure-skills 440.4K installs
azure-enterprise-infra-planner Shared topics
microsoft/azure-skills

Architect and provision enterprise Azure infrastructure from workload descriptions. For cloud a…

402.8K installs

Also in this package

Other skills from gear-foundation/vara-skills · top by installs.

npx skills add gear-foundation/vara-skills
vara-skills 368 sails-local-smoke 2 vara-skills-upgrade 2 sails-program-evolution 2 sails-rust-implementer 2 gear-gstd-api-map 2 sails-idl-client 2 ship-sails-app 2 gtest-tdd-loop 2 idea-to-spec 2

Browse all from gear-foundation/vara-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 17
License LICENSE
Default branch main
Open issues 1
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,480 B
  • docs SUMMARY.md 256 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

Sails Feature Workflow

Goal

Keep feature work inside an existing Sails repo on an explicit sequence instead of skipping straight to code edits or bypassing the typed client path.

If the request targets a released contract, a new deployed contract version, or V1->V2 evolution, route through ../sails-program-evolution/SKILL.md before normal implementation work continues.

Required Sequence

  1. Clarify the feature in docs/plans/YYYY-MM-DD-<topic>-spec.md with idea-to-spec and ../../assets/spec-template.md.
  2. Plan architecture or public interface in ...-architecture.md with ../sails-architecture/SKILL.md and ../../assets/architecture-template.md.
  3. If the work targets a released contract, introduces a new deployed version, requires cutover planning, or prepares V1->V2 migration, review ../sails-program-evolution/SKILL.md before task breakdown and coding.
  4. If the feature needs API selection across gstd, review ../gear-gstd-api-map/SKILL.md before coding.
  5. If the feature changes async behavior, replies, delays, reservations, or waitlist semantics, review ../gear-message-execution/SKILL.md before coding.
  6. Break the work into tasks in ...-tasks.md with task-decomposer and ../../assets/task-plan-template.md.
  7. If the feature introduces a fungible token, mint/burn roles, token-backed accounting, or native-value exchange, review ../awesome-sails-vft/SKILL.md before coding.
  8. Implement the Rust changes through sails-rust-implementer.
  9. If the public interface changed, refresh the .idl and regenerate the typed client through the repo's standard build.rs path first. For dedicated Rust client crates, prefer the sails-rs build-helper path before a manual generator pipeline.
  10. Run gtest through ../sails-gtest/SKILL.md.
  11. Run smoke validation only after green gtest, using ../sails-local-smoke/SKILL.md.

Sponsored UX Cases

  • If the feature includes gasless or signless UX, see ../../references/voucher-and-signless-flows.md for the canonical builder recipes, lifecycle, and failure modes. Define the voucher or session flow in the spec and architecture.

References

  • ../../references/vara-domain-overview.md
  • ../../references/sails-cheatsheet.md
  • ../../references/gtest-cheatsheet.md
  • ../../references/gear-execution-model.md
  • ../../references/gear-messaging-and-replies.md
  • ../../references/sails-gtest-and-local-validation.md
  • ../../references/contract-interface-evolution.md
  • ../../references/voucher-and-signless-flows.md
  • ../../references/sails-idl-v2-syntax.md — IDL v2 annotations for .idl files
  • ../../references/sails-header-wire-format.md — interface ID stability for change classification

Guardrails

  • Do not skip the document chain for “small” features.
  • Do not bypass the generated client path with raw payload encoders, hand-built SCALE payloads, or EVM-style bindings.
  • Do not claim completion before gtest is green and documented.
  • Do not treat local-node smoke as a substitute for gtest.
  • Do not treat released-contract evolution, cutover, or V1->V2 migration as ordinary feature work without routing through the program-evolution flow.