Official coverage map
Mapping the recorded official Markdown inventory to local guides, maintenance procedures and command-cache coverage.
This page audits the original migration snapshot from the official llms.txt: 163 Markdown pages. Local guides aggregate them by onboarding, configuration, governance, extensions, SDK, costs and troubleshooting instead of mirroring each page separately.
Recorded snapshot:
| Item | Count | Location |
|---|---|---|
| Official Markdown pages | 163 | /tmp/claude-docs-current/manifest.json |
| Local Claude Code pages | 73 | content/docs/claude-code/*.mdx |
| Direct official references | 163/163 | Each source URL appears in at least one local page |
| Official commands | 101 | Commands and cache effects cover the recorded set |
#Coverage areas
#Commands and caching
Commands preserves names, purpose and visibility. Cache effects adds five-minute/one-hour implications for the same recorded 101 commands.
Cache interpretation:
| Type | Explanation |
|---|---|
| Five minutes | Typical default for API/Console/gateway paths |
| One hour | Eligible subscriptions or extended-TTL upstreams |
| Commands | Configuration/navigation/permissions/UI/session actions may change future prompts/tools/providers without calling the main model |
| Provider switching | Do not assume reuse across endpoint/model/region/upstream/key changes |
#Maintenance scripts
After refreshing sources, check for official pages without direct local references:
node - <<'NODE'
const fs=require('fs');
const manifest=JSON.parse(fs.readFileSync('/tmp/claude-docs-current/manifest.json','utf8')).entries;
const localFiles=fs.readdirSync('content/docs/claude-code').filter(f=>f.endsWith('.mdx')).map(f=>'content/docs/claude-code/'+f);
const localText=localFiles.map(f=>({f,text:fs.readFileSync(f,'utf8')}));
const missing=[];
for(const e of manifest){
const hits=[];
for(const lf of localText){
if(lf.text.includes(e.url)) hits.push(lf.f);
}
if(!hits.length) missing.push({slug:e.slug,title:e.title,url:e.url});
}
console.log(JSON.stringify({official:manifest.length,directReferenced:manifest.length-missing.length,missingCount:missing.length,missing},null,2));
NODEExtract command coverage from the official table:
node - <<'NODE'
const fs=require('fs');
function official(){
const s=fs.readFileSync('/tmp/claude-docs-current/commands.md','utf8');
return [...new Set([...s.matchAll(/^\|\s*`([^`]+)`/gm)].map(m=>m[1].split(/\s+/)[0]).filter(x=>x.startsWith('/')))].sort();
}
const off=official();
for(const file of ['content/docs/claude-code/commands.mdx','content/docs/claude-code/command-cache.mdx']){
const s=fs.readFileSync(file,'utf8');
const missing=off.filter(c=>!s.includes(c));
console.log(file, JSON.stringify({official:off.length,missingCount:missing.length,missing},null,2));
}
NODE#When to add pages
Prefer a new page when:
- A new independent workflow appears, such as gateway deployment, SDK runtime or governance.
- An existing page has become too long to navigate effectively.
- Gateway, caching, provider or regional deployment boundaries need dedicated explanation.
Prefer updating an existing page when:
- The addition is a command, variable, limitation or troubleshooting entry.
- It belongs to an existing section.
- A source link and explanation suffice without another navigation entry.
Support
Need help?
For setup, billing, or model issues, email us. Check the status page for uptime.
WeChat / QQ support is available at the bottom right.

