joseluisamado
- 3 skills
- 0 followers
- 1 day ago last updated
- ▌ Bootstrap Project · joseluisamado bundleCrystallize a project-design conversation into a complete project scaffold. Reads the current session for project name, principles, milestones, stack, and audience; writes the docs/ quintet (PROJECT, ARCHITECTURE, ROADMAP, PROGRESS, DEPLOY), CLAUDE.md, Makefile, CI workflow, pre-commit config, VERSION, LICENSE, CHANGELOG, and supporting files. Supports stack profiles for Python, Node, Go, Rust, polyglot, and Nix flakes; deploy models for docker-compose, single binaries, artifacts (OS images / appliances), and libraries. Use this when the user says "bootstrap this project", "scaffold the repo", "now write all of this down", or invokes /bootstrap-project. The skill is a finalizer — it assumes the design conversation has happened in this session and extracts spec from context. It will ask only the minimum follow-ups (license, optional add-ons, profile-specific questions, anything missing). Do NOT use this for: existing projects (the skill refuses to clobber files); greenfield brainstorming (have the design conve
- ▌ Retrofit Project · joseluisamado bundleReshape an existing project to the bootstrap-project skill standard without losing content, history, or working code. Walks the repo, classifies every file as missing / present-template-shape / present-bespoke / empty-placeholder, asks the same five spec questions as bootstrap-project (plus a content-strategy question), reshapes the docs quintet, backfills CHANGELOG from git history, moves files with reference-updating, and marks the project with `.bootstrap-meta.yaml` mode: retrofit. Use this when the user says "retrofit this project", "bring this repo up to the bootstrap-project standard", "reshape this to skill shape", or invokes /retrofit-project. Like bootstrap-project, it is a finalizer — it assumes the analysis conversation has happened in this session and extracts spec from context. Unlike bootstrap-project, it does NOT refuse on non-empty projects — that is its entire reason to exist. Do NOT use this for: greenfield projects (use /bootstrap-project instead); projects without a `.git/` directory (the
- ▌ Bootstrap Investigation · joseluisamado bundleCrystallize an investigation-design conversation into a complete investigation/documentation project scaffold. For projects whose deliverable is *understanding and a record* — recoveries, reverse-engineering efforts, forensics, research write-ups, post-mortems — NOT software built from source. Reads the current session for project name, subject, principles, phases, and audience; writes the docs quintet (PROJECT, FOUNDATION, SUBJECT, WRITEUP, PRIVACY), the plan under docs/plan/ (PROCEDURE, ROADMAP), a dated append-only logbook/, an evidence/ directory, CLAUDE.md, LICENSE, CHANGELOG, and supporting files. Asks an artifact-provenance policy (private-archive / public-writeup / none) and offers optional add-ons: a go/no-go GATES decision-log, a docs/COMPONENTS.md flat inventory, and an evidence/netlist/ structure map. Use this when the user says "bootstrap this investigation", "scaffold this recovery/research project", "set up the documentation project", or invokes /bootstrap-investigation. The skill is a finalize