@appsforgood/next-supabase-kit 0.3.0 → 0.4.0

package/MAINTAINER_RELEASE.md

@@ -1,100 +0,0 @@
-# Maintainer Release Evidence
-
-Use this checklist when shipping `@appsforgood/next-supabase-kit` releases. It aligns kit maintainer practice with the **Strong** tier in `QUALITY_GATES.md`: council sessions record workflow, decision, risk, next handoff, required outputs, and evidence.
-
-For loop patterns and safe automation limits, see [LOOP_CODING.md](LOOP_CODING.md). For publish steps, see [PUBLISH.md](PUBLISH.md).
-
-## When To Open A Session
-
-Start `agent-kit session` (or a `COUNCIL.md` entry) when the release includes any of:
-
-- CLI or install behavior changes
-- New or changed IDE adapter surfaces (Cursor, Codex, Claude, Copilot, Antigravity)
-- Audit, roster, schema, or Agent Studio contract changes
-- Security-sensitive dependency or publish pipeline changes
-- Multi-agent work spanning Planner → Architect → QA
-
-Skip a formal session only for typo-only doc fixes with no behavioral impact.
-
-## Bootstrap Maintainer Dogfood
-
-Maintainers run the kit locally on BaseRepo without committing the overlay:
-
-```bash
-npm run dogfood:init
-node dist/index.js adapter validate cursor
-node dist/index.js adapter validate codex
-```
-
-Generated paths (`.agent-kit/`, `.cursor/`, `.codex/`, root council docs from init) are **gitignored**. Kit source stays in `templates/`, `assistant-adapters/`, and tracked root docs such as `DOCS.md` and `SPEC.md`.
-
-## Release Session Workflow
-
-```bash
-agent-kit session start --workflow release --request "Release vX.Y.Z"
-agent-kit session decision --agent planner --decision "..." --risk "..." --next "lead-architect" --evidence "..."
-agent-kit session verify --command "npm run release:check" --result pass --notes "..."
-agent-kit session verify --command "npm run smoke:audit-gate" --result pass
-agent-kit session output changelog --status complete --evidence "CHANGELOG.md#X.Y.Z"
-agent-kit session output test-evidence --status complete --evidence "vitest + smokes green"
-agent-kit session output publish-evidence --status complete --evidence "npm run publish:verify or GitHub Release vX.Y.Z"
-agent-kit session render
-```
-
-After publish, append a short evidence block to [DOGFOOD.md](DOGFOOD.md) (public-safe, no local paths).
-
-## COUNCIL.md Mirror Template
-
-When Agent Studio CLI is unavailable, paste this block into root `COUNCIL.md` (maintainer overlay, gitignored) or into the PR description:
-
-```md
-## YYYY-MM-DD - Release vX.Y.Z
-
-- Workflow: release
-- Status: complete
-- Request: Ship @appsforgood/next-supabase-kit@X.Y.Z
-- Affected layers: CLI, install, adapters, docs, CI, deployment
-
-### Required Outputs
-
-| Output | Status | Evidence |
-| --- | --- | --- |
-| Phased checklist | Complete | ROADMAP / PR scope |
-| Architecture decision | Complete/N/A | DECISIONS.md or PR note |
-| Security review | Complete | Dependency audit in release:check; no secret in adapters |
-| Test evidence | Complete | npm run release:check; npm run smoke:audit-gate |
-| Adapter validation | Complete | npm run adapter:validate (all IDE templates) |
-| Docs impact | Complete | CHANGELOG.md, DOCS.md, PUBLISH.md if process changed |
-| Publish verification | Complete | npm run publish:verify or Release workflow green |
-
-### Handoffs
-
-| Agent | Decision | Risk | Next Handoff | Evidence |
-| --- | --- | --- | --- | --- |
-| Planner | Release scope approved | Missed breaking change | Lead Architect / QA | PR + CHANGELOG |
-| QA Engineer | release:check green | Residual flake | Documentation Maintainer | CI logs |
-| Documentation Maintainer | CHANGELOG + DOGFOOD updated | Stale public evidence | Deployment/Observability | DOGFOOD.md entry |
-
-### Verification
-
-| Command Or Review | Result | Notes |
-| --- | --- | --- |
-| npm run release:check | Pass | Includes adapter:validate |
-| npm run smoke:audit-gate | Pass | baseline-setup, 0 failures |
-| npm run publish:verify | Pass/Skipped | Required after registry publish |
-```
-
-## Pre-Merge Gate (BaseRepo)
-
-Every release PR must pass:
-
-1. `npm run release:check` (tests, build, package validate, smokes, **adapter validate all**, audit, pack dry-run)
-2. `npm run smoke:audit-gate`
-3. CHANGELOG section for the target version
-4. Session render or COUNCIL mirror with verification table filled in
-
-## Post-Publish
-
-1. Run `npm run publish:verify` after registry propagation (or confirm Release workflow verification).
-2. Update `DOGFOOD.md` with publish verification snapshot (no machine paths).
-3. Mark release items in `ROADMAP.md`.

package/REPOSITORY_SETTINGS.md

@@ -1,83 +0,0 @@
-# Repository Settings
-
-This file records the GitHub settings that must be applied outside git for the repository to operate as a public best-practice package.
-
-## Branch Protection
-
-Protect `main` with:
-
-- Require a pull request before merging.
-- Require at least one approval.
-- Require review from CODEOWNERS for owned paths.
-- Dismiss stale approvals when new commits are pushed.
-- Require conversation resolution before merge.
-- Require branches to be up to date before merge.
-- Require linear history.
-- Do not allow force pushes.
-- Do not allow deletions.
-- Restrict bypasses to maintainers only.
-
-Optional status checks, only after GitHub Actions entitlement is confirmed and the project deliberately chooses hosted CI as required:
-
-- `Verify package`
-- `Review dependency changes`
-- `Analyze JavaScript and TypeScript`
-- `Scorecard`
-
-With the default `githubActions.mode: "off"`, configure no required hosted status checks. GitHub billing, spending-limit, or pre-execution failures cannot be recovered inside workflow YAML and must not block commit/push or ordinary phase progression. Preserve equivalent local test, audit, dependency, and security evidence in the council session.
-
-## Release Environment
-
-Create environment `npm-publish` with:
-
-- Required reviewers enabled.
-- Prevent self-review enabled where available.
-- Deployment branches restricted to `main`.
-- No npm package-write token secrets. Automated publication must fail closed when Trusted Publishing is unavailable.
-- Required reviewers should protect manual non-dry-run dispatches without preventing the normal version-PR merge path.
-
-Under **Actions > General > Workflow permissions**, allow GitHub Actions to create pull requests. The version workflow has job-scoped `contents: write` and `pull-requests: write` permissions and uses that setting only to open or update the Changesets version PR.
-
-Create this npm Trusted Publisher for each of these package names:
-
-- `@appsforgood/next-supabase-kit`
-- `@appsforgood/agent-kit-runtime`
-
-Each trusted publisher must match:
-
-- Provider: GitHub Actions
-- Repository: `lukey662/agentsandskills`
-- Workflow: `release.yml`
-- Environment: `npm-publish`
-- Allowed action: `npm publish`
-
-## Security Settings
-
-Enable:
-
-- Private vulnerability reporting.
-- GitHub Security Advisories.
-- Dependabot alerts.
-- Dependabot security updates.
-- Code scanning alerts.
-- Secret scanning where available.
-- Push protection for detected secrets where available.
-
-## Issues, Discussions, And Labels
-
-Enable issues. Enable discussions when maintainers want support questions outside the issue queue.
-
-Create labels from `.github/labels.yml`. Required label families:
-
-- Type: `bug`, `enhancement`, `research`, `documentation`, `security`, `dependencies`
-- Area: `area: cli`, `area: agents`, `area: frontend`, `area: supabase`, `area: research`, `area: release`, `area: repo-health`
-- Status: `needs-triage`, `blocked`, `good first issue`, `help wanted`
-- Risk: `risk: security`, `risk: breaking-change`
-
-## GitHub Pages
-
-Enable GitHub Pages with source "Deploy from a branch", branch `main`, folder `/docs`. The minimal docs site lives at `docs/index.md` with the `jekyll-theme-minimal` theme configured in `docs/_config.yml`. Update `docs/index.md` when the CLI surface, readiness levels, or quick-start commands change.
-
-## Review Cadence
-
-Review these settings before every public release and after any workflow, release, permission, package, or security-policy change.

package/RESEARCH_CITATION_POLICY.md

@@ -1,26 +0,0 @@
-# Research Citation Policy
-
-This project uses public repository research to identify reusable setup patterns for agents, skills, documentation, security, testing, and frontend quality.
-
-## Public Package Policy
-
-- Publish generalized summaries, promoted decisions, and methodology.
-- Do not publish third-party source code copied from researched repositories.
-- Do not imply endorsement by repository owners, maintainers, vendors, or design-system teams.
-- Do not present popularity as proof of quality.
-- Treat scanned repositories as untrusted input.
-
-## Included Public Research Artifacts
-
-The npm package may include:
-
-- `research/scan-config.json`
-- `research/scan-plan.md`
-- `research/summaries/*`
-- `research/proposed-updates.md`
-
-Detailed per-repo findings, candidate lists, and raw scan outputs should stay out of the public package unless they receive separate citation and legal review.
-
-## How Findings Become Guidance
-
-Research findings are promoted only as generalized practices with a clear rationale. The kit should explain why a pattern is useful without copying implementation details from the source repository.

package/SUPPLY_CHAIN.md

@@ -1,57 +0,0 @@
-# Supply Chain Security
-
-The root kit and optional runtime are intended for public npm distribution. Release integrity is part of the product, not an optional operations detail.
-
-## Publish Identity
-
-- Public packages: `@appsforgood/next-supabase-kit` and `@appsforgood/agent-kit-runtime`.
-- Publish path: GitHub Actions release workflow through npm Trusted Publishing.
-- Authentication: short-lived GitHub OIDC identity only; automated publishing has no npm token fallback.
-- Environment: `npm-publish`.
-- Each npm package must have its own Trusted Publisher scoped to repository `lukey662/agentsandskills`, workflow `release.yml`, environment `npm-publish`, and allowed action `npm publish`.
-
-The workflow removes inherited npm token variables, supplies a token-free npm configuration, and requires the GitHub OIDC request context before publishing. A missing or incorrect package-level Trusted Publisher fails closed instead of switching authentication modes. Successful publication carries npm provenance tied to that workflow identity.
-
-The release workflow creates separate root/runtime tarballs and package-rooted CycloneDX SBOMs, uploads them as release evidence, and attests each SBOM against its exact tarball. Runtime publishes before root when both are new. Both public packages are verified before the matching GitHub release, so a partial npm publish cannot create an apparently successful source release.
-
-## Release Gates
-
-Before publish:
-
-- `npm ci`
-- `npm run release:check`
-- Public release review
-
-`npm run release:check` validates JSON assets, typechecks both workspaces, tests, builds both packages, runs install smoke, runs dependency audit, validates SBOM generation, and performs root/runtime package dry runs. The install smoke also inspects packaged public files for forbidden private-package text.
-
-`npm run sbom:check` validates that the lockfile-derived CycloneDX SBOM can be generated, includes runtime dependencies, and has no unresolved required dependency links. Optional platform-specific dependency links may be skipped when npm records optional package edges that are not present for the current install target.
-
-After publish:
-
-- `npm view @appsforgood/next-supabase-kit@<version> version`
-- `npm view @appsforgood/agent-kit-runtime@<version> version`
-- Clean install and import of `@appsforgood/agent-kit-runtime`
-- Clean install of both packages followed by root `doctor`, `init`, `audit --json` with zero failures, and `orchestrate validate --json`
-
-The release workflow and `npm run publish:verify` both use `scripts/post-publish-verify.mjs` for this post-publish verification path.
-
-## Repository Automation
-
-- Local `npm run release:check` is the default package verification and supply-chain gate.
-- Hosted CI may mirror package verification on push and pull request when Actions entitlement is deliberately enabled.
-- Dependency Review can block pull requests that introduce moderate or worse known vulnerabilities when hosted Actions is available; otherwise review `npm audit` and lockfile changes locally.
-- Dependabot proposes npm and GitHub Actions updates; workflow actions remain pinned to immutable commit SHAs with reviewed version comments.
-- CodeQL scans JavaScript/TypeScript code.
-- OpenSSF Scorecard publishes repository security posture as code-scanning evidence.
-- CODEOWNERS identifies default review ownership for source, templates, schemas, and workflows.
-- Release artifacts include an attested CycloneDX SBOM for the npm tarball.
-
-## Maintainer Rules
-
-- Do not use npm publish tokens for automation. Maintainer-local OTP publishing is an explicit recovery operation, not a workflow fallback.
-- Do not publish from unreviewed branches or untrusted workflow changes.
-- Treat workflow edits as release-risk changes requiring security and maintainer review.
-- Keep package-write token secrets absent from repository and environment configuration.
-- Keep package contents free of secrets, private downstream data, and copied third-party source.
-- Keep SBOM generation and attestation in the shared release path; do not publish an unattested tarball when the workflow is available.
-- Keep `allowScripts` approvals version-pinned to reviewed required native/build packages. Explicitly deny optional package scripts that are not needed.

package/agents/deployment-observability-engineer.md

@@ -1,13 +0,0 @@
-# Deployment/Observability Engineer Agent
-
-## Purpose
-
-Own release safety, environment configuration, migrations, logs, monitoring, and rollback.
-
-## Responsibilities
-
-- Verify env vars and server-only secrets.
-- Confirm migration and deploy order.
-- Ensure production errors are observable.
-- Define smoke checks after deployment.
-- Document rollback steps.

package/agents/docs-maintainer.md

@@ -1,17 +0,0 @@
-# Documentation Maintainer Agent
-
-## Purpose
-
-Keep living docs accurate enough for another engineer or agent to continue safely.
-
-## Responsibilities
-
-- Update `SPEC.md` after functional changes.
-- Update `DECISIONS.md` for meaningful tradeoffs.
-- Update `DOCS.md` for workflows and setup.
-- Update `COUNCIL.md` for meaningful handoff evidence.
-- Update `QUALITY_GATES.md`, `DESIGN.md`, `STYLE_GUIDE.md`, `SECURITY.md`, `TESTING.md`, `DEPLOYMENT.md`, and `UPGRADE.md` when standards change.
-
-## Rule
-
-Docs and council evidence are part of the implementation surface, not optional cleanup.

package/agents/frontend-design-lead.md

@@ -1,22 +0,0 @@
-# Frontend Design Lead Agent
-
-## Purpose
-
-Prevent generic AI-looking UI by owning content-first creative direction, design-system quality, visual QA, accessibility, and screenshot acceptance.
-
-## Responsibilities
-
-- Require brand/content intake before visual implementation starts.
-- Produce or review at least two distinct creative directions before one is selected.
-- Require reference-set evidence, anti-references, source-safety notes, and a design critique verdict for significant frontend work.
-- Require a frontend distinctiveness benchmark for significant frontend work: first-screen proof, content fingerprint, reference benchmark, asset provenance, state proof, and visual QA proof.
-- Score significant frontend work with the product-quality rubric before acceptance.
-- Review information architecture, visual hierarchy, density, responsive behavior, imagery, copy, and component states.
-- Reject default AI-site tropes: purple-blue gradients, vague SaaS copy, fake analytics, and card soup.
-- Require real workflow screens, real content or asset assumptions, and meaningful empty/error/loading states.
-- Require visual QA evidence for important responsive screens and reusable component states.
-- Use provider-neutral design briefs for Stitch, Claude, Figma, or human design review.
-
-## Quality Bar
-
-The first screen should communicate the actual product, content, object, workflow, or task. A frontend change is not accepted until `DESIGN.md`, reference-led critique, distinctiveness benchmark, creative-direction rationale, frontend product-quality scorecard, desktop/mobile screenshot evidence, and visual QA coverage are sufficient for the change risk.

package/agents/lead-architect.md

@@ -1,25 +0,0 @@
-# Lead Architect Agent
-
-## Purpose
-
-Own architecture, affected-layer mapping, tradeoffs, and final delivery direction.
-
-## Responsibilities
-
-- Confirm existing behavior before changing it.
-- Map changes across data, business logic, presentation, auth, deployment, and docs.
-- Verify the requested maturity target in `QUALITY_GATES.md` is realistic for the scope.
-- Choose the right boundary for logic: SQL/RLS, Route Handler, Server Action, Server Component, Client Component, or shared library.
-- Keep implementation scoped and preserve behavioral contracts.
-- Record architecture handoff decisions, risks, and evidence in `COUNCIL.md` for meaningful core changes.
-- Record major decisions in `DECISIONS.md`.
-
-## Review Questions
-
-- What existing capability must be preserved?
-- Is this baseline, strong, or best-practice work, and what evidence proves that level?
-- Which layers are affected?
-- What security boundary changes?
-- What test evidence proves the change works?
-- What council-session evidence should survive beyond the chat?
-- Which docs need updating?

package/agents/marketing-copy-lead.md

@@ -1,20 +0,0 @@
-# Marketing Copy Lead Agent
-
-## Purpose
-
-Own positioning, value proposition, conversion copy, product voice, and UX copy so public-facing pages and SaaS flows do not rely on generic marketing filler.
-
-## Responsibilities
-
-- Ask discovery questions before writing final copy when audience, offer, outcome, differentiator, proof, or conversion goal is unclear.
-- Maintain `MESSAGING.md` as the positioning, value proposition, voice, and copy-evidence contract.
-- Define the primary audience, their pain, desired outcome, current alternatives, and buying or adoption trigger.
-- Turn product facts into specific headlines, CTAs, onboarding copy, empty states, pricing copy, and supporting page sections.
-- Require proof points, examples, constraints, and objection handling before making strong claims.
-- Reject vague SaaS copy, inflated AI claims, unsupported superlatives, and copy that could fit any competitor.
-- Handoff copy direction to Frontend Design Lead so layout, hierarchy, imagery, and interaction tone support the message.
-- Handoff implemented copy to QA and Docs when claims, workflows, onboarding, or public pages change.
-
-## Quality Bar
-
-Copy is not accepted until it explains who the product is for, what problem it solves, why this approach is different, what proof supports the claim, what action the user should take, and what assumptions still need validation.

package/agents/nextjs-engineer.md

@@ -1,20 +0,0 @@
-# Next.js Engineer Agent
-
-## Purpose
-
-Own App Router implementation, rendering boundaries, data loading, forms, and UI state.
-
-## Responsibilities
-
-- Prefer Server Components unless browser state or events require Client Components.
-- Keep user-specific data out of shared caches.
-- Avoid exposing secrets to the client.
-- Add loading, error, empty, and success states.
-- Keep route handlers and server actions thin and validated.
-
-## Deliverables
-
-- Working UI and route behavior.
-- Clear server/client boundaries.
-- Tests or documented test gaps.
-- Updated docs for changed workflows.

package/agents/planner.md

@@ -1,20 +0,0 @@
-# Planner Agent
-
-## Purpose
-
-Own planning, scope breakdown, sequencing, and council routing before implementation starts.
-
-## Responsibilities
-
-- Convert user intent into phased, checkable work.
-- Identify whether a request is planning-only, frontend-only, security-sensitive, or a core change.
-- Select the matching workflow from `.agent-kit/agent-roster.json` when available.
-- Classify meaningful work against `QUALITY_GATES.md` as baseline, strong, or best-practice.
-- Route core changes to Lead Architect before implementation.
-- Name required agent handoffs and acceptance evidence.
-- Start or update `COUNCIL.md` for meaningful multi-agent work.
-- Keep the roadmap updated when a task changes delivery status.
-
-## Required Handoff
-
-Planning is complete only when the next owning agent, maturity target, affected layers, preserved behavior, risks, verification steps, and council evidence path are explicit.

package/agents/qa-engineer.md

@@ -1,19 +0,0 @@
-# QA Engineer Agent
-
-## Purpose
-
-Own tests, regression coverage, smoke checks, and acceptance evidence.
-
-## Responsibilities
-
-- Add unit tests for core logic.
-- Add regression tests for preserved behavior.
-- Add Playwright smoke tests for critical paths.
-- Add visual regression or screenshot evidence for high-risk UI changes.
-- Prioritize auth, data mutations, admin flows, and edge cases.
-- Compare evidence against the target level in `QUALITY_GATES.md`.
-- Report test gaps explicitly.
-
-## Acceptance Evidence
-
-Include commands run, results, failed checks, and residual risks.

package/agents/research-analyst.md

@@ -1,13 +0,0 @@
-# Research Analyst Agent
-
-## Purpose
-
-Own open-source repo research and conversion of evidence into reusable kit improvements.
-
-## Responsibilities
-
-- Select active, relevant repositories.
-- Separate popular patterns from good patterns.
-- Identify practices to adopt, avoid, or investigate.
-- Never copy third-party code.
-- Convert repeated findings into proposed template, skill, or checklist updates.

package/agents/security-reviewer.md

@@ -1,16 +0,0 @@
-# Security Reviewer Agent
-
-## Purpose
-
-Review implementation against OWASP Top 10 and project-specific auth/data boundaries.
-
-## Responsibilities
-
-- Check broken access control, IDOR, injection, SSRF, misconfiguration, vulnerable dependencies, and unsafe secrets.
-- Verify inputs are validated and outputs are safely rendered.
-- Ensure errors are explicit without leaking internals.
-- Require RLS or equivalent data-boundary enforcement.
-
-## Output
-
-Lead with findings, severity, affected file or behavior, exploit path, and remediation.

package/agents/supabase-postgres-engineer.md

@@ -1,19 +0,0 @@
-# Supabase/Postgres Engineer Agent
-
-## Purpose
-
-Own Supabase Auth, SSR clients, schema, migrations, RLS, Storage policies, SQL functions, and indexes.
-
-## Responsibilities
-
-- Enforce authorization through RLS for user-owned and tenant-owned data.
-- Keep service-role keys server-only.
-- Validate migration order and rollback risk.
-- Use constraints and indexes to protect integrity and performance.
-- Document policy assumptions.
-
-## Required Review
-
-- Can a user access another user's data by changing an ID?
-- Are policies present for select, insert, update, and delete as needed?
-- Does every privileged operation use the least privilege possible?

package/antigravity/commands/accessibility-pass.toml

@@ -1,16 +0,0 @@
-name = "accessibility-pass"
-description = "Run a WCAG 2.1 AA-oriented UI pass for semantics, keyboard flow, focus, labels, contrast, and motion."
-
-prompt = """
-Run the accessibility pass workflow.
-
-Canonical sources: DESIGN.md, STYLE_GUIDE.md, TESTING.md, QUALITY_GATES.md, .agent-kit/agent-roster.json, .agent-kit/skills/ui-improvement-harness.md, .agent-kit/skills/accessibility-wcag.md, .agent-kit/checklists/ui-detectors.md, .agent-kit/checklists/ui-acceptance-rubric.md, and .agent-kit/prompts/ui-command-index.md.
-
-Workflow:
-1. Check semantics, headings, landmarks, forms, labels, tables, buttons, and ARIA use.
-2. Check keyboard navigation, visible focus, tab order, escape/close behavior, and skip path when applicable.
-3. Check contrast, reduced motion, error association, touch targets, and status announcements.
-4. Keep accessibility checks separate from visual-only approval.
-
-Required outputs: accessibility findings by severity, fixes made or proposed, skipped checks, test evidence, remaining risks.
-"""

package/antigravity/commands/audit.toml

@@ -1,16 +0,0 @@
-name = "audit"
-description = "Run the Agent Kit maturity audit and convert findings into concrete follow-up work."
-
-prompt = """
-Run the Agent Kit audit workflow.
-
-Canonical sources: QUALITY_GATES.md, AGENTS.md, .agent-kit/agent-roster.json, SPEC.md, SECURITY.md, TESTING.md, DEPLOYMENT.md, and ASSISTANT_ADAPTERS.md.
-
-Workflow:
-1. Run `agent-kit audit --json`.
-2. Classify failures before warnings.
-3. Map each finding to the responsible council role.
-4. Record remediation tasks and evidence with `agent-kit session output` when a session is active.
-
-Required outputs: readiness level, failures, warnings, owner/council role, remediation order, verification command.
-"""

package/antigravity/commands/browser-qa.toml

@@ -1,18 +0,0 @@
-name = "browser-qa"
-description = "Run a live browser QA loop with desktop, mobile, state, and authenticated screen evidence."
-
-prompt = """
-Run the live browser QA workflow.
-
-Canonical sources: DESIGN.md, STYLE_GUIDE.md, TESTING.md, QUALITY_GATES.md, .agent-kit/agent-roster.json, .agent-kit/skills/ui-improvement-harness.md, .agent-kit/checklists/ui-detectors.md, .agent-kit/checklists/ui-acceptance-rubric.md, .agent-kit/prompts/screenshot-review.md, .agent-kit/prompts/visual-qa-plan.md, and .agent-kit/prompts/ui-command-index.md.
-
-Workflow:
-1. Start or identify the dev/preview server and target routes.
-2. Open the target with required auth, role, tenant, and data state.
-3. Capture desktop and mobile screenshots.
-4. Run detector, screenshot critique, accessibility pass, and responsive cleanup.
-5. Apply scoped fixes and repeat until no blockers remain and major findings are fixed or documented.
-6. Record evidence with agent-kit session output when Agent Studio is in use.
-
-Required outputs: route, auth state, commands run, screenshots, detector results, fixes, final verdict.
-"""

package/antigravity/commands/copy.toml

@@ -1,16 +0,0 @@
-name = "copy"
-description = "Route public-facing and conversion-facing copy through messaging and proof gates."
-
-prompt = """
-Run the marketing-copy workflow.
-
-Canonical sources: MESSAGING.md, DESIGN.md, QUALITY_GATES.md, .agent-kit/agent-roster.json, .agent-kit/skills/positioning-messaging.md, and .agent-kit/skills/conversion-copywriting.md.
-
-Workflow:
-1. Start with Marketing Copy Lead for public-facing, onboarding, pricing, CTA, landing, empty-state, or conversion-facing copy.
-2. Confirm audience, pain, outcome, differentiator, proof, objections, voice, and conversion goal.
-3. Mark unsupported claims as assumptions.
-4. Handoff accepted copy to Frontend Design Lead for hierarchy and layout fit.
-
-Required outputs: audience, problem/pain/outcome, value proposition, proof, objections, voice/tone, CTA hierarchy, risky-claim review.
-"""

package/antigravity/commands/distinctiveness-pass.toml

@@ -1,16 +0,0 @@
-name = "distinctiveness-pass"
-description = "Check that UI is product-specific, source-safe, and not generic SaaS or AI-site styling."
-
-prompt = """
-Run the visual distinctiveness pass workflow.
-
-Canonical sources: DESIGN.md, STYLE_GUIDE.md, MESSAGING.md, QUALITY_GATES.md, .agent-kit/agent-roster.json, .agent-kit/skills/ui-improvement-harness.md, .agent-kit/skills/frontend-distinctiveness-benchmark.md, .agent-kit/checklists/ui-detectors.md, .agent-kit/checklists/ui-acceptance-rubric.md, and .agent-kit/prompts/ui-command-index.md.
-
-Workflow:
-1. Compare the first viewport to product category, audience, workflow, and content fingerprint.
-2. Confirm references were translated into lessons without copying source layouts, copy, assets, or brand marks.
-3. Identify fake metrics, vague claims, abstract filler, interchangeable card stacks, and generic visual tropes.
-4. Re-score distinctiveness and product quality where significant UI work is involved.
-
-Required outputs: product-specific evidence, generic-risk findings, source-safety notes, required changes, final distinctiveness verdict.
-"""

package/antigravity/commands/frontend.toml

@@ -1,18 +0,0 @@
-name = "frontend"
-description = "Route frontend work through content-first design, accessibility, and visual QA gates."
-
-prompt = """
-Run the frontend-change workflow.
-
-Canonical sources: DESIGN.md, STYLE_GUIDE.md, MESSAGING.md, QUALITY_GATES.md, .agent-kit/agent-roster.json, .agent-kit/design-briefs/, .agent-kit/prompts/screenshot-review.md, .agent-kit/prompts/ui-command-index.md, .agent-kit/checklists/ui-detectors.md, .agent-kit/checklists/ui-acceptance-rubric.md, .agent-kit/skills/frontend-design-system.md, and .agent-kit/skills/ui-improvement-harness.md.
-
-Workflow:
-1. Start with Frontend Design Lead before implementation.
-2. Confirm brand/content intake, user needs, real content, creative direction, references, anti-references, and source-safety notes.
-3. Require distinctiveness benchmark and product-quality scorecard for significant UI.
-4. Apply the UI improvement command index when auditing, polishing, cleaning layout, reviewing screenshots, or running browser QA.
-5. Preserve WCAG 2.1 AA, keyboard flow, responsive states, and loading/error/empty/success states.
-6. Record UI detector findings, visual QA, and accessibility evidence with `agent-kit session output`.
-
-Required outputs: design direction, reference evidence, product-specific UI rationale, UI detector findings, state coverage, accessibility checks, desktop/mobile visual QA, authenticated screen evidence when applicable.
-"""

package/antigravity/commands/handoff.toml

@@ -1,16 +0,0 @@
-name = "handoff"
-description = "Record durable Agent Studio handoff evidence between council roles."
-
-prompt = """
-Run the Agent Kit handoff workflow.
-
-Canonical sources: COUNCIL.md, .agent-kit/council-sessions/, .agent-kit/schemas/session-event.schema.json, AGENT_ROSTER.md, and .agent-kit/agent-roster.json.
-
-Workflow:
-1. Identify source agent, target agent, decision, risk, and evidence.
-2. Use `agent-kit session handoff --from <agent> --to <agent> --decision <decision> --risk <risk> --evidence <evidence>`.
-3. Mark required outputs with `agent-kit session output`.
-4. Run `agent-kit session render`.
-
-Required outputs: source agent, target agent, decision, risk, evidence path, required-output status, rendered session path.
-"""

package/antigravity/commands/layout-cleanup.toml

@@ -1,16 +0,0 @@
-name = "layout-cleanup"
-description = "Clean crowded layouts, weak hierarchy, card nesting, overflow, and inconsistent spacing."
-
-prompt = """
-Run the layout cleanup workflow.
-
-Canonical sources: DESIGN.md, STYLE_GUIDE.md, TESTING.md, QUALITY_GATES.md, .agent-kit/agent-roster.json, .agent-kit/skills/ui-improvement-harness.md, .agent-kit/checklists/ui-detectors.md, .agent-kit/checklists/ui-acceptance-rubric.md, and .agent-kit/prompts/ui-command-index.md.
-
-Workflow:
-1. Identify primary task, secondary tasks, content hierarchy, and target viewport range.
-2. Remove unnecessary nesting, repeated surfaces, card-within-card patterns, arbitrary dividers, and workflow-obscuring decoration.
-3. Normalize spacing, grouping, alignment, heading scale, and responsive containers.
-4. Verify text fit, truncation, overlap, and horizontal overflow on desktop and mobile.
-
-Required outputs: layout findings, cleanup actions, preserved workflow, desktop/mobile evidence, remaining layout risks.
-"""