@appsforgood/next-supabase-kit 0.3.0 → 0.4.1

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.
-"""

package/antigravity/commands/plan.toml

@@ -1,18 +0,0 @@
-name = "plan"
-description = "Create an implementation-ready Agent Kit plan through Planner and Lead Architect routing."
-
-prompt = """
-Run the planning workflow.
-
-Canonical sources: AGENTS.md, AGENT_ROSTER.md, .agent-kit/agent-roster.json, MODEL_ROUTING.md, .agent-kit/model-routing.json, .agent-kit/project-context.md, .agent-kit/corrections/project-rules.json, COUNCIL.md, and QUALITY_GATES.md.
-
-Workflow:
-1. Start with Planner.
-2. Name the active workflow and maturity target from QUALITY_GATES.md.
-3. Map affected layers: data, business logic, presentation, auth, deployment, docs, and tests.
-4. Name preserved behavior and compatibility constraints.
-5. Route core changes through Lead Architect before implementation.
-6. Record decision, risk, next handoff, and required outputs with `agent-kit session ...` when available.
-
-Required outputs: goal, affected layers, preserved capabilities, implementation sequence, risks, tests, docs, handoffs, acceptance criteria.
-"""

package/antigravity/commands/responsive-cleanup.toml

@@ -1,16 +0,0 @@
-name = "responsive-cleanup"
-description = "Verify and repair mobile and responsive UI behavior with required desktop and mobile evidence."
-
-prompt = """
-Run the responsive 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. Review mobile width, desktop width, and project-specific breakpoint assumptions.
-2. Verify tap targets, text fit, navigation, primary action visibility, sticky UI, scroll behavior, and viewport-safe spacing.
-3. Verify relevant loading, empty, error, disabled, success, permission, and focus states on mobile.
-4. Capture or request desktop and mobile screenshots before acceptance.
-
-Required outputs: viewports checked, responsive findings, fixes made or proposed, screenshots, remaining risks.
-"""

package/antigravity/commands/review.toml

@@ -1,16 +0,0 @@
-name = "review"
-description = "Run pre-merge code health review with QA and conditional Security Reviewer routing."
-
-prompt = """
-Run the code-review workflow.
-
-Canonical sources: TESTING.md, SECURITY.md, QUALITY_GATES.md, AGENTS.md, .agent-kit/agent-roster.json, .agent-kit/skills/testing-qa.md, .agent-kit/skills/owasp-security-review.md, and .agent-kit/prompts/lifecycle-command-index.md.
-
-Workflow:
-1. Route through QA Engineer for behavior, regression, and test evidence.
-2. Include Security Reviewer when auth, RLS, data mutation, dependency, secret, or external-call boundaries changed.
-3. Return findings by severity with concrete remediation.
-4. Distinguish this from release GO/NO-GO, which belongs to `/ship`.
-
-Required outputs: reviewed scope, findings by severity, required fixes, security notes when applicable, merge recommendation.
-"""

package/antigravity/commands/screenshot-critique.toml

@@ -1,16 +0,0 @@
-name = "screenshot-critique"
-description = "Critique desktop, mobile, state, and authenticated screenshots against design and detector rules."
-
-prompt = """
-Run the screenshot critique 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, and .agent-kit/prompts/ui-command-index.md.
-
-Workflow:
-1. Name each screenshot, viewport, route, auth state, data state, and UI state.
-2. Run screenshot review, detector checklist, and accessibility risk scan.
-3. Compare against DESIGN.md, STYLE_GUIDE.md, and selected creative direction.
-4. Return concrete fixes and missing screenshot evidence.
-
-Required outputs: screenshot inventory, blockers, high-value fixes, accepted areas, missing screenshots, release verdict.
-"""

package/antigravity/commands/security.toml

@@ -1,16 +0,0 @@
-name = "security"
-description = "Run OWASP, auth, RLS, dependency, secret, and external-call review before acceptance."
-
-prompt = """
-Run the security-review workflow.
-
-Canonical sources: SECURITY.md, .agent-kit/checklists/owasp.md, .agent-kit/checklists/rls.md, .agent-kit/skills/owasp-security-review.md, AGENTS.md, and .agent-kit/agent-roster.json.
-
-Workflow:
-1. Route through Security Reviewer for auth, RLS, API, Server Action, data mutation, dependency, secret, external-call, upload, or release-risk changes.
-2. Check OWASP Top 10, IDOR, SSRF, injection, broken auth, unsafe output rendering, secret leakage, and vulnerable dependencies.
-3. Verify service-role access stays server-only.
-4. Record findings with severity, exploit path, affected behavior, and remediation.
-
-Required outputs: reviewed boundaries, findings, severity, exploit path, mitigation, negative authorization tests or skipped rationale.
-"""

package/antigravity/commands/setup.toml

@@ -1,16 +0,0 @@
-name = "setup"
-description = "Onboard the project into Agent Kit context and verify runtime adapter setup."
-
-prompt = """
-Run Agent Kit setup as a runtime command.
-
-Canonical sources: AGENTS.md, AGENT_ROSTER.md, .agent-kit/agent-roster.json, MODEL_ROUTING.md, .agent-kit/model-routing.json, QUALITY_GATES.md, and ASSISTANT_ADAPTERS.md.
-
-Workflow:
-1. Run or recommend `agent-kit setup --open` when project context is missing.
-2. Validate context with `agent-kit context validate`.
-3. Confirm adapter evidence in ASSISTANT_ADAPTERS.md.
-4. Record setup evidence in an Agent Studio session when meaningful work starts.
-
-Required outputs: project context status, active IDE/runtime surface, model-selection status, remaining setup gaps, verification command.
-"""

package/antigravity/commands/ship.toml

@@ -1,17 +0,0 @@
-name = "ship"
-description = "Make a GO/NO-GO release call from council, security, QA, docs, deployment, and rollback evidence."
-
-prompt = """
-Run the ship workflow.
-
-Canonical sources: QUALITY_GATES.md, TESTING.md, SECURITY.md, DEPLOYMENT.md, UPGRADE.md, COUNCIL.md, .agent-kit/council-sessions/, and .agent-kit/agent-roster.json.
-
-Workflow:
-1. Confirm implementation scope and preserved behavior.
-2. Require code review, Security Reviewer signoff, QA/test evidence, accessibility evidence when UI changed, docs evidence, deployment/observability review, and rollback plan.
-3. Run the project release gate, normally `npm run release:check` for this package or the project-specific equivalent.
-4. Record verification with `agent-kit session verify`.
-5. Return GO only when required outputs are complete or explicitly not-applicable.
-
-Required outputs: code review, security review, QA/test review, accessibility/doc/deployment checks, rollback plan, release command, GO/NO-GO verdict.
-"""

package/antigravity/commands/spec.toml

@@ -1,17 +0,0 @@
-name = "spec"
-description = "Define or update SPEC.md with acceptance criteria before implementation."
-
-prompt = """
-Run the spec workflow.
-
-Canonical sources: SPEC.md, AGENTS.md, AGENT_ROSTER.md, .agent-kit/agent-roster.json, .agent-kit/project-context.md, .agent-kit/corrections/project-rules.json, QUALITY_GATES.md, and .agent-kit/prompts/lifecycle-command-index.md.
-
-Workflow:
-1. Route through Planner and Documentation Maintainer.
-2. Read project context and active correction rules before drafting or updating the spec.
-3. Capture goal, user/workflow, acceptance criteria, preserved behavior, non-goals, and docs impact.
-4. Map affected layers: data, business logic, presentation, auth, deployment, and tests.
-5. Record decision, risk, and next handoff with `agent-kit session ...` when a session is active.
-
-Required outputs: spec delta or draft, acceptance criteria, preserved capabilities, non-goals, verification plan, next handoff.
-"""

package/antigravity/commands/test.toml

@@ -1,17 +0,0 @@
-name = "test"
-description = "Add or run tests and produce acceptance evidence per TESTING.md and QUALITY_GATES.md."
-
-prompt = """
-Run the test workflow.
-
-Canonical sources: TESTING.md, QUALITY_GATES.md, AGENTS.md, .agent-kit/agent-roster.json, .agent-kit/skills/testing-qa.md, and .agent-kit/prompts/lifecycle-command-index.md.
-
-Workflow:
-1. Route through QA Engineer.
-2. Name unit, regression, smoke, and visual QA gaps for the change scope.
-3. Prioritize auth and data mutation paths.
-4. Run project test commands and capture results.
-5. Record verification with `agent-kit session verify` when a session is active.
-
-Required outputs: test plan, commands run, pass/fail summary, coverage gaps, skipped-test rationale.
-"""

package/antigravity/commands/ui-audit.toml

@@ -1,17 +0,0 @@
-name = "ui-audit"
-description = "Run a deterministic UI audit with severity-based detector findings and release evidence."
-
-prompt = """
-Run the UI audit 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 target route, component, workflow, auth state, data state, and risk tier.
-2. Load product/design context and relevant design brief.
-3. Review desktop and mobile evidence, or state which evidence must still be captured.
-4. Run the UI detector checklist and classify blockers, majors, minors, passes, and not-applicable items.
-5. Return required fixes, accepted exceptions, preserved capabilities, and pass/fail verdict.
-
-Required outputs: target surface, risk tier, detector findings by severity, missing evidence, release verdict.
-"""

package/antigravity/commands/ui-polish.toml

@@ -1,17 +0,0 @@
-name = "ui-polish"
-description = "Improve UI hierarchy, spacing, state feedback, and visual finish through detector-guided polish."
-
-prompt = """
-Run the UI polish 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. Start from detector findings, screenshots, or a named target surface.
-2. Preserve product behavior, auth boundaries, copy claims, data contracts, and existing component patterns.
-3. Improve hierarchy, spacing, density, alignment, component states, and interaction feedback.
-4. Remove decorative clutter and generic SaaS or AI-site defaults.
-5. Re-run detector and screenshot critique after the scoped polish pass.
-
-Required outputs: polish goals, changes made or proposed, detector deltas, screenshot evidence, residual risks.
-"""

package/antigravity/commands/upgrade.toml

@@ -1,17 +0,0 @@
-name = "upgrade"
-description = "Plan and verify Agent Kit, framework, dependency, and adapter upgrades with rollback evidence."
-
-prompt = """
-Run the upgrade-maintenance workflow.
-
-Canonical sources: UPGRADE.md, CHANGELOG.md, DECISIONS.md, DEPLOYMENT.md, .agent-kit/skills/upgrade-maintenance.md, and QUALITY_GATES.md.
-
-Workflow:
-1. Run `agent-kit diff` before accepting template changes.
-2. Preserve local overrides and review `.agent-kit/conflicts/`.
-3. Check framework release notes, codemods, migrations, generated types, RLS impact, and rollback risk when applicable.
-4. Run `agent-kit audit --min-readiness baseline-setup` after update.
-5. Record version, migration impact, verification, owner, and rollback evidence.
-
-Required outputs: version change, conflict review, migration impact, generated files/types, audit result, rollback plan, owner/date.
-"""

package/antigravity/plugin.json

@@ -1,70 +0,0 @@
-{
-  "schemaVersion": 1,
-  "name": "agent-kit-next-supabase",
-  "displayName": "Agent Kit Next/Supabase",
-  "version": "0.1.8",
-  "description": "Runtime commands and portable skills for the Agent Kit Next/Supabase council workflow.",
-  "homepage": "https://github.com/lukey662/agentsandskills",
-  "sourceOfTruth": [
-    "AGENTS.md",
-    "AGENT_ROSTER.md",
-    ".agent-kit/agent-roster.json",
-    "MODEL_ROUTING.md",
-    ".agent-kit/model-routing.json",
-    "QUALITY_GATES.md",
-    "COUNCIL.md",
-    ".agent-kit/council-sessions/"
-  ],
-  "commands": [
-    { "name": "setup", "path": "commands/setup.toml" },
-    { "name": "spec", "path": "commands/spec.toml" },
-    { "name": "audit", "path": "commands/audit.toml" },
-    { "name": "plan", "path": "commands/plan.toml" },
-    { "name": "handoff", "path": "commands/handoff.toml" },
-    { "name": "frontend", "path": "commands/frontend.toml" },
-    { "name": "ui-audit", "path": "commands/ui-audit.toml" },
-    { "name": "ui-polish", "path": "commands/ui-polish.toml" },
-    { "name": "layout-cleanup", "path": "commands/layout-cleanup.toml" },
-    { "name": "responsive-cleanup", "path": "commands/responsive-cleanup.toml" },
-    { "name": "accessibility-pass", "path": "commands/accessibility-pass.toml" },
-    { "name": "distinctiveness-pass", "path": "commands/distinctiveness-pass.toml" },
-    { "name": "screenshot-critique", "path": "commands/screenshot-critique.toml" },
-    { "name": "browser-qa", "path": "commands/browser-qa.toml" },
-    { "name": "test", "path": "commands/test.toml" },
-    { "name": "review", "path": "commands/review.toml" },
-    { "name": "security", "path": "commands/security.toml" },
-    { "name": "copy", "path": "commands/copy.toml" },
-    { "name": "ship", "path": "commands/ship.toml" },
-    { "name": "upgrade", "path": "commands/upgrade.toml" }
-  ],
-  "skills": [
-    { "name": "accessibility-wcag", "path": "../runtime-skills/accessibility-wcag/SKILL.md" },
-    { "name": "agent-handoff-tracing", "path": "../runtime-skills/agent-handoff-tracing/SKILL.md" },
-    { "name": "best-practice-maturity-review", "path": "../runtime-skills/best-practice-maturity-review/SKILL.md" },
-    { "name": "content-first-design", "path": "../runtime-skills/content-first-design/SKILL.md" },
-    { "name": "conversion-copywriting", "path": "../runtime-skills/conversion-copywriting/SKILL.md" },
-    { "name": "deployment-observability", "path": "../runtime-skills/deployment-observability/SKILL.md" },
-    { "name": "docs-maintainer", "path": "../runtime-skills/docs-maintainer/SKILL.md" },
-    { "name": "frontend-design-system", "path": "../runtime-skills/frontend-design-system/SKILL.md" },
-    { "name": "frontend-distinctiveness-benchmark", "path": "../runtime-skills/frontend-distinctiveness-benchmark/SKILL.md" },
-    { "name": "frontend-product-quality-rubric", "path": "../runtime-skills/frontend-product-quality-rubric/SKILL.md" },
-    { "name": "landing-page-copy", "path": "../runtime-skills/landing-page-copy/SKILL.md" },
-    { "name": "ui-improvement-harness", "path": "../runtime-skills/ui-improvement-harness/SKILL.md" },
-    { "name": "nextjs-app-router", "path": "../runtime-skills/nextjs-app-router/SKILL.md" },
-    { "name": "onboarding-empty-state-copy", "path": "../runtime-skills/onboarding-empty-state-copy/SKILL.md" },
-    { "name": "owasp-security-review", "path": "../runtime-skills/owasp-security-review/SKILL.md" },
-    { "name": "planning-council", "path": "../runtime-skills/planning-council/SKILL.md" },
-    { "name": "positioning-messaging", "path": "../runtime-skills/positioning-messaging/SKILL.md" },
-    { "name": "postgres-migrations", "path": "../runtime-skills/postgres-migrations/SKILL.md" },
-    { "name": "product-voice-tone", "path": "../runtime-skills/product-voice-tone/SKILL.md" },
-    { "name": "reference-led-design-critique", "path": "../runtime-skills/reference-led-design-critique/SKILL.md" },
-    { "name": "supabase-auth-rls", "path": "../runtime-skills/supabase-auth-rls/SKILL.md" },
-    { "name": "testing-qa", "path": "../runtime-skills/testing-qa/SKILL.md" },
-    { "name": "upgrade-maintenance", "path": "../runtime-skills/upgrade-maintenance/SKILL.md" },
-    { "name": "visual-regression-qa", "path": "../runtime-skills/visual-regression-qa/SKILL.md" }
-  ],
-  "validation": {
-    "agentKit": "agent-kit adapter validate antigravity",
-    "nativeOptional": "agy plugin validate"
-  }
-}