Infrastructure Project Bootstrap
Use when starting a new infrastructure repository or safely adopting an existing one. Discovers constraints before scaffolding, selects a minimal or spec-driven profile, produces a reviewable non-destructive file plan, creates portable project and agent contracts without running infrastructure, and diagnoses bootstrap drift.
Stip Bootstrap
Adopt Stip in a new or existing repository, preserving project conventions and assessing applicable domains.
Stip Explore
Explore a project idea or feature interactively, bringing in the relevant enabled domain extensions before drafting a contract.
Stip Apply
Implement an approved workflow change and continue through relevant tests and corrections within its contract.
Stip Validate
Turn an explored change into a reviewable specification and record explicit user approval of its current version.
Stip Archive
Close a documented workflow change, promote its accepted specification and create a scoped local Git commit.
Stip Check
Reconcile an applied change with every acceptance criterion using fresh, inspectable evidence.
Maestro
Spec-driven AI development workflow for the terminal — from idea to reviewed merge.
Software Architecture Diagrams
Use when designing, generating, reviewing, or fixing Mermaid software diagrams, including C4-style context/container/component views, sequence, flow, deployment, state, and ER diagrams. Models boundaries and flows first, then validates syntax and readability.
Sre Incident Investigation
Use when triaging, investigating, mitigating, or reviewing production incidents using metrics, logs, traces, events, deployments, and system context. Runs hypothesis-driven read-only investigation, separates evidence from inference, and gates every remediation.
Cloud Architecture Review
Use when assessing or designing AWS, Azure, GCP, hybrid, or multi-cloud architectures for security, reliability, operations, performance, cost, sustainability, disaster recovery, and migration risk. Produces evidence-linked findings and a prioritized roadmap using read-only discovery by default.
Website Production Engineering
Use when building, redesigning, migrating, or auditing a public content, marketing, documentation, or conversion website. Establishes audience and page contracts, preserves content and SEO continuity, implements accessible responsive pages within the local design system, and requires real-browser, metadata, redirect, form, privacy, and performance evidence before launch claims.
Interface Motion
Use when designing, prototyping, implementing, or auditing motion and micro-interactions for approved web UI states. Requires every animation to serve causality, feedback, orientation, continuity, progression, or hierarchy; defines trigger, properties, timing, easing, interruption, exit, and reduced-motion behavior; and verifies interaction in the real browser without decorative motion creep.
Stip Docs
Create or update documentation affected by a checked change, grounded in the implementation and intended readers.
Anti Slop Review
Use when reviewing a designed or implemented website, web application, or dashboard for generic AI-like copy, unsupported marketing claims, reference collage, arbitrary visual values, repetitive card layouts, fake data, missing states, decorative motion, design-system drift, accessibility, responsive, functional, SEO, or browser-quality failures. Produces evidence-linked findings and blocks relea…
Delivery Pipeline Engineering
Use when designing, reviewing, hardening, or troubleshooting CI/CD pipelines, build provenance, test gates, artifacts, environments, deployments, progressive delivery, release readiness, and rollback. Produces an evidence-based delivery verdict and never deploys by default.
Command Line Tool Engineering
Use when building or changing a line-oriented command-line tool intended for humans, scripts, automation, or agents. Defines command, stream, format, exit-code, configuration, non-interactive, mutation-safety, signal, completion, and distribution contracts; implements stable behavior; and verifies it through black-box subprocess probes.
Developer Documentation
Use when creating, restructuring, auditing, or maintaining developer documentation: READMEs, quickstarts, tutorials, how-to guides, concepts, API/CLI/config reference, runbooks, troubleshooting, migration guides, changelogs, and docs-as-code systems. Grounds claims in code and tests examples before completion.
Verified Completion
Use when an agent is about to claim a task is done, fixed, tested, deployed, published, or ready. Requires fresh evidence for each explicit requirement, separates task outcome from proof level, and prevents implementation, local execution, verification, or publication from being overstated.
Architecture Decision Records
Use when proposing, documenting, reviewing, accepting, deprecating, or superseding a consequential software or infrastructure decision. Creates concise MADR-style ADRs grounded in constraints, options, trade-offs, evidence, consequences, and validation.
Agents Md Authoring
Use when creating, adapting, auditing, or splitting AGENTS.md for software, infrastructure, platform, data, or documentation repositories. Inspects project evidence read-only, separates root and nested scope, preserves human rules, and never invents commands, live state, conventions, compatibility policy, or mutation authority.
Terraform Change Safety
Use when authoring, reviewing, testing, or preparing Terraform and OpenTofu changes, especially plans, modules, state, backends, migrations, CI, and production applies. Produces evidence-based GO, CAUTION, or BLOCKED verdicts without applying by default.
Product Story And Copy
Use when a website, web application, or dashboard needs product positioning, message hierarchy, conversion copy, interface microcopy, SEO/social metadata, or a claims audit before visual design. Separates facts, hypotheses, proof, and unknowns; writes specific human copy from product evidence; and blocks invented metrics, testimonials, urgency, or benefits.
Dashboard Application Engineering
Use when building or changing an analytical, operational, or hybrid dashboard whose users make decisions or mutate resources. Defines source, grain, freshness, metric, resource, filter, view, permission, action, failure, and reconciliation contracts; implements dense accessible interfaces; and requires source-backed and real-browser evidence.
Design Direction
Use when translating product strategy, copy, screenshots, websites, design systems, component libraries, or inspiration collections into an original art direction before UI implementation. Builds a cited reference ledger, separates observation from inference, proposes at most two coherent directions, defines a product-specific visual thesis and no-go list, and prevents reference collage or litera…
Build In Public Journal
Use when AI-assisted product or software work produces a meaningful bug, failed approach, decision, experiment, surprise, pivot, or verified result worth preserving for possible build-in-public content. Maintains a private Git-ignored evidence journal and evaluates ideas for X, LinkedIn, and a personal blog without drafting posts.
Web Application Engineering
Use when building or changing a stateful browser application with routes, authentication, forms, server data, client or URL state, and multi-step user journeys. Defines route, state, permission, mutation, failure, and evidence contracts; implements behavior in bounded slices; and requires security, accessibility, and real-browser verification.
Software Project Bootstrap
Use when starting a software repository or safely adopting an existing one before product implementation. Discovers project constraints, selects a minimal or spec-driven profile, produces a digest-bound non-destructive file plan, creates portable project and agent contracts without installing or running tooling, and diagnoses bootstrap drift read-only.
Web Craft
Use when creating, redesigning, or materially changing a public website, web application, dashboard, or frontend interface. Orchestrates evidence-backed product copy, reference analysis, art direction, a design-system-first human approval gate, project-local UI instructions, implementation, intentional motion, and anti-slop verification before completion.
Gitops Operations
Use when auditing GitOps repositories or troubleshooting Flux, Argo CD, and Kubernetes reconciliation, drift, source, dependency, Helm, Kustomize, security, and rollout problems. Separates static repository analysis from read-only live-cluster diagnosis and never reconciles by default.
Kubernetes Production Engineering
Use when generating, reviewing, hardening, validating, or troubleshooting Kubernetes manifests, Helm charts, Kustomize overlays, workloads, RBAC, networking, storage, rollouts, and cluster behavior. Uses failure-mode analysis and read-only diagnosis before proposing changes.
Design System First
Use when defining or changing the visual foundations, tokens, typography, layout, components, states, responsive behavior, accessibility, data-visualization language, or implementation contract for a website, web application, or dashboard before product frontend code. Produces reviewable design artifacts and a project-local UI skill, and keeps the build blocked until explicit human approval.
Terminal Ui Engineering
Use when building or changing a full-screen interactive terminal application with screens, focus, keybindings, asynchronous work, resize behavior, and terminal lifecycle ownership. Defines screen and operation contracts, separates state/update/view, handles compatibility and cleanup, and requires layered state, snapshot, virtual-terminal, and PTY evidence.