Loading...
Loading...
Found 344 Skills
Red-green-refactor development methodology requiring verified test coverage. Use for feature implementation, bugfixes, refactoring, or any behavior changes where tests must prove correctness.
Vitest testing framework patterns for test setup, async testing, mocking with vi.*, snapshots, and test performance (formerly test-vitest). This skill should be used when writing or debugging Vitest tests. This skill does NOT cover TDD methodology (use test-tdd skill), API mocking with MSW (use test-msw skill), or Jest-specific APIs.
Help create and optimize blog posts, articles, and polished writing with rigorous structure, reader expectation management, and SCQA methodology. This skill contains a specialized writing framework (reader personas, concept introduction protocol, diagnostic checklists, Pyramid Principle structure) that cannot be replicated without loading it. You must use this skill in any of these scenarios: (1) writing a blog post or article from notes/materials, (2) reviewing, diagnosing, or optimizing any draft or article for structure, clarity, and readability, (3) polishing or refining notes into publishable form, (4) giving feedback on writing structure, flow, or reader experience, (5) creating outlines for articles. Trigger on keywords: "博客", "文章", "发布", "blog", "写作", "初稿", "打磨", "诊断", "优化文章", "结构", "大纲", "投稿", "公众号", "读者". Also trigger when the user shares a markdown file and asks to improve it, or asks if something "reads well" or "makes sense to readers".
Apply Edward de Bono's Six Thinking Hats methodology to software testing for comprehensive quality analysis. Use when designing test strategies, conducting test retrospectives, analyzing test failures, evaluating testing approaches, or facilitating testing discussions. Each hat provides a distinct testing perspective: facts (White), risks (Black), benefits (Yellow), creativity (Green), emotions (Red), and process (Blue).
Content Scaled Production - Efficient Methodology from Solo Creation to Systematic Content Factory
Write copy that gets a "yes" using Joanna Wiebe's research-first, Voice of Customer methodology Use when: **Writing landing pages, emails, or sales pages** that need measurable conversion results; **Starting a new copy project** and need a systematic process to follow; **Struggling with what to write** and staring at a blank page; **Wanting to prove ROI** to clients with data-backed decisions; **Improving existing copy** through validation and testing
Comprehensive growth strategy expertise combining SEO/SMO/CRO implementation, marketplace and network effects frameworks (Andrew Chen), growth loops methodology (Brian Balfour/Reforge), and Silicon Valley growth thinking. Use when building growth strategy, designing growth loops, improving SEO/SMO/CRO, planning acquisition channels, building network effects, or scaling product-led growth. Growth is not marketing — it's systematic application of product, engineering, and data.
Interface Craft by Josh Puckett — a toolkit for building polished, animated interfaces in React. Includes Storyboard Animation (human-readable animation DSL with stage-driven sequencing), DialKit (live control panels for tuning animation values), and Design Critique (systematic UI review based on Josh Puckett's methodology). Triggers on: animate, animation, transition, storyboard, entrance, motion, spring, easing, timing, dialkit, sliders, controls, tune, tweak, critique, review, feedback, audit, improve, polish, refine, redesign.
Go-specific code review with 6-phase methodology: Context, Automated Checks, Quality Analysis, Specific Analysis, Line-by-Line, Documentation. Use when reviewing Go code, PRs, or auditing Go codebases for quality and best practices. Use for "review Go", "Go PR", "check Go code", "Go quality", "review .go". Do NOT use for writing new Go code, debugging Go bugs, or refactoring -- use golang-general-engineer, systematic-debugging, or systematic-refactoring for those tasks.
Go testing patterns and methodology: table-driven tests, t.Run subtests, t.Helper helpers, mocking interfaces, benchmarks, race detection, and synctest. Use when writing new Go tests, modifying existing tests, adding coverage, fixing failing tests, writing benchmarks, or creating mocks. Triggered by "go test", "_test.go", "table-driven", "t.Run", "benchmark", "mock", "race detection", "test coverage". Do NOT use for non-Go testing (use test-driven-development instead), debugging test failures (use systematic-debugging), or general Go development without test focus (use golang-general-engineer directly).
Use when writing specifications for features, projects, or requirements — applies Jobs to Be Done (JTBD) methodology with acceptance criteria focus, no implementation details, and SLC release planning
Download, split, and deeply read academic PDFs for teaching preparation or research. Works with Cowork to split PDFs into 4-page chunks, read in batches, and produce structured reading notes on research methodology and contributions.