refactor-design-report

Generate a code-grounded refactor design report with implementation order and acceptance criteria.

139|20|Updated Jul 5, 2025

Search Tags:#architecture #frontend #backend #refactor #code-quality #design-report

Ready to run

npx skills add https://github.com/penwyp/ClaudePreference --skill refactor-design-report

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: refactor-design-report
Source: https://github.com/penwyp/ClaudePreference/tree/main/skills/refactor-design-report
Command: npx skills add https://github.com/penwyp/ClaudePreference --skill refactor-design-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a durable engineering report that turns concrete problems, gaps, and review findings into an executable refactor or architecture design document grounded in the current code and contracts. The report aggregates identified issues, goals, constraints, risks, and recommended changes across backend and frontend, providing a clear path for validation, rollout, and acceptance criteria.

Core Features & Use Cases

Grounded design reports anchored to real code and contracts.
Target semantics, backend/frontend changes, validation strategy, implementation order, and acceptance criteria.
Optional persistence: write the design document to the appropriate docs location; otherwise present the report in the reply.

Quick Start

Describe the concrete problems and desired outcomes, then request a code-grounded refactor design report.

Frequently Asked Questions about refactor-design-report

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

FAQPage Schema

How do I turn architecture review findings into a refactor design document?▼

A refactor design report converts architecture review findings into a code-grounded design document by aggregating identified problems, outlining target backend and frontend changes, validation strategy, implementation order, and acceptance criteria into a durable engineering report.

What should a backend and frontend refactor report include for code review?▼

A refactor report should include target semantics, required backend and frontend changes, validation strategies, implementation order, acceptance criteria, and rollback and rollout guidance, all grounded in current code and contracts.

How do I document API and UI mismatches as an executable refactor plan?▼

Document API and UI mismatches by grounding the refactor design report in current code and contracts, then outlining target models, required changes, validation strategies, and implementation order to produce a testable design.

Can I persist a refactor design report to a documentation location?▼

Yes, the refactor design report supports optional persistence, writing the generated design document to the appropriate docs location, or otherwise presenting the complete report directly in the reply.

Does this approach work for both feature requests and design gaps?▼

Yes, the refactor design report applies to bugs, API and UI mismatches, design gaps, and feature requests across both backend and frontend contexts, turning them into a durable, testable design with rollout guidance.

What are the limitations of code-grounded refactor design reports?▼

Refactor design reports depend on accurate identification of technical problems and product gaps beforehand, and require grounding in existing code and contracts to produce a testable design with meaningful validation and acceptance criteria.