@cubis/foundry 0.3.63 → 0.3.64

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

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

@@ -2,7 +2,6 @@
 name: spec-miner
 description: Use when understanding legacy or undocumented systems, creating documentation for existing code, or extracting specifications from implementations. Invoke for legacy analysis, code archaeology, undocumented features.
 license: MIT
-allowed-tools: Read, Grep, Glob, Bash
 metadata:
   author: https://github.com/Jeffallan
   version: "1.0.0"
@@ -13,7 +12,6 @@ metadata:
   output-format: document
   related-skills: feature-forge, fullstack-guardian, architecture-designer
 ---
-
 # Spec Miner
 
 Reverse-engineering specialist who extracts specifications from existing codebases.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/sre-engineer/SKILL.md

@@ -12,7 +12,6 @@ metadata:
   output-format: code
   related-skills: devops-engineer, cloud-architect, kubernetes-specialist
 ---
-
 # SRE Engineer
 
 Senior Site Reliability Engineer with expertise in building highly reliable, scalable systems through SLI/SLO management, error budgets, capacity planning, and automation.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/static-analysis/SKILL.md

@@ -1,19 +1,7 @@
 ---
 name: static-analysis
 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.
-allowed-tools:
-  - Bash
-  - Read
-  - Write
-  - Glob
-  - Grep
-  - AskUserQuestion
-  - Task
-  - TaskCreate
-  - TaskList
-  - TaskUpdate
 ---
-
 # CodeQL Analysis
 
 Supported languages: Python, JavaScript/TypeScript, Go, Java/Kotlin, C/C++, C#, Ruby, Swift.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/stitch/SKILL.md

@@ -2,7 +2,6 @@
 name: stitch
 description: Automate Stitch workflows through Stitch MCP using mcp-remote transport.
 ---
-
 # Stitch MCP
 
 Use this skill when you need to call Stitch tools through MCP passthrough.

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

@@ -1,9 +1,9 @@
 ---
 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.
 
 When designing an integration, always prefer the documentation in [Stripe's Integration Options doc](https://docs.stripe.com/payments/payment-methods/integration-options.md)
@@ -31,4 +31,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/copilot/skills/sub-agents/SKILL.md

@@ -1,9 +1,7 @@
 ---
 name: sub-agents
 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.
-allowed-tools: Bash Read
 ---
-
 # Sub-Agents - External CLI AI Task Delegation
 
 Spawns external CLI AIs (claude, cursor-agent, codex, gemini) as isolated sub-agents with dedicated context.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/systematic-debugging/SKILL.md

@@ -1,9 +1,7 @@
 ---
 name: systematic-debugging
 description: 4-phase systematic debugging methodology with root cause analysis and evidence-based verification. Use when debugging complex issues.
-allowed-tools: Read, Glob, Grep
 ---
-
 # Systematic Debugging
 
 > Source: obra/superpowers

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/tailwind-patterns/SKILL.md

@@ -1,9 +1,7 @@
 ---
 name: tailwind-patterns
 description: Tailwind CSS v4 principles. CSS-first configuration, container queries, modern patterns, design token architecture.
-allowed-tools: Read, Write, Edit, Glob, Grep
 ---
-
 # Tailwind CSS Patterns (v4 - 2025)
 
 > Modern utility-first CSS with CSS-native configuration.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/tdd-workflow/SKILL.md

@@ -6,7 +6,6 @@ metadata:
   replaced_by: test-master
   removal_target: v0.6.0
 ---
-
 # Tdd Workflow
 
 ## Compatibility Alias

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/terraform-engineer/SKILL.md

@@ -12,7 +12,6 @@ metadata:
   output-format: code
   related-skills: cloud-architect, devops-engineer, kubernetes-specialist
 ---
-
 # Terraform Engineer
 
 Senior Terraform engineer specializing in infrastructure as code across AWS, Azure, and GCP with expertise in modular design, state management, and production-grade patterns.

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

@@ -2,8 +2,6 @@
 name: "test-master"
 description: "Use when writing tests, creating test strategies, or building automation frameworks. Invoke for unit tests, integration tests, E2E, coverage analysis, performance testing, security testing."
 ---
-
-
 # Test Master
 
 ## Overview
@@ -74,9 +72,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/copilot/skills/testing-patterns/SKILL.md

@@ -6,7 +6,6 @@ metadata:
   replaced_by: test-master
   removal_target: v0.6.0
 ---
-
 # Testing Patterns
 
 ## Compatibility Alias

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

@@ -10,7 +10,6 @@ metadata:
   baseline: "TypeScript 5.9 stable"
   transition: "TypeScript 6 compatibility prep"
 ---
-
 # TypeScript Pro
 
 ## When to use
@@ -20,6 +19,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 +49,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 +70,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/copilot/skills/ui-ux-pro-max/SKILL.md

@@ -2,7 +2,6 @@
 name: ui-ux-pro-max
 description: "UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples."
 ---
-
 # UI/UX Pro Max - Design Intelligence
 
 Comprehensive design guide for web and mobile applications. Contains 50+ styles, 97 color palettes, 57 font pairings, 99 UX guidelines, and 25 chart types across 9 technology stacks. Searchable database with priority-based recommendations.
@@ -158,8 +157,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 +166,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...