claude-code-arcane 2.15.0 → 2.16.0

package/CHANGELOG.md

@@ -1,3 +1,11 @@
+# [2.16.0](https://github.com/SebastianLuser/claude-code-arcane/compare/v2.15.0...v2.16.0) (2026-10-16)
+
+
+### Features
+
+* **profiles:** ship playwright-pro with the web profiles ([a6d3785](https://github.com/SebastianLuser/claude-code-arcane/commit/a6d37851f1c6dd2384a96e7b3a00e797e178b10f))
+* **rules:** review a finished goal with a fresh subagent ([9aab70b](https://github.com/SebastianLuser/claude-code-arcane/commit/9aab70bf1a26af19d8bfe9ba9d7e75b7c651637b))
+
 # [2.15.0](https://github.com/SebastianLuser/claude-code-arcane/compare/v2.14.0...v2.15.0) (2026-10-16)
 
 

package/README.md

@@ -194,13 +194,13 @@ Older names still install and update: `backend-ts`, `frontend`, `mobile`, `flutt
 | `backend-go` | Backend Go — Clean Arch, DB, auth, API, CI | 26 | engineering |
 | `backend-dotnet` | Backend .NET — ASP.NET Core, Vertical Slice/Clean, EF Core, JWT | 27 | engineering |
 | `backend-nestjs` | Backend NestJS — feature modules, DI, Prisma, JWT, microservices | 27 | engineering |
-| `backend-nextjs` | Next.js full-stack — App Router, RSC, Server Actions, SEO, AI SDK | 24 | engineering |
+| `backend-nextjs` | Next.js full-stack — App Router, RSC, Server Actions, SEO, AI SDK | 25 | engineering |
 
 ### Frontend & Design
 
 | Profile | Stack | Skills | Agents |
 |---------|-------|--------|--------|
-| `frontend-react-vite` | React + Vite + TypeScript | 17 | engineering |
+| `frontend-react-vite` | React + Vite + TypeScript | 18 | engineering |
 | `design` | Figma, UX review, design system, handoff | 10 | product |
 
 ### Mobile
@@ -304,7 +304,7 @@ It ships the in-editor skills that operate and extend the MCP (`unreal-mcp`, `cr
 | ClickUp | `/clickup` | `+clickup` |
 | Figma | `/figma`, `/figma-to-code`, `/figma-tokens` | `+design` |
 | Atlassian (Confluence) | `/confluence-expert`, `/atlassian-templates` | `+agile` |
-| TestRail + BrowserStack | `/playwright-pro` (ships its own `.mcp.json`) | `+testing` |
+| TestRail + BrowserStack | `/playwright-pro` (ships its own `.mcp.json`) | `+testing`, `frontend-react-vite`, `backend-nextjs` |
 
 `/jira-tickets` is the exception: it talks to the Jira REST API v3 over `curl`, not MCP.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-code-arcane",
-  "version": "2.15.0",
+  "version": "2.16.0",
   "description": "Skills, agents, hooks and rules for Claude Code — installable via npx claude-code-arcane",
   "type": "module",
   "bin": {

package/profiles/backend-nextjs.yaml

@@ -23,6 +23,7 @@ skills:
   # Frontend quality
   - accessibility
   - performance
+  - playwright-pro
   # Ops & quality
   - testing
   - deps-audit

package/profiles/frontend-react-vite.yaml

@@ -20,6 +20,7 @@ skills:
   - file-uploads
   - frontend-dev
   - csp-headers
+  - playwright-pro
 
 rules:
   universal:

package/profiles/frontend.yaml

@@ -22,6 +22,7 @@ skills:
   - file-uploads
   - frontend-dev
   - csp-headers
+  - playwright-pro
 
 rules:
   universal:

package/rules/frontend-code.md

@@ -55,6 +55,6 @@ paths:
   2. Screenshots at 320, 768, 1024 and 1440 px wide, in both themes if the app has a dark mode.
   3. Walk the flow you changed: clicks, forms, navigation.
   4. Keyboard: every control in the flow is reachable with Tab, usable with Enter or Space, and shows a visible focus.
-  5. Keep the screenshots and show them as evidence.
-- If Playwright is not installed, propose installing it once (`npm i -D @playwright/test`, then `npx playwright install chromium`). If the user declines, close the task with "visual result not verified".
+  5. Save the screenshots to files and show them as evidence; the goal review gets their paths.
+- If Playwright is not installed, propose setting it up once with `/playwright-pro init` (or `npm i -D @playwright/test`, then `npx playwright install chromium`). If the user declines, close the task with "visual result not verified".
 - In React Native or Flutter Playwright does not apply: say what was not verified visually.

package/rules/implementation-workflow.md

@@ -34,9 +34,9 @@ Use AskUserQuestion exactly like this:
 
 ## After selection
 
-- **Plan + Goal:** First define the verifiable session goal with validation criteria. Then EnterPlanMode and design the implementation plan linked to the goal. Plan includes explicit stop conditions (goal met, blocker, scope creep). After approval, create tasks and execute. After each significant step, check progress against the goal. When goal is met, STOP and run validation.
+- **Plan + Goal:** First define the verifiable session goal with validation criteria. Then EnterPlanMode and design the implementation plan linked to the goal. Plan includes explicit stop conditions (goal met, blocker, scope creep). After approval, create tasks and execute. After each significant step, check progress against the goal. When goal is met, STOP and run the goal review below.
 - **Action Plan:** Use EnterPlanMode, design the approach, get approval, create tasks, then implement step by step. No formal goal — implement until the plan is done.
-- **Goal-driven:** Help the user define a verifiable goal statement and 2-4 checkpoints, create tasks, implement toward each checkpoint. No formal plan.
+- **Goal-driven:** Help the user define a verifiable goal statement and 2-4 checkpoints, create tasks, implement toward each checkpoint. No formal plan. When the last checkpoint is met, run the goal review below.
 - **Directo:** Proceed immediately without ceremony.
 
 ## Progress file
@@ -63,6 +63,26 @@ Not verified: <what has not been checked yet>
 
 Directo and Action Plan tasks do not need it.
 
+## Goal review
+
+In **Plan + Goal** and **Goal-driven** mode, whoever did the work does not decide it is done. When the goal looks met, start one `general-purpose` subagent with a clean context. Its prompt carries only:
+
+- the goal and the criteria from `active.md`;
+- the diff against the base branch, untracked files included;
+- how to verify: test, build and type-check commands, and how to start the app;
+- if the task changed a web UI: the paths of the Playwright screenshots, or that the user declined Playwright;
+- the instructions below, verbatim.
+
+Never pass your reasoning or a summary of the conversation: the reviewer judges the work, not the story behind it.
+
+> You are reviewing finished work against its goal. Do not trust any reported result: run every verification yourself. Check each criterion against the code and your own runs. If the diff touches authentication, user input, database queries, file system paths, external APIs, cryptography or payments, also check that input is validated at the boundary, queries are parameterized, no secret is in code or logs, every new path checks authorization, and errors leak no internals. If the task changed a web UI, there are no Playwright screenshots and you cannot produce them, the verdict is FAIL, unless the user declined Playwright: then note "visual result not verified". Answer with `PASS` or `FAIL` on the first line, then one line per criterion with its evidence (the command and its result, or `file:line`), then what is missing.
+
+Then:
+
+1. Show the user the reviewer's verdict as it came, before your own comments.
+2. **FAIL:** fix what it found and review again with a new subagent. After a second FAIL, stop and bring both verdicts to the user.
+3. **PASS:** close `active.md` with the verdict.
+
 ## Before writing new code
 
 In every mode, search in this order and take the first option that fully works: