@appsforgood/next-supabase-kit 0.3.0 → 0.4.1

package/skills/optional/docs/SKILL.md

@@ -0,0 +1,10 @@
+---
+name: docs
+description: Optional. Use when updating USER_GUIDE.md or project docs after a significant change.
+---
+
+# Docs (optional)
+
+Update only the docs that users need. Do not restore the old 17-doc operating system.
+
+Add with `agent-kit add skill docs`.

package/skills/optional/ui-polish/SKILL.md

@@ -0,0 +1,10 @@
+---
+name: ui-polish
+description: Optional. Use for a focused UI polish loop after the main design pass.
+---
+
+# UI Polish (optional)
+
+Improve hierarchy, spacing, states, and mobile fit without changing product scope. Still requires desktop and mobile screenshots via `browser-qa`.
+
+Add with `agent-kit add skill ui-polish`.

package/skills/optional/upgrade/SKILL.md

@@ -0,0 +1,10 @@
+---
+name: upgrade
+description: Optional. Use when updating this pack or framework versions. Prefer agent-kit update over re-init.
+---
+
+# Upgrade (optional)
+
+Run `agent-kit update` on a branch. Local edits win or become conflicts. Do not delete user files.
+
+Add with `agent-kit add skill upgrade`.

package/skills/owasp-security-review/SKILL.md

@@ -0,0 +1,23 @@
+---
+name: owasp-security-review
+description: Use when reviewing auth, APIs, Server Actions, uploads, webhooks, dependencies, secrets, or data mutations.
+---
+
+# OWASP Security Review
+
+## Use when
+
+Auth, APIs, Server Actions, external fetches, uploads, webhooks, dependencies, or mutations.
+
+## Checks
+
+- Broken access control and IDOR are tested.
+- Inputs are validated with safe schemas.
+- Outputs are encoded; secrets are not logged or bundled.
+- SSRF risk is addressed for server-side fetches.
+- Dependencies are reviewed for known critical CVEs.
+- Errors are explicit without leaking internals.
+
+## Done when
+
+Each finding has severity, affected behavior, and a concrete fix. User-visible auth failures were seen in the browser.

package/skills/planning/SKILL.md

@@ -0,0 +1,25 @@
+---
+name: planning
+description: Classify work, pick an owner, and name the evidence QA must capture. Use when the request is ambiguous, cross-layer, or needs a specialist.
+---
+
+# Planning
+
+## Use when
+
+Planning, roadmaps, “what should we do,” or any request that needs an owner.
+
+## Steps
+
+1. Read enough of the repo to name affected routes and data.
+2. Pick one owner: `app-engineer`, `security`, `design`, `qa`, or `copy`.
+3. Add Security for auth/data/secrets, Design for UI, QA for behavior/UI, Copy for public words.
+4. If the change is user-visible, list the desktop and mobile screenshots QA must capture.
+
+## Done when
+
+Owner, extra reviewers, preserved behavior, and required screenshots are explicit. No product code was written.
+
+## Reject
+
+Implementing in the planning pass. Asking one chat to play every role.

package/skills/postgres-migrations/SKILL.md

@@ -0,0 +1,21 @@
+---
+name: postgres-migrations
+description: Use for schema changes, migrations, constraints, indexes, and rollback risk.
+---
+
+# Postgres Migrations
+
+## Use when
+
+Creating or changing tables, constraints, indexes, functions, triggers, or seed data.
+
+## Checks
+
+- Migrations are additive or have an explicit rollback path.
+- Constraints protect integrity; indexes match real query paths.
+- RLS is planned in the same change when the table holds user or tenant data.
+- Generated types are refreshed after schema changes.
+
+## Done when
+
+Migration order and rollback risk are named. User data is not left unprotected.

package/skills/product-copy/SKILL.md

@@ -0,0 +1,54 @@
+---
+name: product-copy
+description: Use for headlines, CTAs, empty states, and conversion copy. Review rendered screenshots, not only strings in source.
+---
+
+# Product Copy
+
+## Use when
+
+Landing pages, CTAs, positioning, onboarding, empty states, pricing copy, or the public user guide (`USER_GUIDE.html`).
+
+## Audience
+
+Engineers and coding agents on a Next.js + Supabase repo who already have Cursor, Claude, Codex, Copilot, or Antigravity. They do not need a manifesto. They need to know **who to @**, **what to paste**, and **what “done” looks like**.
+
+## Positioning (this product)
+
+Name the specialist. Prove the screen. Six agents, twelve skills, five IDEs. QA is two screenshots, not a file diff.
+
+Do not describe this as an “agent operating system,” a copilot marketplace, or “AI-powered delivery.”
+
+## Voice
+
+Direct, specific, slightly dry. Prefer verbs: ask, paste, open, capture, reject.
+
+Use: specialist, owner, screenshot, desktop, mobile, fail-closed, paste, Planner, browser-qa.  
+Avoid: supercharge, seamless, unlock, copilot for X, 10x, enterprise-grade, magic, revolutionize.
+
+## Headline test
+
+If the headline could sell GitHub Copilot, Cursor, or any agent marketplace, rewrite it.
+
+Good: `Ask one specialist. Then open the running UI.`  
+Bad: `Supercharge your AI workflow with agents and skills.`
+
+## CTA test
+
+A CTA is a command or a pasteable prompt, not “Get started.”
+
+Good: `Paste this to Planner` followed by the plan prompt.  
+Good: `npx --yes @appsforgood/next-supabase-kit init --activate all`  
+Bad: `Start building today`.
+
+## Checks
+
+- Audience, pain, and outcome are specific to this product.
+- Claims are backed or marked as assumptions. Do not invent user counts or “best-in-class.”
+- Headlines could not fit any competitor.
+- CTAs say what happens next.
+- Review the words on a screenshot for truncation, wrapping, and hierarchy. Copy that only exists in markdown is not approved for a public HTML page.
+
+## Done when
+
+Copy is specific and the rendered screenshot shows the key line and CTA clearly on desktop and mobile. Copy then runs `deslop` as the last pass — this skill is not the end of the run.

package/skills/ship/SKILL.md

@@ -0,0 +1,22 @@
+---
+name: ship
+description: Use before release. Check env vars, migration order, smoke, and rollback. User-visible releases still need browser-qa evidence.
+---
+
+# Ship
+
+## Use when
+
+Preparing to deploy, promote, or roll back.
+
+## Checks
+
+- Production-critical env vars are named.
+- Migration order and rollback are explicit.
+- Smoke of the primary path passed.
+- User-visible changes have desktop and mobile screenshot evidence from `browser-qa`.
+- Secrets are not in the repo or client bundle.
+
+## Done when
+
+Go / no-go is explicit, with commands run and rollback named.

package/skills/supabase-auth-rls/SKILL.md

@@ -0,0 +1,23 @@
+---
+name: supabase-auth-rls
+description: Use for Supabase Auth, SSR clients, middleware, sessions, Row Level Security, Storage policies, and service-role usage.
+---
+
+# Supabase Auth And RLS
+
+## Use when
+
+Supabase Auth, SSR clients, middleware, sessions, tables, policies, Storage, or service-role operations.
+
+## Checks
+
+- RLS is enabled on user-owned and tenant-owned tables.
+- Policies enforce ownership and tenant boundaries.
+- Service-role keys stay server-only.
+- Auth middleware refreshes sessions safely.
+- Storage buckets have explicit policies.
+- IDOR is considered and tested at the policy boundary.
+
+## Done when
+
+A table that stores user data cannot be read or written across users without a failing policy. UI checks are not treated as authorization.

package/skills/testing-qa/SKILL.md

@@ -0,0 +1,27 @@
+---
+name: testing-qa
+description: Use when adding unit, regression, or smoke tests. Visual proof of a screen always also uses browser-qa.
+---
+
+# Testing QA
+
+## Use when
+
+Adding or reviewing tests, smoke checks, or regression coverage.
+
+## Checks
+
+- Core logic has unit tests.
+- Preserved behavior has regression tests.
+- Critical flows have Playwright or equivalent smoke tests.
+- Auth and mutation paths are prioritized.
+- Network failure, empty, and error behavior is covered.
+- Gaps are named when infrastructure is missing.
+
+## Visual proof
+
+User-visible screens also require `browser-qa`. This skill does not replace screenshots.
+
+## Done when
+
+Commands run, results, and residual gaps are listed.

package/templates/next-supabase/AGENTS.md

@@ -1,140 +1,30 @@
-# Agent Setup
+# Agents
 
-This project uses explicit agent roles so implementation, security, quality, and documentation do not collapse into one vague assistant.
+This repo uses a small specialist pack. **Agent** = who. **Skill** = how. **Tool** = what they must use.
 
-Use `.agent-kit/agent-roster.json` as the default council contract. Use `MODEL_ROUTING.md` and `.agent-kit/model-routing.json` to choose model profiles for each agent. Before meaningful work, read `.agent-kit/project-context.json`, `.agent-kit/project-context.md`, and `.agent-kit/agent-briefs.md` when present, then apply active corrections from `.agent-kit/corrections/project-rules.json` and `.agent-kit/corrections/agent-rules.json`. When a request is ambiguous, planning-oriented, or cross-layer, start with Planner and follow the matching workflow in `AGENT_ROSTER.md`. Use `ASSISTANT_ADAPTERS.md` to confirm which AI coding tools load these instructions and how model selection is handled. Record meaningful council sessions in `COUNCIL.md` or the local Agent Studio files under `.agent-kit/council-sessions/`.
+Read `USER_GUIDE.md` for how to invoke these in Cursor, Claude, Codex, Copilot, and Antigravity.
 
-When `.agent-kit/orchestrator.json` is enabled, treat `agent-kit orchestrate validate`, plan/status output, approvals, runtime events, and worktree/commit state as the executable source of truth. IDE delegation is not proof that the graph ran. Never bypass a paused approval, capability mismatch, Docker/host policy, or the runtime rule that forbids automatic merge, push, pull request, deployment, and migration application.
+## Screenshot rule
 
-## Planner
+A user-visible change is not done until someone opened the running UI, captured desktop and mobile screenshots, and reviewed those images. Reading TSX is not QA.
 
-Owns planning, scope breakdown, sequencing, and council routing before implementation starts.
+## Who to ask
 
-Responsibilities:
-- Convert requests into phased, checkable work.
-- Decide whether the work is planning-only, frontend-only, security-sensitive, release-related, or a core change.
-- Select or confirm the model profile from `MODEL_ROUTING.md` before delegating complex work.
-- Route core changes to Lead Architect before implementation.
-- Name required handoffs and acceptance evidence.
-- Record council-session workflow, decision, risk, next handoff, and evidence for meaningful multi-agent work.
-- Compare proposed work against `QUALITY_GATES.md` and name the required evidence level.
-- Keep roadmap and delivery status current.
+| Ask | Agent |
+| --- | --- |
+| Plan, scope, who owns this | `@planner` |
+| Implement Next.js or Supabase | `@app-engineer` |
+| Auth, RLS, secrets, OWASP | `@security` |
+| UI looks wrong / generic | `@design` |
+| Is this done? | `@qa` |
+| Headlines, CTAs, empty states | `@copy` |
 
-## Lead Architect
+Do not ask one chat to be all six.
 
-Owns system design, affected-layer mapping, tradeoffs, and final implementation direction.
+## Handoff
 
-Responsibilities:
-- Confirm existing behavior before changing it.
-- Map each change across data, business logic, presentation, auth, and deployment.
-- Decide whether logic belongs in Supabase SQL/RLS, Route Handlers, Server Actions, Server Components, or client state.
-- Keep changes scoped and preserve behavioral contracts.
+Planner names the owner. Security joins auth/data/secret work. Design joins user-facing screens. QA joins any behavior or UI change and **must use the browser**. Copy joins public/conversion copy. Stop there.
 
-## Next.js Engineer
+## Skills
 
-Owns App Router implementation, Server Components, Client Components, Route Handlers, Server Actions, forms, data loading, caching, and UI state.
-
-Responsibilities:
-- Keep server/client boundaries explicit.
-- Avoid exposing secrets or privileged data to client bundles.
-- Provide loading, error, empty, and success states.
-- Preserve accessibility and responsive behavior.
-
-## Supabase/Postgres Engineer
-
-Owns schema, migrations, RLS policies, Auth integration, Storage policies, SQL functions, triggers, indexes, and seed data.
-
-Responsibilities:
-- Enforce authorization in Postgres RLS, not only in UI code.
-- Keep service-role access server-only.
-- Add constraints and indexes that protect data integrity and performance.
-- Document migration order and rollback risks.
-
-## Security Reviewer
-
-Owns OWASP Top 10 review, auth boundary review, IDOR prevention, input validation, output encoding, SSRF prevention, dependency risk, and secret handling.
-
-Responsibilities:
-- Review all data mutations and privileged reads.
-- Verify least privilege for Supabase, API routes, automation tokens, and storage.
-- Flag unsafe dependencies or misconfiguration.
-- Ensure every failure path is explicit and observable.
-
-## Frontend Design Lead
-
-Owns content-first creative direction, visual quality, design systems, accessibility, and prevention of generic AI-looking UI.
-
-Responsibilities:
-- Maintain `DESIGN.md` as the project visual identity and content-direction contract.
-- Require audience, user needs, content inventory, brand constraints, and creative-direction options before implementation.
-- Require reference-set evidence, anti-references, source-safety notes, and a design critique verdict before accepting significant frontend work.
-- Require a frontend product-quality scorecard before accepting significant frontend work.
-- Reject generic gradient heroes, vague SaaS copy, card soup, and fake dashboard metrics.
-- Prefer task-first screens, domain-specific hierarchy, real workflow affordances, and reusable components.
-- Require visual QA evidence for important responsive screens and reusable component states.
-- Maintain WCAG 2.1 AA, keyboard navigation, focus states, and mobile-first behavior.
-- Use design adapters for Stitch, Claude, Figma, or human review when visual direction is weak.
-
-## Marketing Copy Lead
-
-Owns positioning, value proposition, conversion copy, product voice, and UX copy for public-facing or conversion-facing surfaces.
-
-Responsibilities:
-- Maintain `MESSAGING.md` as the positioning, value proposition, voice, proof, objection, and CTA contract.
-- Ask discovery questions when audience, pain, outcome, differentiator, proof, objections, voice, or conversion goal is unclear.
-- Reject vague SaaS copy, unsupported AI claims, invented proof, and headlines that could fit any competitor.
-- Translate product facts into specific headlines, CTAs, onboarding copy, empty states, pricing copy, and objection handling.
-- Handoff public-facing copy to Frontend Design Lead so layout, hierarchy, imagery, and interaction tone reinforce the message.
-- Flag risky pricing, security, privacy, compliance, financial, legal, medical, or performance claims before release.
-
-## QA Engineer
-
-Owns tests, regression coverage, smoke checks, and acceptance evidence.
-
-Responsibilities:
-- Add unit coverage for core logic and edge cases.
-- Add regression tests for preserved behavior.
-- Add Playwright smoke coverage for auth and primary workflows.
-- Add screenshot or visual-regression evidence for high-risk UI changes.
-- Report test gaps explicitly when infrastructure is missing.
-
-## Documentation Maintainer
-
-Owns living markdown docs.
-
-Responsibilities:
-- Validate handoff evidence against `COUNCIL.md` and `.agent-kit/schemas/`.
-- Update `SPEC.md`, `DECISIONS.md`, `DOCS.md`, `ASSISTANT_ADAPTERS.md`, `MODEL_ROUTING.md`, `QUALITY_GATES.md`, `DESIGN.md`, `MESSAGING.md`, `STYLE_GUIDE.md`, `SECURITY.md`, `TESTING.md`, `DEPLOYMENT.md`, and `UPGRADE.md`.
-- Record decisions with context, decision, and consequences.
-- Keep docs actionable for another engineer or agent to continue safely.
-
-## Deployment/Observability Engineer
-
-Owns deployment config, environment variables, migrations, logs, monitoring, and rollback guidance.
-
-Responsibilities:
-- Verify production-critical env vars.
-- Confirm migration and release order.
-- Ensure errors are visible through logs or monitoring.
-- Define rollback and recovery steps for risky changes.
-
-## Default Handoff
-
-Use this order for feature work:
-
-1. Planner classifies the request, maps the workflow, and names the council.
-2. Planner starts or updates an Agent Studio session with `agent-kit session start` when the work is meaningful, risky, or cross-agent, then records fallback notes in `COUNCIL.md` if CLI tooling is unavailable.
-3. Lead Architect maps affected layers and preserved behavior.
-4. Supabase/Postgres Engineer handles schema, RLS, and migrations when data/auth changes are involved.
-5. Next.js Engineer implements runtime behavior and UI.
-6. Frontend Design Lead owns content-first creative direction and reviews UX quality/accessibility when user-facing screens change.
-7. Marketing Copy Lead owns positioning, value proposition, conversion copy, product voice, and UX copy when public-facing or conversion-facing copy changes.
-8. Security Reviewer checks OWASP, auth, data boundaries, dependencies, external calls, and secrets.
-9. QA Engineer adds and runs tests.
-10. Documentation Maintainer updates living docs and council evidence.
-11. Deployment/Observability Engineer verifies release and upgrade readiness.
-12. The active agent records decisions, handoffs, corrections, artifacts, required-output status, verification, and status with `agent-kit session ...` commands, then runs `agent-kit session render` so `index.md` and `transcript.md` are current. Run `agent-kit studio export` when the user needs a local visual session view.
-
-## Council Rule
-
-Core changes cannot skip Planner or Lead Architect. Frontend changes cannot skip content/brand intake, creative-direction rationale, reference-led critique, product-quality scorecard, visual QA evidence, and Frontend Design Lead review. Public-facing or conversion-facing copy changes cannot skip Marketing Copy Lead discovery questions, value proposition, proof, objection, voice/tone, and CTA review. Auth, RLS, data mutation, dependency, secret, external-call, and release-risk changes cannot skip Security Reviewer. Behavior changes cannot skip QA evidence. Significant changes cannot skip Documentation Maintainer. Meaningful multi-agent work cannot skip a decision, risk, next-handoff, required-output status, and evidence record. Human corrections must be recorded before continuing work, and durable project or agent corrections must be applied in future sessions. Work is not best-practice ready until it satisfies the relevant `QUALITY_GATES.md` evidence level.
+Default skills live in `.cursor/skills/*/SKILL.md` (and the matching Claude/Codex/Antigravity copies). QA of a screen always uses `browser-qa`, not `testing-qa` alone. Copy finishes public words with `deslop`. Planner uses `planning` and names owners; it does not run the other agents. Each agent file points at `catalog.json` for the full skill list.

package/templates/next-supabase/CLAUDE.md

@@ -1,39 +1,7 @@
-# Claude Code Project Instructions
+# Claude Code
 
-This repository uses Agent Kit. Treat the following as the source of truth for council routing, project context, correction rules, model profiles, quality gates, and handoff evidence:
+This repo uses a small agent and skill pack. Read `AGENTS.md` and `USER_GUIDE.md`.
 
-- `AGENTS.md`
-- `AGENT_ROSTER.md`
-- `.agent-kit/agent-roster.json`
-- `MODEL_ROUTING.md`
-- `.agent-kit/model-routing.json`
-- `.agent-kit/project-context.json`
-- `.agent-kit/project-context.md`
-- `.agent-kit/agent-briefs.md` when present
-- `.agent-kit/corrections/project-rules.json`
-- `.agent-kit/corrections/agent-rules.json`
-- `COUNCIL.md`
-- `.agent-kit/council-sessions/`
-- `QUALITY_GATES.md`
+Subagents live in `.claude/agents/`. Use the matching subagent instead of one generic thread.
 
-## Subagents
-
-Project subagents live in `.claude/agents/*.md` and are generated from `.agent-kit/agent-roster.json` when you run:
-
-```sh
-agent-kit init --activate claude
-```
-
-Use the matching subagent for the active workflow instead of treating every request as a generic implementation pass.
-
-## Validation
-
-```sh
-agent-kit audit --min-readiness baseline-setup
-```
-
-Use `agent-kit session checkpoint --file <json>` to batch-record council evidence instead of many individual session commands.
-
-## Model Selection
-
-Use Claude Code model settings with the profiles in `MODEL_ROUTING.md`. Exact model names are dated recommendations — review when provider docs change.
+A user-visible change is not done until someone opened the running UI, captured desktop and mobile screenshots, and reviewed those images. If you cannot open a browser, use the Playwright fallback in `skills/browser-qa/SKILL.md`.

package/BEST_PRACTICE_EVIDENCE.md

@@ -1,45 +0,0 @@
-# Best-Practice Evidence Matrix
-
-This repository treats the 100-repo research pass as input, not proof. A practice only counts as part of the kit when it is promoted into at least one durable artifact and one validation path.
-
-## Evidence Rule
-
-- Research findings identify repeated gaps or strong patterns.
-- Promoted behavior must appear in installed templates, agents, skills, checklists, schemas, prompts, or repository workflows.
-- Validation must exist through audit checks, schema contracts, tests, release gates, install smoke, or documented external repository settings.
-- Fresh installs are only `baseline-setup` until project-specific evidence replaces starter placeholders.
-
-## Promotion Matrix
-
-| Research signal | Scan evidence | Promoted behavior | Installed or repo artifact | Validation path |
-| --- | --- | --- | --- | --- |
-| Supabase/Auth/RLS expectations are often weak or hard to discover. | 88 of 100 findings had weak or non-discoverable Supabase/Auth/RLS signals. | Make RLS, auth boundaries, service-role isolation, and migration review explicit defaults. | `templates/next-supabase/SECURITY.md`, `templates/next-supabase/SPEC.md`, `skills/supabase-auth-rls.md`, `skills/postgres-migrations.md`, `checklists/rls.md`. | `agent-kit audit`, template hash checks, install smoke, public-readiness tests. |
-| Agent handoff and AI-workflow contracts are immature. | 66 of 100 findings had immature agent handoff or AI-workflow signals. | Require Planner-first routing, Lead Architect ownership for core changes, council handoffs, and evidence records. | `rosters/next-supabase-default-council.json`, `templates/next-supabase/COUNCIL.md`, `schemas/agent-roster.schema.json`, `schemas/council-session.schema.json`, `skills/planning-council.md`, `skills/agent-handoff-tracing.md`. | Roster schema validation, council-session schema validation, `agent-kit audit`, `tests/audit.test.ts`, `tests/public-readiness.test.ts`. |
-| Agent instructions need to load in the tools teams actually use. | Follow-up review of current Codex/AGENTS.md, GitHub Copilot, VS Code, Cursor, and Claude Code instruction surfaces showed that each tool has its own activation path. | Keep the council roster as the source of truth and ship thin adapters for AGENTS.md-compatible tools, Copilot instructions, Cursor rules, and Claude Code subagents. | `templates/next-supabase/ASSISTANT_ADAPTERS.md`, `assistant-adapters/*`, `AGENTS.md`, `AGENT_ROSTER.md`, `.agent-kit/agent-roster.json`. | `agent-kit audit`, public-readiness tests, install smoke, project-specific adapter evidence. |
-| Reusable kits need a safe upgrade lifecycle. | Follow-up review of framework and tooling upgrade practices showed repeated use of upgrade guides, codemods, migration history, diff flows, release notes, and rollback evidence. | Separate initial install from upgrade review and require diff, update, migration, audit, release-note, and rollback evidence. | `UPGRADE.md`, `templates/next-supabase/UPGRADE.md`, `skills/upgrade-maintenance.md`, `checklists/upgrade.md`, `prompts/upgrade-review.md`. | `agent-kit audit`, public-readiness tests, install smoke, release check. |
-| Accessibility evidence is commonly too implicit. | 57 of 100 findings had weak accessibility signals. | Make WCAG-oriented review part of frontend and QA work instead of a late checklist. | `skills/accessibility-wcag.md`, `checklists/accessibility.md`, `checklists/frontend-quality.md`, `templates/next-supabase/TESTING.md`, `templates/next-supabase/STYLE_GUIDE.md`. | Public-readiness tests, install smoke, project maturity evidence in `QUALITY_GATES.md`. |
-| Security expectations are often incomplete. | 54 of 100 findings had implicit or incomplete security expectations. | Treat OWASP, least privilege, input validation, output encoding, dependency risk, and disclosure process as release concerns. | `agents/security-reviewer.md`, `skills/owasp-security-review.md`, `checklists/owasp.md`, `SECURITY.md`, `.github/workflows/codeql.yml`, `.github/workflows/dependency-review.yml`. | `npm audit --audit-level=moderate`, Dependency Review, CodeQL, public-readiness tests, release check. |
-| Reusable components and tokens do not prevent generic AI-looking UI. | Follow-up design review found frontend scoring over-weighted components, tokens, and states. | Require content-first creative direction, brand/content intake, real workflow screens, and screenshot evidence. | `templates/next-supabase/DESIGN.md`, `skills/content-first-design.md`, `skills/frontend-design-system.md`, `agents/frontend-design-lead.md`, `prompts/brand-content-intake.md`, `prompts/creative-direction-matrix.md`, `design-briefs/*`. | Frontend-change roster requirements, `agent-kit audit`, public-readiness tests, screenshot review prompt. |
-| Frontend critique needs reference and distinctiveness evidence. | Follow-up review of design-system and component-state practices showed that strong primitives and screenshots do not prove a product-specific visual direction. | Require reference sets, anti-references, source-safety notes, and a written design critique verdict before accepting significant frontend work. | `skills/reference-led-design-critique.md`, `prompts/design-critique-gate.md`, `checklists/design-critique.md`, `templates/next-supabase/DESIGN.md`, `rosters/next-supabase-default-council.json`. | Frontend-change roster requirements, `agent-kit audit`, public-readiness tests, install smoke. |
-| Frontend distinctiveness needs proof, not taste. | Focused follow-up review of design-system, service-design, content, accessibility, and visual-testing guidance showed that a polished UI can still be interchangeable without first-screen proof, content fingerprint, safe reference learning, asset provenance, state proof, and visual QA proof. | Require a frontend distinctiveness benchmark before accepting significant UI work. | `skills/frontend-distinctiveness-benchmark.md`, `prompts/frontend-distinctiveness-benchmark.md`, `checklists/frontend-distinctiveness.md`, `templates/next-supabase/DESIGN.md`, `rosters/next-supabase-default-council.json`, `research/summaries/frontend-distinctiveness-benchmark-patterns.md`. | Frontend-change roster requirements, `agent-kit audit`, public-readiness tests, install smoke. |
-| Frontend acceptance needs a repeatable product-quality threshold. | Focused follow-up review of design-system, service-design, component-state, and accessibility guidance showed that good primitives do not prove product-specific quality. | Score significant UI work against user/task fit, content specificity, visual identity, information architecture, component states, accessibility and interaction, and source safety. | `skills/frontend-product-quality-rubric.md`, `prompts/frontend-product-quality-scorecard.md`, `checklists/frontend-product-quality.md`, `templates/next-supabase/DESIGN.md`, `rosters/next-supabase-default-council.json`. | Frontend-change roster requirements, `agent-kit audit`, public-readiness tests, install smoke. |
-| Visual QA needs a path beyond manual taste review. | Follow-up visual-testing review identified Storybook, Playwright screenshots, Chromatic, Argos, Loki, and baseline evidence as repeatable patterns. | Provide visual QA tiers that scale from screenshot review to regression evidence. | `skills/visual-regression-qa.md`, `checklists/visual-regression.md`, `prompts/visual-qa-plan.md`, `templates/next-supabase/TESTING.md`. | Public-readiness tests, `QUALITY_GATES.md` maturity evidence, downstream visual QA artifacts. |
-| Public OSS maintainability needs more than a package tarball. | Repository-health follow-up identified structured intake, ownership, labels, support, and governance as durable signals. | Ship contributor intake, labels, CODEOWNERS, support, conduct, governance, and repository settings guidance. | `.github/ISSUE_TEMPLATE/*`, `.github/pull_request_template.md`, `.github/CODEOWNERS`, `.github/labels.yml`, `SUPPORT.md`, `GOVERNANCE.md`, `REPOSITORY_SETTINGS.md`. | Public-readiness tests, PR labeler workflow, documented branch and repository settings. |
-| Supply-chain trust must be visible before publish. | Supply-chain follow-up identified OIDC publishing, provenance, dependency review, Scorecard, SBOMs, workflow controls, and release gates. | Use Trusted Publishing, avoid long-lived npm publish tokens, generate and attest a package-rooted CycloneDX SBOM for every tarball, and verify each public package before creating the source release. | `.github/workflows/release.yml`, `.github/workflows/scorecard.yml`, `.github/workflows/dependency-review.yml`, `SUPPLY_CHAIN.md`, `scripts/release-check.mjs`, `scripts/sbom-check.mjs`. | `npm run release:check`, root/runtime SBOM checks, OpenSSF Scorecard, Dependency Review, npm Trusted Publishing, SBOM attestations, pack dry runs. |
-| Best-practice claims need a maturity model. | Follow-up review showed a green build alone does not prove best-practice readiness. | Separate setup validity from project evidence and best-practice candidacy. | `templates/next-supabase/QUALITY_GATES.md`, `schemas/audit-report.schema.json`, `skills/best-practice-maturity-review.md`, `src/install/audit.ts`. | `agent-kit audit --min-readiness`, audit-report schema validation, install smoke, release check. |
-| Downstream adoption evidence must stay current. | Current read-only dogfood audits of two older installs both produced `11 pass / 20 warn / 7 fail`, proving that later hardening made older installs drift below baseline setup. | Publish a sanitized dogfood summary and keep detailed local-path evidence repo-only. Treat stale dogfood findings as upgrade inputs. | `DOGFOOD.md`, `dogfood/*.md`, `UPGRADE.md`, `agent-kit audit`, `agent-kit update`, `tests/public-readiness.test.ts`. | Public-readiness tests, release check, read-only dogfood audit snapshots, package dry run. |
-| Older installs need a conflict-safe upgrade proof. | Dogfood audits showed both older installs lacked current roster schemas, assistant adapters, maturity gates, upgrade docs, and design critique assets. | Add a deterministic old-install fixture that proves diff previews missing/conflicting assets and update adds missing current assets while preserving customized docs through conflicts. | `tests/update.test.ts`, `src/install/diff.ts`, `src/install/install.ts`, `UPGRADE.md`, `DOGFOOD.md`. | Unit tests, audit report on upgraded fixture, release check. |
-| Public examples must not drift from CLI behavior. | Repeated package hardening changed installed docs, roster messages, manifest hashes, and audit output. Hand-maintained examples can look trustworthy while going stale. | Regenerate a clean install with the built CLI and compare committed example roster, stable manifest fields, audit output, and tree summary before release. | `examples/next-supabase-installed/*`, `scripts/example-check.mjs`, `scripts/release-check.mjs`. | `npm run examples:check`, `npm run release:check`, public-readiness tests. |
-| Package version metadata must agree before release. | Public npm release workflows can publish a package whose lockfile, changelog, or GitHub tag no longer matches `package.json`. | Validate SemVer shape, package-lock root version, changelog section, and release tag before release gates proceed. | `scripts/version-check.mjs`, `package.json`, `package-lock.json`, `CHANGELOG.md`, `.github/workflows/release.yml`. | `npm run version:check`, `npm run release:check`, public-readiness tests. |
-
-## What This Does Not Claim
-
-- A fresh install is not a completed best-practice project.
-- The kit does not copy source code, policy wording, or brand systems from reviewed repositories.
-- External settings such as branch protection, npm Trusted Publishing, and private vulnerability reporting still need to be configured in GitHub and npm.
-- Tool-specific adapters still need to be activated in each downstream project and verified in `ASSISTANT_ADAPTERS.md`.
-- Real upgrade evidence still needs to be recorded per downstream project in `UPGRADE.md`.
-- Real frontend quality still requires project-specific content, creative direction, screenshot review, and visual evidence.
-- Real frontend distinctiveness still requires project-specific references, anti-references, source-safety review, and a critique verdict.
-- Real frontend distinctiveness still requires first-screen proof, content fingerprint, asset provenance, state proof, visual QA proof, and product-specific acceptance evidence.
-- Public-safe dogfood summaries do not replace full downstream branch updates, adapter activation, or post-publish `npx` verification.