mirror of
https://github.com/storytold/deckcraft.git
synced 2026-10-30 05:27:06 -06:00
Dylan M. Taylor
97db282daf
AGENTS.md (and CLAUDE.md where present) gets a CI workflows section: workflows only call craft-common-actions at @main, with no other jobs; feature and fix PRs don't touch CI and link or open a craft-common-actions issue (a PR only for a small fix that is safe for every app and does not increase CI time); legacy jobs aren't added to and move only as their own task, staying until a shared workflow runs them. windows-arm64.yml moves from its SHA pin to @main. The pinned revision is on craft-common-actions main and the workflow (and the actions it calls) is identical there, so nothing changes in behaviour.
1.9 KiB
1.9 KiB
DeckCraft — working notes for Claude
Read AGENTS.md first: its rules (asset policy, clean room, never crash) bind you and win over anything here.
New workspace crates must include [lints] workspace = true in Cargo.toml to inherit
[workspace.lints]. Production crate roots must declare the required crate-level lint attributes
before modules or other crate items; crate-level //! documentation may precede them.
Start every session
- Read
plan/STATUS.md, then the current milestone inplan/execution-plan.md. - Read
../../craftrules/AGENTS.mdand the standards it lists for your task. - Run
cargo xtask cibefore 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, ordeckcraft-cli render. - Commit after each landed arc (
M<n>.<k>: what) and push toorigin main. - Keep
ROADMAP.md, the progress docs indocs/(AGENTS.md §7) andplan/STATUS.mdcurrent. - Don't ask the user questions; record genuinely-theirs decisions in
plan/STATUS.md.
CI workflows
- Workflows in
.github/workflows/call the shared workflows instorytold/craft-common-actionsat@main, with their inputs and secrets. No other jobs: if no shared workflow does what's needed, it doesn't go here. - Don't add or change CI in a feature or fix PR. If the existing workflows can't build or test a change, link an existing craft-common-actions issue or PR, or open a new issue, or a PR only for a small fix that is safe for every app and does not increase CI time.
- Some workflow files here still run their own jobs. Don't add to them. Moving a job into craft-common-actions is its own task, never part of another PR, and the job stays here until a shared workflow runs it.