- Skills
- 251
- 仓库
- 1
- 职业覆盖
- 11
- 场景覆盖
- 7
- Stars
- ★ 12
Danilo Stern-Sapad 的 Skills 251
youtube
Download YouTube video transcripts when user provides a YouTube URL or asks to download/get/fetch a transcript from YouTube. Also use when user wants to transcribe or get captions/subtitles from a YouTube video.
write-plan
Use when you have a spec or requirements for a multi-step task, before touching code. Produces an engineering plan complete with TDD tasks, DRY/SOLID/YAGNI principles, a required Test Plan & Verification section, and a coverage target — then auto-runs /plan-eng-review as an independent double-check before execution.
worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
web-perf
Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (LCP, INP, CLS) and supplementary metrics (FCP, TBT, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed. Biases towards retrieval from current documentation over pre-trained knowledge.
verify
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
validate-idea
Validate a business idea using the minimalist entrepreneur framework. Use when someone has a business idea and wants to test if it's worth pursuing before building anything.
test-coverage
Finds complex business logic, edge cases, corner cases, and past regressions that lack tests, then writes the missing unit tests (and integration/E2E tests when the risk genuinely crosses a boundary) — enforcing Google's Testing on the Toilet best practices (real > fake > mock, don't mock types you don't own, verify state not queries, avoid change-detector tests, DAMP over DRY in tests, limit mocks per test). Use when asked to "add tests", "cover edge cases", "check test coverage", "write missing tests", "harden the tests", "test this properly", or "make sure this is tested".
tdd
Use when implementing any feature or bugfix, before writing implementation code
tapestry
Unified content extraction and action planning. Use when user says "learn-this <URL>", "learn this <URL>", "weave <URL>", "help me plan <URL>", "extract and plan <URL>", "make this actionable <URL>", or similar phrases indicating they want to extract content and create an action plan. Automatically detects content type (YouTube video, article, PDF) and processes accordingly.
superskills-upgrade
Upgrade superskills to the latest version. Pulls from GitHub, re-runs setup, and shows the version change. Use when asked to "upgrade superskills", "update superskills", or "get the latest version of superskills".
superskills-doctor
Diagnose a superskills install WITHOUT changing anything: install kind, which skills are linked, VERSION vs the plugin manifests, gstack (real clone or vendor stopgap), bun and optional tools. Use when a skill is missing or won't trigger, a pull or upgrade looks stale, setup failed, or the user asks whether superskills is healthy, ready, or installed correctly. Read-only: it never installs, pulls, or re-runs setup — to fix things use /superskills-upgrade.
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
quota-resilience
Salvage and resume when the session hits its own usage limit / quota hard stop: commit complete work, leave a clean tree, write a committed resume note, report exact state, and offer one bounded auto-restart where the host can schedule one. Use when the agent's own usage limit, quota, or rate budget is exhausted mid-task, or when picking up work a session left when it died that way. Not for HTTP 429s / rate limits the user's application receives — that is application behavior (/debug, /qa), not agent state.
qa-full
Full per-feature QA pipeline: audit → fix → verify. Runs the complete multi-dimensional fan-out (tests, correctness, security, DB, frontend perf, browser QA, design, accessibility, coverage) scoped to the current branch's diff, FIXES what each check finds, re-verifies the fixes, then emits a pass/fail ship-readiness verdict on the repaired branch. Run it when a feature is finished, before /finish-branch and /ship. Use when asked to "run full QA", "qa-full", "feature done — check it", "is this ready to ship", "pre-ship check", "full quality gate", or "fix everything before ship".
pricing
Help figure out pricing for a product or service using minimalist entrepreneur principles. Use when someone is setting prices, considering price changes, or struggling with what to charge.
playwright
End-to-end testing with Playwright — generate, run, and debug E2E tests.
perf-profile
Performance profiling — measures code execution time, DB call time, and identifies bottlenecks at both the application and database layer. Use when asked to "profile performance", "measure execution time", "find bottlenecks", "check response times", or "why is this slow".
pentest
Authorized security testing — source-code vulnerability hunting, driven by this session's own model by default; network scanning via clearwing when that is genuinely needed and authorized; and exploit verification against a live authorized web application via the vendored Shannon, likewise driven by this session's model. Use when asked to "pentest", "security scan", "hunt vulnerabilities", "scan this code for exploits", or "scan a host". Not for a routine diff review (use /defense for OWASP/secrets, /iac-scan for deploy config, /code-review for correctness).