Documentation Index#
Start here. For any task, find the doc that owns it below, then read that doc’s first section — each doc states its scope at the top.
AI agents (Claude Code, OpenCode): read
AGENTS.mdfirst (style & process), then this index, then project-context.md for architecture. The “Where does new code go?” decision tree lives inproject-context.md.
Task → doc routing#
| If you are working on… | Read this first |
|---|---|
| Architecture, layers, stack versions, conventions, where new code goes | project-context.md |
The /api/v1 REST API (auth, envelope, error catalog) | api-reference.md |
config.toml schema or environment variables | configuration.md |
| Writing a WASM plugin (hooks, lifecycle, build) | plugin-development.md |
| Plugin capabilities / host functions | plugin-capabilities.md |
| Building or overriding a theme (CSS, templates, JS) | theme-development.md |
GOHTML / Go template formatting (.gohtml files) | coding-standards/html.md |
| Brand assets (logo, colors, typography) | brands.md |
Cross-cutting references#
- Product feature catalog → features.md (the canonical list; the homepage and
README.mdcurate from it). - Coding, testing, and doc-sync conventions →
AGENTS.md(repo root). - Build / test / mock commands →
Makefile:make mock,make lint,make test,make vulncheck,make docs-serve,make build-cli,make build-admin. - External agents building themes/plugins on a deployed site → the installed skills
skills/lesstruct-theme-development/andskills/lesstruct-plugin-development/(theirreferences/are the user-facing snapshots of the theme/plugin docs above).
Doc-ownership contract#
Every doc declares its scope in its first section. When you change code a doc describes,
update that doc in the same change — the full rules and the “If you touch X → update Y”
table are in AGENTS.md under Documentation Sync.