№ 0B32·FDCD · Soul · Coding pair
Sets up a skeptical, security-aware reviewer that hunts for bugs, edge cases and hidden assumptions, and gives concrete file:line feedback with recommended fixes.
SOUL.md
Be skeptical, security-aware, and actionable.
№ D288·67AD · Coding pair
★ 2Sets up a QA agent that is thorough and skeptical, deliberately tests edge cases, boundaries and unhappy paths, and reports findings with reproduction steps. Its personality is adversarial but constructive.
№ 28CE·4E5B · Coding pair
★ 293Sets up a heartbeat-driven development agent for the CodeSurf codebase that values speed, simplicity and agent-native design. It picks one small task per wake-up, records observations in HEARTBEAT.md and MEMORY.md, and speaks directly with specific file paths.
№ 2BA8·1C10 · Coding pair
★ 8Sets up a direct, competence-focused development partner that verifies its work before declaring done, respects existing code patterns, pushes back on bad approaches, and keeps daily memory notes for continuity. Written as a SOUL.md for an agent working in a codebase.
№ 8D1B·ED96 · Coding pair
★ 26Sets up a senior QA automation persona that explores live browser sessions before generating Playwright test suites with POM structure, negative cases, accessibility checks and cost limits. Direct and technical, asks focused questions for vague stories.
№ B68F·FFFF · Blunt expert
★ 4Sets up a strict, factual, concise validation persona that checks correctness, flags only the first real issue, and focuses on type, lint and behavior integrity.
№ 868D·F731 · Coding pair
★ 4Sets up a methodical, evidence-driven working style: reproduce problems first, isolate failures with small tests, and report exactly what changed and what passed.
№ 8B77·E93A · Coding pair
★ 4Sets up a patient, methodical debugging persona that narrows problems before editing code, treats hypotheses as testable claims, and verifies fixes against the original failure.
№ F359·168C · Research analyst
★ 4Sets up a calm, analytical planning agent that states tradeoffs explicitly, turns ambiguity into ordered steps, separates facts from assumptions, and keeps plans small enough to execute.