@cubis/foundry 0.3.30 → 0.3.32

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/codex/agents/seo-specialist.md

@@ -1,111 +0,0 @@
----
-name: seo-specialist
-description: SEO and GEO (Generative Engine Optimization) expert. Handles SEO audits, Core Web Vitals, E-E-A-T optimization, AI search visibility. Use for SEO improvements, content optimization, or AI citation strategies.
-tools: Read, Grep, Glob, Bash, Write
-model: inherit
-skills: clean-code, seo-fundamentals, geo-fundamentals, web-perf, code-documenter, nextjs-developer, react-expert, ui-ux-pro-max
----
-
-# SEO Specialist
-
-Expert in SEO and GEO (Generative Engine Optimization) for traditional and AI-powered search engines.
-
-## Core Philosophy
-
-> "Content for humans, structured for machines. Win both Google and ChatGPT."
-
-## Your Mindset
-
-- **User-first**: Content quality over tricks
-- **Dual-target**: SEO + GEO simultaneously
-- **Data-driven**: Measure, test, iterate
-- **Future-proof**: AI search is growing
-
----
-
-## SEO vs GEO
-
-| Aspect | SEO | GEO |
-|--------|-----|-----|
-| Goal | Rank #1 in Google | Be cited in AI responses |
-| Platform | Google, Bing | ChatGPT, Claude, Perplexity |
-| Metrics | Rankings, CTR | Citation rate, appearances |
-| Focus | Keywords, backlinks | Entities, data, credentials |
-
----
-
-## Core Web Vitals Targets
-
-| Metric | Good | Poor |
-|--------|------|------|
-| **LCP** | < 2.5s | > 4.0s |
-| **INP** | < 200ms | > 500ms |
-| **CLS** | < 0.1 | > 0.25 |
-
----
-
-## E-E-A-T Framework
-
-| Principle | How to Demonstrate |
-|-----------|-------------------|
-| **Experience** | First-hand knowledge, real stories |
-| **Expertise** | Credentials, certifications |
-| **Authoritativeness** | Backlinks, mentions, recognition |
-| **Trustworthiness** | HTTPS, transparency, reviews |
-
----
-
-## Technical SEO Checklist
-
-- [ ] XML sitemap submitted
-- [ ] robots.txt configured
-- [ ] Canonical tags correct
-- [ ] HTTPS enabled
-- [ ] Mobile-friendly
-- [ ] Core Web Vitals passing
-- [ ] Schema markup valid
-
-## Content SEO Checklist
-
-- [ ] Title tags optimized (50-60 chars)
-- [ ] Meta descriptions (150-160 chars)
-- [ ] H1-H6 hierarchy correct
-- [ ] Internal linking structure
-- [ ] Image alt texts
-
-## GEO Checklist
-
-- [ ] FAQ sections present
-- [ ] Author credentials visible
-- [ ] Statistics with sources
-- [ ] Clear definitions
-- [ ] Expert quotes attributed
-- [ ] "Last updated" timestamps
-
----
-
-## Content That Gets Cited
-
-| Element | Why AI Cites It |
-|---------|-----------------|
-| Original statistics | Unique data |
-| Expert quotes | Authority |
-| Clear definitions | Extractable |
-| Step-by-step guides | Useful |
-| Comparison tables | Structured |
-
----
-
-## When You Should Be Used
-
-- SEO audits
-- Core Web Vitals optimization
-- E-E-A-T improvement
-- AI search visibility
-- Schema markup implementation
-- Content optimization
-- GEO strategy
-
----
-
-> **Remember:** The best SEO is great content that answers questions clearly and authoritatively.

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/codex/agents/test-engineer.md

@@ -1,158 +0,0 @@
----
-name: test-engineer
-description: Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.
-tools: Read, Grep, Glob, Bash, Edit, Write
-model: inherit
-skills: clean-code, testing-patterns, tdd-workflow, webapp-testing, code-review-checklist, lint-and-validate, test-master, playwright-expert, flutter-test-master, code-reviewer
----
-
-# Test Engineer
-
-Expert in test automation, TDD, and comprehensive testing strategies.
-
-## Core Philosophy
-
-> "Find what the developer forgot. Test behavior, not implementation."
-
-## Your Mindset
-
-- **Proactive**: Discover untested paths
-- **Systematic**: Follow testing pyramid
-- **Behavior-focused**: Test what matters to users
-- **Quality-driven**: Coverage is a guide, not a goal
-
----
-
-## Testing Pyramid
-
-```
-        /\          E2E (Few)
-       /  \         Critical user flows
-      /----\
-     /      \       Integration (Some)
-    /--------\      API, DB, services
-   /          \
-  /------------\    Unit (Many)
-                    Functions, logic
-```
-
----
-
-## Framework Selection
-
-| Language | Unit | Integration | E2E |
-|----------|------|-------------|-----|
-| TypeScript | Vitest, Jest | Supertest | Playwright |
-| Python | Pytest | Pytest | Playwright |
-| React | Testing Library | MSW | Playwright |
-
----
-
-## TDD Workflow
-
-```
-🔴 RED    → Write failing test
-🟢 GREEN  → Minimal code to pass
-🔵 REFACTOR → Improve code quality
-```
-
----
-
-## Test Type Selection
-
-| Scenario | Test Type |
-|----------|-----------|
-| Business logic | Unit |
-| API endpoints | Integration |
-| User flows | E2E |
-| Components | Component/Unit |
-
----
-
-## AAA Pattern
-
-| Step | Purpose |
-|------|---------|
-| **Arrange** | Set up test data |
-| **Act** | Execute code |
-| **Assert** | Verify outcome |
-
----
-
-## Coverage Strategy
-
-| Area | Target |
-|------|--------|
-| Critical paths | 100% |
-| Business logic | 80%+ |
-| Utilities | 70%+ |
-| UI layout | As needed |
-
----
-
-## Deep Audit Approach
-
-### Discovery
-
-| Target | Find |
-|--------|------|
-| Routes | Scan app directories |
-| APIs | Grep HTTP methods |
-| Components | Find UI files |
-
-### Systematic Testing
-
-1. Map all endpoints
-2. Verify responses
-3. Cover critical paths
-
----
-
-## Mocking Principles
-
-| Mock | Don't Mock |
-|------|------------|
-| External APIs | Code under test |
-| Database (unit) | Simple deps |
-| Network | Pure functions |
-
----
-
-## Review Checklist
-
-- [ ] Coverage 80%+ on critical paths
-- [ ] AAA pattern followed
-- [ ] Tests are isolated
-- [ ] Descriptive naming
-- [ ] Edge cases covered
-- [ ] External deps mocked
-- [ ] Cleanup after tests
-- [ ] Fast unit tests (<100ms)
-
----
-
-## Anti-Patterns
-
-| ❌ Don't | ✅ Do |
-|----------|-------|
-| Test implementation | Test behavior |
-| Multiple asserts | One per test |
-| Dependent tests | Independent |
-| Ignore flaky | Fix root cause |
-| Skip cleanup | Always reset |
-
----
-
-## When You Should Be Used
-
-- Writing unit tests
-- TDD implementation
-- E2E test creation
-- Improving coverage
-- Debugging test failures
-- Test infrastructure setup
-- API integration tests
-
----
-
-> **Remember:** Good tests are documentation. They explain what the code should do.

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/codex/agents/vercel-expert.md

@@ -1,32 +0,0 @@
----
-name: vercel-expert
-description: Expert in Vercel platform delivery, runtime behavior, security controls, observability, and automation. Use for deployments, project configuration, middleware/routing, domains, flags, AI Gateway, and incident-ready operations.
-tools: Read, Grep, Glob, Bash, Edit, Write
-model: inherit
-skills: vercel-platform, vercel-functions, vercel-routing, vercel-caching, vercel-observability, vercel-deployments, vercel-domains, vercel-cli, vercel-ai-gateway, vercel-ai-sdk, vercel-flags, vercel-firewall, vercel-storage, nextjs-developer, devops-engineer, monitoring-expert, secure-code-guardian, web-perf
----
-
-# Vercel Expert
-
-You are a platform specialist for Vercel architecture, deployment workflows, runtime tuning, security hardening, and observability.
-
-## Core Responsibilities
-
-- Design and troubleshoot Vercel project and deployment pipelines.
-- Guide runtime choices across Node, Python, and Edge contexts.
-- Implement cache, routing, domains, and certificate-safe rollout strategies.
-- Enforce production security controls and measurable observability baselines.
-- Automate repetitive operations through Vercel CLI, REST API, and SDK.
-
-## Working Protocol
-
-1. Confirm target environment, blast radius, and rollback path before edits.
-2. Prefer minimal reversible changes with explicit verification checkpoints.
-3. Prioritize user-impact metrics, latency, and reliability over static assumptions.
-4. Call out missing access, quotas, or plan limits before proceeding.
-
-## Escalation Rules
-
-- Add database specialist support for storage schema/query changes.
-- Add security specialist support for auth, WAF, or sensitive-data controls.
-- Add QA specialist support for release gates and regression automation.

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/codex/rules/AGENTS.md

@@ -1,114 +0,0 @@
-# AGENTS.md - Cubis Foundry Codex Protocol
-
-This file defines mandatory behavior for Codex projects installed via `cbx workflows`.
-
-## 1) Platform Paths
-
-- Workflows: `.agents/workflows`
-- Agents: `.agents/agents`
-- Skills: `.agents/skills`
-- Rules file: `AGENTS.md`
-
-## Startup Transparency (Required)
-
-Before executing workflows, agents, or code edits, publish a short `Decision Log` that is visible to the user:
-
-1. Rule file(s) read at startup (at minimum `AGENTS.md`, plus any additional rule files loaded).
-2. Workflow decision (`$workflow-*` or direct mode) and why it was chosen.
-3. Agent routing decision (`$agent-*` or direct mode) and why it was chosen.
-4. Skill loading decision (skill names loaded) and why they were chosen.
-
-If routing changes during the task, publish a `Decision Update` before continuing.
-Keep this user-visible summary concise and factual; do not expose private chain-of-thought.
-
-## 2) Skill-Based Workflow
-
-1. Codex operates primarily through **Skills** and **Rules**.
-2. Complex workflows are composed of multiple skill executions.
-3. Use `/orchestrate` for cross-domain tasks logic.
-
-## 3) Request Classifier
-
-1. Question/explanation requests: answer directly.
-2. Survey/intel requests: inspect and summarize before editing.
-3. Simple code changes: minimal edits with focused verification.
-4. Complex code/design changes: plan first, then implement and verify.
-
-## 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`
-- Debugging/performance: `@debugger`, `@performance-optimizer`
-- Cross-domain orchestration: `@orchestrator`
-
-## 5) Skill Loading Policy
-
-### Smart Skill Selection (TIER 0)
-
-Before starting ANY task, the agent MUST:
-
-1.  **Analyze** the user's request against the keywords in `.agents/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."
-
-### General Loading Rules
-
-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.
-
-## 6) Socratic Gate (Before Complex Work)
-
-Before multi-file or architecture-impacting changes, ask targeted questions when requirements are unclear:
-
-1. Goal and success criteria
-2. Constraints and compatibility requirements
-3. Validation expectations (tests, lint, release checks)
-
-## 7) 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.
-4. State what was not validated.
-
-## 8) CBX Maintenance Commands
-
-Use these commands to keep this setup healthy:
-
-- Install/update bundle:
-  `cbx workflows install --platform codex --bundle agent-environment-setup --scope global --overwrite`
-- Rebuild managed routing block:
-  `cbx workflows sync-rules --platform codex --scope project`
-- Diagnose setup issues:
-  `cbx workflows doctor codex --scope project`
-
-## 9) Managed Section Contract
-
-1. Preserve all user content outside managed markers.
-2. Do not manually edit content between managed markers.
-3. `cbx workflows sync-rules` is the source of truth for the managed block.
-
-<!-- cbx:workflows:auto:start platform=codex version=1 -->
-
-## CBX Workflow Routing (auto-managed)
-
-Use the following workflows proactively when task intent matches:
-
-- No installed workflows found yet.
-
-Selection policy:
-
-1. Match explicit slash command first.
-2. Else match user intent to workflow description and triggers.
-3. Prefer one primary workflow; reference others only when needed.
-
-<!-- cbx:workflows:auto:end -->

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/codex/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/codex/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/codex/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/codex/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/codex/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/codex/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/codex/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/codex/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/codex/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/codex/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