refactor

Refactor Retrograde procedural generation passes using a structured checklist.

12|1|Updated Jan 16, 2024
One-click install
npx skills add https://github.com/kaosnyrb/FrankyCLI --skill refactor-kaosnyrb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: refactor
Source: https://github.com/kaosnyrb/FrankyCLI/tree/main/.claude/skills/refactor
Command: npx skills add https://github.com/kaosnyrb/FrankyCLI --skill refactor-kaosnyrb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides systematic refactoring of Retrograde procedural generation passes, applying established patterns and a checklist to improve readability and maintainability.

Core Features & Use Cases

  • Extract configuration, rename constants, and extract methods to reduce complexity.
  • Improve readability and maintainability of Retrograde passes across various pipelines.
  • Apply consistent documentation and stage-based planning to scale refactors.

Quick Start

Apply the refactor skill to a Retrograde pass and verify builds after each step.

Frequently Asked Questions about refactor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I refactor procedural generation passes to improve code maintainability?

Refactoring procedural generation passes involves extracting configuration, reducing parameters via context objects, and applying descriptive naming to improve maintainability. A structured checklist guides incremental extractions and documentation across multiple files.

What is the best way to clean up complex topology and generation pipeline code?

Cleaning up topology and generation pipeline code requires stage-based planning that extracts methods, enforces configuration extraction, and scaffolds unit-test friendly structures to ensure a maintainable codebase.

Can I use a structured checklist to guide incremental refactoring across multiple files?

Yes, a structured checklist guides incremental refactoring across multiple files by enforcing configuration extraction, method extraction with descriptive names, and parameter reduction, ensuring documentation and unit-test friendly scaffolding at each step.

Why does my procedural generation code become difficult to maintain as pipelines scale?

Procedural generation code becomes difficult to maintain as pipelines scale due to high parameter counts, embedded configurations, and complex method bodies. Extracting methods, using context objects, and applying consistent documentation resolves this maintainability degradation.

Does refactoring architecture patterns help with reducing method parameters in generation passes?

Refactoring with architecture patterns reduces method parameters in generation passes by introducing context objects to bundle parameters, lowering complexity and making procedural generation code easier to test and maintain.