@cubis/foundry 0.3.82 → 0.3.83

package/workflows/workflows/agent-environment-setup/platforms/antigravity/workflows/database.md

@@ -1,67 +0,0 @@
----
-command: "/database"
-description: "Design or review schema, queries, and migrations with performance and integrity controls."
-triggers: ["database", "sql", "schema", "migration", "index"]
----
-
-# Database Workflow
-
-## When to use
-
-Use this for schema design, query optimization, migration planning, or database architecture decisions.
-
-## Routing
-
-- Primary specialist: `.agent/agents/database-architect`
-- Implementation support: `.agent/agents/backend-specialist`
-- Verification support: `.agent/agents/test-engineer`
-
-## Context notes
-
-- This workflow file, active platform rules, and selected agents or skills guide execution.
-- Attach existing schema, migration history, query patterns, and performance requirements.
-- Read `ENGINEERING_RULES.md` and `TECH.md` before changing data ownership, persistence boundaries, or shared schema conventions.
-
-## Skill Routing
-
-- Primary skills: `database-design`, `database-design`, `database-design`
-- Supporting skills (optional): `drizzle-orm`, `database-design`, `database-design`, `database-design`, `database-design`, `database-design`, `database-design`, `database-design`, `database-design`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`
-- Start with `database-design` for schema work, `database-design` for performance, or `database-design` for general database operations. Add engine-specific skill when applicable.
-
-## Workflow steps
-
-1. Understand current schema and data model.
-2. Design or review proposed changes with normalization analysis.
-3. Plan migration with rollback strategy.
-4. Optimize queries and indexes for known access patterns.
-5. Validate data integrity constraints.
-6. Set `doc_impact` if the change alters data boundaries, core entities, or persistence patterns that future work should follow.
-
-## Verification
-
-- Schema changes maintain referential integrity.
-- Migrations are reversible or have documented rollback plan.
-- EXPLAIN output reviewed for performance-sensitive queries.
-- No breaking changes to existing consumers without migration plan.
-
-## Output Contract
-
-```yaml
-DATABASE_WORKFLOW_RESULT:
-  primary_agent: database-architect
-  supporting_agents: [backend-specialist?, test-engineer?]
-  primary_skills: [database-design, database-design, database-design]
-  supporting_skills: [<engine-specific-skill>?, drizzle-orm?]
-  schema_changes:
-    tables_affected: [<string>]
-    migration_plan: <string>
-    rollback_plan: <string>
-  query_optimization:
-    queries_reviewed: <number>
-    indexes_recommended: [<string>] | []
-  doc_impact: none | tech | rules | both
-  integrity_checks: [<string>]
-  follow_up_items: [<string>] | []
-```
-
-> **Antigravity note:** Use Agent Manager for parallel agent coordination. Workflow files are stored under `.agent/workflows/`.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/workflows/debug.md

@@ -1,63 +0,0 @@
----
-command: "/debug"
-description: "Isolate root cause quickly, apply the smallest safe remediation, and leave behind regression evidence."
-triggers: ["debug", "bug", "error", "incident", "stack trace"]
----
-
-# Debug Workflow
-
-## When to use
-
-Use this when behavior is failing, inconsistent, flaky, or only reproducible under certain conditions.
-
-## Routing
-
-- Primary specialist: `.agent/agents/debugger`
-- Domain implementation support: `.agent/agents/backend-specialist`, `.agent/agents/frontend-specialist`
-- Verification support: `.agent/agents/test-engineer`
-
-## Context notes
-
-- This workflow file, active platform rules, and selected agents or skills guide execution.
-- Attach stack traces, request IDs, traces, repro steps, recent diffs, and environment notes when context is incomplete.
-
-## Skill Routing
-
-- Primary skills: `systematic-debugging`, `observability`
-- Supporting skills (optional): `unit-testing`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`, `golang-best-practices`, `java-best-practices`, `csharp-best-practices`, `kotlin-best-practices`, `rust-best-practices`, `integration-testing`, `playwright-interactive`, `skill-creator`
-- Start with `systematic-debugging` for reproduce, isolate, instrument, and verify flow. Add `observability` when the failure involves error states, logging, or tracing gaps. Add the dominant language skill for exact code-path analysis, `integration-testing` or `playwright-interactive` when the failure lives in browser or release verification.
-
-## Workflow steps
-
-1. Reproduce the issue and record expected versus actual behavior.
-2. Narrow the fault domain with the smallest useful evidence.
-3. Fix the confirmed cause with the lowest regression risk.
-4. Add or update the regression proof.
-5. Document any remaining uncertainty or environment-specific gaps.
-
-## Verification
-
-- Re-run the failing scenario first.
-- Run focused regression checks on adjacent high-risk paths.
-- Call out any remaining gaps if the full environment could not be reproduced.
-
-## Output Contract
-
-```yaml
-DEBUG_WORKFLOW_RESULT:
-  primary_agent: debugger
-  supporting_agents: [backend-specialist?, frontend-specialist?, test-engineer?]
-  primary_skills: [systematic-debugging, observability]
-  supporting_skills: [unit-testing?, <language-skill>?, integration-testing?, playwright-interactive?]
-  reproduction:
-    steps: [<string>]
-    expected_vs_actual: <string>
-  root_cause: <string>
-  remediation:
-    summary: <string>
-    changed_artifacts: [<path-or-artifact>]
-  regression_checks: [<command or test>]
-  follow_up_items: [<string>] | []
-```
-
-> **Antigravity note:** Use Agent Manager for parallel agent coordination. Workflow files are stored under `.agent/workflows/`.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/workflows/devops.md

@@ -1,78 +0,0 @@
----
-command: "/devops"
-description: "Plan and execute deployment, CI/CD, incident response, and operational safety changes with rollback controls."
-triggers:
-  [
-    "devops",
-    "deploy",
-    "ci",
-    "cd",
-    "rollback",
-    "infra",
-    "incident",
-    "outage",
-    "sev",
-    "degraded",
-    "hotfix",
-    "recovery",
-  ]
----
-
-# DevOps Workflow
-
-## When to use
-
-Use this for deployment automation, CI/CD pipeline changes, incident response, or infrastructure operations.
-
-## Routing
-
-- Primary specialist: `.agent/agents/ci-cd-pipeline`
-- Reliability support: `.agent/agents/observability`
-- Verification support: `.agent/agents/validator`
-
-## Context notes
-
-- This workflow file, active platform rules, and selected agents or skills guide execution.
-- Attach deployment targets, pipeline configs, incident details, and infrastructure specs.
-
-## Skill Routing
-
-- Primary skills: `ci-cd-pipeline`, `ci-cd-pipeline`, `kubernetes-deploy`
-- Supporting skills (optional): `observability`, `observability`, `ci-cd-pipeline`, `git-workflow`, `systematic-debugging`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`, `golang-best-practices`
-- Start with `ci-cd-pipeline` for operational patterns. Add `ci-cd-pipeline` for pipeline work, `kubernetes-deploy` for container operations, `observability` for incident response, `ci-cd-pipeline` for serverless infrastructure.
-
-## Workflow steps
-
-1. Assess current state and change scope.
-2. Plan change with rollback strategy.
-3. Apply change in staged manner (dev → staging → production).
-4. Verify health at each stage before proceeding.
-5. Document operational procedures and runbooks.
-
-## Verification
-
-- Change applied successfully with no service degradation.
-- Rollback procedure verified or documented.
-- Monitoring confirms normal operation after change.
-- Runbook updated for new procedures.
-
-## Output Contract
-
-```yaml
-DEVOPS_WORKFLOW_RESULT:
-  primary_agent: ci-cd-pipeline
-  supporting_agents: [observability?, validator?]
-  primary_skills: [ci-cd-pipeline, ci-cd-pipeline, kubernetes-deploy]
-  supporting_skills: [observability?, observability?, ci-cd-pipeline?]
-  change:
-    description: <string>
-    blast_radius: <string>
-    rollback_plan: <string>
-  execution:
-    stages_completed: [<string>]
-    health_checks: [<string>]
-  operational_docs: [<string>] | []
-  follow_up_items: [<string>] | []
-```
-
-> **Antigravity note:** Use Agent Manager for parallel agent coordination. Workflow files are stored under `.agent/workflows/`.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/workflows/migrate.md

@@ -1,78 +0,0 @@
----
-command: "/migrate"
-description: "Plan and execute technology migrations, framework upgrades, and dependency updates with rollback safety, incremental verification, and zero-downtime transition."
-triggers:
-  [
-    "migrate",
-    "upgrade",
-    "update dependency",
-    "framework upgrade",
-    "version bump",
-    "major update",
-  ]
----
-
-# Migrate Workflow
-
-## When to use
-
-Use this for technology migrations, framework upgrades, dependency updates, or major version transitions.
-
-## Routing
-
-- Primary specialist: `.agent/agents/code-archaeologist`
-- Implementation support: `.agent/agents/backend-specialist`, `.agent/agents/frontend-specialist`
-- Verification support: `.agent/agents/test-engineer`, `.agent/agents/validator`
-
-## Context notes
-
-- This workflow file, active platform rules, and selected agents or skills guide execution.
-- Attach the migration target, current versions, breaking change lists, and impact assessment.
-- Read `ENGINEERING_RULES.md` and `docs/foundation/TECH.md` first because migrations often change accepted patterns and current-state architecture at the same time. After migration, flag updates needed in `docs/foundation/ARCHITECTURE.md` for `## Risks And Tech Debt`.
-
-## Skill Routing
-
-- Primary skills: `system-design`, `system-design`
-- Supporting skills (optional): `code-review`, `unit-testing`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`, `golang-best-practices`
-- Start with `system-design` for migration methodology and `system-design` for system impact. Add `code-review` for automated codemod or compatibility analysis.
-
-## Workflow steps
-
-1. Assess current state and migration target.
-2. Map breaking changes and affected code paths.
-3. Plan incremental migration steps with rollback points.
-4. Execute migration one step at a time with verification.
-5. Update tests and documentation for new patterns.
-6. Set `doc_impact` when the migration changes architecture, deployment shape, boundaries, or design-system rules.
-7. Verify full system behavior after migration complete.
-
-## Verification
-
-- All breaking changes addressed.
-- Tests pass on migrated code.
-- Rollback tested at each migration step.
-- No degradation in performance or functionality.
-- Documentation updated for new patterns.
-
-## Output Contract
-
-```yaml
-MIGRATE_WORKFLOW_RESULT:
-  primary_agent: code-archaeologist
-  supporting_agents: [backend-specialist?, frontend-specialist?, test-engineer?, validator?]
-  primary_skills: [system-design, system-design]
-  supporting_skills: [code-review?, unit-testing?]
-  migration:
-    from: <string>
-    to: <string>
-    breaking_changes: [<string>]
-    steps_completed: [<string>]
-    rollback_points: [<string>]
-  verification:
-    tests_passed: true | false
-    performance_impact: <string>
-  doc_impact: none | tech | rules | both
-  follow_up_items: [<string>] | []
-```
-
-> **Antigravity note:** Use Agent Manager for parallel agent coordination. Workflow files are stored under `.agent/workflows/`.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/workflows/mobile.md

@@ -1,71 +0,0 @@
----
-command: "/mobile"
-description: "Drive mobile implementation decisions for Flutter/cross-platform behavior and reliability."
-triggers: ["mobile", "flutter", "ios", "android", "navigation"]
----
-
-# Mobile Workflow
-
-## When to use
-
-Use this for mobile app development, Flutter architecture, Stitch-driven mobile screen handoff, native integrations, or platform-specific behavior.
-
-## Routing
-
-- Primary specialist: `.agent/agents/mobile-developer`
-- Design support: `.agent/agents/frontend-specialist`
-- Verification support: `.agent/agents/test-engineer`
-
-## Context notes
-
-- This workflow file, active platform rules, and selected agents or skills guide execution.
-- Attach platform targets (iOS, Android, both), Flutter version, and relevant screen/feature context.
-- Read `ENGINEERING_RULES.md` and `docs/foundation/TECH.md` before implementing non-trivial mobile work so screens and features follow the declared architecture and design-system rules. Check `docs/foundation/PRODUCT.md` for `## Domain Glossary` to use consistent terminology.
-
-## Skill Routing
-
-- Primary skills: `expo-app`, `react-native`
-- Supporting skills (optional): `stitch`, `frontend-design`, `expo-app`, `expo-app`, `expo-app`, `expo-app`, `expo-app`, `expo-app`, `expo-app`, `expo-app`, `expo-app`, `swift-best-practices`, `kotlin-best-practices`
-- Start with `expo-app` for feature implementation and `react-native` for UX patterns. Add framework-specific Flutter skill when applicable. Add `frontend-design` for multi-language support.
-- When the request starts from Stitch artifacts or a design sync, load `stitch` first and then pair it with `react-native` plus the narrowest mobile implementation skill for the target stack.
-
-## Workflow steps
-
-1. Clarify platform targets and feature requirements.
-2. Design architecture with platform-appropriate patterns.
-3. Implement with consideration for iOS/Android differences.
-4. Write widget and integration tests.
-5. Review for platform-specific edge cases and UX conventions.
-6. Set `doc_impact` if the feature changes navigation, shared UI rules, or mobile architecture conventions.
-
-## Verification
-
-- Runs correctly on both target platforms.
-- Platform-specific conventions respected (iOS/Android).
-- Touch targets and gesture feedback appropriate.
-- Widget tests cover core behavior.
-- Offline behavior tested if applicable.
-
-## Output Contract
-
-```yaml
-MOBILE_WORKFLOW_RESULT:
-  primary_agent: mobile-developer
-  supporting_agents: [frontend-specialist?, test-engineer?]
-  primary_skills: [expo-app, react-native]
-  supporting_skills: [stitch?, frontend-design?, expo-app?, expo-app?, <flutter-specific>?]
-  implementation:
-    platforms: [ios, android]
-    architecture_decisions: [<string>]
-    changed_artifacts: [<path>]
-  testing:
-    widget_tests: [<path>]
-    integration_tests: [<path>] | []
-  platform_notes:
-    ios: [<string>] | []
-    android: [<string>] | []
-  doc_impact: none | tech | rules | both
-  follow_up_items: [<string>] | []
-```
-
-> **Antigravity note:** Use Agent Manager for parallel agent coordination. Workflow files are stored under `.agent/workflows/`.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/workflows/onboard.md

@@ -1,72 +0,0 @@
----
-command: "/onboard"
-description: "Survey an unfamiliar codebase, map its architecture, identify patterns and conventions, and produce a structured orientation report for new contributors."
-triggers:
-  [
-    "onboard",
-    "explore codebase",
-    "understand project",
-    "new to this repo",
-    "codebase survey",
-  ]
----
-
-# Onboard Workflow
-
-## When to use
-
-Use this when joining a new project, exploring an unfamiliar codebase, or preparing orientation material.
-
-## Routing
-
-- Primary specialist: `.agent/agents/researcher`
-- Architecture mapping: `.agent/agents/code-archaeologist`
-- Domain specialists as needed: `.agent/agents/backend-specialist`, `.agent/agents/frontend-specialist`
-
-## Context notes
-
-- This workflow file, active platform rules, and selected agents or skills guide execution.
-- Provide the repo URL, focus areas, and any specific questions to answer during onboarding.
-- Read `ENGINEERING_RULES.md` first, then `docs/foundation/TECH.md`, `docs/foundation/PRODUCT.md`, and `docs/foundation/ARCHITECTURE.md` when present so onboarding distinguishes the intended contract from current implementation reality. Use the `## Domain Glossary` in PRODUCT.md to learn project-specific terms, and `## Build And Validation` in TECH.md to set up the local environment.
-
-## Skill Routing
-
-- Primary skills: `deep-research`, `system-design`
-- Supporting skills (optional): `system-design`, `database-design`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`
-- Start with `deep-research` for systematic exploration and `system-design` for architecture mapping. Add `system-design` for undocumented systems. Prefer repo evidence first; use external sources only when setup or dependency behavior cannot be confirmed locally.
-
-## Workflow steps
-
-1. Survey the project structure — directories, entry points, and configuration.
-2. Map the architecture — components, data flow, and integration points.
-3. Identify patterns — naming conventions, design patterns, and coding standards.
-4. Document dependencies — external services, databases, and APIs.
-5. Produce orientation report with development setup instructions.
-
-## Verification
-
-- All major components identified and documented.
-- Development setup instructions verified (can be followed by a newcomer).
-- Architecture diagram or description covers main data flows.
-- Key patterns and conventions explicitly documented.
-
-## Output Contract
-
-```yaml
-ONBOARD_WORKFLOW_RESULT:
-  primary_agent: researcher
-  supporting_agents: [code-archaeologist?, backend-specialist?, frontend-specialist?]
-  primary_skills: [deep-research, system-design]
-  supporting_skills: [system-design?, database-design?]
-  project_overview:
-    purpose: <string>
-    tech_stack: [<string>]
-    architecture: <string>
-  key_components: [<string>]
-  patterns_and_conventions: [<string>]
-  development_setup: [<step>]
-  dependencies: [<string>]
-  knowledge_gaps: [<string>] | []
-```
-
-> **Antigravity note:** Use Agent Manager for parallel agent coordination. Workflow files are stored under `.agent/workflows/`.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/workflows/refactor.md

@@ -1,67 +0,0 @@
----
-command: "/refactor"
-description: "Improve maintainability while preserving behavior through incremental safe refactoring."
-triggers: ["refactor", "cleanup", "maintainability", "debt", "modularize"]
----
-
-# Refactor Workflow
-
-## When to use
-
-Use this when improving code structure, reducing tech debt, or modularizing without changing behavior.
-
-## Routing
-
-- Primary specialist: `.agent/agents/code-archaeologist`
-- Domain support: `.agent/agents/backend-specialist`, `.agent/agents/frontend-specialist`
-- Verification support: `.agent/agents/test-engineer`, `.agent/agents/validator`
-
-## Context notes
-
-- This workflow file, active platform rules, and selected agents or skills guide execution.
-- Attach the target code, pain points, and any constraints on what can change.
-- Read `ENGINEERING_RULES.md` and `docs/foundation/TECH.md` first so behavior-preserving structure changes do not drift from the accepted architecture contract. Check `docs/foundation/ARCHITECTURE.md` for `## Dependency Rules` and `## Crosscutting Concerns` before restructuring.
-
-## Skill Routing
-
-- Primary skills: `code-review`, `system-design`
-- Supporting skills (optional): `unit-testing`, `system-design`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`, `golang-best-practices`
-- Start with `code-review` for automated code quality assessment. Add `system-design` for modernization patterns. Add `unit-testing` when refactoring needs test coverage to proceed safely.
-
-## Workflow steps
-
-1. Map the current structure and identify refactoring targets.
-2. Ensure adequate test coverage before modifying (add tests if needed).
-3. Apply one refactoring at a time with behavior preservation.
-4. Verify behavior unchanged after each step.
-5. Document the improved structure and any conventions established.
-6. Set `doc_impact` when the refactor changes project structure, module boundaries, or design-system conventions.
-
-## Verification
-
-- All existing tests pass after each refactoring step.
-- No behavioral changes introduced (unless explicitly intended).
-- Code quality metrics improved (complexity, coupling, cohesion).
-- New tests added for any gaps discovered during refactoring.
-
-## Output Contract
-
-```yaml
-REFACTOR_WORKFLOW_RESULT:
-  primary_agent: code-archaeologist
-  supporting_agents: [backend-specialist?, frontend-specialist?, test-engineer?, validator?]
-  primary_skills: [code-review, system-design]
-  supporting_skills: [unit-testing?, system-design?]
-  refactoring_summary:
-    targets: [<string>]
-    changes_applied: [<string>]
-    behavior_preserved: true | false
-  quality_improvement:
-    complexity_before: <string>
-    complexity_after: <string>
-  doc_impact: none | tech | rules | both
-  tests_added: [<test-file-path>] | []
-  follow_up_items: [<string>] | []
-```
-
-> **Antigravity note:** Use Agent Manager for parallel agent coordination. Workflow files are stored under `.agent/workflows/`.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/workflows/release.md

@@ -1,70 +0,0 @@
----
-command: "/release"
-description: "Prepare and execute release with rollout guardrails, verification, and rollback plan."
-triggers: ["release", "deploy", "rollout", "ship", "go-live"]
----
-
-# Release Workflow
-
-## When to use
-
-Use this when preparing a release, deploying to production, or managing a rollout.
-
-## Routing
-
-- Primary coordinator: `.agent/agents/ci-cd-pipeline`
-- Release verification: `.agent/agents/test-engineer`, `.agent/agents/validator`
-- Documentation: `.agent/agents/documentation-writer`
-
-## Context notes
-
-- This workflow file, active platform rules, and selected agents or skills guide execution.
-- Attach the release scope, version number, changelog draft, and deployment target.
-- Read `ENGINEERING_RULES.md` and `docs/foundation/TECH.md` before release if the shipped changes touched architecture, scaling assumptions, or design-system rules. Check `docs/foundation/TECH.md` for `## Build And Validation` and `## CI CD Pipeline` steps to verify the release pipeline.
-
-## Skill Routing
-
-- Primary skills: `ci-cd-pipeline`, `git-workflow`
-- Supporting skills (optional): `tech-doc`, `ci-cd-pipeline`, `observability`, `kubernetes-deploy`, `observability`, `ci-cd-pipeline`, `typescript-best-practices`, `javascript-best-practices`
-- Start with `ci-cd-pipeline` for deployment automation and `git-workflow` for release branching. Add `tech-doc` for release notes.
-
-## Workflow steps
-
-1. Finalize scope — confirm all changes are merged and tested.
-2. Generate changelog and release notes.
-3. Prepare deployment artifacts and configuration.
-4. Execute staged rollout with health checks at each stage.
-5. Verify production health post-deployment.
-6. Document rollback procedure and post-release status.
-7. Set `doc_impact` if the release includes architecture-affecting work that should refresh the managed docs.
-
-## Verification
-
-- All tests pass on release branch/tag.
-- Changelog accurately reflects changes.
-- Deployment artifacts built and verified.
-- Production health confirmed after rollout.
-- Rollback procedure tested or documented.
-
-## Output Contract
-
-```yaml
-RELEASE_WORKFLOW_RESULT:
-  primary_agent: ci-cd-pipeline
-  supporting_agents: [test-engineer?, validator?, documentation-writer?]
-  primary_skills: [ci-cd-pipeline, git-workflow]
-  supporting_skills: [tech-doc?, ci-cd-pipeline?, observability?]
-  release:
-    version: <string>
-    changelog: <string>
-    artifacts: [<string>]
-  deployment:
-    strategy: <staged | canary | blue-green | direct>
-    stages_completed: [<string>]
-    health_checks: [<string>]
-  rollback_plan: <string>
-  doc_impact: none | tech | rules | both
-  follow_up_items: [<string>] | []
-```
-
-> **Antigravity note:** Use Agent Manager for parallel agent coordination. Workflow files are stored under `.agent/workflows/`.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/workflows/review.md

@@ -1,66 +0,0 @@
----
-command: "/review"
-description: "Run a strict review for bugs, regressions, accessibility issues, security risk, and code quality with prioritized findings."
-triggers: ["review", "audit", "pr", "quality", "security review"]
----
-
-# Review Workflow
-
-## When to use
-
-Use this for code review, PR review, or quality audit of existing code changes.
-
-## Routing
-
-- Primary specialist: `.agent/agents/frontend-specialist` (for frontend code) or `.agent/agents/backend-specialist` (for backend code)
-- Security review: `.agent/agents/security-auditor`
-- Quality validation: `.agent/agents/validator`
-- Verification support: `.agent/agents/test-engineer`
-
-## Context notes
-
-- This workflow file, active platform rules, and selected agents or skills guide execution.
-- Attach the PR diff, changed files, or specific code paths to review.
-
-## Skill Routing
-
-- Primary skills: `code-review`, `code-review`, `unit-testing`
-- Supporting skills (optional): `owasp-security-review`, `owasp-security-review`, `performance-testing`, `react`, `nextjs`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`, `golang-best-practices`
-- Start with `code-review` for UI code or `code-review` for backend code. Add `unit-testing` when evaluating test quality. Add `owasp-security-review` for security-sensitive changes.
-
-## Workflow steps
-
-1. Understand the intent and scope of the changes.
-2. Review for correctness — logic bugs, edge cases, and regressions.
-3. Review for security — input validation, auth, secrets exposure.
-4. Review for accessibility — WCAG compliance, keyboard navigation, screen readers.
-5. Review for performance — unnecessary re-renders, N+1 queries, bundle impact.
-6. Prioritize findings by severity and provide actionable feedback.
-
-## Verification
-
-- Each finding has severity, location, and suggested fix.
-- Findings prioritized: critical > high > medium > low.
-- Positive observations noted alongside issues.
-- Reviewed against codebase conventions.
-
-## Output Contract
-
-```yaml
-REVIEW_WORKFLOW_RESULT:
-  primary_agent: <frontend-specialist | backend-specialist>
-  supporting_agents: [security-auditor?, validator?, test-engineer?]
-  primary_skills: [code-review?, code-review?, unit-testing?]
-  supporting_skills: [owasp-security-review?, owasp-security-review?, performance-testing?]
-  findings:
-    - severity: critical | high | medium | low
-      category: correctness | security | accessibility | performance | style
-      location: <file:line>
-      description: <string>
-      suggestion: <string>
-  overall_assessment: approve | request_changes | reject
-  positive_observations: [<string>] | []
-  follow_up_items: [<string>] | []
-```
-
-> **Antigravity note:** Use Agent Manager for parallel agent coordination. Workflow files are stored under `.agent/workflows/`.