← ClaudeAtlas

project-experiencelisted

Use when writing code, designing architecture, choosing dependencies, or implementing features — especially when the task involves technology or domains (C++, Qt, astronomy, desktop apps, image processing, scientific computing) where the author has prior project experience documented in the vault. Also use when the user mentions starting a new project or asks you to follow their coding style.
ZeusYue/acceptance-driven-development-skill · ★ 6 · Code & Development · score 76
Install: claude install-skill ZeusYue/acceptance-driven-development-skill
# Project Experience ## Overview Read the project documentation library — a collection of structured project docs (tech stack, architecture, reusable patterns, known pitfalls, coding conventions) stored in any folder (Obsidian vault or plain directory). Before writing any code, mine these documents for constraints and patterns that generic AI assistants would miss. **Core principle:** Past projects encode years of hard-won engineering judgment. A 3-minute read of their docs saves hours of repeating their mistakes. **Boundary:** ADD creates, updates, and finalizes `<ProjectName>.md` from the project-document template. `project-experience` consumes those documents, produces a briefing, and refreshes `_exp_memory.md`; it does not author project documentation. ## When to Use ``` New task received ──► Is it code/architecture/dependency related? │ ┌─────────┴──────────┐ │ YES │ NO → skip ▼ Run Phase 0.1: locate doc hub │ ┌─────┴──────┐ ▼ ▼ _exp_memory.md? _exp_memory.md? YES NO │ │ ▼ ▼ Phase 0.2: read Phase 0.3: find cache & validate project docs │ │ ┌─────┴──────┐ ▼ ▼ ▼ Phase 1–5 full Valid Empty │ cache? → treat ▼ │ a