Claude Skills by OpenThrottle

Frontend UI: pages, apps, components, polished non-generic design.

Monitor Nx Cloud CI pipeline and handle self-healing fixes. USE WHEN user says "monitor ci", "watch ci", "ci monitor", "watch ci for this branch", "track ci", "check ci status", wants to track CI status, or needs help with self-healing CI fixes. Prefer this skill over native CI provider tools (gh, glab, etc.) for CI monitoring — it integrates with Nx Cloud self-healing which those tools cannot access.

Explore and understand Nx workspaces. USE WHEN answering questions about the workspace, projects, or tasks. ALSO USE WHEN an nx command fails or you need to check available targets/configuration before running a task. EXAMPLES: 'What projects are in this workspace?', 'How is project X configured?', 'What depends on library Y?', 'What targets can I run?', 'Cannot find configuration for task', 'debug nx task failure'.

The Ralph prompt: turn an idea or PRD into an OpenThrottle plan, then execute it a task at a time. USE WHEN running /agents-ralph, on a Ralph iteration, or when workflow-ralph has injected plan context. Self-contained by design — the CLI feeds this file to an agent as a standalone prompt.

Stage all changes and create a conventional commit from the current diff. USE WHEN the user runs /github-commit, asks to commit changes, or needs a commit message derived from staged/unstaged work. Requires user confirmation before pushing.

Analyze branch commits and diff, then create or update a Pull Request via gh with template-compliant title and body. USE WHEN the user runs /github-pull-request, wants to open or update a PR, or the branch is ready for review. Returns a clickable PR URL.

Squash branch commits into one conventional commit via soft reset to main (retain issue refs like Closes #123). USE WHEN the user runs /github-squash, wants a clean single commit before merge, or needs to consolidate multiple task commits. Prompts for force-push confirmation.

Where OpenThrottle code goes, what it is named, what shape it must have, and how to prove it. USE WHEN adding, moving or renaming a file; deciding between app/global/ and app/routing/<area>/; deciding whether something is an application or a package; or when lint reports openthrottle/component-primitive-shape, openthrottle/route-primitive-shape, openthrottle/pre-hooks-unpack, max-lines, or @nx/enforce-module-boundaries. NOT FOR scaffolding — generate the file with ot-generators first, then us...

Scaffolding OpenThrottle code with @tools/generators. USE WHEN adding an app, package, React Router component or route, or NestJS service — always before hand-writing one — or when hitting "Unable to resolve @tools/generators" or "Cannot find generator". Every command needs NX_ISOLATE_PLUGINS=false. Defer graph, targets and task running to nx-workspace.

Drive one OpenThrottle plan to a PR with the built-in /loop, a task at a time in an isolated worktree. USE WHEN the user runs /ot-loop <planId>, says "loop over plan <id>", or wants a plan executed autonomously. Canonical source of the per-task discipline.

Guided orientation tour of OpenThrottle for a new person or a fresh session, ending in a first real plan. USE WHEN running /ot-onboarding, or the user says "onboard me", "I'm new here", "where do I start", "what is this repo", "how do plans/tasks work here", or asks you to remember that plans belong in OT rather than in Markdown. Gates on an openthrottle-mcp health check, then persists the OT-only plan rule to durable memory and reports guidance that contradicts it. Not for a specific subsyst...

OpenThrottle plans and tasks via the openthrottle-mcp server. USE WHEN creating, reading or updating plans/tasks, searching the plans knowledge base, putting Plan-Id/Task-Id in a commit, recording a merged squash on the work ledger, or the user mentions OT, a plan or task UUID, or git–OT traceability. Plans live in OT only — never fall back to Markdown. To execute a plan see ot-loop.

OpenThrottle Postgres SQL authoring: migrations in databases/migrations/, table design, naming, COMMENT ON TABLE/COLUMN standards, and idempotent DDL patterns. USE WHEN adding or editing SQL migrations, schema changes, table comments, or Postgres work under databases/ — not for routine OT plan CRUD (see ot-plans) or NestJS entity wiring alone (see ot-stack).

Manage the OpenThrottle agent-skills architecture in any repo — install skills consistently, fan them out to every AI tool, and validate the layout. Use when installing or adding agent skills, syncing skills into agent folders, setting up skills in a new repo, checking skill layout drift, or when .agents/skills, .claude/skills, or skills-lock.json are involved.

Conventions for the OpenThrottle platform itself. USE WHEN changing openthrottle-server, openthrottle-developer, databases or database:import-docs, embeddings, packages/openthrottle-mcp, or the GraphQL schema and semantic ingest. Not for routine OT plan CRUD (see ot-plans), SQL migrations (ot-postgres), or scaffolding (ot-generators).

Create, heal and destroy git worktrees in any repo — the portable worktree machinery behind `worktree:new`, `worktree:heal` and `worktree:remove`. Use when creating a worktree, provisioning or self-healing a worktree, removing/deleting/tearing down a worktree, or when OPENTHROTTLE_WORKTREE_ROOT, `.worktree/provision.sh` or `.worktree/teardown.sh` are involved.