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

{claude_code_kit-0.54.0 → claude_code_kit-0.55.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.54.0",
+      "version": "0.55.0",
       "license": "MIT",
       "keywords": ["sdlc", "agents", "orchestration", "quality-gates", "workflow", "scaffold", "cookiecutter"]
     }

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

@@ -1,6 +1,6 @@
 {
   "name": "claude-kit",
-  "version": "0.54.0",
+  "version": "0.55.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.54.0 → claude_code_kit-0.55.0}/.gitignore

@@ -28,3 +28,9 @@ zap-vapt-tool.zip
 # depth, and on case-insensitive filesystems (macOS default) it also swallows
 # rules/continuity.md — the tracked rule file.
 .claude/
+
+# Local-only working artifacts — generated during development, never part of the distributable kit.
+# (Review write-ups, ad-hoc patches, and locally-gathered reference data.)
+claude-kit-review*.md
+*.patch
+ai_repos_over_40k_stars.*

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

@@ -4,6 +4,34 @@ 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.55.0] — 2026-07-01
+
+**React overlay rules split under Claude Code's 40k memory limit.** Two React design-system overlay
+rules shipped over the 40,000-character memory/rule-file limit, so every React scaffold saw the
+`over the 40.0k-char limit · /memory` warning and risked the rule loading only partially. They are now
+split by concern — 100% of content preserved verbatim — and a CI guard keeps any rule from regressing.
+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.**
+
+### Fixed
+
+- **Oversized React overlay rules split under the 40k limit.** `ui-design-system.md` (56.7k) → the
+  foundations/index `ui-design-system.md` + `ui-components.md` (cards, badges, buttons, form controls,
+  states, tooltips, KPI labels, data tables, compound components) + `ui-layout-and-motion.md` (page
+  layout, motion, accessibility, page blueprints, quick reference); `ux-patterns.md` (44.4k) → the
+  content/interaction `ux-patterns.md` + `ux-dashboard-patterns.md` (chart standards, tab bar, KPI-grid
+  layouts, global filter strip). Every shipped rule file is now well under the limit. The React
+  `overlay_rules` list (`catalog/stacks.yaml`) grows 5 → 8; cross-references in `react-patterns.md`,
+  `mobile-design-guidelines.md`, and `design-system-compliance.md`, and the `ui-ux-design` /
+  `component-design` skills + `ui-designer` agent, all repoint to the split files.
+
+### Added
+
+- **`scripts/check_rule_sizes.py` regression guard.** Scans every shipped rule file (`rules/*.md`,
+  `templates/stacks/**/rules/*.md`, `templates/org/rules/*.md`) and fails if any reaches 38,000
+  characters (2k of headroom under the 40k hard limit). Wired into CI next to the MCP-pin gate and
+  covered by `tests/test_rule_sizes.py`.
+
 ## [0.54.0] — 2026-06-29
 
 **Safety, correctness, and capability hardening pass.** Two reviews (a fresh practical review and an

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

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: claude-code-kit
-Version: 0.54.0
+Version: 0.55.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

{claude_code_kit-0.54.0 → claude_code_kit-0.55.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 `.claude/rules/ui-design-system.md` (React overlay), `docs/references/ui/`, `design-system/`, or similar)
+- Design system location (if one exists — check `.claude/rules/ui-design-system.md` (React overlay; its `ui-components.md` / `ui-layout-and-motion.md` companions cover components and layout/motion/a11y), `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.54.0 → claude_code_kit-0.55.0}/catalog/stacks.yaml

@@ -24,7 +24,7 @@ frontend:
       languages:
         default: typescript
         options: [typescript, javascript]
-      overlay_rules: [react-patterns.md, design-system-compliance.md, ui-design-system.md, ux-patterns.md, mobile-design-guidelines.md]
+      overlay_rules: [react-patterns.md, design-system-compliance.md, ui-design-system.md, ui-components.md, ui-layout-and-motion.md, ux-patterns.md, ux-dashboard-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.54.0 → claude_code_kit-0.55.0}/docs/coverage-audit.md

@@ -70,7 +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) |
+| **Design system · UX patterns · mobile guidelines** (0.16.0; split under the 40k limit in 0.55.0) | **OVERLAY RULE — React-gated, always-on, advisory** | `ui-design-system.md` (foundations) + `ui-components.md` + `ui-layout-and-motion.md` / `ux-patterns.md` + `ux-dashboard-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.54.0 → claude_code_kit-0.55.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "claude-code-kit"
-version = "0.54.0"
+version = "0.55.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.55.0/scripts/check_rule_sizes.py

@@ -0,0 +1,75 @@
+#!/usr/bin/env python3
+"""Fail if any shipped rule file is close to Claude Code's memory/rule-file size limit.
+
+Claude Code warns (and can load a rule only partially) when a memory/rule file exceeds
+**40,000 characters**. Every rule this kit ships is copied verbatim into a user project's
+``.claude/rules/`` and loaded on demand, so an over-limit rule silently degrades in every install.
+
+This is an offline, deterministic CI gate. It scans the rule files the kit distributes — the
+stack-agnostic core (``rules/``), the per-stack overlays (``templates/stacks/**/rules/``), and the
+org overlays (``templates/org/rules/``) — and fails if any is at or above ``THRESHOLD`` characters.
+The threshold sits below the hard limit to keep headroom for small edits before a file must be split.
+"""
+
+from __future__ import annotations
+
+import sys
+from pathlib import Path
+
+ROOT = Path(__file__).resolve().parents[1]
+
+# Claude Code's hard limit is 40,000 characters; keep 2k of headroom so a small edit does not
+# immediately push a rule over the line before someone notices it needs splitting.
+HARD_LIMIT = 40_000
+THRESHOLD = 38_000
+
+# Glob patterns (relative to ROOT) for every rule file the kit ships into a user's .claude/rules/.
+RULE_GLOBS = (
+    "rules/*.md",
+    "templates/stacks/**/rules/*.md",
+    "templates/org/rules/*.md",
+)
+
+
+def rule_files(root: Path | None = None) -> list[Path]:
+    """Return every shipped rule file, de-duplicated and sorted by path."""
+    base = root or ROOT
+    found: set[Path] = set()
+    for pattern in RULE_GLOBS:
+        found.update(base.glob(pattern))
+    return sorted(found)
+
+
+def oversized(
+    root: Path | None = None, threshold: int = THRESHOLD
+) -> list[tuple[Path, int]]:
+    """Return ``(path, char_count)`` for each rule file at or above ``threshold`` characters."""
+    base = root or ROOT
+    out: list[tuple[Path, int]] = []
+    for path in rule_files(base):
+        count = len(path.read_text(encoding="utf-8"))
+        if count >= threshold:
+            out.append((path.relative_to(base), count))
+    return out
+
+
+def main() -> int:
+    files = rule_files()
+    bad = oversized()
+    if bad:
+        print(
+            f"FAIL  rule file(s) at/over {THRESHOLD:,} chars "
+            f"(Claude Code's limit is {HARD_LIMIT:,}); split them by concern:"
+        )
+        for rel, count in bad:
+            print(f"  - {rel} -> {count:,} chars")
+        return 1
+    print(
+        f"OK    all {len(files)} shipped rule file(s) are under {THRESHOLD:,} chars "
+        f"(limit {HARD_LIMIT:,})"
+    )
+    return 0
+
+
+if __name__ == "__main__":
+    sys.exit(main())

{claude_code_kit-0.54.0 → claude_code_kit-0.55.0}/skills/component-design/SKILL.md

@@ -9,7 +9,7 @@ Design and implement the component: $ARGUMENTS.
 
 ## Steps
 
-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.
+1. **Read the design system**: Read `.claude/rules/ui-design-system.md` (foundations & index) and `.claude/rules/ui-components.md` (component standards — cards, badges, buttons, form controls, compound components), both installed as React overlay rules — 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: `.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)
+- Design system: `.claude/rules/ui-design-system.md` (foundations) + `.claude/rules/ui-components.md` + `.claude/rules/ui-layout-and-motion.md` (React overlay) or `docs/references/ui/ui-design-system.md` (if present)
+- UX patterns: `.claude/rules/ux-patterns.md` + `.claude/rules/ux-dashboard-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.54.0 → claude_code_kit-0.55.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 `.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.
+1. **Read the design system**: Read `.claude/rules/ui-design-system.md` (foundations & index — colors, typography, spacing, icons, tokens) and its companions `.claude/rules/ui-components.md` (cards, badges, buttons, form controls, states, compound components) and `.claude/rules/ui-layout-and-motion.md` (page layout, motion, accessibility, page blueprints). (Installed as overlay rules when the React stack is selected.) These files are **authoritative**: if the quick-check table below ever conflicts with them, follow the rule files.
 
-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`.
+2. **Read the UX patterns docs**: Read `.claude/rules/ux-patterns.md` for status expression rules, empty state guidelines, breadcrumb conventions, page blueprint selection, and data color rules, and `.claude/rules/ux-dashboard-patterns.md` for chart standards, tab-bar limits, KPI-grid layouts, and the global filter strip. 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,8 @@ Verify UI/UX design compliance for $ARGUMENTS.
 
 ## References
 
-- Design system: `.claude/rules/ui-design-system.md`
-- UX patterns: `.claude/rules/ux-patterns.md`
+- Design system: `.claude/rules/ui-design-system.md` (foundations), `.claude/rules/ui-components.md`, `.claude/rules/ui-layout-and-motion.md`
+- UX patterns: `.claude/rules/ux-patterns.md`, `.claude/rules/ux-dashboard-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`

{claude_code_kit-0.54.0 → claude_code_kit-0.55.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.54.0"
+__version__ = "0.55.0"

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

@@ -6,8 +6,10 @@ 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.
 
-> 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
+> The full token / component / pattern catalog is **`ui-design-system.md`** (foundations & index) plus
+> its companions **`ui-components.md`** (components) and **`ui-layout-and-motion.md`** (layout, motion,
+> accessibility, page blueprints) — with **`ux-patterns.md`** and **`ux-dashboard-patterns.md`** for
+> usage rules and `mobile-design-guidelines.md` for responsive/native. All are 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.
 

{claude_code_kit-0.54.0 → claude_code_kit-0.55.0}/templates/stacks/frontend/react/rules/mobile-design-guidelines.md

@@ -77,7 +77,7 @@ Use Tailwind's mobile-first responsive prefixes. **Write mobile styles first, th
 </MetricGrid>
 
 // GOOD — dashboard KPI cards under tabs (cap + View more / View less toggle on mobile)
-// See ux-patterns.md §20 for the full spec
+// See ux-dashboard-patterns.md (Dashboard KPI Grid Pattern) for the full spec
 <DashboardKpiGrid>
   {kpis.map((k) => <MetricCard key={k.id} label={k.label} value={k.value} />)}
 </DashboardKpiGrid>
@@ -94,7 +94,7 @@ Use Tailwind's mobile-first responsive prefixes. **Write mobile styles first, th
 
 ### Dashboard KPI Grid
 
-KPI cards rendered inside `<TabsContent>` on persona-driven dashboards follow a special responsive pattern: max 4 cards per row on desktop (≥1024px) with fill-space behavior when count < 4, 2 per row + cap of 8 on larger mobile (430-1023px), 1 per row + cap of 4 on small mobile (<430px), and a "View more / View less" ghost button toggle on both mobile sizes (never on desktop). Use a dedicated `<DashboardKpiGrid>` component. See **Section 20** of `ux-patterns.md` for the full breakpoint table, ASCII wireframes, and anti-patterns.
+KPI cards rendered inside `<TabsContent>` on persona-driven dashboards follow a special responsive pattern: max 4 cards per row on desktop (≥1024px) with fill-space behavior when count < 4, 2 per row + cap of 8 on larger mobile (430-1023px), 1 per row + cap of 4 on small mobile (<430px), and a "View more / View less" ghost button toggle on both mobile sizes (never on desktop). Use a dedicated `<DashboardKpiGrid>` component. See the **Dashboard KPI Grid Pattern** in `ux-dashboard-patterns.md` for the full breakpoint table, ASCII wireframes, and anti-patterns.
 
 ### Sidebar & Navigation
 

{claude_code_kit-0.54.0 → claude_code_kit-0.55.0}/templates/stacks/frontend/react/rules/react-patterns.md

@@ -66,7 +66,7 @@ Rules of thumb:
 
 The concrete React/Tailwind/Radix accessibility rules — gray-scale text-contrast thresholds, the
 `p-3 -m-3` 44px touch-target technique, clickable-non-button keyboard requirements, focus rings, and
-icon-only-button labelling — live in **`ui-design-system.md`** (§Accessibility), with the generic WCAG
+icon-only-button labelling — live in **`ui-layout-and-motion.md`** (§Accessibility), with the generic WCAG
 technique in `.claude/rules/responsive-and-accessibility.md` and the `accessibility-review` skill. Two
 React-specific reminders that earn a review finding here: