@cubis/foundry 0.3.83 → 0.3.84

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/frontend-design-implementation-handoff/SKILL.md

@@ -0,0 +1,43 @@
+---
+name: frontend-design-implementation-handoff
+description: Translate design-engine output into repo-native implementation work, preferring real components, Flutter widgets, and existing tokens over pasted generated markup.
+---
+# Frontend Design Implementation Handoff
+
+## Purpose
+
+Convert the design-engine result into implementation work that matches the repo's real stack and components instead of copying raw generated artifacts.
+
+## When to Use
+
+- After Stitch returns a screen artifact
+- After a design screen brief is approved for implementation
+- When moving from design state into Flutter, React, or another real UI stack
+
+## Instructions
+
+1. **Prefer existing components and tokens first** — Reuse the repo's real primitives before creating new visual fragments.
+2. **Translate semantics, not markup** — A generated artifact is a seed. Rebuild it in the target stack using the same hierarchy and state model.
+3. **For Flutter, map into widgets and theme tokens** — Use theme extensions, shared cards, section headers, and navigation widgets instead of porting web structure literally.
+4. **Preserve the brief's anti-slop constraints** — Distinctive typography, component rhythm, and motion rules should survive the handoff.
+5. **Leave QA hooks behind** — Ensure semantics labels, stable copy, and navigable flows are good enough for `flutter-mobile-qa` or frontend tests.
+
+## Output Format
+
+Deliver:
+
+1. Implementation plan
+2. Components/widgets to create or reuse
+3. Token/theme mapping
+4. QA-readiness notes
+
+## Antigravity Platform Notes
+
+- Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
+- TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
+- Rules file relative to the mirrored skill directory: `../../rules/GEMINI.md`.
+- Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
+- Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
+- Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.
+- MCP skill tools (`skill_search`, `skill_get`, `skill_validate`, `skill_get_reference`) are available when Cubis Foundry MCP is configured.
+- User arguments are passed as natural language via `{{args}}` in TOML command prompts.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/frontend-design-mobile-patterns/SKILL.md

@@ -0,0 +1,43 @@
+---
+name: frontend-design-mobile-patterns
+description: Adapt the design engine to mobile and Flutter surfaces using Foundry's normalized mobile-pattern dataset and implementation-first constraints.
+---
+# Frontend Design Mobile Patterns
+
+## Purpose
+
+Translate the design engine into mobile-specific decisions that survive real Flutter implementation instead of staying as web-first UI ideas.
+
+## When to Use
+
+- Designing Flutter screens, flows, or navigation
+- Adapting a Stitch-inspired concept into a mobile-native screen brief
+- Reviewing whether a design will survive small screens and thumb-driven interaction
+
+## Instructions
+
+1. **Load `workflows/design-datasets/mobile-patterns.json` first** — Use it to shape navigation placement, card rhythm, CTA placement, and progress visibility.
+2. **Design for thumb reach and scroll rhythm** — Primary actions should stay reachable and section breaks should remain scannable on smaller screens.
+3. **Prefer Flutter-feasible patterns** — Avoid browser-specific assumptions like hover-led navigation or overly dense freeform layouts that do not translate well to Flutter widgets.
+4. **Write implementation cues, not Figma prose** — Specify scaffold usage, navigation model, card rhythm, token usage, and expected widget states.
+5. **Feed the result into `frontend-design-implementation-handoff` and `flutter-mobile-qa`** — Mobile design is not complete until implementation and QA can consume the same brief.
+
+## Output Format
+
+Deliver:
+
+1. Mobile-specific layout notes
+2. Navigation and CTA placement rules
+3. Widget/state expectations
+4. Flutter feasibility notes
+
+## Antigravity Platform Notes
+
+- Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
+- TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
+- Rules file relative to the mirrored skill directory: `../../rules/GEMINI.md`.
+- Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
+- Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
+- Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.
+- MCP skill tools (`skill_search`, `skill_get`, `skill_validate`, `skill_get_reference`) are available when Cubis Foundry MCP is configured.
+- User arguments are passed as natural language via `{{args}}` in TOML command prompts.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/frontend-design-screen-brief/SKILL.md

@@ -0,0 +1,44 @@
+---
+name: frontend-design-screen-brief
+description: Turn canonical design state plus overlays into a compact, high-signal screen brief for Stitch, frontend implementation, or Flutter/mobile work.
+---
+# Frontend Design Screen Brief
+
+## Purpose
+
+Produce the compact screen-level brief that downstream tools or engineers can execute without losing the product's visual and interaction intent.
+
+## When to Use
+
+- Preparing a Stitch generation or edit prompt
+- Creating a Flutter/mobile screen implementation brief
+- Turning a broad design system into a concrete page or flow
+
+## Instructions
+
+1. **Resolve the design state first** — Read `docs/foundation/DESIGN.md` and any relevant overlay before writing the brief.
+2. **Describe behavior, not just appearance** — Include hierarchy, interaction states, content priority, empty states, and success/failure feedback.
+3. **Keep the prompt compact** — The screen brief should be concise enough for a remote service like Stitch and concrete enough for a human implementer.
+4. **Choose platform-specific emphasis** — For Flutter/mobile, emphasize thumb reach, section staging, safe areas, and navigation patterns. For web, emphasize layout elasticity and information density.
+5. **Write acceptance constraints** — Explicitly state what must be preserved and what generic shortcuts are not acceptable.
+
+## Output Format
+
+Deliver:
+
+1. Screen goal
+2. Hierarchy and layout summary
+3. Token and component cues
+4. Interaction/motion notes
+5. Anti-slop constraints
+
+## Antigravity Platform Notes
+
+- Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
+- TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
+- Rules file relative to the mirrored skill directory: `../../rules/GEMINI.md`.
+- Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
+- Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
+- Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.
+- MCP skill tools (`skill_search`, `skill_get`, `skill_validate`, `skill_get_reference`) are available when Cubis Foundry MCP is configured.
+- User arguments are passed as natural language via `{{args}}` in TOML command prompts.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/frontend-design-style-selector/SKILL.md

@@ -0,0 +1,43 @@
+---
+name: frontend-design-style-selector
+description: Select a non-generic visual direction from Foundry's normalized design datasets and align it to the product's domain, audience, and platform.
+---
+# Frontend Design Style Selector
+
+## Purpose
+
+Choose the visual direction before any screen or component work starts so the result has a deliberate point of view instead of a generic app-template look.
+
+## When to Use
+
+- Starting a new design system or screen family
+- Improving a weak or generic UI prompt before Stitch generation
+- Choosing a consistent mood for a Flutter/mobile app
+
+## Instructions
+
+1. **Use only Foundry datasets** — Load `workflows/design-datasets/style-directions.json`, `layout-patterns.json`, and `component-motifs.json` first.
+2. **Select one primary direction and one supporting motif** — Avoid mixing many vibes. State the lead direction, supporting motif, and what should be excluded.
+3. **Tie the direction to the product domain** — State why the chosen direction fits the product audience, task density, and emotional tone.
+4. **Write anti-slop constraints** — Explicitly call out the visual clichés to avoid, such as generic wellness gradients, default dashboard cards, or unstructured glassmorphism.
+5. **Feed the result into `frontend-design-system` or `frontend-design-screen-brief`** — This skill chooses direction; it does not finish the design state by itself.
+
+## Output Format
+
+Deliver:
+
+1. Primary style direction
+2. Supporting motif
+3. Excluded clichés
+4. Typography, palette, shape, and motion intent summary
+
+## Antigravity Platform Notes
+
+- Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
+- TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
+- Rules file relative to the mirrored skill directory: `../../rules/GEMINI.md`.
+- Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
+- Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
+- Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.
+- MCP skill tools (`skill_search`, `skill_get`, `skill_validate`, `skill_get_reference`) are available when Cubis Foundry MCP is configured.
+- User arguments are passed as natural language via `{{args}}` in TOML command prompts.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/frontend-design-system/SKILL.md

@@ -0,0 +1,45 @@
+---
+name: frontend-design-system
+description: Build or refresh the canonical design-system state for a repo, including DESIGN.md, overlays, token language, and platform-specific adaptation notes.
+---
+# Frontend Design System
+
+## Purpose
+
+Author and refresh the project's canonical design-system state so design, Stitch generation, and implementation share the same visual language.
+
+## When to Use
+
+- `docs/foundation/DESIGN.md` is missing or stale
+- A new design direction needs to be made durable
+- Multi-screen work needs consistent tokens and component vocabulary
+- A Flutter/mobile app needs a stable design foundation before implementation
+
+## Instructions
+
+1. **Create or refresh `docs/foundation/DESIGN.md`** — This file is the source of truth for visual direction, token language, component vocabulary, and motion rules.
+2. **Write scoped overlays only when needed** — Use the page overlays directory under `docs/foundation/design/pages/`, the flow overlays directory under `docs/foundation/design/flows/`, or the mobile overlays directory under `docs/foundation/design/mobile/` when a narrower slice of the product needs additional detail.
+3. **Use semantic token naming** — Load `workflows/design-datasets/token-language.json` and preserve semantic roles instead of raw color dumps.
+4. **Preserve source metadata in the authoring process, not the final doc body** — The final design docs should be crisp and implementation-oriented, but the chosen direction should come from normalized datasets with source provenance.
+5. **Mirror to `.stitch/DESIGN.md` when Stitch flows are in scope** — The mirror should be generated from the canonical state and applicable overlays, never hand-maintained separately.
+
+## Output Format
+
+Deliver:
+
+1. Canonical design-system summary
+2. Token language
+3. Component vocabulary
+4. Overlay files created or refreshed
+5. Whether `.stitch/DESIGN.md` was updated
+
+## Antigravity Platform Notes
+
+- Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
+- TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
+- Rules file relative to the mirrored skill directory: `../../rules/GEMINI.md`.
+- Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
+- Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
+- Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.
+- MCP skill tools (`skill_search`, `skill_get`, `skill_validate`, `skill_get_reference`) are available when Cubis Foundry MCP is configured.
+- User arguments are passed as natural language via `{{args}}` in TOML command prompts.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/git-workflow/SKILL.md

@@ -63,7 +63,7 @@ When advising on git workflows, provide:
 
 - Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
 - TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
-- Rules file: `.agents/rules/GEMINI.md`.
+- Rules file relative to the mirrored skill directory: `../../rules/GEMINI.md`.
 - Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
 - Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
 - Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/golang-best-practices/SKILL.md

@@ -74,7 +74,7 @@ No helper scripts are required for this skill right now. Keep execution in `SKIL
 
 - Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
 - TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
-- Rules file: `.agents/rules/GEMINI.md`.
+- Rules file relative to the mirrored skill directory: `../../rules/GEMINI.md`.
 - Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
 - Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
 - Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/integration-testing/SKILL.md

@@ -100,7 +100,7 @@ Provide a structured methodology for writing integration tests that verify corre
 
 - Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
 - TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
-- Rules file: `.agents/rules/GEMINI.md`.
+- Rules file relative to the mirrored skill directory: `../../rules/GEMINI.md`.
 - Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
 - Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
 - Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/java-best-practices/SKILL.md

@@ -69,7 +69,7 @@ Produces Java code using records, sealed types, pattern matching switch expressi
 
 - Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
 - TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
-- Rules file: `.agents/rules/GEMINI.md`.
+- Rules file relative to the mirrored skill directory: `../../rules/GEMINI.md`.
 - Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
 - Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
 - Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/kaizen-iteration/SKILL.md

@@ -95,7 +95,7 @@ Provide a structured, metrics-driven framework for continuous improvement in sof
 
 - Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
 - TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
-- Rules file: `.agents/rules/GEMINI.md`.
+- Rules file relative to the mirrored skill directory: `../../rules/GEMINI.md`.
 - Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
 - Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
 - Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/kotlin-best-practices/SKILL.md

@@ -69,7 +69,7 @@ Produces Kotlin code using data classes, sealed hierarchies, structured coroutin
 
 - Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
 - TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
-- Rules file: `.agents/rules/GEMINI.md`.
+- Rules file relative to the mirrored skill directory: `../../rules/GEMINI.md`.
 - Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
 - Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
 - Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/kubernetes-deploy/SKILL.md

@@ -73,7 +73,7 @@ Provide complete Kubernetes manifests in YAML with inline comments explaining no
 
 - Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
 - TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
-- Rules file: `.agents/rules/GEMINI.md`.
+- Rules file relative to the mirrored skill directory: `../../rules/GEMINI.md`.
 - Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
 - Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
 - Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/mcp-server-builder/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: mcp-server-builder
-description: "Use when building MCP servers with spec-compliant tools, structured outputs, resource providers, transport configuration, and server testing."
+description: "Use when building MCP servers with spec-compliant tools, structured outputs, resource providers, transport configuration, and server testing. Anthropic compatibility aliases: mcp builder, mcp-builder."
 ---
 # MCP Server Builder
 
@@ -81,11 +81,16 @@ Guide the design and implementation of production-grade Model Context Protocol (
 - "Add a resource provider that serves database schema documentation to connected agents."
 - "Test an MCP server's tool registration and error handling with a mock client."
 
+## Compatibility Aliases
+
+Anthropic upstream compatibility names for this skill: `mcp builder`, `mcp-builder`.
+Treat requests that use those names as equivalent to this canonical Foundry skill.
+
 ## Antigravity Platform Notes
 
 - Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
 - TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
-- Rules file: `.agents/rules/GEMINI.md`.
+- Rules file relative to the mirrored skill directory: `../../rules/GEMINI.md`.
 - Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
 - Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
 - Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/nestjs/SKILL.md

@@ -69,7 +69,7 @@ Provide implementation code, module definitions, decorator usage, configuration
 
 - Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
 - TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
-- Rules file: `.agents/rules/GEMINI.md`.
+- Rules file relative to the mirrored skill directory: `../../rules/GEMINI.md`.
 - Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
 - Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
 - Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/nextjs/SKILL.md

@@ -82,7 +82,7 @@ Load detailed guidance based on context:
 
 - Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
 - TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
-- Rules file: `.agents/rules/GEMINI.md`.
+- Rules file relative to the mirrored skill directory: `../../rules/GEMINI.md`.
 - Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
 - Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
 - Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/observability/SKILL.md

@@ -73,7 +73,7 @@ Provide complete instrumentation code, configuration files, and alert rule defin
 
 - Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
 - TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
-- Rules file: `.agents/rules/GEMINI.md`.
+- Rules file relative to the mirrored skill directory: `../../rules/GEMINI.md`.
 - Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
 - Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
 - Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/owasp-security-review/SKILL.md

@@ -98,7 +98,7 @@ Perform structured, OWASP-standards-based security reviews of application code a
 
 - Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
 - TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
-- Rules file: `.agents/rules/GEMINI.md`.
+- Rules file relative to the mirrored skill directory: `../../rules/GEMINI.md`.
 - Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
 - Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
 - Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/pentest-skill/SKILL.md

@@ -99,7 +99,7 @@ Provide structured guidance for authorized penetration testing engagements follo
 
 - Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
 - TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
-- Rules file: `.agents/rules/GEMINI.md`.
+- Rules file relative to the mirrored skill directory: `../../rules/GEMINI.md`.
 - Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
 - Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
 - Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/playwright-interactive/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: playwright-interactive
-description: "Use when building interactive Playwright suites for browser automation, visual regression, accessibility audits, network interception, and collaborative test workflows."
+description: "Use when building interactive Playwright suites for browser automation, visual regression, accessibility audits, network interception, and collaborative test workflows. Anthropic compatibility aliases: webapp testing, webapp-testing."
 ---
 # Playwright Interactive
 
@@ -76,11 +76,16 @@ Deliver:
 | `agents/visual-reviewer.md` | Delegating screenshot comparison and visual regression tasks |
 | `agents/accessibility-auditor.md` | Delegating accessibility scans and report generation |
 
+## Compatibility Aliases
+
+Anthropic upstream compatibility names for this skill: `webapp testing`, `webapp-testing`.
+Treat requests that use those names as equivalent to this canonical Foundry skill.
+
 ## Antigravity Platform Notes
 
 - Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
 - TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
-- Rules file: `.agents/rules/GEMINI.md`.
+- Rules file relative to the mirrored skill directory: `../../rules/GEMINI.md`.
 - Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
 - Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
 - Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/playwright-web-qa/SKILL.md

@@ -0,0 +1,77 @@
+---
+name: playwright-web-qa
+description: "Use when running charter-driven web QA through Playwright MCP with deterministic evidence, runtime traces, and report-ready browser artifacts."
+---
+# Playwright Web QA
+
+## Purpose
+
+Provide a runtime-oriented browser QA workflow for validating real user journeys through Playwright MCP. This skill is for live charter execution and evidence review, not broad suite design.
+
+## When to Use
+
+- Running a manual or AI-authored QA charter against a real web app
+- Capturing screenshots, DOM state, console logs, network evidence, or accessibility evidence
+- Reproducing a bug with deterministic browser artifacts
+- Checking whether a page is blocked, broken, or visibly regressed before test-suite authoring
+
+## Instructions
+
+1. Confirm the Playwright MCP server is reachable before planning steps.
+2. Require a QA charter with `flow`, `success_criteria`, `base_url`, and `steps`.
+3. Start from an explicit URL state and avoid hidden navigation assumptions.
+4. Use Playwright MCP as the execution path instead of ad hoc browser scripts.
+5. Prefer stable selectors: role or test id first, then text, then CSS as a last resort.
+6. Capture baseline evidence before the first destructive action.
+7. Persist artifacts under `artifacts/web-qa/` with deterministic filenames.
+8. Capture console, network, or accessibility evidence only when the charter asks for it or when a failure needs explanation.
+9. Use one controlled retry only, then stop and report evidence.
+10. Tie the final verdict to artifact paths, not impressions.
+
+## Output Format
+
+```markdown
+## Web QA Charter
+- Flow:
+- Base URL:
+- Start path:
+- Success criteria:
+
+## Execution Log
+1. [action] -> [observation]
+2. [action] -> [observation]
+
+## Assertions
+- Passed:
+- Failed:
+- Blocked:
+
+## Evidence
+- Screenshots:
+- DOM snapshots:
+- Console logs:
+- Network evidence:
+- Accessibility evidence:
+
+## Risks And Follow-ups
+- Risk:
+- Recommended fix:
+```
+
+## References
+
+| File | Load when |
+| --- | --- |
+| `../playwright-interactive/SKILL.md` | The task shifts from runtime QA into suite authoring or broader E2E architecture. |
+| `../flutter-mobile-qa/SKILL.md` | The task also includes Android/mobile QA and needs the parallel mobile runtime pattern. |
+
+## Antigravity Platform Notes
+
+- Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
+- TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
+- Rules file relative to the mirrored skill directory: `../../rules/GEMINI.md`.
+- Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
+- Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
+- Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.
+- MCP skill tools (`skill_search`, `skill_get`, `skill_validate`, `skill_get_reference`) are available when Cubis Foundry MCP is configured.
+- User arguments are passed as natural language via `{{args}}` in TOML command prompts.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/prisma/SKILL.md

@@ -72,7 +72,7 @@ Load only what the current task requires.
 
 - Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
 - TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
-- Rules file: `.agents/rules/GEMINI.md`.
+- Rules file relative to the mirrored skill directory: `../../rules/GEMINI.md`.
 - Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
 - Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
 - Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/prompt-engineering/SKILL.md

@@ -75,7 +75,7 @@ Provide system prompts as formatted text blocks with labeled sections, few-shot
 
 - Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
 - TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
-- Rules file: `.agents/rules/GEMINI.md`.
+- Rules file relative to the mirrored skill directory: `../../rules/GEMINI.md`.
 - Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
 - Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
 - Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/python-best-practices/SKILL.md

@@ -78,7 +78,7 @@ No helper scripts are required for this skill right now. Keep execution in `SKIL
 
 - Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
 - TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
-- Rules file: `.agents/rules/GEMINI.md`.
+- Rules file relative to the mirrored skill directory: `../../rules/GEMINI.md`.
 - Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
 - Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
 - Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/react/SKILL.md

@@ -82,7 +82,7 @@ Load detailed guidance based on context:
 
 - Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
 - TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
-- Rules file: `.agents/rules/GEMINI.md`.
+- Rules file relative to the mirrored skill directory: `../../rules/GEMINI.md`.
 - Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
 - Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
 - Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/rust-best-practices/SKILL.md

@@ -78,7 +78,7 @@ No helper scripts are required for this skill right now. Keep execution in `SKIL
 
 - Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
 - TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
-- Rules file: `.agents/rules/GEMINI.md`.
+- Rules file relative to the mirrored skill directory: `../../rules/GEMINI.md`.
 - Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
 - Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
 - Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/secret-management/SKILL.md

@@ -94,7 +94,7 @@ Guide the design and implementation of robust secret and credential management s
 
 - Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
 - TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
-- Rules file: `.agents/rules/GEMINI.md`.
+- Rules file relative to the mirrored skill directory: `../../rules/GEMINI.md`.
 - Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
 - Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
 - Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/skill-creator/SKILL.md

@@ -157,7 +157,7 @@ skill-creator
 
 - Skills are stored under `.agents/skills/<skill-id>/SKILL.md` (shared Agent Skills standard path).
 - TOML command files in `.gemini/commands/` provide slash-command entry points for workflows and agent routes.
-- Rules file: `.agents/rules/GEMINI.md`.
+- Rules file relative to the mirrored skill directory: `../../rules/GEMINI.md`.
 - Use Agent Manager for parallel agent coordination and multi-specialist delegation (equivalent to `@orchestrator`).
 - Specialist routes are compiled into `.gemini/commands/agent-*.toml` command files — not project-local agent markdown.
 - Reference files are loaded relative to the skill directory under `.agents/skills/<skill-id>/`.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/skills/skill-creator/references/platform-adaptations.md

@@ -105,16 +105,30 @@ allowed-tools: [Read, Edit, Write, Bash, Grep, Glob]
 ## Adaptation Strategy
 
 ### Canonical Version (workflows/skills/)
-The canonical skill in `workflows/skills/<name>/` uses the full Pro Skill Standard format with rich frontmatter. This is the source of truth.
+The canonical skill in `workflows/skills/<name>/` is the authoring source of truth.
 
-### Claude Code Mirror
-Placed at `platforms/claude/skills/<name>/SKILL.md`. Uses full Claude frontmatter. Instructions may reference `context:fork`, `$ARGUMENTS`, and `${CLAUDE_SKILL_DIR}`.
+### Generated Platform Mirrors
+Generated mirrors are maintained for Claude Code, Copilot, Codex, Gemini CLI, and Antigravity under `platforms/<platform>/skills/<name>/SKILL.md`.
 
-### Copilot Mirror
-Placed at `platforms/copilot/skills/<name>/SKILL.md`. Same as Claude (Copilot reads Claude format). May add notes about prompt files and path-scoped instructions.
+- Claude Code mirrors can use Claude-specific frontmatter and instruction references such as `context: fork`, `$ARGUMENTS`, and `${CLAUDE_SKILL_DIR}`.
+- Copilot mirrors stay Claude-compatible where useful, but Copilot-native behavior still follows Copilot's own constraints.
+- Codex, Gemini CLI, and Antigravity mirrors usually keep minimal frontmatter and rely on platform rules plus MCP/routing behavior for the rest.
+- Do not assume one mirror transform works for every asset type. Skills, custom agents, workflow projections, prompts, and command files each have different platform constraints and must be generated through their own platform-aware pipeline.
 
-### Codex, Gemini CLI, Antigravity
-These platforms use the canonical version directly, referenced by their respective rule files. No separate mirror needed — the rule files handle routing.
+### Shared Steering + Platform Overrides
+Routing and loading behavior should not be documented independently in every platform skill.
+
+- `shared/rules/STEERING.md` is the canonical routing and skill-loading source.
+- `shared/rules/overrides/<platform>.md` adds platform-specific behavior.
+- Generated platform rule files are composed from the shared steering file plus the relevant platform override.
+
+### Non-Skill Assets
+Custom agents and workflow projections are not mirrored with the same logic as skills.
+
+- Skills are mirrored with platform-specific frontmatter and body transforms.
+- Shared agents are compiled into platform-native outputs such as Claude/Copilot markdown agents or Codex TOML agents.
+- Workflows are compiled into platform-native workflow skills, command files, or prompt files depending on the target platform.
+- Regenerate these with the platform asset generator, not by copying skill directories.
 
 ## Instruction Adaptation
 
@@ -124,5 +138,5 @@ When the canonical instructions reference platform-specific features, adapt them
 |-----------|------------|-------|--------|-------------|---------|
 | "fork to subagent" | `context: fork` | "switch posture" | "activate agent" | "use workflow" | `context: fork` |
 | "load reference" | `skill_get_reference` | "read file" | `activate_skill` | "read file" | `skill_get_reference` |
-| "use MCP tool" | `skill_validate` | N/A | `activate_skill` | N/A | N/A |
+| "use MCP tool" | `skill_validate` / `skill_get` | `skill_validate` / `skill_get` when MCP is connected | `skill_validate` / `skill_get` when MCP is connected; `activate_skill` only when using Gemini-native skill loading | `skill_validate` / `skill_get` when MCP is configured | `skill_validate` / `skill_get` when MCP is configured |
 | "run script" | `Bash` | `Bash` (may be sandboxed) | Shell | Shell | `Bash` |