Resolve the stale CLAUDE.md problem by removing the duplicated workflow/build/storage guide from the root Claude entrypoint. The root file now points to canonical sources, while the unique Visual Design System content moves into AGENT_INSTRUCTIONS.md where AGENTS.md already directs agents for full guidance. Also refresh docs/CLAUDE.md architecture paths that had drifted from current main. Refs GH#3426. Co-authored-by: Steven Syrek <steven.syrek@deepl.com>
1.1 KiB
1.1 KiB
Claude Code Entry Point for Beads
This file is intentionally short. Do not copy workflow, build, storage, or UI rules here; those details drift quickly when repeated across agent entrypoints.
Read First
- Workflow and safety: AGENTS.md
- Detailed agent operations: AGENT_INSTRUCTIONS.md
- Architecture orientation: docs/CLAUDE.md
- PR maintenance policy: PR_MAINTAINER_GUIDELINES.md
Current Ground Rules
- Run
bd primebefore doing tracked work. - Follow
go.modand AGENT_INSTRUCTIONS.md for build and test commands; do not hard-code toolchain versions here. - Beads uses Dolt as the issue database. Use
bd dolt push/bd dolt pullfor issue data sync; do not use export/import as a routine git workflow. - The CLI Visual Design System lives in AGENT_INSTRUCTIONS.md.
- If this file conflicts with a linked source, trust the linked source and fix this file by removing the duplicate.