HE
78 souls, by quality score.
61 · № B90F·651E · Coding pair
Sets up a thorough, evidence-driven working style: run automated tools before forming judgments, trust execution results over reading code, reject unverified claims like "it probably works", and report issues with specific file paths and line numbers.
62 · № 3205·67AC
Sets up an agent that builds premium, animated web experiences with Laravel, Livewire and FluxUI, requiring light/dark theme toggles and polished micro-interactions. It describes a creative, performance-focused persona that reports its enhancements and technology choices specifically.
63 · № 8772·D42C · Coding pair
Sets up a minimal agent that executes tests and reports raw results without interpreting, suggesting, or judging them. It is framed as a pure function from tests to results.
64 · № A3E4·FDCC · Coding pair
★ 2Sets the agent up as a debugger that forms hypotheses, separates symptoms from causes, and prefers minimal reproduction and instrumentation over guessing.
65 · № 84C5·C5B8 · Coding pair
★ 2Sets the agent up as a technical architect that focuses on system boundaries, maintainability, failure modes and migration paths, and pushes back on vague requirements and weak abstractions.
66 · № A5B4·893A · Coding pair
★ 1Sets up a careful, pragmatic engineering collaborator that verifies results before claiming success, prefers small reversible changes, states uncertainty openly, and reports when it is running in a degraded mode.
67 · № 8F1F·2403 · Coding pair
Royle is a persona that hunts bugs to their root causes, rejects placeholder code and hand-waving, and values working software over ceremony. It guards a codebase against technical rot.
68 · № 3AF3·31FD · Coding pair
Sets up an agent to review DocumentDB documentation changes for accuracy, clarity, completeness and consistency, posting inline comments and a LGTM, NEEDS CHANGES or NEEDS DISCUSSION verdict. It is direct, prioritizes accuracy over style, and is explicitly barred from writing docs, merging, or modifying code.
69 · № 1E72·F798 · Coding pair
Sets up a calm, precise documentation teammate that keeps answers concise, backed by evidence, honest about uncertainty, and clear about blockers and limits of its authority.
70 · № 8530·B9BC · Coding pair
Sets up a Support agent that reproduces bugs before fixing them, pursues root causes, runs regression tests, documents fixes and escalates large issues to HBx. The tone is methodical, patient and reliable.
71 · № AB76·A9ED · Coding pair
Sets up a calm, precise verifier persona that keeps answers concise and evidence-based, admits uncertainty, favors useful artifacts over performance, and flags blocked, risky or out-of-scope work.
72 · № A497·3625 · Coding pair
Sets up an implementation-focused engineer persona that turns concepts into clean, documented, evidence-based code and defers creative or design decisions to an architect role.
73 · № 96DD·7A24 · Coding pair
Sets up a design-focused agent that owns visual direction, validates interfaces for accessibility and hierarchy, and records durable design decisions through memory tools. The working style is restrained and outcome-driven, though much of the text is generic.
74 · № B102·B0D1 · Coding pair
Sets up a calm, precise maintainer persona that keeps answers concise and evidence-based, admits uncertainty, favors useful artifacts over performance, and flags blocked, risky or out-of-scope work.
75 · № 4374·6162 · Coding pair
Sets up a planning agent that produces architecture blueprints without writing the code itself. Designs must be grounded in the existing codebase structure and conventions, and each plan must define verification steps and user review requirements.
76 · № CC98·F20D · Coding pair
Sets up a cautious senior software engineer persona that prioritizes stability, simplicity and bounded changes on an operational atmospheric modeling codebase. It explicitly avoids overengineering, unnecessary abstractions, architecture redesign and unrelated edits.
77 · № 1EFA·B0FA · Coding pair
Sets up a calm, precise architect persona that gives concise, evidence-based answers, admits uncertainty, favors useful artifacts over performance, and flags blockers and risks.
78 · № F5A8·99E5 · Coding pair
★ 1A terse, step-by-step working procedure for an agent fixing an injected bug in a codebase, with strict rules on tests, installs, and scratch files. It sets a budget and insists on verifying output rather than exit codes.