dash-platform-workflows

name	dash-platform-workflows
description	Implement and validate standalone Dash Platform JavaScript workflows for wallets, identities, DPNS names, contracts, and documents. Use when Codex needs a repository-agnostic Dash Platform testnet workflow or when extracting a reusable Dash control center into a new project.

Dash Platform Workflows

Start Here

• This skill is standalone. Do not assume any repository-specific docs, task tooling, or file layout.
• Read references/operating-model.md before choosing commands, state storage, or file structure.
• Read references/sdk-deviations.md before copying tutorial examples into live code.
• Read references/extension-roadmap.md when moving beyond tutorial parity into product workflows.

Operating Rules

• Keep secrets in .env or an equivalent private state store. Document only public identifiers and non-sensitive outcomes.
• Keep project-specific state snapshots outside the reusable skill instructions.
• Prefer existing scripts and conventions if the host project already has them. Otherwise scaffold a minimal Node.js CLI surface.
• Make every write flow idempotent. Detect existing transactions, identities, names, contracts, and documents before creating new ones.
• Verify the official Dash docs section for the target workflow, then confirm the installed SDK surface locally before implementation.
• Distinguish stable facts, runtime-verified findings, and project-specific assumptions in the final documentation.

Minimal Workflow

1. Establish the target network, mnemonic source, and private state store.
2. Choose or scaffold a small command surface for connectivity, funding, identity, name, contract, and document operations.
3. Reuse the state model and command-family guidance from references/operating-model.md.
4. Apply the runtime deviations from references/sdk-deviations.md instead of trusting stale tutorial snippets.
5. Verify on testnet with the smallest live command set that proves the intended behavior.
6. Record public IDs, revisions, balances, and protocol findings in project-local docs or state memory.

Portability Rules

• Keep the skill folder self-contained.
• Do not require a specific workflow framework or repository structure.
• If the host project has task tracking or policy tooling, adapt to it instead of assuming it.
• When exporting the skill, ship the whole folder intact: SKILL.md, agents/openai.yaml, and references/.

References

• references/operating-model.md: portable state model, suggested command families, and integration patterns.
• references/sdk-deviations.md: verified Dash Platform SDK/runtime pitfalls and working substitutes.
• references/extension-roadmap.md: a generic roadmap after tutorial parity is complete.