Skip to content

Claude Skills by NinjaSln-labs

github.com/NinjaSln-labs

94 skillsA× 9411 installs106 views

Pixel PerfectAVisual regression testing — pixel-by-pixel screenshot comparison against a baseline, free and local. TRIGGER when: user mentions "pixel-perfect", "visual regression", "screenshot diff", "snapshot mismatch", "toHaveScreenshot", "UI looks broken after changes", "compare before/after screenshots", "visual QA", "catch visual bugs", "design implementation check", "tests failing with screenshot", or wants to verify that code changes didn't break the UI visually. DO NOT TRIGGER when: user wants func...ai-agentstypescriptshellVotes: 0GitHub stars: 3
Plan GrillingAGrill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases. NOT for executing the plan or gathering background facts — decisions only.ai-agentsgoVotes: 0GitHub stars: 3
Playwright Best PracticesAPlaywright best practices for E2E, component, API, visual, and accessibility testing: flaky-test fixes, Page Object Model, CI/CD, mocking, auth/OAuth, axe-core, uploads, WebSockets, mobile, GraphQL, PWA, Electron, and extensions. Use when writing or debugging Playwright tests. NOT for: non-Playwright frameworks (Cypress/Selenium-only) or general CI without Playwright.developmentreactvueVotes: 0GitHub stars: 3
Positioning StatementACreate a Geoffrey Moore-style positioning statement. Use when clarifying who you serve, what problem you solve, your category, and why you're different from alternatives.ai-agentsgotestingVotes: 0GitHub stars: 3
Positioning WorkshopARun a positioning workshop that surfaces target customer, unmet need, category, benefits, and differentiation. Use when your product messaging feels fuzzy, generic, or misaligned.businessgogitVotes: 0GitHub stars: 3
Prd DevelopmentAPRD development: build a structured Product Requirements Document that connects problem, users, solution, and success criteria. Use when turning discovery notes into an engineering-ready document for a major initiative or feature.ai-agentsgoapiVotes: 0GitHub stars: 3
Skills DirectorySkills Directory Pro Download any skill as a ZIP for Claude.ai, Claude Desktop, or .claude/skills.See Pro
Prd Driven DddATransform product design documents (PRDs, flowcharts, prototypes, state machines, rules/AC) into a domain-driven design model: per-context ubiquitous language/glossary, event storming, bounded contexts and mapping, aggregates/entities/value objects, domain events and versioned integration events (Name:vN), read models, PRD-model traceability. Use when the user asks for DDD, domain modeling, event storming, aggregate design, bounded context mapping, versioned integration events, read models/CQ...ai-agentsapiVotes: 0GitHub stars: 3
Press ReleaseAWrite an Amazon-style press release that defines customer value before building. Use when aligning stakeholders on a new product, feature, or strategic bet.ai-agentsgoreactVotes: 0GitHub stars: 3
Problem HandlingAProblem handling: one evidence-driven pipeline from a reported symptom to a shipped fix — evidence-first intake, root-cause tracing (5 Whys plus RCA tools, falsifiable experiments), cognitive-bias defenses, dual-channel research, severity grading with a P0/P1 restore-first fast path, classify and scope, workaround-vs-permanent-fix decision, TDD fix, verification, and a blameless close with known-error capture plus a 3-strikes design escalation. Use when a problem, bug, error, UX complaint, or...ai-agentsgodebuggingVotes: 0GitHub stars: 3
Problem StatementAWrite a user-centered problem statement with who is blocked, what they are trying to do, why it matters, and how it feels. Use when framing discovery, prioritization, or a PRD.ai-agentsrustgoVotes: 0GitHub stars: 3
Product Doc AuditAProduct Document Audit: three-layer audit of a product documentation set (0-1 phase docs): 1) completeness against the 0-1 delivery doc panorama (required/optional), 2) each doc by type-specific checkpoints and core review dimensions, 3) cross-validate alignment, incl. spot-checking prior audit conclusions. Produces readiness score (0-100), Critical/Major/Minor grading, authority rulings, deliverability judgment, and PRODUCT-DOC-AUDIT.md without modifying audited docs. Supports final project ...ai-agentsgorailsVotes: 0GitHub stars: 3
Product LaunchAPlan a product launch with the ORB framework (owned, rented, borrowed channels) and a five-phase rollout, plus Product Hunt strategy and pre/post-launch checklists. When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update,' 'how do I launch this,' 'launch checklist,' 'GTM plan,' or 'we're about t...content-marketinggotestingVotes: 0GitHub stars: 3
Product MarketingACreates and updates `.agents/product-marketing.md` — shared product, audience, and positioning context that other marketing skills reference so users avoid repeating foundational information. Use when the user wants to create or update their product marketing context document, or mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' 'who is my target audience,' 'describe my product,' 'ICP,' 'ideal customer profile.' Use at the start of any new project before other ...ai-agentsrustgoVotes: 0GitHub stars: 3
Project HandoffAMaintain a project's handoff store (.handoff/, plain text): a multi-dimensional project handoff — status, summary, actions, pitfalls, decisions, commands, scope, exit, plus a machine-checked read-back — with a next-step pointer, driven by a script-enforced `handoff` CLI (single write path, coverage statement). Use when handing off between sessions or tools, or resuming or continuing prior work on a project. Initializing a new project's store or migrating an old HANDOFF.md model is done only w...ai-agentspythonshellVotes: 0GitHub stars: 3
Proto PersonaACreate a proto-persona from current research, market signals, and team knowledge. Use when you need a working customer profile before deeper validation.developmentrustgoVotes: 0GitHub stars: 3
React Vite Best PracticesAReact and Vite performance optimization guidelines. Use when writing, reviewing, or optimizing React components built with Vite. Triggers on tasks involving Vite configuration, build optimization, code splitting, lazy loading, HMR, bundle size, asset handling (images/fonts/SVG), environment variables, or React performance.developmentjavascripttypescriptVotes: 0GitHub stars: 3
Release PipelineARelease guardrails and multi-target release orchestration for packages and repos: OIDC / trusted publishing setup for PyPI and npm, provenance and attestation verification, single-version-source consistency, immutability checks, idempotent multi-registry release plans, and recovery from half-finished releases. Use when you are about to publish a version, wire a release workflow, or resume a release that failed partway across several registries. NOT for: choosing a version number (SemVer/CalVe...ai-agentsrustgoVotes: 0GitHub stars: 3
Roadmap PlanningAPlan a strategic roadmap across prioritization, epic definition, stakeholder alignment, and sequencing. Use when turning strategy into a release plan that teams can execute.businessgoapiVotes: 0GitHub stars: 3
Secrets ScanASecrets scan: detect hardcoded API keys, passwords, tokens, private keys, and connection strings in source code, git history, and config files, with high-entropy analysis. Findings are reported redacted (type plus file:line, never full credential values). Use when hunting leaked credentials in a repo, checking whether a secret committed and later removed is still recoverable from history, or wiring a pre-commit / CI secret gate. NOT for: dependency CVEs, config or IaC misconfiguration review,...ai-agentsjavascriptrustVotes: 0GitHub stars: 3
Security ScanASecurity scan: one comprehensive pass over a whole codebase — OWASP Top 10 detection (access control, crypto, injection, SSRF, logging), hardcoded secrets, insecure configuration, with severity ranking and remediation guidance. Use when you need a full security review before a release or PR, want to triage which security problems matter most, or ask to "scan this project for security issues". Detection is pattern-based: no SAST data-flow engine or CVE advisory database is bundled, so dependen...securitygoshellVotes: 0GitHub stars: 3
Session HealthASession Health: assess the current AI coding tool session — context compaction/condensation ratio, message count, context occupation cost, work nature, recoverability (git/handoff/runtime), and token economics — to judge continue vs new-session. Reads tool session storage read-only. Use when the user mentions context compaction, starting a new session, high context overhead, or long-session continuation (e.g. "go" / "keep going"). NOT for: auditing skill descriptions, full-codebase architectu...ai-agentsgobashVotes: 0GitHub stars: 3
Skill Description AuditASkill Description Audit. User-invoked only: run it when the user asks, never on your own initiative. When asked to audit a skill's description, cross-validate it against that skill's own body and write a graded report beside the skill — the skill is never edited. The audit is a per-criterion sheet: every criterion is answered in turn and graded into a severity band, so a reader sees what was asked, answered, and how sure the auditor was. It covers frontmatter spec compliance, whether every pr...ai-agentspythongoVotes: 0GitHub stars: 3
Skill EvalABehaviorally evaluate a skill in two modes: pass-rate (define 3-5 representative tasks, run each N>=3 times with and without the skill loaded in fresh agents, compare pass rates) and trigger rate (build ~20 queries — 8-10 should-trigger plus 8-10 near-miss — run each 3 times, score per-query trigger rate). Both report a table plus concrete improvement items that feed back into the skill's SKILL.md. Use when a skill changes, at quarterly evaluation, when accepting a new skill, or when descript...ai-agentscode-reviewVotes: 0GitHub stars: 3
Skill FitASkill fit (v2): derives a project's skill needs — tier T0–T4, evidence-backed requirement table against a versioned lexicon (count bounded by tier), coverage four-ways (served / in-catalog-unmounted / poor-fit / gap), and mount-tier advice with a two-value budget. Confirm gate (ask-user; scripts/sf-gate.py apply/verify/rollback): mount/move from 2.1.0, unmount from 2.2.0. Judges fit from skill bodies, not descriptions; catalog.yaml＝supply, lexicon＝demand. Writes feedback (and applied log when...ai-agentsrustgoVotes: 0GitHub stars: 3
Stage GateARun a stage-completion gate for staged delivery (spec-kit): read the stage spec's DoD assertions and execute each one — unit tests, dual tsc, interaction tests, behavioral acceptance, coverage matrix, open audit items, push state — reporting PASS/FAIL per assertion with fresh command evidence. Verifies only, never fixes. Use when a stage is claimed complete or the user asks to run the stage gate. NOT for: verifying one completion claim in isolation, or carrying out a written plan task by task.ai-agentsnodecode-reviewVotes: 0GitHub stars: 3
Stage SpecAWrite or backfill a stage spec for staged delivery (spec-kit): turn a stage row of the phased design into a machine-verifiable contract — DoD assertions directly executable by a stage-completion gate, a TDD grid (spec assertion -> failing test -> implementation -> refactor), deliverables, and explicit non-goals. No prose "done" statements. Use when starting a new stage (e.g. "write the S3 spec" / "backfill the stage spec") or after the design's stage plan changes. NOT for: generic implementat...ai-agentsgoVotes: 0GitHub stars: 3
Systematic DebuggingASystematic Debugging: find the root cause before proposing fixes — symptom fixes are failure; reproduce, isolate, and verify the fix addresses the actual cause. Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. For a reported problem that is not yet a confirmed technical code defect, start with problem-handling; this skill is the code-bug root-cause protocol used inside it.ai-agentsrustgoVotes: 0GitHub stars: 3
Task Loop ProgressAGenerate config + adapter for the generic long-task progress loop (scaffold task_loop_scaffold.py / task_loop_poll.py / task_loop_start.sh from templates/). Config-driven: adapter extracts numeric/percentage/stage progress via progress_extract — zero code changes per task. Supports local files, remote SSH fetch, stdout JSON, and terminal matching. Requires successful poll validation before start; on AGENT_LOOP_TICK, Agent must post chat_line to Chat. Use when the user asks for a task loop, pr...ai-agentspythonshellVotes: 0GitHub stars: 3
Test Data GenerationATest data strategies using Faker.js, factories, builders, and database seeding. Use when generating test data, fixtures, or seeded databases, or when flaky tests fail on inconsistent data — deterministic seeds and factory patterns are the fix.developmenttypescriptpythonVotes: 0GitHub stars: 3
To TicketsABreak a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges. Every ticket is a narrow vertical slice that is demoable or verifiable on its own; wide refactors are sequenced as expand–contract batches instead of one bullet. Present the breakdown for the user's approval and iterate, then publish to the configured tracker — defaulting to one local file per ticket when no tracker is set up, or native blocking links on a real tracker (GitH...ai-agentsgorefactoringVotes: 0GitHub stars: 3
Typescript Best PracticesAGuide AI agents through TypeScript coding best practices including type safety, error handling, code organization, and architecture patterns. This skill should be used when generating TypeScript code, reviewing TypeScript files, creating new TypeScript modules, refactoring JavaScript to TypeScript, or when the user asks about TypeScript patterns, types, or coding standards. Keywords: typescript, types, coding standards, best practices, type safety, generics, architecture, refactoring. Use whe...developmentjavascripttypescriptVotes: 0GitHub stars: 3
Ui AnimationAEncodes Emil Kowalski's design-engineering philosophy: UI polish, component design, animation decisions, and the invisible details that make software feel great. Use when building or reviewing interfaces, improving UI polish, auditing animation timing/easing/motion, checking animation accessibility (prefers-reduced-motion), or making components feel responsive and deliberate.developmentjavascriptgoVotes: 0GitHub stars: 3
Ui TypographyAUI Typography: professional typography rules for UI design, web apps, software interfaces, and screen-based text — quotes, dashes, spacing, hierarchy, layout. ENFORCEMENT MODE: when generating any HTML/CSS/React/JSX UI with visible text, auto-apply silently. AUDIT MODE: when reviewing interfaces, flag violations and fixes. Trigger on UI/landing/component/dashboard/document generation or "fix the typography". NOT for: marketing copywriting strategy, print-only typesetting, or non-UI prose.developmentjavascriptgoVotes: 0GitHub stars: 3
Ui Ux Pro MaxAUI/UX Pro Max design intelligence for web and mobile: searchable local database with styles, color palettes, font pairings, product types, UX guidelines, icons, GSAP motion presets, and chart types across major stacks (React, Next.js, Vue, Nuxt, Svelte, Astro, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, and more). Use when designing, building, or reviewing UI: pages, components, color schemes, typography, layout, accessibility, animation, or data visualization — including design syst...developmentpythongoVotes: 0GitHub stars: 3
User ResearchAPlan, conduct, and synthesize user research. Trigger with "user research plan", "interview guide", "usability test", "survey design", "research questions", or when the user needs help with any aspect of understanding their users through research. NOT for usability of code you cannot observe, or research with no user access.ai-agentsreacttestingVotes: 0GitHub stars: 3
Ux HeuristicsAEvaluate and improve interface usability using heuristic analysis. Use when the user mentions "usability audit", "users are confused", "form usability", "navigation problems", "Nielsen heuristics", or "is this easy to use". Also trigger when reviewing a design for usability issues, improving form-completion rates, or evaluating information architecture and navigation. Covers Krug's laws, Nielsen's 10 heuristics, severity ratings, dark-pattern recognition, and accessibility. NOT for: visual re...ai-agentsrustgoVotes: 0GitHub stars: 3
Verification Before CompletionARun verification commands and confirm fresh output before claiming work complete—evidence before assertions, never claim done without verification. Use when about to claim work is complete, fixed, or passing, before committing or creating PRs. NOT for: stage-level aggregation of a whole DoD spec — that is stage-gate, which runs the full gate and never fixes.ai-agentsrustgoVotes: 0GitHub stars: 3
Version ManagementAUniversal version management for any software artifact, independent of any VCS. Decides the next version from the change set under Semantic Versioning (MAJOR/MINOR/PATCH, prerelease, build metadata), keeps exactly one version source, maintains a Keep-a-Changelog CHANGELOG, and marks releases — VCS tags when git is available, otherwise a RELEASES manifest. Judges breaking versus compatible changes against the public contract (including implicit interfaces), applies deprecate-then-remove polici...developmentpythongoVotes: 0GitHub stars: 3
Visual Regression TesterAVisual Regression Tester: screenshot comparison, diff detection, and CI integration using Playwright or Chromatic. Use when users request visual testing, screenshot testing, UI regression, visual diff, or Chromatic setup. For free local flows prefer a no-service comparator; use this when you need hosted Chromatic baselines.ai-agentstypescriptgoVotes: 0GitHub stars: 3
Voice Of Customer MinerAMine public reviews, app stores, and forums for unmet needs, competitor weaknesses, and switching triggers — with quoted evidence. Use when you want customer voice without waiting on interviews.ai-agentsrustgoVotes: 0GitHub stars: 3
Web Design GuidelinesAReview UI code files against the Vercel Labs Web Interface Guidelines, fetched live at runtime through any web-fetch or HTTP capability (requires network access to the public source, or a previously saved local copy of the guidelines). Outputs terse file:line findings. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices". NOT for: heuristic or usability review of interaction design, design-system/style/palette recommen...ai-agentsbashgitVotes: 0GitHub stars: 3
Workshop FacilitationAFacilitate workshop sessions in a one-step, multi-turn flow. Use when an interactive skill needs consistent pacing, options, and progress tracking.ai-agentsgobackendVotes: 0GitHub stars: 3
Write SpecAWrite a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.developmentgodatabaseVotes: 0GitHub stars: 3
Writing PlansAWrite comprehensive implementation plans from a spec or requirements—break multi-step work into bite-sized tasks with exact file paths, complete code, and verification steps (DRY, YAGNI, TDD, frequent commits; no placeholders). Plans are saved as dated markdown docs under the project's plans directory (probe for an existing convention, default docs/plans/; user preferences override). Use when you have a spec or requirements for a multi-step task, before touching code. NOT for: stage contract ...ai-agentsgotestingVotes: 0GitHub stars: 3