@appsforgood/next-supabase-kit 0.1.0 → 0.1.3

package/templates/next-supabase/CLAUDE.md

@@ -0,0 +1,39 @@
+# Claude Code Project Instructions
+
+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:
+
+- `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
+
+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.

package/templates/next-supabase/DECISIONS.md

@@ -30,6 +30,20 @@ Add new decisions above this line or keep newest first.
 
 Record major frontend choices here when a creative direction, reference set, anti-reference, brand constraint, information architecture, visual QA tier, or component-system rule materially affects implementation.
 
+## Runtime Adapter Rule
+
+### Context
+
+Agent Kit may expose runtime-native command surfaces such as Antigravity plugin commands.
+
+### Decision
+
+Runtime command files are adapters. `AGENTS.md`, `.agent-kit/agent-roster.json`, `QUALITY_GATES.md`, canonical `.agent-kit/skills/`, and Agent Studio session records remain the source of truth.
+
+### Consequences
+
+Native commands improve invocation ergonomics, but project policy, security gates, handoff rules, model routing, and documentation contracts stay centralized in Agent Kit files.
+
 ## Agent Kit Model Routing
 
 ### Context

package/templates/next-supabase/DOCS.md

@@ -17,6 +17,7 @@ Document:
 
 - Agent council routing in `.agent-kit/agent-roster.json`
 - Assistant activation surfaces in `ASSISTANT_ADAPTERS.md`
+- Optional runtime adapter surfaces such as `.antigravity/agent-kit/` and `.antigravity/runtime-skills/`
 - Model profile routing in `MODEL_ROUTING.md` and `.agent-kit/model-routing.json`
 - Council-session evidence in `COUNCIL.md`
 - Agent, council-session, model-routing, and audit-report schemas in `.agent-kit/schemas/`
@@ -38,6 +39,7 @@ Document primary workflows, including:
 
 - Planning and core-change handoffs from `AGENT_ROSTER.md`
 - Tool-specific assistant activation from `ASSISTANT_ADAPTERS.md`
+- Runtime command validation with `agent-kit adapter validate antigravity` when Antigravity is active
 - Model-selection setup, enforcement status, and limitations from `MODEL_ROUTING.md`
 - Council-session evidence capture from `COUNCIL.md`
 - Upgrade review, conflict handling, migration review, and rollback evidence from `UPGRADE.md`
@@ -53,6 +55,8 @@ Document primary workflows, including:
 - Data creation and update workflow
 - Deployment workflow
 
+Runtime command files are adapters only. Native commands such as `/plan`, `/security`, `/frontend`, `/copy`, `/handoff`, `/audit`, `/setup`, `/upgrade`, and `/ship` should point back to `AGENTS.md`, `.agent-kit/agent-roster.json`, `QUALITY_GATES.md`, `.agent-kit/skills/`, and Agent Studio evidence.
+
 ## Integration Points
 
 Document external APIs, webhooks, storage buckets, cron jobs, email providers, analytics, and monitoring.

package/templates/next-supabase/MODEL_ROUTING.md

@@ -40,6 +40,7 @@ Canonical source of truth:
 | Claude Code | `CLAUDE.md`, `.claude/agents/*.md` | Unverified | Partial | Record date, owner, subagent files, and model frontmatter behavior. |
 | Cursor | `.cursor/rules/*.mdc` | Unverified | Advisory | Record date, owner, model picker/team setting, and loaded rule evidence. |
 | GitHub Copilot | `.github/copilot-instructions.md`, `.github/instructions/*.instructions.md` | Unverified | Advisory | Record date, owner, selected chat/coding-agent model, and loaded instruction evidence. |
+| Antigravity | `.antigravity/agent-kit/plugin.json`, `.antigravity/agent-kit/commands/*.toml`, `.antigravity/runtime-skills/*/SKILL.md` | Unverified | Advisory | Record date, owner, `agent-kit adapter validate antigravity`, and optional native `agy plugin validate` output. |
 
 ## June 2026 Commented Recommendations
 
@@ -98,6 +99,17 @@ June 2026 Agent Kit suggestion:
 -->
 ```
 
+### Antigravity
+
+```md
+<!--
+June 2026 Agent Kit suggestion:
+- Use native `/plan`, `/security`, `/frontend`, `/copy`, `/handoff`, `/audit`, `/setup`, `/upgrade`, and `/ship` commands as runtime entrypoints.
+- Keep model choice aligned with MODEL_ROUTING.md profiles, but record that Antigravity model enforcement is advisory unless the runtime/workspace provides stronger controls.
+- Validate structural assets with `agent-kit adapter validate antigravity`; native `agy plugin validate` is optional when the CLI is installed.
+-->
+```
+
 ## Acceptance Evidence
 
 Before claiming strong or best-practice maturity, record:

package/templates/next-supabase/QUALITY_GATES.md

@@ -20,6 +20,7 @@ Baseline means the project is usable and the agent kit can audit it.
 - `AGENTS.md`, `AGENT_ROSTER.md`, `ASSISTANT_ADAPTERS.md`, `COUNCIL.md`, `SPEC.md`, `DECISIONS.md`, `DOCS.md`, `DESIGN.md`, `MESSAGING.md`, `MODEL_ROUTING.md`, `STYLE_GUIDE.md`, `SECURITY.md`, `TESTING.md`, `DEPLOYMENT.md`, and `UPGRADE.md` exist.
 - `.agent-kit/agent-roster.json`, `.agent-kit/model-routing.json`, and `.agent-kit/schemas/` exist.
 - `.agent-kit/assistant-adapters/` exists.
+- Runtime adapters such as Antigravity are validated with `agent-kit adapter validate <target>` before being treated as active.
 - Agent Studio schemas for project context, correction rules, session events, and studio sessions exist when the installed kit version includes them.
 - Planner is the default planning route.
 - Lead Architect reviews core changes.
@@ -59,6 +60,7 @@ Best-practice means evidence can survive handoff, release, and later audit.
 - Public-facing and conversion-facing copy starts from discovery questions, audience, pain, outcome, differentiator, proof, objections, voice/tone, and CTA hierarchy, with unsupported claims marked as assumptions.
 - Test evidence includes the smallest useful unit/regression checks plus critical-path smoke coverage.
 - Release evidence includes install or production smoke, migration order, dependency audit, package or deployment verification, logs, and rollback notes.
+- Runtime adapter evidence includes command/plugin validation, portable `SKILL.md` coverage, package allowlist coverage, and proof that adapter files point back to Agent Kit source-of-truth contracts.
 - Repo health includes issue/PR templates, CODEOWNERS, dependency updates, CodeQL or equivalent scanning, dependency review, provenance expectations, support, conduct, and governance.
 - Public or shared package releases use Trusted Publishing or equivalent identity-bound release provenance.
 
@@ -73,6 +75,7 @@ Best-practice means evidence can survive handoff, release, and later audit.
 | Marketing/copy | Marketing Copy Lead, Frontend Design Lead, QA, Docs | `MESSAGING.md`, audience and pain, value proposition, proof, objections, voice/tone, CTA hierarchy, risky-claim review |
 | Security-sensitive | Security Reviewer, Lead Architect, QA | OWASP review, boundary validation, dependency/secret review, regression or smoke evidence |
 | Release/package | Deployment/Observability Engineer, Security Reviewer, QA, Docs | Release gate output, dependency audit, install/deploy smoke, provenance or publish identity evidence |
+| Runtime adapter/package | Planner, Lead Architect, Security Reviewer, QA, Docs | `agent-kit adapter validate`, `agent-kit package validate`, command/skill asset coverage, source-of-truth references, no secret-like runtime assets |
 | Upgrade/dependency | Planner, Lead Architect, Security Reviewer, QA, Docs, Deployment/Observability Engineer | Release notes, codemods or migration guide, `agent-kit diff`, conflict review, audit output, rollback notes |
 
 ## Evidence Rules
@@ -81,6 +84,7 @@ Best-practice means evidence can survive handoff, release, and later audit.
 - A test is not evidence unless it covers the behavior, risk, or contract being claimed.
 - A screenshot is not visual QA unless it covers the important viewport, state, and content.
 - A research finding is not a best practice until it is promoted into templates, skills, checklists, audit checks, tests, release gates, or documented decisions.
+- A runtime command is not canonical policy; it is accepted only when it wraps `AGENTS.md`, `.agent-kit/agent-roster.json`, `QUALITY_GATES.md`, canonical skills, and Agent Studio evidence.
 - A fresh install can be baseline setup while still warning on `TBD`, example rows, or starter instruction text; those placeholders must be replaced before claiming strong or best-practice maturity.
 - A local customization is acceptable only when `.agent-kit/overrides.json` explains why and when it was reviewed.
 - A human correction is not durable until it is stored in `.agent-kit/corrections/`, remains secret-safe, has a clear scope, and is visible to future agents through installed instructions.

package/templates/next-supabase/SPEC.md

@@ -24,6 +24,7 @@ List behavior that must be preserved during changes:
 
 - Agent council routing in `.agent-kit/agent-roster.json`
 - Model profile routing in `MODEL_ROUTING.md` and `.agent-kit/model-routing.json`
+- Optional runtime adapter commands and portable `SKILL.md` wrappers, when activated
 - Council-session evidence in `COUNCIL.md`
 - Agent, council-session, model-routing, and audit-report schema contracts in `.agent-kit/schemas/`
 - Planner default ownership for planning and Lead Architect review for core changes
@@ -65,6 +66,7 @@ Record the current maturity target and evidence.
 | --- | --- | --- | --- | --- |
 | Council routing | TBD | TBD | TBD | `AGENT_ROSTER.md`, `COUNCIL.md` |
 | Model routing | TBD | TBD | TBD | `MODEL_ROUTING.md`, `ASSISTANT_ADAPTERS.md` |
+| Runtime adapters | TBD | TBD | TBD | `agent-kit adapter validate antigravity`, `.antigravity/agent-kit/`, `.antigravity/runtime-skills/` |
 | Architecture | TBD | TBD | TBD | Affected-layer map, `DECISIONS.md` |
 | Supabase/RLS | TBD | TBD | TBD | RLS inventory, migration tests |
 | Messaging | TBD | TBD | TBD | `MESSAGING.md`, proof map, objection handling, CTA hierarchy |

package/templates/next-supabase/TESTING.md

@@ -9,6 +9,7 @@ Testing should be proportional to risk. Auth, data mutations, payments, admin ac
 - Integration tests for API, Server Actions, and Supabase interactions where practical.
 - Playwright smoke tests for auth and critical user workflows.
 - Visual QA for important user-facing screens and reusable component states.
+- Runtime adapter validation for plugin manifests, native commands, portable `SKILL.md` wrappers, source-of-truth references, package allowlists, and secret safety.
 
 ## Critical Smoke Paths
 
@@ -52,6 +53,7 @@ Recommended baseline:
 - `agent-kit audit --min-readiness baseline-setup`
 - Playwright smoke tests for critical paths
 - Visual QA evidence for high-risk UI changes
+- `agent-kit adapter validate antigravity` and `agent-kit package validate` when adapter/package assets change
 
 ## Security-Focused Tests
 
@@ -62,6 +64,7 @@ Prioritize:
 - Unauthorized API calls
 - RLS-protected reads and writes
 - Service-role-only operations
+- Secret-like values in runtime adapter assets, generated sessions, static exports, docs, and package files
 
 ## Test Gaps
 

package/templates/next-supabase/UPGRADE.md

@@ -5,10 +5,12 @@ Use this file when upgrading Agent Kit, Next.js, Supabase, shared UI primitives,
 ## Agent Kit Upgrade Flow
 
 ```bash
-npx @agent-skills/next-supabase-kit@latest doctor
-npx @agent-skills/next-supabase-kit@latest diff
-npx @agent-skills/next-supabase-kit@latest update
-npx @agent-skills/next-supabase-kit@latest audit --min-readiness baseline-setup
+npx @appsforgood/next-supabase-kit@latest doctor
+npx @appsforgood/next-supabase-kit@latest diff
+npx @appsforgood/next-supabase-kit@latest update
+npx @appsforgood/next-supabase-kit@latest adapter validate antigravity
+npx @appsforgood/next-supabase-kit@latest setup --status
+npx @appsforgood/next-supabase-kit@latest audit --min-readiness baseline-setup
 ```
 
 Use `agent-kit audit --min-readiness best-practice-candidate` only after starter placeholders and upgrade evidence are replaced with project-specific evidence.
@@ -20,6 +22,8 @@ Use `agent-kit audit --min-readiness best-practice-candidate` only after starter
 - Review `.agent-kit/conflicts/` before accepting changed templates.
 - Preserve valid local customizations in `.agent-kit/overrides.json`.
 - Review `AGENTS.md`, `AGENT_ROSTER.md`, `ASSISTANT_ADAPTERS.md`, `MODEL_ROUTING.md`, `COUNCIL.md`, `QUALITY_GATES.md`, `SECURITY.md`, `TESTING.md`, and `DEPLOYMENT.md`.
+- If using Antigravity, review `.antigravity/agent-kit/plugin.json`, `.antigravity/agent-kit/commands/*.toml`, and `.antigravity/runtime-skills/*/SKILL.md`.
+- Validate runtime adapter assets with `agent-kit adapter validate antigravity`.
 - Record accepted tradeoffs in `DECISIONS.md`.
 - Update this file with package version, release notes, migration status, rollback notes, owner, and date.