karpathy-initlisted

Scaffold the Karpathy 3-layer development contracts into a repository — SPEC (specs/), VERIFIER.md, ENVIRONMENT.md — and wire them into AGENTS.md so every agent (Claude, GPT/Copilot, Codex) follows them. Use when a repo has no specs/VERIFIER.md/ENVIRONMENT.md yet, or when the user runs /karpathy-init. Generic across stacks (.NET, Node, Python, Go, Rust, other).
Mace-Enterprise/Agent-Knowledge-Memory-Wiki · ★ 0 · AI & Automation · score 60

Install: claude install-skill Mace-Enterprise/Agent-Knowledge-Memory-Wiki

# karpathy-init Generate the three tool-agnostic, in-repo contracts that make a project legible to any agent. Output is plain markdown — no Claude-only syntax — so a parallel GPT/Copilot agent benefits too. ## Safety: never destroy existing intent - **Never overwrite** an existing `specs/SPEC.md`, `VERIFIER.md`, `ENVIRONMENT.md`, or `AGENTS.md` without first showing the user a diff and getting an OK. - **Append** to an existing `AGENTS.md`; do not clobber existing pointers (e.g. ExampleApp's `project_instructions.yaml` references). - If a contract already exists, offer to *update/refresh* it instead of recreating. ## Step 1 — Detect the stack Look for these markers (a repo may have several; list them all): | Marker | Stack | Build | Test | Run | |---|---|---|---|---| | `*.sln`, `*.csproj` | .NET / C# | `dotnet build <sln>` | `dotnet test` | `dotnet run --project <startup>` | | `package.json` | Node/JS/TS | `npm run build` (if present) | `npm test` | `npm start` / `npm run dev` | | `pyproject.toml`, `requirements.txt`, `setup.py` | Python | `pip install -e .` / `uv sync` | `pytest` | `python -m <pkg>` | | `go.mod` | Go | `go build ./...` | `go test ./...` | `go run .` | | `Cargo.toml` | Rust | `cargo build` | `cargo test` | `cargo run` | | none of the above | other | ask the user | ask the user | ask the user | Read the actual scripts/targets (package.json `scripts`, csproj, Makefile, CI files) and use the **real** commands, not the generic guesses above. Identify t