@cubis/foundry 0.3.63 → 0.3.64

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

@@ -1,9 +1,7 @@
 ---
 name: frontend-design
 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.
-allowed-tools: Read, Write, Edit, Glob, Grep, Bash
 ---
-
 # Frontend Design System
 
 > **Philosophy:** Every pixel has purpose. Restraint is luxury. User psychology drives decisions.
@@ -17,13 +15,13 @@ allowed-tools: Read, Write, Edit, Glob, Grep, Bash
 
 | File | Status | When to Read |
 |------|--------|--------------|
-| [ux-psychology.md](ux-psychology.md) | 🔴 **REQUIRED** | Always read first! |
-| [color-system.md](color-system.md) | ⚪ Optional | Color/palette decisions |
-| [typography-system.md](typography-system.md) | ⚪ Optional | Font selection/pairing |
-| [visual-effects.md](visual-effects.md) | ⚪ Optional | Glassmorphism, shadows, gradients |
-| [animation-guide.md](animation-guide.md) | ⚪ Optional | Animation needed |
-| [motion-graphics.md](motion-graphics.md) | ⚪ Optional | Lottie, GSAP, 3D |
-| [decision-trees.md](decision-trees.md) | ⚪ Optional | Context templates |
+| [ux-psychology.md](references/ux-psychology.md) | 🔴 **REQUIRED** | Always read first! |
+| [color-system.md](references/color-system.md) | ⚪ Optional | Color/palette decisions |
+| [typography-system.md](references/typography-system.md) | ⚪ Optional | Font selection/pairing |
+| [visual-effects.md](references/visual-effects.md) | ⚪ Optional | Glassmorphism, shadows, gradients |
+| [animation-guide.md](references/animation-guide.md) | ⚪ Optional | Animation needed |
+| [motion-graphics.md](references/motion-graphics.md) | ⚪ Optional | Lottie, GSAP, 3D |
+| [decision-trees.md](references/decision-trees.md) | ⚪ Optional | Context templates |
 
 > 🔴 **ux-psychology.md = ALWAYS READ. Others = only if relevant.**
 
@@ -188,7 +186,7 @@ All spacing and sizing in multiples of 8:
 3. **Light or dark mode?** (sets foundation)
 4. **ASK USER** if not specified
 
-For detailed color theory: [color-system.md](color-system.md)
+For detailed color theory: [color-system.md](references/color-system.md)
 
 ---
 
@@ -219,7 +217,7 @@ Contrast + Harmony:
 - **Contrast**: Check WCAG requirements
 - **Size**: 16px+ for body on web
 
-For detailed typography: [typography-system.md](typography-system.md)
+For detailed typography: [typography-system.md](references/typography-system.md)
 
 ---
 
@@ -256,7 +254,7 @@ Harmonious gradients:
 └── VARY from project to project radically
 ```
 
-For complete effects guide: [visual-effects.md](visual-effects.md)
+For complete effects guide: [visual-effects.md](references/visual-effects.md)
 
 ---
 
@@ -287,7 +285,7 @@ Duration based on:
 - Respect reduced-motion preference
 - Test on low-end devices
 
-For animation patterns: [animation-guide.md](animation-guide.md), for advanced: [motion-graphics.md](motion-graphics.md)
+For animation patterns: [animation-guide.md](references/animation-guide.md), for advanced: [motion-graphics.md](references/motion-graphics.md)
 
 ---
 
@@ -383,13 +381,13 @@ For EVERY design task:
 
 For deeper guidance on specific areas:
 
-- [color-system.md](color-system.md) - Color theory and selection process
-- [typography-system.md](typography-system.md) - Font pairing and scale decisions
-- [visual-effects.md](visual-effects.md) - Effects principles and techniques
-- [animation-guide.md](animation-guide.md) - Motion design principles
-- [motion-graphics.md](motion-graphics.md) - Advanced: Lottie, GSAP, SVG, 3D, Particles
-- [decision-trees.md](decision-trees.md) - Context-specific templates
-- [ux-psychology.md](ux-psychology.md) - User psychology deep dive
+- [color-system.md](references/color-system.md) - Color theory and selection process
+- [typography-system.md](references/typography-system.md) - Font pairing and scale decisions
+- [visual-effects.md](references/visual-effects.md) - Effects principles and techniques
+- [animation-guide.md](references/animation-guide.md) - Motion design principles
+- [motion-graphics.md](references/motion-graphics.md) - Advanced: Lottie, GSAP, SVG, 3D, Particles
+- [decision-trees.md](references/decision-trees.md) - Context-specific templates
+- [ux-psychology.md](references/ux-psychology.md) - User psychology deep dive
 
 ---
 

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/game-development/2d-games/SKILL.md

@@ -1,9 +1,7 @@
 ---
 name: 2d-games
 description: 2D game development principles. Sprites, tilemaps, physics, camera.
-allowed-tools: Read, Write, Edit, Glob, Grep
 ---
-
 # 2D Game Development
 
 > Principles for 2D game systems.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/game-development/3d-games/SKILL.md

@@ -1,9 +1,7 @@
 ---
 name: 3d-games
 description: 3D game development principles. Rendering, shaders, physics, cameras.
-allowed-tools: Read, Write, Edit, Glob, Grep
 ---
-
 # 3D Game Development
 
 > Principles for 3D game systems.

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

@@ -1,9 +1,7 @@
 ---
 name: game-development
 description: Game development orchestrator. Routes to platform-specific skills based on project needs.
-allowed-tools: Read, Write, Edit, Glob, Grep, Bash
 ---
-
 # Game Development
 
 > **Orchestrator skill** that provides core principles and routes to specialized sub-skills.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/game-development/game-art/SKILL.md

@@ -1,9 +1,7 @@
 ---
 name: game-art
 description: Game art principles. Visual style selection, asset pipeline, animation workflow.
-allowed-tools: Read, Glob, Grep
 ---
-
 # Game Art Principles
 
 > Visual design thinking for games - style selection, asset pipelines, and art direction.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/game-development/game-audio/SKILL.md

@@ -1,9 +1,7 @@
 ---
 name: game-audio
 description: Game audio principles. Sound design, music integration, adaptive audio systems.
-allowed-tools: Read, Glob, Grep
 ---
-
 # Game Audio Principles
 
 > Sound design and music integration for immersive game experiences.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/game-development/game-design/SKILL.md

@@ -1,9 +1,7 @@
 ---
 name: game-design
 description: Game design principles. GDD structure, balancing, player psychology, progression.
-allowed-tools: Read, Glob, Grep
 ---
-
 # Game Design Principles
 
 > Design thinking for engaging games.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/game-development/mobile-games/SKILL.md

@@ -1,9 +1,7 @@
 ---
 name: mobile-games
 description: Mobile game development principles. Touch input, battery, performance, app stores.
-allowed-tools: Read, Write, Edit, Glob, Grep
 ---
-
 # Mobile Game Development
 
 > Platform constraints and optimization principles.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/game-development/multiplayer/SKILL.md

@@ -1,9 +1,7 @@
 ---
 name: multiplayer
 description: Multiplayer game development principles. Architecture, networking, synchronization.
-allowed-tools: Read, Write, Edit, Glob, Grep, Bash
 ---
-
 # Multiplayer Game Development
 
 > Networking architecture and synchronization principles.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/game-development/pc-games/SKILL.md

@@ -1,9 +1,7 @@
 ---
 name: pc-games
 description: PC and console game development principles. Engine selection, platform features, optimization strategies.
-allowed-tools: Read, Write, Edit, Glob, Grep
 ---
-
 # PC/Console Game Development
 
 > Engine selection and platform-specific principles.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/game-development/vr-ar/SKILL.md

@@ -1,9 +1,7 @@
 ---
 name: vr-ar
 description: VR/AR development principles. Comfort, interaction, performance requirements.
-allowed-tools: Read, Write, Edit, Glob, Grep
 ---
-
 # VR/AR Development
 
 > Immersive experience principles.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/game-development/web-games/SKILL.md

@@ -1,9 +1,7 @@
 ---
 name: web-games
 description: Web browser game development principles. Framework selection, WebGPU, optimization, PWA.
-allowed-tools: Read, Write, Edit, Glob, Grep
 ---
-
 # Web Browser Game Development
 
 > Framework selection and browser-specific principles.

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

@@ -1,9 +1,7 @@
 ---
 name: geo-fundamentals
 description: Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity).
-allowed-tools: Read, Glob, Grep
 ---
-
 # GEO Fundamentals
 
 > Optimization for AI-powered search engines.

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

@@ -1,10 +1,7 @@
 ---
 name: "git-commit"
-displayName: "Git Commit"
 description: "Create conventional commits with intelligent staging and message generation"
-keywords: ["git", "commit", "conventional", "stage", "push", "version control"]
 ---
-
 # Git Commit
 
 ## Conventional Commit Format

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

@@ -9,7 +9,6 @@ metadata:
   stack: "go"
   baseline: "Go 1.26"
 ---
-
 # Golang Pro
 
 ## When to use
@@ -18,6 +17,12 @@ metadata:
 - Designing concurrency with goroutines/channels/context.
 - Optimizing latency, allocations, and reliability.
 
+## When not to use
+
+- Database-only tuning with no Go code change.
+- Browser/frontend tasks outside Go-backed services or tooling.
+- Small shell automation already well-covered by existing scripts.
+
 ## Core workflow
 
 1. Define package boundaries and interfaces.
@@ -41,6 +46,18 @@ metadata:
 - Use generics where they simplify, not where they obscure.
 - Benchmark hot paths (`testing.B`, `pprof`) before tuning.
 
+## Debugging and observability
+
+- Thread request IDs and trace context through handlers and workers.
+- Use structured logs that make cancellation, retries, and deadlines visible.
+- Reproduce concurrency issues with race tests and deterministic fixtures first.
+
+## Performance and reliability
+
+- Prefer bounded worker pools over unbounded goroutine fan-out.
+- Make timeout/cancellation behavior explicit at every network boundary.
+- Profile CPU, heap, and block contention before low-level rewrites.
+
 ## Avoid
 
 - Fire-and-forget goroutines without cancellation path.
@@ -49,8 +66,10 @@ metadata:
 
 ## Reference files
 
-- `references/concurrency.md`
-- `references/generics.md`
-- `references/interfaces.md`
-- `references/testing.md`
-- `references/project-structure.md`
+| File | Load when |
+| --- | --- |
+| `references/concurrency.md` | Concurrency ownership, channels, mutexes, or cancellation safety need detail. |
+| `references/generics.md` | Generics tradeoffs or reusable type-safe helpers are in scope. |
+| `references/interfaces.md` | Interface boundaries and package seams need review. |
+| `references/testing.md` | Test strategy, race checks, or benchmark setup is needed. |
+| `references/project-structure.md` | Package layout or service/module decomposition needs guidance. |

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

@@ -1,19 +1,7 @@
 ---
 name: "gorouter-restoration"
-displayName: "GoRouter & State Restoration"
 description: "GoRouter guard patterns, deep links, redirect safety, tab preservation, and restoration best practices"
-keywords:
-  [
-    "gorouter",
-    "routing",
-    "navigation",
-    "guards",
-    "deep links",
-    "state restoration",
-    "statefulshellroute",
-  ]
 ---
-
 # GoRouter & State Restoration
 
 ## Overview
@@ -114,10 +102,14 @@ MaterialApp.router(
 
 ## Steering Files
 
-- `guard_patterns.md` - Guard decision rules and anti-loop checks
-- `tab_preservation.md` - StatefulShellRoute and restoration patterns
+| File | Load when |
+| --- | --- |
+| `references/guard_patterns.md` | Designing guard logic, redirect rules, or anti-loop checks. |
+| `references/tab_preservation.md` | Preserving `StatefulShellRoute` branches and restoration state. |
 
 ## Templates
 
-- `guard_redirect` - Guard redirect function skeleton
-- `stateful_shell_skeleton` - Tab shell starter
+| File | Load when |
+| --- | --- |
+| `templates/guard_redirect.md` | Starting a redirect/guard function skeleton. |
+| `templates/stateful_shell_skeleton.md` | Starting a shell/tab restoration scaffold. |

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

@@ -12,7 +12,6 @@ metadata:
   output-format: schema
   related-skills: api-designer, microservices-architect, database-optimizer
 ---
-
 # GraphQL Architect
 
 Senior GraphQL architect specializing in schema design and distributed graph architectures with deep expertise in Apollo Federation 2.5+, GraphQL subscriptions, and performance optimization.

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

@@ -1,9 +1,7 @@
 ---
 name: i18n-localization
 description: Internationalization and localization patterns. Detecting hardcoded strings, managing translations, locale files, RTL support.
-allowed-tools: Read, Glob, Grep
 ---
-
 # i18n & Localization
 
 > Internationalization (i18n) and Localization (L10n) best practices.

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

@@ -1,9 +1,7 @@
 ---
 name: intelligent-routing
 description: Automatic agent selection and intelligent task routing. Analyzes user requests and automatically selects the best specialist agent(s) without requiring explicit user mentions.
-version: 1.0.0
 ---
-
 # Intelligent Agent Routing
 
 **Purpose**: Automatically analyze user requests and route them to the most appropriate specialist agent(s) without requiring explicit user mentions.

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

@@ -9,7 +9,6 @@ metadata:
   stack: "java"
   baseline: "Java SE 25"
 ---
-
 # Java Pro
 
 ## When to use
@@ -18,6 +17,12 @@ metadata:
 - Designing JVM architecture for high-throughput systems.
 - Improving reliability, observability, and maintainability.
 
+## When not to use
+
+- Frontend-only tasks with no JVM component.
+- Pure schema/index work better handled as database design or optimization.
+- Low-level native systems work where Rust/Go is the actual project stack.
+
 ## Core workflow
 
 1. Clarify runtime target and deployment constraints.
@@ -33,6 +38,24 @@ metadata:
 - Use structured logging and trace propagation.
 - Enforce dependency and API compatibility checks in CI.
 
+## Debugging and observability
+
+- Capture request/job correlation IDs in logs and traces.
+- Keep exception handling consistent between transport, service, and persistence layers.
+- Reproduce performance or memory issues with focused benchmarks/profilers before redesigning.
+
+## Performance and reliability
+
+- Prefer explicit timeouts, bulkheads, and retry budgets at I/O boundaries.
+- Keep thread/virtual-thread usage bounded and observable.
+- Separate transport DTOs from domain and persistence models to reduce cascade failures.
+
+## References
+
+| File | Load when |
+| --- | --- |
+| `references/operational-baseline.md` | You need current Java service guardrails for logging, testing, dependency hygiene, and runtime operations. |
+
 ## Avoid
 
 - Monolithic service classes with mixed responsibilities.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/java-pro/references/operational-baseline.md

@@ -0,0 +1,9 @@
+## Operational baseline
+
+Load when: JVM service reliability, logging, dependency hygiene, or runtime guardrails need explicit guidance.
+
+- Use structured logging and trace propagation at service boundaries.
+- Keep timeout/retry budgets explicit for external I/O.
+- Separate API contracts from persistence entities.
+- Prefer focused benchmark/profiler evidence before redesigning hot paths.
+- Validate with tests and compatibility checks in CI.

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

@@ -1,15 +1,14 @@
 ---
 name: "javascript-pro"
-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."
 license: MIT
 metadata:
   version: "2.0.0"
   domain: "language"
   role: "specialist"
   stack: "javascript"
-  baseline: "ES2025+"
+  baseline: "Runtime-policy baseline (Node/browser/edge)"
 ---
-
 # JavaScript Pro
 
 ## When to use
@@ -18,6 +17,12 @@ metadata:
 - Refactoring legacy JS toward modern modules and async flows.
 - Improving performance and reliability in browser/Node runtimes.
 
+## When not to use
+
+- Type-driven architecture work where TypeScript is the actual project language.
+- Database-only investigation with no JavaScript runtime behavior involved.
+- One-off shell automation that should remain shell-native.
+
 ## Core workflow
 
 1. Confirm runtime constraints (browser targets, Node/edge version).
@@ -40,6 +45,18 @@ metadata:
 - Use streams for large payloads to avoid memory spikes.
 - Use feature detection, not UA sniffing, in browser code.
 
+## Debugging and observability
+
+- Reproduce runtime-specific failures in the exact target environment: browser, Node, or edge.
+- Surface async failures with structured errors and explicit logging context.
+- Use performance tooling before redesigning hot paths or caching strategy.
+
+## Performance and reliability
+
+- Keep bundle/runtime boundaries explicit so shared code does not assume unavailable APIs.
+- Bound parallelism and cancellation for network-heavy flows.
+- Prefer streaming, chunking, and incremental parsing for large payloads.
+
 ## Avoid
 
 - Silent promise rejections.
@@ -48,8 +65,10 @@ metadata:
 
 ## Reference files
 
-- `references/modern-syntax.md`
-- `references/async-patterns.md`
-- `references/modules.md`
-- `references/browser-apis.md`
-- `references/node-essentials.md`
+| File | Load when |
+| --- | --- |
+| `references/modern-syntax.md` | Choosing modern syntax/features for current runtime targets. |
+| `references/async-patterns.md` | Cancellation, retries, concurrency, or promise orchestration needs detail. |
+| `references/modules.md` | ESM/CJS/module-boundary tradeoffs are in scope. |
+| `references/browser-apis.md` | Browser-specific APIs, capability checks, or UX/runtime constraints matter. |
+| `references/node-essentials.md` | Node runtime behavior, streams, files, or process concerns matter. |

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

@@ -9,7 +9,6 @@ metadata:
   stack: "kotlin"
   baseline: "Kotlin 2.3 line (2.2.20+ compatible)"
 ---
-
 # Kotlin Pro
 
 ## When to use
@@ -18,6 +17,12 @@ metadata:
 - Designing coroutine-based async flows.
 - Improving null-safety and domain model clarity.
 
+## When not to use
+
+- Frontend-only work with no Kotlin/JVM/Android/shared module in scope.
+- Database-only tuning without Kotlin code changes.
+- Tiny scripts that should stay in existing project tooling.
+
 ## Core workflow
 
 1. Establish target platform (JVM/Android/multiplatform).
@@ -33,6 +38,24 @@ metadata:
 - Keep serialization and transport models separate from domain.
 - Use dependency boundaries that support modular testing.
 
+## Debugging and observability
+
+- Keep coroutine context, dispatcher use, and cancellation visible in logs/traces.
+- Reproduce lifecycle-related failures with focused tests before broader rewrites.
+- Prefer deterministic `Flow`/coroutine tests for race-prone logic.
+
+## Performance and reliability
+
+- Bound coroutine fan-out and avoid hidden blocking on default dispatchers.
+- Keep Android/shared/JVM boundaries explicit to avoid platform leakage.
+- Favor allocation-light data flows in hot paths and measure before micro-optimizing.
+
+## References
+
+| File | Load when |
+| --- | --- |
+| `references/operational-baseline.md` | You need Kotlin coroutine, modularity, testing, and production guardrails. |
+
 ## Avoid
 
 - Coroutine launches without lifecycle ownership.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/kotlin-pro/references/operational-baseline.md

@@ -0,0 +1,9 @@
+## Operational baseline
+
+Load when: coroutine ownership, modularity, testing, or production guardrails need explicit guidance.
+
+- Keep coroutine scope ownership explicit and lifecycle-aware.
+- Avoid hidden blocking on shared/default dispatchers.
+- Keep shared/domain modules isolated from platform-specific details.
+- Use deterministic tests for `Flow`, coroutine, and lifecycle behavior.
+- Prefer structured logs and traces that show dispatcher/cancellation context.

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

@@ -12,7 +12,6 @@ metadata:
   output-format: code+analysis
   related-skills: test-master, devops-engineer
 ---
-
 # Legacy Modernizer
 
 Senior legacy modernization specialist with expertise in transforming aging systems into modern architectures without disrupting business operations.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/lint-and-validate/SKILL.md

@@ -1,9 +1,7 @@
 ---
 name: lint-and-validate
 description: "Automatic quality control, linting, and static analysis procedures. Use after every code modification to ensure syntax correctness and project standards. Triggers: lint, format, check, validate, types, static analysis."
-allowed-tools: Read, Glob, Grep, Bash
 ---
-
 # Lint and Validate Skill
 
 > **MANDATORY:** Run appropriate validation tools after EVERY code change. Do not finish a task until the code is error-free.

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

@@ -2,8 +2,6 @@
 name: "microservices-architect"
 description: "Use when designing distributed systems, decomposing monoliths, or implementing microservices patterns. Invoke for service boundaries, DDD, saga patterns, event sourcing, service mesh, distributed tracing."
 ---
-
-
 # Microservices Architect
 
 ## Overview
@@ -83,11 +81,3 @@ When designing microservices architecture, provide:
 ## Knowledge Reference
 
 Domain-driven design, bounded contexts, event storming, REST/gRPC, message queues (Kafka, RabbitMQ), service mesh (Istio, Linkerd), Kubernetes, circuit breakers, saga patterns, event sourcing, CQRS, distributed tracing (Jaeger, Zipkin), API gateways, eventual consistency, CAP theorem
-
-## Related Powers
-
-- **DevOps Engineer** - Container orchestration and CI/CD pipelines
-- **Kubernetes Specialist** - Advanced K8s patterns and operators
-- **GraphQL Architect** - Federation for distributed schemas
-- **Architecture Designer** - High-level system design
-- **Monitoring Expert** - Observability implementation