docs-workflows

1# Docs Workflows (docs / explanation / issue / prototype / extension)
2 
3This skill groups the repo's documentation-oriented slash commands into reusable workflows.
4 
5## When to use this skill
6 
7Use this skill when the user asks to:
8 
9- create or standardize documentation
10- produce a structured explanation of changes
11- draft an issue
12- create a quick prototype plan or outline
13- add an article/video tutorial entry
14- add AI IDE / skill / command templates
15- run MCP design quality review
16 
17## Source of truth
18 
19- `references/add_article_tutorial.md`
20- `references/create_doc.md`
21- `references/doc_type.md`
22- `references/explanation.md`
23- `references/issue.md`
24- `references/prototype.md`
25- `references/add_video_tutorial.md`
26- `references/add_aiide.md`
27- `references/add_skill.md`
28- `references/add_command.md`
29- `references/mcp_design_review.mdc`
30 
31## Execution rules
32 
331. Read the relevant command template from this skill's `references/`.
342. Apply the template structure and required fields as the output contract.
353. Keep edits minimal and consistent with repo doc locations (e.g. `doc/`, `specs/`).
36   - `doc/` is public documentation and is committed; `specs/` is local-only and gitignored — never commit it, and see `AGENTS.md` section `<internal_dirs>` for sync / retrieval.
374. Prefer clarity and auditability over verbosity.
38 
39## Command mapping
40 
41See `references/command-catalog.md`.