@cubis/foundry 0.3.30 → 0.3.32

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

@@ -1,29 +0,0 @@
----
-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. Always update API docs: OpenAPI spec, Swagger UI route, and Stoplight Elements route/component.
-5. Run targeted tests and summarize rollout notes.
-
-## Output Contract
-- API/contract changes
-- OpenAPI spec path
-- Swagger UI route
-- Stoplight route/component status
-- Migration impact
-- Reliability/security notes
-- Verification evidence

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

@@ -1,20 +0,0 @@
----
-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

@@ -1,20 +0,0 @@
----
-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

@@ -1,34 +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
-
-Use this when data modeling, query quality, migration safety, or database performance is core to the task.
-
-## Routing
-- Primary specialist: `@database-architect`
-- Backend integration: `@backend-specialist`
-- Verification support: `@test-engineer`
-- Core skill hub: `database-skills`
-- Companion skills: `database-design` (schema/migrations), `database-optimizer` (tuning/triage)
-- Mobile/local persistence companion: `drift-flutter`
-- Power bridge: `Ai Agent Workflow/powers/database-skills`
-- Engine wrappers: `postgres`, `mysql`, `vitess`, `neki`, `mongodb`, `sqlite`, `supabase`, `redis`
-
-## Steps
-1. Confirm data shape, access patterns, and workload size.
-2. Choose track: `database-design` (schema/migrations), `database-optimizer` (tuning), or `database-skills` (engine wrappers).
-3. Choose engine wrapper and define index strategy.
-4. Define pagination strategy (keyset first, offset only if justified).
-5. Plan migration and rollback.
-6. Validate with query-plan evidence and production-risk notes.
-
-## Output Contract
-- Schema/query changes
-- Indexing plan
-- Pagination plan
-- Migration + rollback plan
-- Query-plan evidence (`EXPLAIN` or equivalent)
-- Validation evidence

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

@@ -1,20 +0,0 @@
----
-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

@@ -1,25 +0,0 @@
----
-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

@@ -1,21 +0,0 @@
----
-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

@@ -1,28 +0,0 @@
----
-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

@@ -1,25 +0,0 @@
----
-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

@@ -1,31 +0,0 @@
----
-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

@@ -1,21 +0,0 @@
----
-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

@@ -1,25 +0,0 @@
----
-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

@@ -1,20 +0,0 @@
----
-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

@@ -1,26 +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
-
-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

@@ -1,26 +0,0 @@
----
-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

@@ -1,25 +0,0 @@
----
-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

@@ -1,20 +0,0 @@
----
-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

@@ -1,26 +0,0 @@
----
-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/skills/architecture/SKILL.md

@@ -1,55 +0,0 @@
----
-name: architecture
-description: Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.
-allowed-tools: Read, Glob, Grep
----
-
-# Architecture Decision Framework
-
-> "Requirements drive architecture. Trade-offs inform decisions. ADRs capture rationale."
-
-## 🎯 Selective Reading Rule
-
-**Read ONLY files relevant to the request!** Check the content map, find what you need.
-
-| File | Description | When to Read |
-|------|-------------|--------------|
-| `context-discovery.md` | Questions to ask, project classification | Starting architecture design |
-| `trade-off-analysis.md` | ADR templates, trade-off framework | Documenting decisions |
-| `pattern-selection.md` | Decision trees, anti-patterns | Choosing patterns |
-| `examples.md` | MVP, SaaS, Enterprise examples | Reference implementations |
-| `patterns-reference.md` | Quick lookup for patterns | Pattern comparison |
-
----
-
-## 🔗 Related Skills
-
-| Skill | Use For |
-|-------|---------|
-| `@[skills/database-design]` | Database schema design |
-| `@[skills/api-patterns]` | API design patterns |
-| `@[skills/deployment-procedures]` | Deployment architecture |
-
----
-
-## Core Principle
-
-**"Simplicity is the ultimate sophistication."**
-
-- Start simple
-- Add complexity ONLY when proven necessary
-- You can always add patterns later
-- Removing complexity is MUCH harder than adding it
-
----
-
-## Validation Checklist
-
-Before finalizing architecture:
-
-- [ ] Requirements clearly understood
-- [ ] Constraints identified
-- [ ] Each decision has trade-off analysis
-- [ ] Simpler alternatives considered
-- [ ] ADRs written for significant decisions
-- [ ] Team expertise matches chosen patterns

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/cursor/skills/code-review-checklist/SKILL.md

@@ -1,109 +0,0 @@
----
-name: code-review-checklist
-description: Code review guidelines covering code quality, security, and best practices.
-allowed-tools: Read, Glob, Grep
----
-
-# Code Review Checklist
-
-## Quick Review Checklist
-
-### Correctness
-- [ ] Code does what it's supposed to do
-- [ ] Edge cases handled
-- [ ] Error handling in place
-- [ ] No obvious bugs
-
-### Security
-- [ ] Input validated and sanitized
-- [ ] No SQL/NoSQL injection vulnerabilities
-- [ ] No XSS or CSRF vulnerabilities
-- [ ] No hardcoded secrets or sensitive credentials
-- [ ] **AI-Specific:** Protection against Prompt Injection (if applicable)
-- [ ] **AI-Specific:** Outputs are sanitized before being used in critical sinks
-
-### Performance
-- [ ] No N+1 queries
-- [ ] No unnecessary loops
-- [ ] Appropriate caching
-- [ ] Bundle size impact considered
-
-### Code Quality
-- [ ] Clear naming
-- [ ] DRY - no duplicate code
-- [ ] SOLID principles followed
-- [ ] Appropriate abstraction level
-
-### Testing
-- [ ] Unit tests for new code
-- [ ] Edge cases tested
-- [ ] Tests readable and maintainable
-
-### Documentation
-- [ ] Complex logic commented
-- [ ] Public APIs documented
-- [ ] README updated if needed
-
-## AI & LLM Review Patterns (2025)
-
-### Logic & Hallucinations
-- [ ] **Chain of Thought:** Does the logic follow a verifiable path?
-- [ ] **Edge Cases:** Did the AI account for empty states, timeouts, and partial failures?
-- [ ] **External State:** Is the code making safe assumptions about file systems or networks?
-
-### Prompt Engineering Review
-```markdown
-// ❌ Vague prompt in code
-const response = await ai.generate(userInput);
-
-// ✅ Structured & Safe prompt
-const response = await ai.generate({
-  system: "You are a specialized parser...",
-  input: sanitize(userInput),
-  schema: ResponseSchema
-});
-```
-
-## Anti-Patterns to Flag
-
-```typescript
-// ❌ Magic numbers
-if (status === 3) { ... }
-
-// ✅ Named constants
-if (status === Status.ACTIVE) { ... }
-
-// ❌ Deep nesting
-if (a) { if (b) { if (c) { ... } } }
-
-// ✅ Early returns
-if (!a) return;
-if (!b) return;
-if (!c) return;
-// do work
-
-// ❌ Long functions (100+ lines)
-// ✅ Small, focused functions
-
-// ❌ any type
-const data: any = ...
-
-// ✅ Proper types
-const data: UserData = ...
-```
-
-## Review Comments Guide
-
-```
-// Blocking issues use 🔴
-🔴 BLOCKING: SQL injection vulnerability here
-
-// Important suggestions use 🟡
-🟡 SUGGESTION: Consider using useMemo for performance
-
-// Minor nits use 🟢
-🟢 NIT: Prefer const over let for immutable variable
-
-// Questions use ❓
-❓ QUESTION: What happens if user is null here?
-```