fabric

TRIGGER when the user asks to upgrade the project to a newer or the latest version of Microbus, or to update the framework. Each Microbus release ships this one self-contained skill; it applies that release's single-version migration, then chains to the next release's copy of this skill until the target version is reached.

TRIGGER when user asks to create, scaffold, or initialize a new microservice.

How to choose the hostname of a new Microbus microservice. Referenced by the add-microservice and add-sql-microservice scaffolding skills (and, through their delegation to add-microservice, by add-python-microservice and import-openapi-microservice). Consult it whenever a microservice's hostname is being chosen.

Performs an architectural review of a microservice-based system built on the Microbus framework. Covers only cross-cutting, cross-microservice concerns - service boundaries, the dependency graph, coupling, cross-service consistency, data ownership, workflow composition, edge security, and system operations. Anything judgeable inside a single microservice directory belongs to the review-microservice skill and is out of scope here. Produces a structured report with findings and recommendations.

Reviews the microservices touched by a set of changes - by default the whole current feature branch versus its merge-base with main, plus any uncommitted work. Runs the review-microservice skill on each changed microservice and the review-architecture skill scoped to those microservices and their graph neighbors, then consolidates one report. Use before merging a branch or before committing working-tree changes.

Performs a thorough review of a single Microbus microservice. Checks for completeness, framework compliance, code quality, security, test coverage, documentation, API design, and data access performance. Produces a structured report with findings and recommendations.

TRIGGER when user asks to create a CRUD microservice, database-backed service, or a service to persist/store objects in SQL (MySQL, Postgres, MSSQL).

Runs the agent-guided tour of Microbus using examples. Use when the user asks to take the tour.

TRIGGER when user asks to add or modify a configuration property or setting, or to make a value configurable.

TRIGGER when user asks to add, create, or modify an API endpoint, function, or RPC, or a route that accepts typed arguments and returns typed results.

TRIGGER when user asks to listen for, subscribe to, or handle an event emitted by another microservice.

TRIGGER when user asks to add or modify a metric, counter, gauge, or histogram, or to track/measure an operation.

TRIGGER when user asks to fire, emit, or publish an event that other microservices can subscribe to.

TRIGGER when user asks to add a workflow step, agent step, agentic task, task endpoint, or workflow phase. "Agent step" and "workflow step" are interchangeable - a task is a single step of a workflow / agent, whether or not the surrounding workflow calls an LLM.

TRIGGER when user asks to add a recurring job, periodic task, scheduled operation, or ticker.

TRIGGER when user asks to add or modify a web handler, HTML page, file download, or raw HTTP endpoint that works with http.ResponseWriter/http.Request.

TRIGGER when user asks to define a workflow graph, create an agent or agentic workflow, orchestrate tasks, or build a multi-step process. "Agent", "agentic workflow", and "workflow" are interchangeable here - an LLM is not required for a workflow to be an agent (rule-based, deterministic, and LLM-driven workflows are all agents).

TRIGGER when the user asks to delegate to or integrate an external/third-party REST API, import an OpenAPI/Swagger document, or generate a microservice from an OpenAPI spec (by URL or pasted JSON/YAML). Produces a one-for-one delegating microservice and stores openapispecs.json in its directory so more endpoints can be imported later.

Run after completing any change to a microservice to bring its generated files, documentation, version, and topology diagram up to date. Skip if the skill you just followed already ran housekeeping as its final step.

TRIGGER when user asks to change the signature, route, method, arguments, or return type of an existing endpoint, config, metric, or ticker.

Use when a microservice's generated files are corrupted, outdated, or need to be rebuilt from scratch.

TRIGGER when user asks to remove, delete, or drop an endpoint, config, metric, ticker, or event from a microservice.

TRIGGER when user asks to add a Python-backed function endpoint to an existing Python-backed microservice.

TRIGGER when user asks to add a Python-backed workflow task to an existing Python-backed microservice.

TRIGGER when user asks to initialize, set up, or bootstrap a Microbus project. Scaffolds main/main.go, config files, agent files, .gitignore, VS Code launch config, Claude Code permissions, and the token-signing key.

TRIGGER when user asks to create a microservice that calls Python, runs ML inference, or uses Python libraries (PyTorch, pandas, sentence-transformers, numpy) for its core compute.

TRIGGER when user asks to add fields, properties, or columns to a SQL CRUD microservice's object.

TRIGGER when user asks to change, rename, or retype fields, properties, or columns of a SQL CRUD microservice's object.

TRIGGER when user asks to remove, drop, or delete fields, properties, or columns from a SQL CRUD microservice's object.

TRIGGER when user asks to rename the object type or struct used by a SQL CRUD microservice.

TRIGGER when user asks to rename the database table used by a SQL CRUD microservice.

TRIGGER when user asks to externalize, internationalize, or translate user-facing strings. Moves hardcoded display text into a text.yaml resource bundle for i18n support.