f41c22d0ac
- CLAUDE.md: add "Question the question" and "One clarifying question" rules to Tone and Interaction — XY problem detection, false premise checks, and explicit reframe pattern before answering - Add claude/ detail-file directory (topic docs referenced from CLAUDE.md) - Add ABOUT.md, FUTURE.md - Update memory/, scripts/, settings.yaml with accumulated session changes Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
23 lines
1.5 KiB
Markdown
23 lines
1.5 KiB
Markdown
# New Projects
|
|
|
|
When the user picks "New project!" from the session-start menu, or otherwise asks to start a new project:
|
|
|
|
1. Create a new directory under `~/dev/claude/<project-name>/`
|
|
2. **Ask the user** which Gitea user/org the repo should be created under (e.g., `homelab`, `skynet`, `oreillyit`, a personal user) before setting up the remote
|
|
3. Create the initial standard files:
|
|
- **ABOUT.md** — One-sentence project description (see `documentation-standards.md`). Picked up by `context-load` for the session-start menu.
|
|
- **CLAUDE.md** — Project-specific architecture, conventions, repo structure, and working instructions for Claude
|
|
- **MEMORY.md** — Thin index pointing to `memory/` topic files
|
|
- **FUTURE.md** — Backlog ideas (Problem/Idea/Open questions/Depends on format)
|
|
- **README.md** — Human-readable overview, quick start, milestones, scripts reference
|
|
4. Parse sibling project CLAUDE.md files in `~/dev/claude/` and bring over related practices, guidelines, and learnings that apply to the new project's stack
|
|
5. **For coding projects with multiple milestones:** Read `best-practices/spec-driven-development.md` and `best-practices/test-driven-development.md`. Create `SPEC.md` and `spec/` directory. Write specs before writing code — see `spec-driven-development.md`.
|
|
|
|
## ABOUT.md format
|
|
|
|
```markdown
|
|
description: One sentence describing what this project is
|
|
```
|
|
|
|
Every project **must** have an ABOUT.md. Keep the description under ~80 characters.
|