Menu
Cluster related instincts and evolve them into skills, commands, or agents
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Senior backend architect for system design decisions — service decomposition, database schema design, API contract governance, migration strategy, reliability and observability patterns. Use when designing a new backend system or service, choosing between monolith/microservices, designing schemas or APIs, or planning a data migration. Advisory only — produces specifications, does not write code.
Branch synchronization agent — merges the team base branch into the current feature branch before a PR, resolves merge conflicts with three-way evidence and intent analysis, verifies the merge with a build and targeted tests, and reports what was merged and how each conflict was resolved. Use when preparing a branch for a PR, when a PR has conflicts with its target, or when asked to sync/update a feature branch with developer/main.
Browser testing agent — verifies web features and user flows end-to-end by writing and running re-runnable Playwright scripts, capturing screenshot/console/network evidence, and producing structured test reports. Use when a UI change needs real-browser verification, a user flow needs smoke testing, a UI bug needs reproduction, or the user asks to test the site in a browser and report results.
Expert code reviewer providing constructive, prioritized feedback on correctness, security, maintainability, performance, and test coverage — not style preferences. Use when reviewing a diff, branch, or PR for general quality. For a security-only deep audit, use the security-reviewer agent instead.
Expert frontend developer for building and improving web UI — components, state management, responsive layouts, accessibility, and Core Web Vitals performance. Use when implementing UI features or component libraries, fixing layout/responsiveness issues, improving accessibility compliance, or optimizing bundle size and page performance.
"Codebase onboarding specialist — builds fast, accurate mental models of unfamiliar repositories by reading source, tracing execution paths, and stating only facts grounded in inspected code. Use when onboarding into a new codebase, asking "where should I start", "what owns this behavior", or "how does a request flow through this system". Strictly read-only and descriptive — no reviews, refactors, or recommendations."
| name | evolve |
| description | Cluster related instincts and evolve them into skills, commands, or agents |
Evolve accumulated instincts into higher-level structures. This is a two-step flow: the CLI finds and prints clusters of related instincts; you (Claude) then read that output and write the evolved files yourself.
python3 "${PLUGIN_ROOT}/skills/auto-learning/scripts/instinct-cli.py" evolve
The CLI loads all instincts from ~/.codex/homunculus/instincts/, groups them by normalized trigger, and prints:
The only flag is --generate, which just prints the target directories — the CLI never writes evolved files itself. There are no other flags.
For each cluster the user wants to evolve, read the underlying instinct files, then write the evolved file to ~/.codex/homunculus/evolved/{skills,commands,agents}/. Decide the type:
Write each evolved file as markdown with frontmatter linking back to its source instincts:
---
name: <kebab-case-name>
description: <one line, trigger-oriented>
evolved_from:
- <instinct-id-1>
- <instinct-id-2>
- <instinct-id-3>
---
# <Title>
<Synthesized instructions combining the clustered instincts: when to apply,
the steps to follow, and any evidence-backed caveats.>
~/.codex/homunculus/evolved/.