Refactoring
Code restructuring and optimization
skill-optimizer-yashu
by steelan9199
分析并优化其他 Skill 的文档质量问题，包括 frontmatter 格式、渐进式披露结构、文件引用完整性、AI 友好性等检查。何时使用：当用户说"优化这个 skill"、"检查 skill 质量"、"review skill"、"skill 有问题"、"帮我看看这个 skill"、"诊断 skill"时。
db-query-optimization
by KentoShimizu
"Query optimization workflow for reducing latency and resource cost through plan-aware rewrites and access-path improvements. Use when hot-path query behavior is the bottleneck; do not use for conceptual schema redesign without workload evidence."
rotz-dotfiles
by gwenwindflower
Use when working with a rotz-based dotfiles repository. This includes: (1) Managing tools or apps (adding, configuring, or removing), (2) Modifying rotz configuration files (dot.yaml, defaults.yaml, config.yaml), (3) Updating tool configurations managed by rotz (mise.toml, config.fish, etc.), (4) Restructuring the dotfiles hierarchy, (5) Planning architectural changes to the dotfiles project.
youtube-transcript
by Jst-Well-Dan
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.
pw-redbook-image
by plugins-world
将文章内容拆解为小红书风格的系列配图。支持从 URL、文件或文本生成封面图、内容图和结尾图，自动创建提示词并调用图片生成工具。
TDG Test-Driven Generation
by chanwit
Test-Driven Generation uses TDD (Test-Driven Development) techniques to generate tests and code in Red-Green-Refactor loops. Key words to detect are tdg, TDG.
testing-strategy
by block
Guidelines for writing effective tests in this project
retro
by alunadev
"Facilitates a sprint retrospective using Start/Stop/Continue, 4Ls, or Sailboat format, producing 2-3 prioritized action items with owners and deadlines. Use after a sprint or milestone to drive continuous improvement. Triggers on: retrospective, retro, sprint review, what went well, lessons learned, team improvement, action items, start stop continue, post-mortem, sprint reflection."
tdd-workflow
by DoubleslashSE
Test-Driven Development workflow for .NET. Use when implementing features, fixing bugs, or writing new code. Guides RED-GREEN-REFACTOR cycle with proper test design.
tdd-workflow
by peopleforrester
Test-driven development workflow for implementing new features and fixing bugs. Use when the user mentions TDD, "write tests first", "red-green-refactor", or when implementing features that need comprehensive test coverage.
docs-maker
by alpoxdev
Create and refactor AI-readable structured documentation for any domain, optimized for fast parsing, recall, and reliable execution.
refactoring-guide
by peopleforrester
Safe refactoring patterns and techniques. Use when the user wants to improve code structure, reduce duplication, or make code more maintainable without changing behavior. Emphasizes incremental changes with test coverage.
dotnet-build
by DoubleslashSE
.NET build configuration and error handling. Use when building projects, diagnosing build errors, or configuring build options.
youtube-downloader
by cdeistopened
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.
anti-ai-writing
by cdeistopened
Transform AI-assisted drafts into authentic, human-sounding content. This skill provides patterns to detect and eliminate AI tells, frameworks for natural writing, and techniques for creating prose that reads as genuinely human. Use when reviewing any AI-generated content or when writing content that must not appear AI-assisted.
swift-patterns
by efremidze
Review, refactor, or build SwiftUI features with correct state management, modern API usage, optimal view composition, navigation patterns, performance optimization, and testing best practices.
open-closed-principle
by yanko-belov
Use when adding new functionality to existing code. Use when tempted to add if/else or switch branches. Use when extending behavior of existing classes.
test-driven-development
by yanko-belov
Use when implementing any new feature or function. Use when asked to "add tests later". Use when writing code before tests.
faion-code-quality
by faionfaion
"Code quality specialist: architecture patterns, refactoring, code review, development practices. 23 methodologies."
jobs-to-be-done
by wdavidturner
Use when asked to "jobs to be done", "JTBD", "why customers churn", "prep for customer interviews", "hire and fire products", or "find real competitors". Helps discover unmet needs and the context behind purchasing decisions. The Jobs to be Done framework (created by Clayton Christensen and Bob Moesta) explains why customers hire and fire products.
thinking-in-bets
by wdavidturner
Use when asked to "thinking in bets", "make decisions under uncertainty", "think probabilistically", "avoid resulting", "separate decision quality from outcomes", or "reduce bias in decisions". Helps make explicit bets and evaluate decisions on process, not results. The Thinking in Bets framework (from Annie Duke) applies poker strategy to business and life decisions.
craftsmanship
by Tyler-R-Kendrick
Use when applying software craftsmanship principles — code quality, professional practices, and continuous improvement drawn from canonical works. USE FOR: code quality principles, Boy Scout Rule, DRY/KISS/YAGNI, craftsmanship practices, choosing quality improvement approaches DO NOT USE FOR: specific principle details (use clean-code, solid, refactoring sub-skills), architecture decisions (use dev/architecture), testing strategy (use testing)
pyscf
by tondevrel
Comprehensive guide for PySCF - Python-based Simulations of Chemistry Framework. Use for ab initio quantum chemistry calculations including Hartree-Fock, DFT, MP2, CCSD, geometry optimization, excited states, and molecular properties. Industry-standard library for electronic structure calculations.
architecture-clean-architecture
by KentoShimizu
"Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications."