Inki references
This skill holds no workflow. It hosts the files that several inki-* skills share, so each file exists once. Other skills cite them as ../inki-references/<path>, relative to their own SKILL.md, a path that resolves the same from the source folder and from every linked skills folder.
templates/: page skeletons per doc type (feature, plugin, configuration, API, guide, breaking change, Cloud). Start withtemplates/README.md. Component rules (badges, tabs…) are intemplates/components/.authoring/:AGENTS.*.mdauthoring guides, one per docs area (CMS features, plugins, API, configurations, guides, breaking changes, Cloud, snippets).prompts/: reviewer and drafter specifications (router, outliner, outline checker, UX analyzer, drafter, style checker, integrity checkers, known-pitfalls catalog). Start withprompts/README.md.shared/: commit, push, PR, PR title, and PR description rules used byinki-commit,inki-push,inki-pr, andinki-pr-fix.12-rules-of-technical-writing.md,STYLE_GUIDE.pdf: the writing rules. The repo-root12-rules-of-technical-writing.mdis canonical; this copy is synced by CI.git-rules.md: branch, commit, and PR conventions. The repo-rootgit-rules.mdis canonical; this copy is synced by CI.logging.md: how everyinki-*skill writes its run log.help.md: how everyinki-*skill answers--help.subject-resolver.md,target-resolver.md: howinki-documentandinki-reviewturn their argument into a subject or a list of files.