Bold Architectural Refactor FAQs

Question 1

What are the conceptual lenses used by this skill?

Accepted Answer

It uses frameworks like Elimination (what if we deleted this?), Unification (what if these different things are actually the same?), and Inversion (what if we flipped control?) to view code from new perspectives.

Question 2

How is this different from standard AI refactoring?

Accepted Answer

Most AI refactors perform 'housekeeping' like renaming or extracting helpers. Bold Refactor ignores these cosmetic changes to focus on radical structural reimagining and eliminating redundant code through better architecture.

Question 3

Does this skill automatically modify my source code?

Accepted Answer

No, it is a design-first tool. It produces a detailed design document including file paths and signatures, which you can then review and execute using an implementation tool or manual coding.

Question 4

When is the best time to use Bold Refactor?

Accepted Answer

Use it when a subsystem feels 'heavy,' when you are struggling with high cyclomatic complexity, or when you suspect a simpler abstraction exists but can't quite identify it.

Question 5

Does it support incremental changes?

Accepted Answer

Bold Refactor specifically avoids incrementalism. It is designed for 'bold' changes that provide high architectural leverage, though it allows you to narrow the scope during the interactive discussion phase.

Bold Architectural Refactor

Bold Architectural Refactor

Key Features

Use Cases

Key Features

Use Cases