OT
20 souls, by quality score.
01 · № 074F·9121 · Coding pair
★ 20Sets up Puffer, a terminal coding agent that investigates, changes and verifies code end-to-end with a blunt, concrete voice. It favors the smallest fix, verified claims, and refuses fabricated results and telemetry.
02 · № D70C·B61E · Coding pair
★ 89A calm, decisive team lead persona that decomposes goals, delegates to workers, and insists on evidence like test runs and artifacts before accepting work as done. It pushes back on incomplete briefs and surfaces blockers quickly.
03 · № 523E·810F · Coding pair
★ 134Sets up a principal coding agent that reads the project first, plans with a TODO list, executes and tests each step, and reports only verified progress. It is direct and thorough rather than theatrical, and it is provider-agnostic.
04 · № C212·8C59 · Coding pair
★ 25Sets up a terminal coding agent with a stable working identity that prefers reading code and running checks over guessing, makes minimal in-idiom diffs, and narrates outcomes like a colleague. It is written as a self-described soul with convictions about memory and autonomy.
05 · № DE1A·9CB7 · Coding pair
★ 11Sets up a friendly, proactive coding persona that routes work to specialist agents, writes tests first, prioritizes security, plans before executing, and avoids emoji in favor of SVG or plain Unicode. It also emphasizes lightweight model use to control cost.
06 · № D54C·2F4C · Coding pair
★ 66Sets up a concise, direct senior developer persona that explains trade-offs, asks for clarification on ambiguous requests, avoids unapproved changes, and logs progress, bugs and decisions into project memory files.
07 · № CEA4·CAB9 · Coding pair
★ 8Sets up a git agent that runs version control over the ChittiOS store with shell-like commands, short imperative commit messages, status checks before commits, and verbatim error reporting.
08 · № 3445·3E58 · Coding pair
★ 5A UX designer persona focused on scannable interfaces, WCAG 2.1 AA accessibility and consistency with ICDEV's existing Jinja2 and HTMX patterns. It requires user-journey mapping before screen design and Playwright validation before UI work is marked done.
09 · № 07CD·1AA2 · Coding pair
★ 4Sets up a calm, adversarial root-cause analyst that wakes on BLOCKED tasks, traces defects to their origin phase, applies minimal state corrections, and escalates unresolvable blocks instead of forcing success. Work is driven through mandatory tool calls rather than pasted code.
10 · № D728·A346 · Coding pair
★ 2Sets up a review agent that checks diffs against the work order, cites file and line for each finding, refuses to rubber-stamp changes, and reports problems without rewriting the code.
11 · № 9EC5·AE33 · Coding pair
★ 2Sets up a reviewer role that independently assesses a builder's code for correctness, architecture fit, security and performance, issuing PASS or FAIL verdicts with severity-graded, evidence-based findings and no code writing.
12 · № 0A3F·8A3A · Coding pair
Sets up an autonomous executive agent that orchestrates worker coding CLIs through isolated Git worktrees, demands machine-verifiable proof instead of claims, kills and retries failing workers, and records every mistake as a convention. Its working style is strict, process-driven and terse.
13 · № A8C8·A4BE · Coding pair
Sets up a direct, analytical personal assistant and debugging partner in Spanish with a rioplatense touch. It requires explicit confirmation before sending emails, editing project files or deleting anything, and manages persistent memory across sessions.
14 · № 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.
15 · № D008·A67C · Coding pair
★ 1Sets up Archie as the scaffolding agent in a builder pipeline, creating protocols, in-memory fakes, Hypothesis property tests and module skeletons from a Spec without writing implementation code. The working style is procedural and checklist-driven, with pipeline position and file conventions spelled out.
16 · № 1B95·7851 · Coding pair
★ 4Sets up a risk-focused reviewer that escalates security, performance and test-quality gaps, blocks ships on non-negotiable concerns, and gives specific, proportionate findings. It is a template with placeholders for the user's own compliance and performance context.
17 · № AE83·CF84 · Coding pair
Sets up a direct, concise lead engineer persona for a thesis PWA project that asks for clarification before editing code, enforces modular mobile-first design, and communicates in Indonesian. It is tuned for terminal use over SSH on a phone.
18 · № CE21·363F · Coding pair
A values document for BeeHarness that sets up a human-sovereign hive where agents act as scouts, builders and reviewers with bounded mandates. It stresses verified evidence, transparency, lightweight decoupled design and honest trade-offs with clear recommendations.
19 · № 3888·97AA · Coding pair
★ 3Sets up a high-performance agentic OS orchestrator with native machine access that plans step by step, uses tools precisely, and asks for manual approval on risky actions. Tone is concise, technical and high-integrity.
20 · № 03A7·76C2 · Coding pair
Sets up a coding agent that speaks plainly, makes concrete edits rather than abstract proposals, and keeps the user informed without narrating every step. Correctness is treated as part of its voice.