All authors
Claude Skills by helderberto
github.com/helderberto37 skills0 installs0 views
- A11y AuditAudit accessibility (WCAG) in frontend code. Use when asked to "check accessibility", "audit a11y", "check WCAG", or find accessibility issues. Don't use for backend code, bundle size (/perf-audit), or translations (/i18n).Votes: 0GitHub stars: 16
- Architecture AuditSurface architectural friction across a codebase and propose deep-module refactors as RFCs.Votes: 0GitHub stars: 16
- BuildImplement the next unblocked ticket test-first and commit it, or fan every ticket out to parallel subagents with `--all`.Votes: 0GitHub stars: 16
- CheckValidate code quality — auto-fix formatting/lint, verify types, run tests. Use when asked to "validate code", "check code", or validate before committing; also lint-only asks ("run linter", "fix lint errors"). Don't use for committing, pushing, or writing new tests.Votes: 0GitHub stars: 16
- Code ReviewCorrectness lens for a PR or diff, used by build and review — bugs, security, performance, and code quality. Use when asked to review a PR or give pull request feedback, even when the diff is pasted inline. Don't use for local uncommitted changes, creating PRs, or merging.Votes: 0GitHub stars: 16
- Codebase DesignShared vocabulary for designing deep modules. Use when designing or improving a module's interface, placing a seam, making code more testable, or when another skill needs it. Don't use for codebase-wide audits (/architecture-audit) or UI components (/frontend-ui-engineering).Votes: 0GitHub stars: 16
- CommitGroup unstaged changes into atomic commits by concern, matching repository style. Use when asked to "commit", "create a commit", or "commit changes". Don't use for pushing or pull requests (/to-pr).Votes: 0GitHub stars: 16
- Create SkillCreate or restructure agent skills — frontmatter, description routing, progressive disclosure. Use when asked to create, write, or build a new skill, or "make a skill for X". Don't use for eval-driven trigger optimization (skill-creator) or one-off prose edits to a skill.Votes: 0GitHub stars: 16
- DebugDisciplined diagnosis loop for hard bugs and performance regressions. Use when user says "diagnose" or "debug this", or reports something broken, throwing, failing, or slow. Don't use to build a feature or fix an understood bug test-first (/tdd).Votes: 0GitHub stars: 16
- Deps AuditCheck dependencies for known vulnerabilities and staleness. Use when asked to "audit dependencies", "check for vulnerabilities", or check dependency health. Don't use for code quality review.Votes: 0GitHub stars: 16
- Domain ModelingBuild a project's domain model — challenge terms, pin down a ubiquitous language, write the glossary down. Use when defining domain terminology, resolving ambiguous terms, or another skill needs the shared vocabulary. Don't use for a single architectural decision (/to-adr) or explaining code (/zoom-out).Votes: 0GitHub stars: 16
- FeedbackFetch unresolved review comments on a GitHub PR (Copilot and human), verify against the code, classify Address / Skip / Optional / Discuss. Use when asked to triage reviewer feedback, which comments to actually fix, or to sort signal from noise on a PR. Don't use to reply to or resolve threads, or to write a fresh review (/code-review).Votes: 0GitHub stars: 16
- Frontend Ui EngineeringFront-load UI construction decisions — component boundary and prop API, state placement, required states, responsiveness, accessibility. Use when creating or refactoring a component, page, or design-system primitive. Don't use for pure logic (/tdd), throwaway exploration (/prototype), or auditing finished UI (/a11y-audit).Votes: 0GitHub stars: 16
- GrillInterview in rounds until a plan or idea has no open decisions.Votes: 0GitHub stars: 16
- GuideExplain which hb skill or flow fits your situation, from a map of how the skills fit together.Votes: 0GitHub stars: 16
- HandoffCompact the current conversation into a handoff document for a fresh agent.Votes: 0GitHub stars: 16
- HardenHarden code where untrusted input enters the system. Use when implementing auth, handling user input, storing sensitive data, integrating external APIs, adding file uploads, or crossing any trust boundary. Don't use for secret scanning (/safe-repo) or dependency CVEs (/deps-audit).Votes: 0GitHub stars: 16
- I18nAudit internationalization coverage and find hardcoded strings. Use when asked to "check i18n", "find hardcoded strings", or verify translation coverage. Don't use for backend code, projects without an i18n library, accessibility (/a11y-audit), or bundle size (/perf-audit).Votes: 0GitHub stars: 16
- Perf AuditAudit frontend bundle size and performance. Use when asked to "audit performance", "analyze bundle", "check bundle size", or find frontend bottlenecks. Don't use for backend performance, database queries, or projects without a frontend build step.Votes: 0GitHub stars: 16
- PrototypeBuild a throwaway prototype — a shareable HTML demo for state/logic questions, or several UI variations toggleable from one route. Use when comparing design directions before committing, or the user says "prototype", "mock up", "try a few approaches". Don't use for production code (/build, /tdd).Votes: 0GitHub stars: 16
- RefactorImprove existing code without changing behavior — split large functions, backfill tests, simplify. Use when asked to "refactor", "make robust", "bulletproof", "strengthen", "add missing tests", "split functions", "simplify", "clean up", or "reduce complexity". Don't use for new features (/tdd), security (/harden), or PR review.Votes: 0GitHub stars: 16
- ResearchInvestigate a question against primary sources and capture cited findings as Markdown. Use when the user wants a topic researched, docs or API facts gathered, or reading delegated to a background agent. Pass the question as the argument. Don't use for implementing against pinned dependency versions (/source-driven) or codebase search.Votes: 0GitHub stars: 16
- RetroRun a retrospective on a coding session and suggest changes to the agent's environment, not the code.Votes: 0GitHub stars: 16
- ReviewFan out parallel read-only reviewers over a diff and consolidate one severity-ranked verdict.Votes: 0GitHub stars: 16
- ReviseEdit prose in place — restructure article drafts (reorder sections, tighten arguments) or polish any markdown/text (typos, dashes, filler). Use when asked to "revise", "edit my draft", "improve my article", "fix typos", "fix dashes", "clean up text", or "improve sentences". Don't use for code style or linting (/check).Votes: 0GitHub stars: 16
- Safe RepoCheck the repository for sensitive data. Use when asked to "check for sensitive data" or verify no credentials or company data are committed; `--diff [<base>]` scopes to a branch's changes. Don't use for general code review or non-git directories.Votes: 0GitHub stars: 16
- Source DrivenImplement features from official docs for the exact installed dependency versions, not training data. Use when asked to "check the docs", "use official docs", "source-driven", or with unfamiliar APIs/libraries. Don't use for well-known stdlib APIs or project-internal code.Votes: 0GitHub stars: 16
- TddTest-driven development, from unit to end-to-end tests. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration or end-to-end tests (Playwright, Cypress). Don't use to backfill tests on existing code (/refactor) or diagnose an unknown bug (/debug).Votes: 0GitHub stars: 16
- TeachTeach the user a new skill or concept, within this workspace.Votes: 0GitHub stars: 16
- To AdrRecord an Architecture Decision Record (ADR) — 1–3 sentences on what was decided and why. Use when user says "create an ADR", "record this decision", or just made an architecturally significant choice. Don't use for forward-looking specs (/to-spec) or repo conventions (CLAUDE.md).Votes: 0GitHub stars: 16
- To PrGate, push, and open a GitHub pull request on the repo's PR template, then watch CI.Votes: 0GitHub stars: 16
- To SpecTurn the settled conversation into a spec (PRD) at `.specs/specs/<slug>.md`.Votes: 0GitHub stars: 16
- To TicketsSlice a spec or a ticket into tracer-bullet tickets with blocking edges, saved to `.specs/tickets/<slug>.md`.Votes: 0GitHub stars: 16
- TriageClassify any input — idea, bug, ticket key, `#42`, PR URL, stack trace — size it, and name the command to type; with no args, report where you are.Votes: 0GitHub stars: 16
- Visual ReviewTwo visual modes — render a PR diff as an HTML page with each hunk annotated by principle, or check a UI change in a real browser (screenshots, console, network). Use for a visual/HTML diff report, "check the UI", or "screenshot before/after". Don't use for text-only feedback (/code-review), unit tests (/tdd), or full reviews (/review).Votes: 0GitHub stars: 16
- Wait WhatStop — that last message didn't land. Re-pitch it plainly.Votes: 0GitHub stars: 16
- Zoom OutExplain code with visual diagrams and analogies. Use when explaining how code works, walking through a codebase area, or the user asks "how does this work?" Don't use for modifying code, fixing bugs, or multi-session learning (/teach).Votes: 0GitHub stars: 16