frontend-context

Maintaining frontend consistency across multiple projects requires a single source of truth for architecture standards. This Skill loads conventions from docs/architecture/frontend.md to enforce uniform component structure, state management, styling, API usage, and testing patterns.

Enforcing frontend code review standards is best achieved by loading documented architecture conventions. This Skill references docs/architecture/frontend.md during reviews to verify approved patterns for component structure, state management, styling, and API usage.

Applying frontend architecture standards requires a specific file structure. You must have a reference document located exactly at docs/architecture/frontend.md containing your project's approved guidelines for component structure and testing patterns.

Stopping code drift when implementing new frontend tickets requires referencing centralized architecture standards before writing code. This Skill loads approved state management and styling conventions from docs/architecture/frontend.md to align implementations and reduce rework.

For consistent UI development, document frontend conventions covering component naming, state management, styling, API usage, and testing patterns. This Skill loads these specific standards from your architecture reference document to guide implementations.

You cannot use this Skill for backend code review and standards. It is specifically designed to load and enforce frontend architecture conventions, focusing on component structure, state management, and styling patterns from docs/architecture/frontend.md.