prometheus-patterns
PromQL queries, alerting rules, recording rules, Grafana dashboard JSON, SLO
PromQL queries, alerting rules, recording rules, Grafana dashboard JSON, SLO
OpenTelemetry setup, span context propagation, sampling strategies, Jaeger queries
Structured logging with Pino/Winston, OpenTelemetry tracing, metrics collection, Grafana dashboards, and alerting rules.
Defines the core development conventions for the Squad CLI tool (create-squad), a zero-dependency Node.js package that adds AI agent teams to any project. Covers the zero-dependency constraint, Node.js built-in test runner usage, fatal() error handling pattern, ANSI color constants, .squad/ file structure, Windows-compatible path construction, and init idempotency. Use when modifying Squad source code, adding new CLI commands, writing tests with node:test, handling errors in user-facing flows, or ensuring cross-platform file path compatibility.
Defines the core development conventions for the Squad CLI tool (create-squad), a zero-dependency Node.js package that adds AI agent teams to any project. Covers the zero-dependency constraint, Node.js built-in test runner usage, fatal() error handling pattern, ANSI color constants, .ai-team/ file structure, Windows-compatible path construction, and init idempotency. Use when modifying Squad source code, adding new CLI commands, writing tests with node:test, handling errors in user-facing flows, or ensuring cross-platform file path compatibility.
Enforce canonical migration standards for ASP.NET Web Forms to Blazor using BWFC. Covers target architecture (.NET 10, Server Interactive), database provider detection, event handler preservation, SelectMethod patterns, and page lifecycle mapping. WHEN: "migration standards", "target architecture", "render mode placement", "page base class", "Layer 1 vs Layer 2".
Migrate Web Forms data access and application architecture to Blazor Server. Covers EF6 to EF Core, Session state to scoped services, Global.asax to Program.cs, Web.config to appsettings.json, and HTTP handlers to middleware. WHEN: "migrate EF6", "session state to services", "Global.asax to Program.cs", "Web.config to appsettings", "data access migration".
Migrate ASP.NET Web Forms applications (.aspx/.ascx/.master) to Blazor Server using BlazorWebFormsComponents (BWFC). Use this skill when converting Web Forms markup, code-behind, Master Pages, User Controls, or data-binding patterns to Blazor equivalents.
Defines the canonical target architecture, BWFC control preservation rules, and migration patterns for converting ASP.NET Web Forms applications to Blazor Server on .NET 10. Covers WebFormsPageBase setup, render mode placement, database and identity migration, data control strategy, static asset relocation, and ListView template placeholder conversion. Use when running the bwfc-migrate.ps1 script, performing manual Layer 2 migration, debugging missing controls or broken page titles, or configuring _Imports.razor and Program.cs for a BWFC project.
Coordinate multi-agent development pipelines using shared JSON task files. Use when dispatching work across dev team agents (code-agent, test-agent, docs-agent, monitor-bot), tracking pipeline progress, or running sequential/parallel workflows. Covers project init, task assignment, status tracking, agent dispatch via sessions_send, and result collection. Supports two modes: linear (sequential pipeline) and dag (dependency graph with parallel execution).
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Manage Lean toolchain and Mathlib versions with backup, upgrade, and rollback support
Orchestrate multi-agent implementation with parallel phase execution. Spawns teammates for independent phases and coordinates dependent phases. Includes debugger teammate for error recovery.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Create scoped git commits for task operations. Invoke after task status changes or artifact creation.
Add new benchmarks to the CI pipeline. Guides through creating benchmark JSON files, integrating with bootstrap.sh, and ensuring proper CI upload via ci3.yml workflow.
Use when distributing Electrobun apps, configuring auto-updates, uploading artifacts, understanding update channels, or integrating the Updater API. Covers artifact naming, update.json format, bsdiff patch generation, upload targets, and the full Updater lifecycle.
Use when scaffolding a new Electrobun project, choosing a template, or understanding what each template provides. Activates on electrobun init, new project setup, or template questions.
Run the local maintainer release flow for this Changesets-based pnpm monorepo.