You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
pubconstSYMBOL_SYSTEM:&str = "You write concise API reference notes. Return one sentence describing the symbol's purpose. Do not include markdown fences.";
6
8
pubconstFILE_SYSTEM:&str = "You write concise file-level code documentation. Return a short purpose summary grounded only in the supplied symbol summaries and source excerpt: what the file does and how its pieces work together. Do not include markdown fences.";
7
9
pubconstCONTENT_FILE_SYSTEM:&str = "You write concise documentation for non-code repository files. Return a short purpose summary describing what the file contains and what it is for, grounded only in the supplied leading content. Do not include markdown fences.";
8
-
pubconstMODULE_SYSTEM:&str = "You write module documentation briefs. Using only the supplied file summaries, child module summaries, and source excerpts, write two to three short paragraphs covering the module's responsibilities, its key flows, and how its files and submodules collaborate. Plain paragraphs only - no headings, no lists, no markdown fences. Cite supporting file:line spans that appear in the supplied input.";
9
-
pubconstREPO_SYSTEM:&str = "You write repository overview briefs. Using only the supplied module summaries, root-file summaries, and source excerpts, write two to three short paragraphs covering what the system is, how the major pieces fit together, and where a reader should start. Plain paragraphs only - no headings, no lists, no markdown fences. Cite supporting file:line spans that appear in the supplied input.";
10
-
pubconstARCHITECTURE_SYSTEM:&str = "You write concise architecture documentation. Using only the supplied summariesand source excerpts, return one to two sentences naming the subsystem's responsibility and how it collaborates with the rest of the system. Do not include markdown fences.";
10
+
pubconstMODULE_SYSTEM:&str = "You write module documentation briefs. Using only the supplied file summaries, child module summaries, component table, and source excerpts, write one to two short paragraphs covering the module's responsibilities, key flows, and collaboration points. Add compact Markdown tables for enumerable facts such as CLI commands or flags, configuration keys, environment variables, and public API symbols. No markdown fences. Cite supporting file:line spans that appear in the supplied input.";
11
+
pubconstREPO_SYSTEM:&str = "You write repository overview briefs. Using only the supplied module summaries, root-file summaries, and source excerpts, write one to two short paragraphs covering what the system is, how the major pieces fit together, and where a reader should start. Add compact Markdown tables for enumerable facts such as CLI commands or flags, configuration keys, environment variables, and public API symbols. No markdown fences. Cite supporting file:line spans that appear in the supplied input.";
12
+
pubconstARCHITECTURE_SYSTEM:&str = "You write concise architecture documentation. Using only the supplied summaries, component table, and source excerpts, return a short responsibility summary plus compact Markdown tables for enumerable facts such as public API symbols, CLI commands or flags, configuration keys, and environment variables. No markdown fences.";
11
13
pubconstARCHITECTURE_NARRATIVE_SYSTEM:&str = "You write architecture overviews. Using only the supplied subsystem responsibilities and dependency edges, write two to three short paragraphs describing the system in layers: which subsystems sit at the foundation, which build on them, and how the layers interact. Plain paragraphs only - no headings, no lists, no markdown fences.";
12
14
pubconstCURATED_NAVIGATION_SYSTEM:&str = "You design a curated navigation layer for grounded code documentation. Return strict JSON only. Name user-facing concept modules, organize them into a hierarchy, and create short narrative tour pages. Use only supplied module and file identifiers, and link into reference pages instead of duplicating source detail.";
constENUMERABLE_FACTS_GUIDANCE:&str = "When the supplied input exposes enumerable facts (CLI commands/flags, configuration keys, environment variables, or public API symbols), prefer compact Markdown tables beside the narrative instead of burying those facts in prose.";
263
274
264
275
/// First paragraph of a child summary, flattened to one line and hard-capped
265
276
/// at [`CHILD_SUMMARY_EXCERPT_MAX_CHARS`], so each prompt list entry stays one
0 commit comments