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…
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".…
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…
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…
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…
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".…
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…
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…
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…
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…
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…
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…
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.…
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…
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".…
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…
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…
Skill Claude CodeCodex
Zero-downtime schema and data migration discipline — expand → migrate → contract, never destructive in the release that ships the code, backfills as jobs, every step reversible. INVOKE PROACTIVELY when creating or editing a migration in any framework, writing ALTER TABLE / index / enum / constraint changes, planning a…
Skill Claude CodeCodex
Build-time security discipline — threat-model before controls, Always/Ask-First/Never boundary tiers, SSRF, supply chain, LLM/agent security, privacy. INVOKE PROACTIVELY when building anything touching auth, user data, uploads, outbound fetches, dependencies, or model output — even when nobody says "security". The…
Skill Claude CodeCodex
Surface the riskiest parts of the current diff so a reviewer knows where to look hardest — one inline pass on small diffs, parallel review lenses with adversarial synthesis on substantial ones. INVOKE PROACTIVELY whenever a change is finished and about to be handed off, reviewed, or shipped. It points attention …
Skill Claude CodeCodex
SEO for anything served as a web page — the plumbing (templates, routes, redirects, metadata, JSON-LD, sitemaps, robots.txt) and the prose (posts, guides, landing copy, docs) so pages rank and get cited by AI answer engines. INVOKE when creating or editing page templates (HTML/JSX/TSX/Vue/Svelte/Astro), routes…
Skill Claude CodeCodex
Test-driven development — the red-green-refactor discipline for code that's correct by design, not by accident. INVOKE PROACTIVELY whenever writing or changing code, fixing a bug, adding or structuring tests, or choosing what to mock — even when nobody says "TDD" or "tests". (Tests are code held to…
Skill Claude CodeCodex
The ticket-as-control-plane rulebook — the single home for the tracker-operations contract, tracker resolution, the type/priority taxonomy, human-only trigger authorization, derived status, and trust boundaries. INVOKE when reading or writing tickets in a queue-driven flow, resolving a repo's tracker, or deciding…
Skill Claude CodeCodex
Turn one raw ticket into an implementation-ready spec — or ask the smallest unblocking question — without writing production code. INVOKE when specifying, scoping, or triaging a ticket from any tracker, when a ticket carries the ready-for-spec trigger, or when /sonu:factory routes a spec pass. Not backlog-wide…