sails-new-app

Bootstrap new Gear/Vara Sails applications with standard workspace structure and planning docs.

17|23|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/gear-foundation/vara-skills --skill sails-new-app
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sails-new-app
Source: https://github.com/gear-foundation/vara-skills/tree/main/skills/sails-new-app
Command: npx skills add https://github.com/gear-foundation/vara-skills --skill sails-new-app

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of broken workspaces, missing planning artifacts, and avoidable build errors that occur when builders skip critical steps or use non-standard setups when starting a new Gear/Vara Sails application.

Core Features & Use Cases

  • Structured Greenfield Workflow: Provides a step-by-step sequence for new Sails/Vara projects, from environment validation to pre-implementation checks.
  • Workspace Integrity Guardrails: Enforces the standard cargo sails new template structure and generated client pipeline to prevent common Cargo feature unification and build errors.
  • Planning Artifact Enforcement: Requires creation of spec and architecture documentation before implementation to align stakeholders and reduce rework. Use Case: A builder starting a new Vara Sails service can use this Skill to avoid hand-assembled workspaces that break due to conflicting gstd and gtest feature flags, and ensure all required planning docs are created before writing any code.

Quick Start

Use the sails-new-app skill to bootstrap a new standard Gear/Vara Sails app following the correct greenfield setup and planning sequence.

Frequently Asked Questions about sails-new-app

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I bootstrap a new Sails app on Vara without getting build errors?

To bootstrap a Sails app without build errors, use the standard `cargo sails new` template structure to prevent conflicting `gstd` and `gtest` feature flags and ensure correct workspace generation.

Why does my Gear Sails workspace fail due to Cargo feature unification?

Gear Sails workspaces fail when hand-assembled setups cause conflicting `gstd` and `gtest` feature flags. Enforcing a standard template workspace structure and generated client pipeline prevents these build errors.

What planning artifacts do I need before implementing a Vara smart contract?

Before implementing a Vara smart contract, you must create spec and architecture documentation as required planning artifacts to align stakeholders, validate pre-implementation steps, and reduce rework.

What is the correct greenfield workflow for initiating a Gear Sails project?

The correct greenfield workflow for a Gear Sails project follows a step-by-step sequence from environment validation to pre-implementation checks, enforcing standard workspace bootstrapping and planning doc creation.

Can I skip architecture documentation when starting a new Sails application?

You cannot skip architecture documentation when starting a new Sails application. Planning artifact enforcement requires spec and architecture docs before implementation to prevent stakeholder misalignment and rework.