refactor

pproenca/dot-skills · updated Jun 1, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/pproenca/dot-skills --skill refactor
0 commentsdiscussion
summary

Comprehensive code refactoring guide based on Martin Fowler's catalog and Clean Code principles, designed for AI agents and LLMs. Contains 43 rules across 8 categories, prioritized by impact to guide automated refactoring and code generation.

skill.md

Fowler/Martin Code Refactoring Best Practices

Comprehensive code refactoring guide based on Martin Fowler's catalog and Clean Code principles, designed for AI agents and LLMs. Contains 43 rules across 8 categories, prioritized by impact to guide automated refactoring and code generation.

When to Apply

Reference these guidelines when:

  • Refactoring existing code to improve maintainability
  • Decomposing long methods or large classes
  • Reducing coupling between components
  • Simplifying complex conditional logic
  • Reviewing code for code smells and anti-patterns

Rule Categories by Priority

Priority Category Impact Prefix
1 Structure & Decomposition CRITICAL struct-
2 Coupling & Dependencies CRITICAL couple-
3 Naming & Clarity HIGH name-
4 Conditional Logic HIGH cond-
5 Abstraction & Patterns MEDIUM-HIGH pattern-
6 Data Organization MEDIUM data-
7 Error Handling MEDIUM error-
8 Micro-Refactoring LOW micro-

Quick Reference

1. Structure & Decomposition (CRITICAL)

  • struct-extract-method - Extract Method for Long Functions
  • struct-single-responsibility - Apply Single Responsibility Principle
  • struct-extract-class - Extract Class from Large Class
  • struct-compose-method - Compose Method for Readable Flow
  • struct-function-length - Keep Functions Under 20 Lines
  • struct-replace-method-with-object - Replace Method with Method Object
  • struct-parameter-object - Introduce Parameter Object

2. Coupling & Dependencies (CRITICAL)

  • couple-dependency-injection - Use Dependency Injection
  • couple-hide-delegate - Hide Delegate to Reduce Coupling
  • couple-remove-middle-man - Remove Middle Man When Excessive
  • couple-feature-envy - Fix Feature Envy by Moving Methods
  • couple-interface-segregation - Apply Interface Segregation Principle
  • couple-preserve-whole-object - Preserve Whole Object Instead of Fields

3. Naming & Clarity (HIGH)

  • name-intention-revealing - Use Intention-Revealing Names
  • name-avoid-abbreviations - Avoid Abbreviations and Acronyms
  • name-consistent-vocabulary - Use Consistent Vocabulary
  • name-searchable-names - Use Searchable Names
  • name-avoid-encodings - Avoid Type Encodings in Names

4. Conditional Logic (HIGH)

  • cond-guard-clauses - Replace Nested Conditionals with Guard Clauses
  • cond-polymorphism - Replace Conditional with Polymorphism
  • cond-decompose - Decompose Complex Conditionals
  • cond-consolidate - Consolidate Duplicate Conditional Fragments
  • cond-special-case - Introduce Special Case Object
  • cond-lookup-table - Replace Conditional with Lookup Table

5. Abstraction & Patterns (MEDIUM-HIGH)

  • pattern-strategy - Extract Strategy for Algorithm Variants
  • pattern-template-method - Use Template Method for Shared Skeleton
  • pattern-factory - Use Factory for Complex Object Creation
  • pattern-open-closed - Apply Open-Closed Principle
  • pattern-composition-over-inheritance - Prefer Composition Over Inheritance
  • pattern-extract-superclass - Extract Superclass for Common Behavior

6. Data Organization (MEDIUM)

  • data-encapsulate-collection - Encapsulate Collection
  • data-replace-primitive - Replace Primitive with Object
  • data-encapsulate-record - Encapsulate Record into Class
  • data-split-variable - Split Variable with Multiple Assignments
  • data-replace-temp-with-query - Replace Temp with Query

7. Error Handling (MEDIUM)

  • error-exceptions-over-codes - Use Exceptions Instead of Error Codes
  • error-custom-exceptions - Create Domain-Specific Exception Types
  • error-fail-fast - Fail Fast with Preconditions
  • error-separate-concerns - Separate Error Handling from Business Logic

8. Micro-Refactoring (LOW)

  • micro-remove-dead-code - Remove Dead Code
  • micro-inline-variable - Inline Trivial Variables
  • micro-simplify-expressions - Simplify Boolean Expressions
  • micro-rename-for-clarity - Rename for Clarity

How to Use

Read individual reference files for detailed explanations and code examples:

Full Compiled Document

For the complete guide with all rules expanded: AGENTS.md

how to use refactor

How to use refactor on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add refactor
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/pproenca/dot-skills --skill refactor

The skills CLI fetches refactor from GitHub repository pproenca/dot-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/refactor

Reload or restart Cursor to activate refactor. Access the skill through slash commands (e.g., /refactor) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.756 reviews
  • Yusuf Gupta· Dec 24, 2024

    refactor reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Aditi Sanchez· Dec 20, 2024

    Registry listing for refactor matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Yash Thakker· Dec 8, 2024

    We added refactor from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Liam Sanchez· Nov 15, 2024

    Registry listing for refactor matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Valentina Jackson· Nov 11, 2024

    refactor reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Arya Park· Nov 11, 2024

    refactor is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Diego Menon· Oct 6, 2024

    refactor fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Advait Chen· Oct 2, 2024

    I recommend refactor for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Arya Ndlovu· Oct 2, 2024

    Useful defaults in refactor — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Noor Desai· Sep 17, 2024

    Solid pick for teams standardizing on skills: refactor is focused, and the summary matches what you get after install.

showing 1-10 of 56

1 / 6