PrabhdeepSingh

PrabhdeepSingh/claude-plugins

Plugin Claude Code

Prabhdeep Singh's personal AI coding-agent tools.

PrabhdeepSingh/claude-plugins

Command Claude Code

Prepare a release of the sonu plugin — decide the semver bump, sync the version and plugin description across all five homes, run /validate, then hand to /sonu:ship. Only meaningful inside the claude-plugins repo; in any other repo, say so and stop.

PrabhdeepSingh/claude-plugins

Command Claude Code

Mechanically validate the sonu plugin repo before a PR — manifest sync, YAML frontmatter, shell-fence syntax, named-source and AI-attribution scans, cross-reference integrity, skill reachability. Only meaningful inside the claude-plugins repo; in any other repo, say so and stop.

PrabhdeepSingh/claude-plugins

Skill Claude CodeCodex

The maintainer's handbook for the sonu plugin and the claude-plugins repo. INVOKE whenever authoring, editing, reviewing, or releasing any component in this repo — a skill's SKILL.md, a command file (under sonu/commands/ or .claude/commands/), a manifest, or the README — or when answering how the plugin's pieces fit…

PrabhdeepSingh/claude-plugins

Plugin Claude Code

Make your coding agent work like a senior teammate instead of an eager intern. /sonu:build writes every change in your style and test-first, then hands it back with the riskiest parts flagged before you review. /sonu:ship takes it from working tree to merged PR on its own — collecting every AI reviewer bot enabled on…

PrabhdeepSingh/claude-plugins

Command

Sequence decide → build → hand back for any feature or fix. Triage the change, run design-tree in plan mode (with you as the approval gate — skipped when /sonu:factory routes a ticket whose spec you already approved), build test-first under code-standards, then surface the riskiest parts before handing back to…

PrabhdeepSingh/claude-plugins

Command

Run one pass of the ticket queue — scan the tracker for human-authorized tickets, claim one, and route it to the right workflow (spec a raw ticket, groom the backlog, hunt a bug, or build an approved spec in its own worktree via /sonu:build). You are the trigger; there is no daemon. Never merges and never authorizes…

PrabhdeepSingh/claude-plugins

Command

Branch, commit, open PR, gather Claude + every enabled AI reviewer (Copilot, CodeRabbit, etc.), fix/justify/resolve every finding, loop until clean, then merge. Run only when implementation is finished AND the owner has said to ship (e.g. "ship it") — never self-invoke just because the work looks done. To design and…

PrabhdeepSingh/claude-plugins

Skill Claude CodeCodex

Accessibility engineering for product interfaces — keyboard support, focus states, ARIA, forms, screen readers, hit areas, motion and zoom. INVOKE PROACTIVELY when building or reviewing any UI component, modal, menu, form, or custom widget, and on any keyboard or screen-reader complaint — even when nobody says "a11y".…

PrabhdeepSingh/claude-plugins

Skill Claude CodeCodex

Consumer-impact discipline for contract changes — enumerate every consumer, flag the ones that degrade silently, verify one downstream path end-to-end before shipping. INVOKE PROACTIVELY when a change alters anything other code reads — return shapes, payloads, DB columns, telemetry fields, config values — or renames a…

PrabhdeepSingh/claude-plugins

Skill Claude CodeCodex

Hunt for one real, previously unreported defect and file it as a well-evidenced ticket — proactive discovery, not reactive diagnosis. INVOKE when asked to sweep code for bugs or hunt risky areas, and when /sonu:factory runs a bug-hunt pass. A known symptom is [[debugging]]; a pending diff is [[self-review]]. It files…

PrabhdeepSingh/claude-plugins

Skill Claude CodeCodex

Backlog hygiene as a sweep — exactly one type and one evidence-based priority per open ticket, and nothing else changes. INVOKE when grooming or prioritizing a backlog, when classifications have drifted, or when /sonu:factory runs a classify pass. Not per-ticket spec work ([[ticket-triage]]) or defect discovery…

PrabhdeepSingh/claude-plugins

Skill Claude CodeCodex

Prabhdeep (Sonu) Singh's personal coding standards — the house rules and quality bar for how code gets written. INVOKE before writing, generating, refactoring, or reviewing ANY code in ANY language — schemas, endpoints, queries, logging, validation, error handling — even when nobody says "standards" or "style".…

PrabhdeepSingh/claude-plugins

Skill Claude CodeCodex

Color systems for web interfaces — OKLCH conversion and palette generation, contrast measurement (APCA/WCAG), gamut and P3 fallbacks, theming, one meaning per color. INVOKE PROACTIVELY when converting color values, building or extending a palette or token set, checking or reporting contrast, or theming light and dark…

PrabhdeepSingh/claude-plugins

Skill Claude CodeCodex

The scientific debugging loop — reproduce first, pull the real event from the repo's observability stack, one hypothesis → one change → one observation, revert failed attempts, escalate instead of thrash. INVOKE PROACTIVELY when diagnosing any bug, error, stack trace, failing or flaky test, crash, regression, or…

PrabhdeepSingh/claude-plugins

Skill Claude CodeCodex

Make design decisions as an explicit branching tree — genuine alternatives, decisive rationale, rejected branches preserved. INVOKE PROACTIVELY when planning or designing any implementation approach, or choosing between architectures, libraries, or data models — especially in plan mode. Skip trivial or forced changes…

PrabhdeepSingh/claude-plugins

Skill Claude CodeCodex

Infrastructure, container, and CI/CD discipline — IaC, Dockerfiles and compose files, CI pipelines, platform deploy config, env/secrets handling. INVOKE PROACTIVELY when creating or editing any such file (.tf, .bicep, Dockerfile, docker-compose, .github/workflows/, vercel.json) — even when nobody says "infra". Not for…

PrabhdeepSingh/claude-plugins

Skill Claude CodeCodex

Pre-spec intent extraction — one question at a time, each with a guess attached, until you can predict the user's answers; for when the asked-for artifact itself might be wrong. INVOKE when a request's outcome, audience, or success measure is genuinely unclear. NOT ticket speccing ([[ticket-triage]]), choosing…

PrabhdeepSingh/claude-plugins

Skill Claude CodeCodex

Cross-discipline review of a whole screen, flow, or feature — coordinates [[accessibility]], [[layout]], [[ux-writing]], [[typography]], [[colors]], and [[ui-polish]] into one ranked findings table and a single verdict. INVOKE for a holistic interface review or UI audit; quick and full modes. Orchestration only — it…

PrabhdeepSingh/claude-plugins

Skill Claude CodeCodex

Layout structure for web interfaces — grouping, alignment, negative space, reading order, progressive disclosure, breakpoints, direction-aware (RTL) structure. INVOKE PROACTIVELY when structuring a page or component, spacing or aligning controls, deciding what collapses at small sizes, or reviewing frontend structure.…

PrabhdeepSingh/claude-plugins

Skill Claude CodeCodex

Tag each plan step with the cheapest model tier that can execute it reliably, then delegate tagged steps to subagents at execution — keeping an orchestrator-class session clean for judgment, integration, and review. INVOKE when writing an implementation plan or executing one whose steps carry…

PrabhdeepSingh/claude-plugins

Skill Claude CodeCodex

Producing telemetry worth having — metrics, traces, error capture, health-check endpoints, and alerts that page on user-facing symptoms. INVOKE PROACTIVELY when creating a service, endpoint, or background job, or adding instrumentation, dashboards, health endpoints, or alert rules — "add monitoring/logging/alerting".…

PrabhdeepSingh/claude-plugins

Skill Claude CodeCodex

Performance work as measurement discipline — baseline first, one change at a time, beat the noise, and a keep/revert verdict where neutral is a revert. INVOKE when making anything faster or lighter, investigating slowness, or reviewing an optimization — "optimize", "too slow", "reduce latency/bundle size" — even…

PrabhdeepSingh/claude-plugins

Skill Claude CodeCodex

Author PR descriptions from the right per-change-type template (the repo's own PULLREQUESTTEMPLATE wins), embed issue-tracker links, keep the description current as fixes land, and reply to human and bot review threads. INVOKE when opening or updating a PR or responding to reviewer comments — inside /sonu:ship or…