react-single-responsibility

Apply these strategies to keep components, hooks, and methods focused, testable, and readable. Rules are split into component, hook, and method simplification.

| KISS | Simplest solution that works. Avoid over-engineering. | | Single responsibility | One clear responsibility per component or function; extract utilities, hooks, sub-components. | | DRY | Extract common logic; create reusable functions or components. | | YAGNI | Don't build features before they're needed. |

| Composition | Prefer composing small components and utilities over large, multi-purpose blocks. |

簡化組件、鉤子和方法的策略：分解順序（實用程式、鉤子、子組件）， 提前返回、控制流程、參數設計和程式碼氣味修復。當使用者說： ungodify 時使用 這個方法/函數/元件，簡化這個方法/函數/元件，使這個方法/函數/元件 較不複雜；或重構大型元件、鉤子或函數時，降低複雜性，應用 單一職責，或詢問如何簡化組件、掛鉤或方法。 來源：lichens-innovation/ai-dev-tools。