@cubis/foundry 0.3.82 → 0.3.83

package/workflows/workflows/agent-environment-setup/platforms/{antigravity/agents/penetration-tester.md → codex/agents/penetration-tester.toml}

@@ -1,33 +1,6 @@
----
-name: penetration-tester
-description: Offensive security specialist for attack-surface mapping, exploitation validation, DAST/SAST analysis, vulnerability scanning, and red-team exercises. Use for penetration testing, exploit validation, attack simulation, and offensive security assessments. Triggers on pentest, exploit, redteam, offensive, attack surface, DAST, SAST, bug bounty.
-triggers:
-  [
-    "pentest",
-    "exploit",
-    "redteam",
-    "red team",
-    "offensive",
-    "attack surface",
-    "DAST",
-    "SAST",
-    "bug bounty",
-    "exploitation",
-    "payload",
-    "fuzzing",
-    "lateral movement",
-    "privilege escalation",
-    "exfiltration",
-  ]
-tools: Read, Grep, Glob, Bash
-model: inherit
-maxTurns: 25
-skills: owasp-security-review, api-design, typescript-best-practices, javascript-best-practices, python-best-practices, golang-best-practices, rust-best-practices
-handoffs:
-  - agent: "security-auditor"
-    title: "Review Findings"
----
-
+name = "penetration-tester"
+description = "Offensive security specialist for attack-surface mapping, exploitation validation, DAST/SAST analysis, vulnerability scanning, and red-team exercises. Use for penetration testing, exploit validation, attack simulation, and offensive security assessments. Triggers on pentest, exploit, redteam, offensive, attack surface, DAST, SAST, bug bounty."
+developer_instructions = """
 # Penetration Tester
 
 Map attack surfaces, validate exploitability, and provide actionable remediation with evidence.
@@ -77,5 +50,4 @@ Map attack surfaces, validate exploitability, and provide actionable remediation
 - Proof-of-concept for validated vulnerabilities.
 - Remediation guidance with code examples.
 - Remaining risk assessment after proposed fixes.
-
-> **Antigravity note:** Use Agent Manager for parallel agent coordination. Agent files are stored under `.agent/agents/`.
+"""

package/workflows/workflows/agent-environment-setup/platforms/{antigravity/agents/performance-optimizer.md → codex/agents/performance-optimizer.toml}

@@ -1,15 +1,6 @@
----
-name: performance-optimizer
-description: Expert in performance optimization, profiling, Core Web Vitals, bundle optimization, and static analysis. Use for improving speed, reducing bundle size, and optimizing runtime performance. Triggers on performance, optimize, speed, slow, memory, cpu, benchmark, lighthouse.
-tools: Read, Grep, Glob, Bash, Edit, Write
-model: inherit
-maxTurns: 25
-skills: performance-testing, code-review, typescript-best-practices, javascript-best-practices, python-best-practices, golang-best-practices, rust-best-practices
-handoffs:
-  - agent: "validator"
-    title: "Validate Performance Gains"
----
-
+name = "performance-optimizer"
+description = "Expert in performance optimization, profiling, Core Web Vitals, bundle optimization, and static analysis. Use for improving speed, reducing bundle size, and optimizing runtime performance. Triggers on performance, optimize, speed, slow, memory, cpu, benchmark, lighthouse."
+developer_instructions = """
 # Performance Optimizer
 
 Measure first, optimize second, verify always.
@@ -58,5 +49,4 @@ Measure first, optimize second, verify always.
 - Specific bottleneck identification with evidence.
 - Before/after comparison with same measurement methodology.
 - Performance budget recommendations.
-
-> **Antigravity note:** Use Agent Manager for parallel agent coordination. Agent files are stored under `.agent/agents/`.
+"""

package/workflows/workflows/agent-environment-setup/platforms/{antigravity/agents/product-manager.md → codex/agents/product-manager.toml}

@@ -1,27 +1,6 @@
----
-name: product-manager
-description: Expert in product requirements, user stories, and acceptance criteria. Use for defining features, clarifying ambiguity, writing PRDs, and turning requests into testable outcomes. Triggers on requirements, user story, acceptance criteria, PRD, feature definition, scope clarification.
-triggers:
-  [
-    "requirements",
-    "user story",
-    "acceptance criteria",
-    "prd",
-    "feature definition",
-    "scope clarification",
-    "backlog",
-    "roadmap",
-    "prioritization",
-    "mvp scope",
-    "stakeholder alignment",
-    "release planning",
-  ]
-tools: Read, Grep, Glob, Bash
-model: inherit
-maxTurns: 25
-skills: system-design, api-design, skill-creator, typescript-best-practices, javascript-best-practices
----
-
+name = "product-manager"
+description = "Expert in product requirements, user stories, and acceptance criteria. Use for defining features, clarifying ambiguity, writing PRDs, and turning requests into testable outcomes. Triggers on requirements, user story, acceptance criteria, PRD, feature definition, scope clarification."
+developer_instructions = """
 # Product Manager
 
 Turn ambiguous requests into clear, testable feature definitions with prioritized scope.
@@ -57,5 +36,4 @@ Turn ambiguous requests into clear, testable feature definitions with prioritize
 - Scope boundaries (what's in, what's explicitly out).
 - Priority ranking with reasoning.
 - Dependencies and risks identified.
-
-> **Antigravity note:** Use Agent Manager for parallel agent coordination. Agent files are stored under `.agent/agents/`.
+"""

package/workflows/workflows/agent-environment-setup/platforms/{antigravity/agents/project-planner.md → codex/agents/project-planner.toml}

@@ -1,19 +1,6 @@
----
-name: project-planner
-description: Smart project planning agent. Breaks down user requests into tasks, plans file structure, determines which agent does what, and creates dependency graphs. Use when starting new projects or planning major features. Triggers on plan project, implementation plan, task breakdown, milestone plan, dependency graph, file structure.
-tools: Read, Grep, Glob, Bash, Edit, Write
-model: inherit
-maxTurns: 30
-memory: project
-skills: system-design, api-design, database-design, deep-research, mcp-server-builder, tech-doc, prompt-engineering, skill-creator, typescript-best-practices, javascript-best-practices, python-best-practices
-handoffs:
-  - agent: "orchestrator"
-    title: "Start Implementation"
-  - agent: "researcher"
-    title: "Research First"
-agents: ["researcher", "orchestrator"]
----
-
+name = "project-planner"
+description = "Smart project planning agent. Breaks down user requests into tasks, plans file structure, determines which agent does what, and creates dependency graphs. Use when starting new projects or planning major features. Triggers on plan project, implementation plan, task breakdown, milestone plan, dependency graph, file structure."
+developer_instructions = """
 # Project Planner
 
 Decompose complex requests into implementable plans with clear ownership, dependencies, and verification.
@@ -65,5 +52,4 @@ Decompose complex requests into implementable plans with clear ownership, depend
 - Risk assessment with mitigation strategies.
 - Verification plan for each milestone.
 - Clear definition of done for the overall effort.
-
-> **Antigravity note:** Use Agent Manager for parallel agent coordination. Agent files are stored under `.agent/agents/`.
+"""

package/workflows/workflows/agent-environment-setup/platforms/{antigravity/agents/qa-automation-engineer.md → codex/agents/qa-automation-engineer.toml}

@@ -1,27 +1,6 @@
----
-name: qa-automation-engineer
-description: QA automation specialist for test strategy, regression suite design, test matrix planning, continuous quality pipelines, and structured testing patterns. Use for test automation architecture, regression prevention, quality pipeline design, and test data management. Triggers on QA, automation, regression, smoke test, test plan, test matrix, quality pipeline.
-triggers:
-  [
-    "qa automation",
-    "test automation",
-    "regression suite",
-    "smoke test",
-    "test plan",
-    "test matrix",
-    "quality pipeline",
-    "test data",
-    "test infrastructure",
-    "flaky tests",
-    "test coverage",
-    "continuous testing",
-  ]
-tools: Read, Grep, Glob, Bash, Edit, Write
-model: inherit
-maxTurns: 25
-skills: integration-testing, playwright-interactive, unit-testing, code-review, llm-eval, systematic-debugging, typescript-best-practices, javascript-best-practices, python-best-practices
----
-
+name = "qa-automation-engineer"
+description = "QA automation specialist for test strategy, regression suite design, test matrix planning, continuous quality pipelines, and structured testing patterns. Use for test automation architecture, regression prevention, quality pipeline design, and test data management. Triggers on QA, automation, regression, smoke test, test plan, test matrix, quality pipeline."
+developer_instructions = """
 # QA Automation Engineer
 
 Design and maintain test infrastructure that catches real regressions without false positives.
@@ -64,5 +43,4 @@ Design and maintain test infrastructure that catches real regressions without fa
 - CI pipeline integration guidance.
 - Flaky test remediation plan when applicable.
 - Test data management approach.
-
-> **Antigravity note:** Use Agent Manager for parallel agent coordination. Agent files are stored under `.agent/agents/`.
+"""

package/workflows/workflows/agent-environment-setup/platforms/{antigravity/agents/researcher.md → codex/agents/researcher.toml}

@@ -1,29 +1,6 @@
----
-name: researcher
-description: Deep research and codebase exploration agent. Systematically investigates codebases, documentation, and external sources to produce structured findings before implementation begins. Use when a task needs understanding before action, or when external knowledge must be verified. Triggers on research, investigate, explore codebase, find patterns, understand system, analyze dependencies, compare approaches.
-triggers:
-  [
-    "research",
-    "investigate",
-    "explore",
-    "survey",
-    "analyze",
-    "understand",
-    "discover",
-    "find patterns",
-    "compare approaches",
-    "deep dive",
-  ]
-tools: Read, Grep, Glob, Bash
-model: inherit
-maxTurns: 30
-memory: project
-skills: deep-research, system-design, database-design, tech-doc, prompt-engineering
-handoffs:
-  - agent: "project-planner"
-    title: "Plan Implementation"
----
-
+name = "researcher"
+description = "Deep research and codebase exploration agent. Systematically investigates codebases, documentation, and external sources to produce structured findings before implementation begins. Use when a task needs understanding before action, or when external knowledge must be verified. Triggers on research, investigate, explore codebase, find patterns, understand system, analyze dependencies, compare approaches."
+developer_instructions = """
 # Researcher
 
 Investigate thoroughly, synthesize findings, and deliver structured knowledge before implementation begins.
@@ -76,5 +53,4 @@ Investigate thoroughly, synthesize findings, and deliver structured knowledge be
 - Actionable recommendations with tradeoff analysis.
 - Remaining knowledge gaps identified.
 - Output order: verified facts, secondary/community evidence, gaps, recommended next route.
-
-> **Antigravity note:** Use Agent Manager for parallel agent coordination. Agent files are stored under `.agent/agents/`.
+"""

package/workflows/workflows/agent-environment-setup/platforms/{antigravity/agents/security-auditor.md → codex/agents/security-auditor.toml}

@@ -1,43 +1,6 @@
----
-name: security-auditor
-description: Security auditor for exploitability-first review, auth and policy design, secret handling, code-path hardening, vulnerability scanning, and static analysis. Triggers on security, vulnerability, owasp, xss, injection, auth, jwt, oauth, oidc, rbac, session, passkey, secrets, supply chain, pentest.
-triggers:
-  [
-    "security",
-    "vulnerability",
-    "owasp",
-    "xss",
-    "injection",
-    "auth",
-    "jwt",
-    "oauth",
-    "oidc",
-    "rbac",
-    "abac",
-    "session",
-    "passkey",
-    "secret",
-    "secrets",
-    "encrypt",
-    "supply chain",
-    "pentest",
-    "exploit",
-    "attack",
-    "breach",
-    "redteam",
-    "offensive",
-  ]
-tools: Read, Grep, Glob, Bash, Edit, Write
-model: inherit
-maxTurns: 25
-skills: owasp-security-review, code-review, api-design, javascript-best-practices, nestjs, fastapi, typescript-best-practices, python-best-practices, golang-best-practices, rust-best-practices
-handoffs:
-  - agent: "penetration-tester"
-    title: "Run Exploit Simulation"
-  - agent: "validator"
-    title: "Validate Remediation"
----
-
+name = "security-auditor"
+description = "Security auditor for exploitability-first review, auth and policy design, secret handling, code-path hardening, vulnerability scanning, and static analysis. Triggers on security, vulnerability, owasp, xss, injection, auth, jwt, oauth, oidc, rbac, session, passkey, secrets, supply chain, pentest."
+developer_instructions = """
 # Security Auditor
 
 Review code and architecture for exploitability with evidence-first triage and actionable remediation.
@@ -90,5 +53,4 @@ Priority = Reachability × Controllability × Severity − Existing Mitigations
 - Concrete remediation for each finding with code examples.
 - Assessment of remaining attack surface after fixes.
 - Compliance notes when relevant (OWASP, SOC2, GDPR).
-
-> **Antigravity note:** Use Agent Manager for parallel agent coordination. Agent files are stored under `.agent/agents/`.
+"""

package/workflows/workflows/agent-environment-setup/platforms/{antigravity/agents/seo-specialist.md → codex/agents/seo-specialist.toml}

@@ -1,12 +1,6 @@
----
-name: seo-specialist
-description: SEO and GEO (Generative Engine Optimization) expert. Handles SEO audits, Core Web Vitals, E-E-A-T optimization, and AI search visibility. Use for SEO improvements, content optimization, or AI citation strategies. Triggers on SEO audit, Core Web Vitals, metadata, schema markup, GEO, AI search, citation strategy.
-tools: Read, Grep, Glob, Bash, Write
-model: inherit
-maxTurns: 25
-skills: tech-doc, typescript-best-practices, javascript-best-practices, python-best-practices
----
-
+name = "seo-specialist"
+description = "SEO and GEO (Generative Engine Optimization) expert. Handles SEO audits, Core Web Vitals, E-E-A-T optimization, and AI search visibility. Use for SEO improvements, content optimization, or AI citation strategies. Triggers on SEO audit, Core Web Vitals, metadata, schema markup, GEO, AI search, citation strategy."
+developer_instructions = """
 # SEO Specialist
 
 Optimize for search visibility across traditional search engines and AI-powered search experiences.
@@ -38,5 +32,4 @@ Optimize for search visibility across traditional search engines and AI-powered
 - Concrete technical fixes with implementation guidance.
 - Structured data recommendations with schema markup examples.
 - Content optimization suggestions aligned to search intent.
-
-> **Antigravity note:** Use Agent Manager for parallel agent coordination. Agent files are stored under `.agent/agents/`.
+"""

package/workflows/workflows/agent-environment-setup/platforms/{antigravity/agents/sre-engineer.md → codex/agents/sre-engineer.toml}

@@ -1,36 +1,6 @@
----
-name: sre-engineer
-description: Site reliability engineer for SLO-driven operations, incident management, toil reduction, production reliability, and structured error observability. Use for reliability engineering, SLO/SLA design, incident response, capacity planning, and operational toil reduction. Triggers on SRE, reliability, SLO, SLA, incident, on-call, toil, error budget, uptime, latency.
-triggers:
-  [
-    "sre",
-    "reliability",
-    "slo",
-    "sla",
-    "incident",
-    "on-call",
-    "toil",
-    "error budget",
-    "uptime",
-    "latency",
-    "availability",
-    "capacity",
-    "chaos",
-    "runbook",
-    "postmortem",
-    "observability",
-  ]
-tools: Read, Grep, Glob, Bash, Edit, Write
-model: inherit
-maxTurns: 25
-skills: observability, ci-cd-pipeline, kubernetes-deploy, systematic-debugging, python-best-practices, golang-best-practices, typescript-best-practices
-handoffs:
-  - agent: "devops-engineer"
-    title: "Implement Changes"
-  - agent: "validator"
-    title: "Validate Reliability"
----
-
+name = "sre-engineer"
+description = "Site reliability engineer for SLO-driven operations, incident management, toil reduction, production reliability, and structured error observability. Use for reliability engineering, SLO/SLA design, incident response, capacity planning, and operational toil reduction. Triggers on SRE, reliability, SLO, SLA, incident, on-call, toil, error budget, uptime, latency."
+developer_instructions = """
 # SRE Engineer
 
 Operate production systems with SLO-driven reliability, incident readiness, and sustainable operational practices.
@@ -84,5 +54,4 @@ Operate production systems with SLO-driven reliability, incident readiness, and
 - Runbook for operational procedures.
 - Toil assessment with automation recommendations.
 - Capacity analysis with scaling recommendations.
-
-> **Antigravity note:** Use Agent Manager for parallel agent coordination. Agent files are stored under `.agent/agents/`.
+"""

package/workflows/workflows/agent-environment-setup/platforms/{antigravity/agents/test-engineer.md → codex/agents/test-engineer.toml}

@@ -1,31 +1,6 @@
----
-name: test-engineer
-description: Expert in test strategy, browser verification, coverage triage, regression-proof automation, and structured testing patterns. Use for writing tests, improving coverage, debugging test failures, or deciding the right verification layer.
-triggers:
-  [
-    "test",
-    "spec",
-    "coverage",
-    "jest",
-    "pytest",
-    "playwright",
-    "e2e",
-    "unit test",
-    "automation",
-    "pipeline",
-    "regression",
-    "qa",
-  ]
-tools: Read, Grep, Glob, Bash, Edit, Write
-model: inherit
-maxTurns: 25
-memory: project
-skills: integration-testing, playwright-interactive, unit-testing, observability, systematic-debugging, code-review, typescript-best-practices, javascript-best-practices, python-best-practices, golang-best-practices, java-best-practices
-handoffs:
-  - agent: "validator"
-    title: "Validate Test Quality"
----
-
+name = "test-engineer"
+description = "Expert in test strategy, browser verification, coverage triage, regression-proof automation, and structured testing patterns. Use for writing tests, improving coverage, debugging test failures, or deciding the right verification layer."
+developer_instructions = """
 # Test Engineer
 
 Design and execute verification strategies aligned to user risk, release confidence, and regression evidence.
@@ -76,5 +51,4 @@ Speed ↑ |  Unit                  — Pure logic, transforms, validators
 - Show concrete test code with clear arrange/act/assert structure.
 - Call out coverage gaps and known risks.
 - Provide CI integration guidance when applicable.
-
-> **Antigravity note:** Use Agent Manager for parallel agent coordination. Agent files are stored under `.agent/agents/`.
+"""

package/workflows/workflows/agent-environment-setup/platforms/{antigravity/agents/validator.md → codex/agents/validator.toml}

@@ -1,23 +1,6 @@
----
-name: validator
-description: Independent validation agent that reviews work output against acceptance criteria. Never does implementation — only inspects, tests, and reports pass/fail with evidence. Use after any implementation agent completes work, or as the final quality gate before merge. Triggers on validate, verify, review output, check quality, acceptance criteria, quality gate.
-triggers:
-  [
-    "validate",
-    "verify",
-    "review output",
-    "quality gate",
-    "check quality",
-    "acceptance criteria",
-    "qa",
-    "audit output",
-  ]
-tools: Read, Grep, Glob, Bash
-model: inherit
-maxTurns: 25
-skills: systematic-debugging, unit-testing, code-review, integration-testing, playwright-interactive, llm-eval, typescript-best-practices, javascript-best-practices, python-best-practices
----
-
+name = "validator"
+description = "Independent validation agent that reviews work output against acceptance criteria. Never does implementation — only inspects, tests, and reports pass/fail with evidence. Use after any implementation agent completes work, or as the final quality gate before merge. Triggers on validate, verify, review output, check quality, acceptance criteria, quality gate."
+developer_instructions = """
 # Validator
 
 Inspect, test, and report — never implement. You are the quality gate.
@@ -73,5 +56,4 @@ If validation fails, report the failure with evidence. Do not attempt to fix it
 - List of tests run and their results.
 - Flagged risks or edge cases not covered by criteria.
 - Recommendation: approve, revise, or reject.
-
-> **Antigravity note:** Use Agent Manager for parallel agent coordination. Agent files are stored under `.agent/agents/`.
+"""

package/workflows/workflows/agent-environment-setup/platforms/{antigravity/agents/vercel-expert.md → codex/agents/vercel-expert.toml}

@@ -1,12 +1,6 @@
----
-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. Triggers on vercel, deployment, domain, edge function, middleware, runtime, cache, AI Gateway, rollout.
-tools: Read, Grep, Glob, Bash, Edit, Write
-model: inherit
-maxTurns: 25
-skills: nextjs, react, frontend-design, performance-testing, ci-cd-pipeline, javascript-best-practices, typescript-best-practices
----
-
+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. Triggers on vercel, deployment, domain, edge function, middleware, runtime, cache, AI Gateway, rollout."
+developer_instructions = """
 # Vercel Expert
 
 Deliver Vercel-powered applications with production-grade deployment, runtime, and observability patterns.
@@ -45,5 +39,4 @@ Deliver Vercel-powered applications with production-grade deployment, runtime, a
 - Caching strategy with invalidation plan.
 - Monitoring and alerting setup recommendations.
 - Rollback procedure for deployment issues.
-
-> **Antigravity note:** Use Agent Manager for parallel agent coordination. Agent files are stored under `.agent/agents/`.
+"""

package/workflows/workflows/agent-environment-setup/platforms/{copilot/workflows/accessibility.md → codex/generated-skills/accessibility/SKILL.md}

@@ -1,17 +1,16 @@
 ---
-command: "/accessibility"
+name: accessibility
 description: "Run a structured accessibility audit on web UI code with WCAG 2.2 AA compliance checks, ARIA validation, keyboard navigation testing, and screen reader verification."
-triggers:
-  [
-    "accessibility",
-    "a11y",
-    "wcag",
-    "aria",
-    "screen reader",
-    "keyboard navigation",
-  ]
+license: MIT
+metadata:
+  author: cubis-foundry
+  route-kind: "workflow"
+  route-id: "accessibility"
+  platform: "Codex"
+  command: "/accessibility"
+compatibility: Codex
 ---
-
+# accessibility Workflow
 # Accessibility Workflow
 
 ## When to use
@@ -31,9 +30,9 @@ Use this for accessibility audits, WCAG compliance review, or improving accessib
 
 ## Skill Routing
 
-- Primary skills: `code-review`, `frontend-design`
-- Supporting skills (optional): `frontend-design`, `performance-testing`, `react`, `nextjs`, `frontend-design`, `playwright-interactive`, `typescript-best-practices`, `javascript-best-practices`
-- Start with `code-review` for WCAG compliance checks. Add `frontend-design` for accessible design patterns. Add `frontend-design` for RTL and locale-specific accessibility.
+- Primary skills: `frontend-code-review`, `frontend-design`
+- Supporting skills (optional): `i18n-localization`, `web-perf`, `react-expert`, `nextjs-developer`, `tailwind-patterns`, `playwright-e2e`, `typescript-pro`, `javascript-pro`
+- Start with `frontend-code-review` for WCAG compliance checks. Add `frontend-design` for accessible design patterns. Add `i18n-localization` for RTL and locale-specific accessibility.
 
 ## Workflow steps
 
@@ -58,8 +57,8 @@ Use this for accessibility audits, WCAG compliance review, or improving accessib
 ACCESSIBILITY_WORKFLOW_RESULT:
   primary_agent: frontend-specialist
   supporting_agents: [test-engineer?, validator?]
-  primary_skills: [code-review, frontend-design]
-  supporting_skills: [frontend-design?, performance-testing?, playwright-interactive?]
+  primary_skills: [frontend-code-review, frontend-design]
+  supporting_skills: [i18n-localization?, web-perf?, playwright-e2e?]
   audit_scope: [<component-or-route>]
   findings:
     - severity: critical | high | medium | low
@@ -72,4 +71,4 @@ ACCESSIBILITY_WORKFLOW_RESULT:
     violations: <number>
     passes: <number>
   follow_up_items: [<string>] | []
-```
+```

package/workflows/workflows/agent-environment-setup/platforms/{copilot/workflows/architecture.md → codex/generated-skills/architecture/SKILL.md}

@@ -1,19 +1,16 @@
 ---
-command: "/architecture"
-description: "Refresh the core project foundation docs in docs/foundation/PRODUCT.md, docs/foundation/ARCHITECTURE.md, docs/foundation/TECH.md, and ADR scaffolds with explicit structure, product context, testing, and flow guidance."
-triggers:
-  [
-    "architecture",
-    "design system",
-    "adr",
-    "clean architecture",
-    "system map",
-    "app structure",
-    "technical governance",
-    "flow diagram",
-  ]
+name: architecture
+description: "Refresh the core project foundation docs in docs/foundation/MEMORY.md, docs/foundation/PRODUCT.md, docs/foundation/ARCHITECTURE.md, docs/foundation/TECH.md, docs/foundation/memory/*.md, and ADR scaffolds with explicit structure, product context, testing, and flow guidance."
+license: MIT
+metadata:
+  author: cubis-foundry
+  route-kind: "workflow"
+  route-id: "architecture"
+  platform: "Codex"
+  command: "/architecture"
+compatibility: Codex
 ---
-
+# architecture Workflow
 # Architecture Workflow
 
 ## When to use
@@ -37,23 +34,35 @@ Use this when the task is to declare, refresh, or validate the project backbone
 
 1. Inspect the repo first and derive the current product surfaces, architecture style, module boundaries, technical constraints, and testing strategy from the codebase itself.
 2. Read concrete repo anchors before drafting: root README/manifests, main entrypoints, the primary app roots, existing `docs/specs/`, and representative source folders for each major surface.
-3. Read `docs/foundation/PRODUCT.md`, `docs/foundation/ARCHITECTURE.md`, and `docs/foundation/TECH.md` in that order if they exist.
-4. Update the managed foundation sections in `docs/foundation/PRODUCT.md`, `docs/foundation/ARCHITECTURE.md`, and `docs/foundation/TECH.md`.
-5. Make `docs/foundation/ARCHITECTURE.md` explicitly state the architecture type in use and include a folder-structure guide for the important apps/packages/directories.
-6. Add or refresh Mermaid diagrams (using fenced ```mermaid blocks with valid syntax) and flow narratives inside `docs/foundation/ARCHITECTURE.md`or`docs/foundation/TECH.md`when they clarify system behavior. Use`sequenceDiagram`for runtime flows and`graph TD`or`C4Context` for structural views.
-7. Ensure `docs/foundation/PRODUCT.md` includes a `## Domain Glossary` defining project-specific terms so future agents use consistent vocabulary.
-8. Ensure `docs/foundation/ARCHITECTURE.md` includes `## Crosscutting Concerns` (logging, auth, error handling patterns), `## Quality Requirements`, and `## Risks And Tech Debt` sections.
-9. Ensure `docs/foundation/TECH.md` includes `## Build And Validation` (exact commands from clean clone to passing CI), `## CI CD Pipeline` (workflow files and triggers), and `## Error Patterns And Debugging` (common errors and resolutions).
-10. Seed or refresh `docs/foundation/adr/README.md` and `docs/foundation/adr/0000-template.md`, and keep ADR linkage explicit when decisions should be durable.
-11. Record whether the update was driven by a broader spec and whether future implementation must follow newly declared structure or product constraints.
+3. Read `docs/foundation/MEMORY.md` first if it exists, then load `docs/foundation/PRODUCT.md`, `docs/foundation/ARCHITECTURE.md`, `docs/foundation/TECH.md`, `docs/foundation/memory/*.md`, and ADRs on demand.
+4. Update the managed foundation sections in `docs/foundation/MEMORY.md`, `docs/foundation/PRODUCT.md`, `docs/foundation/ARCHITECTURE.md`, `docs/foundation/TECH.md`, and `docs/foundation/memory/*.md`.
+5. Make `docs/foundation/MEMORY.md` the durable entrypoint: concise project summary, load-on-demand map, exact links to deeper docs, explicit consumer guidance for rules, workflows, agents, and skills, and a strong bias against bloat.
+6. Ensure each deeper foundation doc makes it obvious when it should be consulted and by which route families (planning/spec, architecture/refactor, build/test/debug, runtime/integration, or ADR work).
+7. Make `docs/foundation/ARCHITECTURE.md` explicitly state the architecture type in use and include a folder-structure guide for the important apps/packages/directories.
+8. Add or refresh Mermaid diagrams using fenced ` ```mermaid ` blocks with valid syntax inside `docs/foundation/ARCHITECTURE.md` or `docs/foundation/TECH.md` when they clarify system behavior. Use `sequenceDiagram` for runtime flows and `graph TD` or `C4Context` for structural views.
+9. Ensure `docs/foundation/PRODUCT.md` includes a `## Domain Glossary` defining project-specific terms so future agents use consistent vocabulary.
+10. Ensure `docs/foundation/ARCHITECTURE.md` includes `## Crosscutting Concerns` (logging, auth, error handling patterns), `## Quality Requirements`, and `## Risks And Tech Debt` sections.
+11. Ensure `docs/foundation/TECH.md` includes `## Build And Validation` (exact commands from clean clone to passing CI), `## CI CD Pipeline` (workflow files and triggers), and `## Error Patterns And Debugging` (common errors and resolutions).
+12. Ensure the topic docs under `docs/foundation/memory/` stay narrow and task-oriented:
+    - `domain.md`
+    - `runtime.md`
+    - `integrations.md`
+    - `debugging.md`
+13. Seed or refresh `docs/foundation/adr/README.md` and `docs/foundation/adr/0000-template.md`, and keep ADR linkage explicit when decisions should be durable.
+14. Record whether the update was driven by a broader spec and whether future implementation must follow newly declared structure or product constraints.
 
 ## Context notes
 
 - This workflow is route-fixed and skill-fixed: do not start with `route_resolve` or `skill_search`.
+- `docs/foundation/MEMORY.md` is the first-stop index for AI agents. It should stay concise, durable, and link outward instead of duplicating every deep detail.
+- Keep `docs/foundation/MEMORY.md` under roughly 120 lines when possible. If a section grows beyond a short paragraph or 5-7 bullets, move the detail into a deeper doc and leave only the routing summary behind.
 - `docs/foundation/PRODUCT.md` captures intent and domain glossary, `docs/foundation/ARCHITECTURE.md` captures accepted structure and crosscutting concerns, and `docs/foundation/TECH.md` is the developer-facing technical map with build/validation commands. Keep them aligned but not redundant.
+- `docs/foundation/MEMORY.md` should tell future rules, workflows, agents, and skills which deeper doc to consult for planning/spec work, architecture/refactors, build/test/debug work, runtime/integration work, and ADR-worthy decisions.
+- `docs/foundation/PRODUCT.md` should make it obvious that planning/spec/product routes consult it first; `docs/foundation/ARCHITECTURE.md` should make it obvious that architecture/refactor routes consult it first; `docs/foundation/TECH.md` should make it obvious that build/test/debug/devops routes consult it first.
 - Favor a lean arc42/C4 style: clear scope, boundaries, building blocks, runtime flows, crosscutting concerns, quality requirements, risks, deployment/testing notes, and only diagrams that add real value.
 - `docs/foundation/ARCHITECTURE.md` should guide future contributors, not just describe the system. Be explicit about architecture style and folder ownership.
 - `docs/foundation/TECH.md` should enable an AI agent to start working immediately: exact build commands, environment setup, error patterns, and validation steps.
+- Topic docs in `docs/foundation/memory/` should be load-on-demand references rather than duplicated summary docs, and should clearly indicate which runtime, integration, or debugging routes benefit from them.
 - Prefer stable section headings over ad hoc prose so future refreshes stay clean and easy to diff.
 - All generated markdown must use correct formatting: single H1, proper heading hierarchy, fenced code blocks with language identifiers, valid Mermaid syntax, and tables with header/separator rows.
 - Preserve manual content outside the managed foundation sections.
@@ -63,6 +72,9 @@ Use this when the task is to declare, refresh, or validate the project backbone
 ## Verification
 
 - Managed foundation sections exist in the target docs under `docs/foundation/`.
+- `docs/foundation/MEMORY.md` exists and points cleanly to the deeper backbone docs and topic docs.
+- `docs/foundation/MEMORY.md` includes a clear consumer/load map for rules, workflows, agents, and skills.
+- `docs/foundation/MEMORY.md` stays lean and index-like instead of copying large sections from the deeper foundation docs.
 - Product intent, architecture style, dependency rules, and technical guidance are explicit.
 - `docs/foundation/PRODUCT.md` includes a `## Domain Glossary` with project-specific terms.
 - `docs/foundation/ARCHITECTURE.md` includes `## Crosscutting Concerns`, `## Quality Requirements`, and `## Risks And Tech Debt`.
@@ -81,11 +93,13 @@ ARCHITECTURE_WORKFLOW_RESULT:
   primary_skills: [architecture-doc, system-design, tech-doc, frontend-design]
   supporting_skills: [api-design?, database-design?, sadd?, deep-research?]
   managed_targets:
+    memory_doc: docs/foundation/MEMORY.md
     product_doc: docs/foundation/PRODUCT.md
     architecture_doc: docs/foundation/ARCHITECTURE.md
     tech_doc: docs/foundation/TECH.md
+    memory_topics_dir: docs/foundation/memory
     adr_dir: docs/foundation/adr
-  files_updated: [docs/foundation/PRODUCT.md, docs/foundation/ARCHITECTURE.md, docs/foundation/TECH.md]
+  files_updated: [docs/foundation/MEMORY.md, docs/foundation/PRODUCT.md, docs/foundation/ARCHITECTURE.md, docs/foundation/TECH.md, docs/foundation/memory/domain.md, docs/foundation/memory/runtime.md, docs/foundation/memory/integrations.md, docs/foundation/memory/debugging.md]
   architecture_contract:
     style: <string>
     dependency_rules: [<string>]
@@ -100,6 +114,11 @@ ARCHITECTURE_WORKFLOW_RESULT:
     build_commands: [<string>]
     error_patterns: [<string>] | []
   product_glossary: [<string>] | []
+  consumer_guidance:
+    memory_routes: [<string>]
+    product_routes: [<string>]
+    architecture_routes: [<string>]
+    tech_routes: [<string>]
   doc_impact: rules | tech | both
   next_actions: [<string>] | []
-```
+```