dev
Skill68 starsChanged 4 months agoMITView on GitHub
Develop phase with exploration and plan validation
56 other projects use a version of this.
Adopted by
Most recently taken up by
- TsukiNi22/skillstheir own version, first seen Nov 16, 2026
- TsukiNi22/ai-utilstheir own version, first seen Nov 16, 2026
- waynesutton/convexskillstheir own version, first seen Nov 15, 2026
- waynesutton/builder-skillstheir own version, first seen Nov 15, 2026
- ztcools/skillstheir own version, first seen Nov 15, 2026
- mayoz/rabbittheir own version, first seen Nov 15, 2026
Used with
Projects with it also use metrics-graphana, control-flow and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
slopusSkillmetrics-graphana
Query and manage Grafana dashboards and Prometheus metrics for Happy infrastructure. Covers grafanactl CLI usage, direct Prometheus queries through Grafana proxy, and dashboard-as-code workflows. Use when user asks about metrics, dashboards, monitoring, Grafana, Prometheus, or wants to add/modify panels.
Also in 3 projects that use this
slopusSkillcontrol-flow
Analyze and design control flows and data structures. Produces compact ASCII tree diagrams showing triggers, call chains, payload shapes, state mutations, and re-render effects. Use when user asks to diagram, trace, visualize, or design a flow or data structure.
Also in 3 projects that use this
waynesuttonSkillsec-check
Security review checklist for Convex functions, auth logic, public queries, admin routes, webhooks, uploads, and AI-generated code. Use when reviewing code that touches user data, PII, or access control.
Also in 3 projects that use this
waynesuttonSkillupdate-project-docs
Also in 3 projects that use this
silverkyoon-RachelSkillstyle
Tailwind CSS 스타일을 검토하고 개선합니다.
Also in 3 projects that use this
jasonmichaelbell78-creatorSkillaudit-security
Run a single-session security audit on the codebase
Also in 3 projects that use this
Other versions56 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 56
- slopus/happy★ 25ksame name
- microsoft/playwright-cli★ 15ksame name
- atopile/atopile★ 4ksame name
- cexll/myclaude★ 2.8ksame name
- waynesutton/markdown-site★ 628same name
- Automattic/wordpress-activitypub★ 583same name
- waynesutton/builder-skills★ 404same name
- waynesutton/convexskills★ 404same name
- justrach/merjs★ 357same name
- stella/stella★ 280same name
46 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
Show its rules and text
We split this skill into the rules it gives an agent
20 rules. 0 are common, 15 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 38 edited versions we read keep these.
15
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 25
After exploration results: reflect on completeness before planning
- Distinctive: line 26
Before implementation: consider edge cases, patterns to follow, potential issues
- Distinctive: line 27
After validation: ensure the approach aligns with user intent
- Distinctive: line 50
No ceiling, real floor: Use at least 2 agents per domain in scope (1 only for a genuinely trivial single-file change).
- Distinctive: line 80
Add one agent per distinct table cluster, or to cover prod alongside dev.
- Distinctive: line 100
After agents return, verify coverage across all dimensions:
- Very specific: line 103
Similar patterns identified?: Do I have a reference implementation to follow?
- Very specific: line 105
Library docs sufficient?: If not -> launch additional parallel explore-docs agents (one per missing library / feature)
- Distinctive: line 107
Do NOT proceed with incomplete context.
- Very specific: line 136
If $ARGUMENTS.auto is true:
- Distinctive: line 140
Ask with AskUserQuestion: "Proceed with implementation?"
- Distinctive: line 148
After validation, implement in appropriate order:
- Distinctive: line 152
Follow Clean Architecture patterns
- Very specific: line 155
Follow existing test patterns (testify, hand-written mocks, *Env struct helper)
- Very specific: line 163
Follow existing test patterns (vitest + @testing-library/react, vi.mock for module-level deps, jest-dom matchers via the shared test setup)
- Distinctive: line 179
Backend and frontend tests are MANDATORY: All existing tests must pass (zero regressions).
- Distinctive: line 187
Check off completed items in the Execution Plan of the spec file.
- Distinctive: line 193
EXPLORE FIRST: - Always explore before implementing
- Distinctive: line 195
VALIDATE: - Always ask before implementing
- Distinctive: line 196
STAY IN SCOPE: - Only the specified phase
“Common” is measured: kept by at least 6 in 10 of the 38 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
YOU ARE EXECUTING THE /dev SKILL. The user triggered this skill. Follow ALL instructions below step by step. Do NOT treat this as a freeform conversation - execute the skill workflow.
Follow CLAUDE.md rules.
Ultra Think Strategy
Ultra think before each phase transition:
- After exploration results: reflect on completeness before planning
- Before implementation: consider edge cases, patterns to follow, potential issues
- After validation: ensure the approach aligns with user intent
1. UNDERSTAND
- Read spec:
$ARGUMENTS.spec - Identify phase:
$ARGUMENTS.phase - Phases completed:
$ARGUMENTS.done - Extract from phase description:
- Scope: backend / frontend / both
- Files to create/modify
- Libraries needed
2. EXPLORE (PARALLEL)
Launch focused agents in a single message (parallel execution). There is no upper limit on agent count. Spawn one agent per distinct concern, area, or file-cluster the task actually has, and scale up freely with its breadth. The lists below are a starting menu, not a quota: add as many agents as full coverage requires.
Agent-count principle
- You decide the count from the actual scope. Assess how many distinct concerns / areas / file-clusters the task really spans on this codebase, and launch one focused agent for each. Do not anchor to a fixed number or to file counts.
- No ceiling, real floor. Use at least 2 agents per domain in scope (1 only for a genuinely trivial single-file change). Above that floor there is no maximum; on a large codebase the realistic count usually sits well above it.
- One distinct focus per agent. Split by concern so two agents never run the same search. Add agents to widen coverage, never to duplicate it.
- No batching. Launch them all in one message; the harness schedules them, so you never hold back to stay under a number.
Backend Agents (≥2 when backend in scope, one per distinct concern, no maximum)
- Domain & data flow -
explore-codebase: "Find entities, repository interfaces, value objects, and DTOs related to [feature] in backend/internal/domain/ and backend/internal/application/dto/" - Usecases & business logic -
explore-codebase: "Find usecases related to [feature] in backend/internal/application/usecases/. Read their Execute methods, dependencies, and error handling" - Handlers & routing -
explore-codebase: "Find HTTP handlers and routes related to [feature] in backend/internal/presentation/. Check middleware, validation, response patterns" - Infrastructure & services -
explore-codebase: "Find repo implementations, external service adapters, and config related to [feature] in backend/internal/infrastructure/" - Similar patterns -
explore-codebase: "Find the most similar existing feature to [feature] in backend/. I need to replicate its patterns"
Frontend Agents (≥2 when frontend in scope, one per distinct concern, no maximum)
- Components & UI -
explore-codebase: "Find components related to [feature] in frontend/src/components/. Check props, state, Shadcn UI usage" - Hooks & state -
explore-codebase: "Find hooks, React Query calls, and state management related to [feature] in frontend/src/hooks/ and frontend/src/lib/" - Pages & routing -
explore-codebase: "Find pages and layouts related to [feature] in frontend/src/app/. Check route structure, data fetching, i18n" - Types & API layer -
explore-codebase: "Find TypeScript types, API client functions related to [feature] in frontend/src/types/ and frontend/src/lib/" - Similar patterns -
explore-codebase: "Find the most similar existing feature to [feature] in frontend/src/. I need to replicate its patterns"
The supporting agents below fan out the SAME way as the code agents: one agent per distinct concern, no maximum. None of them is capped at a single instance.
Database Agents (≥1 when DB in scope, one per distinct concern, no maximum)
Launch one explore-db per distinct DB concern in the same single message. One agent is enough for a single-table lookup; scale up freely when the phase spans multiple table clusters, both dev and prod, or several concerns. First token of each prompt selects the env (dev/prod, defaults to dev).
- Schema & relationships -
explore-db: "dev - Map tables and foreign keys related to [feature]: columns, types, FK relationships" - Constraints & policies -
explore-db: "dev - Inspect constraints and RLS policies (if used) on tables related to [feature]" - Migrations & advisors -
explore-db: "dev - List migrations touching [feature] tables, run get_advisors for security/perf issues"
Add one agent per distinct table cluster, or to cover prod alongside dev.
Documentation Agents (≥1 when external docs needed, one per library/feature, no maximum)
Launch one explore-docs per distinct library or per distinct feature within a library. One agent is enough for a single lib question; scale up when the phase touches multiple libraries or several independent features of one.
- [library A] -
explore-docs: "[library A] [specific feature] documentation" - [library B] -
explore-docs: "[library B] [specific feature] documentation"
Web-research Agents (≥1 when external research needed, one per topic, no maximum)
Launch one websearch per distinct external question. One agent is enough for a single topic; scale up when there are several independent questions.
- [topic A] -
websearch: "[topic A] best practices 2025 2026" - [topic B] -
websearch: "[topic B] ..."
2.5 POST-EXPLORATION CHECK
After agents return, verify coverage across all dimensions:
- Full code path traced? Can I trace handler -> usecase -> repository -> DB (backend) and page -> hook -> API -> component (frontend)? If gaps -> launch targeted
explore-codebase - Similar patterns identified? Do I have a reference implementation to follow? If not -> launch
explore-codebase - Data model complete? Tables, columns, relationships, policies known? If not -> launch additional parallel
explore-dbagents (one per missing concern / cluster / env) - Library docs sufficient? If not -> launch additional parallel
explore-docsagents (one per missing library / feature)
Do NOT proceed with incomplete context.
3. SHOW PLAN
Display enriched plan:
## Phase $ARGUMENTS.phase
### Files to Create
- `path/file` - [purpose]
### Files to Modify
- `path/file:XX` - [what to change]
### Patterns to Reuse (from exploration)
- [existing code patterns found]
### Order
Backend: Domain -> Application -> Infrastructure -> Presentation
Frontend: Types -> API -> Hooks -> Components -> Pages4. VALIDATE
If $ARGUMENTS.auto is true:
- Skip the gate. Log "Auto-confirmed (auto=true), proceeding to implementation." and go directly to step 5.
Otherwise (default):
- Ask with AskUserQuestion: "Proceed with implementation?"
- "Implement"
- "Modify"
5. IMPLEMENT
After validation, implement in appropriate order:
Backend: Domain -> Application -> Infrastructure -> Presentation
- context.Context as first parameter for I/O
- Follow Clean Architecture patterns
- Complete error handling
- Write unit tests for all new usecases/services (colocated
*_test.go) - Follow existing test patterns (testify, hand-written mocks,
*Envstruct helper) - Tests must cover happy path + main error cases
Frontend: Types -> API -> Hooks -> Components -> Pages
useTranslationsfromnext-intlfor ALL user-facing text- Shadcn UI for standard components
- Strict TypeScript (no
any) - Write unit tests for new components with branching logic, new hooks, and new utility/parser functions (colocated
*.test.ts/*.test.tsx) - Follow existing test patterns (vitest +
@testing-library/react,vi.mockfor module-level deps, jest-dom matchers via the shared test setup) - Tests must cover happy path + main error / edge cases
For significant UI: Skill(skill="frontend-design:frontend-design")
6. VERIFY
# Backend
cd backend && go build ./... && go vet ./... && golangci-lint run ./... && go test ./...
# Frontend
cd frontend && npm run test:run && npm run buildBackend and frontend tests are MANDATORY: All existing tests must pass (zero regressions). If a test fails, fix it before proceeding.
Database verification (if schema/policies changed): run get_advisors via explore-db (dev/prod).
7. UPDATE SPEC
Check off completed items in the Execution Plan of the spec file.
Rules
- EXPLORE FIRST - Always explore before implementing
- REUSE - Existing code/patterns as much as possible
- VALIDATE - Always ask before implementing
- STAY IN SCOPE - Only the specified phase
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

