Development workflow orchestrator for Viterbit web-app. Automatically activates on development tasks and guides through the appropriate flow based on scenario.
Orchestrates Viterbit development workflows by automatically detecting scenarios and guiding appropriate implementation flows.
/plugin marketplace add viterbit/viterbit-ai-tools/plugin install viterbit-viterbit-ai-tools@viterbit/viterbit-ai-toolsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
This skill activates when detecting:
VITERBIT-CONTEXT.mdapp/src/{Context}/CLAUDE.md| If the request involves... | Scenario |
|---|---|
| New bounded context, new subdomain, new module | New Feature |
| Add command/query/endpoint to existing context | New Use Case |
| Add field, change behavior of existing entity | Modify Entity |
| Bug, error, "doesn't work", "fails when" | Bug Fix |
| Move from Document/ to DDD, legacy modernization | Legacy Migration |
| Improve, clean, extract, reorganize (no behavior change) | Refactoring |
Verification level: Strict
BRAINSTORMING (mandatory)
brainstorming skillSETUP
git checkout -b feat/descriptive-name
SCAFFOLDING
creating-bounded-contextcreating-entity, creating-use-case, creating-listener, creating-crudVERIFICATION
verify (complete)architecture-validator agenttest-writer agent for additional coverageCOMMIT & PR
code-reviewer agentfeat: descriptionVerification level: Pragmatic
ANALYSIS
CLAUDE.mdBRAINSTORMING (if complex)
SETUP
git checkout -b feat/use-case-name
SCAFFOLDING
creating-use-casecreating-controller if exposing HTTPcreating-listener if publishing eventsVERIFICATION
verify-light runs automaticallyverify before commitCOMMIT
feat: descriptionVerification level: Pragmatic
ANALYSIS
SETUP
git checkout -b feat/add-field-to-entity
# or refactor/ if no new functionality
IMPLEMENTATION
creating-vo as reference)VERIFICATION
verify-light runs automaticallyverify before commitCOMMIT
feat: or refactor:Verification level: Pragmatic
CONTEXT
SETUP
git checkout -b fix/short-description
INVESTIGATION
systematic-debugging skillIMPLEMENTATION
VERIFICATION
verify-light runs automaticallyverify before commitCOMMIT
fix: descriptionfix: description - refs LINEAR-XXXVerification level: Strict
ANALYSIS (mandatory)
legacy-migrator agentBRAINSTORMING
SETUP
git checkout -b refactor/migrate-entity-to-context
IMPLEMENTATION (incremental)
creating-entity)VERIFICATION
verify (complete)architecture-validator agentdoctrine-specialist if complex mappingsCOMMIT
refactor: migrate X to Context/SubdomainVerification level: Pragmatic
ANALYSIS
SETUP
git checkout -b refactor/description
IMPLEMENTATION
VERIFICATION
verify-light runs automaticallyverify before commitCOMMIT
refactor: description| Agent | Use When | Don't Use When |
|---|---|---|
test-writer | Need additional test coverage after implementing | Simple tests that creating-test handles |
architecture-validator | New features, legacy migrations, DDD compliance doubts | Small changes, bug fixes |
doctrine-specialist | Complex mappings, custom types, index optimization | Simple mappings that creating-mapping handles |
legacy-migrator | Any migration from Document/ to DDD structure | Code already in DDD |
code-reviewer | Before PR on significant features | Every small commit |
| Scenario | test-writer | arch-validator | doctrine-spec | legacy-migrator | code-reviewer |
|---|---|---|---|---|---|
| New feature | ✓ | ✓ | If needed | - | ✓ |
| New use case | Optional | - | - | - | Optional |
| Modify entity | Optional | - | If needed | - | - |
| Bug fix | - | - | - | - | - |
| Legacy migration | ✓ | ✓ | ✓ | ✓ Required | ✓ |
| Refactoring | - | Optional | - | - | Optional |
verify-light on every edit (automatic)verify complete before commitarchitecture-validator agent reviewverify-light on every edit (automatic)verify complete before commit| Prefix | When | Example |
|---|---|---|
feat/ | New functionality | feat/notification-system |
fix/ | Bug fixes | fix/webhook-timeout-refs-LINEAR-123 |
refactor/ | Code improvement, no behavior change | refactor/extract-email-service |
feat: add notification preferences endpoint
fix: resolve webhook timeout on large payloads - refs LINEAR-456
refactor: extract email sending to dedicated service
Always use conventional commits. Include Linear reference on bug fixes when available.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.