jrmatherly

Specialized Spacebot development skill with deep architectural knowledge. Use when working on any Spacebot feature, bug fix, refactor, or investigation. Covers the five-process agent model (Channel, Branch, Worker, Compactor, Cortex), memory system (SQLite + LanceDB + redb), task lifecycle, 60+ tool definitions, Rig framework integration, prompt templates, identity system, messaging adapters, config hot-reload, security/sandbox, and API server. Activate for any Rust code changes in src/, prompt template edits in prompts/, migration work, tool additions, or architectural questions.

Use this skill when preparing a release bump or updating release notes. It writes a launch-style release story from the actual change set, then runs `cargo bump` so the generated GitHub notes and the marketing copy land together in `CHANGELOG.md`.

Use when bumping a bun-managed dependency in interface/, docs/, packages/api-client/, or spaceui/. Avoids the "lockfile updated, manifest spec stale" drift class that opened PRs

Use when auditing project documentation for drift, stale claims, missing changelog entries, completed-but-still-listed TODOs, or when the user asks to review/refresh/cleanup docs across interface/, spaceui/, docs/, or repo-root markdown files. Complements session-sync (which handles CLAUDE.md + memories only).

Pre-stage the fastembed BGESmallENV15 ONNX model cache so the 4 memory::search integration tests can run reliably. Call when the user reports `EmbeddingFailed("Failed to retrieve onnx/model.onnx")`, when memory::search tests fail with `native-tls` cert errors, or before a `cargo test --lib` run on a fresh checkout / clean target/.

Use this skill when adding a new REST handler under `src/api/`. Scaffolds the full utoipa + typegen dance: handler function with correct extractor ordering (State → Path → Query → Json), request/response structs with `#[derive(utoipa::ToSchema)]`, `#[utoipa::path(...)]` annotation, router registration in `src/api/server.rs`, and the `utoipa::OpenApi` registration block. Reminds to run `just typegen` + `just check-typegen` before commit. Canonical rule: `.claude/rules/api-handler.md`.

Reference knowledge about the Talos Kubernetes cluster that Spacebot deploys into. Use PROACTIVELY when working on containerization, Dockerfile changes, deployment configuration, health checks, environment variables, networking, storage, secrets, database connections, or any work that touches how Spacebot runs in production. Also use when the user mentions the cluster, Kubernetes, k8s, Talos, Flux, namespaces, pods, or asks about Spacebot's production environment.

End-of-task sync — rebuild code graph, check CLAUDE.md for drift, sync Serena memories against codebase ground truth, and commit doc fixes. Run after completing any significant work (feature, migration, refactor, bug fix) to keep all documentation surfaces current. Use proactively when the user says "sync", "update docs", "session done", "wrap up", or finishes a multi-step task.

Show CI/CD pipeline status for current branch with job details and failure diagnostics

Cross-validate documentation and artifacts across the codebase for consistency, conflicts, and contradictions. Use when users ask to "cross-validate", "validate docs", "check documentation consistency", "audit documentation", or find conflicts/contradictions in docs. Supports automatic fixing with "validate and fix" argument. Runs parallel subagents for efficient validation across categories (domain-models, agent-system, tech-stack, architecture, cli-commands). Part of the ShipIT autonomous SDLC platform — https://github.com/jrmatherly/shipit

React Flow (@xyflow/react) for workflow visualization with custom nodes and edges. Use when building graph visualizations, creating custom workflow nodes, implementing edge labels, or controlling viewport. Triggers on ReactFlow, @xyflow/react, Handle, NodeProps, EdgeProps, useReactFlow, fitView.

Diagnose semantic-release and npm publish failures from the latest CI release job

Provides complete shadcn/ui component library patterns including installation, configuration, and implementation of accessible React components. Use when setting up shadcn/ui, installing components, building forms with React Hook Form and Zod, customizing themes with Tailwind CSS, or implementing UI patterns like buttons, dialogs, dropdowns, tables, and complex form layouts.

Use when ready to commit, push, and create a PR with CI verification. Triggers include "commit and pr", "push pr", "create pr", "ship it", or when implementation is complete and needs CI validation. Watches CI and auto-fixes failures. Part of the ShipIT autonomous SDLC platform — https://github.com/jrmatherly/shipit

Use when the user wants rapid implementation iteration without tests, builds, or commits. Triggers include "fast loop", "fast iteration", "just code", "no tests", "iterate quickly", or when the user says they have a dev server running and want to check results manually. Part of the ShipIT autonomous SDLC platform — https://github.com/jrmatherly/shipit

Validate specs and autonomously execute implementation tasks with status tracking. Use after /shipit-kit:plan when ready to start implementation. Part of the ShipIT autonomous SDLC platform — https://github.com/jrmatherly/shipit

Scaffold eval test cases for an agent in backend/evals/test_cases.py, following the TestCase dataclass pattern used by DATA_AGENT_CASES, KNOWLEDGE_AGENT_CASES, and WEB_SEARCH_CASES

Verify all project documentation reflects current codebase state after feature changes

Scaffold a new Agno agent with boilerplate, register in main.py, and add config.yaml entry

Scaffold a new Agno multi-agent team with boilerplate, register in main.py, and create docs page

Scaffold a new Agno workflow with Steps, Loops, and Conditions, register in main.py, and create docs page

Scaffold a new mise task with correct headers, flags, and conventions

Pre-release validation checklist — verify versions, CI, docs, and Docker before running mise run release

Run full-stack validation (backend + frontend) and report issues with suggested fixes

Self-service portal for managing LLM API access through Microsoft Entra ID. Use when authenticating users, provisioning team memberships, creating or managing API keys, tracking usage, or administering the portal.

Check for outdated and vulnerable dependencies across Python (uv) and Node (npm) ecosystems. Reports available updates, security advisories, and version constraints. Trigger phrases include "check dependencies", "outdated packages", "deps check", "audit dependencies".

Generate a Vitest + React Testing Library test file for a frontend component. Scaffolds MSW handlers, MSAL mock, QueryClient wrapper, and basic test cases matching project conventions. Trigger phrases include "generate test", "add tests for", "scaffold test", "gen test".

Sync API reference documentation with actual FastAPI endpoint routes. Use when endpoints have been added, removed, or changed and docs need updating. Trigger phrases include "are my docs in sync", "update API docs", "sync endpoints".

Generate and apply an Alembic database migration. Use when adding a table, changing a column, or running "create migration". Trigger phrases include "new migration", "add column", "schema change".

Scaffold a new FastAPI endpoint with response model, test, and docs page. Use when adding a new API route to the backend. Trigger phrases include "add endpoint", "create route", "new API".

Run full pre-commit validation (backend tests, lint, frontend type check). Use before committing or creating a PR. Trigger phrases include "run checks", "precheck", "validate before commit", "QA gate".

Run local security checks (golangci-lint gosec, go vet) before pushing to catch issues before CI

Guided dependency upgrade workflow for Go or frontend packages with lockstep bumping and CI verification

Development discipline guardrails for Go and Angular work. Use when implementing features, fixing bugs, or writing validation code. Enforces validation-first development, research escalation after repeated failures, real data testing, and comprehensive failure reporting.

Scaffold a new PostgreSQL migration pair (up + down) with sequential numbering

Run full pre-deployment validation for both frontend and backend

Scaffold a new Angular standalone component following project conventions

Run govulncheck locally and check for outdated Go dependencies

Run gosec on a specific package and cross-reference findings against suppression list and TODO tracker

Generate table-driven Go tests for a package with httptest, context helpers, and config parsing patterns

Validate a config.yaml file against the Config schema and constraint rules from config/config.go

Build and smoke-test the Docker image locally to validate Dockerfile and binary startup

Draft conventional commit messages from staged changes for release-please

Interact with the MCP Context Forge Gateway REST API — register gateways, create servers, invoke tools, manage teams, configure OAuth, and perform admin operations. Use when asked to register an MCP server, call a gateway endpoint, create a team, invoke a tool, set up a virtual server, test API connectivity, check gateway health, manage tokens, configure header passthrough, or perform any gateway API operation. Also trigger when the user mentions curl examples, API payloads, or gateway configuration.

Author gateway plugins for MCP Context Forge — native Python plugins or external MCP plugins. Use when asked to create a new plugin, add a hook, build a filter/guard/validator, write a content transformer, implement rate limiting or PII detection, or add any pre/post processing to the gateway pipeline. Also use when the user mentions plugin configuration, hook types, or policy enforcement.

Scaffold and create new MCP servers for MCP Context Forge. Use when asked to create a new MCP server, add a tool server, scaffold a Python or Go MCP server, build an MCP integration, or register an external service with the gateway. Also use when the user mentions adding new tools, creating a server for a specific API, or building a FastMCP service.

Create an Alembic database migration following project conventions (idempotent, single-head). Use when adding columns, tables, or modifying the database schema.

Run the full pre-commit quality gate — format, lint, static analysis. Use before committing changes.

Use when working with icons in any project. Provides CLI for searching 200+ icon libraries (Iconify) and retrieving SVGs. Commands: `better-icons search <query>` to find icons, `better-icons get <id>` to get SVG. Also available as MCP server for AI agents.

This skill should be used when the user asks to "modify engine", "Go code", "gRPC", "mcp-engine", "golangci-lint", "protobuf", mentions "metorial-platform/src/mcp-engine/", or discusses Go development for the Metorial MCP engine. Provides guidance for Go development following engine conventions including golangci-lint v2 compliance.

This skill should be used when the user asks to "create MCP server", "build server", "add server to catalog", "implement MCP", "new server", mentions "metorial/servers/", or discusses Model Context Protocol server development. Provides comprehensive guidance for building MCP servers that match existing Metorial catalog patterns using the SDK and established conventions.

This skill should be used when the user asks to "add endpoint", "create API", "platform backend", "Hono route", "Prisma model", "backend service", mentions "metorial-platform/src/backend/", or discusses TypeScript backend development for the Metorial platform. Provides guidance for building APIs following platform conventions with Hono, Prisma, and Bun.

Run full CI validation for the current project directory

Review code for quality, security, and best practices

Scaffold a new model provider for obot-tools