From f73fc03c67e37bfa8290cbb03c5d2ec188aa5eea Mon Sep 17 00:00:00 2001 From: Amolith Date: Fri, 15 Aug 2025 17:57:39 -0600 Subject: [PATCH] feat(init): elicit control/data flow, arch descs --- internal/agent/templates/initialize.md.tpl | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/internal/agent/templates/initialize.md.tpl b/internal/agent/templates/initialize.md.tpl index 1ca1a8132b07bc9d05efe32aaea04d050a1a1a2e..6b7458ce4542415afb75ea8d583a9583ec1ca930 100644 --- a/internal/agent/templates/initialize.md.tpl +++ b/internal/agent/templates/initialize.md.tpl @@ -2,7 +2,7 @@ Analyze this codebase and create/update **{{.Config.Options.InitializeAs}}** to **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}}." -**Goal**: Document what an agent needs to know to work in this codebase - commands, patterns, conventions, gotchas. +**Goal**: Document what an agent needs to know to work in this codebase - commands, patterns, conventions, gotchas, overall architecture, how components fit together **Discovery process**: @@ -10,13 +10,13 @@ Analyze this codebase and create/update **{{.Config.Options.InitializeAs}}** to 2. Look for existing rule files (`.cursor/rules/*.md`, `.cursorrules`, `.github/copilot-instructions.md`, `claude.md`, `agents.md`) - only read if they exist 3. Identify project type from config files and directory structure 4. Find build/test/lint commands from config files, scripts, Makefiles, or CI configs -5. Read representative source files to understand code patterns +5. Read representative source files to understand code patterns, architecture, control/data flow 6. If {{.Config.Options.InitializeAs}} exists, read and improve it **Content to include**: - Essential commands (build, test, run, deploy, etc.) - whatever is relevant for this project -- Code organization and structure +- Code organization and structure, application architecture and control/data flow - Naming conventions and style patterns - Testing approach and patterns - Important gotchas or non-obvious patterns