brand
- Senior engineers evaluating project rigor during hiring, due diligence, or architecture review
- GitHub contributors who need a clear map from project value to implementation detail
- Team leads adopting Cursor rules as a reusable engineering asset instead of one-off prompts
Turn a rule collection into a whitepaper-grade project surface: first explain why the library matters, then show how it is structured, then guide readers into evidence, implementation, and research trails.
- precise
- archival
- opinionated
- Lead with thesis, not taxonomy.
- Read like a technical dossier, not a template docs homepage.
- Let diagrams and evidence carry credibility, not decorative marketing copy.
- Keep Chinese as the richest narrative path, with English mirroring the same IA.
- Treat rules as evidence in a broader system of governance, onboarding, and research.
- A new visitor understands the project thesis in the first screen without opening the rules index.
- An interviewer can trace value, architecture, adoption, and evidence in a deliberate reading order.
- Light and dark themes keep diagrams, SVG figures, and data marks legible without fallback hacks.
- The docs build stays deterministic and derives project facts from source assets.
- generic SaaS hero plus metric cards
- glassy AI landing pages
- taxonomy-first docs homes that feel like generated catalogs