All authors
Claude Skills by PrabhdeepSingh
github.com/PrabhdeepSingh27 skills0 installs31 views
- Code StandardsPrabhdeep (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". ([[tdd]] assumes this bar.)Votes: 0GitHub stars: 3
- Plugin DevThe 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 together. Covers the house rules, plugin/skill/command mechanics, the authoring conventions, the trap catalogue mined from this repo's own incidents, and the validation/release pr...Votes: 0GitHub stars: 3
- AccessibilityAccessibility 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". Contrast measurement: [[colors]]; text sizing and iOS input zoom: [[typography]]; spatial RTL: [[layout]]; whole-screen audits: [[interface-review]].Votes: 0GitHub stars: 3
- Blast RadiusConsumer-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 published identifier. Skip purely internal changes and strictly additive optional fields. (Schema seams: [[safe-migrations]]; downstream verification: [[tdd]].)Votes: 0GitHub stars: 3
- Bug FinderHunt 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 one ticket; it never fixes, changes code, or opens a PR.Votes: 0GitHub stars: 3
- Classify TicketsBacklog 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 ([[bug-finder]]). It never edits ticket text, closes tickets, or authorizes work. (Rulebook: [[ticket-lifecycle]].)Votes: 0GitHub stars: 3
- ColorsColor 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 appearances. Which contrast requirement applies: [[accessibility]]; text rendering: [[typography]]; whole-screen audits: [[interface-review]].Votes: 0GitHub stars: 3
- DebuggingThe 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 production incident — even a bare pasted error. Not for building features ([[tdd]] + [[code-standards]]); this governs finding WHY it's broken.Votes: 0GitHub stars: 3
- Design TreeMake 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 with no real alternatives.Votes: 0GitHub stars: 3
- Infra StandardsInfrastructure, 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 application code ([[code-standards]]), telemetry ([[observability]]), or schema changes ([[safe-migrations]]).Votes: 0GitHub stars: 3
- Intent InterviewPre-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 approaches ([[design-tree]]), or any non-interactive run — there an underspecified ask is a blocker, never a license to guess.Votes: 0GitHub stars: 3
- Interface ReviewCross-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 carries no domain rules. For one domain, or for build-time interface work, use the domain skills directly.Votes: 0GitHub stars: 3
- LayoutLayout 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. Hit areas and focus: [[accessibility]]; radius, shadows, motion: [[ui-polish]]; line length and text spacing: [[typography]]; whole-screen audits: [[interface-review]].Votes: 0GitHub stars: 3
- Model TieringTag 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 [delegate]/[delegate-heavy] tags; it locates its own tier and no-ops when no trustworthy tier sits below. Not for design-only exploration with no plan artifact.Votes: 0GitHub stars: 3
- ObservabilityProducing 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". Log-line mechanics: [[code-standards]]; consuming telemetry while diagnosing: [[debugging]].Votes: 0GitHub stars: 3
- PerformancePerformance 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 mid-build. NOT for diagnosing functional bugs ([[debugging]]) or query-shape hygiene while writing ordinary code ([[code-standards]] §5).Votes: 0GitHub stars: 3
- Pr ConventionsAuthor PR descriptions from the right per-change-type template (the repo's own PULL_REQUEST_TEMPLATE 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 standalone. ([[self-review]] seeds the risk section.)Votes: 0GitHub stars: 3
- Safe MigrationsZero-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 backfill, or shipping code and schema together. Not for greenfield schema design ([[code-standards]]) or diagnosing a broken migration ([[debugging]]).Votes: 0GitHub stars: 3
- SecurityBuild-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 after-the-fact review pass belongs to /security-review; validation mechanics: [[code-standards]]; infra secrets: [[infra-standards]].Votes: 0GitHub stars: 3
- Self ReviewSurface the riskiest parts of the current diff so a reviewer knows where to look hardest — one inline pass on small diffs, one cold read on a cheaper model tier with in-session synthesis on substantial ones. INVOKE PROACTIVELY whenever a change is finished and about to be handed off, reviewed, or shipped. It points attention — never approves, never fixes.Votes: 0GitHub stars: 3
- SeoSEO for anything served as a web page — the plumbing (templates, routes, redirects, <head> 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, metadata, or any content meant for the web — even when nobody says "SEO". Interface microcopy is [[ux-writing]], not SEO prose.Votes: 0GitHub stars: 3
- TddTest-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 [[code-standards]]'s bar.)Votes: 0GitHub stars: 3
- Ticket LifecycleThe 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 whether a trigger may move. Never a workflow itself — [[ticket-triage]] specs, [[classify-tickets]] grooms, [[bug-finder]] files; they consult this rulebook.Votes: 0GitHub stars: 3
- Ticket TriageTurn 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 classification ([[classify-tickets]]), defect discovery ([[bug-finder]]), or building an approved spec (/sonu:build). It writes only to the ticket. (Rulebook: [[ticket-lifecycle]].)Votes: 0GitHub stars: 3
- TypographyWeb typography — typeface choice and pairing, variable fonts and OpenType features, type scales, line-height, letter-spacing, measure, wrapping, truncation, underlines, tabular numbers, iOS input zoom. INVOKE PROACTIVELY when styling or reviewing anything that renders text. The words themselves: [[ux-writing]]; heading semantics: [[accessibility]]; RTL and logical properties: [[layout]]; contrast measurement: [[colors]]; whole-screen audits: [[interface-review]].Votes: 0GitHub stars: 3
- Ui PolishDesign-engineering details that make an interface feel polished — border radius, optical alignment, shadows and elevation, animations and micro-interactions, press feedback, icons. INVOKE PROACTIVELY when building or reviewing UI components, adding motion or hover/active states, or when the user says "make it feel better" or "something feels off". Text rendering: [[typography]]; hit areas, focus, reduced motion: [[accessibility]]; structure: [[layout]]; whole-screen audits: [[interface-review]].Votes: 0GitHub stars: 3
- Ux WritingUX writing and interface copy — voice and tone, button and link labels, error messages, settings labels, empty states, placeholders. INVOKE PROACTIVELY when writing or reviewing any user-facing interface text — even when nobody says "copy" or "microcopy". How copy renders: [[typography]]; error markup and announcements: [[accessibility]]; prose meant to rank in search: [[seo]]; whole-screen audits: [[interface-review]].Votes: 0GitHub stars: 3