@cubis/foundry 0.3.63 → 0.3.65

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

@@ -1,4 +1,24 @@
 [
+  {
+    "id": "2d-games",
+    "name": "2d-games",
+    "canonical_id": "2d-games",
+    "deprecated": false,
+    "replaced_by": null,
+    "path": ".cursor/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": ".cursor/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": ".cursor/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": ".cursor/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": ".cursor/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": ".cursor/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": ".cursor/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": ".cursor/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": ".cursor/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": ".cursor/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": ".cursor/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": ".cursor/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": ".cursor/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": ".cursor/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": ".cursor/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": ".cursor/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": ".cursor/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": ".cursor/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": ".cursor/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": ".cursor/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": ".cursor/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": ".cursor/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": ".cursor/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": ".cursor/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": ".cursor/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": ".cursor/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": ".cursor/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": ".cursor/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/cursor/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/cursor/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/cursor/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/cursor/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/cursor/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/cursor/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/platforms/windsurf/skills/accessibility/SKILL.md

@@ -91,13 +91,15 @@ SizedBox(
 4. **Color Contrast**: Text must have 4.5:1 contrast ratio (3:1 for large text)
 5. **Screen Reader**: Test with TalkBack (Android) and VoiceOver (iOS)
 
-## Steering Files
+## References
 
-Load detailed guidance:
-- `a11y_checklist.md` - Complete accessibility checklist for reviews
+Load detailed guidance only when needed.
+
+| File | Load when |
+| --- | --- |
+| `references/a11y_checklist.md` | Running an accessibility review or validating a widget/screen against the full checklist |
 
 ## Templates
 
 - `focus_form` - Form with proper focus management
 - `semantics_icon_button` - Icon button with semantic labels
-

package/workflows/workflows/agent-environment-setup/platforms/windsurf/skills/api-designer/SKILL.md

@@ -1,11 +1,15 @@
 ---
 name: "api-designer"
-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."
 ---
 
 
 # API Designer
 
+# CHANGED: description — added a sharper trigger boundary and explicit non-goals — reduces false-positive invocation.
+# CHANGED: references section — normalized to explicit Load When guidance with platform-safe relative paths — prevents speculative sidecar loading.
+# CHANGED: related powers cleanup — removed power-era section — keeps this skill canonical and platform-safe.
+
 ## Overview
 
 Senior API architect with expertise in designing scalable, developer-friendly REST and GraphQL APIs with comprehensive OpenAPI specifications.
@@ -25,6 +29,12 @@ You are a senior API designer with 10+ years of experience creating intuitive, s
 - Planning authentication flows
 - Documenting API contracts
 
+## When Not to Use This Skill
+
+- Pure database schema, indexing, or migration work without an API contract change
+- Framework-only implementation tasks such as wiring handlers, middleware, or DI containers
+- Internal refactors that do not change request/response contracts
+
 ## Core Workflow
 
 1. **Analyze domain** - Understand business requirements, data models, client needs
@@ -33,7 +43,7 @@ You are a senior API designer with 10+ years of experience creating intuitive, s
 4. **Specify contract** - Create OpenAPI 3.1 spec with complete documentation
 5. **Plan evolution** - Design versioning, deprecation, backward compatibility
 
-## Available Steering Files
+## References
 
 Load detailed guidance on-demand:
 
@@ -84,11 +94,3 @@ When designing APIs, provide:
 ## Knowledge Reference
 
 REST architecture, OpenAPI 3.1, GraphQL, HTTP semantics, JSON:API, HATEOAS, OAuth 2.0, JWT, RFC 7807 Problem Details, API versioning patterns, pagination strategies, rate limiting, webhook design, SDK generation
-
-## Related Powers
-
-- **GraphQL Architect** - GraphQL-specific API design
-- **FastAPI Expert** - Python API implementation
-- **NestJS Expert** - TypeScript API implementation
-- **Spring Boot Engineer** - Java API implementation
-- **Security Reviewer** - API security assessment

package/workflows/workflows/agent-environment-setup/platforms/windsurf/skills/api-patterns/SKILL.md

@@ -19,16 +19,16 @@ allowed-tools: Read, Write, Edit, Glob, Grep
 
 | File | Description | When to Read |
 |------|-------------|--------------|
-| `api-style.md` | REST vs GraphQL vs tRPC decision tree | Choosing API type |
-| `rest.md` | Resource naming, HTTP methods, status codes | Designing REST API |
-| `response.md` | Envelope pattern, error format, pagination | Response structure |
-| `graphql.md` | Schema design, when to use, security | Considering GraphQL |
-| `trpc.md` | TypeScript monorepo, type safety | TS fullstack projects |
-| `versioning.md` | URI/Header/Query versioning | API evolution planning |
-| `auth.md` | JWT, OAuth, Passkey, API Keys | Auth pattern selection |
-| `rate-limiting.md` | Token bucket, sliding window | API protection |
-| `documentation.md` | OpenAPI/Swagger best practices | Documentation |
-| `security-testing.md` | OWASP API Top 10, auth/authz testing | Security audits |
+| `references/api-style.md` | REST vs GraphQL vs tRPC decision tree | Choosing API type |
+| `references/rest.md` | Resource naming, HTTP methods, status codes | Designing REST API |
+| `references/response.md` | Envelope pattern, error format, pagination | Response structure |
+| `references/graphql.md` | Schema design, when to use, security | Considering GraphQL |
+| `references/trpc.md` | TypeScript monorepo, type safety | TS fullstack projects |
+| `references/versioning.md` | URI/Header/Query versioning | API evolution planning |
+| `references/auth.md` | JWT, OAuth, Passkey, API Keys | Auth pattern selection |
+| `references/rate-limiting.md` | Token bucket, sliding window | API protection |
+| `references/documentation.md` | OpenAPI/Swagger best practices | Documentation |
+| `references/security-testing.md` | OWASP API Top 10, auth/authz testing | Security audits |
 
 ---
 
@@ -78,4 +78,3 @@ Before designing an API:
 | Script | Purpose | Command |
 |--------|---------|---------|
 | `scripts/api_validator.py` | API endpoint validation | `python scripts/api_validator.py <project_path>` |
-