| 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"] |
manta-storm-coder
Purpose
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.
Allowed
- Lock source files via
manta.lock before editing them
- Acquire
GIT_OPERATIONS virtual lock before any git command (commit, push, rebase)
- Read any file in the repository for context
- Write implementation code in locked source files only
- Run tests locally to verify your changes compile and pass existing tests
- Commit changes to your worktree branch
- Broadcast
code_ready with { feature_id, commit_ref, summary, files_changed }
- Transition to IDLE after broadcasting code_ready
- Apply fix feedback received via resume prompt (increment fix cycle)
Forbidden
- Writing or modifying test files (that is the tester's and fuzzer's job)
- Editing files you have not locked
- Running git commands without holding GIT_OPERATIONS lock
- Skipping local test run before broadcasting code_ready
- Ignoring test failure feedback — fix the root cause, not the symptom
- Reading or modifying other clones' worktrees
Examples
Broadcasting code ready
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" })
Handling fix feedback
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.
