Documentation Method
Diátaxis
Absorbed
Useful for separating explanation, guidance, and reference material.
Advanced
Condensed into introduction, architecture, algorithms, performance, evidence, and references.
References and Evolution
This page is not a link dump. It is the site dossier: where the methods come from, what the competitor landscape teaches, where this project goes further, and which evolution questions remain open.
Reference Dossier
Map methods, competitors, and evolution signals into one reusable matrix
Each reference should explain which layer it influenced and what this site advances beyond it.
Docs Engineering
MoonshotAI / kimi-cli
Absorbed
Borrowed the build-time docs snapshot workflow.
Advanced
Expanded the snapshot into a data model that powers figures, metrics, and dossiers.
Open Source Framing
AOSA / peer repositories
Absorbed
Treats structure, boundaries, and trade-offs as publishable assets.
Advanced
Turns the rules index into an evidence layer rather than the whole story.
Competitor comparison
| Competitor / reference | Worth learning | Adopted here | Advanced here |
|---|---|---|---|
| kimi-cli | Clear docs engineering | Pre-build sync | A fuller whitepaper shell |
| cursor-rules | Broad template coverage | Corpus survey | Architecture and algorithm chapters |
| awesome-cursorrules | Efficient resource aggregation | Entry-point organization | Evidence library plus research dossier |
Why a competitor view matters
Competitor analysis is not there to dismiss other projects. It helps define whether this project has a real differentiator, which ideas were adopted, and where the system can still evolve.
Evolution questions
The next meaningful evolution questions include:
- Should the snapshot layer emit more granular rule quality signals?
- Should the algorithms chapter visualize more composition and upgrade paths?
- Should the evidence library support stronger thematic comparison views?
- Should competitor analysis evolve into a maintained comparison database?