← ClaudeAtlas

aod-foundationlisted

Guided post-init workshop that helps new AOD Kit adopters establish product vision and design identity. Two-part flow: Part 1 (Vision) asks 5 guided questions to populate product-vision.md; Part 2 (Design) browses archetypes to generate brand files (brand.md, tokens.css, anti-patterns.md). Supports --vision and --design flags for partial execution. Use when a developer invokes /aod.foundation after running make init.
davidmatousek/tachi · ★ 75 · AI & Automation · score 82
Install: claude install-skill davidmatousek/tachi
# /aod.foundation Skill ## Purpose Guided post-init workshop with two parts: - **Part 1 (Vision)**: 5 storytelling-arc questions that populate `product-vision.md` - **Part 2 (Design)**: Archetype browser that generates `brands/{project-name}/` files Run after `make init` to replace placeholder markers with real content. --- ## Step 0: Parse Flags Parse `--vision` and `--design` flags from the user's arguments. 1. If arguments contain `--vision`: - Set `vision_only = true` - Strip `--vision` from arguments 2. If arguments contain `--design`: - Set `design_only = true` - Strip `--design` from arguments 3. If neither flag is present: - Set `run_both = true` (full workshop) 4. If both flags are present: - Treat as `run_both = true` (equivalent to no flags) --- ## Step 1: State Detection Detect the current project state to determine which parts to activate and whether this is a first-run or re-run. ### 1a: Derive Project Name Use this ordered fallback to determine `{project-name}`: 1. **Repository directory name**: Run `basename $(git rev-parse --show-toplevel)` — use this if it yields a non-empty value 2. **CLAUDE.md PROJECT_NAME**: Read `CLAUDE.md`, grep for a line matching `PROJECT_NAME` that does NOT contain `tachi` (the un-replaced placeholder). Extract the value. 3. **AskUserQuestion fallback**: If neither source yields a usable name, ask: "What is your project name?" with a text input. Sanitize the derived name to **kebab-case**: lowercase, r