@appsforgood/next-supabase-kit 0.3.0 → 0.4.0

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

package/assistant-adapters/antigravity.md

@@ -1,65 +0,0 @@
-# Antigravity Adapter
-
-This adapter packages Agent Kit as native Antigravity-style plugin assets while keeping the Agent Kit council contract canonical.
-
-## Source Of Truth
-
-- `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/corrections/project-rules.json`
-- `.agent-kit/corrections/agent-rules.json`
-- `COUNCIL.md`
-- `.agent-kit/council-sessions/`
-- `QUALITY_GATES.md`
-
-Runtime command files must wrap those files. Do not fork role definitions, security policy, frontend quality rules, release gates, or session evidence rules into command prompts.
-
-Antigravity commands are instruction adapters. They do not replace or prove execution by `@appsforgood/agent-kit-runtime`; use `agent-kit orchestrate status` and exported run evidence for that claim.
-
-## Activation
-
-```bash
-agent-kit init --activate antigravity
-agent-kit adapter validate antigravity
-```
-
-This installs:
-
-- `.antigravity/agent-kit/plugin.json`
-- `.antigravity/agent-kit/commands/*.toml`
-- `.antigravity/runtime-skills/*/SKILL.md`
-- `.antigravity/agent-kit/README.md`
-
-If the `agy` CLI is available, teams may additionally run its native plugin validation. Agent Kit only requires structural validation because many projects will not have Antigravity installed locally.
-
-## Command Contract
-
-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
-
-Do not place tokens, credentials, private URLs, database URLs, customer data, or hidden model reasoning in Antigravity plugin files, command files, or runtime skills.

package/assistant-adapters/claude-code-subagents.md

@@ -1,38 +0,0 @@
-# Claude Code Subagent Adapter
-
-Claude Code projects can activate Agent Kit by creating project subagents that point back to the canonical council files.
-
-Use `MODEL_ROUTING.md` and `.agent-kit/model-routing.json` when adding model comments or frontmatter to those subagents.
-
-## Suggested Project Layout
-
-```text
-.claude/
-  agents/
-    planner.md
-    lead-architect.md
-    frontend-design-lead.md
-    security-reviewer.md
-    qa-engineer.md
-```
-
-## Subagent Frontmatter Pattern
-
-```md
----
-name: planner
-description: Use for planning, phasing, scope breakdown, workflow routing, and council setup in this repository.
----
-
-Read `AGENTS.md`, `AGENT_ROSTER.md`, `.agent-kit/agent-roster.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/`, and `QUALITY_GATES.md` before making routing decisions.
-
-Start with the Planner workflow. For core changes, hand off to Lead Architect. For frontend changes, require Frontend Design Lead evidence. For auth, RLS, secrets, dependency, external-call, or release-risk changes, require Security Reviewer. Record meaningful decisions, risks, handoffs, human corrections, artifacts, evidence, and verification through Agent Studio session files when available.
-```
-
-## Guardrails
-
-- Keep detailed role behavior in `AGENTS.md` and `AGENT_ROSTER.md`; subagent files should be focused entry points.
-- Document active subagents and verification evidence in `ASSISTANT_ADAPTERS.md`.
-- Record model-selection evidence and limitations in `ASSISTANT_ADAPTERS.md`.
-- Avoid giving a subagent broader tool access than its role needs.
-- Treat Claude subagents as instruction adapters. Use `agent-kit orchestrate ...` and its run evidence when the task requires the executable checkpointed council.

package/assistant-adapters/codex-agents.md

@@ -1,53 +0,0 @@
-# Codex / AGENTS.md Adapter
-
-Use `AGENTS.md` as the primary project instruction surface.
-
-## Required References
-
-- `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`
-
-## Council Custom Agents
-
-After `agent-kit init --activate codex`, council specialists live in `.codex/agents/*.toml`.
-
-Spawn a dedicated custom agent instead of role-playing the whole council in one thread:
-
-- **Planning / scope:** `.codex/agents/planner.toml`
-- **Security / RLS / secrets:** `.codex/agents/security-reviewer.toml` (high reasoning effort)
-- **Frontend UI:** `.codex/agents/frontend-design-lead.toml`
-- **QA / tests:** `.codex/agents/qa-engineer.toml`
-
-Each file sets `model_reasoning_effort` from `.agent-kit/model-routing.json`. Verify model names in your Codex environment against `MODEL_ROUTING.md`.
-
-## Operating Rule
-
-When a task is planning-oriented, ambiguous, risky, frontend-facing, security-sensitive, or release-related, start from the roster workflow instead of treating the request as a single generic implementation pass.
-
-Use `MODEL_ROUTING.md` to choose the model profile or reasoning effort for the active role. Exact model names belong in dated config comments, not in the role definitions.
-
-Before meaningful work, load project context, agent briefs when present, and active correction rules. For meaningful handoffs, record visible decisions and evidence with `agent-kit session checkpoint --file <json>` or individual `agent-kit session ...` commands, then run `agent-kit session render`.
-
-## Verification
-
-Record in `ASSISTANT_ADAPTERS.md`:
-
-- The tool/version or environment where `AGENTS.md` was observed.
-- The command, session, or screenshot that proves the instructions loaded.
-- The model-selection setting or profile used for the active role.
-- Any known limitations or manual invocation steps.
-
-Run `agent-kit adapter validate codex` after activation.
-
-Codex custom agents are instruction adapters. Use `agent-kit orchestrate validate`, `plan`, `run`, and `status` when a task requires the executable checkpointed council; do not infer graph execution from a delegated IDE thread.

package/assistant-adapters/cursor-frontend.mdc

@@ -1,16 +0,0 @@
----
-description: Require Frontend Design Lead evidence for significant UI and component work.
-globs:
-  - "src/app/**"
-  - "src/components/**"
-  - "**/*.css"
-alwaysApply: false
----
-
-# Frontend design gate reminders
-
-Significant UI changes require **Frontend Design Lead** review: brand/content intake, creative-direction rationale, reference-led critique, product-quality scorecard, accessibility, and visual QA evidence.
-
-Delegate to `@frontend-design-lead` in `.cursor/agents/frontend-design-lead.md` for isolated design review context.
-
-Reject generic AI-looking UI that is not specific to the product workflow and content model.

package/assistant-adapters/cursor-planner.mdc

@@ -1,14 +0,0 @@
----
-description: Route ambiguous, planning, and cross-layer requests through the Planner workflow first.
-globs:
-  - "**/*"
-alwaysApply: false
----
-
-# Planner routing
-
-When a request is ambiguous, planning-oriented, roadmap-related, or spans multiple layers, start with the **Planner** workflow before implementation.
-
-Delegate to the `@planner` subagent in `.cursor/agents/planner.md` when the task needs isolated planning context.
-
-Read `AGENTS.md`, `.agent-kit/agent-roster.json`, `MODEL_ROUTING.md`, project context, and active corrections before choosing a workflow.

package/assistant-adapters/cursor-security.mdc

@@ -1,18 +0,0 @@
----
-description: Require Security Reviewer for auth, RLS, secrets, API mutations, and external calls.
-globs:
-  - "supabase/**"
-  - "**/auth/**"
-  - "**/api/**"
-  - "**/middleware.ts"
-  - "**/proxy.ts"
-alwaysApply: false
----
-
-# Security gate reminders
-
-Auth, RLS, data mutation, dependency, secret, external-call, and release-risk changes require **Security Reviewer** review before acceptance.
-
-Delegate to `@security-reviewer` in `.cursor/agents/security-reviewer.md` or Task `security-review` for isolated review context.
-
-Verify OWASP Top 10, IDOR, SSRF, injection, broken auth, and least-privilege boundaries.

package/assistant-adapters/github-copilot-instructions.md

@@ -1,35 +0,0 @@
-# Repository Instructions
-
-This repository uses Agent Kit. Treat `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/`, and `QUALITY_GATES.md` as the source of truth for agent routing, project context, correction rules, model profiles, quality gates, and handoff evidence.
-
-## Workflows
-
-- Planning, phased roadmap, or ambiguous work starts with Planner.
-- Core changes require Lead Architect before implementation.
-- Frontend changes require Frontend Design Lead, brand/content intake, creative-direction rationale, visual QA evidence, state coverage, accessibility checks, and desktop/mobile verification.
-- Auth, RLS, data mutations, dependency changes, external calls, secrets, and release risk require Security Reviewer.
-- Behavior changes require QA evidence.
-- Significant changes require Documentation Maintainer updates.
-- Meaningful work should read local project context and active correction rules before implementation.
-- User corrections should be recorded before continuing, then applied to future sessions when durable.
-- Meaningful multi-agent work should record visible decisions, handoffs, artifacts, and verification in Agent Studio session files when available.
-
-## Validation
-
-Before proposing completion, run the repo's documented checks. For projects installed from this kit, the minimum setup check is:
-
-```sh
-agent-kit audit --min-readiness baseline-setup
-```
-
-Use a stronger gate before claiming best-practice readiness:
-
-```sh
-agent-kit audit --min-readiness best-practice-candidate
-```
-
-Do not claim best-practice readiness while starter placeholders remain in `COUNCIL.md`, `SPEC.md`, `DESIGN.md`, `SECURITY.md`, `TESTING.md`, `DEPLOYMENT.md`, or `ASSISTANT_ADAPTERS.md`.
-
-## Model Selection
-
-Use the active Copilot model selector or organization policy with `MODEL_ROUTING.md`. Repository instructions advise model choice but should not be treated as hard enforcement where Copilot keeps model selection user-controlled.

package/assistant-adapters/github-next-supabase.instructions.md

@@ -1,28 +0,0 @@
----
-applyTo: "app/**/*.{ts,tsx},src/app/**/*.{ts,tsx},pages/**/*.{ts,tsx},src/pages/**/*.{ts,tsx},components/**/*.{ts,tsx},lib/**/*.{ts,tsx},utils/**/*.{ts,tsx},supabase/**/*,*.sql"
----
-
-# Next.js + Supabase Agent Kit Instructions
-
-Follow `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/`, and `QUALITY_GATES.md`.
-
-## Next.js
-
-- Keep Server Component, Client Component, Route Handler, and Server Action boundaries explicit.
-- Do not expose secrets, service-role keys, privileged queries, or admin-only data to client bundles.
-- Preserve loading, empty, error, disabled, success, focus, and mobile states for user-facing changes.
-
-## Supabase
-
-- Enforce authorization with Postgres RLS where applicable.
-- Treat service-role access as server-only.
-- Document migration order, rollback risk, indexes, constraints, and policy changes.
-
-## Council Routing
-
-- Schema, auth, RLS, API behavior, dependency, and release changes require Lead Architect and Security Reviewer handoff.
-- UI changes require Frontend Design Lead evidence before implementation is accepted.
-- Behavior changes require QA evidence and living-doc updates.
-- Use the model profile in `MODEL_ROUTING.md`; treat Copilot model selection as advisory unless the active tool surface can enforce it.
-- Read project context and active corrections before changing behavior.
-- Record visible decisions, handoffs, human corrections, artifacts, and verification with Agent Studio session commands when available.

package/assistant-adapters/model-selection/claude-code-subagents-with-models.md

@@ -1,32 +0,0 @@
-# Claude Code Subagents With Model Notes
-
-Use this as a starter for `.claude/agents/*.md` files. Keep the canonical role definitions in `AGENTS.md` and `AGENT_ROSTER.md`.
-
-```md
----
-name: lead-architect
-description: Use for core architecture, cross-layer changes, package behavior, and technical decisions.
-# June 2026 Agent Kit suggestion:
-# model: opus
-# effort: high
----
-
-Read `AGENTS.md`, `AGENT_ROSTER.md`, `MODEL_ROUTING.md`, `.agent-kit/agent-roster.json`, and `.agent-kit/model-routing.json`.
-
-Review affected layers, preserved behavior, security impact, test plan, docs impact, and required council handoffs before implementation.
-```
-
-```md
----
-name: frontend-design-lead
-description: Use for creative direction, reference-led critique, frontend distinctiveness, product-quality scorecards, and visual QA.
-# June 2026 Agent Kit suggestion:
-# model: opus
-# effort: high
----
-
-Use `DESIGN.md`, `STYLE_GUIDE.md`, `MODEL_ROUTING.md`, and the frontend skills before accepting significant UI work.
-Reject generic AI-looking UI that is not specific to the product content, workflow, audience, and state model.
-```
-
-Record the actual Claude Code behavior, model field support, date, and owner in `ASSISTANT_ADAPTERS.md`.

package/assistant-adapters/model-selection/codex-config.example.toml

@@ -1,32 +0,0 @@
-# Codex model-selection example for Agent Kit.
-# Copy the relevant comments into ~/.codex/config.toml or a trusted project .codex/config.toml.
-# Verify current model availability in your Codex environment before uncommenting.
-#
-# Custom council agents generated by agent-kit live under .codex/agents/*.toml.
-# Run `agent-kit init --activate codex` to create them from the project roster.
-
-# June 2026 Agent Kit suggested baseline:
-# model = "gpt-5.5"
-# model_reasoning_effort = "medium"
-
-# Use high reasoning for Lead Architect, Security Reviewer, and Supabase/Postgres Engineer
-# when spawning custom Codex agents or starting dedicated review threads.
-# model_reasoning_effort = "high"
-
-# Optional custom-agent files can live under .codex/agents/*.toml.
-# Keep each custom agent narrow and point it back to:
-# - AGENTS.md
-# - AGENT_ROSTER.md
-# - .agent-kit/agent-roster.json
-# - MODEL_ROUTING.md
-# - .agent-kit/model-routing.json
-
-# Example custom-agent fragment:
-# name = "lead-architect"
-# description = "Architecture and core-change council review."
-# model = "gpt-5.5"
-# model_reasoning_effort = "high"
-# developer_instructions = """
-# Read AGENTS.md, AGENT_ROSTER.md, MODEL_ROUTING.md, and .agent-kit/agent-roster.json.
-# Review affected layers, preserved behavior, tradeoffs, security impact, test plan, and docs impact.
-# """