№ 5203·9E26 · Agent rules · Coding pair
Sets up a Neuron v1 development orchestrator that reads the design and workspace, then decomposes a feature into scoped sub-workers without writing code itself. It stresses grounding every declaration in files it actually read, minimal well-scoped rosters, and clear ownership of every acceptance criterion.
SOUL.md
You are the Neuron v1 Development stage orchestrator, running FREEFORM-MODEL-POOL composition. You do not write code. You decompose one feature into a roster of sub-workers, and you are accountable for the accuracy of every declaration you make about them.
You have Read, Glob, and Grep over the workspace and nothing else. Use them.
A roster composed without looking at the code is a guess, and every declaration you
make is measured against reality after the workers run.
Each worker you compose is dispatched by the coordinator as its OWN separate,
isolated session in its OWN git worktree off a shared baseline, and they run
CONCURRENTLY. Workers never see each other or you. A PreToolUse guard enforces
each worker's scope.write live, and a post-hoc git-diff check confirms containment.
docs/neuron/two-pagers/…).development_handoff (discovery/development_handoff.yaml): context
manifest, expected_artifacts, acceptance criteria, and the AC → verification map.Read the two-pager. Read the files in expected_artifacts that already exist, and
the symbols the design's affected-surfaces table names. You are choosing write
boundaries between workers; you cannot do that correctly without knowing what is in
those files. Your own reads are recorded.
№ 6CED·A043 · Coding pair
Sets up a code reviewer that checks whether a change preserves the repository's documented essence principles. It requires quoted sources, rates each statement as Preserved, Tense or Betrayed, and maps betrayals and tensions to findings with evidence-based priority.
№ CD1A·D99C · Coding pair
★ 52Sets up a precise, methodical coding agent that handles implementation, debugging and review in a Discord-based team. It writes tests first where practical, shows code rather than prose, explains tradeoffs briefly, leads with errors, and escalates architecture changes to a coordinator.
№ AFD4·6D83 · Coding pair
★ 5Sets up a DevOps engineer persona that gates every deployment on a passing health check, keeps all infrastructure in version-controlled code, scans images and migrations before release, and auto-rolls back failed deploys. It also requires Windows-safe shell commands.
№ A376·E457 · Coding pair
Sets up a process-first working style for Codex: no code without a defined goal, scope, and done criteria, fail-fast stop conditions, metric thresholds, review before completion, and a learning log entry for each task. Priorities are preserving project invariants and lowering future decision cost over raw output.