Refactoring
Code restructuring and optimization
sales-funnel-design
by JK-0001
Design and optimize a sales funnel for a solopreneur business. Use when mapping how customers move from first awareness to paying customer, identifying where leads drop off, building or improving any stage of the funnel (awareness, consideration, decision, retention), or optimizing conversion rates. Covers funnel architecture, stage-by-stage tactics, conversion benchmarks, solopreneur-specific funnel models (self-serve vs. high-touch), and funnel analytics. Trigger on "sales funnel", "design my funnel", "optimize my funnel", "conversion funnel", "why aren't people buying", "lead to customer", "funnel stages", "improve conversions".
vroid
by Logos-Liber
Vroid Studio, VRM format, and VTuber avatar creation
asset-optimization
by Logos-Liber
Polygon reduction, LOD creation, texture compression, and real-time optimization
ruby-on-rails
by faqndo97
Build Ruby on Rails features from scratch through production. Full lifecycle - build, debug, test, optimize, refactor. Follows Vanilla Rails philosophy (37signals/DHH), SOLID principles, and Rails 8 patterns.
Test-Driven Development (TDD) Workflow
by ShunsukeHayashi
Miyabi Plugins for Claude Code - 25+ Agents, 22 Skills, 50+ Commands
data-sleuth
by petekp
Identify non-obvious signals, hidden patterns, and clever correlations in datasets using investigative data analysis techniques. Use when analyzing social media exports, user data, behavioral datasets, or any structured data where deeper insights are desired. Pairs with personality-profiler for enhanced signal extraction. Triggers on requests like "what patterns do you see", "find hidden signals", "correlate these datasets", "what am I missing in this data", "analyze across datasets", "find non-obvious insights", or when users want to go beyond surface-level analysis. Also use proactively when you notice interesting anomalies or correlations during any data analysis task.
code-simplify
by PaulRBerg
This skill should be used when the user asks to "simplify code", "clean up code", "refactor for clarity", "reduce complexity", "improve readability", "make this easier to maintain", or asks to simplify recently modified code.
checkpoint
by petekp
Meta-cognitive decision support that analyzes current context and surfaces intelligent next-step options to the user. Use this skill when: (1) User explicitly invokes /checkpoint, (2) Significant work has been completed and a checkpoint is valuable, (3) Uncertainty or ambiguity exists about requirements or approach, (4) Task complexity has expanded beyond initial scope, (5) Before finalizing or committing to ensure nothing is missed. This skill pauses execution, assesses the situation holistically, and presents 2-5 contextually-appropriate options via AskUserQuestion, with a recommended option and rationale.
engineering-discipline
by duyet
Core engineering principles for sustainable, maintainable code. No shortcuts, no hacks. Quality gates before completion.
code-polish
by PaulRBerg
This skill should be used when the user asks to "polish code", "simplify and review", "clean up and review code", "full code polish", "simplify then review", "refactor and review", "simplify and fix", "clean up and fix", or wants a combined simplification and review workflow on recently changed code.
TDD Workflow
by ShunsukeHayashi
Test-Driven Development workflow for Miyabi. Red-Green-Refactor cycle with Rust-specific patterns. Use when implementing new features, fixing bugs, or writing tests.
TDD Workflow
by ShunsukeHayashi
Test-Driven Development workflow for Miyabi. Red-Green-Refactor cycle with Rust-specific patterns. Use when implementing new features, fixing bugs, or writing tests.
android-build
by hyperb1iss
Use when building Android apps (Gradle CLI) or ROMs (AOSP, LineageOS). Triggers on "gradle build", "assemble", "AOSP", "LineageOS", "lunch", "mka", "breakfast", "brunch", "compile android", "device tree", "kernel build".
brand-logo
by phrazzld
Generate and optimize brand logos. LLM SVG generation with SVGO optimization, favicon variants, and vision-model critique loop.
learning-notes-organizer
by z-soulx
整理与重构已有学习笔记：重划边界、归类重组、合并冗余、精简口语化表达；优化排版与可读性；为各部分补充引导与注释；按从基础到高级建立学习路径并打通知识关联；同时尽量保留原文 Markdown/HTML 强调标记（如 ==高亮==、、Setext 标题等），输出结构清晰、可检索、便于长期维护的笔记体系。
section-refactor-with-todo-routing
by z-soulx
基于 learning-notes-organizer 的方法论，对指定文件执行"全标题索引+含义/引导注释 + 指定章节重构 + 越界内容路由到合适标题并按需新增待整理容器"的局部重构工作流；用 planning-with-files 输出抽取→规划→映射→交付，范围外章节默认不改，仅做迁移所需最小改动。
pmf-survey
by wdavidturner
Use when asked to "PMF survey", "measure product-market fit", "40% rule", "Sean Ellis test", "Rahul Vohra method", or "how disappointed would you be". Helps quantify product-market fit and systematically improve it. The PMF Survey framework (created by Sean Ellis, popularized by Rahul Vohra at Superhuman) measures how disappointed users would be without your product and turns that data into a roadmap.
okrs
by wdavidturner
Use when asked to "set OKRs", "objectives and key results", "quarterly OKR planning", "align objectives", "measure OKR progress", or "focus priorities with OKRs". Helps teams focus on what matters most and create a cadence of progress. The OKR framework (originated by Andy Grove at Intel, popularized by John Doerr at Google) creates alignment, focus, and learning cycles. Christina Wodtke's Radical Focus approach emphasizes simplicity and avoiding common pitfalls.
code-refactoring
by Zpankz
The practice of restructuring and simplifying code continuously – reducing complexity, improving design, and keeping codebases clean.
code-refactoring
by DauQuangThanh
Guides systematic code refactoring to improve code quality, maintainability, and design. Identifies code smells, applies refactoring patterns, ensures test coverage, and follows safe refactoring practices. Produces cleaner, more maintainable code while preserving functionality. Use when improving code quality, eliminating technical debt, preparing for feature additions, addressing code smells, or when users mention refactoring, code cleanup, improving design, reducing complexity, or modernizing legacy code.
swift-api-design-guidelines-skill
by Erikote04
Write, review, or improve Swift APIs using Swift API Design Guidelines for naming, argument labels, documentation comments, terminology, and general conventions. Use when designing new APIs, refactoring existing interfaces, or reviewing API clarity and fluency.
hierarchy-of-engagement
by wdavidturner
Use when asked to "define our core action", "North Star metric", "accruing benefits", "improve retention mechanics", "hierarchy of engagement", or "Sarah Tavel framework". Helps consumer products identify the actions and benefits that drive long-term retention. The Hierarchy of Engagement framework (created by Sarah Tavel at Benchmark) maps progression from core action to mounting loss.
song-lyrics
by adamos486
Provides insights and techniques from renowned songwriters across different genres to help users improve their own lyrical compositions.
complexity-guardrails
by noartem
Keep cyclomatic complexity low; flatten control flow, extract helpers, and prefer table-driven/strategy patterns over large switches