implementation-guardrails

What problem does it solve?

It prevents teams from shipping messy architecture by ensuring implementation work respects ownership boundaries, correct module shapes, and clean layering across UI, hooks, server boundaries, and pure logic.

Core Features & Use Cases

• Boundary and file-placement standards: Guides where domain logic should live (feature-adjacent modules vs generic utils) and how to structure responsibilities across components, hooks, pure modules, actions, services, and routes.
• Orchestration separation: Discourages business workflow orchestration inside UI components and instead pushes coordination into the correct layer (hooks, providers, services/actions, or server boundaries).
• Effect and pass-through avoidance: Reduces common React/Next.js smells by discouraging unnecessary useEffect usage and thin pass-through clutter in server actions and routes.
• Cleanup and naming integrity: Encourages removing dead/duplicated paths, deprecations, and misleading names after architecture changes.

Quick Start

Use this skill when starting a refactor in the repo to quickly align on the correct ownership seam, choose the right module boundary, and confirm placement and orchestration decisions against REFERENCE and CHECKLIST.