@@ -2,7 +2,7 @@ Analyze this codebase and create/update **{{.Config.Options.InitializeAs}}** to
3**First**: Check if directory is empty or contains only config files. If so, stop and say "Directory appears empty or only contains config. Add source code first, then run this command to generate {{.Config.Options.InitializeAs}}."
3**First**: Check if directory is empty or contains only config files. If so, stop and say "Directory appears empty or only contains config. Add source code first, then run this command to generate {{.Config.Options.InitializeAs}}."
5−**Goal**: Document what an agent needs to know to work in this codebase - commands, patterns, conventions, gotchas.
5+**Goal**: Document what an agent needs to know to work in this codebase - commands, patterns, conventions, gotchas, overall architecture, how components fit together
7**Discovery process**:
7**Discovery process**:
@@ -10,13 +10,13 @@ Analyze this codebase and create/update **{{.Config.Options.InitializeAs}}** to
102. Look for existing rule files (`.cursor/rules/*.md`, `.cursorrules`, `.github/copilot-instructions.md`, `claude.md`, `agents.md`) - only read if they exist
102. Look for existing rule files (`.cursor/rules/*.md`, `.cursorrules`, `.github/copilot-instructions.md`, `claude.md`, `agents.md`) - only read if they exist
113. Identify project type from config files and directory structure
113. Identify project type from config files and directory structure
124. Find build/test/lint commands from config files, scripts, Makefiles, or CI configs
124. Find build/test/lint commands from config files, scripts, Makefiles, or CI configs
13−5. Read representative source files to understand code patterns
13+5. Read representative source files to understand code patterns, architecture, control/data flow
146. If {{.Config.Options.InitializeAs}} exists, read and improve it
146. If {{.Config.Options.InitializeAs}} exists, read and improve it
16**Content to include**:
16**Content to include**:
18- Essential commands (build, test, run, deploy, etc.) - whatever is relevant for this project
18- Essential commands (build, test, run, deploy, etc.) - whatever is relevant for this project
19−- Code organization and structure
19+- Code organization and structure, application architecture and control/data flow
20- Naming conventions and style patterns
20- Naming conventions and style patterns
21- Testing approach and patterns
21- Testing approach and patterns
22- Important gotchas or non-obvious patterns
22- Important gotchas or non-obvious patterns