agentleFS
PradnyeshpPradnyeshp/Claude-Skills/.claude/skills/scaffold/SKILL.md

scaffold

Skill2 starsChanged 4 months agoMITView on GitHub

Generate boilerplate for a new file, component, module, endpoint, or test by following the project's existing conventions. Use when the user says "scaffold a", "create a new component/module/endpoint", "generate boilerplate for", "set up a new", or "stub out".

50 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ascii-diagram, docs-ci 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.
  • SethGammonSkill

    ascii-diagram

    Generate perfectly aligned ASCII diagrams — architecture, flow, sequence, box-and-arrow. Uses a programmatic character-grid approach so alignment is guaranteed by math, not token prediction. Includes post-render verification.

    Also in 4 projects that use this

  • jh941213Skill

    docs-ci

    문서 CI(링크·OpenAPI lint·breaking 게이트·mermaid 검증)나 문서 드리프트 감지(docs.yaml 신선도 검사)를 설치하거나 돌릴 때 사용. 문서 내용 작성은 docs-architecture·docs-interfaces·docs-manuals.

    Also in 3 projects that use this

  • jh941213Skill

    docs-interfaces

    API·이벤트 인터페이스 문서(OpenAPI·swagger·AsyncAPI 명세, 엔드포인트 레퍼런스, API 구성도·시퀀스, API CHANGELOG)를 만들거나 코드와 맞출 때 사용. 시스템 구성도는 docs-architecture, API 설계 원칙은 api-design-principles.

    Also in 3 projects that use this

  • SethGammonSkill

    research-fleet

    Parallel research using Fleet wave mechanics. Spawns multiple scout agents, each investigating a different angle of the same question. Findings are compressed between waves. Produces a unified research brief from multiple independent perspectives.

    Also in 3 projects that use this

  • RachaelQuiselSkill

    client-docs

    Client documentation. Use when a build needs documentation updates or missing project documents need to be identified.

    Also in 3 projects that use this

  • vicoa-aiSkill

    live-preview

    Start a local app in the current user project, expose it through a tunnel, and return preview details in structured Markdown. Use when the user asks for a preview URL, public URL, shareable localhost, mobile/web preview, or tunnel setup.

    Also in 4 projects that use this

  • +4 more from jh941213

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 43 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Wire it up: only where the project's pattern makes it obvious and low-risk (e.g.

    line 24
  2. Distinctive:

    Create the companion test file: if the project conventionally pairs tests with this file type.

    line 25
  3. Distinctive:

    Follow existing conventions over any external "best practice." When two patterns exist, match the most recent / most common one and note …

    line 29
  4. Distinctive:

    Keep generated logic minimal — skeletons with TODOs, not guessed implementations.

    line 30
  5. Distinctive:

    Don't add new dependencies or config unless the user asked.

    line 31

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

Project layout & config

!ls 2>/dev/null

!ls package.json pyproject.toml Cargo.toml go.mod tsconfig.json 2>/dev/null

Instructions

Scaffold what the user described in $ARGUMENTS. If it's unclear what to create or where, ask for the type and intended location before generating files.

Method

  1. Find a sibling to copy from. Locate an existing file of the same kind (another component, route, model, test) with Glob/Grep and read it. The existing code — not generic templates — defines the conventions: directory, file naming, imports, export style, typing, framework idioms.
  2. Mirror those conventions exactly. Match indentation, quote style, naming case, and structure. Place new files where siblings live.
  3. Generate the minimum useful skeleton — correct imports, the declaration, a sensible default structure, and clearly marked TODO placeholders where the user must fill in logic. Don't invent business logic.
  4. Wire it up only where the project's pattern makes it obvious and low-risk (e.g. add an export to an index barrel, register a route) — and say what you wired.
  5. Create the companion test file if the project conventionally pairs tests with this file type.

Rules

  1. Follow existing conventions over any external "best practice." When two patterns exist, match the most recent / most common one and note the choice.
  2. Keep generated logic minimal — skeletons with TODOs, not guessed implementations.
  3. Don't add new dependencies or config unless the user asked.
  4. List every file you created and any wiring you did. Mention the next step the user needs to take.

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.