What problem are you trying to solve?
The repo declares a docs contract in .tituskirch-skills.json — docs.preset: package, docs.render: duxt — but no docs/ tree exists. What gitignore-sync does, how it is configured, and which decisions were taken along the way live only in the README or nowhere at all.
Proposed solution
Scaffold docs/ with the write-docs skill in the TitusKirch docs format. Settled up front, so nothing is left to the implementer's judgement:
- Preset
package — the section set comes from the preset; no invented sections.
- Rendering
duxt — docs.render is set, so the duxt page contract applies: no body H1, absolute doc paths, ::page-cards in a section index, theme frontmatter fields, ::callout for the status marker.
- Language
en — from the root language key.
- Scope — the scaffold plus the pages the preset calls for, filled from what the repo actually is today. No ADR as part of this issue.
Alternatives considered
Growing the README instead. Rejected: the config already declares both a preset and a render target, so the README would keep absorbing a docs tree without ever getting its structure.
Additional context
docs.render: duxt was added to this repo's config today. Acceptance: docs/ exists, follows the preset's sections, every page obeys the duxt contract, and no statement in it contradicts the repo.
What problem are you trying to solve?
The repo declares a docs contract in
.tituskirch-skills.json—docs.preset: package,docs.render: duxt— but nodocs/tree exists. What gitignore-sync does, how it is configured, and which decisions were taken along the way live only in the README or nowhere at all.Proposed solution
Scaffold
docs/with thewrite-docsskill in the TitusKirch docs format. Settled up front, so nothing is left to the implementer's judgement:package— the section set comes from the preset; no invented sections.duxt—docs.renderis set, so the duxt page contract applies: no body H1, absolute doc paths,::page-cardsin a section index, theme frontmatter fields,::calloutfor the status marker.en— from the rootlanguagekey.Alternatives considered
Growing the README instead. Rejected: the config already declares both a preset and a render target, so the README would keep absorbing a docs tree without ever getting its structure.
Additional context
docs.render: duxtwas added to this repo's config today. Acceptance:docs/exists, follows the preset's sections, every page obeys the duxt contract, and no statement in it contradicts the repo.