ph-build

Plugin ph-build from marketplace photon-plugins in mattlindell/photon-plugins. Commands read from the repo's manifest — 2 days ago.

Skills (59)

• architect

  Sketch types, signatures, and module structure before code, exploring alternatives across a panel, then stay in the loop while implementation fills in.

• arena

  Spawn parallel candidates at the same task, pick a base, and graft the strongest parts of the losers into it.

• babysit

  Watch an open PR — fix failing CI, handle the straightforward review comments, and drive it to a mergeable state. Claude Code analog of Cursor's built-in /babysit. Use after opening a PR when the user wants the agent to shepherd it without re-prompting.

• benchmark-checklist

  Vet a perf measurement (limiter, tuning, limits, errors, repeatability, relevance, and whether the work happened) before you report or act on it. Use when you run a benchmark or report a speedup or regression you measured.

• blast-radius

  Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', reviewing a small diff you don't trust, or a brief that asserts something a

• claude-md

  Use when creating a new CLAUDE.md, auditing an existing CLAUDE.md for quality, or triaging session learnings into CLAUDE.md, rules, or memory

• code-review

  Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them

• commit

  Use when the user asks to commit changes, write commit messages, or review staged work for committing

• correct

  Find the mistakes agents keep repeating in this repo and make each one impossible, at the highest level that works, with every check proven to fail on a real past mistake.

• create-verification-skill

  Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for /create-verification-skill, \"make a control skill for this repo\", or when a project has no scripted way to prove UI/CLI/service behavior.

• deslop

  Remove AI-generated code slop and clean up code style

• diagnosing-bugs

  Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

• dispatch

  Entry point for building something. Reads how much was already decided, sizes the rigor to what is left, and routes to a playbook. Use before any non-trivial code change — a feature, bug fix, refactor, migration, or performance work.

• explain

  Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.

• figure-it-out

  Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a human reviews after stepping away. Scales rigor to the task, runs a hypothesis loop, and logs decisions via show-me-your-work. Use for /figure-it-out, 'figure it out', a large migrati

• fix-ci

  Find failing PR checks, inspect logs or external check links, and apply focused fixes

• fix-merge-conflicts

  Resolve merge conflicts non-interactively, validate build and tests, and finalize conflict resolution

• get-pr-comments

  Fetch and summarize review comments from the active pull request

• git-guardrails-claude-code

  Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.

• how

  Use for \"how does X work\", code walkthroughs before changing something, and placement / ownership / layering questions (\"where should this live\", \"which package owns this\", \"is this the right layer\"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motiva

• interrogate

  Multi-model adversarial review — independent reviewers challenge a change from different angles to surface blind spots.

• maintain-verification-skill

  Periodic audit that keeps a project's verification skill and feature map honest against the real app.

• make-pr-easy-to-review

  Prepare PRs for review by cleaning noisy history, improving PR descriptions, and adding reviewer guidance without changing code behavior. Use for "make this easy to review", "tidy this PR", "clean up commits", or "annotate the diff".

• no-comments

  Spawn the comment-sicko subagent, fix accepted findings, and offer encodings for claimed constraints.

• principle-attack-the-premise

  Apply when two or more fixes that share one premise have failed the same gate. Write the premise down and test it directly before you write another fix that assumes it.

• principle-boundary-discipline

  Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust internal types and keep business logic in pure functions.

• principle-build-the-lever

  Apply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks. Build the tool that does it or proves it (codemod, script, generator, or a skill your subagents follow) instead of working by hand. The tool is the artifact a reviewer can rerun.

• principle-encode-lessons-in-structure

  Apply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the rule as a lint, metadata flag, runtime check, or script instead of more text.

• principle-exhaust-the-design-space

  Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3 competing prototypes and compare side by side before committing.

• principle-experience-first

  Apply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.

• principle-explain-the-number

  Apply before you trust, report, or act on a number you measured: a speedup, a regression, a throughput, a latency, or an eval result. Find what limits it, and rule out that it measured something other than the work you think.

• principle-fix-root-causes

  Apply when debugging. Trace each symptom back to the first place the system went wrong and fix it there. A guard is a fix only when the state it handles is legitimate.

• principle-foundational-thinking

  Apply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data structures right so downstream code becomes obvious.

• principle-guard-the-context-window

  Apply when context is filling up: large outputs, long files, repeated reads, fan-out planning. Route bulk to subagents; keep summaries in the main thread, not raw payloads.

• principle-laziness-protocol

  Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that solves the problem.

• principle-make-operations-idempotent

  Apply when designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries. Converge to the same end state regardless of partial prior runs.

• principle-migrate-callers-then-delete-legacy-apis

  Apply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the same wave instead of preserving compatibility layers.

• principle-minimize-reader-load

  Apply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state in the reader's head; collapse one-caller wrappers and shrink mutable scope.

• principle-model-the-domain

  Apply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files. Encode the domain in a structure instead of scattered conditionals.

• principle-never-block-on-the-human

  Apply when tempted to ask 'should I do X?' on reversible work. Proceed, present the result, let the human course-correct after the fact; reserve confirmation for irreversible actions.

• principle-outcome-oriented-execution

  Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't preserve smooth intermediate states with throwaway compatibility code.

• principle-prove-it-works

  Apply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the actual value, inspect the diff), not a proxy, self-report, or 'it compiles.'

• principle-redesign-from-first-principles

  Apply when integrating a new requirement into an existing design. Redesign as if the requirement had been a foundational assumption from day one, instead of bolting it on.

• principle-separate-before-serializing-shared-state

  Apply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first; serialize structurally only when one shared writer is a real invariant.

• principle-sequence-verifiable-units

  Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work into small units that each end in a verifiable state, check each before the next, and order delivery so the sequence proves itself to a reviewer.

• principle-subtract-before-you-add

  Apply when sequencing an addition, refactor, or rewrite. Remove dead code, redundant validators, and stub references first, then build on the simpler base.

• principle-test-behavior-not-implementation

  Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.

• principle-type-system-discipline

  Apply when designing types, reviewing a function signature, or writing code in any statically-typed language. Make illegal states unrepresentable, brand semantic primitives, parse external data at boundaries, refuse to lie to the compiler, exhaust variants, derive from authoritative schemas.

• setup-ph-build

  Detect the harness, map the five effort tiers onto models it can actually reach, and write the fan-out policy that every ph-build skill reads.

• setup-pre-commit

  Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.

• show-me-your-work

  Keep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why, evidence, result). Local by default; commit it when a reviewer needs the trail to trust the result. Use for /show-me-your-work, autonomous or multi-phase runs, or work a human review

• swarm

  Fan out parallel workers over a partitioned job, drain them, and return one report.

• tdd

  Test-driven development. Use when building a feature or fixing a bug, when the user mentions "red-green-refactor" or wants integration tests, or whenever code is about to be written without a test in front of it.

• thermo-nuclear-code-quality-review

  Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth.

• thermo-nuclear-review

  Run an extremely thorough security and correctness audit of a branch's changes for bugs, breakage, devex regressions, and feature-gate leaks.

• typescript-best-practices

  TypeScript best practices. Use when reading or editing any .ts or .tsx file.

• why

  Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, prod

• wizard

  Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can pe

• worktree

  Create, enter, and remove git worktrees following sibling-directory placement rules with branch-name mirroring, source-branch verification, and post-creation file copying. Use when the user asks to create a worktree, start work in a worktree, work on a feature in isolation, set up a sibling checkout

Subagents (3)

• code-review

  Use this agent when a pull request or branch is handed over to be reviewed with no further instruction, and the changes should be checked against both the repo's coding standards and the spec that originated them. Typical triggers include a task thread opened from a PR, "review PR #42", "review this

• comment-sicko

  A deranged comment-hater that savors deletion and condemns workaround code.

• implement

  Use this agent when a ticket is handed over to be built with no further instruction — a Jira or Linear key, a GitHub/GitLab issue, or a spec file — and the work should be implemented test-first, reviewed, and shipped. Typical triggers include a task thread opened from a tracker ticket, "implement TE

Hooks (1)

• SessionStart

  cat "${CLAUDE_PLUGIN_ROOT}/hooks/session-start-context.md"

Similar plugins