inc – Coleção de Agentes e Skills para Claude Code
mihai-chiorean/inc
55 agentes + skills para automação de tarefas de dev, produto, seg e conteúdo
Ver no GitHubRepositório com 55 agentes especializados e múltiplas skills para acelerar desenvolvimento em Claude Code. Inclui agentes org-scope (hiring-manager, blog-writer, product-manager, tech-lead, security-auditor) e project-scope, além de binários CLI para gerenciamento. Instalação via `install.sh` com suporte a symlink e curação via comando `/staff`.
Instalação
npx convez-ai mihai-chiorean/inc1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Prototipagem rápida de aplicações e features
- Auditoria de segurança e revisão técnica automatizada
- Gestão de contratação, product management e liderança técnica
- Escrita de conteúdo, blogs e amplificação em redes sociais
- Pesquisa de tendências e análise de feedback de usuários
Veredito

Projeto maduro e bem estruturado para times que usam Claude Code intensivamente. Excelente para automação de workflows dev, product e sec; o sistema de curação `/staff` é inteligente. Requer familiaridade com Claude Code e CLI para aproveitar plenamente.
README
A tradução para o português deste README ainda está na fila.
Contains Studio AI Agents
A comprehensive collection of specialized AI agents designed to accelerate and enhance every aspect of rapid development. Each agent is an expert in their domain, ready to be invoked when their expertise is needed.
📥 Installation
This repo is the canonical home for agents and skills. Use install.sh to wire them into Claude Code.
Recommended (default)
git clone <this-repo>
cd inc
./install.sh --link
# Set this in ~/.zshrc so `staff` knows where HR lives:
echo 'export STAFF_HR_REPO=$HOME/workspace/inc' >> ~/.zshrc
The default install puts at user scope:
- All skills (
~/.claude/skills/) — procedural overlays load in every session. - Skill binaries (
~/.local/bin/) —staff,sitrep-linear,design-doc-scaffold,plan-eng-review-audit. - Org-scope agents (
~/.claude/agents/) — currently 7:hiring-manager,blog-writer,social-amplifier,product-manager,tpm,tech-lead,security-auditor. These genuinely fire across every project. An agent is "org-scope" iff its frontmatter containsscope: org.
The other ~48 project-shaped agents stay in this repo. In each project, use /staff (or staff suggest && staff apply) to stage a curated subset into <project>/.claude/agents/. Use /staff promote <id> to lift a project-scope agent into the org set (flips scope: org, regens the manifest, re-runs install). /staff rif <id> un-staffs an agent at the project, global, or both scopes — see skills/staff/SKILL.md for the mode flags.
Alternative modes
./install.sh --link --skills-only # zero agents at user scope; fully /staff-driven
./install.sh --link --include-all-agents # all 55 agents at user scope (defeats /staff curation; not recommended)
Flags
| Flag | Purpose |
|---|---|
--link | Symlink instead of copy (keeps the repo as source of truth; updates via git pull) |
--dry-run | Print what would happen, no writes |
--include-all-agents | Install all 55 agents at user scope (not recommended; loads every agent in every session) |
--skills-only | Install zero agents (skills + bins only) |
--cleanup / --auto-cleanup / --no-cleanup | Control the pre-install cleanup gate. See docs/getting-started/bootstrap.md |
Idempotency
./install.sh is safe to re-run. Existing symlinks pointing into this repo are left alone; targets that point elsewhere are reported and skipped (no clobbering). The cleanup gate (scripts/cleanup-prior-install.sh) catches most "stale leftover from a prior install" cases automatically.
After updates: git pull && ./install.sh --link. Then in each project, staff sync refreshes staffed agents against the new HR HEAD.
Restart Claude Code
After install, restart Claude Code to pick up new agents and skills.
🚀 Quick Start
Agents are automatically available in Claude Code. Simply describe your task and the appropriate agent will be triggered. You can also explicitly request an agent by mentioning their name.
📚 Learn more: Claude Code Sub-Agents Documentation
Example Usage
- "Create a new app for tracking meditation habits" →
rapid-prototyper - "What's trending on TikTok that we could build?" →
trend-researcher - "Our app reviews are dropping, what's wrong?" →
feedback-synthesizer - "Make this loading screen more fun" →
whimsy-injector
📁 Directory Structure
Agents are organized by department for easy discovery:
contains-studio-agents/
├── design/
│ ├── brand-guardian.md
│ ├── ui-designer.md
│ ├── ux-researcher.md
│ ├── visual-storyteller.md
│ └── whimsy-injector.md
├── engineering/
│ ├── ai-engineer.md
│ ├── backend-architect.md
│ ├── devops-automator.md
│ ├── frontend-developer.md
│ ├── mobile-app-builder.md
│ ├── rapid-prototyper.md
│ └── test-writer-fixer.md
├── marketing/
│ ├── app-store-optimizer.md
│ ├── content-creator.md
│ ├── growth-hacker.md
│ ├── instagram-curator.md
│ ├── reddit-community-builder.md
│ ├── tiktok-strategist.md
│ └── twitter-engager.md
├── product/
│ ├── feedback-synthesizer.md
│ ├── sprint-prioritizer.md
│ └── trend-researcher.md
├── project-management/
│ ├── experiment-tracker.md
│ ├── project-shipper.md
│ └── studio-producer.md
├── studio-operations/
│ ├── analytics-reporter.md
│ ├── finance-tracker.md
│ ├── infrastructure-maintainer.md
│ ├── legal-compliance-checker.md
│ └── support-responder.md
├── testing/
│ ├── api-tester.md
│ ├── performance-benchmarker.md
│ ├── test-results-analyzer.md
│ ├── tool-evaluator.md
│ └── workflow-optimizer.md
└── bonus/
├── joker.md
└── studio-coach.md
📋 Complete Agent List
Engineering Department (engineering/)
- ai-engineer - Integrate AI/ML features that actually ship
- backend-architect - Design scalable APIs and server systems
- devops-automator - Deploy continuously without breaking things
- frontend-developer - Build blazing-fast user interfaces
- mobile-app-builder - Create native iOS/Android experiences
- rapid-prototyper - Build MVPs in days, not weeks
- test-writer-fixer - Write tests that catch real bugs
Product Department (product/)
- feedback-synthesizer - Transform complaints into features
- sprint-prioritizer - Ship maximum value in 6 days
- trend-researcher - Identify viral opportunities
Marketing Department (marketing/)
- app-store-optimizer - Dominate app store search results
- content-creator - Generate content across all platforms
- growth-hacker - Find and exploit viral growth loops
- instagram-curator - Master the visual content game
- reddit-community-builder - Win Reddit without being banned
- tiktok-strategist - Create shareable marketing moments
- twitter-engager - Ride trends to viral engagement
Design Department (design/)
- brand-guardian - Keep visual identity consistent everywhere
- ui-designer - Design interfaces developers can actually build
- ux-researcher - Turn user insights into product improvements
- visual-storyteller - Create visuals that convert and share
- whimsy-injector - Add delight to every interaction
Project Management (project-management/)
- experiment-tracker - Data-driven feature validation
- project-shipper - Launch products that don't crash
- studio-producer - Keep teams shipping, not meeting
Studio Operations (studio-operations/)
- analytics-reporter - Turn data into actionable insights
- finance-tracker - Keep the studio profitable
- infrastructure-maintainer - Scale without breaking the bank
- legal-compliance-checker - Stay legal while moving fast
- support-responder - Turn angry users into advocates
Testing & Benchmarking (testing/)
- api-tester - Ensure APIs work under pressure
- performance-benchmarker - Make everything faster
- test-results-analyzer - Find patterns in test failures
- tool-evaluator - Choose tools that actually help
- workflow-optimizer - Eliminate workflow bottlenecks
🎁 Bonus Agents
- studio-coach - Rally the AI troops to excellence
- joker - Lighten the mood with tech humor
🎯 Proactive Agents
Some agents trigger automatically in specific contexts:
- studio-coach - When complex multi-agent tasks begin or agents need guidance
- test-writer-fixer - After implementing features, fixing bugs, or modifying code
- whimsy-injector - After UI/UX changes
- experiment-tracker - When feature flags are added
💡 Best Practices
- Let agents work together - Many tasks benefit from multiple agents
- Be specific - Clear task descriptions help agents perform better
- Trust the expertise - Agents are designed for their specific domains
- Iterate quickly - Agents support the 6-day sprint philosophy
🔧 Technical Details
Agent Structure
Each agent includes:
- name: Unique identifier
- description: When to use the agent with examples
- color: Visual identification
- tools: Specific tools the agent can access
- System prompt: Detailed expertise and instructions
Adding New Agents
- Create a new
.mdfile in the appropriate department folder - Follow the existing format with YAML frontmatter
- Include 3-4 detailed usage examples
- Write comprehensive system prompt (500+ words)
- Test the agent with real tasks
📊 Agent Performance
Track agent effectiveness through:
- Task completion time
- User satisfaction
- Error rates
- Feature adoption
- Development velocity
🚦 Status
- ✅ Active: Fully functional and tested
- 🚧 Coming Soon: In development
- 🧪 Beta: Testing with limited functionality
🛠️ Customizing Agents for Your Studio
Agent Customization Todo List
Use this checklist when creating or modifying agents for your specific needs:
📋 Required Components
- YAML Frontmatter
-
name: Unique agent identifier (kebab-case) -
description: When to use + 3-4 detailed examples with context/commentary -
color: Visual identification (e.g., blue, green, purple, indigo) -
tools: Specific tools the agent can access (Write, Read, MultiEdit, Bash, etc.)
-
📝 System Prompt Requirements (500+ words)
- Agent Identity: Clear role definition and expertise area
- Core Responsibilities: 5-8 specific primary duties
- Domain Expertise: Technical skills and knowledge areas
- Studio Integration: How agent fits into 6-day sprint workflow
- Best Practices: Specific methodologies and approaches
- Constraints: What the agent should/shouldn't do
- Success Metrics: How to measure agent effectiveness
🎯 Required Examples by Agent Type
Engineering Agents need examples for:
- Feature implementation requests
- Bug fixing scenarios
- Code refactoring tasks
- Architecture decisions
Design Agents need examples for:
- New UI component creation
- Design system work
- User experience problems
- Visual identity tasks
Marketing Agents need examples for:
- Campaign creation requests
- Platform-specific content needs
- Growth opportunity identification
- Brand positioning tasks
Product Agents need examples for:
- Feature prioritization decisions
- User feedback analysis
- Market research requests
- Strategic planning needs
Operations Agents need examples for:
- Process optimization
- Tool evaluation
- Resource management
- Performance analysis
✅ Testing & Validation Checklist
- Trigger Testing: Agent activates correctly for intended use cases
- Tool Access: Agent can use all specified tools properly
- Output Quality: Responses are helpful and actionable
- Edge Cases: Agent handles unexpected or complex scenarios
- Integration: Works well with other agents in multi-agent workflows
- Performance: Completes tasks within reasonable timeframes
- Documentation: Examples accurately reflect real usage patterns
🔧 Agent File Structure Template
---
name: your-agent-name
description: Use this agent when [scenario]. This agent specializes in [expertise]. Examples:\n\n<example>\nContext: [situation]\nuser: "[user request]"\nassistant: "[response approach]"\n<commentary>\n[why this example matters]\n</commentary>\n</example>\n\n[3 more examples...]
color: agent-color
tools: Tool1, Tool2, Tool3
---
You are a [role] who [primary function]. Your expertise spans [domains]. You understand that in 6-day sprints, [sprint constraint], so you [approach].
Your primary responsibilities:
1. [Responsibility 1]
2. [Responsibility 2]
...
[Detailed system prompt content...]
Your goal is to [ultimate objective]. You [key behavior traits]. Remember: [key philosophy for 6-day sprints].
📂 Department-Specific Guidelines
Engineering (engineering/): Focus on implementation speed, code quality, testing
Design (design/): Emphasize user experience, visual consistency, rapid iteration
Marketing (marketing/): Target viral potential, platform expertise, growth metrics
Product (product/): Prioritize user value, data-driven decisions, market fit
Operations (studio-operations/): Optimize processes, reduce friction, scale systems
Testing (testing/): Ensure quality, find bottlenecks, validate performance
Project Management (project-management/): Coordinate teams, ship on time, manage scope
🎨 Customizations
Modify these elements for your needs:
- Adjust examples to reflect your product types
- Add specific tools agents have access to
- Modify success metrics for your KPIs
- Update department structure if needed
- Customize agent colors for your brand
🤝 Contributing
To improve existing agents or suggest new ones:
- Use the customization checklist above
- Test thoroughly with real projects
- Document performance improvements
- Share successful patterns with the community