Browse Skills

Log into the local Carbon ERP dev server with agent-browser using the DEV_BYPASS_EMAIL bypass. Use before any browser automation that needs an authenticated session.

Drives a single work item through a doer→gate→judge→keep-or-revert→ledger cycle to produce a gated pull request, unattended. Use when asked to autonomously build or fix a tightly-scoped item with acceptance criteria.

Orchestrates the complete feature development lifecycle from research and planning to execution and review. Use for building new features in structured phases with autonomy mode options.

Reference for writing and reviewing Inngest durable functions with v3 syntax. Covers steps, events, flow control (concurrency, throttle, debounce, singleton, batch), and debugging retries.

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task.

Authenticate against a local Carbon ERP dev server using the DEV_BYPASS_EMAIL bypass with agent-browser. Used as a prerequisite for automated tests that require an authenticated session.

Executes an approved implementation plan task by task, running verifications and committing each task via a check-and-commit gate. Use after /plan approval for automated, verifiable implementation of software plans.

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.

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.

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.

Create a Jira bug ticket in the LPD project through the REST API. Use when the user asks to create or file a Jira bug or LPD ticket.

Creates a task ticket in the LPD Jira project automatically via REST API. Useful when a user wants to quickly generate a Jira task from a commit hash or description, inferring components and formatting details.