shift-docs

Route 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

SKILL.md.codex/skills/shift-docs/SKILL.md

Shift Docs

Use the right destination for the artifact.

Routing

Stable repo documentation belongs in docs/ or the module's canonical DOCS.md, following docs/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.md files.

Before Writing

Read docs/architecture/index.md when 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.

Related in documents

applying-brand-guidelines-anthropics-claude-cookbooks

This skill applies consistent corporate branding and styling to all generated documents including colors, fonts, layouts...

docx

Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservati...

pdf

Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, a...