agentleFS
coroboroscoroboros/agent-skills/skills/scaffold/SKILL.md

scaffold

Skill4 starsChanged 15 days agoMITView on GitHub

Create a new Next.js or Astro project on the bundled Cloudflare Workers stack with pnpm, Biome and Tailwind. Use for an empty target directory; skip existing applications and requests for a different stack.

49 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

6 rules. 0 are common, 2 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 42 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the user does not specify a scaffold or is ambiguous, show this table and ask which one.

    line 25
  2. Distinctive:

    Use Biome for linting and formatting.

    line 55
  3. Very specific:

    Use ES modules ("type": "module").

    line 56
  4. Very specific:

    Treat target=occupied as a hard stop.

    line 58
  5. Very specific:

    Read "$SKILL_DIR"/references/decisions.md only when the brief requires an application decision beyond scaffolding.

    line 60
  6. Very specific:

    When scaffolding astro-cloudflare or later editing its astro.config.mjs / wrangler.jsonc, read …

    line 64

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

Scaffold

Bootstrap the requested project with the opinionated stack.

The deterministic work — environment preflight, template overlay, package.json merge, post-scaffold verification — happens in three bundled scripts. Parse the invocation arguments, run the framework CLI, invoke the scripts in order, and turn their RESULT: lines into a concise report.

Available scaffolds

ScaffoldFrameworkInfraStack highlights
next-cloudflareNext.js 16 (App Router)Cloudflare Workers via OpenNextDrizzle + Neon, Better-Auth, shadcn/ui, Vitest + Playwright
astro-cloudflareAstro 6 (SSG-first, islands)Cloudflare WorkersZero JS by default, Content Collections, SEO rules

Shared across all scaffolds: TypeScript strict, pnpm, Biome (no ESLint/Prettier), Tailwind CSS, .node-version 22.12.0.

If the user does not specify a scaffold or is ambiguous, show this table and ask which one.

Workflow

$SKILL_DIR = this skill's folder — ${CLAUDE_SKILL_DIR} in Claude Code, the directory containing this SKILL.md elsewhere.

1. Parse arguments

Extract {scaffold} and {project_name} from the invocation arguments. Aliases: next-cf → next-cloudflare, astro-cf → astro-cloudflare. Missing {scaffold} → show the Available scaffolds table and ask. Missing {project_name} → derive from cwd or ask. {project_dir} defaults to ..

2. Preflight

bash "$SKILL_DIR"/scripts/preflight.sh "{project_dir}" "{project_name}" → check RESULT: lines. Stop on error=invalid-project-name, error=invalid-cloudflare-service-name, or error=invalid-target-name and request the named constraint; on pnpm=no, jq=no, or node=no|too-old|unsupported, provide the official install or version remediation; on target=occupied, require an empty target including dotfiles. Continue only on ok=true.

3. Install

Per-scaffold steps (framework CLI, conflict removal, dependency installs, CSS-token setup): references/setup-{scaffold}.md. Then apply the shared overlay:

bash "$SKILL_DIR"/scripts/overlay_templates.sh "{scaffold}" "{project_name}" "{project_dir}"

Writes opinionated configs (biome.json, .worktreeinclude, canonical AGENTS.md, thin CLAUDE.md, .agents/rules/, .node-version, .dev.vars.example, wrangler.jsonc, framework configs), ensures Tailwind is imported, merges the shared rules into the generator's .gitignore, and applies the validated name plus scripts and module settings to package.json. Every publication uses a same-directory temporary file and rejects destination or parent symlinks. Idempotent — skips existing files unless --force; ok=partial → show the skipped list, ask whether to rerun or keep partial.

4. Verify and summarize

bash "$SKILL_DIR"/scripts/verify_scaffold.sh "{project_dir}" runs pnpm biome check --write . and pnpm typecheck. On failure, surface the first 60 diagnostic lines + a fix; do not mark the scaffold complete. On success, report files created and next steps: configure .dev.vars, optionally hand off to /award-design <brief> (award-level direction, then /design-system audit DESIGN.md) or /frontend-dev (everyday UI) when those skills are installed, then run pnpm dev.

Rules

  • Use Biome for linting and formatting.
  • Use ES modules ("type": "module").
  • Use pnpm.
  • Treat target=occupied as a hard stop; this skill creates new projects only.
  • Preserve framework-generated README.md; leave project-specific documentation and Git initialization to the user.
  • Read "$SKILL_DIR"/references/decisions.md only when the brief requires an application decision beyond scaffolding. Record established choices; ask only for a material unresolved decision. Do not add a mandatory questionnaire after a completed scaffold.

astro-cloudflare specifics

When scaffolding astro-cloudflare or later editing its astro.config.mjs / wrangler.jsonc, read "$SKILL_DIR"/references/astro-cloudflare-notes.md — covers imageService, assets.directory, the pre-build shim, and the Sharp pitfall.

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.