mirror of
https://github.com/storytold/deckcraft.git
synced 2026-10-24 10:37:03 -06:00
Brandon ThomasandClaude Opus 5.5
f44857624e
Progress docs per craftrules standards/progress-docs.md: target-app parity, gaps, roadmap with alpha gate, readiness by audience (full / mainstream / essentials) with Opus 5.5 hours, and feature, format, hardware, UI and localization parity docs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
18 lines
890 B
Markdown
18 lines
890 B
Markdown
# DeckCraft — working notes for Claude
|
|
|
|
Read [AGENTS.md](AGENTS.md) first: its rules (asset policy, clean room, never crash) bind you and
|
|
win over anything here.
|
|
|
|
## Start every session
|
|
1. Read `plan/STATUS.md`, then the current milestone in `plan/execution-plan.md`.
|
|
2. Read `../../craftrules/AGENTS.md` and the standards it lists for your task.
|
|
3. Run `cargo xtask ci` before you change anything, so you know the tree is green.
|
|
|
|
## Habits
|
|
- Every user-visible action is a command with tests (`crates/engine/src/cmd/*`).
|
|
- Look at UI changes: `deckcraft --sample --control 7990` + `ui.screenshot`, or
|
|
`deckcraft-cli render`.
|
|
- Commit after each landed arc (`M<n>.<k>: what`) and push to `origin main`.
|
|
- Keep `ROADMAP.md`, the progress docs in `docs/` (AGENTS.md §7) and `plan/STATUS.md` current.
|
|
- Don't ask the user questions; record genuinely-theirs decisions in `plan/STATUS.md`.
|