Browse Skills

Surveys how best-in-class ERPs implement features and produces a structured findings file. Use before designing ERP-domain features like accounting, inventory, or manufacturing.

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.

Performs read-only root-cause analysis for bugs, test failures, or unexpected behavior, producing a structured brief with the cause, files to change, approach, and risks. Use before proposing any fix or when the cause isn't proven.

Rust coding conventions for Carbon's cargo workspace, emphasizing safe async/FFI patterns, ownership choices, error handling, and performance profiling when working with OpenCASCADE and FCL bridges.

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

Critically reviews your own branch diff against main before opening or merging a PR, identifying must-fix issues, risks, improvements, and docs-freshness checks. Supports an opt-in strict thermo-nuclear mode for deep maintainability audits.

Quick end-to-end smoke test of the local Carbon ERP dev server: logs in and verifies core modules (dashboard, sales, purchasing, etc.) render without errors. Use after booting, broad changes, or when asked to smoke test.

Guides feature design by researching competitors, surfacing open questions, and interviewing stakeholders before writing the spec. Use for new modules, data model changes, or changes across 3+ files.

Guides feature design and spec writing by researching competitors, making design decisions, and resolving open questions before writing the spec document. Use for new features, modules, data model changes, or cross-module changes.

Supabase Postgres Best Practices covers query, schema, connection, and RLS guidance for Postgres. Use it when writing, reviewing, or tuning SQL and database configuration.

Test-Driven Development enforces writing a failing Vitest test before production code in Carbon. Use it for features and bug fixes when you need a regression-safe red→green→refactor loop.

Translate fills missing Lingui .po msgstr entries in locale catalogs using cheap Haiku subagents, then merges and verifies the results. Use it after adding UI strings or when you need to run the translation workflow without overwriting existing translations.