All authors
Claude Skills by NinjaSln-labs
github.com/NinjaSln-labs94 skills11 installs106 views
- Accessibility AuditorComprehensive WCAG 2.1 AA compliance testing combining automated axe-core scans with manual keyboard navigation and focus management verification, with screen reader checks limited to ARIA and live-region readiness because full screen reader compatibility requires manual testing. Use when running accessibility checks, WCAG compliance testing, or axe-core audits.Votes: 0GitHub stars: 3
- Agent DispatchUser-invoked only: run it when the user explicitly asks to hand work to an external agent CLI, never on your own initiative. On enable it probes the machine first — which agent CLIs are on PATH, and which LLM each one runs, read from that CLI's own --help / --list-models, never from memory or this file — then asks the user, one question at a time, to pick the agents, their model modes, and whether to append. It drives the loop after that: a task brief carrying only checked-in artifact paths p...Votes: 0GitHub stars: 3
- Api Contract ValidatorValidate API responses against OpenAPI/Swagger specifications, JSON Schema definitions, and GraphQL schemas to prevent breaking changes. Use when checking whether an API change removes fields, changes types, or breaks backward compatibility; when validating responses against a published contract in CI; when detecting GraphQL schema breaking changes; or when reviewing consumer-driven contract tests.Votes: 0GitHub stars: 3
- Architecture PatternsImplement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design (ports/adapters, dependency rule, in-memory adapters for unit tests). Use when designing clean architecture for a new microservice, refactoring a monolith to bounded contexts, implementing hexagonal or onion architecture, or debugging dependency cycles between application layers.Votes: 0GitHub stars: 3
- Audit ItemTrack audit/review findings as numbered issue files (audit-items/NNN-slug.md, under the directory the project keeps such findings) with id, severity, source audit, status (open/fixed/recorded), fix commit, regression test, and closing evidence, plus a summary index README that the stage-completion gate enumerates. Use when an audit or review produces findings and the user asks to record them (e.g. "log the audit findings"). USER-INVOKED ONLY: it writes tracked files — the agent must not auto-...Votes: 0GitHub stars: 3
- Autonomous InvestigationThe evidence protocol behind recurring competitive and market investigation skills — market scans, competitive snapshots, intel watches, battle cards — not a research executor. Use when AI research must proceed without you: search-plan gate, Fact/Inference/Assumption labels, confidence stacking, diffable outputs. NOT for answering a one-off research question or producing a single research report.Votes: 0GitHub stars: 3
- Battle Card BuilderResearch and draft a competitive battle card from public evidence — every claim labeled and sourced. Use when a rep needs a field-action card, not a research report.Votes: 0GitHub stars: 3
- Cicd PipelineConfigure testing in CI/CD pipelines for GitHub Actions, Jenkins, and GitLab CI: shards, parallelization, wait-on health checks, and service containers. Use when configuring tests in CI/CD pipelines (GitHub Actions, Jenkins, GitLab).Votes: 0GitHub stars: 3
- Code ReviewReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Stage-end mode: fixed point is the parent of the stage's first commit, Spec axis checks the stage spec's DoD, output is a statusized open/fixed/recorded findings list. Use when the use...Votes: 0GitHub stars: 3
- Codebase DesignShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable, or when another skill needs the deep-module vocabulary.Votes: 0GitHub stars: 3
- Company IntelResearch a company, industry, or competitor set using web search and seven analytical lenses. Use when you need structured intel that feeds downstream PM skills.Votes: 0GitHub stars: 3
- Competitive Analysis ProcessOrchestrate a complete competitive analysis end to end: market landscape, product-level comparison, ability to fulfill customer needs, business and financial baseline, relative positioning, and competitors' strategic direction — closing with the artifacts owners consume: battle cards, an executive comparison matrix, positioning counter-moves, a threat assessment. Use when a decision needs the whole competitive picture — market entry, a roadmap bet, a positioning refresh, deal defense — or whe...Votes: 0GitHub stars: 3
- Competitive Intel WatchCompetitive Intel Watch: scheduled delta monitoring against a prior competitive snapshot. Use when tracking competitors on a cadence: material shifts only, cited evidence, battle-card update flags, runs unattended.Votes: 0GitHub stars: 3
- Competitive Research SnapshotResearch a competitive landscape with cited snapshots, a comparison matrix, and so-what implications. Use when a product decision needs competitive grounding, not a market report.Votes: 0GitHub stars: 3
- Config ScanConfig scan: detect security misconfigurations in config files, Docker, and IaC. Use when reviewing configuration security for containers, Kubernetes, Terraform, or application settings.Votes: 0GitHub stars: 3
- Core RulesRETIRED 2026-09-17 — the consumer link was removed; this source is kept for reference only. Its surviving bottom line (no plaintext secrets) now lives in the user-level AGENTS.md memory; the session-progress rule is covered by project-handoff (formerly project-intake); permission-confirmation and long-task-feedback were dropped. Original text — global rules applicable to all projects/sessions across AI coding tools (Deep Code / Cursor, etc.), four bottom lines: credential safety (no plaintext...Votes: 0GitHub stars: 3
- Coverage MatrixGenerate or maintain the three-way coverage matrix (invariants<->tests / events<->tests / DoD<->gate) for staged-delivery projects using this skill family's layout: unit tests under tests/unit/, a domain event registry (e.g. TIMELINE_EVENT_SPECS in src/domain/timeline.ts), per-stage spec DoD files, output at docs/tests/coverage-matrix.md — if your project does not follow this layout, this skill does not apply without path adaptation. Scans those sources, produces the matrix, and flags gaps (i...Votes: 0GitHub stars: 3
- Customer Journey MapCreate a customer journey map across stages, touchpoints, actions, emotions, and metrics. Use when diagnosing a broken experience or aligning a team on the full customer flow.Votes: 0GitHub stars: 3
- Ddd AggregatesDesign DDD aggregates and aggregate boundaries from invariants: aggregate roots, entities, value objects, transaction boundaries, and cross-aggregate consistency strategies. Use when designing aggregate boundaries, invariants, transaction boundaries, or cross-aggregate consistency.Votes: 0GitHub stars: 3
- Ddd Context MapMap relationships and integration strategies between bounded contexts: pattern selection, contract ownership, failure modes, and versioning strategy. Use when mapping bounded-context relationships, integration patterns, or contract ownership.Votes: 0GitHub stars: 3
- Ddd ContextsDesign bounded contexts and their ubiquitous language: boundaries, responsibilities, glossary, team ownership, and boundary ADRs. Use when defining bounded contexts.Votes: 0GitHub stars: 3
- Ddd DiscoverCollaborative domain discovery via event storming, producing event streams, command/event candidates, hotspots, ambiguity lists, and preliminary context-boundary clues for downstream subdomain classification. Use when doing domain discovery — identifying domain events and commands, aligning core business flows and exception paths, or re-running discovery after bounded-context term conflicts. NOT for: facilitating live EventStorming workshops (formats and facilitation patterns are separate ref...Votes: 0GitHub stars: 3
- Ddd Domain InteractionsDesign collaboration mechanisms between building blocks: domain events, domain services, repository interfaces, and factories. Use when designing domain services, repositories, domain events, or factories.Votes: 0GitHub stars: 3
- Ddd Model ReviewGlobal model quality assessment: consistency, completeness, coupling analysis, and feedback-loop triggers. Use when evaluating domain model quality, consistency/completeness/coupling checks, or model evolution review.Votes: 0GitHub stars: 3
- Ddd Openspec BridgeMap DDD tactical modeling artifacts into OpenSpec structured specifications for a smooth handoff from domain modeling to engineering implementation. Use when bridging domain modeling outputs to OpenSpec specs.Votes: 0GitHub stars: 3
- Ddd Qa ChainRun the quality verification chain—5 abstract verification layers (domain logic / contract / component interaction / E2E user journeys / visual regression) mapped onto the project's own test stack (unit runner, type checker, contract tests, e2e suite, visual regression), each with a gate, plus a run-all delivery gate and a DoD quality gate (deterministic assertions + probabilistic sample/threshold for model-driven behavior). Use when delivering or verifying a feature, before claiming work com...Votes: 0GitHub stars: 3
- Ddd ScopeDDD scope: converge vague requirements into executable DDD modeling inputs — problem statement, goals/non-goals, constraints, term seeds, and risk list. Use when converging fuzzy requirements into DDD modeling inputs or defining modeling scope.Votes: 0GitHub stars: 3
- Ddd SubdomainsIdentify business capabilities and classify subdomains (Core/Supporting/Generic), producing core-domain declarations, ownership recommendations, and bounded-context boundary candidates. Use when partitioning core/supporting/generic subdomains, or re-partitioning when god-context or circular-dependency signals suggest a subdomain misfire.Votes: 0GitHub stars: 3
- Ddd Tactical ReviewDetects anemic domain models, validates and refactors them into rich domain models, and enforces tactical DDD patterns (Entities, Value Objects, Aggregates, Domain Services, Domain Events). Use when the user asks to validate, review, or check domain models or DDD code; detect anemia; refactor domain objects; improve encapsulation; or mentions terms like "anemic model", "rich domain", "aggregate", "value object", "domain event", "ubiquitous language", "is this good DDD", "does this follow DDD"...Votes: 0GitHub stars: 3
- Decision Log记录或检索架构决策记录（ADR）——Nygard 模板（背景/决策/后果），带 proposed/accepted/superseded/rejected 状态机，写入 docs/decisions/NNN-slug.md 并更新索引表； 若项目保有交接存储，则在其中留一条引用行。当阶段内发生语义裁定或用户说 「记录裁定」「写进决策日志」「ADR」或要查「决策 X 的现状」时使用。不适用于： 撰写会话交接本身——交接存储只引用 ADR 编号、绝不复制正文。Votes: 0GitHub stars: 3
- Deep Codebase AnalysisDeep codebase analysis: read and analyze an entire software project's source to understand architecture, communication, design patterns, and business flows. Use when the user asks to analyze the overall structure of a whole codebase (exploring a new system, understanding architecture before maintenance, or scoping a refactor). NOT for: single-file edits, auditing one skill's SKILL.md, or reviewing a small diff — those belong to code-review / skill-description-audit.Votes: 0GitHub stars: 3
- Delegated ResearchInvestigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent. NOT for decisions the user must make, one-call lookups, or any code changes.Votes: 0GitHub stars: 3
- Dependency ScanDependency scan: detect CVEs and security issues in project dependencies, report severity with remediations, and optionally auto-fix by updating to patched versions. Also checks dependency health: outdated, deprecated, unmaintained, and license issues. Use when you need to audit packages for known vulnerabilities, fix vulnerable dependencies, or review dependency health across npm, pip, cargo, bundler, Go modules, and other ecosystems. NOT for: source-code security review, secrets or credenti...Votes: 0GitHub stars: 3
- Discovery Interview PrepPlan customer discovery interviews with the right goal, segment, constraints, and method. Use when preparing interviews for problem validation, churn research, or new product ideas.Votes: 0GitHub stars: 3
- Electron Best PracticesGuide AI agents through Electron app development with React including security patterns, type-safe IPC, React integration, packaging with code signing, and testing. Keywords: electron, electron-vite, electron-forge, contextBridge, IPC, security, react, packaging, code signing, notarization, playwright, desktop app. Use when building secure Electron apps with React/TypeScript (IPC, packaging, testing).Votes: 0GitHub stars: 3
- Env CheckEnvironment check: read-only health inspection of the local dev environment — toolchain presence/version/shadowing, PATH and proxy env vars, disk space and inodes, dev-port occupancy (--ports), dependency-tree integrity (node_modules, broken venvs), and WSL2/Windows interop (PATH injection, autocrlf, wsl.conf). Produces a structured report with fix commands; never executes fixes itself. Use when builds fail with "works on my machine" symptoms, commands resolve to wrong binaries, a proxy block...Votes: 0GitHub stars: 3
- Event StormingEventStorming facilitation knowledge and reference across Big Picture, Process Modeling, and Design-Level formats. Use when: 'run EventStorming', 'model a domain', 'discover bounded contexts', 'Big Picture session', 'map domain events', 'find aggregates', 'DDD workshop', 'bounded context heuristics'. Actions: --big-picture / --process / --design-level (format guidance), --patterns (facilitation patterns/anti-patterns), --glossary, --notation, --remote. No args: interactive discovery — checks ...Votes: 0GitHub stars: 3
- Executing PlansExecuting Plans: execute a written implementation plan — load the plan, review it critically, execute all tasks in order running the verifications each task specifies, and report when complete. Use when you have a written implementation plan to execute in a separate session, or when resuming a plan in a fresh session after an agent/tool switch (if your agent environment can run plans with subagents, prefer that — this skill executes solo). NOT for: verify-only stage completion checks against ...Votes: 0GitHub stars: 3
- Experiment HandoffExperiment handoff for mid-project experiments and spikes. Isolates a trial in a git worktree (default), an in-place branch, or a project copy; records a small experiment doc (.experiments/<slug>.md plus a generated index); supports handing off to another agent/session; and on close merges the validated change back into the project (full or partial) or discards it, then cleans up the sandbox. Auto-detects VCS and the isolation strategy, and records the base revision. This skill is mounted but...Votes: 0GitHub stars: 3
- Frontend DesignGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, color, motion, and interface copy that doesn't read as templated defaults. Use when designing or restyling a web page, landing page, dashboard, or app UI; when choosing fonts, palettes, layout, or a signature visual element; or when generated design looks generic and needs a stronger point of view. NOT for: accessibility/WCAG compliance review, UI ...Votes: 0GitHub stars: 3
- Git WorkflowGit workflow skill: branching strategies, Conventional Commits, creating or reviewing PRs, resolving PR review comments, merging PRs (CI verification, auto-merge queues, post-merge cleanup), PR review threads, signed commits, merge conflicts, Git+CI/CD integration, git hooks (lefthook, captainhook, husky, pre-commit), debugging hook-install failures in git worktrees, and GitHub release creation rules. Use when merging stalls on failing checks or unresolved review threads, when a hook fails to...Votes: 0GitHub stars: 3
- Grill MeUser-invoked entry that runs a plan-grilling session — a relentless one-question-at-a-time interview to sharpen a plan or design. Use when the user wants to stress-test a plan, decision, or idea before committing to it. USER-INVOKED ONLY: the agent must not auto-invoke this entry — the user runs it explicitly. NOT for gathering facts or doing research — grilling is for decisions, not lookups.Votes: 0GitHub stars: 3
- Intelligence Collection DisciplinesRun competitive research like an intelligence agency: eight collection disciplines (OSINT to MASINT), signal-to-inference chains, and fusion. Use when one-source research isn't enough.Votes: 0GitHub stars: 3
- Jobs To Be DoneUncover customer jobs, pains, and gains in a structured JTBD format. Use when clarifying unmet needs, repositioning a product, or improving discovery and messaging.Votes: 0GitHub stars: 3
- K6 Performancek6 performance testing: modern load testing with thresholds, scenarios, custom metrics, and env-based BASE_URL. Use when load/performance testing with k6 (thresholds, scenarios, metrics).Votes: 0GitHub stars: 3
- Llm Gateway OpsOperate the standing configuration of an application's model calls: multi-provider access over openai-compatible endpoints, capability matrices, routing and fallback chains, quota and rate-limit budgets, inference cost attribution, and the seven provider-specific failure classes (rate limits, auth, bad request, content filtering, server error, timeout, response-shape drift). Use when wiring a second provider, choosing a fallback chain, capping spend or throughput, or naming which model tier s...Votes: 0GitHub stars: 3
- Market Landscape ScanMarket Landscape Scan: map a market's segments, players, substitutes, and whitespace with cited evidence. Use when entering or re-evaluating a market before sizing, positioning, or picking competitors to study.Votes: 0GitHub stars: 3
- Marketing CopywritingMarketing copywriting: write, rewrite, or improve marketing copy for any page — homepage, landing, pricing, feature, about, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," "CTA copy," "value proposition," "tagline," "subheadline," "hero section copy," "above the fold," "this copy is weak," "make this more compelling," or "help me describe my product." Use whenever website text must persuade or convert...Votes: 0GitHub stars: 3
- Perf CheckMachine performance check: read-only sampling diagnosis of the dev machine's speed — memory pressure (MemAvailable gauge, swap thrash rate), CPU (load vs cores, utilization sampling), WSL2 resource tuning (cgroup ceilings, .wslconfig with autoMemoryReclaim advice), disk IO await per device, top CPU/memory processes, and macOS memory pressure (compressor gauge). Judgements follow the USE method; every threshold carries a basis tag (consensus vs heuristic). Read-only, tuning suggestions are com...Votes: 0GitHub stars: 3
- Pipeline 0to1NeonForge 本仓的 0→1 阶段流水线推进器（ADR-026）：9 段＋横切审计/经验沉淀， 工件冻结为唯一接口、出口闸红不放行、闸结果记 .handoff。当开始新一段、段内产出 工件、段出口过闸、或需要判断「现在在哪段/下一步做什么」时使用。只管推进与拦截， 不替段内技能干活（各段有自己的执行技能，见段表）。仅适用于 NeonForge 仓——正文绑 ADR-026、docs/decisions、docs/audits、.handoff 与段6 闸这套布局，别的仓没有即不适用。 NOT for: 段内干活本身（写阶段契约用 stage-spec、拆计划用 writing-plans、执行计划用 executing-plans、跑阶段 DoD 门禁用 stage-gate）——本件只判「现在在哪段、能不能放行」。Votes: 0GitHub stars: 3