diff --git a/.story_kit/work/2_current/228_story_auto_detect_tech_stack_and_generate_component_sections_during_scaffolding.md b/.story_kit/work/2_current/228_story_auto_detect_tech_stack_and_generate_component_sections_during_scaffolding.md
index 202c9e1..549d45a 100644
--- a/.story_kit/work/2_current/228_story_auto_detect_tech_stack_and_generate_component_sections_during_scaffolding.md
+++ b/.story_kit/work/2_current/228_story_auto_detect_tech_stack_and_generate_component_sections_during_scaffolding.md
@@ -10,11 +10,10 @@ As a user setting up a new project, I want the scaffold to include example [[com
 
 ## Acceptance Criteria
 
-- [ ] Scaffolding inspects the project root for known markers (Cargo.toml, package.json, pyproject.toml, go.mod, etc.) and generates a [[component]] entry for each detected stack
-- [ ] Each generated component includes sensible default setup commands (e.g. pnpm install for Node, cargo check for Rust)
-- [ ] If no known tech stack is detected, a single root component with empty setup is generated so the pipeline doesn't break
-- [ ] The generated components are written into project.toml alongside the agent sections
-- [ ] Existing project.toml files with components already defined are not overwritten
+- [ ] DEFAULT_PROJECT_TOML includes example [[component]] sections with comments indicating they are placeholders to be replaced with real definitions
+- [ ] Example components cover common patterns (e.g. a frontend component with pnpm install, a backend component with cargo check) so users understand the format
+- [ ] The chat agent's project setup prompt instructs it to inspect the project's tech stack and replace the example components with real [[component]] definitions
+- [ ] Existing project.toml files with components already defined are not overwritten during scaffolding
 
 ## Out of Scope