.fyi
SkillsMCPPluginsSubagents

Browse by category

DevOps & CI/CD SkillsProductivity & Workflow SkillsOther SkillsProduct & Project Management SkillsDocumentation & Knowledge SkillsCode Review & Refactor SkillsBackend & APIs SkillsAgent Meta & Communication SkillsResearch SkillsSecurity SkillsUX UI & Design SkillsTesting & QA SkillsSee all →

Every Claude Code skill, MCP server, plugin and subagent in one directory. Searchable, comparable, and one command from installed. Live stats from GitHub, npm and PyPI.

We're on Product HuntYour agent's app storeCheck it out →
Agent SkillsMCP ServersPluginsSubagentsCoding Agents
CollectionsOfficial publishersGlossaryFAQBlogSearchSavedFeedback
PrivacyTermsllms.txtSitemap

made with ♥ · © 2026 aaaa.fyi

Independent project · real data from public registries

…/studiokjm/ai-harness-template
home/subagents/studiokjm/ai-harness-template
studiokjm avatar

studiokjm/ai-harness-template

11 subagents

View on GitHub
Subagent
architectUSE THIS WHEN symptoms keep recurring, layer boundaries blur, or changes ripple unexpectedly. ALWAYS invoke for structural diagnosis during /unstuck or major refactors. Finds root causes in design,…contrarianUSE THIS WHEN the team reaches quick consensus, before committing to a major design decision, or during /evolve and /unstuck. Challenges assumptions with "what if we're wrong?" scenarios. Always…evaluatorUSE THIS WHEN verifying implementation against a seed spec, running gates, or assessing AC compliance. ALWAYS invoke during /evaluate. Never fixes — only judges Pass/Fail with file:line evidence.…hackerUSE THIS WHEN the official path is blocked, a deadline looms, or a temporary workaround is acceptable. ALWAYS invoke during /unstuck when standard approaches fail. Finds safe bypasses (monkey-patch,…interviewerUSE PROACTIVELY whenever the user describes a new feature, vague requirement, or unclear goal. ALWAYS run BEFORE writing code or creating a seed spec. Asks Socratic questions to surface hidden…navigatorUSE THIS as the planning half of pair programming during /run (PAIR_MODE). Generates 3 solution plans per AC, selects optimal one, directs Driver. Never writes code directly. Based on PairCoder (ASE…ontologistUSE THIS WHEN defining domain terms, extracting entities/relationships from requirements, or unifying synonyms (e.g., "user" vs "member" vs "account"). ALWAYS invoke during /seed spec generation.…researcherUSE THIS WHEN a claim needs evidence, debugging requires history, or library/API behavior is uncertain. ALWAYS invoke before guessing — checks official docs, existing code patterns, git log/blame…seed-architectUSE THIS WHEN crystallizing interview results into an immutable specification. ALWAYS invoke during /seed. Converts conversation + ontology into structured seed YAML with zero TODO/TBD tolerance.…simplifierUSE THIS WHEN code feels over-engineered, scope seems to creep, or abstractions pile up. ALWAYS invoke during /evolve and /unstuck. Asks "is this needed for MVP?" on every feature. YAGNI-first —…test-designerUSE THIS for independent test case generation during /run (PAIR_MODE). Designs tests from AC and seed spec only — never reads implementation code. Prevents biased testing. Based on AgentCoder (2024)…