HE
78 souls, by quality score.
01 · № 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.
02 · № 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.
03 · № 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.
04 · № 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.
05 · № A817·53F7 · Coding pair
★ 6Sets up a direct, goal-focused AI collaborator for building a self-hosted, filesystem-native life OS. It pushes back on scope creep, premature refactors, cloud lock-in and database migrations, and communicates in short, precise next steps.
06 · № B081·EFA5 · Coding pair
★ 30A project-level soul document that sets design principles, a tech stack, crawler-friendly and performance red lines, and non-negotiable rules for an AI coding agent working on a personal blog. It describes a junior-developer persona voice and a sense of playful, down-to-earth work.
07 · № 7EF6·36A1 · Coding pair
★ 36Sets up a senior frontend engineer who prioritizes Core Web Vitals, WCAG 2.1 AA accessibility, and measurable before/after results, with clear trade-off reasoning and no invented performance data. It also defines boundaries around not approving or publishing on the user's behalf and confirming destructive actions first.
08 · № C2BE·F185 · Coding pair
★ 8Sets up a warrior-themed security reviewer that hunts SQL, NoSQL and other query-layer injection in codebases, including ORM escape hatches and stored procedures. It requires reading a skill file first, tracing source-to-query paths, citing file:line, and flagging findings that need live validation.
09 · № 4BF9·B15A · Coding pair
★ 111Sets up a methodical, patient debugger that gathers evidence, reproduces issues, isolates problems systematically and cites documentation before forming conclusions. It keeps detailed memory notes of root causes and failure patterns.
10 · № F929·938A · Coding pair
★ 24Sets up a calm, factual, concise technical assistant that reads code, diagnoses root causes, and gives minimal executable fixes with stated assumptions and risks. It avoids flattery, separates evidence from guesses, and structures answers by problem type.
11 · № 9863·2B07 · Coding pair
★ 11A terse coding agent named Builder that receives tasks, implements them with tests, and opens PRs without chatting or making architectural decisions on its own. It enforces Material UI, TypeScript and never pushing to main.
12 · № F722·3F5A · Coding pair
★ 7Sets up a meticulous AI game developer that builds 2D browser games step by step in a sandbox. It prioritizes polished visuals, milestone-gated development, retrieval of design data before writing physics or balance code, and transparent ReAct-style logging.
13 · № 2512·BF53 · Coding pair
★ 59Sets up a reliable, pragmatic SRE partner that gives the conclusion first, supporting evidence and next steps, avoids filler, flags uncertainty with verification paths, and stays cautious with high-risk changes.
14 · № 807C·0FBB · Coding pair
★ 48Sets up a careful, direct software engineer who values correctness, understands problems before coding, asks when unclear, and keeps scope tight. Written as a SOUL.md identity file with style, avoidances and technical preferences.
15 · № 08E9·079F · Coding pair
★ 8Sets up a triage agent that removes noise from bulk security findings, merges duplicates and related issues on the same locus, and assigns defensible CVSS scores and severity bands. It is a strictly procedural working style with no conversational voice.
16 · № 2D88·9E13 · Coding pair
★ 2A Dutch-language portable profile for a builder agent that ships narrow, verified code and product slices, keeps diffs small, and asks for approval before publishing, sending, deleting or changing credentials. It also sets strict rules for running Codex in isolated worktrees and treating its output as untrusted.
17 · № 58A9·A8AF · Coding pair
★ 1Sets up a senior software engineer who verifies claims against the repo and docs, makes minimal surgical changes, tests every fix, and avoids silent failures. Direct and technical with no filler, and pushes back on risky shortcuts.
18 · № 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.
19 · № D04E·6BF4 · Coding pair
★ 5Sets up a self-evolving agent that reads and digests the project before answering, holds opinions, and defaults to executing tasks end-to-end with minimal permission-seeking. It keeps its identity in persistent files it reads and updates each session.
20 · № 2DCF·DADA · Coding pair
★ 80Sets up a direct, practical local coding assistant that works within the current repository, treats project rule files as authoritative, makes small reviewable changes, and proactively uses a live Hunk review session for code feedback.
21 · № E37C·A96F · Coding pair
★ 1Sets up a implementation-focused coding agent that takes specs, writes tested code, and opens tight, well-described PRs without scope creep. It is a seed template for per-agent souls in a multi-agent team.
22 · № 2BC4·FEB9 · Coding pair
★ 1A template-architect agent that maintains the Harness SDD framework's conventions, manifest-first and deterministic, and refuses shortcuts like hand-editing generated files or skipping checks. Its tone is direct, precise and terse, leading with constraints before solutions.
23 · № 42BF·2C02 · Coding pair
★ 1A base QA role soul focused on release verification, integration testing and regression hunting. It sets a curious, specific, neutral reporting style and tells the agent to verify rather than rubber-stamp, and to be honest about untested gaps.
24 · № 0F71·72A5 · Coding pair
★ 1Sets up Chris, a strict but constructive code reviewer who flags security, quality and tech-debt issues with severity labels, and stays within review scope while coordinating with six other team roles via @mentions in Feishu.
25 · № 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.
26 · № 1928·65A9 · Coding pair
★ 101Sets up a meticulous, methodical Golang engineer agent that works through assigned GitHub issues, writes tests and docs, manages pull requests, and reports progress in detail. The base SOUL template adds guidance on competence, respectful handling of private access, and cautious external actions.
27 · № A292·FBC2 · Coding pair
★ 4Sets up a direct, correctness-first developer agent that reads full context before coding, follows every workflow phase, completes the commit, PR and notification lifecycle, and respects strict git and workspace boundaries.
28 · № B8C1·3C1C · Coding pair
★ 25A focused QA agent that turns plain-English requirements into deterministic, CI-friendly end-to-end tests and diagnoses failures in a strict CATEGORY/REASON/FIX format. It sets rules on selectors, secrets and git safety, with no personality flourish.
29 · № 0D22·4BC7 · Coding pair
★ 1Sets up smolbot as a practical coding agent that speaks calmly and directly, avoids claiming unwired capabilities, and prefers small testable changes over broad rewrites. It also tells the agent to load any skill that might apply.
30 · № CAFA·DE0A · Coding pair
★ 6Sets up an agent that locks a character's visual identity (face, exact eye shade, hair, costume, marks) and records it in a characters.md file so it never drifts. The style is terse and procedural.