All authors
Claude Skills by kensaurus
github.com/kensaurus243 skills0 installs139 views
- 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 Aeo ReadinessPlan-only audit of answer-engine (AEO/GEO) citation readiness for ChatGPT, Perplexity, and AI Overviews. Use when "AEO", "GEO", "show up in ChatGPT/Perplexity", "AI search visibility", "llms.txt", or "am I blocking AI crawlers".Votes: 0GitHub stars: 9
- Plan AntislopPlan-only authenticity / AI-slop audit across prose, UI, code, and IA. Use when "looks like AI slop", "reads like ChatGPT", or "authenticity burndown". One-page UX apply → enhance-web-ux. Visual polish → enhance-web-ui.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 Capacitor HardeningPlan-only Capacitor/Ionic native-layer security audit: WebView, token storage, deep links, OAuth, cleartext, exported activities. Use when "is my Capacitor app secure?". Store readiness → plan-mobile-readiness.Votes: 0GitHub stars: 9
- Plan Data IntegrityPlan-only audit of destructive-operation and migration safety. Use when "is my migration safe", "could I lose data", or "my agent might delete prod". Restore drills, RPO/RTO → plan-backup-dr. Code transforms → audit-codemod-safety.Votes: 0GitHub stars: 9
- Plan Dead CodePlan-only dead-code audit: Knip baseline for unused files, exports, and deps, plus duplication, debug residue, suppressions, orphan assets, env drift. Deletes nothing. Use when "find dead code", "is this code used", or "unused exports".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 Error HandlingPlan-only audit of silent failures and observability gaps (Sentry, Langfuse). Use when "errors aren't showing in Sentry", "things fail silently", or "empty catch blocks". Apply patterns → backend-error-handling.Votes: 0GitHub stars: 9
- Plan Input ValidationPlan-only trust-boundary audit for missing validation, injection, XSS, and forged requests across forms, APIs, and webhooks. Use when "validate my inputs", "is my app injection-safe?", "check my forms", or "can someone forge requests?".Votes: 0GitHub stars: 9
- Plan Llm Cost GuardrailsPlan-only audit of an LLM app's runaway-cost and quota-abuse exposure. Use when "cap my AI costs", "my LLM bill could blow up", "rate limit my AI", "token budget", "runaway agent loop", or hardening LLM features before launch.Votes: 0GitHub stars: 9
- Plan Mobile ReadinessPlan-only App Store / Google Play submission audit for Capacitor and React Native: manifests, permissions, privacy, signing. Use when "ready for App Store?" or "will Google Play reject this?".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 Rls AuditPlan-only audit of Supabase/Postgres Row-Level Security and access-control gaps. Use when "RLS", "is my Supabase secure", "anyone can read my data", or "lock down my tables". App-layer route gates → audit-auth-flows.Votes: 0GitHub stars: 9
- Plan Secrets AuditPlan-only scan of the working tree and git history for exposed or mis-scoped keys, then a rotate-vs-relocate plan. Use when "hardcoded secrets", "did I commit a key", "secret scan", "is my .env safe", or "rotate keys".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 StallGuardrail for Playwright CLI sessions: headed, named, isolated; prevents parallel collisions and recovers stalls without scripted shortcuts. Read before browser work or when automation freezes.Votes: 0GitHub stars: 9
- ResearchResearch current practice with Context7, Firecrawl, and official docs before a non-trivial change: gap analysis and a file-mapped plan, no implementation. Use when "look up current docs" or before anything unfamiliar.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 Red TeamRed-team a running web, React Native, or Capacitor app. Use when "red team this app", "attack my app", "break it", "pentest the app", or "pre-launch hardening". Monkey test → test-exploratory.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
- Thirdparty Ui Ux Pro MaxThird-party skill — searchable style catalog, palettes, typography, and UX guidelines via Python scripts. Use when the user names ui-ux-pro-max or asks for a palette or font pairing from that catalog. Generic UI review → audit-ux.Votes: 0GitHub stars: 9
- Thirdparty Web Interface GuidelinesThird-party skill — Vercel Web Interface Guidelines compliance (focus, forms, animation, copy). Use when the user names Vercel or web interface guidelines. Generic a11y → audit-accessibility.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 Environment ReadyProve runtimes, installs, tools, services, env names, and the repo's verification commands work before a long run. Use when "preflight the repo", "set up the environment", or tests cannot start. Failing tests → workflow-green-repo.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 Feedback To ClosureTurn raw feedback — bug reports, review comments, Sentry, QA, audit output — into deduplicated tickets and drive each to verified closure. Use when "triage this feedback", "process the bug backlog", or "close the loop".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