agentleFS
AurealibeAurealibe/claude-config/.claude/skills/oneshot/SKILL.md

oneshot

Skill68 starsChanged 4 months agoMITView on GitHub

Quick implementation without a full spec file

12 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use brainstorm.

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.
  • nicolasestremSkill

    brainstorm

    Structured idea generation and solution exploration with systematic analysis.

    Also in 3 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

19 rules. 0 are common, 17 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 17

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After clarification: ensure you understand exactly what to build

    line 25
  2. Distinctive:

    After exploration results: reflect on completeness before planning

    line 26
  3. Distinctive:

    Before implementation: consider edge cases, patterns to follow, potential issues

    line 27
  4. Distinctive:

    After validation: ensure the approach aligns with user intent

    line 28
  5. Distinctive:

    Use AskUserQuestion to clarify before exploration:

    line 34
  6. Distinctive:

    Default values for new fields?

    line 38
  7. Distinctive:

    Do not proceed until critical details are clarified.

    line 55
  8. Distinctive:

    No ceiling, real floor: Use at least 2 agents per domain in scope (1 only for a genuinely trivial single-file change).

    line 66
  9. Distinctive:

    Add one agent per distinct table cluster, or to cover prod alongside dev.

    line 95
  10. Distinctive:

    After agents return, verify coverage across all dimensions:

    line 111
  11. Very specific:

    Similar patterns identified?: Do I have a reference implementation to follow?

    line 114
  12. Very specific:

    Library docs sufficient?: If not -> launch additional parallel explore-docs agents

    line 116
  13. Distinctive:

    Do NOT proceed with incomplete context.

    line 118
  14. Distinctive:

    Write detailed implementation plan:

    line 124
  15. Distinctive:

    Ask with AskUserQuestion: "Approve this plan?"

    line 150
  16. Distinctive:

    Follow patterns from exploration

    line 163
  17. Distinctive:

    Tests are MANDATORY: all existing tests must pass (zero regressions).

    line 180
  18. Distinctive:

    VALIDATE: - always ask before implementing

    line 188
  19. Distinctive:

    STAY IN SCOPE: - only what's needed

    line 189

“Common” is measured: kept by at least 6 in 10 of the 9 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

YOU ARE EXECUTING THE /oneshot 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 clarification: ensure you understand exactly what to build
  • 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. CLARIFY REQUIREMENTS

Use AskUserQuestion to clarify before exploration:

Must clarify (if not specified)

  • Error messages for user-facing failures?
  • Default values for new fields?
  • Validation rules?
  • What triggers state changes?

UX Decisions (if not specified)

  • What happens on success? (toast, redirect, refresh?)
  • What happens on error?
  • Confirmation dialogs needed?

Permissions (if not specified)

  • Who can perform each action?
  • RLS policy rules (if the DB uses RLS)?

Scope (if not specified)

  • Backend only, frontend only, or both?
  • Database changes needed?

Do not proceed until critical details are clarified.


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)

  1. 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/"
  2. Usecases & business logic - explore-codebase: "Find usecases related to [feature] in backend/internal/application/usecases/. Read their Execute methods, dependencies, and error handling"
  3. Handlers & routing - explore-codebase: "Find HTTP handlers and routes related to [feature] in backend/internal/presentation/. Check middleware, validation, response patterns"
  4. Infrastructure & services - explore-codebase: "Find repo implementations, external service adapters, and config related to [feature] in backend/internal/infrastructure/"
  5. 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)

  1. Components & UI - explore-codebase: "Find components related to [feature] in frontend/src/components/. Check props, state, Shadcn UI usage"
  2. Hooks & state - explore-codebase: "Find hooks, React Query calls, and state management related to [feature] in frontend/src/hooks/ and frontend/src/lib/"
  3. Pages & routing - explore-codebase: "Find pages and layouts related to [feature] in frontend/src/app/. Check route structure, data fetching, i18n"
  4. Types & API layer - explore-codebase: "Find TypeScript types, API client functions related to [feature] in frontend/src/types/ and frontend/src/lib/"
  5. 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. First token of each prompt selects the env (dev/prod, defaults to dev).

  1. Schema & relationships - explore-db: "dev - Map tables and foreign keys related to [feature]: columns, types, FK relationships"
  2. Constraints & policies - explore-db: "dev - Inspect constraints and RLS policies (if used) on tables related to [feature]"

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)

  1. [library A] - explore-docs: "[library A] [specific feature] documentation"
  2. [library B] - explore-docs: "[library B] [specific feature] documentation"

Web-research Agents (≥1 when external research needed, one per topic, no maximum)

  1. [topic A] - websearch: "[topic A] best practices 2025 2026"
  2. [topic B] - websearch: "[topic B] ..."

2.5 POST-EXPLORATION CHECK

After agents return, verify coverage across all dimensions:

  1. Full code path traced? Can I trace handler -> usecase -> repository -> DB (backend) and page -> hook -> API -> component (frontend)? If gaps -> launch targeted explore-codebase
  2. Similar patterns identified? Do I have a reference implementation to follow? If not -> launch explore-codebase
  3. Data model complete? Tables, columns, relationships, policies known? If not -> launch additional parallel explore-db agents
  4. Library docs sufficient? If not -> launch additional parallel explore-docs agents

Do NOT proceed with incomplete context.


3. PLAN

Write detailed implementation plan:

## Implementation Plan

### Database changes (if applicable)
- Migration: [description]

### Backend changes
- Files to create/modify with line numbers

### Frontend changes
- Files to create/modify with line numbers

### Patterns to follow (from exploration)
- [code snippets to replicate]

### Order
1. [step 1]
2. [step 2]

4. VALIDATE

Ask with AskUserQuestion: "Approve this plan?"

  • "Implement"
  • "Modify"

5. IMPLEMENT

After validation, implement:

  • Backend first (Domain -> Application -> Infrastructure -> Presentation)
  • Frontend second (Types -> API -> Hooks -> Components -> Pages)

Rules:

  • Follow patterns from exploration
  • No hardcoded values
  • Complete error handling
  • useTranslations from next-intl for ALL user-facing text; Shadcn UI for standard components; strict TypeScript (no any)
  • Write unit tests for new usecases/services (backend *_test.go) and for new components with branching logic, new hooks, and new utility/parser functions (frontend *.test.ts / *.test.tsx). Follow existing test patterns; cover happy path + main error cases

For significant UI: Skill(skill="frontend-design:frontend-design")


6. VERIFY

cd backend && go build ./... && go vet ./... && golangci-lint run ./... && go test ./...
cd frontend && npm run test:run && npm run build

Tests are MANDATORY: all existing tests must pass (zero regressions). Fix any failure before proceeding.


Rules

  • CLARIFY FIRST - understand requirements before exploring
  • EXPLORE SECOND - parallel exploration before planning
  • VALIDATE - always ask before implementing
  • STAY IN SCOPE - only what's needed

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.