@appsforgood/next-supabase-kit 0.1.5 → 0.1.7

package/antigravity/commands/screenshot-critique.toml

@@ -0,0 +1,16 @@
+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/spec.toml

@@ -0,0 +1,17 @@
+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

@@ -0,0 +1,17 @@
+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

@@ -0,0 +1,17 @@
+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

@@ -0,0 +1,17 @@
+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/plugin.json

@@ -2,7 +2,7 @@
   "schemaVersion": 1,
   "name": "agent-kit-next-supabase",
   "displayName": "Agent Kit Next/Supabase",
-  "version": "0.1.3",
+  "version": "0.1.7",
   "description": "Runtime commands and portable skills for the Agent Kit Next/Supabase council workflow.",
   "homepage": "https://github.com/lukey662/agentsandskills",
   "sourceOfTruth": [
@@ -17,10 +17,21 @@
   ],
   "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" },
@@ -38,6 +49,7 @@
     { "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" },

package/assistant-adapters/antigravity.md

@@ -40,15 +40,22 @@ If the `agy` CLI is available, teams may additionally run its native plugin vali
 Commands expose short runtime entrypoints:
 
 - `/setup`
+- `/spec`
 - `/audit`
 - `/plan`
 - `/handoff`
 - `/frontend`
+- `/test`
+- `/review`
 - `/security`
 - `/copy`
 - `/ship`
 - `/upgrade`
 
+UI harness commands (`/ui-audit`, `/ui-polish`, `/layout-cleanup`, `/responsive-cleanup`, `/accessibility-pass`, `/distinctiveness-pass`, `/screenshot-critique`, `/browser-qa`) are documented in `.agent-kit/prompts/ui-command-index.md`.
+
+Delivery lifecycle commands are documented in `.agent-kit/prompts/lifecycle-command-index.md`.
+
 Each command must load project context and correction rules when present, select the appropriate roster workflow, record required outputs with `agent-kit session output`, and render sessions when evidence changes.
 
 ## Security

package/checklists/ui-acceptance-rubric.md

@@ -0,0 +1,58 @@
+# UI Acceptance Rubric
+
+Use this rubric after the UI detector checklist, screenshot critique, accessibility pass, and browser QA loop.
+
+## Pass/Fail
+
+| Verdict | Criteria |
+| --- | --- |
+| fail | Any blocker remains, required screenshot evidence is missing, or authenticated screens were not reviewed when auth is required |
+| conditional | No blockers remain, but major findings need documented owner, rationale, or follow-up before high-risk release |
+| pass | No blockers remain, major findings are fixed or explicitly accepted, and evidence covers viewports, states, and auth needs |
+| strong | Pass criteria plus clear product specificity, accessible keyboard flow, responsive resilience, and state coverage for the workflow |
+
+## Required Evidence
+
+- Target surface: route, component, flow, or screenshot set.
+- Product context source: `DESIGN.md`, `STYLE_GUIDE.md`, design brief, or documented override.
+- Viewports: desktop and mobile dimensions.
+- Auth state: public, signed-in, role, tenant, permission, or explicit not-applicable.
+- Data state: realistic, empty, loading, error, or fixture notes.
+- Screenshots: first viewport, primary workflow, mobile, and highest-risk state.
+- Checks: detector checklist, accessibility pass, screenshot critique, and visual QA tier.
+
+## Release Blocking Rules
+
+- Block release for any blocker detector.
+- Block high-risk UI release when desktop or mobile screenshot evidence is missing.
+- Block authenticated workflow release when no signed-in or permission-state evidence exists.
+- Block acceptance when loading, empty, error, disabled, success, permission, or focus states are relevant but omitted without rationale.
+- Block best-practice claims when product specificity, accessibility, or source safety is weak.
+
+## Risk Tiers
+
+| Tier | Use When | Minimum Evidence |
+| --- | --- | --- |
+| low | Copy-only or isolated cosmetic change to a stable component | Targeted screenshot or component evidence plus detector review |
+| medium | Layout, responsive, or state changes on a user-facing surface | Desktop and mobile screenshots plus relevant state evidence |
+| high | Authenticated workflow, checkout, data mutation, admin, onboarding, or shared component system | Desktop, mobile, auth/permission, error/empty/loading, keyboard/focus, and smoke evidence |
+
+## Exception Rules
+
+Exceptions are allowed only when:
+
+- The finding is not a blocker.
+- The rationale names product or technical constraints.
+- The owner and follow-up path are documented.
+- The exception does not weaken auth, accessibility, data integrity, or source safety.
+
+## Output Format
+
+Return:
+
+1. Verdict: fail, conditional, pass, or strong.
+2. Risk tier and target surface.
+3. Evidence reviewed.
+4. Blockers, majors, minors, and accepted exceptions.
+5. Required fixes before release.
+6. Follow-up work after release.

package/checklists/ui-detectors.md

@@ -0,0 +1,75 @@
+# UI Detector Checklist
+
+Use this deterministic checklist for UI audit, polish, layout cleanup, responsive cleanup, screenshot critique, and browser QA. Mark each item as `blocker`, `major`, `minor`, `pass`, or `not-applicable`.
+
+## Severity
+
+| Severity | Meaning |
+| --- | --- |
+| blocker | Prevents release because a user cannot complete the workflow, the UI is inaccessible, or required evidence is missing |
+| major | Degrades comprehension, trust, responsiveness, or state handling enough that high-risk UI should not ship without a fix or accepted exception |
+| minor | Polish issue that should be fixed when nearby but does not block normal release |
+| pass | Checked and acceptable for the target surface |
+| not-applicable | The detector does not apply to this surface or state |
+
+## Layout And Hierarchy
+
+| Detector | Blocker Signal | Major Signal |
+| --- | --- | --- |
+| Crowded layout | Primary workflow cannot be identified or completed | Too many competing sections, controls, badges, or panels |
+| Weak hierarchy | Primary action or current state is hidden | Headings, labels, and actions do not establish clear priority |
+| Inconsistent spacing | Spacing causes overlap or unusable controls | Density, gaps, padding, or alignment shift without system logic |
+| Card-within-card | Nested containers obscure the workflow or trap scroll | Decorative nested panels add visual noise without information value |
+| Poor grouping | Related controls are separated or unrelated items are grouped | Scan path is unclear or section boundaries are arbitrary |
+
+## Responsive And Mobile
+
+| Detector | Blocker Signal | Major Signal |
+| --- | --- | --- |
+| Poor tap targets | Critical control is too small, overlapped, or unreachable | Repeated controls feel cramped or hard to tap |
+| Truncation or overflow | Text, inputs, tables, or controls clip essential content | Labels wrap badly, overflow horizontally, or push layout off-screen |
+| Mobile hierarchy | Mobile first screen hides the primary task or action | Desktop order collapses into a confusing mobile sequence |
+| Sticky or fixed UI | Fixed header/footer covers content or controls | Sticky UI consumes too much viewport or causes awkward scrolling |
+| Orientation and narrow widths | Page breaks at common mobile widths | Responsive behavior is untested below tablet width |
+
+## States And Feedback
+
+| Detector | Blocker Signal | Major Signal |
+| --- | --- | --- |
+| Missing loading state | User can trigger duplicate or unsafe action while waiting | Loading state exists but does not preserve layout or context |
+| Missing empty state | Empty data leaves a dead end | Empty state lacks next action or domain-specific guidance |
+| Missing error state | Failure is silent or blocks recovery | Error is vague, unactionable, or visually disconnected |
+| Missing disabled state | Disabled action looks enabled or loses explanation | Disabled state lacks affordance, label, or contrast |
+| Missing success feedback | User cannot tell whether action completed | Success message is too subtle, transient, or ambiguous |
+| Missing permission state | Protected UI leaks actions or fails without explanation | Permission limitation is not clear to the affected role |
+| Weak interaction feedback | Focus, selected, hover, pressed, or active state is absent on critical controls | State feedback is inconsistent across similar controls |
+
+## Accessibility
+
+| Detector | Blocker Signal | Major Signal |
+| --- | --- | --- |
+| Keyboard path | Critical workflow cannot be completed by keyboard | Tab order is confusing or focus moves unexpectedly |
+| Focus visibility | Focus indicator is absent on interactive controls | Focus is low contrast or inconsistent |
+| Semantic structure | Heading, landmark, form, table, or button semantics block assistive tech use | Semantics are mostly present but incomplete |
+| Labels and errors | Inputs or controls lack accessible names or error association | Labels exist but are vague, duplicate, or visually disconnected |
+| Contrast | Text or critical controls fail WCAG 2.1 AA contrast | Secondary text or state colors are borderline |
+| Motion | Motion prevents comprehension or ignores reduced-motion need | Motion distracts from workflow or feels inconsistent |
+
+## Distinctiveness And Source Safety
+
+| Detector | Blocker Signal | Major Signal |
+| --- | --- | --- |
+| Generic SaaS styling | First screen could fit another product by changing logo and headline | Visual direction relies on common cards, gradients, fake dashboards, or vague claims |
+| Missing content fingerprint | UI hides missing product decisions behind placeholders | Real nouns, records, actions, or edge cases are too sparse |
+| Weak visual identity | No product-specific density, typography, imagery, or interaction point of view | Direction is coherent but category-generic |
+| Unsafe reference use | Copy, assets, layout signature, or brand identity appear copied | References are cited without lessons and anti-copy notes |
+| Fake or unsupported proof | Fake metrics or claims imply unavailable capability | Proof exists but is not tied to actual product behavior |
+
+## Evidence Requirements
+
+- Desktop screenshot reviewed.
+- Mobile screenshot reviewed.
+- Highest-risk state screenshot reviewed.
+- Authenticated or permission-state screenshot reviewed when applicable.
+- Browser route, viewport, data fixture, and user role named.
+- Detector exceptions documented with rationale and owner.