0xbigboss-claude-code

Plugin 0xbigboss-claude-code from marketplace cascade-featured in joshuarweaver/cascade-featured. Commands read from the repo's manifest — 1 month ago.

Skills (30)

• atlas-best-practices

  Use when working with atlas.hcl, Atlas CLI commands, schema HCL/SQL files, or migration planning and reviews, including Atlas v1.1 security, data, and exporter capabilities.

• axe-ios-simulator

  Use when automating iOS Simulator interactions, capturing screenshots/video, or inspecting accessibility via AXe CLI.

• brief-best-practices

  Use when creating, reviewing, or updating a BRIEF.md (the quality law for a surface), defining what "good"/shippable means, or setting up a verified autonomous loop.

• canton-network-repos

  Use when working with Canton Network participants, DAML smart contracts, Splice applications, or debugging LF version and package ID issues.

• e2e

  Use when running e2e tests, debugging test failures, or fixing flaky tests. Covers failure taxonomy, fix rules, and workflow. Never changes source code logic or API without spec backing.

• electrobun-best-practices

  Use when building or maintaining Electrobun desktop apps in TypeScript, including electrobun.config.ts, electrobun/bun or electrobun/view imports, BrowserWindow/BrowserView usage, updater flows, and distribution artifacts.

• git-best-practices

  Use when creating commits, managing branches, opening PRs, or rewriting history. Not for non-git implementation tasks or repo-specific release policy decisions.

• git-rebase-sync

  Use when syncing a feature branch onto the latest origin base branch via git rebase.

• git-worktree-tidy

  Fetch latest from origin, prune remote-tracking refs, delete stale local branches and worktrees, and fast-forward important branches. Use when tidying up a worktree-based repo layout.

• go-best-practices

  Use when reading or writing Go files (.go, go.mod).

• improve

  Use after completing a task, before claiming done, before handoff, or when asked "what are some improvements?" Surfaces concrete suggestions grounded in session observations.

• ios-device-toolkit

  Use when interacting with USB-attached iOS devices via pymobiledevice3 — screenshots, syslog, crash reports, app install/launch/pull, file transfer, sysmon perf, TCP port forwarding, WebInspector/CDP, and device diagnostics.

• nix-best-practices

  Use when working with Nix flakes, overlays, shell.nix, or flake.nix files.

• op-cli

  Use when reading from 1Password, discovering vaults/items, rotating secrets, or piping credentials to other tools via op CLI.

• orbstack-best-practices

  Use when working with OrbStack Linux VMs, Docker on macOS, orbctl commands, or orb machine lifecycle.

• playwright-best-practices

  Use when writing or modifying Playwright tests (.spec.ts, .test.ts with @playwright/test imports).

• python-best-practices

  Use when reading or writing Python files (.py, pyproject.toml, requirements.txt).

• react-best-practices

  Use when reading or writing React components (.tsx, .jsx files with React imports).

• spec-best-practices

  Use when creating, reviewing, or updating SPEC.md files, running /specout, or entering the ADF SPEC gate.

• tamagui-best-practices

  Use when working with Tamagui projects (tamagui.config.ts, @tamagui imports).

• testing-best-practices

  Use when designing tests, writing test cases, or planning test strategy for a module. Covers unit, integration, and e2e layering.

• tilt

  Use when checking deployment health, investigating errors, reading logs, or working with Tiltfiles. Queries Tilt resource status, logs, and manages dev environments.

• tiltup

  Use when starting tilt, debugging Tiltfile errors, or bootstrapping a dev environment. Starts Tilt in zmx, monitors bootstrap to healthy state, fixes Tiltfile bugs without hard-coding or fallbacks.

• typescript-best-practices

  Use when reading or writing TypeScript or JavaScript files (.ts, .tsx, .js, tsconfig.json).

• web-fetch

  Fetches web content as clean markdown by preferring markdown-native responses and falling back to selector-based HTML extraction. Use for documentation, articles, and reference pages at http/https URLs.

• zig-best-practices

  Use when reading or writing Zig files (.zig, build.zig, build.zig.zon).

• zmx

  Use when starting dev servers, watchers, tilt, or any process expected to outlive the conversation. Provides zmx session management patterns for long-lived processes.

• dispatching-parallel-agents

  Use when there are multiple independent subtasks that can progress in parallel without overlapping ownership or blocking the next local step

• writing-plans

  Use when requirements are clear enough to plan and the work spans multiple steps, files, or verification stages

• writing-skills

  Use when creating or editing a skill and you need it to be discoverable, concise, and native to the target harness

Slash commands (8)

• /0xbigboss-claude-code:brb

  Use when the user signals they're stepping away (brb, afk, heading out) — keep working autonomously, skip anything that needs interactive approval, handoff when done or blocked.

• /0xbigboss-claude-code:commit

  Create a git commit

• /0xbigboss-claude-code:fix-issue
• /0xbigboss-claude-code:greenline

  Sequenced tilt bootstrap then e2e test baseline improvement. Runs tiltup workflow, then e2e test loop with categorized fixes and conventional commits. Not for unit-test-only projects or non-tilt dev environments.

• /0xbigboss-claude-code:handoff

  Generate concise handoff summary with context

• /0xbigboss-claude-code:rewrite-history
• /0xbigboss-claude-code:specout

  Interview to fill gaps in a specification file

• /0xbigboss-claude-code:triage

  Interactive Linear issue triage with codebase verification. Lists issues, verifies implementation status via Explore agents, and updates issue states.

Subagents (4)

• code-reviewer

  Reviews code for quality, security, and adherence to project conventions. Use after writing or modifying code, or when explicitly requested.

• debugger

  Investigates errors, test failures, and unexpected behavior through root cause analysis. Use when encountering failures or errors.

• refactorer

  Restructures code with clean breaks and complete migrations. Use when renaming, extracting, or changing interfaces.

• test-writer

  Writes unit, integration, and e2e tests that verify correctness without gaming assertions. Use when adding test coverage or writing new tests.

Similar plugins