kibi-cursor 0.2.0

package/hooks/hooks.json

@@ -0,0 +1,31 @@
+{
+  "version": 1,
+  "hooks": {
+    "sessionStart": [
+      {
+        "command": "node dist/hook-runner.js"
+      }
+    ],
+    "preToolUse": [
+      {
+        "command": "node dist/hook-runner.js"
+      }
+    ],
+    "postToolUse": [
+      {
+        "command": "node dist/hook-runner.js"
+      }
+    ],
+    "beforeReadFile": [
+      {
+        "command": "node dist/hook-runner.js"
+      }
+    ],
+    "stop": [
+      {
+        "command": "node dist/hook-runner.js",
+        "loop_limit": 1
+      }
+    ]
+  }
+}

package/mcp.json

@@ -0,0 +1,8 @@
+{
+  "mcpServers": {
+    "kibi": {
+      "command": "npx",
+      "args": ["--no-install", "kibi-mcp"]
+    }
+  }
+}

package/package.json

@@ -0,0 +1,58 @@
+{
+  "name": "kibi-cursor",
+  "version": "0.2.0",
+  "description": "Kibi Cursor plugin - thin adapter for Cursor MCP integration and editor hooks",
+  "type": "module",
+  "main": "dist/index.js",
+  "types": "./dist/index.d.ts",
+  "exports": {
+    ".": {
+      "types": "./dist/index.d.ts",
+      "import": "./dist/index.js",
+      "default": "./dist/index.js"
+    }
+  },
+  "files": [
+    ".cursor-plugin",
+    "mcp.json",
+    "hooks",
+    "skills",
+    "rules",
+    "commands",
+    "dist",
+    "CHANGELOG.md"
+  ],
+  "engines": {
+    "node": ">=18"
+  },
+  "license": "AGPL-3.0-or-later",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/Looted/kibi.git"
+  },
+  "publishConfig": {
+    "access": "public"
+  },
+  "scripts": {
+    "build": "tsc -p tsconfig.json && bun run scripts/copy-plugin-assets.ts",
+    "dev": "tsc -p tsconfig.json --watch",
+    "clean": "rm -rf dist",
+    "prepack": "npm run build"
+  },
+  "peerDependencies": {
+    "kibi-cli": ">=0.12.0 <1",
+    "kibi-mcp": ">=0.12.0 <1"
+  },
+  "peerDependenciesMeta": {
+    "kibi-cli": {
+      "optional": true
+    },
+    "kibi-mcp": {
+      "optional": true
+    }
+  },
+  "devDependencies": {
+    "@types/node": "latest",
+    "typescript": "^5.7.0"
+  }
+}

package/rules/kibi-traceability.mdc

@@ -0,0 +1,14 @@
+---
+description: Requirement traceability and symbol linking through Kibi
+globs:
+  - "**/*.{ts,tsx,js,jsx,py,go,rs,java}"
+alwaysApply: false
+---
+
+Before changing production code, discover linked requirements with `kb_search` and `kb_query(sourceFile=...)`.
+
+Preserve the canonical chain `REQ-* -> SCEN-* -> TEST-*` when modeling behavior.
+
+Prefer symbol manifest + `executable_for` for test/e2e code. Inline `// implements REQ-xxx` remains acceptable for quick code-only changes.
+
+Route durable domain facts to strict `fact` entities. Use `fact_kind: observation` or `meta` for bugs and workarounds, not `flag`.

package/rules/kibi-workflow.mdc

@@ -0,0 +1,19 @@
+---
+description: Kibi MCP discovery-first workflow and KB mutation discipline
+alwaysApply: true
+---
+
+Use Kibi via MCP tools only. Do not manually read or edit `.kb/` files.
+
+Discovery workflow:
+- Start with `kb_search` for broad discovery.
+- Follow with `kb_query` for exact entities, filters, and source-linked lookups.
+- Use `kb_status`, `kb_find_gaps`, `kb_coverage`, and `kb_graph` when reporting questions need them.
+
+Mutation workflow:
+- Query before mutate.
+- Create relationship endpoints before linking.
+- Use `kb_upsert` sequentially, then `kb_check`.
+- Use `kb_delete` only for intentional removals with dependency awareness.
+
+Completion must state KB freshness outcome: updated, no-impact with rationale, or deferred/failed.

package/skills/init-kibi/SKILL.md

@@ -0,0 +1,23 @@
+---
+name: init-kibi
+description: Bootstrap and model knowledge safely using approved Kibi MCP initialization and mutation workflow.
+---
+
+## Goal
+
+Set up or refresh Kibi knowledge for the current branch without manual filesystem edits.
+
+## MCP workflow
+
+- Run `kb_autopilot_generate` for suggested initial facts and claims.
+- Show the generated preview and get explicit approval before writes.
+- Use `kb_upsert` for reviewed entity creation or updates.
+- If cleanup is needed, use `kb_delete` only after checking dependencies.
+- Finish with `kb_check` to validate the branch snapshot.
+
+## Guidance
+
+- Keep mutation requests explicit and small.
+- Use source-linked entities where possible so future `kb_query` lookups can verify context.
+- Do not edit `.kb/**` files directly; all changes go through MCP calls.
+- Ask at most four bounded context questions, and only when repository evidence is insufficient.

package/skills/kibi-freshness/SKILL.md

@@ -0,0 +1,22 @@
+---
+name: kibi-freshness
+description: Check branch freshness and source linkage quality before decisions or risky writes.
+---
+
+## Goal
+
+Help agents decide whether KB context is current enough to support safe changes.
+
+## MCP workflow
+
+- Use `kb_status` first to confirm branch attachment and freshness state.
+- Use `kb_query` with `sourceFile`/text refs for source-linked discovery.
+- Re-run `kb_search` after sync gaps are detected.
+- If knowledge must change, update it with `kb_upsert` or `kb_delete` and finish with `kb_check`.
+
+## Guidance
+
+- Never proceed with broad changes when freshness is stale and unresolved.
+- If entities look stale, prefer refreshing context via MCP flows and then re-query.
+- Avoid direct `.kb` editing; use `kb_status` and other MCP checks instead.
+- Completion must state one freshness outcome: KB updated, no KB impact with rationale, or deferred/failed.

package/skills/kibi-traceability/SKILL.md

@@ -0,0 +1,22 @@
+---
+name: kibi-traceability
+description: Maintain requirement, scenario, and test traceability through Kibi MCP tools.
+---
+
+## Goal
+
+Validate and strengthen traceability before and after code changes.
+
+## MCP workflow
+
+- Locate requirements with `kb_search` and inspect exact details with `kb_query`.
+- Apply updates with `kb_upsert` for requirements, scenarios, tests, or facts.
+- Validate constraints and consistency with `kb_check`.
+
+## Guidance
+
+- Prefer source-linked relationships so symbols and files can be traced back cleanly.
+- Include `kb_query` and `kb_delete` only when explicit cleanups are required.
+- Never directly edit `.kb/**`; all modeling and cleanup goes through MCP tools.
+- Preserve the canonical chain `REQ-* -> SCEN-* -> TEST-*` when adding or changing requirements.
+- Production symbols should implement requirements; test symbols should remain executable evidence for tests.

package/skills/kibi-usage/SKILL.md

@@ -0,0 +1,23 @@
+---
+name: kibi-usage
+description: Use Kibi MCP discovery tools to find relevant requirements and context before editing code.
+---
+
+## Goal
+
+Help an agent discover existing knowledge in Kibi before making changes.
+
+## MCP workflow
+
+- Start with `kb_search` using domain keywords and requirement intent.
+- Move to `kb_query` for exact entity retrieval by `id` or `type`.
+- Use `kb_status` when context is stale or branch linkage is unclear.
+- Use curated reports only when the question needs them: `kb_find_gaps`, `kb_coverage`, or `kb_graph`.
+- Mutate only through `kb_upsert` or `kb_delete`, then validate with `kb_check`.
+
+## Guidance
+
+- Prefer source-linked lookups and traceability-aware retrieval via `kb_query` filters.
+- Never open or patch files under `.kb/` directly.
+- When unsure about scope, re-run `kb_search` with tighter terms, then validate with `kb_query`.
+- Report the KB outcome before completion: updated, no-impact with rationale, or deferred/failed.