awesome-sails-vft
Use when a builder wants to add a fungible token to a standard Gear/Vara Sails app using awesome-sails building blocks, choose the right VFT-related crates, and wire roles, events, tests, and client integration. Do not use for NFT or RMRK work, abstract tokenomics-only analysis, or non-Sails projects.
What this skill does
# Awesome Sails VFT ## Goal Help the builder add a fungible token layer to a standard Gear/Vara Sails app through awesome-sails without reimplementing standard token behavior from scratch. ## Local Handbook - `../../references/gear-sails-production-patterns.md` - `../../references/sails-program-and-service-architecture.md` - `../../references/sails-idl-client-pipeline.md` - `../../references/sails-gtest-and-local-validation.md` - `../../references/sails-cheatsheet.md` - `../../references/awesome-sails-token-patterns.md` ## Local Assets - `assets/token-scope-checklist.md` - `assets/token-crate-chooser.md` - `assets/token-gtest-matrix.md` ## Required Sequence 1. Define token intent and deployment shape with `assets/token-scope-checklist.md`. 2. Choose the smallest `awesome-sails` token stack with `assets/token-crate-chooser.md`. 3. Decide whether the token lives as a dedicated program or as embedded token-related services. 4. Name the role model and event model explicitly. 5. Keep the IDL and generated client path intact. 6. Write and execute the selected tests from `assets/token-gtest-matrix.md`. 7. Route to local smoke only after green gtest. ## Crate Selection Rules - Use the smallest awesome-sails surface that satisfies the feature. - Prefer base VFT-compatible behavior over custom token logic. - Add admin and RBAC layers only when the spec requires privileged token operations. - Add native-exchange only when value↔token conversion is part of the design. ## Dependency Source Rules Prefer one of: - crates.io version dependencies - pinned git dependencies - repository-relative `path` dependencies only for intentional local co-development Do not use absolute paths into `~/.cargo/git/checkouts`, `target`, or other machine-local caches. ## Guardrails - Do not write a custom fungible token from scratch when awesome-sails already covers the standard path. - Do not mix unrelated token policy decisions into implementation before the spec is written. - Do not bypass IDL/generated clients for the normal token path. - Do not treat token events as optional for production-facing state transitions. - Do not make every app build its own mint/burn/allowance logic ad hoc. - Do not point dependencies to `~/.cargo/git/checkouts/...` or other machine-local Cargo cache paths. - Prefer crates.io versions, a pinned git dependency, or a repository-relative path only when the project intentionally vendors or co-develops the dependency.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.