agentleFS
RidhuanDEVRidhuanDEV/claude-skills/shadow-bootstrap/SKILL.md

shadow-bootstrap

Skill1 starsChanged yesterdayMITView on GitHub

Greenfield Project Scaffolder. Use when initializing or scaffolding a new project repository from zero (TypeScript/lint, env validation, DB/ORM, Docker dev, CI, seed). Do NOT use on existing brownfield codebases.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Very specific:

    Use this skill after architectural decisions (/shadow-architect) are confirmed to initialize a clean, reproducible project foundation from …

    line 8
  2. Very specific:

    When scaffolding a new repository (Monorepo or Single-Service), /shadow-bootstrap MUST set up and verify all 8 pillars:

    line 14
  3. Very specific:

    Create src/config/env.ts (or config.py / config.go) that validates all required environment variables at process boot using a schema …

    line 30
  4. Very specific:

    Create a complete, well-commented .env.example (never commit real secrets in .env).

    line 31
  5. Very specific:

    Create the initial migration and an idempotent seed script (npm run db:seed) so a fresh developer machine gets working reference data …

    line 40
  6. Very specific:

    Write a crisp README.md covering Prerequisites, 5-step Quick Start (cp .env.example .env, docker compose up -d, npm install, npm run …

    line 49

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

Shadow Bootstrap (/shadow-bootstrap) — Project Foundation & Zero-to-Runnable Scaffold

Use this skill after architectural decisions (/shadow-architect) are confirmed to initialize a clean, reproducible project foundation from scratch. Never pick a tech stack arbitrarily — follow the approved ADR or the Monarch's stack instruction.


1. The 8 Mandatory Bootstrap Pillars

When scaffolding a new repository (Monorepo or Single-Service), /shadow-bootstrap MUST set up and verify all 8 pillars:

1. Repository & Directory Structure

  • Clean separation of concerns:
    • Backend: src/config/, src/modules/<domain>/{controller,service,repository,dto,entities}, src/common/{middleware,errors,guards,logger}, tests/.
    • Frontend: src/app/ (or pages/), src/components/ui/, src/features/<domain>/, src/lib/, src/types/.
    • Documentation & Specs: docs/{adr,api,db,uat,handover}/, openapi.yaml, postman_collection.json.
  • Standard .gitignore, .gitattributes (enforcing LF line endings for scripts), and .editorconfig.

2. Strict Compiler, Linter & Formatter Configuration

  • TypeScript: tsconfig.json with "strict": true, "noImplicitAny": true, "noUncheckedIndexedAccess": true, "exactOptionalPropertyTypes": true, and clean path aliases (@/*).
  • Python: pyproject.toml with ruff + mypy --strict / pyright.
  • Go: .golangci.yml with govet, errcheck, staticcheck.
  • PHP/Laravel: pint.json + phpstan.neon (Larastan level 6+).

3. Fail-Fast Startup Environment Validation

  • Create src/config/env.ts (or config.py / config.go) that validates all required environment variables at process boot using a schema validator (zod, pydantic-settings, etc.) and fails fast with a clear human-readable error if any variable is missing or malformed.
  • Create a complete, well-commented .env.example (never commit real secrets in .env).

4. Standard Error Envelope, Structured Logger & Health Probes

  • Global error handler returning a deterministic JSON error envelope (statusCode, errorCode, message, details, requestId).
  • Correlation X-Request-Id middleware + structured JSON logger (pino / structlog / zap).
  • Built-in /healthz (liveness: process up) and /readyz (readiness: DB + Redis ping) endpoints.

5. Database, ORM, Migration & Deterministic Seed Setup

  • Configure the chosen ORM/query builder (Prisma, Drizzle, TypeORM, SQLAlchemy/Alembic, GORM/sqlc, Eloquent).
  • Create the initial migration and an idempotent seed script (npm run db:seed) so a fresh developer machine gets working reference data immediately.

6. Local Development docker-compose.dev.yml

  • Provide a one-command local infrastructure file (docker compose -f docker-compose.dev.yml up -d) spinning up local PostgreSQL/MySQL, Redis, Mailpit (local SMTP testing UI), and MinIO (if object storage is needed) with healthchecks and named volumes.

7. Testing Framework & Initial Smoke Spec

  • Wire up the test runner (Vitest/Jest, Pytest, Go test, Pest) with a passing initial test (GET /healthz -> 200 OK) so npm test / pytest works out of the box from commit #1.

8. Developer README.md & Fresh-Clone Verification

  • Write a crisp README.md covering Prerequisites, 5-step Quick Start (cp .env.example .env, docker compose up -d, npm install, npm run db:migrate && npm run db:seed, npm run dev), and available scripts.
  • Verification Gate: Execute install, typecheck, lint, build, and the healthcheck test before declaring bootstrap complete.

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.