菜单
Use when creating a phased implementation plan from a specification, with review gates after each phase.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | dapp-sdd:plan |
| description | Use when creating a phased implementation plan from a specification, with review gates after each phase. |
Creates a phased implementation plan with mandatory review gates.
.dapp-sdd/spec.md - The expanded specificationdapp-sdd:constitution - Quality standards to followA phased plan saved to .dapp-sdd/plan.md with:
Every plan follows this structure:
create-mn-app scaffold.dapp-sdd/ to .gitignore# {DApp Name} Implementation Plan
## Phase 1: Project Setup
**Goal:** Establish project foundation with quality tooling
### Tasks
1. Verify create-mn-app scaffold is complete
2. Configure ESLint with strict rules
3. Configure Prettier for formatting
4. Verify TypeScript strict mode
5. Add `.dapp-sdd/` to `.gitignore`
**Skills:** `midnight-tooling:midnight-setup`
### Review Gate
- [ ] `compact-reviewer:compact-reviewer` (if contracts exist)
- [ ] `devs:code-reviewer`
---
## Phase 2: Contract Implementation
**Goal:** Implement the Compact smart contract
### Tasks
1. Create contract skeleton in `contracts/{name}.compact`
2. Define ledger state
3. Implement circuit: `{circuit_name}`
4. Add witness functions
**Skills:** `compact-core:language-reference`, `compact-core:contract-patterns`, `compact-core:standard-library`
### Review Gate
- [ ] `compact-reviewer:compact-reviewer`
- [ ] `devs:code-reviewer`
---
(Continue for remaining phases...)
.dapp-sdd/spec.mddapp-sdd:constitution.dapp-sdd/plan.mdReference these skills in the plan:
compact-core:contract-patterns - Contract design patternscompact-core:typescript-integration - TS integration patternsmidnight-proofs:* - Proof generation approachmidnight-tooling:midnight-setup - Tooling configurationUse when encountering "potential witness-value disclosure" compiler errors, implementing commit-reveal patterns, working with persistentCommit/transientCommit vs persistentHash/transientHash, or designing privacy-preserving circuits with proper witness protection.
Use when asking about zero-knowledge proofs, ZK SNARKs, circuit compilation, witness data, prover/verifier roles, constraints, or how Midnight uses ZK for privacy.
Use when subscribing to real-time blockchain events, setting up WebSocket connections, monitoring contract state changes, building live dashboards, or implementing push notifications from Midnight.
Use when querying the Midnight indexer for blockchain data, fetching account balances, listing transactions, reading contract state, or building data-driven DApp backends.
Use when caching ZK proofs for performance, implementing proof cache invalidation, storing verification results, caching intermediate proof components, or building distributed proof caches with Redis.
Use when generating ZK proofs server-side, building proof-as-a-service backends, offloading proof computation from clients, creating proof generation queues, or implementing async proof generation.