gear-foundation/sails-new-app
skills/sails-new-app/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add gear-foundation/vara-skills sails-new-appInstall 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:40 AM86.4s1 file scanned
SKILL.md
- name:
- sails-new-app
- description:
- 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.
Sails New App
Goal
Move a greenfield request from scope to an approved Sails workspace path without skipping the planning artifacts that later implementation depends on.
Sequence
- If the machine does not already have
rustup, the required Wasm targets,cargo-sails, and a localgearbinary, start with../sails-dev-env/SKILL.md. - For a new standard Sails/Vara project, bootstrap the workspace first with
cargo sails new <project-name>unless the user explicitly needs a custom non-template layout. - Write the feature or app goal to
docs/plans/YYYY-MM-DD-<topic>-spec.mdusing../../assets/spec-template.md. - Route architecture decisions through
../sails-architecture/SKILL.md. - Keep the standard template workspace shape created by
cargo sails new <project-name>intact:app,client,src,tests, top-levelbuild.rs, Wasm output, and generated-client path. - Keep the standard build-script pipeline intact. In a standard Sails workspace, use the repo-generated build path for
.idland Rust client artifacts. For a dedicated client crate, prefersails-rswithfeatures = ["build"]andsails_rs::build_client::<Program>()before introducing manualsails-idl-gen/sails-client-gen-v2wiring. - Validate before moving to later phases by finishing with
../sails-gtest/SKILL.md, then../sails-local-smoke/SKILL.md. - When the builder needs a frontend, use
create-vara-appto scaffold it from the program's.idl:npx create-vara-app <name> --idl path/to/service.idl. Then route to../sails-frontend/SKILL.mdfor customization.
Shared Inputs
../../references/vara-domain-overview.md../../references/sails-cheatsheet.md../../references/sails-program-and-service-architecture.md../../references/sails-idl-client-pipeline.md../../references/sails-idl-v2-syntax.md— IDL v2 annotations,!@include, service-scoped types
Guardrails
- Keep the builder on standard Sails scaffolding and generated clients.
- Keep the standard Sails workspace shape and build-generated
.idland.opt.wasmartifact path intact, and check the crate'sbuild.rsbefore adding ad hoc generation steps. - Do not jump into raw Gear primitives when a Sails path already exists.
- Do not skip the planning docs just because the repo is greenfield.
- Always use
cargo sails new <project-name>for greenfield Sails/Vara work. Hand-assembled workspaces are a known source of errors: shared top-level workspaces cause Cargo feature unification to enable bothgstdandgtestonsails-rssimultaneously, breaking the build. See../../references/sails-rs-imports.mdfor the canonical layout. - Use
#[sails_type]for all custom types (structs, enums) used in service interfaces. This replaces the verbose#[derive(Encode, Decode, TypeInfo)] #[codec(crate = ...)]pattern from 0.x.
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