Refactoring Move Features

--- name: fec-refactoring-move-features description: Use when behavior-preserving frontend refactoring focuses on behavior/data ownership, statement placement, loops, or dead-code knowledge, and the selected technique needs family-specific mechanics, risks, and JavaScript/TypeScript/React/Vue adaptation. --- # Moving Feature Refactorings ## Overview Use this family after evidence identifies a fitting structural transformation. Apply one primary technique at a time and verify immediately. ## Procedure 1. Confirm the selected technique and its preconditions in [Moving Feature Refactorings](references/moving-refactorings.md). 2. Record affected behavior and a diff budget. 3. Apply only the selected technique's smallest viable step. 4. Verify the step before composing another transformation. 5. Stop and reassess when public contracts, lifecycle, state identity, or actual scope exceed expectations. ## Quick Reference The family reference contains 9 canonical techniques with intent, signals, avoid conditions, mechanics, preservation checkpoints, smell links, composition hints, JavaScript/TypeScript notes, React/Vue notes, adaptation guidance, and original frontend examples. ## Common Mistakes - Choosing a technique by name without checking its preconditions. - Combining several structural intentions in one diff. - Assuming a classical class-based form is mandatory in modern frontend code. - Treating passing tests as proof when the relevant behavior is not covered.

存档时间线

版本索引永久保留；内容副本只保留最近 2 版，更早版本仅留索引与哈希（存档时间线的证据链不会因此断裂）。

下载存档内容副本