@cubis/foundry 0.3.10

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/copilot/workflows/backend.md

@@ -0,0 +1,25 @@
+---
+command: "/backend"
+description: "Drive backend architecture and implementation via backend specialist with API, data, and reliability focus."
+triggers: ["backend", "api", "service", "database", "performance"]
+---
+# Backend Workflow
+
+Use this when backend architecture or service logic is primary.
+
+## Routing
+- Primary specialist: `@backend-specialist`
+- Add `@database-architect` for schema/query changes.
+- Add `@security-auditor` when auth, secrets, or sensitive data are involved.
+
+## Steps
+1. Ask specialist(s) for design and risk assessment.
+2. Validate contracts, data model, and failure handling.
+3. Implement backend changes with observability.
+4. Run targeted tests and summarize rollout notes.
+
+## Output Contract
+- API/contract changes
+- Migration impact
+- Reliability/security notes
+- Verification evidence

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/copilot/workflows/brainstorm.md

@@ -0,0 +1,20 @@
+---
+command: "/brainstorm"
+description: "Generate concrete solution options and tradeoffs before committing to implementation."
+triggers: ["idea", "brainstorm", "options", "tradeoff", "approach"]
+---
+# Brainstorm Workflow
+
+Use this when requirements are still fluid and architecture choices are open.
+
+## Steps
+1. Restate problem, constraints, and success metrics.
+2. Produce 2-4 options with architecture shape.
+3. Compare complexity, risk, and implementation speed.
+4. Recommend one option and justify rejection of others.
+
+## Output Contract
+- Option table (pros/cons)
+- Recommended option
+- Known unknowns
+- First implementation milestone

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/copilot/workflows/create.md

@@ -0,0 +1,20 @@
+---
+command: "/create"
+description: "Implement feature work with minimal blast radius and clear verification checkpoints."
+triggers: ["create", "build", "implement", "feature", "develop"]
+---
+# Create Workflow
+
+Use this for net-new implementation after design is stable.
+
+## Steps
+1. Confirm target files and contracts.
+2. Implement smallest coherent increment.
+3. Validate behavior with focused tests.
+4. Capture remaining gaps and follow-ups.
+
+## Output Contract
+- Changed components/files
+- Behavioral impact
+- Test evidence
+- Follow-up items

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/copilot/workflows/database.md

@@ -0,0 +1,26 @@
+---
+command: "/database"
+description: "Design or review schema, queries, and migrations with performance and integrity controls."
+triggers: ["database", "sql", "schema", "migration", "index"]
+---
+# Database Workflow
+
+Use this when data modeling, query quality, or migration safety is core to the task.
+
+## Routing
+- Primary specialist: `@database-architect`
+- Backend integration: `@backend-specialist`
+- Verification support: `@test-engineer`
+- Core skill package: `database-skills`
+
+## Steps
+1. Confirm data shape and access patterns.
+2. Design schema/index strategy.
+3. Plan migration with rollback.
+4. Validate performance and integrity impacts.
+
+## Output Contract
+- Schema/query changes
+- Migration + rollback plan
+- Performance expectations
+- Validation evidence

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/copilot/workflows/debug.md

@@ -0,0 +1,20 @@
+---
+command: "/debug"
+description: "Isolate root cause quickly and apply the smallest safe remediation with verification."
+triggers: ["debug", "bug", "error", "incident", "stack trace"]
+---
+# Debug Workflow
+
+Use this when behavior is failing or inconsistent.
+
+## Steps
+1. Reproduce issue and collect evidence.
+2. Narrow fault domain and identify root cause.
+3. Apply focused fix with low regression risk.
+4. Verify resolution and monitor for recurrence.
+
+## Output Contract
+- Reproduction notes
+- Root cause summary
+- Fix summary
+- Regression checks performed

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/copilot/workflows/devops.md

@@ -0,0 +1,25 @@
+---
+command: "/devops"
+description: "Plan and execute deployment, CI/CD, and operational safety changes with rollback controls."
+triggers: ["devops", "deploy", "ci", "cd", "rollback", "infra"]
+---
+# DevOps Workflow
+
+Use this when deployment pipeline, infrastructure, or release execution is the main scope.
+
+## Routing
+- Primary specialist: `@devops-engineer`
+- Security checks: `@security-auditor`
+- Verification support: `@test-engineer`
+
+## Steps
+1. Confirm target environment and risk level.
+2. Define rollout and rollback strategy.
+3. Apply CI/CD or infra changes.
+4. Validate monitors/alerts and recovery path.
+
+## Output Contract
+- Deployment plan
+- Rollback conditions
+- Validation and observability checks
+- Outstanding operational risks

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/copilot/workflows/implement-track.md

@@ -0,0 +1,21 @@
+---
+command: "/implement-track"
+description: "Execute large work in milestones with explicit quality gates and status updates."
+triggers: ["track", "milestone", "delivery", "progress", "execution"]
+---
+# Implement Track Workflow
+
+Use this for medium/large efforts where progress visibility is required.
+
+## Steps
+1. Split into milestone-sized deliverables.
+2. Define done criteria per milestone.
+3. Execute one milestone at a time.
+4. Validate before moving forward.
+5. Publish progress and remaining risks.
+
+## Output Contract
+- Milestone board (done/in-progress/next)
+- Gate status
+- Blockers and dependencies
+- ETA confidence

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/copilot/workflows/incident.md

@@ -0,0 +1,28 @@
+---
+command: "/incident"
+description: "Handle production incidents with triage, mitigation, root cause, and post-incident actions."
+triggers: ["incident", "outage", "sev", "degraded", "hotfix"]
+---
+# Incident Workflow
+
+Use this for active or recent production incidents.
+
+## Routing
+- Runtime/service issues: `@backend-specialist` + `@debugger`
+- Data inconsistencies: `@database-architect`
+- Security events: `@security-auditor`
+- Recovery validation: `@test-engineer`
+- Deployment rollback execution: `@devops-engineer`
+
+## Steps
+1. Establish impact, severity, and current status.
+2. Mitigate first, then stabilize.
+3. Identify probable root cause and confirm.
+4. Implement and verify durable fix.
+5. Document post-incident follow-up actions.
+
+## Output Contract
+- Incident timeline
+- Mitigation actions
+- Root cause statement
+- Follow-up prevention tasks

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/copilot/workflows/mobile.md

@@ -0,0 +1,25 @@
+---
+command: "/mobile"
+description: "Drive mobile implementation decisions for Flutter/cross-platform behavior and reliability."
+triggers: ["mobile", "flutter", "ios", "android", "navigation"]
+---
+# Mobile Workflow
+
+Use this when mobile app architecture, UX behavior, or platform constraints are the focus.
+
+## Routing
+- Primary specialist: `@mobile-developer`
+- UI support: `@frontend-specialist`
+- Verification support: `@test-engineer`
+
+## Steps
+1. Confirm platform and UX constraints.
+2. Plan navigation/state/offline behavior.
+3. Implement or refactor mobile flows.
+4. Validate behavior across critical paths.
+
+## Output Contract
+- Mobile flow changes
+- Platform constraints handled
+- Test coverage summary
+- Release-readiness notes

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/copilot/workflows/orchestrate.md

@@ -0,0 +1,31 @@
+---
+command: "/orchestrate"
+description: "Coordinate multiple specialists to solve cross-cutting tasks with explicit ownership and handoff."
+triggers: ["orchestrate", "coordinate", "multi-area", "cross-team", "handoff"]
+---
+# Orchestrate Workflow
+
+Use this when a task spans backend, frontend, data, testing, and release concerns.
+
+## Routing
+- Primary coordinator: `@orchestrator`
+- Architecture decisions: `@backend-specialist`
+- Data model/query risk: `@database-architect`
+- UX/client behavior: `@frontend-specialist`
+- Security review: `@security-auditor`
+- Verification strategy: `@test-engineer`
+- Rollout plan: `@devops-engineer`
+
+## Protocol
+1. Break the request into workstreams with owners.
+2. Request one primary specialist output per workstream.
+3. Merge outputs into a single implementation plan.
+4. Resolve conflicts before implementation.
+5. End with a release-risk summary.
+
+## Output Contract
+- Scope and assumptions
+- Workstreams with owner + deliverable
+- Consolidated execution order
+- Test and rollout gates
+- Open risks and mitigations

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/copilot/workflows/plan.md

@@ -0,0 +1,21 @@
+---
+command: "/plan"
+description: "Build a decision-complete implementation plan with interfaces, failure modes, and acceptance criteria."
+triggers: ["plan", "spec", "design", "roadmap", "acceptance"]
+---
+# Plan Workflow
+
+Use this when execution needs a stable specification.
+
+## Steps
+1. Lock scope and non-goals.
+2. Define architecture, boundaries, and data flow.
+3. Specify interfaces and validation rules.
+4. Document failure modes and mitigations.
+5. Define tests and release acceptance criteria.
+
+## Output Contract
+- Implementation phases
+- API/data/interface details
+- Edge cases and risk matrix
+- Verification and rollout checklist

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/copilot/workflows/qa.md

@@ -0,0 +1,25 @@
+---
+command: "/qa"
+description: "Create and execute quality strategy with automation and regression-focused coverage."
+triggers: ["qa", "test", "regression", "automation", "e2e"]
+---
+# QA Workflow
+
+Use this when verification quality and regression prevention are primary concerns.
+
+## Routing
+- Primary specialist: `@qa-automation-engineer`
+- Test strategy support: `@test-engineer`
+- Bug investigation support: `@debugger`
+
+## Steps
+1. Identify risk-heavy user journeys.
+2. Define automation + manual checks where needed.
+3. Execute validation and triage failures.
+4. Report confidence level and remaining gaps.
+
+## Output Contract
+- Test strategy and scope
+- Automation coverage updates
+- Defect findings and severity
+- Confidence and residual risk

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/copilot/workflows/refactor.md

@@ -0,0 +1,20 @@
+---
+command: "/refactor"
+description: "Improve maintainability while preserving behavior through incremental safe refactoring."
+triggers: ["refactor", "cleanup", "maintainability", "debt", "modularize"]
+---
+# Refactor Workflow
+
+Use this for design improvement without intentional behavior changes.
+
+## Steps
+1. Define behavior invariants and guardrails.
+2. Isolate refactor slices with low coupling.
+3. Apply changes incrementally with tests.
+4. Confirm behavior parity and performance baseline.
+
+## Output Contract
+- Refactor scope and invariants
+- Structural changes
+- Behavior parity evidence
+- Deferred technical debt items

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/copilot/workflows/release.md

@@ -0,0 +1,26 @@
+---
+command: "/release"
+description: "Prepare and execute release with rollout guardrails, verification, and rollback plan."
+triggers: ["release", "deploy", "rollout", "ship", "go-live"]
+---
+# Release Workflow
+
+Use this before deployment to production-like environments.
+
+## Routing
+- Release orchestration: `@devops-engineer`
+- Risk checks: `@security-auditor` + `@test-engineer`
+- Scope/fallback alignment: `@product-owner`
+
+## Steps
+1. Confirm release scope and dependencies.
+2. Validate test evidence and readiness gates.
+3. Define rollout strategy and rollback triggers.
+4. Execute release and monitor signals.
+5. Publish release summary and next actions.
+
+## Output Contract
+- Release checklist status
+- Rollout strategy
+- Rollback conditions
+- Post-release monitoring plan

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/copilot/workflows/review.md

@@ -0,0 +1,26 @@
+---
+command: "/review"
+description: "Run a strict review for bugs, regressions, and security issues with prioritized findings."
+triggers: ["review", "audit", "pr", "quality", "security review"]
+---
+# Review Workflow
+
+Use this for pull request or branch quality review.
+
+## Routing
+- Code quality and legacy risk: `@code-archaeologist`
+- Frontend quality: `@frontend-specialist`
+- Security checks: `@security-auditor`
+- Test adequacy: `@test-engineer`
+
+## Steps
+1. Inspect changed behavior and risk surface.
+2. Identify defects by severity.
+3. Validate tests and missing coverage.
+4. Produce actionable remediation guidance.
+
+## Output Contract
+- Findings ordered by severity
+- Affected files/areas
+- Recommended fixes
+- Residual risks after fixes

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/copilot/workflows/security.md

@@ -0,0 +1,25 @@
+---
+command: "/security"
+description: "Run security-focused analysis and remediation planning with exploitability-first triage."
+triggers: ["security", "vulnerability", "owasp", "auth", "hardening"]
+---
+# Security Workflow
+
+Use this when the task is primarily about security risk discovery, triage, or remediation.
+
+## Routing
+- Primary specialist: `@security-auditor`
+- Exploitability validation: `@penetration-tester`
+- Verification support: `@test-engineer`
+
+## Steps
+1. Map threat surface and high-risk paths.
+2. Prioritize findings by exploitability and impact.
+3. Propose concrete fixes with least regression risk.
+4. Validate remediation and residual risk.
+
+## Output Contract
+- Findings by severity
+- Fix plan with owners
+- Verification evidence
+- Residual risk notes

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/copilot/workflows/test.md

@@ -0,0 +1,20 @@
+---
+command: "/test"
+description: "Design and execute verification strategy aligned to risk and acceptance criteria."
+triggers: ["test", "verify", "coverage", "qa", "regression"]
+---
+# Test Workflow
+
+Use this to drive confidence before merge or release.
+
+## Steps
+1. Map change surface to risk areas.
+2. Choose unit/integration/e2e depth per risk.
+3. Run fast checks first, then broad suite.
+4. Report failures with root-cause direction.
+
+## Output Contract
+- Coverage map (what was tested)
+- Test results summary
+- Remaining risk and gaps
+- Merge/release recommendation

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/copilot/workflows/vercel.md

@@ -0,0 +1,26 @@
+---
+command: "/vercel"
+description: "Drive Vercel implementation and operations via vercel-expert with deployment, runtime, security, and observability guardrails."
+triggers: ["vercel", "deployment", "preview", "edge", "functions", "domains", "vercel cli"]
+---
+# Vercel Workflow
+
+Use this workflow when the primary concern is Vercel platform behavior, deployment safety, or Vercel-specific automation.
+
+## Routing
+- Primary specialist: `@vercel-expert`
+- Add `@devops-engineer` for CI/CD and rollout policy design.
+- Add `@security-auditor` for WAF, auth, and network-hardening decisions.
+- Add `@test-engineer` or `@qa-automation-engineer` for release quality gates.
+
+## Steps
+1. Confirm environment targets, success criteria, and rollback constraints.
+2. Design the smallest Vercel-specific change that solves the issue.
+3. Implement and verify using focused checks with logs/traces evidence.
+4. Summarize risk, residual gaps, and next operational actions.
+
+## Output Contract
+- Config/code changes and affected Vercel components
+- Deployment and rollback notes
+- Security and observability impact
+- Verification evidence and follow-up items

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/cursor/rules/.cursorrules

@@ -0,0 +1,41 @@
+# .cursorrules - Cubis Foundry Cursor Protocol
+
+This file defines mandatory behavior for Cursor projects installed via `cbx workflows`.
+
+## 1) Platform Paths
+
+- Workflows: `.cursor/workflows`
+- Agents: `.cursor/agents`
+- Skills: `.cursor/skills`
+- Rules file: `.cursorrules`
+
+## 2) Smart Skill Selection (TIER 0)
+
+Before starting ANY task, the agent MUST:
+1.  **Analyze** the user's request against the keywords in `.cursor/skills/skills_index.json`.
+2.  **Select** the most relevant skill(s) if a strong match is found.
+3.  **Load** the selected skill's `SKILL.md` using `view_file` **BEFORE** proceeding.
+4.  **Announce** the selection: "I am loading the `[Skill Name]` skill to handle your request."
+
+## 3) Skill Loading Policy
+
+1.  Load only skills needed for the active request.
+2.  Prefer progressive disclosure: start from `SKILL.md`, then specific sections.
+3.  Keep context lean; avoid loading unrelated skill documents.
+4.  If a mapped skill is missing, continue with best fallback and state it.
+
+## 4) Agent Routing Policy
+
+Use the best specialist first:
+- Backend/API/database: `@backend-specialist`, `@database-architect`
+- Frontend/UI: `@frontend-specialist`
+- Mobile: `@mobile-developer`
+- Security: `@security-auditor`, `@penetration-tester`
+- DevOps/release: `@devops-engineer`
+- Testing/QA: `@test-engineer`, `@qa-automation-engineer`
+
+## 5) Quality and Safety Gates
+
+1.  Do not run destructive actions without explicit user confirmation.
+2.  Keep diffs small and reversible when possible.
+3.  Verify behavior with focused checks before finalizing.

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/cursor/skills/accessibility/POWER.md

@@ -0,0 +1,103 @@
+---
+name: "accessibility"
+displayName: "Accessibility Expert"
+description: "Ensure Flutter apps meet WCAG 2.1 AA standards with proper semantics, focus management, and screen reader support"
+keywords:
+  [
+    "accessibility",
+    "a11y",
+    "wcag",
+    "semantics",
+    "screen reader",
+    "focus",
+    "contrast",
+    "flutter accessibility",
+  ]
+---
+
+# Accessibility Expert
+
+## Overview
+
+This power helps you build accessible Flutter widgets that work well with screen readers (TalkBack/VoiceOver), keyboard navigation, and meet WCAG 2.1 AA standards.
+
+## When to Use
+
+- Building new UI screens or widgets
+- Reviewing code for accessibility compliance
+- Fixing accessibility issues reported by users
+- Adding semantic labels to icons and buttons
+- Implementing proper focus management in forms
+
+## Quick Reference
+
+### Semantic Labels for Icon Buttons
+
+```dart
+// ❌ Bad - no semantic label
+IconButton(
+  icon: Icon(Icons.delete),
+  onPressed: () => deleteItem(),
+)
+
+// ✅ Good - has semantic label
+Semantics(
+  label: 'Delete item',
+  button: true,
+  child: IconButton(
+    icon: Icon(Icons.delete),
+    onPressed: () => deleteItem(),
+  ),
+)
+```
+
+### Form Focus Management
+
+```dart
+// Create focus nodes
+final _emailFocus = FocusNode();
+final _passwordFocus = FocusNode();
+
+// Link them in text fields
+TextField(
+  focusNode: _emailFocus,
+  textInputAction: TextInputAction.next,
+  onSubmitted: (_) => _passwordFocus.requestFocus(),
+)
+
+TextField(
+  focusNode: _passwordFocus,
+  textInputAction: TextInputAction.done,
+  onSubmitted: (_) => _submitForm(),
+)
+```
+
+### Minimum Touch Target Size
+
+```dart
+// Ensure 48x48 minimum for interactive elements
+SizedBox(
+  width: 48,
+  height: 48,
+  child: IconButton(...),
+)
+```
+
+## Key Principles
+
+1. **Semantic Labels**: All icon buttons, images, and non-text elements need labels
+2. **Focus Order**: Tab order should follow visual/logical flow
+3. **Touch Targets**: Minimum 48x48 dp for all interactive elements
+4. **Color Contrast**: Text must have 4.5:1 contrast ratio (3:1 for large text)
+5. **Screen Reader**: Test with TalkBack (Android) and VoiceOver (iOS)
+
+## Steering Files
+
+Load detailed guidance:
+- `a11y_checklist.md` - Complete accessibility checklist for reviews
+
+## Templates
+
+- `focus_form` - Form with proper focus management
+- `semantics_icon_button` - Icon button with semantic labels
+