claude-code-kit 0.55.0__tar.gz → 0.57.0__tar.gz

{claude_code_kit-0.55.0 → claude_code_kit-0.57.0}/.claude-plugin/marketplace.json

@@ -10,7 +10,7 @@
       "name": "claude-kit",
       "source": "./",
       "description": "Cookiecutter-style scaffolder for an autonomous Claude Code SDLC config (no app code, no Docker): install CLAUDE.md + .claude/ (rules, the profile's agents/skills, hooks, artifact templates) + optional .mcp.json, then run /sdlc to drive spec → review → build → test → security → ship through profile-aware quality gates, working memory, and a self-improving learnings loop.",
-      "version": "0.55.0",
+      "version": "0.57.0",
       "license": "MIT",
       "keywords": ["sdlc", "agents", "orchestration", "quality-gates", "workflow", "scaffold", "cookiecutter"]
     }

{claude_code_kit-0.55.0 → claude_code_kit-0.57.0}/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-kit",
-  "version": "0.55.0",
+  "version": "0.57.0",
   "description": "Cookiecutter-style scaffolder for an autonomous Claude Code SDLC config (no app code, no Docker). `claude-kit init` asks ordered questions and installs CLAUDE.md + .claude/ (rules, the profile's agents/skills, hooks, artifact templates) + optional .mcp.json; run /sdlc to drive spec → review → build → test → security → ship through profile-aware quality gates with working memory and a self-improving learnings loop.",
   "author": {
     "name": "Arjunsingh Yadav",

{claude_code_kit-0.55.0 → claude_code_kit-0.57.0}/CHANGELOG.md

@@ -4,6 +4,85 @@ All notable changes to claude-kit are documented here. The format follows
 [Keep a Changelog](https://keepachangelog.com/), and the project uses
 [semantic versioning](https://semver.org/).
 
+## [0.57.0] — 2026-07-03
+
+**Adoption & hardening — release automation, honest docs, and a credibility pass.** No new
+capability and no change to the core promise: configuration-only SDLC scaffolding for Claude Code, no
+application code, no Docker, stack-agnostic core, catalog-driven. This release closes the gap between
+"published to PyPI" and "tagged/released on GitHub," adds an honest release + road-to-1.0 policy, audits
+the skill surface, and tightens the README so every claim is verifiable. **0 new agents/skills/rules;
+`catalog.resolve()` and `catalog/*.yaml` untouched.**
+
+### Added
+
+- **Automated git tag + GitHub Release on publish.** `publish.yml` gains a `github-release` job that,
+  after a successful PyPI publish, creates the `vX.Y.Z` tag and a GitHub Release whose body is that
+  version's `CHANGELOG.md` section. Idempotent (a re-run over an already-released version is a no-op) and
+  downstream of `publish` (a Release is only cut once the wheel is actually on PyPI).
+- **`scripts/backfill-releases.sh` (`--dry-run`).** One-off, idempotent backfill that retroactively
+  creates the tag + Release for past versions that shipped via merge-to-main before the automation
+  existed. Anchors each tag to the commit that introduced that version into `pyproject.toml` (git
+  pickaxe), and skips — with a warning — any version whose release commit can't be located.
+- **[`docs/RELEASE-POLICY.md`](docs/RELEASE-POLICY.md).** Versioning, latest-only support, the
+  five-place version bump + CHANGELOG, and the publish/tag/Release automation, in one place.
+- **[`docs/launch/road-to-1.0.md`](docs/launch/road-to-1.0.md).** An honest, verifiable list of what
+  stands between the current `4 - Beta` and 1.0 (stack coverage, enforcement honesty, hook portability,
+  evidence base, export fidelity, API stability). The Development Status classifier stays `4 - Beta`.
+- **[`docs/skill-audit.md`](docs/skill-audit.md).** Core-vs-collection classification, the per-profile
+  install footprint (agents/skills/rules + an on-disk token estimate), and the finding that the
+  `enterprise` profile's `skills: all` installs every collection skill regardless of the chosen stack.
+  Documents and recommends; changes no profile (skills load on demand, so this is selection, not
+  always-resident context).
+- **Launch-prep assets under `docs/launch/`** (owner checklists, not code): `github-about.md`,
+  `demo-script.md`, `directory-submission.md`, `awesome-prs.md`, `posts.md`, and `seed-issues.md`.
+
+### Changed
+
+- **README credibility pass.** Strengthened the anti-sycophancy / evidence framing and added a
+  "What loads into your context" per-profile table (agents/skills/rules), so the footprint is explicit
+  before install. Counts remain pinned by `scripts/check_docs_consistency.py`.
+
+### Not adopted (deliberately)
+
+- **No version-parity CI addition** — `scripts/check_docs_consistency.py::check_versions()` already
+  enforces parity across the four manifests, `SECURITY.md`, and the latest CHANGELOG heading.
+- **No `profiles.yaml` change** for the `skills: all` finding — flagged and recommended in the audit;
+  any opt-in must stay a catalog/config change with no `resolve()` branching (golden rule #6).
+- **Development Status stays `4 - Beta`** — the classifier is not flipped until the road-to-1.0 gaps
+  are met.
+
+## [0.56.0] — 2026-07-01
+
+**`export` command — carry the config to Cursor / VS Code / GitHub Copilot.** A teammate who works in
+an editor that isn't Claude Code can't consume `.claude/` or run the gated `/sdlc` pipeline. `claude-kit
+export` projects the **same resolved plan** into the formats those single-agent editors read natively,
+so claude-kit's standards travel even where the pipeline can't. No change to the core promise —
+configuration-only SDLC scaffolding for Claude Code, no application code, no Docker, stack-agnostic
+core, catalog-driven. **0 new agents/skills**; `catalog.resolve()` untouched (a pure projection of the
+existing plan).
+
+### Added
+
+- **`claude-kit export [path] -t cursor|agents|copilot`.** Re-targets the resolved `ResolvedPlan` to:
+  - **`cursor`** — `.cursor/rules/*.mdc` (one per rule, with YAML frontmatter derived generically from
+    each rule: `description` = H1 + lead sentence; `alwaysApply: false` for the on-demand rule set;
+    overlay rules get `globs` keyed on the plan's *language/database* values — `typescript` →
+    `**/*.ts,**/*.tsx`, `python` → `**/*.py`, `postgres` → `**/*.sql`, …), an always-applied
+    `000-project.mdc` charter, and `.cursor/mcp.json` (the `type` discriminator stripped for Cursor).
+  - **`agents`** — a root `AGENTS.md` (charter + single-agent SDLC checklist + rule index + fidelity
+    note); read by both Cursor and Copilot.
+  - **`copilot`** — `.github/copilot-instructions.md` (the same synthesized document as `agents`).
+- **Honest fidelity, everywhere.** Rules, the project charter, and MCP port cleanly; the **enforced**
+  quality gates, independent reviewer subagents, and automated defect loop are Claude-Code-only and are
+  exported as a single-agent **self-check checklist**. Every exported document states this explicitly
+  (a "What ports from Claude Code — and what doesn't" note + the workflow guide's opening).
+- **Flags mirror `init`:** `--dry-run` (report, write nothing), `--force` (refresh in place; otherwise
+  a hand-edited file is preserved and the new version lands beside it as a `.claude-kit` sidecar),
+  `--config`/`--defaults` (resolve a fresh selection instead of the project's installed one), `--json`.
+- **New payload template** `templates/export/sdlc-workflow-guide.md.tmpl` (stack-agnostic; renders with
+  the project's real test/lint/build commands), plus `tests/test_export.py` and
+  [`docs/cursor-export.md`](docs/cursor-export.md) (usage + the full fidelity matrix).
+
 ## [0.55.0] — 2026-07-01
 
 **React overlay rules split under Claude Code's 40k memory limit.** Two React design-system overlay

{claude_code_kit-0.55.0 → claude_code_kit-0.57.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: claude-code-kit
-Version: 0.55.0
+Version: 0.57.0
 Summary: Cookiecutter-style scaffolder for an autonomous Claude Code SDLC configuration (no app code, no Docker). Asks ordered questions and installs CLAUDE.md + .claude/ (rules, the chosen profile's agents/skills, hooks, artifact templates) + optional .mcp.json; run /sdlc to drive spec → review → build → test → security → ship through profile-aware quality gates, working memory, and a self-improving learnings loop.
 Project-URL: Homepage, https://github.com/ajyadav013/claude-kit
 Project-URL: Repository, https://github.com/ajyadav013/claude-kit
@@ -43,6 +43,12 @@ assumed, or partial-output "it works" is itself an auto-Critical finding — so
 checks actually ran. A Cookiecutter-style scaffolder, installed as **configuration only — no
 application code, no Docker.**
 
+<!-- DEMO PLACEHOLDER — a 60–90s terminal capture of a gated `/sdlc` run belongs here once recorded.
+     Shot list, timing, and which real assets to show: docs/launch/demo-script.md.
+     The recording replays the genuine run already in examples/real-run/ (the devils-advocate catching a
+     Medium bug a unanimous review missed, and the gate refusing to advance until it was fixed).
+     Until the GIF exists, that folder IS the evidence — linked from "How it works" and "The pipeline" below. -->
+
 [![PyPI](https://img.shields.io/pypi/v/claude-code-kit.svg)](https://pypi.org/project/claude-code-kit/)
 [![Python](https://img.shields.io/pypi/pyversions/claude-code-kit.svg)](https://pypi.org/project/claude-code-kit/)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
@@ -236,6 +242,36 @@ README.claude-sdlc.md
 
 ---
 
+## Use in Cursor / VS Code / Copilot (export)
+
+A teammate who works in **Cursor**, **VS Code**, or **GitHub Copilot** can't consume `.claude/` or run
+the gated multi-agent `/sdlc` pipeline — those editors drive their own single agent. `claude-kit
+export` projects the **same resolved plan** into the formats those agents read natively, so the
+standards travel even when the pipeline can't:
+
+```bash
+claude-kit export .                              # → .cursor/ (default target)
+claude-kit export . -t cursor -t agents -t copilot   # all three at once
+claude-kit export . --dry-run                    # preview; writes nothing
+```
+
+| Target | Emits | What lands |
+|---|---|---|
+| `cursor` | `.cursor/rules/*.mdc` + `.cursor/mcp.json` | The full rule set (one on-demand `.mdc` each, overlays auto-attach by file glob), an always-applied `000-project.mdc` charter, and your MCP servers |
+| `agents` | `AGENTS.md` (repo root) | Project charter + single-agent SDLC checklist + rule index (read by Cursor **and** Copilot) |
+| `copilot` | `.github/copilot-instructions.md` | The same synthesized document as `agents` |
+
+**Fidelity is honest.** Rules, the project charter, and MCP servers port cleanly. The **enforced**
+quality gates, independent reviewer subagents, and automated defect loop are Claude-Code-only — the
+export carries the SDLC workflow as a **single-agent self-check checklist**, not enforced gates. Every
+exported document says so. Exports are regenerable projections: `--force` refreshes them in place, and
+without it a hand-edited file is preserved (the new version drops beside it as a `.claude-kit` sidecar).
+
+See **[docs/cursor-export.md](docs/cursor-export.md)** for the full fidelity matrix and the `.mdc`
+frontmatter mapping.
+
+---
+
 ## Feature details
 
 Each area from the [Features](#features) table, expanded — the README stays short; open only what you
@@ -333,6 +369,26 @@ need.
   compliance, production-data) install only in organization scope (see
   [`docs/org-capabilities.md`](docs/org-capabilities.md)).
 
+**What loads into your context** — the profile you pick decides how much lands in `.claude/`. Measured
+on a React + FastAPI + PostgreSQL project, individual scope:
+
+| Profile | Agents | Skills | Rules |
+|---------|-------:|-------:|------:|
+| `lean` | 8 | 14 | 35 |
+| `standard` (default) | 26 | 42 | 35 |
+| `enterprise` | 31 | 104 | 35 |
+
+- **Rules are profile-independent** — every profile installs the same 24 core rules + the selected
+  stack's overlays (11 for this stack = 35); rigor changes the *agents and gates*, not the rule set.
+- **Skills activate on demand** — they are installed and available, then pulled into context by task
+  relevance, not all held resident at once. The count is what's on disk, not a fixed context tax.
+- **Counts include stack overlays** — the numbers above already fold in the chosen stack (e.g. the
+  Postgres overlay adds 3 agents, which is why `enterprise` shows 31 against a 28-agent core roster). A
+  different stack shifts them by a few.
+- **`enterprise` installs the whole skill collection** (`skills: all`) — all 104 skills, including
+  collection skills for stacks you didn't select. That's disk/selection footprint, not always-resident
+  context, but if you want a tighter install prefer `standard`. See [`docs/skill-audit.md`](docs/skill-audit.md).
+
 </details>
 
 <details>
@@ -724,6 +780,7 @@ everything available.
 | `validate [path] [--strict]` | Structurally validate an installed config; `--strict` adds hooks→script, `.mcp.json`-shape, snapshot, and catalog-integrity checks |
 | `doctor [path] [--mcp]` | Strict validate + environment/health checks; `--mcp` checks MCP commands, `${ENV}` vars, and lockfile drift |
 | `diff [path]` | Preview what an `upgrade` would change (no writes) |
+| `export [path] -t cursor\|agents\|copilot [--force] [--dry-run] [--json]` | Project the config into Cursor (`.cursor/`), a root `AGENTS.md`, or GitHub Copilot (`.github/copilot-instructions.md`) for editors that aren't Claude Code |
 | `upgrade [path] [--force]` | Refresh kit/overlay files; protect your edits; prune orphans |
 | `pipeline validate · status · close-gate · abort` | Inspect/mutate the `/sdlc` state files (gate/lane/evidence coherence); **does not run** the pipeline |
 | `list-options` | List available frontend/backend/database/profile/MCP options |

{claude_code_kit-0.55.0 → claude_code_kit-0.57.0}/README.md

@@ -10,6 +10,12 @@ assumed, or partial-output "it works" is itself an auto-Critical finding — so
 checks actually ran. A Cookiecutter-style scaffolder, installed as **configuration only — no
 application code, no Docker.**
 
+<!-- DEMO PLACEHOLDER — a 60–90s terminal capture of a gated `/sdlc` run belongs here once recorded.
+     Shot list, timing, and which real assets to show: docs/launch/demo-script.md.
+     The recording replays the genuine run already in examples/real-run/ (the devils-advocate catching a
+     Medium bug a unanimous review missed, and the gate refusing to advance until it was fixed).
+     Until the GIF exists, that folder IS the evidence — linked from "How it works" and "The pipeline" below. -->
+
 [![PyPI](https://img.shields.io/pypi/v/claude-code-kit.svg)](https://pypi.org/project/claude-code-kit/)
 [![Python](https://img.shields.io/pypi/pyversions/claude-code-kit.svg)](https://pypi.org/project/claude-code-kit/)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
@@ -203,6 +209,36 @@ README.claude-sdlc.md
 
 ---
 
+## Use in Cursor / VS Code / Copilot (export)
+
+A teammate who works in **Cursor**, **VS Code**, or **GitHub Copilot** can't consume `.claude/` or run
+the gated multi-agent `/sdlc` pipeline — those editors drive their own single agent. `claude-kit
+export` projects the **same resolved plan** into the formats those agents read natively, so the
+standards travel even when the pipeline can't:
+
+```bash
+claude-kit export .                              # → .cursor/ (default target)
+claude-kit export . -t cursor -t agents -t copilot   # all three at once
+claude-kit export . --dry-run                    # preview; writes nothing
+```
+
+| Target | Emits | What lands |
+|---|---|---|
+| `cursor` | `.cursor/rules/*.mdc` + `.cursor/mcp.json` | The full rule set (one on-demand `.mdc` each, overlays auto-attach by file glob), an always-applied `000-project.mdc` charter, and your MCP servers |
+| `agents` | `AGENTS.md` (repo root) | Project charter + single-agent SDLC checklist + rule index (read by Cursor **and** Copilot) |
+| `copilot` | `.github/copilot-instructions.md` | The same synthesized document as `agents` |
+
+**Fidelity is honest.** Rules, the project charter, and MCP servers port cleanly. The **enforced**
+quality gates, independent reviewer subagents, and automated defect loop are Claude-Code-only — the
+export carries the SDLC workflow as a **single-agent self-check checklist**, not enforced gates. Every
+exported document says so. Exports are regenerable projections: `--force` refreshes them in place, and
+without it a hand-edited file is preserved (the new version drops beside it as a `.claude-kit` sidecar).
+
+See **[docs/cursor-export.md](docs/cursor-export.md)** for the full fidelity matrix and the `.mdc`
+frontmatter mapping.
+
+---
+
 ## Feature details
 
 Each area from the [Features](#features) table, expanded — the README stays short; open only what you
@@ -300,6 +336,26 @@ need.
   compliance, production-data) install only in organization scope (see
   [`docs/org-capabilities.md`](docs/org-capabilities.md)).
 
+**What loads into your context** — the profile you pick decides how much lands in `.claude/`. Measured
+on a React + FastAPI + PostgreSQL project, individual scope:
+
+| Profile | Agents | Skills | Rules |
+|---------|-------:|-------:|------:|
+| `lean` | 8 | 14 | 35 |
+| `standard` (default) | 26 | 42 | 35 |
+| `enterprise` | 31 | 104 | 35 |
+
+- **Rules are profile-independent** — every profile installs the same 24 core rules + the selected
+  stack's overlays (11 for this stack = 35); rigor changes the *agents and gates*, not the rule set.
+- **Skills activate on demand** — they are installed and available, then pulled into context by task
+  relevance, not all held resident at once. The count is what's on disk, not a fixed context tax.
+- **Counts include stack overlays** — the numbers above already fold in the chosen stack (e.g. the
+  Postgres overlay adds 3 agents, which is why `enterprise` shows 31 against a 28-agent core roster). A
+  different stack shifts them by a few.
+- **`enterprise` installs the whole skill collection** (`skills: all`) — all 104 skills, including
+  collection skills for stacks you didn't select. That's disk/selection footprint, not always-resident
+  context, but if you want a tighter install prefer `standard`. See [`docs/skill-audit.md`](docs/skill-audit.md).
+
 </details>
 
 <details>
@@ -691,6 +747,7 @@ everything available.
 | `validate [path] [--strict]` | Structurally validate an installed config; `--strict` adds hooks→script, `.mcp.json`-shape, snapshot, and catalog-integrity checks |
 | `doctor [path] [--mcp]` | Strict validate + environment/health checks; `--mcp` checks MCP commands, `${ENV}` vars, and lockfile drift |
 | `diff [path]` | Preview what an `upgrade` would change (no writes) |
+| `export [path] -t cursor\|agents\|copilot [--force] [--dry-run] [--json]` | Project the config into Cursor (`.cursor/`), a root `AGENTS.md`, or GitHub Copilot (`.github/copilot-instructions.md`) for editors that aren't Claude Code |
 | `upgrade [path] [--force]` | Refresh kit/overlay files; protect your edits; prune orphans |
 | `pipeline validate · status · close-gate · abort` | Inspect/mutate the `/sdlc` state files (gate/lane/evidence coherence); **does not run** the pipeline |
 | `list-options` | List available frontend/backend/database/profile/MCP options |

claude_code_kit-0.57.0/docs/RELEASE-POLICY.md

@@ -0,0 +1,92 @@
+# Release Policy
+
+This document describes claude-kit's versioning, release, and support policy.
+
+## Versioning
+
+claude-kit follows [Semantic Versioning](https://semver.org/) (SemVer).
+
+**Pre-1.0 stability:** The project is currently pre-1.0 (Development Status :: 4 - Beta). During
+the 0.x phase, minor version increments (e.g., 0.56.0 → 0.57.0) may introduce behavior changes or
+breaking changes. Breaking changes are always called out explicitly in the CHANGELOG.
+
+Once the project reaches 1.0.0, the standard SemVer contract will apply: breaking changes only in
+major versions, backwards-compatible features in minor versions, and fixes in patch versions.
+
+## Supported Versions
+
+**Only the latest released version receives fixes.** There is no long-term-support (LTS) branch or
+backport policy. When a new version is released, the previous version is no longer supported.
+
+This policy mirrors the project's [SECURITY.md](../SECURITY.md) stance: security fixes are
+published only for the latest release.
+
+## What Is in a Release
+
+Every release includes:
+
+- A version bump in **all five** of the following files (enforced by CI):
+  - `pyproject.toml`
+  - `.claude-plugin/plugin.json`
+  - `.claude-plugin/marketplace.json` (the marketplace entry)
+  - `src/claude_kit/__init__.py` (`__version__`)
+  - `SECURITY.md` (the "Supported Versions" table)
+- A new section in `CHANGELOG.md` following [Keep a Changelog](https://keepachangelog.com/)
+  format, with a dated heading matching the new version
+- A "Not adopted (deliberately)" note in the CHANGELOG entry, documenting what was reviewed but
+  intentionally excluded from the kit
+
+A CI check (`scripts/check_docs_consistency.py`) enforces version parity across all five locations
+and verifies that the latest CHANGELOG heading matches the current version.
+
+## Release Process
+
+1. **Bump the version** in all five files listed above.
+2. **Update CHANGELOG.md** with a new section for the release, including the date and the
+   "Not adopted" note.
+3. **Merge to main.** Once the pull request is merged:
+   - `.github/workflows/publish.yml` automatically checks whether the version in `pyproject.toml`
+     is newer than the latest version on PyPI.
+   - If the version is new, the workflow publishes the package to PyPI and creates:
+     - A git tag `vX.Y.Z`
+     - A GitHub Release whose body is the new version's CHANGELOG section
+
+No manual PyPI upload or tag creation is required. As of version 0.57.0, the workflow handles both
+PyPI publishing and GitHub Release creation in a single run.
+
+## Publishing and Provenance
+
+Releases are published to [PyPI](https://pypi.org/project/claude-code-kit/) via **OIDC Trusted
+Publishing** (no long-lived token) with **PEP 740 build attestations** for provenance verification.
+
+The workflow is version-gated: it only publishes when the version in `pyproject.toml` is newer than
+the latest version on PyPI.
+
+## Pre-1.0 Stability Caveat
+
+Because the project is pre-1.0, minor version updates may include:
+
+- Changes to the SDLC agent protocols or quality gates
+- Modifications to the catalog schema or resolution behavior
+- Removal or renaming of skills, agents, or rules
+- Breaking changes to the CLI interface
+
+Always review the CHANGELOG before upgrading. Breaking changes are explicitly called out.
+
+## Release Cadence
+
+Releases are shipped **when ready**. There is no fixed calendar schedule.
+
+Many minor releases are driven by **reuse-first adoption reviews** — surveys of external projects
+or organizations (e.g., Alibaba, Microsoft, Google) that result in new overlay rules, skills, or
+agents being added to the kit.
+
+## Reporting Issues
+
+- **Feature requests and regressions:** Open a [GitHub issue](https://github.com/ajyadav013/claude-kit/issues).
+- **Security vulnerabilities:** Follow the [SECURITY.md](../SECURITY.md) policy (private reporting via GitHub).
+
+---
+
+**License:** MIT © Arjunsingh Yadav  
+**Repository:** [github.com/ajyadav013/claude-kit](https://github.com/ajyadav013/claude-kit)

{claude_code_kit-0.55.0 → claude_code_kit-0.57.0}/docs/architecture.md

@@ -75,6 +75,17 @@ flowchart TB
 Adding a framework/database/profile/MCP server is a **catalog edit + a `templates/stacks/` folder** —
 never a change to `resolve()`.
 
+### Same plan, second target: `export` (for non-Claude-Code editors)
+
+The `ResolvedPlan` is the reuse seam. `claude-kit export` (`src/claude_kit/export.py`) takes the **same**
+plan and, instead of `scaffold.install_sdlc()` writing `.claude/`, projects it into the formats a
+single-agent editor reads natively — `.cursor/rules/*.mdc` + `.cursor/mcp.json` (Cursor), a root
+`AGENTS.md`, or `.github/copilot-instructions.md` (Copilot). It is a pure projection: it adds no stack
+knowledge, and `catalog.resolve()` gains no branches (golden rules #1 and #6). Fidelity is asymmetric
+and stated in every exported file — rules, the charter, and MCP port cleanly, while the *enforced*
+gates and reviewer subagents become single-agent guidance. See
+[cursor-export.md](cursor-export.md) for the full mapping.
+
 ---
 
 ## 3. The SDLC pipeline (run)

claude_code_kit-0.57.0/docs/cursor-export.md

@@ -0,0 +1,94 @@
+# Exporting to Cursor / VS Code / GitHub Copilot
+
+claude-kit's home is **Claude Code**, where it installs a `.claude/` configuration and runs a gated,
+multi-agent `/sdlc` pipeline. A teammate working in **Cursor**, **VS Code**, or **GitHub Copilot**
+uses that editor's *own* single agent — which can't read `.claude/` or run the pipeline. `claude-kit
+export` bridges the gap by projecting the **same resolved plan** into the formats those agents read
+natively.
+
+It is a **projection**, not a second source of truth: the exporter re-targets the exact `ResolvedPlan`
+that `init` installs (`catalog.resolve()` is untouched, no new stack knowledge). Re-run it any time to
+regenerate; it writes **configuration only** — no application code, no Docker.
+
+## Usage
+
+```bash
+claude-kit export .                                   # default target: cursor
+claude-kit export . -t cursor -t agents -t copilot    # all three
+claude-kit export . --dry-run                         # preview; write nothing
+claude-kit export . --force                            # refresh existing files in place
+claude-kit export . -t agents --json                  # machine-readable file list
+```
+
+By default `export` resolves from the project's **installed selection**
+(`.claude/config/init-options.json`), so the export matches what was scaffolded. Pass `--config FILE`
+or `--defaults` to resolve a fresh selection instead — useful for a standalone export into a project
+that never ran `init`.
+
+**Conflict-safe writes.** Exports are regenerable, so `--force` refreshes them in place. Without
+`--force`, an existing (possibly hand-edited) file is preserved and the new version is written beside it
+as a `<name>.claude-kit` sidecar — the same non-destructive convention the installer uses.
+
+## What each target emits
+
+| Target | Files | Contents |
+|---|---|---|
+| `cursor` | `.cursor/rules/000-project.mdc` | The project **charter** + single-agent SDLC workflow + fidelity note. `alwaysApply: true` — always in context. |
+| | `.cursor/rules/<rule>.mdc` (one per rule) | Every core rule and every stack overlay, `alwaysApply: false` (agent pulls on demand by `description`); overlays also carry `globs` to auto-attach on matching files. |
+| | `.cursor/mcp.json` | Your selected MCP servers (omitted when none are selected). |
+| `agents` | `AGENTS.md` (repo root) | Charter + workflow + a **rule index** (one line per rule) + the fidelity note. Read by both Cursor and Copilot. |
+| `copilot` | `.github/copilot-instructions.md` | The same synthesized document as `agents`. |
+
+## `.mdc` frontmatter derivation
+
+Each Cursor rule file gets YAML frontmatter derived generically from the rule's own content — no
+per-stack branching:
+
+- **`description`** — the rule's H1 heading plus its first lead sentence (falling back to a humanized
+  filename), trimmed to ~200 characters. Cursor uses this to decide when to pull an on-demand rule.
+- **`alwaysApply`** — `false` for the whole rule set (mirroring Claude Code's on-demand rule loading);
+  `true` only for the synthesized `000-project.mdc` charter.
+- **`globs`** — attached to **overlay** rules only, chosen from the overlay's lane and the plan's
+  *language/database* values (not framework names):
+
+  | Lane | Source value | Example glob |
+  |---|---|---|
+  | frontend | `frontend_language` | `typescript` → `**/*.ts,**/*.tsx` |
+  | backend | `backend_language` | `python` → `**/*.py`, `go` → `**/*.go` |
+  | database | `database` | `postgres` → `**/*.sql` |
+
+  A store with no reliable file signal (e.g. a document database) gets **no** glob and loads by
+  `description` instead. Core rules never get globs.
+
+Values are JSON-quoted so the frontmatter is always valid YAML — an unquoted glob such as
+`**/*.{ts,tsx}` would be misparsed as a YAML flow mapping.
+
+## MCP projection
+
+Cursor's `.cursor/mcp.json` uses a top-level `mcpServers` map and infers transport from the keys
+present — stdio servers use `command`/`args`/`env`, remote servers use `url`/`headers`. claude-kit's
+internal `type` discriminator is **dropped**; every other key passes through verbatim.
+
+## Fidelity: what ports, and what doesn't
+
+| Capability | Claude Code | Exported (Cursor / AGENTS.md / Copilot) |
+|---|---|---|
+| Engineering rules + stack/design-system overlays | ✅ enforced/on-demand | ✅ full text (`.mdc`) or index (AGENTS.md) |
+| Project charter (stack, commands, lanes) | ✅ | ✅ |
+| MCP servers | ✅ (`.mcp.json`) | ✅ Cursor (`.cursor/mcp.json`); not applicable to AGENTS.md/Copilot |
+| SDLC phases | ✅ **enforced quality gates** | ⚠️ single-agent **self-check checklist** (guidance) |
+| Independent reviewer subagents | ✅ separate agents | ❌ one agent plays every role |
+| Security scan (parallel sub-scanners) | ✅ | ⚠️ a security self-check step in the checklist |
+| Automated defect loop (blocks on unproven verdict) | ✅ | ⚠️ described as discipline; nothing blocks |
+
+The enforced gates, reviewer subagents, and automated defect loop depend on Claude Code's multi-agent
+runtime and **cannot** be reproduced under a single-agent editor. The export is honest about this: the
+charter carries a "What ports from Claude Code — and what doesn't" note, and the workflow guide opens
+by stating it is a self-check checklist, not enforced gates.
+
+## Out of scope (for now)
+
+- **Cursor hooks** (`.cursor/hooks.json`) and **commands/skills** export — a different event/format
+  model; noted as future work.
+- **Drift tracking** of exported files in the `init-options.json` ownership manifest — exports are
+  regenerable projections (`export --force` refreshes), so they are intentionally not tracked.

claude_code_kit-0.57.0/docs/launch/awesome-prs.md

@@ -0,0 +1,118 @@
+# Awesome List Submission Guide
+
+This document provides ready-to-submit entries for relevant awesome lists. All submissions should be made by the project owner following each list's contribution guidelines.
+
+## Priority Order
+
+1. **hesreallyhim/awesome-claude-code** (~47.8k stars, active) — highest visibility
+2. **VoltAgent/awesome-claude-code-subagents** (~22.7k stars, active) — relevant category
+3. **ComposioHQ/awesome-claude-plugins** (stale, ~2 months no activity) — optional, deprioritized
+
+---
+
+## hesreallyhim/awesome-claude-code
+
+**Target:** [hesreallyhim/awesome-claude-code](https://github.com/hesreallyhim/awesome-claude-code) (~47.8k stars, active)
+
+**Method:** Submit via **ISSUE FORM** (NOT a pull request)
+- Path: `issues/new?template=recommend-resource.yml`
+- Full URL: https://github.com/hesreallyhim/awesome-claude-code/issues/new?template=recommend-resource.yml
+
+**Category:** Infrastructure & DevOps
+
+**Ready Copy:**
+
+*Description (204 characters, within 10-500 constraint):*
+```
+An autonomous, stack-agnostic SDLC for Claude Code, shipped as a plugin and a pip scaffolder, that enforces quality gates and independent reviewer agents including an anti-sycophancy devils-advocate gate.
+```
+
+*Resource URL:*
+```
+https://github.com/ajyadav013/claude-kit
+```
+
+**Etiquette:**
+- Use the issue form fields exactly as provided
+- No emoji in description
+- Non-promotional language (already honored above)
+- Wait for maintainer review before follow-up
+
+---
+
+## VoltAgent/awesome-claude-code-subagents
+
+**Target:** [VoltAgent/awesome-claude-code-subagents](https://github.com/VoltAgent/awesome-claude-code-subagents) (~22.7k stars, active)
+
+**Method:** Submit a **PULL REQUEST**
+- File to edit: `categories/09-meta-orchestration/README.md`
+- Add one bullet line in the appropriate section
+
+**Category:** Meta Orchestration
+
+**Ready Copy:**
+
+*One-line bullet (vendor-neutral):*
+```markdown
+- [**claude-kit**](https://github.com/ajyadav013/claude-kit) - Autonomous stack-agnostic SDLC for Claude Code (plugin + pip scaffolder) with quality gates and independent reviewer agents, including an anti-sycophancy devils-advocate gate.
+```
+
+**Etiquette:**
+- Follow the repository's CONTRIBUTING.md guidelines
+- One entry per PR
+- Ensure the bullet follows the existing format in the category
+- Provide a clear PR title: "Add claude-kit to Meta Orchestration"
+- Keep the description factual and non-promotional
+
+---
+
+## ComposioHQ/awesome-claude-plugins
+
+**Target:** [ComposioHQ/awesome-claude-plugins](https://github.com/ComposioHQ/awesome-claude-plugins) (stale, ~2 months no activity)
+
+**Status:** Optional, deprioritized due to inactivity
+
+**Method:** If submitting, likely a **PULL REQUEST** (check CONTRIBUTING.md)
+
+**Ready Copy:**
+
+*Suggested bullet:*
+```markdown
+- [**claude-kit**](https://github.com/ajyadav013/claude-kit) - Stack-agnostic autonomous SDLC plugin with quality gates, reviewer agents, and anti-sycophancy devils-advocate verification.
+```
+
+**Etiquette:**
+- Check repository activity before submitting
+- Review CONTRIBUTING.md if it exists
+- Consider waiting for signs of active maintenance before submitting
+
+---
+
+## General Submission Etiquette
+
+1. **Follow each list's CONTRIBUTING guidelines** — some require issues, others PRs
+2. **One entry per submission** — do not batch multiple resources
+3. **Factual, non-promotional descriptions** — let the features speak for themselves
+4. **No emoji** in descriptions unless the list explicitly uses them
+5. **Respect maintainer time** — wait for review, do not ping or rush
+6. **Verify links** before submitting
+7. **Check star counts and activity** — prioritize active, high-visibility lists
+
+---
+
+## Verification Checklist
+
+Before submitting to any list:
+
+- [ ] Repository is MIT-licensed (verified)
+- [ ] GitHub URL is correct: https://github.com/ajyadav013/claude-kit
+- [ ] PyPI package exists: https://pypi.org/project/claude-code-kit/
+- [ ] Description is factual and non-promotional
+- [ ] Character count is within constraints (where applicable)
+- [ ] Submission method matches the list's requirements (issue vs PR)
+- [ ] Target file path is correct (for PRs)
+- [ ] Category is appropriate for the resource
+
+---
+
+*Last updated: 2026-07-03*