From 36122b500be0bc1c10c1b4795aaba5b0294819ae Mon Sep 17 00:00:00 2001 From: Lukas Date: Fri, 27 Mar 2026 16:04:32 +0100 Subject: [PATCH] Add import/export to README, research scope guidance to CLAUDE.md Add import/export feature bullet to README.md (constitution requires README updates when user-facing capabilities change). Add research scope note to CLAUDE.md RPI section: research phases should scan for existing patterns and consolidation opportunities, not just what the feature needs. Remove auto-generated Active Technologies / Recent Changes sections that duplicated Tech Stack. Co-Authored-By: Claude Opus 4.6 (1M context) --- CLAUDE.md | 10 ++-------- README.md | 1 + 2 files changed, 3 insertions(+), 8 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index 39441cd..977ddf6 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -98,6 +98,8 @@ Speckit (`/speckit.*` skills) manages the spec-driven development pipeline. Spec - `rpi-plan` — interactive phased implementation plan in `docs/agents/plans/` - `rpi-implement` — execute a plan file phase by phase with automated + manual verification +**Research scope**: Research should include a scan for existing patterns similar to what the feature needs (e.g., shared UI primitives, duplicated validation logic, repeated state management patterns). Identify extraction and consolidation opportunities before implementation, not during. + ### Choosing the right workflow by scope | Scope | Workflow | @@ -127,11 +129,3 @@ The constitution (`.specify/memory/constitution.md`) governs all feature work: 3. **Clarification-First** — Ask before making non-trivial assumptions. 4. **MVP Baseline** — Say "MVP baseline does not include X", never permanent bans. 5. **Spec-driven features** — Features are described in living specs; evolve existing specs via `/integrate-issue`, create new ones via `/speckit.specify`. Bug fixes and tooling changes do not require specs. - - -## Active Technologies -- TypeScript 5.8 (strict mode, `verbatimModuleSyntax`) + React 19, Vite 6, Tailwind CSS v4, Lucide Reac (007-json-import-export) -- localStorage (encounter, undo/redo, player characters) (007-json-import-export) - -## Recent Changes -- 007-json-import-export: Added TypeScript 5.8 (strict mode, `verbatimModuleSyntax`) + React 19, Vite 6, Tailwind CSS v4, Lucide Reac diff --git a/README.md b/README.md index 229f867..316637c 100644 --- a/README.md +++ b/README.md @@ -9,6 +9,7 @@ A local-first initiative tracker and encounter manager for tabletop RPGs (D&D 5e - **Bestiary integration** — import bestiary JSON sources, search creatures, and view full stat blocks - **Player characters** — create reusable player character templates with name, AC, HP, color, and icon; search and add them to encounters with pre-filled stats; manage (edit/delete) from a dedicated panel - **Undo/redo** — reverse any encounter action with Undo/Redo buttons or keyboard shortcuts (Ctrl+Z / Ctrl+Shift+Z, Cmd on Mac); history persists across page reloads +- **Import/export** — export the full encounter state (combatants, undo/redo history, player characters) as a JSON file or copy to clipboard; import from file upload or pasted JSON with validation and confirmation - **Persistent** — encounters survive page reloads via localStorage; bestiary data cached in IndexedDB; player characters stored independently ## Prerequisites