claude-code-kit 0.15.0__tar.gz → 0.16.0__tar.gz

{claude_code_kit-0.15.0 → claude_code_kit-0.16.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.15.0",
+      "version": "0.16.0",
       "license": "MIT",
       "keywords": ["sdlc", "agents", "orchestration", "quality-gates", "workflow", "scaffold", "cookiecutter"]
     }

{claude_code_kit-0.15.0 → claude_code_kit-0.16.0}/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-kit",
-  "version": "0.15.0",
+  "version": "0.16.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.15.0 → claude_code_kit-0.16.0}/CHANGELOG.md

@@ -4,6 +4,57 @@ 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.16.0] — 2026-06-16
+
+**Adopt a full React/Tailwind/Radix design-system rule set as always-on React overlay rules.** Three
+manually-authored, production-grade design docs — `ui-design-system.md` (color/spacing/typography/
+radius scales, card & badge & icon standards, accessibility), `ux-patterns.md` (status expression,
+empty states, breadcrumbs, page archetypes/blueprints, button ordering, date formatting, data colors),
+and `mobile-design-guidelines.md` (responsive breakpoints, touch targets, Capacitor native patterns) —
+are now installed into `.claude/rules/` whenever the **React** frontend is selected. This closes a
+long-standing gap: the kit already shipped the *readers* (`ui-ux-design` + `component-design` skills,
+`ui-designer` agent) but not the *content* they pointed at, so a fresh install never created the design
+docs they read.
+
+Placement is **always-on React overlay rules** (wired purely through `catalog/stacks.yaml`
+`overlay_rules` — no new scaffold mechanism, `resolve()` untouched per golden rule #6). Accepted
+trade-off: ~3k lines of design rules load every session on React projects, in exchange for the design
+system being authoritative and always present. The three files live **only** in
+`templates/stacks/frontend/react/rules/` (golden rule #1 — stack content stays in overlays).
+
+IP boundary: the design **decisions** are preserved verbatim (radius, touch targets, status-via-Badge,
+button ordering, date formats, chart standards, the four page archetypes and their blueprints/compound
+tables), while every app-specific reference was neutralized — product/persona/route identity, concrete
+`src/...` module paths and named app components, the 52-page inventory, dated migration backlogs, the
+domain KPI glossary and INR locale specifics, project-specific lint-rule identifiers, and brand hex
+values (→ `#______` placeholders, matching the existing `design-system-compliance.md` style).
+
+### Added
+- **Three React overlay rules** under `templates/stacks/frontend/react/rules/`:
+  `ui-design-system.md`, `ux-patterns.md`, `mobile-design-guidelines.md` — registered in
+  `catalog/stacks.yaml` → `frontend.frameworks.react.overlay_rules`, installed into `.claude/rules/`
+  only when React is selected. Consumed by the React-gated `ui-ux-design` / `component-design` skills
+  and the `ui-designer` agent.
+
+### Changed
+- **Conflicts resolved in favor of the new files.** `design-system-compliance.md` — the placeholder
+  token table is replaced by a thin pointer naming `ui-design-system.md` (+ `ux-patterns.md` /
+  `mobile-design-guidelines.md`) as the source of truth ("if anything here conflicts, that file wins"),
+  keeping only the concise always-on enforcement hook. `react-patterns.md` — the "Accessibility
+  specifics (Tailwind + Radix)" rules (contrast table, `p-3 -m-3` touch target, clickable-non-button)
+  are trimmed to a cross-reference into `ui-design-system.md` §Accessibility, retaining two
+  React-specific review reminders.
+- **Reader paths repointed** from `docs/references/ui/...` → `.claude/rules/...` so the existing
+  reader-loop connects to the now-installed content: `skills/ui-ux-design` (steps 1–2 + References,
+  with the design-system rule marked authoritative over the inline quick-check table),
+  `skills/component-design` (read whichever of the overlay rule or `docs/references/ui/` is present),
+  and `agents/ui-designer` (overlay rule added to its candidate locations, defensive "if one exists"
+  framing kept — the agent is core/un-gated and must not assume the React overlay is present).
+
+### Notes
+- `docs/references/ui/sidebar-navigation.md` is **not** supplied by the kit; the skills reference it as
+  project-specific/optional.
+
 ## [0.15.0] — 2026-06-16
 
 **Adopt the Fynd Agentic Engineering personas & skills** (an internal Claude Code plugin marketplace —

{claude_code_kit-0.15.0 → claude_code_kit-0.16.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: claude-code-kit
-Version: 0.15.0
+Version: 0.16.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
@@ -60,7 +60,9 @@ refuses to advance a phase until its **quality gate** passes. You drive it all w
 
 - 🧱 **Stack-agnostic** — the pipeline assumes no language or framework. Pick a stack at `init` and it
   installs matching overlay rules (React · FastAPI · Go/net-http · PostgreSQL · MongoDB) and your exact
-  lint/test/build commands. It never writes your app code and never needs Docker.
+  lint/test/build commands. Picking React also installs a full design-system rule set (design tokens,
+  UX patterns, mobile/Capacitor guidelines) that the UI skills and `ui-designer` agent read. It never
+  writes your app code and never needs Docker.
 - 🎚️ **Dial the rigor with profiles** — `lean ⊊ standard ⊊ enterprise` decide how many agents, skills,
   hooks, and gates are active, from "fast track" to "full audit".
 - 👥 **Scope to your team** — `individual` / `team` (default) / `organization`. Org scope adds a

{claude_code_kit-0.15.0 → claude_code_kit-0.16.0}/README.md

@@ -33,7 +33,9 @@ refuses to advance a phase until its **quality gate** passes. You drive it all w
 
 - 🧱 **Stack-agnostic** — the pipeline assumes no language or framework. Pick a stack at `init` and it
   installs matching overlay rules (React · FastAPI · Go/net-http · PostgreSQL · MongoDB) and your exact
-  lint/test/build commands. It never writes your app code and never needs Docker.
+  lint/test/build commands. Picking React also installs a full design-system rule set (design tokens,
+  UX patterns, mobile/Capacitor guidelines) that the UI skills and `ui-designer` agent read. It never
+  writes your app code and never needs Docker.
 - 🎚️ **Dial the rigor with profiles** — `lean ⊊ standard ⊊ enterprise` decide how many agents, skills,
   hooks, and gates are active, from "fast track" to "full audit".
 - 👥 **Scope to your team** — `individual` / `team` (default) / `organization`. Org scope adds a

{claude_code_kit-0.15.0 → claude_code_kit-0.16.0}/agents/ui-designer.md

@@ -19,7 +19,7 @@ For any frontend, UI, or interaction work, produce a **complete, production-read
 Your project's frontend stack may vary. Before designing, identify:
 - The UI framework (e.g., React, Vue, Svelte, Angular, vanilla JS)
 - The styling approach (e.g., CSS modules, Tailwind, styled-components, CSS-in-JS)
-- Design system location (if one exists — check `docs/references/ui/`, `design-system/`, or similar)
+- Design system location (if one exists — check `.claude/rules/ui-design-system.md` (React overlay), `docs/references/ui/`, `design-system/`, or similar)
 - Component library path (check `src/components/`, `lib/ui/`, or similar)
 
 ## MANDATORY: Read Before Designing

{claude_code_kit-0.15.0 → claude_code_kit-0.16.0}/catalog/stacks.yaml

@@ -24,7 +24,7 @@ frontend:
       languages:
         default: typescript
         options: [typescript, javascript]
-      overlay_rules: [react-patterns.md, design-system-compliance.md]
+      overlay_rules: [react-patterns.md, design-system-compliance.md, ui-design-system.md, ux-patterns.md, mobile-design-guidelines.md]
       overlay_agents: []
       skills: [frontend-ui-engineering, component-design, ui-ux-design, unit-test]
       stack_dir: frontend/react

{claude_code_kit-0.15.0 → claude_code_kit-0.16.0}/docs/coverage-audit.md

@@ -70,6 +70,7 @@ checklists that ride *inside existing* review gates. Enforcement class of each:
 | **Suite-architecture audit** | **AGENT mode — standard+** | `suite-audit` mode on `agents/senior-tester`; a verification *mode*, not a separate token | advisory (within testing) |
 | **Staff-PM product-lens review tier** | **SKILL/AGENT — organization scope only** | `staff-pm-reviewer` + `review-scope`/`review-sprint-plan`/`review-ux-flow`/`review-sprint` install only when `scope == organization` (`catalog/org.yaml`); read-only, advisory — no product gate token | org scope (advisory) |
 | **Design-system compliance · a11y/contract overlay enrichments** | **OVERLAY RULE** | `design-system-compliance.md` + enrichments in `react-patterns.md`/`fastapi-patterns.md`; install only when the matching stack is selected | when stack selected (advisory rule) |
+| **Design system · UX patterns · mobile guidelines** (0.16.0) | **OVERLAY RULE — React-gated, always-on, advisory** | `ui-design-system.md` / `ux-patterns.md` / `mobile-design-guidelines.md` (React `overlay_rules`); install into `.claude/rules/` only when React is selected, then load every session. The authoritative source for `design-system-compliance.md`'s thin pointer and `react-patterns.md`'s trimmed a11y cross-ref; consumed by the `ui-ux-design` / `component-design` skills + `ui-designer` agent | when React selected (advisory rule) |
 
 The two that reach *enforced* (claim-audit, eval/HITL) do so the same way P0-2 did — by strengthening
 an **existing** gate's owner-agent checklist, not by minting a token. Everything else is advisory by

{claude_code_kit-0.15.0 → claude_code_kit-0.16.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "claude-code-kit"
-version = "0.15.0"
+version = "0.16.0"
 description = "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."
 readme = "README.md"
 requires-python = ">=3.9"

{claude_code_kit-0.15.0 → claude_code_kit-0.16.0}/skills/component-design/SKILL.md

@@ -9,7 +9,7 @@ Design and implement the component: $ARGUMENTS.
 
 ## Steps
 
-1. **Read the design system**: Read `docs/references/ui/ui-design-system.md` for visual rules and component standards (if available).
+1. **Read the design system**: Read `.claude/rules/ui-design-system.md` (installed as a React overlay rule) for visual rules and component standards — or a project's `docs/references/ui/ui-design-system.md` equivalent. Read whichever is present.
 
 2. **Check existing components**: Check the project's component directory for available UI primitives and established patterns. Search for similar components to follow the project's conventions.
 
@@ -95,8 +95,8 @@ Design and implement the component: $ARGUMENTS.
 ## References
 
 - UI primitives: Project's UI primitives directory/barrel export
-- Design system: `docs/references/ui/ui-design-system.md` (if available)
-- UX patterns: `docs/references/ui/ux-patterns.md` (if available)
+- Design system: `.claude/rules/ui-design-system.md` (React overlay) or `docs/references/ui/ui-design-system.md` (if present)
+- UX patterns: `.claude/rules/ux-patterns.md` (React overlay) or `docs/references/ui/ux-patterns.md` (if present)
 - Rules: `.claude/rules/frontend-best-practices.md`, `.claude/rules/responsive-and-accessibility.md`
 
 ## Examples

{claude_code_kit-0.15.0 → claude_code_kit-0.16.0}/skills/ui-ux-design/SKILL.md

@@ -9,9 +9,9 @@ Verify UI/UX design compliance for $ARGUMENTS.
 
 ## Steps
 
-1. **Read the design system**: Read `docs/references/ui/ui-design-system.md` to load the full design rules — colors, typography, spacing, cards, icons, badges, components, and accessibility.
+1. **Read the design system**: Read `.claude/rules/ui-design-system.md` to load the full design rules — colors, typography, spacing, cards, icons, badges, components, and accessibility. (Installed as an overlay rule when the React stack is selected.) This file is **authoritative**: if the quick-check table below ever conflicts with it, follow the rule file.
 
-2. **Read the UX patterns doc**: Read `docs/references/ui/ux-patterns.md` for status expression rules, empty state guidelines, breadcrumb conventions, page blueprints, and data color rules.
+2. **Read the UX patterns doc**: Read `.claude/rules/ux-patterns.md` for status expression rules, empty state guidelines, breadcrumb conventions, page blueprints, and data color rules. For responsive/native specifics, also read `.claude/rules/mobile-design-guidelines.md`.
 
 3. **Identify the page archetype**: Determine if the target is a **List**, **Dashboard**, **Detail**, or **Config** page. Each archetype has specific compound components and hooks it should use.
 
@@ -64,8 +64,9 @@ Verify UI/UX design compliance for $ARGUMENTS.
 
 ## References
 
-- Design system: `docs/references/ui/ui-design-system.md`
-- UX patterns: `docs/references/ui/ux-patterns.md`
-- Sidebar navigation: `docs/references/ui/sidebar-navigation.md`
+- Design system: `.claude/rules/ui-design-system.md`
+- UX patterns: `.claude/rules/ux-patterns.md`
+- Mobile / responsive: `.claude/rules/mobile-design-guidelines.md`
+- Sidebar navigation: `docs/references/ui/sidebar-navigation.md` (project-specific, if present)
 - UI components: `src/components/ui/index.ts`
 - Existing pages: `src/pages/` (look at similar archetype)

{claude_code_kit-0.15.0 → claude_code_kit-0.16.0}/src/claude_kit/__init__.py

@@ -7,4 +7,4 @@ Docker): ``claude-kit init`` asks ordered questions and lays down ``CLAUDE.md``
 as a plugin. Extensibility is data-driven via the ``catalog/`` (stacks, profiles, MCP).
 """
 
-__version__ = "0.15.0"
+__version__ = "0.16.0"

{claude_code_kit-0.15.0 → claude_code_kit-0.16.0}/templates/stacks/frontend/react/rules/design-system-compliance.md

@@ -6,22 +6,19 @@ the **React** frontend is selected; it complements `react-patterns.md`,
 design-review technique). This file is about **consistency**: make every screen look like it came from
 one system, by going through tokens and shared primitives instead of one-off styling.
 
-> Fill in the bracketed values with **your** project's design tokens once; after that the rules below
-> enforce them. The point is not the specific numbers — it's that there is exactly one source for each.
+> The full token / component / pattern catalog is **`ui-design-system.md`** (with `ux-patterns.md` for
+> usage rules and `mobile-design-guidelines.md` for responsive/native) — all installed alongside this
+> file in `.claude/rules/`. Those are the source of truth; this file is the short, always-on
+> **enforcement** hook. If anything here ever conflicts with `ui-design-system.md`, that file wins.
 
 ## Use tokens, never arbitrary values
 
 - Reference the configured theme/palette names (`bg-primary`, `text-muted-foreground`, …) — **do not**
   ship Tailwind arbitrary values like `bg-[#5347CD]`, `rounded-[7px]`, `p-[13px]`. An arbitrary value
   in a component is a design-system bypass and a review finding.
-- Pin the palette in the Tailwind theme config; components consume the names:
-
-  | Token | Project value (fill in) |
-  |---|---|
-  | primary | `[#______]` |
-  | accent | `[#______]` |
-  | background / surface | `[#______]` |
-  | foreground / muted-foreground | `[#______]` / `[#______]` |
+- Pin the palette once in the Tailwind theme config (`@theme`); components consume the names. The
+  actual token values and the full color / spacing / typography / radius scales are defined in
+  **`ui-design-system.md`** — set them there, then reference the names everywhere.
 
 ## One set of component variants