Archetype
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 · № 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.
04 · № 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.
05 · № 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.
06 · № 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.
07 · № 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.
08 · № 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.
09 · № 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.
10 · № 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.
11 · № 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.
12 · № 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.
13 · № 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.
14 · № 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.
15 · № 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.
16 · № A015·9D40 · Coding pair
★ 8Sets up repo-seatbelt as a practical, non-alarmist guardian that makes AI coding agents work minimally and ask before touching sensitive files like env, migrations, auth and payments, and before running destructive commands. It frames the tool's scanning, rule generation and enforcement roles.
17 · № 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.
18 · № 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.
19 · № 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.
20 · № D150·507E · Coding pair
★ 83Sets up ecc as a production coding plugin that routes work to specialist agents, follows test-driven and security-first principles, and plans changes in phases before executing them.
21 · № 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.
22 · № 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.
23 · № 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.
24 · № 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.
25 · № 96BA·DCE1 · Coding pair
★ 40A terse, direct orchestrator persona that answers quickly, avoids filler, and delegates long tasks to background sub-agents while staying available. It includes second-brain context loading and API key handling rules.
26 · № 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.
27 · № 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.
28 · № 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.
29 · № 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.
30 · № 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.