Context-efficient codebase navigation and documentation using structured frontmatter headers. Use this when exploring an unfamiliar codebase, answering "where is X / how does Y work" questions, or when asked to add/maintain file-level documentation. Index a tree's headers in one pass instead of reading every file, and generate or validate frontmatter with the bundled scripts. Reach for it whenever token budget matters while navigating code, even if the user does not say "frontmatter".
71
100%
Does it follow best practices?
Impact
52%
4.33xAverage score across 7 eval scenarios
Passed
No known issues
Navigate a documented url-shortener to find where to add a storage backend
Names interface file
0%
100%
Names implementation to model on
0%
100%
Names wiring file
0%
100%
Trace a short-link click through a documented url-shortener
Traces server then shortener
0%
0%
Locates click increment in store
0%
0%
Determine rate-limiting scope and implementation in a documented analytics-api
States per-API-key scope
0%
0%
Identifies implementation file
0%
0%
Navigate a documented analytics-api to find where to add a storage backend
Names interface file
0%
0%
Names template implementation
0%
0%
Names wiring file
0%
0%
Add valid code-frontmatter headers to a bare (undocumented) url-shortener
All substantive files covered
100%
100%
Blocks are valid
62%
100%
Purposes accurate and specific
100%
100%
Trace POST /v1/events ingestion through a documented analytics-api
Traces ingest entry path
0%
62%
Locates validation
0%
75%
Locates storage write
0%
62%
Find the server-side timestamp-override rule in a documented analytics-api
Identifies responsible file
0%
100%
States the rule
0%
100%