bklog-hooks

To standardize UI hooks naming conventions, centralize available hooks under a dedicated directory like src/hooks/ using conventional names such as use-xxx.ts. This establishes a single source of truth for hook scope and maintenance boundaries.

A hooks map improves maintainability by documenting reusable UI hooks in a central reference like hooks-reference.md. It provides developers with a quick lookup for hook details, usage constraints, and naming conventions to ensure consistency across teams.

To assess the cross-cutting impact of changing a shared hook, apply ChangeImpact rules to identify wide-scale effects. Consulting a central hooks map helps developers understand maintenance boundaries and minimize unintended side effects across the codebase.

Developing a new hook requires placing the file in src/hooks/ with a conventional name like use-xxx.ts. You must include a YAML frontmatter containing name and description, and you can optionally add resources, scripts, references, or assets directories.

You need to consult a hooks reference document when adding a new hook or modifying existing shared utilities like useStore or useRouter. It ensures proper placement, validates naming conventions, and helps evaluate minimal cross-cutting impact before implementation.