What problem does it solve? Large codebases accumulate god-files, bypassed service layers, and duplicated logic that erode maintainability. This Skill prevents those anti-patterns in the git-manager repo by enforcing documented architecture invariants (R1/R2/R3) whenever you add or edit Tauri commands, React components, hooks, Zustand stores, or API files. ## Core Features & Use Cases - Layering enforcement: Ensures every operation goes through the service/API layer — no direct invoke() or lib/tauri.ts calls from components, hooks, or stores, and thin Tauri commands that delegate to services/. - File-size and complexity discipline: Treats ~300 lines as the signal to split a component, hook, or function into feature-scoped files with their own colocated tests. - Safe retrofit method (R3): Provides a test-mapped, incremental extraction workflow for unwinding existing god-files, including barrel re-exports for multi-domain aggregator splits. - Use Case: Before adding a new #[tauri::command] or editing a 400-line React component, activate this Skill to check the layering rules and decide whether to extract logic into a hook or service first. ## Quick Start Ask the assistant to review your planned changes to a Tauri command or React component against the repo's architecture rules before writing the code.
