All authors
Claude Skills by kensaurus
github.com/kensaurus236 skills15 installs639 views
- Enhance Web FormsBuild or upgrade web forms: accessible structure, schema-driven validation, client↔server parity. Use when "improve this form", "form validation", "accessible form", "multi-step form", "form error handling", or "the form UX is bad".Votes: 0GitHub stars: 9
- Enhance Web Instant NavInstant in-site navigation: Speculation Rules, View Transitions, bfcache, 103 Early Hints. Use when "instant navigation", "prerender", "early hints", "back button reloads", or "second page is slow". First-load CWV → audit-performance.Votes: 0GitHub stars: 9
- Enhance Web SeoAudit and fix SEO for a web app. Use when "improve SEO", "SEO audit", "add meta tags", "add structured data", "sitemap", "canonical URLs", "Open Graph", "Google indexing", "rich results", or "why is my site not ranking".Votes: 0GitHub stars: 9
- HandoffCompact the current conversation into a handoff document for a fresh agent: state, next steps, suggested skills, gotchas, saved to the OS temp dir. User-invoked via /handoff; an optional argument sets the next session focus. Use when "write a handoff", "hand off to a new session", or before ending a long session.Votes: 0GitHub stars: 9
- Housekeep BacklogInventory parked work — unfinished plans, deferred phases, TODO/FIXME, skipped tests, open findings — into a living BACKLOG.md that diffs new/done/stale. Use when "what's left behind", "inventory TODOs", or "consolidate the backlog".Votes: 0GitHub stars: 9
- Housekeep DesignConsolidate a drifted design system into one token and component source of truth. Use after an approved plan-uiux-unification, or when "clean up the design system now", "migrate to one button", or "resolve token conflicts".Votes: 0GitHub stars: 9
- Housekeep GatesConsolidate accreted CI gates, ratchets, and hooks into one required aggregator check. Use after audit-gate-logic, or when "clean up our CI checks", "we have three lint jobs", or "make one quality gate". Pipeline cost → audit-cicd.Votes: 0GitHub stars: 9
- Iterate Agent HarnessTurn an agent failure (premature stop, false completion, gamed check, missed file) into a rule, hook, or CI guard with a regression test. Use when "the agent stopped early again", "it gamed the test", or "add a guard so this doesn't recur".Votes: 0GitHub stars: 9
- Iterate Post LaunchClose the feedback loop on a live app: read production signals, rank the top issues, fix, verify live, repeat. Use when "post-launch polish", "fix the top production issues", "iterate on feedback", or "what should I fix next after launch?".Votes: 0GitHub stars: 9
- Meta Mcp BuilderBuild Model Context Protocol (MCP) servers that expose services, APIs, and data as typed tools for agents. Use when "build an MCP server", "give Claude access to X", "create an MCP tool", "expose my API to an agent", or "AI agent integration".Votes: 0GitHub stars: 9
- Mobile Emulator StartBoot the Android emulator and Metro (Expo or bare RN) in order: check terminals, kill stale ports, pick an AVD. Use when "start Metro", "start emulator", "Cannot connect to Expo", or a stuck dev loop. QA → mobile-emulator-test.Votes: 0GitHub stars: 9
- Mushi HealthPass/fail health check across every Mushi Mushi pipeline component — CLI credentials, API reachability, edge functions, BYOK key pool, QA cron. Use when "is mushi working", "mushi health check", "check mushi pipeline", "mushi deploy check", "pipeline not responding", or right after setup.Votes: 0GitHub stars: 9
- Mushi IntegrationFull end-to-end Mushi Mushi integration smoke test: bug capture → AI triage → story mapping → TDD test generation → approval → execution → PDCA cycle. Use when "test mushi integration", "verify full pipeline", "mushi e2e check", "does mushi work end-to-end", "smoke test mushi", or after deploying changes.Votes: 0GitHub stars: 9
- Plan AsoPlan-only ASO audit of App Store and Google Play listings: keywords, localized metadata, screenshots, ratings prompts. Use when "optimize our store listing", "improve app downloads", or "ASO". Submission readiness → plan-mobile-readiness.Votes: 0GitHub stars: 9
- Plan Backup DrPlan-only audit of whether a project can actually recover from data loss, not just whether backups exist. Use when "can we recover if the DB dies", "audit our backups", "what's our RPO/RTO", or "disaster recovery".Votes: 0GitHub stars: 9
- Plan Dependency ProvenancePlan-only audit of dependencies for hallucinated or slopsquatted packages, supply-chain risk, and license gaps. Use when "check my dependencies", "is this package real", "slopsquatting", "SBOM", or "did the AI hallucinate a package".Votes: 0GitHub stars: 9
- Plan Docs SyncPlan-only audit of documentation against actual code behavior. Use when "docs drift", "sync docs with code", "audit documentation", "stale README", "onboarding docs broken", "phantom docs", or "docs out of date". Decisions/ADRs → docs-adr.Votes: 0GitHub stars: 9
- Plan Perf AuditPlan-only performance audit across web, mobile, backend, and data; measures first, fixes nothing. Use when "performance audit plan", "perf burndown", "measure before optimize", or "N+1 audit plan". Apply fixes → audit-performance.Votes: 0GitHub stars: 9
- Plan Privacy CompliancePlan-only audit mapping real personal-data flows to the privacy policy, GDPR, Japan APPI, and store labels. Use when "privacy compliance", "what data do we collect?", "App Store privacy labels", or before a consumer launch.Votes: 0GitHub stars: 9
- Plan Security AuditPlan-only OWASP Top 10 and Supabase-first hardening burndown. Use when "security audit plan", "OWASP audit", "hardening plan", or "security burndown". Auth flows → audit-auth-flows. RLS → plan-rls-audit. Keys → plan-secrets-audit.Votes: 0GitHub stars: 9
- Plan Stub CheckerPlan-only sweep for stubs, dead buttons, fake components, unwired handlers, and dead links, then a wiring plan. Use when "find dead buttons", "stub checker", "fake components", "unwired handlers", or "dead links".Votes: 0GitHub stars: 9
- Plan Test CoveragePlan-only, user-story-driven test coverage audit. Use when "test coverage plan", "traceability matrix", "fake-green tests", or "what's not tested". Mutation score → test-mutation.Votes: 0GitHub stars: 9
- Plan Uiux UnificationPlan-only UI/UX and design-system audit that emits a unification burndown; no code until a phase is approved. Use when "audit UI without fixing", "UI burndown", or "IA audit before redesign". Apply now → housekeep-design.Votes: 0GitHub stars: 9
- Protocol Browser Anti Stallplaywright-cli guardrail: headed, named -s= sessions, one real action at a time, max 4 attempts, then a BLOCKER. Read before browser work, or when "the browser is stuck", "playwright hangs", or agents share a browser.Votes: 0GitHub stars: 9
- Test ExploratoryHeaded exploratory QA of a live app as guest, then logged in, with junk input and navigation abuse. Use when "monkey test", "wander like a confused user", or "guest vs logged in". CRUD stories → test-qa. Hostile sweep → test-red-team.Votes: 0GitHub stars: 9
- Test LoadDesign and run a k6 or Artillery load profile: throughput, latency percentiles, error rate, breaking point. Use when "load test this", "will it handle launch traffic", or "find the breaking point". Code-level resilience → audit-resilience.Votes: 0GitHub stars: 9
- Test MutationRun mutation testing (StrykerJS, mutmut) to measure whether tests assert behavior, not just execute lines. Use when "add mutation testing", "are our tests real", "can our test suite be gamed", or after an agent bulk-generated tests.Votes: 0GitHub stars: 9
- Test PlaywrightClose the PDCA loop on this session's diff. Headed playwright-cli, fix as you go. Use when "test my changes", "PDCA this". Pixel diffs → test-visual-regression. Story CRUD → test-qa. Monkey / guest vs logged-in → test-exploratory.Votes: 0GitHub stars: 9
- Test QaWeb-app CRUD and story QA when no project-specific skill applies. Use when "QA the app", "test CRUD", or "smoke test". Native → mobile-emulator-test. Guest vs logged in → test-exploratory. Pixel diffs → test-visual-regression.Votes: 0GitHub stars: 9
- Test UnitWrite unit and integration tests for a named module or change. Use when "write unit tests" or "add tests for this function". Coverage plan → plan-test-coverage. Mutation score → test-mutation. Browser check → test-playwright.Votes: 0GitHub stars: 9
- Test Visual RegressionSet up Playwright screenshot baselines and CI diffing so UI changes fail pixel by pixel instead of by eye. Use when "add visual regression tests" or "catch UI regressions". Functional clicks → test-playwright.Votes: 0GitHub stars: 9
- Thirdparty Emil Design EngThird-party skill — Emil Kowalski's design-engineering notes (animation craft, Sonner-style components). Use when the user names emil-design-eng or asks for that philosophy. Motion pass → enhance-motion.Votes: 0GitHub stars: 9
- Workflow Build FeatureBuild a feature end to end: spec and TDD, implement, unit tests, Playwright check, PR. Use when "build a feature" or "implement this end-to-end". Spec/TDD loop only → workflow-spec-tdd. One bug → workflow-fix-and-ship.Votes: 0GitHub stars: 9
- Workflow Coding DisciplineGuardrails for writing, editing, refactoring, or debugging code: surface assumptions, simplicity first, surgical changes. Use when vibe-coding keeps producing wrong results, or for "think before coding" or "surgical changes".Votes: 0GitHub stars: 9
- Workflow Feature FlagPlan and run a feature-flag rollout. Use when "add a feature flag", "gradual rollout", "staged release", "kill switch", "dark launch", "flag cleanup", "canary release", "rollback plan", or "deploy without switching on".Votes: 0GitHub stars: 9
- Workflow Fix And ShipOne bug-fix lifecycle: triage, reproduce, debug, regression test, fix, live check, PR, optional deploy verify. Use when "fix this bug and close the ticket", "patch this and ship", or a named production error. Many reports → workflow-feedback-to-closure.Votes: 0GitHub stars: 9
- Workflow Git CommitCreate one conventional commit from an already-scoped change: stage the named files or hunks, write the message, commit, never push. Use when "commit these files" or "write a commit message". Whole tree to a PR → workflow-release-prep.Votes: 0GitHub stars: 9
- Workflow Green RepoDrive a repository to a green baseline — typecheck, lint, tests, and build passing from a clean checkout — when fixing is authorized. Use when "make the repo green", "get CI passing", or "fix all the failing tests".Votes: 0GitHub stars: 9
- Workflow GrillingInterview the user about a plan, decision, or idea one question at a time until you agree. Use when "grill me", "stress-test this plan", "interview me about this", "poke holes in this", "challenge my thinking", or before a non-trivial design.Votes: 0GitHub stars: 9
- Workflow HousekeepRepository maintenance: sync the README, remove confirmed dead artifacts, update dependencies safely. Use when "housekeep", "clean up repo", "update README", or "update dependencies". Unused exports → plan-dead-code. Parked work → housekeep-backlog.Votes: 0GitHub stars: 9
- Workflow Launch ReadyLaunch-preparation sweep for a new app or major release. Use when "prepare for launch", "launch week", "everything before going live", "is the app launch-ready?", or "pre-launch sweep". Working tree to a PR → workflow-release-prep.Votes: 0GitHub stars: 9
- Workflow Merge ConflictsResolve an in-progress merge or rebase conflict by tracing each side back to its intent. Use when "resolve the conflicts", "fix this merge", "the rebase is stuck", or a pull has left conflict markers in the tree.Votes: 0GitHub stars: 9
- Workflow OnboardFirst-contact orientation for an unfamiliar codebase. Use when "I'm new to this repo", "orient me", "explain this codebase", "what does this do?", "onboard me", "first day on this project", or "catch me up on the codebase".Votes: 0GitHub stars: 9
- Workflow Parallel AgentsRun multiple agents in parallel via git worktrees, cloud agents, or multi-model comparison. Use for "run agents in parallel", "best-of-N", "compare approaches", "multi-model", "parallel worktrees".Votes: 0GitHub stars: 9
- Workflow PrManage an existing PR lifecycle — review, bot feedback, conflicts, merge. Use when opening a PR from an already-committed branch, addressing review, or merging. Uncommitted working tree to merge-ready → workflow-release-prep.Votes: 0GitHub stars: 9
- Workflow Quality GatePre-release quality gate across red-team, security, bundle size, performance, and unit tests. Use when "is this ready to ship?", "quality gate", or "pre-release checklist". Working tree to a PR → workflow-release-prep.Votes: 0GitHub stars: 9
- Workflow RefactorScoped, behavior-preserving refactor: map dependencies, change structure, run affected tests. Use when "refactor this", "reduce duplication", or "improve readability". Dead code → plan-dead-code. Repo-wide smells → audit-code-quality.Votes: 0GitHub stars: 9
- Workflow Release PrepTake the local working tree to a merge-ready PR against main: review, split if needed, commit, push, open the PR, drive CI green; never merge. Use when "prepare this for a PR" or "get my working tree merge-ready". Existing PR → workflow-pr.Votes: 0GitHub stars: 9
- Workflow Ship And ObserveTake merged, green code to a verified, monitored production release. Use when "ship it", "deploy to production", "go live", or "cut a release" for a running app (npm packages → deploy-npm).Votes: 0GitHub stars: 9
- Workflow Spec TddA spec → plan → TDD loop before writing a line. Use when "spec first", "TDD", "do it properly", or LLM output keeps being wrong. Feature through PR → workflow-build-feature. One bug → workflow-fix-and-ship.Votes: 0GitHub stars: 9