Skip to content

Releases

v0.25.1

Choose a tag to compare

@github-actions github-actions released this 04 Aug 12:38

Changed

  • The installer, updater, and README name /doctor as the way to register copied-in skills without losing the session — confirmed in practice on the install that prompted 0.25.0, where the advice had been to start a new session.

v0.25.0

Choose a tag to compare

@github-actions github-actions released this 04 Aug 12:31

Onboarding reachability. A real install showed /wizard was unreachable in the session that installed it, and that the
wizard asked for a name package.json already declares.

Added

  • plugin/skills/wizard/SKILL.md — a signpost (not a copy) to the repo's own wizard, so /wizard resolves in the session that installed the kit. Slash commands register at session start, so the copied-in skill isn't one yet: the keystroke arrived as plain text and matched /frontend-kit:install, whose description names the wizard — the kit demanding an install that had just happened. Same disable-model-invocation gate, or the plugin would become the hole in it.

Changed

  • /wizard resolves the CLAUDE.md title instead of asking for it: name from package.json, the repo folder name when that's absent, verbatim either way. The prompt offered exactly those two values and step 9 now names the one it used, so a wrong guess is a one-word edit rather than a question every run.
  • The wizard states that its gate is on the Skill tool, not on the file: a user asking for onboarding in words — the only form available before a restart — is the keystroke the gate wants, so the steps get worked instead of refused. Three refusals preceded a manual run in the install that prompted this.
  • Step 3 asks its four questions in one AskUserQuestion call rather than two, now that the name question is gone.
  • The installer and updater name the session-start registration trap and offer to work the onboarding inline from the copy they just wrote; the README quick start says the same.

v0.22.0

Choose a tag to compare

@github-actions github-actions released this 14 Jul 20:36

Surface trim (team review): agents 12 → 5, skills 15 → 7, rules 16 → 13 files.

Changed

  • Agents are now only the quality-gate board — 4 read-only auditors (ui-reviewer, accessibility-auditor, performance-auditor, security-scanner) + test-engineer; the lead plans, builds, debugs, and refactors inline (workflow.md rewritten accordingly).
  • principles.md and git-operations.md folded into CLAUDE.md (Working principles / Git sections); observability.md merged into error-handling.md (same path scope, adjacent domain).
  • /verify hands deeper passes to the auditor agents; /prune unit map rebuilt for the new surface (11 units).

Removed

  • Agents planner, devil, frontend-developer, refactoring-expert, debugger, ci-cd-engineer, docs-writer — persona-shaped delegation the lead does inline; isolation/parallelism/least-privilege stays with the auditors.
  • Skills a11y-audit, perf-audit, security-audit, code-review, debug-frontend, add-tests, refactor, upgrade-deps — their checklists live in the owning rules; the agents execute them.

v0.21.0

Choose a tag to compare

@TarasTsavolyk TarasTsavolyk released this 30 Jul 21:27

Security trim (team review): smaller allowlist, one wired hook, no committed MCP config.

Changed

  • settings.json allowlist: no more run:* wildcards or install/npx pre-approvals (supply-chain vectors) — only the four explicit gate scripts per package manager plus read-only git; everything else goes through first-party permission prompts.
  • Playwright MCP is now a per-developer local install (claude mcp add playwright -s local …, documented in README) — agents fall back to code review + CLI without it.

Removed

  • .mcp.json — personal preference, not shared repo config; enabledMcpjsonServers gone with it.
  • session-start.mjs hook (+ its test and SessionStart wiring) — onboarding is now "run /wizard after install", nothing executes automatically on session start.

v0.20.0

Choose a tag to compare

@TarasTsavolyk TarasTsavolyk released this 30 Jul 21:28

Vue-3-only: the multi-framework surface is gone (team review decision).

Changed

  • detect-stack.mjs detects Vue/Nuxt only — isVue/vueVersion replace framework/frameworkVersion, non-Vue repos get an explicit warning (facts schema v4).
  • /wizard onboards Vue projects only — stops on non-Vue repos; the framework question is gone.

Removed

  • Framework-agnostic / "translation mode" framing from CLAUDE.md and README — the kit targets Vue 3, period.

v0.19.0

Choose a tag to compare

@github-actions github-actions released this 05 Jul 19:13

The testing surface gets wiring mechanics and honest bars — same audit as v0.18.0.

Added

  • testing.md: read-the-harness-first; MSW lifecycle (onUnhandledRequest: 'error', resetHandlers() per test); test-data builders over copy-pasted fixtures; Pinia wiring (setActivePinia / createTestingPinia); router wiring (RouterLinkStub / createMemoryHistory + isReady); settle-before-asserting (await interactions, nextTick, flushPromises); web-first e2e assertions; per-flow @axe-core/playwright scan; a characterization-tests definition under Bar (with the golden-master carve-out). Frontmatter now also scopes __tests__/ dirs and tsx/jsx test files.
  • /add-tests: step 1 "Find the gap" (diff-driven or --coverage) and a closing "Run & report" step matching test-engineer's report.
  • /verify: conditional test:e2e run when e2e is touched; leftover .only/.skip joins the scope-creep check (a local .only greens the gate on one test).

Changed

  • testing.md Bar: "happy path + one edge/error/empty branch" now lives in the owning rule; the coverage ratchet names its mechanism (Vitest coverage.thresholds + autoUpdate) instead of being aspiration; flake check is --repeat-each=3 --retries=0 (retries mask flakes; synced in /add-tests); visual regression covers Vitest browser mode's toMatchScreenshot(), not just Storybook; the snapshot ban gains its one legitimate carve-out.
  • /debug-frontend steps 5–6: the failing test that confirms the hypothesis IS the regression test — no fix-first with a retrofitted test.
  • workflow.md step 3 tells the truth about the gate board: auditors are read-only, test-engineer alone writes.
  • /prune e2e trim also strips the new test:e2e bullet from /verify.

v0.18.0

Choose a tag to compare

@github-actions github-actions released this 05 Jul 19:09

The refactor path gets real safety mechanics — found by a 6-lens adversarially-verified audit.

Added

  • /refactor: reference sweep before editing (PascalCase and kebab-case tags, alias and relative imports, lazy import() strings, barrel re-exports, string-keyed i18n/analytics/route/storage keys — grep is the only net in JS projects); strangler-fig migration for many-caller replacements; red-step abort rule (revert, never edit an assertion to green a refactor); visual-parity check when template/styles move; a codemod procedure for mechanical many-file changes. Sweep + abort rule mirrored in refactoring-expert.
  • architecture.md: Split a fat store pattern (domain split, demote to local, actions → plain functions, server data → query layer; defineStore id is public API) and the scoped-<style> breakage gotcha on leaf extraction.
  • workflow.md: markup-moving refactors add accessibility-auditor to the Refactor verify board — focus/label/aria wiring breaks with tests green.

Fixed

  • /refactor delegation criterion now matches workflow.md ("large, bounded restructuring") and drops the false "least-privilege" tag on a write-capable agent.

v0.17.0

Choose a tag to compare

@github-actions github-actions released this 04 Jul 22:31

The riskiest code in the kit — the hooks — is now tested.

Added

  • tests/hooks/ — 28 unit tests over all five hooks via zero-dep node --test (no package.json needed): detect-stack heuristics (framework/meta/PM/corepack/workspaces/kit-state), pre-commit-gate (fail-open paths, commit parsing, block/pass, docs-only skip, --native), check-refs (corpus exclusions, hyphen boundary), post-edit-lint (fail-open, real --fix invocation), session-start (nudge/silence).
  • .github/workflows/test.yml runs the suite on every push/PR; README Contributing points hook changes at it.

v0.16.0

Choose a tag to compare

@github-actions github-actions released this 04 Jul 22:24

The kit gets an update path.

Added

  • The repo is now a plugin marketplace (.claude-plugin/marketplace.json) shipping one plugin: frontend-kit (plugin/) — an installer/updater, not a runtime. /frontend-kit:install copies the kit into a repo (then hands off to /wizard); /frontend-kit:update syncs new releases into the committed copy — diff-aware, prune-aware (never silently re-adds removed units), and never touches the project's CLAUDE.md.
  • Why not a full plugin port: plugins can't ship rules, CLAUDE.md, permissions, or env settings — so the owned committed copy stays the source of truth and the plugin is only the delivery vehicle. README quick start now leads with the plugin route; the Design choices distribution bullet updated.

v0.15.0

Choose a tag to compare

@github-actions github-actions released this 04 Jul 22:21

The gate and the framing tell the truth.

Added

  • pre-commit-gate.mjs --native: the same gate runs from .git/hooks/pre-commit, so terminal commits are gated too — the PreToolUse hook only ever caught commits made through Claude Code. /wizard step 7 offers to install it (husky/lefthook-aware); README documents the one-liner and the limit.

Changed

  • README repositioned as Vue-first: Vue is the native fit; other detected frameworks run in explicit "translation mode" until per-framework rule sets exist — no more implying full framework-agnostic value today.