optimus-prime

$npx mdskill add avibebuilder/claude-prime/optimus-prime

Generates a tailored Claude Code configuration for a specific project

  • Identifies and analyzes the real codebase to understand its conventions and patterns.
  • Deploys necessary skills, rules, and CLAUDE.md entries based on the analysis.
  • Preserves existing intentional work while refreshing or filling gaps in the config.
  • Delivers a customized Claude Code configuration for optimal project performance.

SKILL.md

.github/skills/optimus-primeView on GitHub ↗
---
name: optimus-prime
argument-hint: additional-context
description: "Generates a Claude Code configuration tailored to a specific project. Use whenever the user wants to prime a project, set up claude for a repo, bootstrap claude config, or re-prime/refresh an already-primed project (for example after `/prime-sync` pulled new starter content). Triggers on 'prime', 'prime this project', 'optimus-prime', 're-prime', 'refresh claude config', 'regenerate CLAUDE.md', 'set up claude for this repo'. Deeply analyzes the real codebase and builds project-specific skills, rules, and CLAUDE.md — not generic boilerplate. For ongoing config health checks and proposal review, use `self-evolve` instead."
disable-model-invocation: true
---

Ultrathink.

## Mission

Generate a Claude configuration that fits the specific project. Every skill, rule, and CLAUDE.md entry must exist because this project needs it — not because a template included it. Analyze the real codebase deeply, understand its conventions and patterns, and build a config that makes Claude work well here.

## Modes

- **Fresh prime** — no claude config yet. Build from scratch.
- **Re-prime** — claude config already exists. Preserve intentional project work, refresh what is stale or generic, fill gaps.

Default to re-prime whenever meaningful existing config is found. Never overwrite it wholesale without user approval.

## Flow

1. **Analyze** the repo deeply — stack, conventions, boundaries, docs, existing config. See [analysis-checklist.md](./references/analysis-checklist.md).
2. **Propose** findings using the Output Format below. Do not touch meaningful files before approval.
3. **Create skills** via `/skill-creator` — every skill must go through skill-creator to ensure quality and project fit. Starters in `.claude/starter-skills/` are reference input to accelerate creation, not templates to copy.
4. **Generate or refine CLAUDE.md** — lean, high-signal, always-on context only. Point to docs/READMEs for detail.
5. **Rules only if needed** — apply the rule test. Zero rules is valid.
6. **Offer CLAUDE.local.md** — personal preferences (role, sandbox URLs, preferred test data, workflow quirks), gitignored.
7. **Clean up** — delete `.claude/starter-skills/` after processing. Keep protected skills. Confirm all deletions.
8. **Verify** — references resolve, stack claims match evidence, config is project-specific not generic.
9. **Offer skill optimization** — after everything is set up, offer optimization paths sized to how many new skills were created. ≤3 skills: recommend full optimization for all. >3 skills: recommend full optimization for user-designated core skills only + description optimization for the rest (avoids long execution time and token burn). Always emphasize that full optimization takes meaningful time and tokens. **Run sequentially — never in parallel; concurrent runs overload the user's machine.**

Follow full step-by-step in [setup-project.md](./references/setup-project.md).

## Placement Decision Matrix

Every piece of knowledge must earn its place. Use this to decide where it belongs:

| Detected need | Where it belongs | Test |
|---|---|---|
| General framework/library knowledge | Skill (via `/skill-creator`) | Would a reusable skill teach this across projects? |
| Project-specific constraint that still produces wrong code with the right skill loaded | `.claude/rules/<name>.md` with `paths:` | With the relevant skill activated, will code still be wrong without this? |
| Identity, commands, stack, key architecture, reference pointers | `CLAUDE.md` | Should this be always-on for most tasks in this repo? |
| Detailed architecture or domain explanations | Existing `docs/`, READMEs — referenced from CLAUDE.md | Valuable but too detailed for always-on? |
| Dense agent-oriented reference material - referenced from CLAUDE.md | `.claude/project/` (optional) | Do agents need a tighter reference than the human docs provide? |

## Principles

- **Domain-scoped, project-fitted.** Skills target a capability, not the project itself — with this project's patterns baked in. Generic templates and project-named catch-alls both degrade context quality.
- **Repo evidence is the source of truth.** Verify conventions from actual source files, configs, and docs. Do not assert what you haven't confirmed.
- **Lean context, high signal.** Follow the context engineering philosophy — load only what's needed, when it's needed. CLAUDE.md carries always-on essentials. Skills load on demand. Rules auto-attach by path.
- **Rules are optional and path-scoped.** Only create a rule when the rule test passes. Do **not** modify `_apply-all.md` — it is a universal boilerplate rule from prime, not project config.
- **Reuse over duplication.** If the project has strong docs, point to them. Do not re-author parallel agent docs unless existing material is too noisy or incomplete.

## Output Format

Before making non-trivial changes, report findings in this shape:

### Current State
What Claude config already exists; what the repo evidence says about stack, tooling, and conventions.

### Proposed Changes
What to create, update, keep, or remove — including which skills to build and what each should cover.

### Files to Touch
Concrete file list with short purpose notes.

Include these only when non-empty:
- **Decisions Needing User Input** — overwrites, deletions, or major structural changes
- **Risks / Assumptions** — inferred facts that still need verification

After approval, implement and finish with a short summary of what changed and any follow-ups.

## References

| Reference | Content |
|---|---|
| [analysis-checklist.md](./references/analysis-checklist.md) | What to inspect during repo + existing-config review |
| [setup-project.md](./references/setup-project.md) | Fresh-prime / re-prime step-by-step workflow |

## Additional Context (Optional)

<user-context>$ARGUMENTS</user-context>

More from avibebuilder/claude-prime

SkillDescription
askAnswer questions about code, architecture, and technical decisions — no implementation. Trigger on questions asking 'why', 'what does this do', 'what is the purpose of', 'explain', 'what's the difference', 'compare', or 'what are the tradeoffs' — even when referencing specific files, code snippets, or inline code. The key signal is the user wants to UNDERSTAND something, not change it. Do NOT trigger for requests to build, fix, plan, review, research, or add/modify code.
backend-fastapi-pythonUse this skill for any Python backend work in this project: building FastAPI endpoints, writing service functions, defining Pydantic/SQLModel schemas, running Alembic migrations, or debugging 422 errors. Essential for authentication and authorization patterns — setting up get_current_user, is_superuser checks, admin-only guards, role-based access, and dependency injection chains like Depends(). Also covers middleware, background tasks, async SQLAlchemy sessions, ORM relationship loading, and request/response design. Activate whenever the question involves Python API code, FastAPI patterns, or backend architecture in this codebase. Not for frontend, Docker, CI/CD, or infrastructure.
create-docUse when the user wants to save knowledge as a file so others don't have to rediscover it — \"turn this into a doc\", \"write this up\", \"document how X works\", \"we figured this out and want to capture it\", \"nobody should have to figure this out again\". Covers any request to create or update durable written artifacts: onboarding guides, runbooks, ADRs, API docs, architecture notes, postmortems, changelogs, setup guides. The trigger: user wants knowledge captured in a file for future reference, not just a conversation. Do NOT use when still making decisions (→ give-plan), just asking for explanation without a file (→ ask), or writing code (→ cook).
discussBrainstorms and debates approaches, then drives toward an actionable decision. Use whenever someone needs a thinking partner for a decision they're facing: 'discuss', 'debate', 'brainstorm', 'weigh options', 'tradeoffs', 'should I do X or Y', 'help me decide', 'I'm torn between', 'sanity check my thinking', or 'what do you think about'. The user must be asking for help reasoning through a choice — not asking to build, fix, evaluate, plan, or modify something (even if the topic involves this skill itself). Picks the right decision lens, surfaces tradeoffs and blind spots, pushes back when reasoning is genuinely weak, and never implements.
docs-seekerFetch up-to-date documentation for any library, framework, API, or service into context. Use when the user wants to look up API references, check function signatures or required fields, find feature-specific docs, or verify how an external tool actually works. Triggers for queries about third-party libraries like Stripe, SQLAlchemy, Tailwind, FastAPI, shadcn, Drizzle, Hono, Better Auth — any time the answer lives in official docs rather than in the project codebase. Use this instead of guessing from trained knowledge, which is stale.
frontend-developmentUse this skill for ANY work involving React, Next.js, TypeScript, or Tailwind in the browser layer. This includes building components and pages, but equally covers debugging and fixing frontend issues: CSS/Tailwind classes not applying, form validation behavior, hydration mismatches between server and client renders, styling bugs, layout shifts, and rendering problems. Also use for refactoring components (e.g., splitting Server vs Client Components), data fetching patterns, state management, bundle optimization, and frontend tooling. If the problem involves what users see or interact with in a web browser — whether building, fixing, or refactoring — use this skill. Not for backend APIs, databases, infrastructure, or DevOps.
give-planUse when the user wants a written, reviewable plan or spec produced before coding starts. Triggers on: mapping out changes without implementing, thinking through risks of upgrades or migrations, evaluating approaches before committing to one, writing specs for team review, phasing work into stages, or any request that explicitly defers coding ('don't implement yet', 'before we build'). The distinguishing signal is that the user wants a plan artifact — not implementation, not a conversational answer. MUST activates inside Claude's native plan mode to have a better planning behavior.
media-processorSpecialized visual and multimedia processing tools. Use this skill whenever a task involves complex visual content — UI mockups, dense screenshots, design images, charts, artwork — where precise details like spacing, hex colors, font sizes, and component hierarchy need to be extracted accurately. Also use for: reviewing or auditing existing UI against designs, comparing screenshots for visual regressions, transcribing audio/video, extracting data from PDFs with complex layouts, and generating images. Trigger whenever the user wants to implement from a design, review or compare UI screenshots, analyze visual details precisely, describe artwork or aesthetic content, or process any media file (audio, video, PDF).
prime-syncSyncs Claude config between prime repo and target projects. Trigger on 'sync', 'prime-sync', 'push config', 'pull config', 'update prime', 'sync claude config'. Push mode deploys to targets; pull mode imports changes back.
self-evolve>