Refactoring
Code restructuring and optimization
aipoint-brand
by kcchien
Apply AIPoint brand guidelines to presentations, documents, and designs. Use this skill when creating or styling any content for AIPoint including: presentations (PPTX), documents (DOCX), web designs, marketing materials, or any visual content requiring AIPoint branding. Triggers: "AIPoint brand", "our brand", "company colors", "brand guidelines", "AIPoint style", or when working on AIPoint materials.
improve-skill
by mauromedda
Analyze Claude Code session transcripts to improve existing skills or create new ones. Use when you want to review a past session to identify what worked, what didn't, and how to enhance skill documentation. Extracts session data and provides structured analysis prompts. Triggers on "improve skill", "analyze session", "review session", "skill improvement", "create skill from session", "skill not working", "skill missed", "skill didn't trigger", "enhance skill", "refine skill", "skill feedback", "session transcript", "what went wrong", "skill optimization", "better triggers".
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.
liquid-glass
by patrickserrano
Implement, review, or improve SwiftUI features using the iOS 26+ Liquid Glass API. Use when asked to adopt Liquid Glass in SwiftUI UI, refactor to Liquid Glass, or review Liquid Glass usage.
single-responsibility-principle
by yanko-belov
Use when creating or modifying classes, modules, or functions. Use when feeling pressure to add functionality to existing code. Use when class has multiple reasons to change.
clean-architecture
by G1Joshi
Clean Architecture layered design. Use for maintainable code.
optimize-post
by masayan1126
原稿からXのアルゴリズムに最適化されたポスト内容を生成。「X投稿を最適化」「ツイート作成」などで使用。
test-driven-development
by mrtolkien
Use when implementing any feature or bugfix, before writing implementation code
test-driven-development
by aiaiohhh
Use when implementing any feature or bugfix, before writing implementation code
gather
by jesseposner
Pause and reset. Gather what's scattered, commit what's ready, prepare for what's next.
ac-tdd-runner
by adaptationio
Run TDD cycle for feature implementation. Use when implementing features with RED-GREEN-REFACTOR, running test-driven development, automating TDD workflow, or ensuring test-first development.
ac-context-optimizer
by adaptationio
Optimize context usage for autonomous coding. Use when managing context window, prioritizing information, reducing token usage, or improving efficiency.
referral-program
by aiaiohhh
"When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy. Also use when the user mentions 'referral,' 'affiliate,' 'ambassador,' 'word of mouth,' 'viral loop,' 'refer a friend,' or 'partner program.' This skill covers program design, incentive structure, and growth optimization."
Clean Architecture Patterns
by Kaakati
"Domain, Data, and Presentation layer separation with dependency inversion and use case patterns"
tailored-resume-generator
by founderjourney
Analyze job postings and customize resumes to highlight relevant experience, skills, and achievements. Optimizes for ATS systems and interview success.
clean-architecture-ios
by Kaakati
"Expert Clean Architecture decisions for iOS/tvOS: when Clean Architecture adds value vs overkill, layer boundary judgment calls, dependency rule violations to catch, and practical trade-offs between purity and pragmatism. Use when designing app architecture, debugging layer violations, or deciding what belongs where. Trigger keywords: Clean Architecture, layer, domain, data, presentation, use case, repository, dependency rule, entity, DTO, mapper"
brand-logo
by phrazzld
Generate and optimize brand logos. LLM SVG generation with SVGO optimization, favicon variants, and vision-model critique loop.
yc-sv-development-framework
by founderjourney
Decision-making framework for software development, Y Combinator / Silicon Valley style. Based on real principles from Paul Graham, Sam Altman, Michael Seibel, Patrick Collison, and Brian Chesky. Use when: - Developing features or products - Making technical decisions (what to do, how, when) - Prioritizing work (P0, P1, P2) - Evaluating whether to refactor or patch - Deciding on technical debt - Evaluating whether to add tests, CI/CD, or automation - Any architecture or engineering decision Triggers: development, code, feature, refactor, architecture, prioritize, technical decision, what to do first, technical debt, tests, CI/CD, sprint, backlog
GetX State Management Patterns
by Kaakati
"GetX controllers, reactive state, dependency injection, bindings, navigation, and best practices"
refactoring-expert
by samhvw8
"Systematic code refactoring following Martin Fowler's catalog. Methodologies: characterization tests, Red-Green-Refactor, incremental transformation. Capabilities: SOLID compliance, DRY cleanup, code smell detection, complexity reduction, legacy modernization, design patterns, functional programming patterns. Actions: refactor, extract, inline, rename, move, simplify code. Keywords: refactor, SOLID, DRY, code smell, complexity, extract method, inline, rename, move, clean code, technical debt, legacy code, design pattern, characterization test, Red-Green-Refactor, functional programming, higher-order function, immutability, pure function, composition, currying, side effects. Use when: improving code quality, reducing technical debt, applying SOLID principles, fixing DRY violations, removing code smells, modernizing legacy code, applying design patterns."
tdd
by inkeep
Universal test-driven development methodology and test design craft. Background knowledge for writing behavior-focused tests, mocking strategy, vertical slicing, and tracer bullet execution. Auto-loaded when writing tests during implementation, review feedback, or standalone test authoring. Triggers: writing tests, test design, mocking strategy, test quality, behavior testing, integration testing, test-first, red-green-refactor.
clean-typescript
by academind
Write clean, efficient TypeScript code that follows common best practices
refactor:flutter
by SnakeO
Refactor Flutter/Dart code to improve maintainability, readability, and performance. This skill applies Dart 3 features like records, patterns, and sealed classes, implements proper state management with Riverpod or BLoC, and uses Freezed for immutable models. It addresses monolithic widgets, missing const constructors, improper BuildContext usage, and deep nesting. Apply when you notice widgets doing too much, performance issues from unnecessary rebuilds, or legacy Dart 2 patterns.
refactor:pandas
by SnakeO
Refactor Pandas code to improve maintainability, readability, and performance. Identifies and fixes loops/.iterrows() that should be vectorized, overuse of .apply() where vectorized alternatives exist, chained indexing patterns, inplace=True usage, inefficient dtypes, missing method chaining opportunities, complex filters, merge operations without validation, and SettingWithCopyWarning patterns. Applies Pandas 2.0+ features including PyArrow backend, Copy-on-Write, vectorized operations, method chaining, .query()/.eval(), optimized dtypes, and pipeline patterns.