← ClaudeAtlas

project-bootstraplisted

Bootstraps or standardizes the full AI-agent workspace for any project - analyzes the existing source first, then generates/reconciles the complete .claude folder (agents incl. orchestrator, rules, commands, hooks, skills, settings.json), the standardized docs tree (specs/requirements/architecture/tasks/context/templates), CLAUDE.md + AGENTS.md + README.md, and relevant skills - so the repo runs under orchestrator-driven task control. Use when the user asks to "set up base", "thiet lap base coding", "chuan hoa claude folder", "chuan hoa source thanh claude ready", "khoi tao workspace cho AI agents", or starts/adopts a project that should follow the standard structure.
nguyenhx2/agent-harness-bootstrap · ★ 5 · AI & Automation · score 77
Install: claude install-skill nguyenhx2/agent-harness-bootstrap
# Project bootstrap Sets up the standard AI-agent operating structure for a project, Claude Code first (other tools via AGENTS.md). The skill is **self-contained**: every asset it generates has a bundled template under `templates/` (settings.json, hooks, agents, rules, commands, root files, docs). A user-supplied reference repository is OPTIONAL enrichment - when one is given, prefer copying its battle-tested files and adapt; when none is given, generate everything from the bundled packs. This SKILL.md is the navigation layer. Detailed procedures live in `reference/`; copyable assets live in `templates/`. Read each file when you reach that step - do not improvise a step that has a reference doc. ## Three modes - decide first | Mode | When | What changes | |------|------|--------------| | **Greenfield** | Empty or near-empty repo | Generate the full structure from intake answers | | **Brownfield (standardize existing source)** | Repo already has code, and possibly a partial `.claude`/docs | Run codebase analysis FIRST (`reference/codebase-analysis.md`), derive most intake answers from evidence, then RECONCILE - never clobber - the existing setup into the standard shape | | **Audit / assessment** | The repo(s) are ANALYSED but never MODIFIED by agents - e.g. a read-only security/performance audit, possibly over multiple product repos under one workspace root | Build a CONTROL PLANE (root `.claude` + `docs/`) beside the untouched source: agents are read-only on product code