One command turns your AI coding agent into a domain specialist.

Website · Catalog · npm · 中文

Your Claude Code, Cursor, OpenCode, or Codex gives generic answers because it doesn't know your domain. AgentBrief fixes that — install a brief and your agent gains real expertise: security auditing, code review, product specs, growth hacking, and more.

npx agentbrief use fullstack-engineer # Your agent now enforces strict TypeScript, follows Next.js conventions, # builds accessible UIs, and reviews PRs like a staff engineer — 9 skills in 1 command

WITHOUT a brief: You: "Review this code for issues" Agent: "The code looks good overall. Consider adding error handling." WITH security-auditor brief: You: "Review this code for issues" Agent: "CWE-89 CRITICAL at line 23: SQL injection via string concatenation. Attack vector: attacker injects arbitrary SQL through userId param. Fix: const query = 'SELECT * FROM users WHERE id = $1'; await db.query(query, [userId]);" 

npm install -g agentbrief # or pnpm add -g agentbrief

Not sure where to begin? Pick a combo — each one bundles multiple specialist briefs into a single command:

 fullstack-engineer → release-engineer → startup-founder Build Ship Grow 

agentbrief use fullstack-engineer # Build: write production code agentbrief use release-engineer # Ship: test, secure, deploy, document agentbrief use startup-founder # Grow: product, growth, launch strategy

Code Quality & Engineering:

Product, Growth & Business:

Browse the full Catalog or the Website for details on each brief.

# Apply from the official registry agentbrief use security-auditor # Apply from GitHub agentbrief use github:owner/repo agentbrief use github:owner/repo@v1.0 # Apply from local path agentbrief use ./path/to/brief # Browse, inspect, manage agentbrief search # List all briefs agentbrief list # See what's applied agentbrief show <name> # View injected content agentbrief preview <name> # Preview without applying agentbrief update # Fetch latest versions agentbrief eject <name> # Clean removal

AgentBrief compiles a brief (role + knowledge + skills) into the instruction files your AI agent reads, with content optimized per engine:

Your existing files are preserved — briefs are injected between <!-- agentbrief:name:start/end --> markers. Eject removes only the brief content.

<!-- agentbrief:fullstack-engineer:start --> # AgentBrief: fullstack-engineer ## Role You are a senior full-stack TypeScript developer. You build production applications with Next.js 15, React 19, and Tailwind CSS. You enforce strict type safety and review your own code with principal-engineer rigor. ## Constraints - Never use `any` — always annotate return types on exports - Server Components by default — only add 'use client' when needed - WCAG 2.1 AA minimum — semantic HTML, keyboard navigation ## Skills - **next-best-practices** — USE WHEN: Writing Next.js code - **typescript-advanced-types** — USE WHEN: Complex type logic - **architecture-review** — USE WHEN: Reviewing PRs - **design-review-checklist** — USE WHEN: Checking UI quality - **agent-browser** — USE WHEN: Visual verification needed ...and 4 more <!-- agentbrief:fullstack-engineer:end -->

my-brief/ ├── brief.yaml # Config: name, version, extends, skills ├── personality.md # Identity: role, tone, constraints ├── knowledge/ # Reference: domain materials (read on demand) │ └── cheatsheet.md └── skills/ # Workflows: executable skill directories └── my-skill/ ├── SKILL.md # Trigger condition + step-by-step process └── ... # Any supporting files 

See briefs/security-auditor/ for a complete example.

Every official brief is curated from battle-tested, community-endorsed skills:

• obra/superpowers (90.6k ★) — TDD, systematic debugging, verification
• anthropics/skills (95.8k ★) — Anthropic's official skill packages
• garrytan/gstack (YC CEO) — CEO review, design review, QA
• vercel-labs (Vercel official) — Next.js best practices, browser automation
• coreyhaines31/marketingskills — SEO audit, launch strategy, analytics

agentbrief init my-agent # Scaffold # Edit personality.md, add knowledge/ and skills/ agentbrief use ./my-agent # Test locally agentbrief preview ./my-agent # See compiled output # Push to GitHub → agentbrief use github:you/my-agent

Want it in the official registry? Submit a PR. Read the Authoring Guide.

• GitHub Discussions — Questions, showcase, feature ideas
• Contributing Guide — Submit briefs to the registry

Add .agentbrief/ to your .gitignore. Commit the engine files (CLAUDE.md, .cursorrules, AGENTS.md) so your team shares the same agent behavior.

MIT