@c4a/context-cli 0.5.41-beta.6 → 0.6.0-alpha.1

package/plugins/codex/skills/init/references/internal-procedures/skill-source-scope.md

@@ -0,0 +1,402 @@
+---
+name: skill-source-scope
+description: >
+  Internal procedure invoked by the public Context continuation entry; not a user slash command.
+  Handles source registration, monorepo source boundaries, extract phase
+  declaration, no-write scope preview, and the pre-extraction confirmation gate.
+tools:
+  - Bash
+---
+
+# skill-source-scope
+
+Choose and validate what may become draft knowledge.
+
+## TL;DR
+
+- Missing source means the next product action is "add a knowledge source".
+  Explain that in user-facing language before showing any CLI command.
+- Ask what source the user wants to add: local code repo/package, remote Git
+  repo/package, local Markdown/MDX document/folder, article/documentation repo as a
+  file source, or Lark/Feishu document. Current CLI can execute repo sources,
+  local file sources, and Lark document capture through the declared flow.
+- Treat source registration as a knowledge-boundary decision, not a parameter
+  prompt. Explain that the source name becomes a stable namespace in source
+  refs, phase ids, and package naming. Approved knowledge paths are derived
+  later from collection, containment, and slug. Give concrete examples before
+  asking for confirmation.
+- If the user already provided a path and only the source name is missing, still
+  explain what that name means. Do not ask "confirm source name" without saying
+  whether the boundary is a single package/module or a parent monorepo/subspace
+  namespace.
+- Do not infer a source from cwd, parent directories, package names, monorepo
+  layout, or git remote.
+- In monorepos, one source may conceptually be the whole repo/subspace or one
+  package/subdirectory. If the user wants one package manual, prefer the
+  package/subdirectory. If the user wants one unified knowledge product across
+  modules, explain that the source name becomes the repo/source identity and
+  may be used in codegraph NodeRefs such as `codegraph/product-ui/...` when the
+  extraction rules derive those refs. Current repo extraction
+  still requires choosing a concrete single-module extraction boundary before
+  running extraction; do not run extraction against an ambiguous multi-module
+  source.
+- `extractTs.include` filters files inside the selected source; it is not a
+  package/module selector.
+- Use `context source inspect <source-name> --format json` for module choices.
+- Before first real extraction, generate a no-write preview and show module
+  counts plus `knowledgeTree` / `knowledgePathExamples` to the user. Use
+  `--dry-run` only in the command you execute, not as the user-facing label.
+- Human-facing explanations must describe the extraction impact first: what code
+  files are read, what symbols become draft knowledge, what is skipped, and what
+  review gate follows. Do not lead with `extractTs`, `include`, `exportedOnly`,
+  or `reviewValidity`.
+- Document capture has its own gate. After a file or Lark source is registered,
+  ask for permission before reading the source body, then show the capture
+  summary before handing off to material investigation and structure drafting.
+  Do not default to one page per document, and do not create final draft pages
+  directly from capture.
+- For capture routing, output handling, missing dependency recovery, and final
+  reporting discipline, read the source capture procedure at
+  [skill-source-scope/references/capture-source.md](skill-source-scope/references/capture-source.md). Its judgment
+  rules use only the declared source/capture phase flow in this skill.
+- Do not use unsupported source lifecycle shortcuts. There is no direct
+  source deletion or purge command in this workflow, and agents must not delete
+  `sources/`, `knowledge/`, `unapproved/`, `dist/`, or `.tmp` to simulate one.
+  If the user asks to retract, remove, or purge a source, stop and explain that
+  the current plugin exposes no approved gate for that operation.
+
+<reference>
+
+## Source Type Guide
+
+When the workspace has no source, do not ask with a raw placeholder command.
+Ask for a knowledge source in plain language and map it to the supported path:
+
+| User source | What to ask for | Current handling |
+|---|---|---|
+| Local code repo | knowledge boundary, stable source name, and local repo path | Register with `context source add repo <name> --local <path>`. CLI records git root + optional `subpath`; `sources/repo/<name>` becomes an ignored symlink to the chosen repo/subdir view. |
+| Local monorepo package/module | whether the source is the whole repo/subspace or one package/subdir; stable source name; chosen path | Register the chosen boundary as the repo source. If the user wants one package manual, register that package/subdir. If the user wants a unified subspace manual, register the subspace. Do not use `extractTs.include` as a package selector. |
+| Remote Git repo | knowledge boundary, stable source name, remote URL, pinned commit/ref, desired package/subdir, and permission to clone | CLI does not clone automatically. After explicit user approval, the agent may clone/checkout to an ignored local path, then register that local checkout. Cloned source content must not be committed. |
+| Local Markdown / document file or folder | document boundary, stable source name, local path, include glob if needed, and permission to read the source body | Register with `context source add file <name> --local <path>`, declare the matching capture phase, then hand off to material investigation and structure drafting after capture. Do not run capture before the user confirms read permission. |
+| Lark / Feishu document | document URL/token, intended collection, and permission to read remotely | Register with `context source add lark <name>` plus exactly one of `--url`, `--doc-token`, or `--wiki-token`; declare the matching capture phase, then hand off to material investigation and structure drafting after capture. Explain that capture writes a committed snapshot under `sources/lark/<name>/`, supports offline verify/fresh clone reproduction, and does not write credentials. Do not fetch through ad hoc scripts. |
+
+</reference>
+
+<procedures>
+
+### Step 1 — Register Only User-Chosen Sources
+
+If no source is registered, tell the user that the next step is adding a
+knowledge source. Use the user's language and explain that this is a boundary
+choice:
+
+```text
+You are choosing what one source means for this knowledge workspace.
+The source name becomes part of source refs and phase ids. Approved knowledge
+paths are derived later from collection, containment, and slug. NodeRef and
+ViewRef are identity fields, not path strings.
+
+If the source is one package:
+knowledge/codegraph/component-lib/...
+repo:component-lib#symbol:...
+capture:file:component-lib
+dist/component-lib-kb/
+
+If the source is one document source:
+knowledge/architecture/entity/example.md
+file:product-docs/getting-started.md#span:...
+align:file:product-docs:architecture
+dist/product-docs-kb/
+
+If the source is a parent monorepo/subspace namespace, later multi-module
+outputs can be shaped like:
+knowledge/codegraph/product-ui/component-web/...
+knowledge/codegraph/product-ui/component-lynx/...
+```
+
+If the source already points at one package/module root, the path uses the
+source name once. An extra module/package segment is only expected when the
+chosen source boundary intentionally covers multiple modules. In the current workflow, treat that
+parent source as a planning/inspection boundary first; choose a concrete
+package/subdirectory source before real extraction.
+
+When the user has already provided a path, describe the current interpretation
+before asking for the name:
+
+```text
+I am treating this path as the source boundary:
+<path>
+
+If this path is one package/module, the source name will be used directly:
+source refs such as repo:<source-name>#...
+
+If this path is a parent monorepo/subspace that contains multiple modules, the
+source name becomes the parent source namespace for grouped codegraph NodeRefs
+when extraction derives those refs:
+knowledge/codegraph/<source-name>/<module-name>/...
+
+For the current extraction flow, a multi-module parent source is used for
+inspection/planning first. Before reading code, we still need a concrete
+package/subdirectory boundary.
+```
+
+Then ask for one of:
+
+- local code repo or package path;
+- remote Git repo URL plus pinned commit/ref and target package/subdir;
+- local document path;
+- Lark/Feishu document URL.
+
+Do not ask "what is the source name?" as the first or only question. Ask what
+they want the knowledge source to cover, then propose a source name derived from
+that boundary and explain the path impact.
+
+Good user-facing wording:
+
+```text
+Next we need to add a knowledge source.
+
+If you only want a manual for the component package, choose that package
+directory as the source boundary, for example:
+name: component-lib
+path: /repo/packages/component-lib
+
+If you want one manual for the whole subspace, choose the subspace root:
+name: product-ui
+path: /repo/subspaces/product-ui
+
+The name is not just a label. It will appear in source refs such as
+repo:component-lib#... and in phase ids such as extract:component-lib:codegraph.
+Approved paths are derived from collection, containment, and slug. NodeRef and
+ViewRef are identity fields, not path strings.
+
+For a unified subspace package shape, a parent source name such as `product-ui`
+lets the output group child modules under that namespace:
+knowledge/codegraph/product-ui/component-web/...
+knowledge/codegraph/product-ui/component-lynx/...
+
+Current extraction can inspect a parent source, but it should extract from a
+confirmed single package/subdirectory source. If this path is a parent source,
+I will show the module tree first and ask which package(s) to use before
+reading code.
+```
+
+Mention the CLI command only as an implementation detail after the user chooses
+a supported repo source.
+
+For a local repo source, ask for:
+
+- source boundary and stable source name;
+- local repo or package/subdirectory path;
+- remote/ref only when not inferable or when the user wants an explicit pin.
+
+After the user provides the choice, run:
+
+```bash
+context source add repo <name> --local <repo-or-subdir>
+context source ensure
+```
+
+Add `--remote` / `--ref` only when the user gave explicit values.
+
+For a remote Git repo source, ask for permission before clone/checkout. If the
+user approves, clone to an ignored local path, checkout the requested commit,
+then register that local checkout with `context source add repo`. Do not commit
+cloned source content.
+
+For local Markdown/MDX document sources, after the user confirms the boundary, run:
+
+```bash
+context source add file <name> --local <file-or-folder>
+```
+
+Default file capture handles Markdown. For MDX documentation sites that use
+`_meta.json` route metadata, declare
+`captureFile({ source: source("<name>"), processor: mdxJsonDocs() })` in
+`src/index.ts`; included `_meta.json` files are route metadata, not body
+evidence. Use `--include` only when the approved boundary is narrower than the
+folder. Then explain that the next operation reads the approved document files
+and writes a committed snapshot under `sources/file/<name>/`. After the user
+confirms read permission, summarize the `src/index.ts` change or show an
+equivalent diff summary, and run the capture phase.
+Apply [skill-source-scope/references/capture-source.md](skill-source-scope/references/capture-source.md) for route
+selection, dependency recovery, output handling, and final reporting, using the
+current capture phase command returned by `context status`.
+
+For Lark/Feishu document sources, register the source but do not fetch content
+with ad hoc scripts. Explain which remote document or wiki token will be read,
+that the snapshot is written under `sources/lark/<name>/`, that committed
+snapshots enable offline verify and fresh-clone reproduction, that whether to
+add extra ignore rules is a business repository decision, and that access
+credentials are not written to the workspace. Use the declared capture/align
+flow only after the user confirms remote reading. After declaring
+`captureLark({ source: source("<name>") })`, summarize the `src/index.ts`
+change or show an equivalent diff summary.
+Apply [skill-source-scope/references/capture-source.md](skill-source-scope/references/capture-source.md) for route
+selection, dependency recovery, output handling, and final reporting, using the
+current capture phase command returned by `context status`.
+
+### Step 2 — Handle Monorepos
+
+If a registered source may contain multiple packages, run:
+
+```bash
+context source inspect <source-name> --format json
+```
+
+Present the detected module/package paths from that CLI output as a tree. Explain
+the choices without exposing internal API names first:
+
+- for the current executable flow, register one package/subdirectory as its
+  own source when the user wants a focused package manual;
+- if the user is designing a unified subspace knowledge base, keep the
+  parent source name as the namespace decision, but do not run extraction until
+  the concrete module extraction boundary is confirmed.
+
+Wait for the user to choose. If the user chooses `packages/button`, register it
+as a separate source such as:
+
+```bash
+context source add repo button --local <repo>/packages/button
+```
+
+Do not model a monorepo package choice as `include: ["packages/button/src/**"]`
+on the parent source.
+
+### Step 3 — Review Captured Document Summary
+
+When status is `captured-ready-to-investigate`, or after a capture phase
+completes, do not immediately create draft pages or compile actions. Present
+the capture summary first:
+
+- document count;
+- title tree, heading tree, or source span distribution from the CLI output;
+- available reading budget and evidence views;
+- snapshot path under `sources/file|lark/<source-name>/`;
+- the fact that approved pages are planned through
+  `unapproved/structure.yaml` before compile;
+- whether the source is local file/folder evidence or Lark/Feishu evidence.
+
+Then explain the next semantic gate in user-facing terms:
+
+```text
+The source body has been captured into a committed snapshot.
+
+Next we investigate the material and propose a structure draft:
+- which knowledge pages should exist;
+- which source spans support each section;
+- which relationships are supported by evidence;
+- what remains unresolved or weak.
+
+No approved Markdown is written at this point. Compile can start only after the
+structure is validated and you confirm it.
+```
+
+If the user wants to influence the shape before the Agent drafts it, ask a
+small semantic question with host-native multi-choice support when available:
+
+- Continue material investigation and propose a structure draft.
+- First add a reference structure or preference, such as expected domains,
+  page naming, or relationship focus.
+- Narrow or correct the captured source before planning.
+
+Do not use SDK factory names as user-facing option labels. If the user asks for
+one page per source document, represent that as a degenerate structure draft
+and still route through structure confirmation plus compile. Then follow
+`skill-prose-align.md`.
+
+### Step 4 — Declare Extract And Review
+
+Read the SDK guide before editing:
+
+```text
+node_modules/@c4a/context/docs/guides/agent-dialogue.md
+node_modules/@c4a/context/docs/guides/agent-guide.md
+node_modules/@c4a/context/docs/reference/project-api.md
+```
+
+Before editing, explain the proposed extraction in product terms. Use wording
+like:
+
+```text
+The source is ready and resolves to one package/module.
+
+Proposed extraction:
+- read TypeScript/TSX files under `src/`;
+- include exported symbols such as components, functions, types, and props;
+- create draft candidates for human review;
+- write no approved Markdown until the review payload is applied.
+
+This skips files outside `src/` and non-exported/internal helpers. If you want
+docs, tests, examples, or internal APIs included, say that before extraction.
+
+I will first generate a preview without writing candidates. The preview will
+show counts plus the planned `knowledge/` tree.
+```
+
+Only after the user confirms this product-level scope, declare the chosen source
+with `source("<name>")`, add the TypeScript extraction phase, and add the human
+review phase. Use `include` only for a file-level filter within the chosen
+source boundary. Mention the internal API names only in code-change summaries,
+or when the user asks for implementation details.
+
+### Step 5 — Show The Pre-extraction Preview
+
+Before real extraction, run the CLI no-write preview:
+
+```bash
+context run <extract-phase-id> --dry-run --format json
+```
+
+Show the user:
+
+- resolved source and module/package list;
+- file, symbol, and candidate estimate counts;
+- `knowledgeTree`;
+- several `knowledgePathExamples`.
+
+Explain that approved pages will land under paths derived from collection,
+containment, and slug; NodeRef/ViewRef are identity fields, not path strings:
+
+```text
+knowledge/<collection>/<containment>/<slug>.md
+```
+
+If source name, package name, module list, candidate estimate, or path shape is
+not what the user expects, stop and repair the source boundary or source name
+before extraction.
+
+For a single-module code source, a repeated path like
+`knowledge/codegraph/<source-name>/<package-name>/...` is usually a schema
+problem or a wrong source boundary. Stop before extraction if the preview shows
+that shape unexpectedly.
+
+Do not present this as a CLI option or as "Context default options" to the
+user. Present it as the actual proposed knowledge impact: code area read,
+exported-symbol policy, candidate count, and final path shape. The user-facing
+phrase is "preview without writing".
+
+### Step 6 — Run Extraction Only After Scope Is Clear
+
+If the user already confirmed the exact source/scope and the no-write preview
+matches it, run:
+
+```bash
+context run <extract-phase-id>
+```
+
+If the preview reports modules outside the confirmed source boundary, do not
+run extraction. Ask the user to choose the corrected source boundary.
+
+### Step 7 — Self-verify Checklist
+
+- [ ] Source choice came from the user, not inference. If not, return to
+  **Step 1**.
+- [ ] Monorepo package selection is represented as source boundary. If not,
+  return to **Step 2**.
+- [ ] Captured document summary was shown before structure/compile. If not, return to
+  **Step 3**.
+- [ ] No-write tree/path preview was shown before first real extraction. If not,
+  return to **Step 5**.
+
+</procedures>

package/plugins/cursor/.cursor-plugin/plugin.json

@@ -0,0 +1,29 @@
+{
+  "name": "context",
+  "displayName": "C4A Context",
+  "version": "0.6.0-alpha.1",
+  "description": "Maintain a project-local knowledge workspace through init and next-step agent guidance.",
+  "author": {
+    "name": "Context4AI",
+    "email": "support@context4ai.dev"
+  },
+  "homepage": "https://github.com/context4ai/c4a",
+  "repository": "https://github.com/context4ai/c4a",
+  "license": "MIT",
+  "logo": "assets/logo.svg",
+  "keywords": [
+    "context",
+    "knowledge",
+    "citations",
+    "agent-skills"
+  ],
+  "category": "developer-tools",
+  "tags": [
+    "knowledge",
+    "documentation",
+    "agent-skills",
+    "citations"
+  ],
+  "commands": "./commands/",
+  "skills": "./skills/"
+}

package/plugins/cursor/.generated

@@ -0,0 +1 @@
+generated by packages/context-cli/scripts/build-plugin.ts

package/plugins/cursor/AGENTS.md

@@ -0,0 +1,5 @@
+# Generated Cursor plugin build
+
+This directory is generated by `bun run build:plugin`.
+Do not edit files here directly.
+Edit `packages/context-cli/plugin/` and rerun the build instead.

package/plugins/cursor/README.md

@@ -0,0 +1,13 @@
+# Generated Cursor plugin build
+
+This directory is generated by `bun run build:plugin`.
+Do not edit files here directly.
+Edit `packages/context-cli/plugin/` and rerun the build instead.
+
+Install shape:
+
+- Marketplace/GitHub plugin shape: this directory is a plugin root with `.cursor-plugin/plugin.json`, `commands/`, and `skills/`.
+- User entries are under `commands/`; Cursor command files are prefixed as `context-*` to avoid global slash-command collisions.
+- Local plugin fallback: symlink or copy this directory to `~/.cursor/plugins/local/context/` only when Marketplace import is unavailable.
+
+Do not copy these files into `.cursor/skills/` as the main install path. Cursor Marketplace installs this plugin root directly.

package/plugins/cursor/assets/icon.svg

@@ -0,0 +1,3 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 758 296" fill="none">
+  <path fill-rule="evenodd" clip-rule="evenodd" d="M647.569 0.78043C613.4 3.48518 581.318 15.3269 533.021 43.0605C527.45 46.2597 498.781 61.8832 490.42 67.9156C464.4 83.1281 440.36 99.9754 407.462 125.999C399.965 131.93 392.626 137.658 391.153 138.729C389.68 139.8 382.798 145.128 375.858 150.569C368.919 156.01 358.504 163.98 352.714 168.281L343.516 175.006L348.516 179.006C351.553 181.229 358.164 187.09 362.516 190.006L370.516 196.006L379.016 190.006C384.498 185.597 392.279 178.726 395.782 175.811C399.285 172.896 411.776 162.857 414.201 160.847C416.626 158.838 420.318 155.949 427.144 150.29C445.631 134.963 481.502 112.007 494.26 102.533C581.313 47.1925 633.705 27.2029 682.312 46.6436C688.772 50.1275 692.158 52.8781 699.014 60.2106C706.594 68.3166 708.17 70.6632 712.305 79.9992C717.792 92.3865 720.263 102.609 721.288 117.182C723.104 142.96 716.794 171.243 703.236 198.108C693.06 218.269 684.3 229.708 671.088 242.211C628.153 272.315 597.665 274.481 543.801 261.017C510.873 246.43 487.481 230.006 448.016 193.506C444.204 190.241 440.144 186.014 439.516 186.006C438.281 185.991 399.991 214.634 399.516 216.006C399.235 216.815 404.057 219.412 409.016 222.506C410.702 223.559 412.975 225.335 416.516 227.006C433.391 238.059 468.991 255.632 482.516 262.006C485.929 263.614 490.402 264.707 492.545 265.749C509.884 274.195 533.276 282.099 555.644 287.07C564.55 289.049 601.674 289.814 609.103 288.171C612.031 287.523 616.387 286.554 618.782 286.017C633.747 282.66 656.745 272.897 670.289 264.153C708.746 239.325 740.493 194.104 753.016 146.317C764.533 102.359 755.681 60.2459 728.902 31.5909C712.119 13.6333 693.371 4.36271 667.389 1.17066C661.613 0.461953 656.637 -0.0628543 656.33 0.00607299C656.023 0.0750003 652.081 0.42386 647.569 0.78043ZM122.268 6.91848C100.692 8.62683 75.6783 17.7423 58.0176 30.3336C30.2119 50.158 12.2534 76.5887 3.92103 109.95C0.744084 122.668 -0.943192 149.281 0.550004 163.097C6.34545 216.709 38.9366 261.239 87.8925 282.436C108.528 291.37 128.098 295.45 152.658 295.937C173.489 296.35 191.779 294.037 213.531 288.238C254.082 277.427 282.658 266.098 328.68 231.976C341.818 222.235 344.259 221.314 342.05 219.506C337.696 215.941 316.951 199.525 316.016 199.506C315.451 199.495 312.641 202.192 307.128 205.872C245.084 247.275 198.239 258.453 151.476 252.979C138.261 251.432 123.184 247.836 114.645 244.194C82.5503 230.506 61.7452 207.016 52.8018 174.371C50.4952 165.952 50.3622 164.208 50.7059 146.886C51.0496 129.561 51.2517 127.827 53.8915 119.499C58.217 105.86 62.5516 96.3835 68.4271 87.7254C96.678 46.0924 144.857 34.898 199.322 57.3119C205.245 59.7489 221.144 67.3217 224.619 69.361C245.505 81.6138 248.559 83.5927 268.609 97.8683C286.178 110.375 299.632 125.4 316.016 139.031C330.379 150.982 332.229 144.373 335.6 144.44C337.306 142.561 337.353 141.225 335.571 139.031C334.554 137.779 334.892 138.21 331.041 133.458C307.893 104.899 285.92 82.0366 264.533 63.4627C232.185 35.3673 200.085 17.5822 168.343 10.1701C158.514 7.87465 132.964 6.07147 122.268 6.91848Z" fill="#ef6f2e"/>
+</svg>

package/plugins/cursor/assets/logo.svg

@@ -0,0 +1,3 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 758 296" fill="none">
+  <path fill-rule="evenodd" clip-rule="evenodd" d="M647.569 0.78043C613.4 3.48518 581.318 15.3269 533.021 43.0605C527.45 46.2597 498.781 61.8832 490.42 67.9156C464.4 83.1281 440.36 99.9754 407.462 125.999C399.965 131.93 392.626 137.658 391.153 138.729C389.68 139.8 382.798 145.128 375.858 150.569C368.919 156.01 358.504 163.98 352.714 168.281L343.516 175.006L348.516 179.006C351.553 181.229 358.164 187.09 362.516 190.006L370.516 196.006L379.016 190.006C384.498 185.597 392.279 178.726 395.782 175.811C399.285 172.896 411.776 162.857 414.201 160.847C416.626 158.838 420.318 155.949 427.144 150.29C445.631 134.963 481.502 112.007 494.26 102.533C581.313 47.1925 633.705 27.2029 682.312 46.6436C688.772 50.1275 692.158 52.8781 699.014 60.2106C706.594 68.3166 708.17 70.6632 712.305 79.9992C717.792 92.3865 720.263 102.609 721.288 117.182C723.104 142.96 716.794 171.243 703.236 198.108C693.06 218.269 684.3 229.708 671.088 242.211C628.153 272.315 597.665 274.481 543.801 261.017C510.873 246.43 487.481 230.006 448.016 193.506C444.204 190.241 440.144 186.014 439.516 186.006C438.281 185.991 399.991 214.634 399.516 216.006C399.235 216.815 404.057 219.412 409.016 222.506C410.702 223.559 412.975 225.335 416.516 227.006C433.391 238.059 468.991 255.632 482.516 262.006C485.929 263.614 490.402 264.707 492.545 265.749C509.884 274.195 533.276 282.099 555.644 287.07C564.55 289.049 601.674 289.814 609.103 288.171C612.031 287.523 616.387 286.554 618.782 286.017C633.747 282.66 656.745 272.897 670.289 264.153C708.746 239.325 740.493 194.104 753.016 146.317C764.533 102.359 755.681 60.2459 728.902 31.5909C712.119 13.6333 693.371 4.36271 667.389 1.17066C661.613 0.461953 656.637 -0.0628543 656.33 0.00607299C656.023 0.0750003 652.081 0.42386 647.569 0.78043ZM122.268 6.91848C100.692 8.62683 75.6783 17.7423 58.0176 30.3336C30.2119 50.158 12.2534 76.5887 3.92103 109.95C0.744084 122.668 -0.943192 149.281 0.550004 163.097C6.34545 216.709 38.9366 261.239 87.8925 282.436C108.528 291.37 128.098 295.45 152.658 295.937C173.489 296.35 191.779 294.037 213.531 288.238C254.082 277.427 282.658 266.098 328.68 231.976C341.818 222.235 344.259 221.314 342.05 219.506C337.696 215.941 316.951 199.525 316.016 199.506C315.451 199.495 312.641 202.192 307.128 205.872C245.084 247.275 198.239 258.453 151.476 252.979C138.261 251.432 123.184 247.836 114.645 244.194C82.5503 230.506 61.7452 207.016 52.8018 174.371C50.4952 165.952 50.3622 164.208 50.7059 146.886C51.0496 129.561 51.2517 127.827 53.8915 119.499C58.217 105.86 62.5516 96.3835 68.4271 87.7254C96.678 46.0924 144.857 34.898 199.322 57.3119C205.245 59.7489 221.144 67.3217 224.619 69.361C245.505 81.6138 248.559 83.5927 268.609 97.8683C286.178 110.375 299.632 125.4 316.016 139.031C330.379 150.982 332.229 144.373 335.6 144.44C337.306 142.561 337.353 141.225 335.571 139.031C334.554 137.779 334.892 138.21 331.041 133.458C307.893 104.899 285.92 82.0366 264.533 63.4627C232.185 35.3673 200.085 17.5822 168.343 10.1701C158.514 7.87465 132.964 6.07147 122.268 6.91848Z" fill="#ef6f2e"/>
+</svg>

package/plugins/cursor/commands/context-continue.md

@@ -0,0 +1,38 @@
+---
+description: "Inspect the Context workspace, decide the next useful action, and proceed."
+argument-hint: "[user intent]"
+allowed-tools: Bash(context:*), Bash(bun:*), Bash(cd *)
+---
+
+Continue the Context workflow from the current workspace state.
+
+---
+
+## Workflow
+
+Use this as the conversational entry for an existing Context workspace. There is
+no `context continue` CLI primitive; the command runs lower-level `context ...`
+commands only when the workspace state requires them.
+
+If the user is starting a new workspace or a new batch from a raw repository
+root, do not run `context status` first. Use the public Context init entry or
+`context init` to create the workspace, complete the init setup command, then
+return here from the initialized workspace.
+
+If `context status` reports `workspace-not-found` and points at a configured
+`context.workspaceDir`, do not keep working from the host repository root. Enter
+that workspace when it exists, or initialize it through the init workflow after
+confirming with the user.
+
+Language policy: explain, ask, confirm, and summarize in the user's current
+conversation language. Keep CLI commands, flags, paths, ids, status enum values,
+JSONL payload keys, `source_ref` values, and copied CLI output tokens unchanged.
+
+Use the procedure in `../skills/skill-continue-workflow/SKILL.md` end to end. It owns the
+status loop, safe mechanical next steps, source/scope gate, review gate, package
+gate, and final report rules.
+
+Do not infer repo sources, extraction scope, review decisions, or package output
+choices from surrounding files. Do not call source-repo operations such as
+clone, checkout, reset, fetch, install, build, or test without explicit user
+approval.

package/plugins/cursor/commands/context-init.md

@@ -0,0 +1,25 @@
+---
+description: "Initialize a Context knowledge workspace."
+argument-hint: "[project-dir] [--name <name>]"
+allowed-tools: Bash(context:*), Bash(bun:*), Bash(cd *)
+---
+
+Initialize a Context knowledge workspace.
+
+---
+
+## Workflow
+
+Initialize a Context workspace with the global CLI, then continue only through
+safe mechanical setup steps until the first human decision gate.
+
+Language policy: explain, ask, confirm, and summarize in the user's current
+conversation language. Keep CLI commands, flags, file paths, package names,
+enum values, payload keys, and copied CLI output tokens unchanged.
+
+Use the procedure in `../skills/skill-init-workspace/SKILL.md` end to end. It owns
+the `context init` invocation, dependency install follow-up, generated
+`AGENTS.md` handoff, status handoff, and stop conditions.
+
+Do not add extra project-local agent setup. Do not infer repo sources or
+extraction scope from the surrounding monorepo after setup.