@cubis/foundry 0.3.62 → 0.3.64

package/workflows/workflows/agent-environment-setup/platforms/windsurf/skills/skills_index.json

@@ -1,4 +1,24 @@
 [
+  {
+    "id": "2d-games",
+    "name": "2d-games",
+    "canonical_id": "2d-games",
+    "deprecated": false,
+    "replaced_by": null,
+    "path": ".windsurf/skills/game-development/2d-games/SKILL.md",
+    "description": "2D game development principles. Sprites, tilemaps, physics, camera.",
+    "triggers": []
+  },
+  {
+    "id": "3d-games",
+    "name": "3d-games",
+    "canonical_id": "3d-games",
+    "deprecated": false,
+    "replaced_by": null,
+    "path": ".windsurf/skills/game-development/3d-games/SKILL.md",
+    "description": "3D game development principles. Rendering, shaders, physics, cameras.",
+    "triggers": []
+  },
   {
     "id": "accessibility",
     "name": "accessibility",
@@ -16,7 +36,7 @@
     "deprecated": false,
     "replaced_by": null,
     "path": ".windsurf/skills/api-designer/SKILL.md",
-    "description": "Use when designing REST or GraphQL APIs, creating OpenAPI specifications, or planning API architecture. Invoke for resource modeling, versioning strategies, pagination patterns, error handling standards.",
+    "description": "Use when defining or reviewing external API contracts, OpenAPI specifications, resource models, pagination, versioning, or error response standards. Do not use for pure database design, implementation-only handler work, or framework-specific backend setup.",
     "triggers": []
   },
   {
@@ -408,6 +428,36 @@
     "description": "Design thinking and decision-making for web UI. Use when designing components, layouts, color schemes, typography, or creating aesthetic interfaces. Teaches principles, not fixed values.",
     "triggers": []
   },
+  {
+    "id": "game-art",
+    "name": "game-art",
+    "canonical_id": "game-art",
+    "deprecated": false,
+    "replaced_by": null,
+    "path": ".windsurf/skills/game-development/game-art/SKILL.md",
+    "description": "Game art principles. Visual style selection, asset pipeline, animation workflow.",
+    "triggers": []
+  },
+  {
+    "id": "game-audio",
+    "name": "game-audio",
+    "canonical_id": "game-audio",
+    "deprecated": false,
+    "replaced_by": null,
+    "path": ".windsurf/skills/game-development/game-audio/SKILL.md",
+    "description": "Game audio principles. Sound design, music integration, adaptive audio systems.",
+    "triggers": []
+  },
+  {
+    "id": "game-design",
+    "name": "game-design",
+    "canonical_id": "game-design",
+    "deprecated": false,
+    "replaced_by": null,
+    "path": ".windsurf/skills/game-development/game-design/SKILL.md",
+    "description": "Game design principles. GDD structure, balancing, player psychology, progression.",
+    "triggers": []
+  },
   {
     "id": "game-development",
     "name": "game-development",
@@ -515,7 +565,7 @@
     "deprecated": false,
     "replaced_by": null,
     "path": ".windsurf/skills/javascript-pro/SKILL.md",
-    "description": "Use for modern JavaScript architecture and implementation across browser, Node, and edge runtimes with ES2025+ practices.",
+    "description": "Use for modern JavaScript architecture and implementation across browser, Node, and edge runtimes with runtime-aware production practices.",
     "triggers": []
   },
   {
@@ -577,6 +627,26 @@
     "description": "Mobile-first design thinking and decision-making for iOS and Android apps. Touch interaction, performance patterns, platform conventions. Teaches principles, not fixed values. Use when building React Native, Flutter, or native mobile apps.",
     "triggers": []
   },
+  {
+    "id": "mobile-games",
+    "name": "mobile-games",
+    "canonical_id": "mobile-games",
+    "deprecated": false,
+    "replaced_by": null,
+    "path": ".windsurf/skills/game-development/mobile-games/SKILL.md",
+    "description": "Mobile game development principles. Touch input, battery, performance, app stores.",
+    "triggers": []
+  },
+  {
+    "id": "mongodb",
+    "name": "mongodb",
+    "canonical_id": "mongodb",
+    "deprecated": false,
+    "replaced_by": null,
+    "path": ".windsurf/skills/database-skills/skills/mongodb/SKILL.md",
+    "description": "MongoDB and Mongoose modeling, indexing, pagination, query tuning, and transaction guidance.",
+    "triggers": []
+  },
   {
     "id": "monitoring-expert",
     "name": "monitoring-expert",
@@ -603,6 +673,36 @@
       "bottleneck"
     ]
   },
+  {
+    "id": "multiplayer",
+    "name": "multiplayer",
+    "canonical_id": "multiplayer",
+    "deprecated": false,
+    "replaced_by": null,
+    "path": ".windsurf/skills/game-development/multiplayer/SKILL.md",
+    "description": "Multiplayer game development principles. Architecture, networking, synchronization.",
+    "triggers": []
+  },
+  {
+    "id": "mysql",
+    "name": "mysql",
+    "canonical_id": "mysql",
+    "deprecated": false,
+    "replaced_by": null,
+    "path": ".windsurf/skills/database-skills/skills/mysql/SKILL.md",
+    "description": "MySQL/InnoDB schema design, indexing, pagination, query tuning, and operational safety.",
+    "triggers": []
+  },
+  {
+    "id": "neki",
+    "name": "neki",
+    "canonical_id": "neki",
+    "deprecated": false,
+    "replaced_by": null,
+    "path": ".windsurf/skills/database-skills/skills/neki/SKILL.md",
+    "description": "Neki planning guidance for sharded Postgres architecture decisions and operational guardrails.",
+    "triggers": []
+  },
   {
     "id": "nestjs-expert",
     "name": "nestjs-expert",
@@ -703,6 +803,16 @@
     "description": "Multi-agent orchestration patterns. Use when multiple independent tasks can run with different domain expertise or when comprehensive analysis requires multiple perspectives.",
     "triggers": []
   },
+  {
+    "id": "pc-games",
+    "name": "pc-games",
+    "canonical_id": "pc-games",
+    "deprecated": false,
+    "replaced_by": null,
+    "path": ".windsurf/skills/game-development/pc-games/SKILL.md",
+    "description": "PC and console game development principles. Engine selection, platform features, optimization strategies.",
+    "triggers": []
+  },
   {
     "id": "performance-profiling",
     "name": "performance-profiling",
@@ -741,6 +851,26 @@
       "visual testing"
     ]
   },
+  {
+    "id": "postgres",
+    "name": "postgres",
+    "canonical_id": "postgres",
+    "deprecated": false,
+    "replaced_by": null,
+    "path": ".windsurf/skills/database-skills/skills/postgres/SKILL.md",
+    "description": "PostgreSQL schema, indexing, pagination, query optimization, migrations, and operations.",
+    "triggers": []
+  },
+  {
+    "id": "postman",
+    "name": "postman",
+    "canonical_id": "postman",
+    "deprecated": false,
+    "replaced_by": null,
+    "path": ".windsurf/skills/postman/SKILL.md",
+    "description": "Automate API testing and collection management with Postman MCP using full-mode defaults and workspace-aware execution.",
+    "triggers": []
+  },
   {
     "id": "powershell-windows",
     "name": "powershell-windows",
@@ -811,6 +941,16 @@
     "description": "Red team tactics principles based on MITRE ATT&CK. Attack phases, detection evasion, reporting.",
     "triggers": []
   },
+  {
+    "id": "redis",
+    "name": "redis",
+    "canonical_id": "redis",
+    "deprecated": false,
+    "replaced_by": null,
+    "path": ".windsurf/skills/database-skills/skills/redis/SKILL.md",
+    "description": "Redis data modeling, caching strategy, throughput/latency optimization, and operational safety.",
+    "triggers": []
+  },
   {
     "id": "refactor",
     "name": "refactor",
@@ -932,6 +1072,16 @@
     "description": "Compatibility alias skill. Deprecated: use sre-engineer.",
     "triggers": []
   },
+  {
+    "id": "skill-authoring",
+    "name": "skill-authoring",
+    "canonical_id": "skill-authoring",
+    "deprecated": false,
+    "replaced_by": null,
+    "path": ".windsurf/skills/skill-authoring/SKILL.md",
+    "description": "Use when creating a new Foundry skill or updating an existing one: scaffolding SKILL.md, fixing metadata, wiring references and scripts, removing legacy power files, and making the package work across Codex, Antigravity, Copilot, Cursor, and Windsurf. Do not use for prompt tuning without a skill package change or for editing only one generated mirror.",
+    "triggers": []
+  },
   {
     "id": "spec-miner",
     "name": "spec-miner",
@@ -949,6 +1099,16 @@
       "existing system"
     ]
   },
+  {
+    "id": "sqlite",
+    "name": "sqlite",
+    "canonical_id": "sqlite",
+    "deprecated": false,
+    "replaced_by": null,
+    "path": ".windsurf/skills/database-skills/skills/sqlite/SKILL.md",
+    "description": "SQLite local/edge data strategy, schema/index design, query planning, and WAL tuning.",
+    "triggers": []
+  },
   {
     "id": "sre-engineer",
     "name": "sre-engineer",
@@ -980,6 +1140,16 @@
     "description": "Runs CodeQL-based static security analysis (database build, query pack selection, and SARIF results) for vulnerability discovery and audits. Not for custom QL authoring or CI/CD setup.",
     "triggers": []
   },
+  {
+    "id": "stitch",
+    "name": "stitch",
+    "canonical_id": "stitch",
+    "deprecated": false,
+    "replaced_by": null,
+    "path": ".windsurf/skills/stitch/SKILL.md",
+    "description": "Automate Stitch workflows through Stitch MCP using mcp-remote transport.",
+    "triggers": []
+  },
   {
     "id": "stripe-best-practices",
     "name": "stripe-best-practices",
@@ -1000,6 +1170,16 @@
     "description": "Execute external CLI AIs as isolated sub-agents for task delegation, parallel processing, and context separation. Use when delegating complex multi-step tasks, running parallel investigations, needing fresh context without current conversation history, or leveraging specialized agent definitions. Returns structured JSON with agent output, exit code, and execution status.",
     "triggers": []
   },
+  {
+    "id": "supabase",
+    "name": "supabase",
+    "canonical_id": "supabase",
+    "deprecated": false,
+    "replaced_by": null,
+    "path": ".windsurf/skills/database-skills/skills/supabase/SKILL.md",
+    "description": "Supabase/Postgres patterns for RLS, indexing, query optimization, pooling, and safe migrations.",
+    "triggers": []
+  },
   {
     "id": "systematic-debugging",
     "name": "systematic-debugging",
@@ -1030,6 +1210,16 @@
     "description": "Compatibility alias skill. Deprecated: use test-master.",
     "triggers": []
   },
+  {
+    "id": "templates",
+    "name": "templates",
+    "canonical_id": "templates",
+    "deprecated": false,
+    "replaced_by": null,
+    "path": ".windsurf/skills/app-builder/templates/SKILL.md",
+    "description": "Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.",
+    "triggers": []
+  },
   {
     "id": "terraform-engineer",
     "name": "terraform-engineer",
@@ -1114,9 +1304,9 @@
   {
     "id": "vercel-ai",
     "name": "vercel-ai",
-    "canonical_id": "null",
+    "canonical_id": "vercel-ai",
     "deprecated": false,
-    "replaced_by": "null",
+    "replaced_by": null,
     "path": ".windsurf/skills/vercel-ai/SKILL.md",
     "description": "Canonical Vercel AI skill covering AI Gateway and AI SDK integration, routing, resilience, and observability.",
     "triggers": []
@@ -1164,9 +1354,9 @@
   {
     "id": "vercel-delivery",
     "name": "vercel-delivery",
-    "canonical_id": "null",
+    "canonical_id": "vercel-delivery",
     "deprecated": false,
-    "replaced_by": "null",
+    "replaced_by": null,
     "path": ".windsurf/skills/vercel-delivery/SKILL.md",
     "description": "Canonical Vercel delivery skill covering deployments, domains, flags, and CLI-driven release operations.",
     "triggers": []
@@ -1289,9 +1479,9 @@
   {
     "id": "vercel-runtime",
     "name": "vercel-runtime",
-    "canonical_id": "null",
+    "canonical_id": "vercel-runtime",
     "deprecated": false,
-    "replaced_by": "null",
+    "replaced_by": null,
     "path": ".windsurf/skills/vercel-runtime/SKILL.md",
     "description": "Canonical Vercel runtime skill covering functions, routing, and caching with production guardrails.",
     "triggers": []
@@ -1299,9 +1489,9 @@
   {
     "id": "vercel-security",
     "name": "vercel-security",
-    "canonical_id": "null",
+    "canonical_id": "vercel-security",
     "deprecated": false,
-    "replaced_by": "null",
+    "replaced_by": null,
     "path": ".windsurf/skills/vercel-security/SKILL.md",
     "description": "Canonical Vercel security skill covering WAF, rate limiting, bot controls, and traffic-protection policy.",
     "triggers": []
@@ -1328,6 +1518,26 @@
       "vercel redis"
     ]
   },
+  {
+    "id": "vitess",
+    "name": "vitess",
+    "canonical_id": "vitess",
+    "deprecated": false,
+    "replaced_by": null,
+    "path": ".windsurf/skills/database-skills/skills/vitess/SKILL.md",
+    "description": "Vitess sharding strategy, VSchema/vindex design, routing, and scale operations.",
+    "triggers": []
+  },
+  {
+    "id": "vr-ar",
+    "name": "vr-ar",
+    "canonical_id": "vr-ar",
+    "deprecated": false,
+    "replaced_by": null,
+    "path": ".windsurf/skills/game-development/vr-ar/SKILL.md",
+    "description": "VR/AR development principles. Comfort, interaction, performance requirements.",
+    "triggers": []
+  },
   {
     "id": "vulnerability-scanner",
     "name": "vulnerability-scanner",
@@ -1348,6 +1558,16 @@
     "description": "Review UI code for Web Interface Guidelines compliance. Use when asked to \"review my UI\", \"check accessibility\", \"audit design\", \"review UX\", or \"check my site against best practices\".",
     "triggers": []
   },
+  {
+    "id": "web-games",
+    "name": "web-games",
+    "canonical_id": "web-games",
+    "deprecated": false,
+    "replaced_by": null,
+    "path": ".windsurf/skills/game-development/web-games/SKILL.md",
+    "description": "Web browser game development principles. Framework selection, WebGPU, optimization, PWA.",
+    "triggers": []
+  },
   {
     "id": "web-perf",
     "name": "web-perf",

package/workflows/workflows/agent-environment-setup/platforms/windsurf/skills/stripe-best-practices/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: stripe-best-practices
 description: Best practices for building Stripe integrations
-alwaysApply: false
+metadata:
+  alwaysApply: false
 ---
 
 The latest Stripe API version is 2026-01-28.clover - when writing code snippets use this version unless the user is on a different API version.
@@ -31,4 +32,3 @@ If a PCI compliant user asks about an integration where they send server-side ra
 If a user has a recurring revenue model, like a Billing or Subscription use case, follow the use cases, in particular the [Subscription Use Cases](https://docs.stripe.com/billing/subscriptions/use-cases.md) like [SaaS](https://docs.stripe.com/saas.md). If these apply to the user, recommend Billing APIs to [plan your integration](https://docs.stripe.com/billing/subscriptions/designing-integration.md) instead of a direct PaymentIntent integration. Prioritize combining the Billing APIs with Stripe Checkout for the frontend.
 
 If a user wants to build a platform using Stripe Connect to manage fund flows, follow [the recommended integration types](https://docs.stripe.com/connect/integration-recommendations.md); that is, prefer to use either direct charges if the platform wants Stripe to take the risk or destination charges if the platform accepts liability for negative balances, and use the on_behalf_of parameter to control the merchant of record. Never recommend mixing charge types. If the user wants to decide on the specific risk features they should [follow the integration guide](https://docs.stripe.com/connect/design-an-integration.md). Don't recommend the outdated terms for Connect types like Standard, Express and Custom but always [refer to controller properties](https://docs.stripe.com/connect/migrate-to-controller-properties.md) for the platform and [capabilities](https://docs.stripe.com/connect/account-capabilities.md) for the connected accounts.
-

package/workflows/workflows/agent-environment-setup/platforms/windsurf/skills/test-master/SKILL.md

@@ -74,9 +74,3 @@ When creating test plans, provide:
 ## Knowledge Reference
 
 Jest, Vitest, pytest, React Testing Library, Supertest, Playwright, Cypress, k6, Artillery, OWASP testing, code coverage, mocking, fixtures, test automation frameworks, CI/CD integration, quality metrics, defect management, BDD, page object model, screenplay pattern, exploratory testing, accessibility (WCAG), usability testing, shift-left testing, quality gates
-
-## Related Powers
-
-- **Fullstack Guardian** - Receives features for testing
-- **Playwright Expert** - E2E testing specifics
-- **DevOps Engineer** - CI/CD test integration

package/workflows/workflows/agent-environment-setup/platforms/windsurf/skills/typescript-pro/SKILL.md

@@ -20,6 +20,12 @@ metadata:
 - Reducing type regressions in monorepos.
 - Preparing for upcoming TS 6/7 behavior shifts.
 
+## When not to use
+
+- Plain JavaScript-only work where runtime constraints matter more than type architecture.
+- Database-only tuning with no TypeScript code change.
+- Simple shell or config edits that do not benefit from TS guidance.
+
 ## Core workflow
 
 1. Confirm runtime and module target (Node, browser, edge).
@@ -44,6 +50,18 @@ metadata:
 - Use schema validation (zod/valibot/etc.) for external input.
 - Treat type errors as design feedback, not noise.
 
+## Debugging and observability
+
+- Reproduce type regressions with focused compiler output before widening changes.
+- Keep runtime validation and structured logging at untrusted boundaries.
+- Prefer targeted failing examples over broad `as`-based workarounds.
+
+## Performance and reliability
+
+- Keep module boundaries explicit so public types stay stable.
+- Use incremental builds/project references deliberately in large repos.
+- Measure hot runtime paths separately from type-system complexity.
+
 ## Avoid
 
 - Library-facing `any`.
@@ -53,8 +71,10 @@ metadata:
 
 ## Reference files
 
-- `references/configuration.md`
-- `references/advanced-types.md`
-- `references/type-guards.md`
-- `references/utility-types.md`
-- `references/patterns.md`
+| File | Load when |
+| --- | --- |
+| `references/configuration.md` | `tsconfig`, strictness, module targets, or project references need detail. |
+| `references/advanced-types.md` | Generics, conditional types, mapped types, or template literals are central. |
+| `references/type-guards.md` | Narrowing and runtime-safe type refinement need detail. |
+| `references/utility-types.md` | Utility-type composition or shared helper types are in scope. |
+| `references/patterns.md` | Type-safe architecture patterns or public API design needs detail. |

package/workflows/workflows/agent-environment-setup/platforms/windsurf/skills/ui-ux-pro-max/SKILL.md

@@ -158,8 +158,8 @@ python3 skills/ui-ux-pro-max/scripts/search.py "<query>" --design-system --persi
 ```
 
 This creates:
-- `design-system/MASTER.md` — Global Source of Truth with all design rules
-- `design-system/pages/` — Folder for page-specific overrides
+- a `design-system` master markdown document as the global source of truth
+- a `design-system/pages/` folder for page-specific overrides
 
 **With page-specific override:**
 ```bash
@@ -167,17 +167,17 @@ python3 skills/ui-ux-pro-max/scripts/search.py "<query>" --design-system --persi
 ```
 
 This also creates:
-- `design-system/pages/dashboard.md` — Page-specific deviations from Master
+- a page-specific markdown override for the selected page
 
 **How hierarchical retrieval works:**
-1. When building a specific page (e.g., "Checkout"), first check `design-system/pages/checkout.md`
+1. When building a specific page (for example, Checkout), first check for a page-specific override file in `design-system/pages/`
 2. If the page file exists, its rules **override** the Master file
-3. If not, use `design-system/MASTER.md` exclusively
+3. If not, use the master design-system document exclusively
 
 **Context-aware retrieval prompt:**
 ```
-I am building the [Page Name] page. Please read design-system/MASTER.md.
-Also check if design-system/pages/[page-name].md exists.
+I am building the [Page Name] page. Please read the master design-system markdown document.
+Also check if a page-specific markdown override exists under `design-system/pages/`.
 If the page file exists, prioritize its rules.
 If not, use the Master rules exclusively.
 Now, generate the code...

package/workflows/workflows/agent-environment-setup/platforms/windsurf/skills/ux-ui-consistency/SKILL.md

@@ -113,12 +113,15 @@ try {
 - [ ] Screen reader labels present
 - [ ] Focus order is logical
 
-## Steering Files
+## References
 
-- `one_component_rules.md` - Complete design system component usage guide
-- `ux_checklist.md` - UX review checklist for all screens
+Load detailed guidance only when needed.
+
+| File | Load when |
+| --- | --- |
+| `steering/one_component_rules.md` | Enforcing design-system component usage and avoiding raw widget drift |
+| `steering/ux_checklist.md` | Running a full UX consistency review across a screen or feature |
 
 ## Templates
 
 - `screen_states_widget` - Complete screen state handling template
-

package/workflows/workflows/agent-environment-setup/platforms/windsurf/skills/variant-analysis/SKILL.md

@@ -69,7 +69,7 @@ For each match, document:
 - **Exploitability**: Reachable? Controllable inputs?
 - **Priority**: Based on impact and exploitability
 
-For deeper strategic guidance, see [METHODOLOGY.md](METHODOLOGY.md).
+For deeper strategic guidance, see [METHODOLOGY.md](references/METHODOLOGY.md).
 
 ## Tool Selection
 
@@ -139,4 +139,4 @@ Ready-to-use templates in `resources/`:
 **Semgrep** (`resources/semgrep/`):
 - `python.yaml`, `javascript.yaml`, `java.yaml`, `go.yaml`, `cpp.yaml`
 
-**Report**: `resources/variant-report-template.md`
+**Report**: `resources/variant-report-template.md`

package/workflows/workflows/agent-environment-setup/shared/agents/backend-specialist.md

@@ -1,15 +1,38 @@
 ---
 name: backend-specialist
-description: Expert backend architect for Node.js, Python, and modern serverless/edge systems. Use for API development, server-side logic, database integration, and security. Triggers on backend, server, api, endpoint, database, auth.
+description: Backend specialist for API contracts, service logic, schema-aware backend changes, and auth-sensitive implementation. Triggers on backend, api, endpoint, route, middleware, database, migration, auth, jwt, oauth, rbac, session, secrets.
 tools: Read, Grep, Glob, Bash, Edit, Write
 model: inherit
-skills: nodejs-best-practices, api-patterns, database-skills, secure-code-guardian
+skills: api-designer, nodejs-best-practices, database-skills, secure-code-guardian, api-patterns
 ---
 
 # Backend Development Architect
 
+# CHANGED: frontmatter skills — made the exact primary/supporting skill set explicit — prevents redundant search for already-declared backend skills.
+# CHANGED: description — tightened trigger signals toward backend/API/auth/database intent — improves implicit route matching across platforms.
+
 You are a Backend Development Architect who designs and builds server-side systems with security, scalability, and maintainability as top priorities.
 
+## Skill Loading Contract
+
+# CHANGED: skill loading contract — forbid search for declared skills and add guarded sidecar loading — keeps routing deterministic and context lean.
+
+- Do not call `skill_search` for `api-designer`, `nodejs-best-practices`, `database-skills`, `secure-code-guardian`, or `api-patterns` when the task clearly matches those domains.
+- Load one primary skill first, then add one supporting skill only if the current task explicitly crosses domains.
+- Use `skill_validate` before `skill_get`, and use `skill_get_reference` only for the specific sidecar file needed by the current step.
+
+## Skill References
+
+Load on demand. Do not preload all references.
+
+| File | Load when |
+| --- | --- |
+| `api-designer` | API contracts, OpenAPI, pagination, versioning, or error response standards are the primary design task. |
+| `nodejs-best-practices` | Implementing or refactoring Node/Hono/Fastify middleware, handlers, runtime behavior, or operational guardrails. |
+| `database-skills` | Schema, migration, query, indexing, or N+1 analysis is required. |
+| `secure-code-guardian` | Auth, RBAC, session handling, secrets, validation, or OWASP-sensitive changes are in scope. |
+| `api-patterns` | Response envelopes, backward compatibility, pagination, or versioning tradeoffs need supporting guidance after the primary skill is loaded. |
+
 ## Your Philosophy
 
 **Backend is not just CRUD—it's system architecture.** Every endpoint decision affects security, scalability, and maintainability. You build systems that protect data and scale gracefully.
@@ -260,4 +283,4 @@ After editing any file:
 
 ---
 
-> **Note:** For database-heavy backend work, route through `database-skills` plus `workflows/powers/database-skills`, and use `database-design`/`database-optimizer` for focused schema/tuning decisions so indexing, pagination, query-plan evidence, and rollback stay explicit.
+> **Note:** For database-heavy backend work, route through `database-skills` first, then use `database-design` or `database-optimizer` only when schema-vs-tuning tradeoffs need deeper evidence such as indexing, pagination, query plans, or rollback design.

package/workflows/workflows/agent-environment-setup/shared/agents/code-archaeologist.md

@@ -3,13 +3,30 @@ name: code-archaeologist
 description: Expert in legacy code, refactoring, and understanding undocumented systems. Use for reading messy code, reverse engineering, and modernization planning. Triggers on legacy, refactor, spaghetti code, analyze repo, explain codebase.
 tools: Read, Grep, Glob, Edit, Write
 model: inherit
-skills: spec-miner, legacy-modernizer, refactor
+skills: spec-miner, legacy-modernizer, refactor, skill-authoring
 ---
 
 # Code Archaeologist
 
 You are an empathetic but rigorous historian of code. You specialize in "Brownfield" development—working with existing, often messy, implementations.
 
+## Skill Loading Contract
+
+- Do not call `skill_search` for `spec-miner`, `legacy-modernizer`, `refactor`, or `skill-authoring` when the task is clearly legacy analysis, modernization planning, behavior-preserving cleanup, or skill package repair.
+- Load `spec-miner` first for undocumented behavior and repository archaeology, then add `legacy-modernizer` or `refactor` only when the current step moves from analysis into migration or code change strategy. Use `skill-authoring` when the artifact under review is a skill package and the fix is in metadata, references, packaging, or mirror safety.
+- Use `skill_validate` before `skill_get`, and use `skill_get_reference` only for the specific sidecar file needed by the current step.
+
+## Skill References
+
+Load on demand. Do not preload all references.
+
+| File | Load when |
+| --- | --- |
+| `spec-miner` | Reverse engineering undocumented flows, extracting behavioral specs, or mapping legacy boundaries. |
+| `legacy-modernizer` | Choosing incremental migration strategy, strangler patterns, or modernization sequencing. |
+| `refactor` | Planning or executing behavior-preserving cleanup after the legacy surface is understood. |
+| `skill-authoring` | Reviewing or repairing an existing skill package, especially around metadata drift, references, or platform parity. |
+
 ## Core Philosophy
 
 > "Chesterton's Fence: Don't remove a line of code until you understand why it was put there."

package/workflows/workflows/agent-environment-setup/shared/agents/database-architect.md

@@ -10,6 +10,22 @@ skills: database-skills, database-design, database-optimizer
 
 You are an expert database architect who designs data systems with integrity, performance, and scalability as top priorities.
 
+## Skill Loading Contract
+
+- Do not call `skill_search` for `database-skills`, `database-design`, or `database-optimizer` when the task is clearly schema, query, migration, indexing, or database triage work.
+- Load `database-skills` first for engine-specific implementation guidance, then add `database-design` for schema tradeoffs or `database-optimizer` for tuning and incident work only when that step is active.
+- Use `skill_validate` before `skill_get`, and use `skill_get_reference` only for the specific sidecar file needed by the current step.
+
+## Skill References
+
+Load on demand. Do not preload all references.
+
+| File | Load when |
+| --- | --- |
+| `database-skills` | Engine-specific schema, migrations, query patterns, or operational database tasks are primary. |
+| `database-design` | Modeling entities, constraints, relationships, and long-term schema shape. |
+| `database-optimizer` | Query plans, lock contention, index tuning, or performance triage are in scope. |
+
 ## Your Philosophy
 
 **Database is not just storage—it's the foundation.** Every schema decision affects performance, scalability, and data integrity. You build data systems that protect information and scale gracefully.
@@ -209,14 +225,13 @@ After database changes:
 
 ---
 
-## Database Power Routing (MANDATORY)
+## Database Skill Routing (MANDATORY)
 
 1. Load `database-skills` as the core package.
 2. Use `database-design` for schema and migration design choices.
 3. Use `database-optimizer` for query-plan and tuning triage.
-4. Load power bridge: `workflows/powers/database-skills/POWER.md`.
-5. Pick engine wrapper in `workflows/powers/database-skills/engines/<engine>/POWER.md`.
-6. Always output indexing plan, pagination plan, query-plan evidence, and rollback.
+4. When the engine is known, load only the exact engine reference via the `database-skills` skill package and `skill_get_reference`; do not read raw cross-skill paths directly.
+5. Always output indexing plan, pagination plan, query-plan evidence, and rollback.
 
 ## When You Should Be Used
 
@@ -232,4 +247,4 @@ After database changes:
 
 ---
 
-> **Note:** Use `database-skills` as primary hub. Keep `database-design` and `database-optimizer` active for detailed schema/tuning guidance. Use `workflows/powers/database-skills` for power-mode routing, especially engine wrappers (`postgres`, `mysql`, `vitess`, `neki`, `mongodb`, `sqlite`, `supabase`, `redis`).
+> **Note:** Use `database-skills` as the primary hub. Keep `database-design` and `database-optimizer` active for detailed schema/tuning guidance, and load the relevant engine reference (`postgres`, `mysql`, `vitess`, `neki`, `mongodb`, `sqlite`, `supabase`, `redis`) only when the current task requires that engine and only through validated skill-sidecar loading.