sails-rust-implementer

Implement approved Gear and Vara Sails Rust changes with backward compatibility.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the critical problem of implementing approved Gear/Vara Sails and Rust code changes without introducing unapproved scope, breaking existing public contract interfaces, or violating Sails release conventions, which is essential for maintaining production application stability.

Core Features & Use Cases

  • Spec-Adherent Implementation: Enforces use of only pre-approved specs and architecture artifacts to prevent scope creep during coding.
  • Backward Compatibility Preservation: Safeguards existing public service routes, reply shapes, emitted events, and generated client expectations for released contracts unless explicitly permitted to modify them.
  • Sails Convention Enforcement: Guides correct usage of #[export] annotations, #[sails_type] derives, Syscall APIs, and Gear/Vara async semantics to avoid common implementation errors.
  • Use Case: For example, when implementing an approved feature to add a new query method to an existing Sails app, this Skill ensures you follow the correct export pattern, use proper type derives, and do not break existing public routes or client integrations.

Quick Start

Use the sails-rust-implementer skill to implement the approved new token transfer feature in your Sails app without modifying any existing public contract routes or event payloads.

Frequently Asked Questions about sails-rust-implementer

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

FAQPage Schema
How do I implement new features in Sails Rust smart contracts without breaking existing public routes?

Use correct #[export] annotations and #[sails_type] derives when adding Sails Rust contract methods. Following Sails release conventions ensures proper type generation and prevents common implementation errors in Gear/Vara asynchronous execution environments.

What are Sails release conventions for Rust workspace updates on Gear and Vara?

No, you should only use pre-approved specs and architecture artifacts when coding Sails Rust contracts. Spec-adherent implementation prevents unapproved scope creep and ensures new feature development aligns with reviewed architecture for Gear and Vara applications.

How do I add a new query method to an existing Sails app without modifying current event payloads?

To add a Sails app query method safely, follow the correct export pattern and use proper type derives while explicitly avoiding modifications to existing public routes or event payloads. This preserves backward compatibility for current client integrations.

Why do my Gear/Vara async smart contracts fail gas reservation during Sails Rust updates?

Gear/Vara async smart contract gas reservation failures during Sails Rust updates usually occur due to misaligned asynchronous execution semantics. Enforcing correct Syscall API usage and Sails conventions ensures proper gas handling and contract stability.