@cubis/foundry 0.3.32 → 0.3.33

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

@@ -1,84 +1,56 @@
 ---
-name: golang-pro
-description: Use when building Go applications requiring concurrent programming, microservices architecture, or high-performance systems. Invoke for goroutines, channels, Go generics, gRPC integration.
+name: "golang-pro"
+description: "Use for modern Go services and tooling with Go 1.26-era language/runtime patterns, concurrency safety, and production operations."
 license: MIT
 metadata:
-  author: https://github.com/Jeffallan
-  version: "1.0.0"
-  domain: language
-  triggers: Go, Golang, goroutines, channels, gRPC, microservices Go, Go generics, concurrent programming, Go interfaces
-  role: specialist
-  scope: implementation
-  output-format: code
-  related-skills: devops-engineer, microservices-architect, test-master
+  version: "2.0.0"
+  domain: "language"
+  role: "specialist"
+  stack: "go"
+  baseline: "Go 1.26"
 ---
 
 # Golang Pro
 
-Senior Go developer with deep expertise in Go 1.21+, concurrent programming, and cloud-native microservices. Specializes in idiomatic patterns, performance optimization, and production-grade systems.
+## When to use
 
-## Role Definition
+- Building APIs, workers, CLIs, and microservices in Go.
+- Designing concurrency with goroutines/channels/context.
+- Optimizing latency, allocations, and reliability.
 
-You are a senior Go engineer with 8+ years of systems programming experience. You specialize in Go 1.21+ with generics, concurrent patterns, gRPC microservices, and cloud-native applications. You build efficient, type-safe systems following Go proverbs.
+## Core workflow
 
-## When to Use This Skill
+1. Define package boundaries and interfaces.
+2. Implement with explicit error handling and context propagation.
+3. Add tests and race checks for behavior under load.
+4. Profile before optimization.
 
-- Building concurrent Go applications with goroutines and channels
-- Implementing microservices with gRPC or REST APIs
-- Creating CLI tools and system utilities
-- Optimizing Go code for performance and memory efficiency
-- Designing interfaces and using Go generics
-- Setting up testing with table-driven tests and benchmarks
+## Baseline standards
 
-## Core Workflow
+- Keep APIs context-aware: pass `context.Context` first.
+- Handle every error with actionable wrapping.
+- Use table-driven tests and subtests for logic coverage.
+- Run `go test -race` for concurrency-sensitive paths.
+- Prefer composition over deep inheritance-like abstractions.
 
-1. **Analyze architecture** - Review module structure, interfaces, concurrency patterns
-2. **Design interfaces** - Create small, focused interfaces with composition
-3. **Implement** - Write idiomatic Go with proper error handling and context propagation
-4. **Optimize** - Profile with pprof, write benchmarks, eliminate allocations
-5. **Test** - Table-driven tests, race detector, fuzzing, 80%+ coverage
+## Implementation guidance
 
-## Reference Guide
+- Use channels for ownership transfer, not shared mutation.
+- Choose sync primitives deliberately (`Mutex`, `RWMutex`, `atomic`).
+- Keep goroutine lifecycles bounded with cancellation.
+- Use generics where they simplify, not where they obscure.
+- Benchmark hot paths (`testing.B`, `pprof`) before tuning.
 
-Load detailed guidance based on context:
+## Avoid
 
-| Topic | Reference | Load When |
-|-------|-----------|-----------|
-| Concurrency | `references/concurrency.md` | Goroutines, channels, select, sync primitives |
-| Interfaces | `references/interfaces.md` | Interface design, io.Reader/Writer, composition |
-| Generics | `references/generics.md` | Type parameters, constraints, generic patterns |
-| Testing | `references/testing.md` | Table-driven tests, benchmarks, fuzzing |
-| Project Structure | `references/project-structure.md` | Module layout, internal packages, go.mod |
+- Fire-and-forget goroutines without cancellation path.
+- Panic-based control flow.
+- Over-generalized interfaces without real callers.
 
-## Constraints
+## Reference files
 
-### MUST DO
-- Use gofmt and golangci-lint on all code
-- Add context.Context to all blocking operations
-- Handle all errors explicitly (no naked returns)
-- Write table-driven tests with subtests
-- Document all exported functions, types, and packages
-- Use `X | Y` union constraints for generics (Go 1.18+)
-- Propagate errors with fmt.Errorf("%w", err)
-- Run race detector on tests (-race flag)
-
-### MUST NOT DO
-- Ignore errors (avoid _ assignment without justification)
-- Use panic for normal error handling
-- Create goroutines without clear lifecycle management
-- Skip context cancellation handling
-- Use reflection without performance justification
-- Mix sync and async patterns carelessly
-- Hardcode configuration (use functional options or env vars)
-
-## Output Templates
-
-When implementing Go features, provide:
-1. Interface definitions (contracts first)
-2. Implementation files with proper package structure
-3. Test file with table-driven tests
-4. Brief explanation of concurrency patterns used
-
-## Knowledge Reference
-
-Go 1.21+, goroutines, channels, select, sync package, generics, type parameters, constraints, io.Reader/Writer, gRPC, context, error wrapping, pprof profiling, benchmarks, table-driven tests, fuzzing, go.mod, internal packages, functional options
+- `references/concurrency.md`
+- `references/generics.md`
+- `references/interfaces.md`
+- `references/testing.md`
+- `references/project-structure.md`

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

@@ -0,0 +1,40 @@
+---
+name: "java-pro"
+description: "Use for modern Java backend and platform engineering with Java 25-era language/runtime practices."
+license: MIT
+metadata:
+  version: "1.0.0"
+  domain: "language"
+  role: "specialist"
+  stack: "java"
+  baseline: "Java SE 25"
+---
+
+# Java Pro
+
+## When to use
+
+- Building or modernizing Java backend services.
+- Designing JVM architecture for high-throughput systems.
+- Improving reliability, observability, and maintainability.
+
+## Core workflow
+
+1. Clarify runtime target and deployment constraints.
+2. Define module boundaries and API contracts.
+3. Implement with clear domain/service/infrastructure separation.
+4. Add tests and performance checks for critical paths.
+
+## Baseline standards
+
+- Use current LTS/JDK baseline approved by project policy.
+- Prefer records/sealed hierarchies where they simplify modeling.
+- Keep null-handling explicit; avoid silent NPE pathways.
+- Use structured logging and trace propagation.
+- Enforce dependency and API compatibility checks in CI.
+
+## Avoid
+
+- Monolithic service classes with mixed responsibilities.
+- Reflection-heavy magic when explicit code is clearer.
+- Leaking persistence entities directly into API contracts.

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

@@ -1,85 +1,55 @@
 ---
-name: javascript-pro
-description: Use when building JavaScript applications with modern ES2023+ features, async patterns, or Node.js development. Invoke for vanilla JavaScript, browser APIs, performance optimization, module systems.
+name: "javascript-pro"
+description: "Use for modern JavaScript architecture and implementation across browser, Node, and edge runtimes with ES2025+ practices."
 license: MIT
 metadata:
-  author: https://github.com/Jeffallan
-  version: "1.0.0"
-  domain: language
-  triggers: JavaScript, ES2023, async await, Node.js, vanilla JavaScript, Web Workers, Fetch API, browser API, module system
-  role: specialist
-  scope: implementation
-  output-format: code
-  related-skills: fullstack-guardian
+  version: "2.0.0"
+  domain: "language"
+  role: "specialist"
+  stack: "javascript"
+  baseline: "ES2025+"
 ---
 
 # JavaScript Pro
 
-Senior JavaScript developer with 10+ years mastering modern ES2023+ features, asynchronous patterns, and full-stack JavaScript development.
+## When to use
 
-## Role Definition
+- Implementing feature work in plain JavaScript.
+- Refactoring legacy JS toward modern modules and async flows.
+- Improving performance and reliability in browser/Node runtimes.
 
-You are a senior JavaScript engineer with 10+ years of experience. You specialize in modern ES2023+ JavaScript, Node.js 20+, asynchronous programming, functional patterns, and performance optimization. You build clean, maintainable code following modern best practices.
+## Core workflow
 
-## When to Use This Skill
+1. Confirm runtime constraints (browser targets, Node/edge version).
+2. Choose module boundaries and async strategy.
+3. Implement with explicit error and cancellation handling.
+4. Verify behavior with tests and runtime checks.
 
-- Building vanilla JavaScript applications
-- Implementing async/await patterns and Promise handling
-- Working with modern module systems (ESM/CJS)
-- Optimizing browser performance and memory usage
-- Developing Node.js backend services
-- Implementing Web Workers, Service Workers, or browser APIs
+## Baseline standards
 
-## Core Workflow
+- Prefer ESM for new code unless compatibility blocks it.
+- Use `AbortSignal` for cancellable async operations.
+- Keep side effects at edges; pure logic in reusable modules.
+- Validate untrusted input at boundaries.
+- Keep dependency surface intentionally small.
 
-1. **Analyze requirements** - Review package.json, module system, Node version, browser targets
-2. **Design architecture** - Plan modules, async flows, error handling strategies
-3. **Implement** - Write ES2023+ code with proper patterns and optimizations
-4. **Optimize** - Profile performance, reduce bundle size, prevent memory leaks
-5. **Test** - Write comprehensive tests with Jest achieving 85%+ coverage
+## Implementation guidance
 
-## Reference Guide
+- Use `Promise.all` for independent parallel operations.
+- Use structured logging and consistent error shapes.
+- Use streams for large payloads to avoid memory spikes.
+- Use feature detection, not UA sniffing, in browser code.
 
-Load detailed guidance based on context:
+## Avoid
 
-| Topic | Reference | Load When |
-|-------|-----------|-----------|
-| Modern Syntax | `references/modern-syntax.md` | ES2023+ features, optional chaining, private fields |
-| Async Patterns | `references/async-patterns.md` | Promises, async/await, error handling, event loop |
-| Modules | `references/modules.md` | ESM vs CJS, dynamic imports, package.json exports |
-| Browser APIs | `references/browser-apis.md` | Fetch, Web Workers, Storage, IntersectionObserver |
-| Node Essentials | `references/node-essentials.md` | fs/promises, streams, EventEmitter, worker threads |
+- Silent promise rejections.
+- Heavy framework coupling in low-level modules.
+- Copy-paste utility proliferation without consolidation.
 
-## Constraints
+## Reference files
 
-### MUST DO
-- Use ES2023+ features exclusively
-- Use `X | null` or `X | undefined` patterns
-- Use optional chaining (`?.`) and nullish coalescing (`??`)
-- Use async/await for all asynchronous operations
-- Use ESM (`import`/`export`) for new projects
-- Implement proper error handling with try/catch
-- Add JSDoc comments for complex functions
-- Follow functional programming principles
-
-### MUST NOT DO
-- Use `var` (always use `const` or `let`)
-- Use callback-based patterns (prefer Promises)
-- Mix CommonJS and ESM in same module
-- Ignore memory leaks or performance issues
-- Skip error handling in async functions
-- Use synchronous I/O in Node.js
-- Mutate function parameters
-- Create blocking operations in browser
-
-## Output Templates
-
-When implementing JavaScript features, provide:
-1. Module file with clean exports
-2. Test file with comprehensive coverage
-3. JSDoc documentation for public APIs
-4. Brief explanation of patterns used
-
-## Knowledge Reference
-
-ES2023, optional chaining, nullish coalescing, private fields, top-level await, Promise patterns, async/await, event loop, ESM/CJS, dynamic imports, Fetch API, Web Workers, Service Workers, Node.js streams, EventEmitter, memory optimization, functional programming
+- `references/modern-syntax.md`
+- `references/async-patterns.md`
+- `references/modules.md`
+- `references/browser-apis.md`
+- `references/node-essentials.md`

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

@@ -0,0 +1,40 @@
+---
+name: "kotlin-pro"
+description: "Use for modern Kotlin backend/mobile/shared code with Kotlin 2.3-era language tooling and production patterns."
+license: MIT
+metadata:
+  version: "1.0.0"
+  domain: "language"
+  role: "specialist"
+  stack: "kotlin"
+  baseline: "Kotlin 2.3 line (2.2.20+ compatible)"
+---
+
+# Kotlin Pro
+
+## When to use
+
+- Building Kotlin services or Android/shared modules.
+- Designing coroutine-based async flows.
+- Improving null-safety and domain model clarity.
+
+## Core workflow
+
+1. Establish target platform (JVM/Android/multiplatform).
+2. Define domain types and boundary contracts first.
+3. Implement with coroutine/flow patterns where appropriate.
+4. Validate with tests and static analysis.
+
+## Baseline standards
+
+- Keep nullability explicit; avoid forced non-null assertions.
+- Prefer immutable data models and pure transforms.
+- Use structured concurrency and clear scope ownership.
+- Keep serialization and transport models separate from domain.
+- Use dependency boundaries that support modular testing.
+
+## Avoid
+
+- Coroutine launches without lifecycle ownership.
+- Platform-specific leakage into shared/core modules.
+- Overusing extension magic that hurts readability.

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

@@ -1,166 +1,59 @@
 ---
 name: "nextjs-developer"
 displayName: "Next.js Developer"
-description: "Use for implementing/refactoring Next.js App Router features, Server Components/Actions, SEO, and production architecture. Not for version migration workflows or cache-components-only tuning."
-keywords:
-  [
-    "nextjs",
-    "next.js",
-    "react",
-    "app router",
-    "server components",
-    "server actions",
-    "vercel",
-    "ssr",
-    "seo",
-    "typescript",
-  ]
+description: "Use for implementing/refactoring Next.js App Router features, React Server Components/Actions, SEO, and production architecture."
+license: MIT
+metadata:
+  version: "2.0.0"
+  domain: "frontend"
+  role: "specialist"
+  stack: "nextjs"
+  baseline: "Next.js 16 + React 19"
 ---
 
 # Next.js Developer
 
-## Overview
+## Scope
 
-Senior Next.js developer expertise for Next.js 14+ with App Router and full-stack features. Covers server components, server actions, edge runtime, performance optimization, and production deployment with focus on fast, SEO-friendly applications.
+- Primary skill for App Router implementation and refactors.
+- Not for version migration playbooks (`next-upgrade`) or cache-components-only tuning (`next-cache-components`).
 
-## When to Use
+## When to use
 
-- Building new Next.js 14+ projects with App Router
-- Implementing Server Components and Server Actions
-- Optimizing Core Web Vitals and performance
-- Setting up data fetching with caching and revalidation
-- Configuring SEO (metadata, sitemaps, structured data)
-- Deploying to Vercel, Docker, or self-hosted environments
-- Writing tests with Playwright and React Testing Library
+- Building routes/layouts/loading/error boundaries.
+- Implementing server components and server actions.
+- Designing data fetching/revalidation strategy.
+- Improving SEO and web vitals.
 
-## Quick Reference
+## Core workflow
 
-### App Router File Conventions
+1. Define rendering mode per route (static/dynamic/streaming).
+2. Keep server/client component boundaries explicit.
+3. Implement data access with caching semantics by intent.
+4. Add forms/actions with validation and auth checks.
+5. Verify perf, accessibility, and error handling.
 
-```
-app/
-├── layout.tsx          # Root layout (required)
-├── page.tsx            # Home page
-├── loading.tsx         # Loading UI (Suspense boundary)
-├── error.tsx           # Error boundary
-├── not-found.tsx       # 404 page
-├── (auth)/             # Route group (no URL segment)
-│   ├── login/page.tsx
-│   └── register/page.tsx
-├── dashboard/
-│   ├── layout.tsx      # Nested layout
-│   ├── page.tsx
-│   └── @modal/         # Parallel route (slot)
-│       └── (..)settings/page.tsx  # Intercepting route
-└── api/
-    └── route.ts        # API route handler
-```
+## Baseline standards
 
-### Server vs Client Components
+- Default to Server Components; opt into client components only when needed.
+- Keep server-only code out of client bundles.
+- Use route-level loading/error states.
+- Use metadata API and structured data for SEO.
+- Measure Core Web Vitals and act on regressions.
 
-```tsx
-// Server Component (default) — no directive needed
-async function ProductList() {
-  const products = await db.product.findMany();
-  return (
-    <ul>
-      {products.map((p) => (
-        <li key={p.id}>{p.name}</li>
-      ))}
-    </ul>
-  );
-}
+## Avoid
 
-// Client Component — needs 'use client' directive
-("use client");
-import { useState } from "react";
-export function Counter() {
-  const [count, setCount] = useState(0);
-  return <button onClick={() => setCount((c) => c + 1)}>{count}</button>;
-}
-```
+- Unnecessary client hydration.
+- Mixing auth-sensitive logic into client-only paths.
+- Overusing global revalidation when targeted invalidation is possible.
 
-### Server Actions
+## Reference files
 
-```tsx
-// Inline server action
-async function createPost(formData: FormData) {
-  "use server";
-  const title = formData.get("title") as string;
-  await db.post.create({ data: { title } });
-  revalidatePath("/posts");
-}
-
-// In a form
-<form action={createPost}>
-  <input name="title" />
-  <button type="submit">Create</button>
-</form>;
-```
-
-### Data Fetching with Cache
-
-```tsx
-// Cached by default (static)
-const data = await fetch("https://api.example.com/data");
-
-// Revalidate every 60 seconds (ISR)
-const data = await fetch("https://api.example.com/data", {
-  next: { revalidate: 60 },
-});
-
-// No cache (dynamic)
-const data = await fetch("https://api.example.com/data", {
-  cache: "no-store",
-});
-```
-
-### Metadata API
-
-```tsx
-// Static metadata
-export const metadata: Metadata = {
-  title: "My App",
-  description: "Description",
-  openGraph: { title: "My App", images: ["/og.png"] },
-};
-
-// Dynamic metadata
-export async function generateMetadata({ params }): Promise<Metadata> {
-  const product = await getProduct(params.id);
-  return { title: product.name };
-}
-```
-
-## Quality Checklist
-
-- [ ] TypeScript strict mode enabled
-- [ ] Core Web Vitals > 90
-- [ ] SEO score > 95
-- [ ] Error boundaries on all routes
-- [ ] Loading states for async content
-- [ ] Edge runtime compatible where needed
-- [ ] Monitoring and error tracking configured
-
-## Steering Files
-
-| File                   | Load When                                                            |
-| ---------------------- | -------------------------------------------------------------------- |
-| `app-router.md`        | Route structure, layouts, route groups, parallel/intercepting routes |
-| `server-components.md` | Server/Client component patterns, streaming, Suspense                |
-| `server-actions.md`    | Form handling, mutations, validation, optimistic updates             |
-| `data-fetching.md`     | Fetch patterns, caching, revalidation, SWR/React Query               |
-| `performance.md`       | Image/font/script optimization, Core Web Vitals, bundle analysis     |
-| `seo.md`               | Metadata API, sitemaps, structured data, Open Graph                  |
-| `deployment.md`        | Vercel, Docker, self-hosting, monitoring, multi-region               |
-| `testing.md`           | Playwright E2E, component tests, visual regression, accessibility    |
-
-## Performance Targets
-
-| Metric | Target  |
-| ------ | ------- |
-| TTFB   | < 200ms |
-| FCP    | < 1s    |
-| LCP    | < 2.5s  |
-| CLS    | < 0.1   |
-| FID    | < 100ms |
+- `references/app-router.md`
+- `references/server-components.md`
+- `references/server-actions.md`
+- `references/data-fetching.md`
+- `references/performance.md`
+- `references/seo.md`
+- `references/deployment.md`
+- `references/testing.md`

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/nextjs-react-expert/SKILL.md

@@ -1,21 +1,15 @@
 ---
-name: nextjs-react-expert
+name: "nextjs-react-expert"
 description: "Compatibility alias skill. Deprecated: use react-best-practices."
 metadata:
   deprecated: true
-  replaced_by: react-best-practices
-  removal_target: v0.6.0
+  replaced_by: "react-best-practices"
+  removal_target: "v0.6.0"
+  alias_of: "react-best-practices"
 ---
 
-# Nextjs React Expert
-
-## Compatibility Alias
+# nextjs-react-expert (Compatibility Alias)
 
 This skill is deprecated and kept for backward compatibility.
 
-Use `react-best-practices` as the canonical skill.
-
-## Migration
-
-1. Replace direct references to `nextjs-react-expert` with `react-best-practices`.
-2. Apply the full workflow from `react-best-practices` for new work.
+Use `react-best-practices` for optimization/review workflows.