hook

Scaffold reusable React hooks under lib/hooks/<name>.ts with explicit TypeScript types and named exports. This enforces consistent conventions, standardizes client-side logic, and improves maintainability across varied project contexts.

Follow conventions by including 'use client', frontmatter name and description, explicit types for options and returns, and named exports. Files must be located under lib/hooks/<name>.ts and named with the use prefix.

Scaffold a new React hook file by asking Claude to generate use<YourName> in lib/hooks. The generated file automatically includes 'use client', explicit types, and named exports to support scalable patterns for state, effects, and external library integration.

No, this React hook scaffolding approach does not work for server components. It enforces 'use client' for client-side React apps, targeting reusable hooks for state, effects, and external library integration.

Custom React hooks need 'use client' and explicit types to follow Darkroom standards, ensuring the hooks are properly scoped for client-side execution and typed for scalable integration. This standardizes logic and improves maintainability.