Browse Skills

Provides guidelines for writing idiomatic Rust code, covering borrowing, error handling, performance, testing, and documentation. Use when writing, reviewing, or refactoring Rust code.

Performs read-only root cause analysis for bugs, test failures, and unexpected behaviors. Produces a brief identifying the root cause, files to change, approach, and risks, without making any edits or state changes.

Surveys how best-in-class ERPs and point solutions implement a feature, producing a structured findings file. Use when designing a new feature, evaluating approaches, or answering industry-standard questions.

Break a large pull request into smaller, reviewable PRs (stacked or parallel) while preserving all original work. Use when a PR is too big, mixes refactors with features, or requires incremental delivery.

Generates a self-contained HTML page that explains a pull request's purpose, changes, and verification, helping reviewers quickly understand complex changes without reading the full diff.

Creates a detailed, executable implementation plan from a finalized specification, breaking down work into verifiable tasks with exact file paths, commands, and expected outputs. For use in agent-assisted development workflows to plan implementation steps before execution.

Design engineering principles for making interfaces feel polished. Use when building UI components, reviewing frontend code, implementing animations, hover states, shadows, borders, typography, micro-interactions, enter/exit animations, or any visual detail work.

Reference for Inngest v3 durable functions in Carbon. Use when writing or reviewing Inngest functions, managing concurrency, throttling, debouncing, and debugging retries in Carbon's background jobs.

Audits the Carbon codebase as a senior advisor to surface improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX) and produces self-contained implementation plans for other AI agents to execute. Strictly read-only; never modifies code.

Interviews the user relentlessly, one question at a time, to resolve every open decision in a plan, spec, or design idea. Cross-checks answers against the codebase and domain glossary, records resolutions immediately, and surfaces contradictions. Supervised use only.

Orchestrates the bug-fix lifecycle from root cause analysis to implementing and proving the fix with a mandatory red→green regression test. Use when fixing a bug, test failure, or unexpected behavior.

Orchestrates the complete feature lifecycle from research and spec writing to plan, build, test, and self-review. Supports autonomous and approval-based modes with structured run records.