@cubis/foundry 0.3.31 → 0.3.33

package/workflows/skills/github-automation/SKILL.md

@@ -1,227 +1,18 @@
 ---
-name: github-automation
-description: Automate GitHub repositories, issues, pull requests, branches, CI/CD, and permissions via Rube MCP (Composio). Manage code workflows, review PRs, search code, and handle deployments programmatically.
-requires:
-  mcp: [rube]
+name: "github-automation"
+description: "Compatibility wrapper skill. Canonical MCP skill moved to mcp/skills/github-automation."
+metadata:
+  deprecated: true
+  replaced_by: "github-automation"
+  moved_to: "mcp/skills/github-automation/SKILL.md"
+  removal_target: "v0.6.0"
 ---
 
-# GitHub Automation via Rube MCP
+# github-automation (Compatibility Wrapper)
 
-Automate GitHub repository management, issue tracking, pull request workflows, branch operations, and CI/CD through Composio's GitHub toolkit.
+This legacy workflow-path skill is kept for backward compatibility.
 
-## Prerequisites
+Canonical MCP skill path:
+- mcp/skills/github-automation/SKILL.md
 
-- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
-- Active GitHub connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `github`
-- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
-
-## Setup
-
-**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
-
-
-1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
-2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `github`
-3. If connection is not ACTIVE, follow the returned auth link to complete GitHub OAuth
-4. Confirm connection status shows ACTIVE before running any workflows
-
-## Core Workflows
-
-### 1. Create and Manage Issues
-
-**When to use**: User wants to create, list, or manage GitHub issues
-
-**Tool sequence**:
-1. `GITHUB_LIST_REPOSITORIES_FOR_THE_AUTHENTICATED_USER` - Find target repo if unknown [Prerequisite]
-2. `GITHUB_LIST_REPOSITORY_ISSUES` - List existing issues (includes PRs) [Required]
-3. `GITHUB_CREATE_AN_ISSUE` - Create a new issue [Required]
-4. `GITHUB_CREATE_AN_ISSUE_COMMENT` - Add comments to an issue [Optional]
-5. `GITHUB_SEARCH_ISSUES_AND_PULL_REQUESTS` - Search across repos by keyword [Optional]
-
-**Key parameters**:
-- `owner`: Repository owner (username or org), case-insensitive
-- `repo`: Repository name without .git extension
-- `title`: Issue title (required for creation)
-- `body`: Issue description (supports Markdown)
-- `labels`: Array of label names
-- `assignees`: Array of GitHub usernames
-- `state`: 'open', 'closed', or 'all' for filtering
-
-**Pitfalls**:
-- `GITHUB_LIST_REPOSITORY_ISSUES` returns both issues AND pull requests; check `pull_request` field to distinguish
-- Only users with push access can set assignees, labels, and milestones; they are silently dropped otherwise
-- Pagination: `per_page` max 100; iterate pages until empty
-
-### 2. Manage Pull Requests
-
-**When to use**: User wants to create, review, or merge pull requests
-
-**Tool sequence**:
-1. `GITHUB_FIND_PULL_REQUESTS` - Search and filter PRs [Required]
-2. `GITHUB_GET_A_PULL_REQUEST` - Get detailed PR info including mergeable status [Required]
-3. `GITHUB_LIST_PULL_REQUESTS_FILES` - Review changed files [Optional]
-4. `GITHUB_CREATE_A_PULL_REQUEST` - Create a new PR [Required]
-5. `GITHUB_CREATE_AN_ISSUE_COMMENT` - Post review comments [Optional]
-6. `GITHUB_LIST_CHECK_RUNS_FOR_A_REF` - Verify CI status before merge [Optional]
-7. `GITHUB_MERGE_A_PULL_REQUEST` - Merge after explicit user approval [Required]
-
-**Key parameters**:
-- `head`: Source branch with changes (must exist; for cross-repo: 'username:branch')
-- `base`: Target branch to merge into (e.g., 'main')
-- `title`: PR title (required unless `issue` number provided)
-- `merge_method`: 'merge', 'squash', or 'rebase'
-- `state`: 'open', 'closed', or 'all'
-
-**Pitfalls**:
-- `GITHUB_CREATE_A_PULL_REQUEST` fails with 422 if base/head are invalid, identical, or already merged
-- `GITHUB_MERGE_A_PULL_REQUEST` can be rejected if PR is draft, closed, or branch protection applies
-- Always verify mergeable status with `GITHUB_GET_A_PULL_REQUEST` immediately before merging
-- Require explicit user confirmation before calling MERGE
-
-### 3. Manage Repositories and Branches
-
-**When to use**: User wants to create repos, manage branches, or update repo settings
-
-**Tool sequence**:
-1. `GITHUB_LIST_REPOSITORIES_FOR_THE_AUTHENTICATED_USER` - List user's repos [Required]
-2. `GITHUB_GET_A_REPOSITORY` - Get detailed repo info [Optional]
-3. `GITHUB_CREATE_A_REPOSITORY_FOR_THE_AUTHENTICATED_USER` - Create personal repo [Required]
-4. `GITHUB_CREATE_AN_ORGANIZATION_REPOSITORY` - Create org repo [Alternative]
-5. `GITHUB_LIST_BRANCHES` - List branches [Required]
-6. `GITHUB_CREATE_A_REFERENCE` - Create new branch from SHA [Required]
-7. `GITHUB_UPDATE_A_REPOSITORY` - Update repo settings [Optional]
-
-**Key parameters**:
-- `name`: Repository name
-- `private`: Boolean for visibility
-- `ref`: Full reference path (e.g., 'refs/heads/new-branch')
-- `sha`: Commit SHA to point the new reference to
-- `default_branch`: Default branch name
-
-**Pitfalls**:
-- `GITHUB_CREATE_A_REFERENCE` only creates NEW references; use `GITHUB_UPDATE_A_REFERENCE` for existing ones
-- `ref` must start with 'refs/' and contain at least two slashes
-- `GITHUB_LIST_BRANCHES` paginates via `page`/`per_page`; iterate until empty page
-- `GITHUB_DELETE_A_REPOSITORY` is permanent and irreversible; requires admin privileges
-
-### 4. Search Code and Commits
-
-**When to use**: User wants to find code, files, or commits across repositories
-
-**Tool sequence**:
-1. `GITHUB_SEARCH_CODE` - Search file contents and paths [Required]
-2. `GITHUB_SEARCH_CODE_ALL_PAGES` - Multi-page code search [Alternative]
-3. `GITHUB_SEARCH_COMMITS_BY_AUTHOR` - Search commits by author/date/org [Required]
-4. `GITHUB_LIST_COMMITS` - List commits for a specific repo [Alternative]
-5. `GITHUB_GET_A_COMMIT` - Get detailed commit info [Optional]
-6. `GITHUB_GET_REPOSITORY_CONTENT` - Get file content [Optional]
-
-**Key parameters**:
-- `q`: Search query with qualifiers (`language:python`, `repo:owner/repo`, `extension:js`)
-- `owner`/`repo`: For repo-specific commit listing
-- `author`: Filter by commit author
-- `since`/`until`: ISO 8601 date range for commits
-
-**Pitfalls**:
-- Code search only indexes files under 384KB on default branch
-- Maximum 1000 results returned from code search
-- `GITHUB_SEARCH_COMMITS_BY_AUTHOR` requires keywords in addition to qualifiers; qualifier-only queries are not allowed
-- `GITHUB_LIST_COMMITS` returns 409 on empty repos
-
-### 5. Manage CI/CD and Deployments
-
-**When to use**: User wants to view workflows, check CI status, or manage deployments
-
-**Tool sequence**:
-1. `GITHUB_LIST_REPOSITORY_WORKFLOWS` - List GitHub Actions workflows [Required]
-2. `GITHUB_GET_A_WORKFLOW` - Get workflow details by ID or filename [Optional]
-3. `GITHUB_CREATE_A_WORKFLOW_DISPATCH_EVENT` - Manually trigger a workflow [Required]
-4. `GITHUB_LIST_CHECK_RUNS_FOR_A_REF` - Check CI status for a commit/branch [Required]
-5. `GITHUB_LIST_DEPLOYMENTS` - List deployments [Optional]
-6. `GITHUB_GET_A_DEPLOYMENT_STATUS` - Get deployment status [Optional]
-
-**Key parameters**:
-- `workflow_id`: Numeric ID or filename (e.g., 'ci.yml')
-- `ref`: Git reference (branch/tag) for workflow dispatch
-- `inputs`: JSON string of workflow inputs matching `on.workflow_dispatch.inputs`
-- `environment`: Filter deployments by environment name
-
-**Pitfalls**:
-- `GITHUB_CREATE_A_WORKFLOW_DISPATCH_EVENT` requires the workflow to have `workflow_dispatch` trigger configured
-- Full path `.github/workflows/main.yml` is auto-stripped to just `main.yml`
-- Inputs max 10 key-value pairs; must match workflow's `on.workflow_dispatch.inputs` definitions
-
-### 6. Manage Users and Permissions
-
-**When to use**: User wants to check collaborators, permissions, or branch protection
-
-**Tool sequence**:
-1. `GITHUB_LIST_REPOSITORY_COLLABORATORS` - List repo collaborators [Required]
-2. `GITHUB_GET_REPOSITORY_PERMISSIONS_FOR_A_USER` - Check specific user's access [Optional]
-3. `GITHUB_GET_BRANCH_PROTECTION` - Inspect branch protection rules [Required]
-4. `GITHUB_UPDATE_BRANCH_PROTECTION` - Update protection settings [Optional]
-5. `GITHUB_ADD_A_REPOSITORY_COLLABORATOR` - Add/update collaborator [Optional]
-
-**Key parameters**:
-- `affiliation`: 'outside', 'direct', or 'all' for collaborator filtering
-- `permission`: Filter by 'pull', 'triage', 'push', 'maintain', 'admin'
-- `branch`: Branch name for protection rules
-- `enforce_admins`: Whether protection applies to admins
-
-**Pitfalls**:
-- `GITHUB_GET_BRANCH_PROTECTION` returns 404 for unprotected branches; treat as no protection rules
-- Determine push ability from `permissions.push` or `role_name`, not display labels
-- `GITHUB_LIST_REPOSITORY_COLLABORATORS` paginates; iterate all pages
-- `GITHUB_GET_REPOSITORY_PERMISSIONS_FOR_A_USER` may be inconclusive for non-collaborators
-
-## Common Patterns
-
-### ID Resolution
-- **Repo name -> owner/repo**: `GITHUB_LIST_REPOSITORIES_FOR_THE_AUTHENTICATED_USER`
-- **PR number -> PR details**: `GITHUB_FIND_PULL_REQUESTS` then `GITHUB_GET_A_PULL_REQUEST`
-- **Branch name -> SHA**: `GITHUB_GET_A_BRANCH`
-- **Workflow name -> ID**: `GITHUB_LIST_REPOSITORY_WORKFLOWS`
-
-### Pagination
-All list endpoints use page-based pagination:
-- `page`: Page number (starts at 1)
-- `per_page`: Results per page (max 100)
-- Iterate until response returns fewer results than `per_page`
-
-### Safety
-- Always verify PR mergeable status before merge
-- Require explicit user confirmation for destructive operations (merge, delete)
-- Check CI status with `GITHUB_LIST_CHECK_RUNS_FOR_A_REF` before merging
-
-## Known Pitfalls
-
-- **Issues vs PRs**: `GITHUB_LIST_REPOSITORY_ISSUES` returns both; check `pull_request` field
-- **Pagination limits**: `per_page` max 100; always iterate pages until empty
-- **Branch creation**: `GITHUB_CREATE_A_REFERENCE` fails with 422 if reference already exists
-- **Merge guards**: Merge can fail due to branch protection, failing checks, or draft status
-- **Code search limits**: Only files <384KB on default branch; max 1000 results
-- **Commit search**: Requires search text keywords alongside qualifiers
-- **Destructive actions**: Repo deletion is irreversible; merge cannot be undone
-- **Silent permission drops**: Labels, assignees, milestones silently dropped without push access
-
-## Quick Reference
-
-| Task | Tool Slug | Key Params |
-|------|-----------|------------|
-| List repos | `GITHUB_LIST_REPOSITORIES_FOR_THE_AUTHENTICATED_USER` | `type`, `sort`, `per_page` |
-| Get repo | `GITHUB_GET_A_REPOSITORY` | `owner`, `repo` |
-| Create issue | `GITHUB_CREATE_AN_ISSUE` | `owner`, `repo`, `title`, `body` |
-| List issues | `GITHUB_LIST_REPOSITORY_ISSUES` | `owner`, `repo`, `state` |
-| Find PRs | `GITHUB_FIND_PULL_REQUESTS` | `repo`, `state`, `author` |
-| Create PR | `GITHUB_CREATE_A_PULL_REQUEST` | `owner`, `repo`, `head`, `base`, `title` |
-| Merge PR | `GITHUB_MERGE_A_PULL_REQUEST` | `owner`, `repo`, `pull_number`, `merge_method` |
-| List branches | `GITHUB_LIST_BRANCHES` | `owner`, `repo` |
-| Create branch | `GITHUB_CREATE_A_REFERENCE` | `owner`, `repo`, `ref`, `sha` |
-| Search code | `GITHUB_SEARCH_CODE` | `q` |
-| List commits | `GITHUB_LIST_COMMITS` | `owner`, `repo`, `author`, `since` |
-| Search commits | `GITHUB_SEARCH_COMMITS_BY_AUTHOR` | `q` |
-| List workflows | `GITHUB_LIST_REPOSITORY_WORKFLOWS` | `owner`, `repo` |
-| Trigger workflow | `GITHUB_CREATE_A_WORKFLOW_DISPATCH_EVENT` | `owner`, `repo`, `workflow_id`, `ref` |
-| Check CI | `GITHUB_LIST_CHECK_RUNS_FOR_A_REF` | `owner`, `repo`, ref |
-| List collaborators | `GITHUB_LIST_REPOSITORY_COLLABORATORS` | `owner`, `repo` |
-| Branch protection | `GITHUB_GET_BRANCH_PROTECTION` | `owner`, `repo`, `branch` |
+Install MCP skills with: cbx workflows install --include-mcp

package/workflows/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/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/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/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.