Add "Inki" Claude Code plugin: discover, write, review, submit your docs

.claude-plugin/marketplace.json

@@ -0,0 +1,13 @@
+{
+  "name": "strapi-documentation",
+  "owner": {
+    "name": "Strapi Documentation"
+  },
+  "plugins": [
+    {
+      "name": "inki",
+      "description": "Inki — discover, write, review, submit your docs. A Claude Code plugin encapsulating the Strapi documentation toolkit.",
+      "source": "./claude-plugins/inki"
+    }
+  ]
+}

.cursor/rules/strapi-docs-drafter.mdc

@@ -56,7 +56,7 @@ The Drafter operates in one of 3 modes, determined by the target's `priority` an
 
 **Mode selection rule:** If an outline is provided → Compose. If a `micro_instruction` is provided → Micro-edit. Otherwise (existing page + edits needed) → Patch.
 
-See the interface specification (`agents/prompts/shared/drafter-interface.md`) for the full mode selection logic.
+See the interface specification (`claude-plugins/inki/references/prompts/shared/drafter-interface.md`) for the full mode selection logic.
 
 ---
 
@@ -66,8 +66,8 @@ See the interface specification (`agents/prompts/shared/drafter-interface.md`) f
 
 ```yaml
 doc_type: feature | plugin | configuration | guide | api | ...
-template: agents/templates/feature-template.md    # or null
-guide: agents/authoring/AGENTS.cms.features.md     # or null
+template: claude-plugins/inki/references/templates/feature-template.md    # or null
+guide: claude-plugins/inki/references/authoring/AGENTS.cms.features.md     # or null
 key_topics: [topic1, topic2]
 
 target:
@@ -88,7 +88,7 @@ The outline contains:
 - `sections` — the heading tree with `intent`, `content_hints`, `source_refs`, and `components` per node
 - `drafter_notes` — free-text notes about gaps, ambiguities, and cross-links
 
-See the interface specification (`agents/prompts/shared/drafter-interface.md`) for the full outline schema.
+See the interface specification (`claude-plugins/inki/references/prompts/shared/drafter-interface.md`) for the full outline schema.
 
 #### Source material
 

.cursor/rules/strapi-docs-orchestrator.mdc

@@ -293,10 +293,10 @@ When a prompt needs to run, search project knowledge for the file name (e.g., se
 
 ### Claude Code
 
-The prompt files live in the repository at `agents/prompts/`. Claude Code can read them directly from disk:
+The prompt files live in the repository at `claude-plugins/inki/references/prompts/`. Claude Code can read them directly from disk:
 
 ```
-cat agents/prompts/router.md
+cat claude-plugins/inki/references/prompts/router.md
 ```
 
 The `AGENTS.md` file at the repo root can serve as an alternative entry point, but this system prompt provides more detailed orchestration logic.
@@ -305,7 +305,7 @@ The `AGENTS.md` file at the repo root can serve as an alternative entry point, b
 
 Add the prompt files to the workspace context. Depending on the IDE:
 
-- **Cursor**: Reference prompt files with `@file` (e.g., `@agents/prompts/router.md`) or add them to `.cursor/rules/`. See [Cursor Rules Setup](#cursor-rules-setup) below.
+- **Cursor**: Reference prompt files with `@file` (e.g., `@claude-plugins/inki/references/prompts/router.md`) or add them to `.cursor/rules/`. See [Cursor Rules Setup](#cursor-rules-setup) below.
 - **Windsurf**: Add to `.windsurfrules` or reference in workspace context.
 - **Other IDE agents**: Add the prompt files to whatever context/knowledge mechanism the IDE provides.
 
@@ -501,8 +501,8 @@ The `shared/` folder contains guides used by multiple prompts:
 ## References
 
 - **12 Rules of Technical Writing:** https://github.com/strapi/documentation/blob/main/12-rules-of-technical-writing.md
-- **Templates:** [`agents/templates/` in the repository](https://github.com/strapi/documentation/tree/main/agents/templates)
-- **Authoring guides:** [`agents/authoring/AGENTS.*.md` in the repository](https://github.com/strapi/documentation/tree/main/agents/authoring)
+- **Templates:** [`claude-plugins/inki/references/templates/` in the repository](https://github.com/strapi/documentation/tree/main/claude-plugins/inki/references/templates)
+- **Authoring guides:** [`claude-plugins/inki/references/authoring/AGENTS.*.md` in the repository](https://github.com/strapi/documentation/tree/main/claude-plugins/inki/references/authoring)
 - **Root agent guide:** [`AGENTS.md` in the repository](https://github.com/strapi/documentation/blob/main/AGENTS.md)
 
 ---
@@ -656,12 +656,12 @@ Detected: **[Type]** (from path `[path]`)
 
 | Path pattern | Type | Template |
 |-------------|------|----------|
-| `cms/features/*` | Feature | `agents/templates/feature-template.md` |
-| `cms/plugins/*` | Plugin | `agents/templates/plugin-template.md` |
-| `cms/configurations/*` | Configuration | `agents/templates/configuration-template.md` |
-| `cms/api/*` | API | `agents/templates/api-template.md` |
-| `cms/migration/**/breaking-changes/*` | Breaking Change | `agents/templates/breaking-change-template.md` |
-| `**/guides/*` or "How to..." | Guide | `agents/templates/guide-template.md` |
+| `cms/features/*` | Feature | `claude-plugins/inki/references/templates/feature-template.md` |
+| `cms/plugins/*` | Plugin | `claude-plugins/inki/references/templates/plugin-template.md` |
+| `cms/configurations/*` | Configuration | `claude-plugins/inki/references/templates/configuration-template.md` |
+| `cms/api/*` | API | `claude-plugins/inki/references/templates/api-template.md` |
+| `cms/migration/**/breaking-changes/*` | Breaking Change | `claude-plugins/inki/references/templates/breaking-change-template.md` |
+| `**/guides/*` or "How to..." | Guide | `claude-plugins/inki/references/templates/guide-template.md` |
 
 ---
 

.cursor/rules/strapi-docs-outline-checker.mdc

@@ -166,12 +166,12 @@ Each page should primarily serve ONE Diataxis type:
 
 | Path pattern | Type | Template |
 |-------------|------|----------|
-| `cms/features/*` | Feature | `agents/templates/feature-template.md` |
-| `cms/plugins/*` | Plugin | `agents/templates/plugin-template.md` |
-| `cms/configurations/*` | Configuration | `agents/templates/configuration-template.md` |
-| `cms/api/*` | API | `agents/templates/api-template.md` |
-| `cms/migration/**/breaking-changes/*` | Breaking Change | `agents/templates/breaking-change-template.md` |
-| `**/guides/*` or title starts with "How to" | Guide | `agents/templates/guide-template.md` |
+| `cms/features/*` | Feature | `claude-plugins/inki/references/templates/feature-template.md` |
+| `cms/plugins/*` | Plugin | `claude-plugins/inki/references/templates/plugin-template.md` |
+| `cms/configurations/*` | Configuration | `claude-plugins/inki/references/templates/configuration-template.md` |
+| `cms/api/*` | API | `claude-plugins/inki/references/templates/api-template.md` |
+| `cms/migration/**/breaking-changes/*` | Breaking Change | `claude-plugins/inki/references/templates/breaking-change-template.md` |
+| `**/guides/*` or title starts with "How to" | Guide | `claude-plugins/inki/references/templates/guide-template.md` |
 
 ### Override
 

.cursor/rules/strapi-docs-outline-generator.mdc

@@ -48,8 +48,8 @@ The machine-readable YAML from the Router, containing:
 
 ```yaml
 doc_type: feature | plugin | configuration | guide | api | breaking-change
-template: agents/templates/feature-template.md    # or null
-guide: agents/authoring/AGENTS.cms.features.md    # or null
+template: claude-plugins/inki/references/templates/feature-template.md    # or null
+guide: claude-plugins/inki/references/authoring/AGENTS.cms.features.md    # or null
 key_topics: [topic1, topic2, topic3]
 
 targets:
@@ -75,7 +75,7 @@ The raw input that describes what needs to be documented:
 
 **Not required when:** `action: create_page` — the page doesn't exist yet.
 
-**How to obtain it:** Use GitHub MCP tools to fetch the file from the repository (see `agents/prompts/shared/github-mcp-usage.md`).
+**How to obtain it:** Use GitHub MCP tools to fetch the file from the repository (see `claude-plugins/inki/references/prompts/shared/github-mcp-usage.md`).
 
 ---
 
@@ -95,8 +95,8 @@ If the Router output contains multiple `primary` targets (rare), generate a sepa
 
 **Before analyzing source material**, read the template and authoring guide specified in the Router output:
 
-1. **Read the template file** (e.g., `agents/templates/feature-template.md`). This is the Single Source of Truth (SSOT) for required sections, components, and structure.
-2. **Read the authoring guide** (e.g., `agents/authoring/AGENTS.cms.features.md`). This provides additional conventions, heading rules, and quality expectations.
+1. **Read the template file** (e.g., `claude-plugins/inki/references/templates/feature-template.md`). This is the Single Source of Truth (SSOT) for required sections, components, and structure.
+2. **Read the authoring guide** (e.g., `claude-plugins/inki/references/authoring/AGENTS.cms.features.md`). This provides additional conventions, heading rules, and quality expectations.
 
 If both `template` and `guide` are null (rare), fall back to the type-specific heuristics in the "Document type handling" section below plus the 12 Rules of Technical Writing.
 
@@ -151,8 +151,8 @@ Generate the structured YAML outline following the output format defined below.
 
 ### Feature (`doc_type: feature`)
 
-**Template:** `agents/templates/feature-template.md`
-**Guide:** `agents/authoring/AGENTS.cms.features.md`
+**Template:** `claude-plugins/inki/references/templates/feature-template.md`
+**Guide:** `claude-plugins/inki/references/authoring/AGENTS.cms.features.md`
 
 **Skeleton:** H1 → `<Tldr>` → Intro → `<IdentityCard>` → `## Configuration` → `## Usage`
 
@@ -164,8 +164,8 @@ Generate the structured YAML outline following the output format defined below.
 
 ### Plugin (`doc_type: plugin`)
 
-**Template:** `agents/templates/plugin-template.md`
-**Guide:** `agents/authoring/AGENTS.cms.plugins.md`
+**Template:** `claude-plugins/inki/references/templates/plugin-template.md`
+**Guide:** `claude-plugins/inki/references/authoring/AGENTS.cms.plugins.md`
 
 **Skeleton:** H1 → `<Tldr>` → `<IdentityCard isPlugin>` → `## Installation` → `## Configuration` → `## Usage`
 
@@ -182,8 +182,8 @@ Generate the structured YAML outline following the output format defined below.
 
 ### Configuration (`doc_type: configuration`)
 
-**Template:** `agents/templates/configuration-template.md`
-**Guide:** `agents/authoring/AGENTS.cms.configurations.md`
+**Template:** `claude-plugins/inki/references/templates/configuration-template.md`
+**Guide:** `claude-plugins/inki/references/authoring/AGENTS.cms.configurations.md`
 
 **Common core:** H1 → `<Tldr>` → `:::caution` (if applicable) → Intro paragraph (names file paths)
 
@@ -198,8 +198,8 @@ Generate the structured YAML outline following the output format defined below.
 
 ### Guide (`doc_type: guide`)
 
-**Template:** `agents/templates/guide-template.md`
-**Guide:** `agents/authoring/AGENTS.cms.guides.md`
+**Template:** `claude-plugins/inki/references/templates/guide-template.md`
+**Guide:** `claude-plugins/inki/references/authoring/AGENTS.cms.guides.md`
 
 **Skeleton:** H1 → `<Tldr>` → Intro → `:::prerequisites` → Steps → `## Troubleshooting` (optional)
 
@@ -212,8 +212,8 @@ Generate the structured YAML outline following the output format defined below.
 
 ### API (`doc_type: api`)
 
-**Template:** `agents/templates/api-template.md`
-**Guide:** `agents/authoring/AGENTS.cms.api.md`
+**Template:** `claude-plugins/inki/references/templates/api-template.md`
+**Guide:** `claude-plugins/inki/references/authoring/AGENTS.cms.api.md`
 
 API pages have **3 sub-types**. Determine from source material:
 
@@ -244,8 +244,8 @@ Each endpoint H2 has H3s: Path/query parameters, Request body, Responses, Exampl
 
 ### Breaking Change (`doc_type: breaking-change`)
 
-**Template:** `agents/templates/breaking-change-template.md`
-**Guide:** `agents/authoring/AGENTS.cms.breaking-changes.md`
+**Template:** `claude-plugins/inki/references/templates/breaking-change-template.md`
+**Guide:** `claude-plugins/inki/references/authoring/AGENTS.cms.breaking-changes.md`
 
 **Skeleton:** imports → H1 → Summary → `<Intro />` → `<BreakingChangeIdCard />` → `## Breaking change description` → `## Migration`
 

.cursor/rules/strapi-docs-router.mdc

@@ -36,7 +36,7 @@ The Router cannot make reliable placement decisions without these files. If neit
 
 When the user provides a GitHub PR as source material, use the GitHub MCP tools to fetch the PR content directly.
 
-👉 **See [GitHub MCP Usage Guide](agents/prompts/shared/github-mcp-usage.md)** for the full workflow.
+👉 **See [GitHub MCP Usage Guide](claude-plugins/inki/references/prompts/shared/github-mcp-usage.md)** for the full workflow.
 
 **Quick reference:**
 1. `github:get_pull_request(owner, repo, pull_number)` → PR title, description
@@ -74,7 +74,7 @@ A structured Markdown report containing:
 
 | Page | What to do |
 |------|------------|
-| `path/to/new-page.md` | **Create** new page — follow [Feature template](https://github.com/strapi/documentation/blob/main/agents/templates/feature-template.md) + [Features authoring guide](https://github.com/strapi/documentation/blob/main/agents/authoring/AGENTS.cms.features.md) |
+| `path/to/new-page.md` | **Create** new page — follow [Feature template](https://github.com/strapi/documentation/blob/main/claude-plugins/inki/references/templates/feature-template.md) + [Features authoring guide](https://github.com/strapi/documentation/blob/main/claude-plugins/inki/references/authoring/AGENTS.cms.features.md) |
 | `path/to/existing.md` | **Update** — add [description] to "[Section name]" section |
 | `path/to/other.md` | **Update** — add row to "[Table name]" table |
 | `path/to/conditional.md` | **Later** — [condition, e.g., "when X feature ships"] |
@@ -306,12 +306,12 @@ Set `ask_user` (as a top-level YAML field or as the placement decision) when:
 
 | Type | Path patterns | Template | Authoring guide |
 |------|--------------|----------|-----------------|
-| **Feature** | `cms/features/*` | `agents/templates/feature-template.md` | `agents/cms/features/AGENTS.md` |
-| **Plugin** | `cms/plugins/*` (not `plugins-development`) | `agents/templates/plugin-template.md` | `agents/cms/plugins/AGENTS.md` |
-| **Configuration** | `cms/configurations/*` | `agents/templates/configuration-template.md` | `agents/cms/configurations/AGENTS.md` |
-| **Guide** | `**/guides/*` or task-oriented "How to…" | `agents/templates/guide-template.md` | `agents/cms/AGENTS.guides.md` |
-| **API** | `cms/api/*` | `agents/templates/api-template.md` | `agents/cms/api/AGENTS.md` |
-| **Breaking Change** | `cms/migration/**/breaking-changes/*.md` | `agents/templates/breaking-change-template.md` | `agents/cms/migration/AGENTS.md` |
+| **Feature** | `cms/features/*` | `claude-plugins/inki/references/templates/feature-template.md` | `agents/cms/features/AGENTS.md` |
+| **Plugin** | `cms/plugins/*` (not `plugins-development`) | `claude-plugins/inki/references/templates/plugin-template.md` | `agents/cms/plugins/AGENTS.md` |
+| **Configuration** | `cms/configurations/*` | `claude-plugins/inki/references/templates/configuration-template.md` | `agents/cms/configurations/AGENTS.md` |
+| **Guide** | `**/guides/*` or task-oriented "How to…" | `claude-plugins/inki/references/templates/guide-template.md` | `agents/cms/AGENTS.guides.md` |
+| **API** | `cms/api/*` | `claude-plugins/inki/references/templates/api-template.md` | `agents/cms/api/AGENTS.md` |
+| **Breaking Change** | `cms/migration/**/breaking-changes/*.md` | `claude-plugins/inki/references/templates/breaking-change-template.md` | `agents/cms/migration/AGENTS.md` |
 | **Concept** | Introductions, overviews, conceptual pages | None | `agents/cms/AGENTS.concepts.md` |
 | **Cloud** | `cloud/*` | None | `agents/cloud/AGENTS.md` |
 | **Snippet** | `snippets/*` | None | `agents/snippets/AGENTS.md` |
@@ -404,7 +404,7 @@ For **each target** in the routing:
 1. **Determine document type** from the target's path (see Document Types table)
 2. **Locate the template** (if one exists for this type)
 3. **Locate the authoring guide** (if one exists for this type)
-4. If no template or guide exists for a target, note that the [12 Rules of Technical Writing](https://strapi.notion.site/12-Rules-of-Technical-Writing-c75e080e6b19432287b3dd61c2c9fa04) and the [Style Checker](https://github.com/strapi/documentation/blob/main/agents/prompts/style-checker.md) are the minimum standards.
+4. If no template or guide exists for a target, note that the [12 Rules of Technical Writing](https://strapi.notion.site/12-Rules-of-Technical-Writing-c75e080e6b19432287b3dd61c2c9fa04) and the [Style Checker](https://github.com/strapi/documentation/blob/main/claude-plugins/inki/references/prompts/style-checker.md) are the minimum standards.
 
 **Important:** Each target may have a different document type. For example, a routing with both `cms/features/mcp-server.md` and `cms/configurations/server.md` requires:
 - Feature template + Features authoring guide for the feature page
@@ -432,7 +432,7 @@ The "Existing pages found" table must show the correct template and authoring gu
 
 8. **Respect existing architecture.** Prefer fitting content into the existing structure over creating new categories. `create_category` should be rare and always confirmed with the user.
 
-9. **Use GitHub MCP when available.** When the source is a GitHub PR, use the GitHub MCP tools to fetch the PR content directly rather than asking the user to paste it. See [GitHub MCP Usage Guide](agents/prompts/shared/github-mcp-usage.md).
+9. **Use GitHub MCP when available.** When the source is a GitHub PR, use the GitHub MCP tools to fetch the PR content directly rather than asking the user to paste it. See [GitHub MCP Usage Guide](claude-plugins/inki/references/prompts/shared/github-mcp-usage.md).
 
 10. **Stay in scope.** The Router decides *where* content goes. It does NOT:
     - Extract detailed specifications from the source material (→ Outline Generator)
@@ -639,7 +639,7 @@ targets:
 
 **Source:** User says "Route PR #1542 from strapi/documentation"
 
-**Expected workflow:** See [GitHub MCP Usage Guide](agents/prompts/shared/github-mcp-usage.md)
+**Expected workflow:** See [GitHub MCP Usage Guide](claude-plugins/inki/references/prompts/shared/github-mcp-usage.md)
 
 1. Fetch PR metadata → Title: "Add MCP Server documentation"
 2. Fetch changed files → `docs/cms/features/mcp-server.md` (added), `docs/cms/configurations/server.md` (modified)