From bf21a59b9d559f19b720d8325edad73cbeca8d40 Mon Sep 17 00:00:00 2001 From: Amolith Date: Tue, 31 Mar 2026 13:46:22 -0600 Subject: [PATCH] feat(init): elicit control/data flow, arch descs (#1790) --- 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 c9c79c32bd6fc444a9d2fec30545e43285a313d3..d352960a1e5bb79e78b6e34e56ee58aaa13c6d25 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