Menu
Use when implementing any Midnight example dApp to ensure compliance with quality standards and project conventions.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Use 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.
| name | dapp-sdd:constitution |
| description | Use when implementing any Midnight example dApp to ensure compliance with quality standards and project conventions. |
This constitution defines non-negotiable standards for all example dApps built with the dapp-sdd plugin.
contracts/ directory@midnight-ntwrk/*)create-mn-appAll code must pass quality checks with zero warnings or errors:
| Check | Command | Requirement |
|---|---|---|
| Linting | npm run lint | No errors, no warnings |
| Formatting | npm run format:check | No formatting issues |
| TypeScript | tsc --noEmit | No type errors |
| Compact | compact compile | Clean compilation |
Quality gates are mandatory before every commit.
readme-and-co:documentation-standardsgit-lovely:useful-commits skill for commit messages{feature-name} (provided by user)counter-example, token-transferAfter each implementation phase, run BOTH reviews:
Use compact-reviewer:compact-reviewer agent
Instructions: "You are reviewing an example dApp for the Midnight Network.
This project is intended to demonstrate concepts to developers learning Midnight.
Be pragmatic with suggestions:
- Focus on correctness and clarity over production concerns
- Flag anything that would confuse learners
- Flag bad practices that learners might copy
- Accept reasonable shortcuts that keep the example focused
- Ensure educational comments are accurate"
Use devs:code-reviewer agent
Instructions: "You are reviewing an example dApp for the Midnight Network.
This project is intended to demonstrate concepts to developers learning Midnight.
Be pragmatic with suggestions:
- Focus on correctness and clarity over production concerns
- Flag anything that would confuse learners
- Flag bad practices that learners might copy
- Accept reasonable shortcuts that keep the example focused
- Ensure educational comments are accurate"
All review issues must be addressed before proceeding to next phase.
TestContextPlugin state is stored in .dapp-sdd/ directory (gitignored):
.dapp-sdd/
├── spec.md # Expanded specification
├── plan.md # Implementation plan
├── tasks.md # Task list with checkboxes
└── pr-context.json # PR metadata
During implementation, leverage these skills:
| Phase | Skills |
|---|---|
| Specify | compact-core:language-reference, midnight-dapp:* |
| Plan | compact-core:contract-patterns, compact-core:typescript-integration, midnight-proofs:* |
| Implement | compact-core:standard-library, compact-core:privacy-disclosure, compact-core:testing-debugging, midnight-tooling:* |
| Commits | git-lovely:useful-commits |
| Docs | readme-and-co:documentation-standards |