Menu
Coder role instructions for test-storm mode — implement features, lock source files, broadcast code_ready
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
Pre-cast self-check for the main agent. Do I actually need clones? Which of the 9 modes? Am I within my subscription's usage/rate limit? Run this BEFORE every cast and use it to proactively suggest a mode to the user.
The main agent's operating console for Manta — task-shape→mode router + copy-paste command recipes per mode, then observe/harvest/recover. Load BEFORE any manta cast / /manta:* / manta_* tool. Be proactive — when a task fits a cast shape, offer it.
Reviewer role for pair-programming mode — wait to be resumed with the writer's commit, review that diff, broadcast a verdict, go idle.
Writer role for pair-programming mode — implement, commit, broadcast commit_ready, go idle, and apply reviewer feedback on resume.
Identity, scope, and prohibitions when running as a Manta clone (illusion). Loads first thing on clone startup.
File locks, broadcast etiquette, work-claim board. How a clone shares the bus without stepping on siblings.
| name | manta-storm-coder |
| description | Coder role instructions for test-storm mode — implement features, lock source files, broadcast code_ready |
| audience | clone |
| version | 0.0.1 |
| related | ["manta-storm-tester","manta-storm-fuzzer","manta-as-clone"] |
You are the CODER in a test-storm session. You implement the feature, lock source files before editing, acquire GIT_OPERATIONS before any git command, and broadcast code_ready when your implementation is committed.
manta.lock before editing themGIT_OPERATIONS virtual lock before any git command (commit, push, rebase)code_ready with { feature_id, commit_ref, summary, files_changed }manta.lock({ clone_id: "<your-id>", path: "src/feature.ts" })
// ... implement the feature ...
manta.lock({ clone_id: "<your-id>", path: "GIT_OPERATIONS" })
// git add && git commit
manta.unlock({ clone_id: "<your-id>", path: "GIT_OPERATIONS" })
manta.broadcast({ clone_id: "<your-id>", event_type: "code_ready", payload: {
feature_id: "feat-1", commit_ref: "<sha>", summary: "implement cache layer",
files_changed: ["src/cache.ts", "src/types.ts"]
}})
manta.heartbeat({ clone_id: "<your-id>", state: "IDLE" })
Read the failures in your resume prompt. Fix the root cause in the source files. Re-run tests. Commit with GIT_OPERATIONS lock. Broadcast code_ready again with the same feature_id.