Shift Docs
SkillDocs & knowledgeRoute Shift documentation, architecture notes, and tickets correctly. Use when Codex is about to create or move docs, write an architecture plan, capture a design decision, create a ticket, or update repo documentation for Shift.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Shift Docs skill
What this skill tells your AI
The instructions your AI receives, as published by shift-editor/shift in .codex/skills/shift-docs/SKILL.md and read by ahel’s review.
Use the right destination for the artifact.
Routing
- Stable repo documentation belongs in
docs/or the module's canonicalDOCS.md, followingdocs/architecture/index.md. - Tickets, design scratchpads, future-work plans, and exploratory architecture proposals do not belong in repo
docs/. - Put tickets and exploratory plans in Obsidian under
~/Documents/KostyaVault/projects/shift/, or open a GitHub issue when the user asks for a tracked issue. - Do not create
CONTEXT.mdfiles.
Before Writing
- Read
docs/architecture/index.mdwhen changing stable repo documentation. - If the artifact is a ticket, plan, or unresolved proposal, route it to Obsidian or GitHub instead of
docs/. - If unsure whether something is stable documentation or a ticket, ask briefly before writing.
Signals
- GitHub stars
- 261
- Forks
- 7
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
shift-docs- Source
- github.com/shift-editor/shift