How this skill is triggered — by the user, by Claude, or both
Slash command
/enterprise-os:codebase-first-devThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Adds a mandatory codebase exploration phase before implementation, ensuring new code matches existing patterns perfectly.
Adds a mandatory codebase exploration phase before implementation, ensuring new code matches existing patterns perfectly.
"Don't invent patterns. Discover them."
Before writing any new code, explore the existing codebase to find:
Step 1: Find Similar Features
Search for existing implementations of similar concepts:
- Glob for similar file names in the same directory
- Grep for similar function names, types, or patterns
- Read 2-3 example files to understand the pattern
Step 2: Map the Pattern Document what you found:
## Pattern Analysis
**Similar existing feature**: {name}
**Files examined**: {list}
### Pattern found:
- File structure: {how files are organized}
- Component pattern: {how components are structured}
- Data flow: {how data moves through the feature}
- Error handling: {how errors are managed}
- State management: {how state is handled}
### Reusable code found:
- {utility/component}: {path} — {what it does}
- {type/interface}: {path} — {can be reused for our feature}
Step 3: Plan with Patterns Based on exploration, plan the implementation:
## Implementation Plan (Pattern-Aligned)
### Files to create (matching existing structure):
- {path} — follows pattern from {example file}
### Files to modify:
- {path} — add {what}, following pattern from {example}
### Shared code to reuse:
- {import from existing utility/component}
### New patterns needed (if any):
- {only if no existing pattern fits — explain why}
This skill is standalone and optional — invoke it directly when you want to explore existing patterns before coding. It is not automatically invoked by feature-developer or any pipeline. You can optionally use its output to inform your implementation:
Task: "Add user earnings page"
Exploration finds:
src/app/dashboard/page.tsxDashboardLayout wrapperlib/Implementation follows:
src/app/earnings/page.tsx (same structure as dashboard)DashboardLayoutlib/queries.ts (existing file)After exploration, produce:
## Codebase Exploration Summary
**Similar features examined**: {count}
**Patterns discovered**: {count}
**Reusable code found**: {count}
**New patterns needed**: {count}
Proceeding with implementation following {primary pattern} from {example file}.
npx claudepluginhub tyjpark0317/enterprise-os --plugin enterprise-osUse when building ANY feature within an existing project - search the current codebase for existing patterns, conventions, similar implementations, and established approaches before writing new code
Investigates codebase to verify design assumptions, find patterns, locate features, confirm file locations/structure, and ground planning in reality before implementation.
Explores project structure, configurations, code patterns, conventions, tests, and dependencies before modifying existing code to understand context and avoid bugs.