enosta-frontend-os

Provides verification gates, feedback reception patterns, and review request workflows. Activates during code review, PR preparation, task completion verification, and before claiming implementation is done. Use when receiving code review feedback (especially if unclear or technically questionable), when completing tasks or major features requiring review before proceeding, or before making any completion/success claims. Covers three practices - receiving feedback with technical rigor over performative agreement, requesting reviews via code-reviewer subagent, and verification gates requiring evidence before any status claims. Essential for subagent-driven development, pull requests, and preventing false completion claims.

Enforces component responsibility limits, ownership decisions, and composition patterns when creating, editing, or refactoring React components, TSX/JSX files, or component folders. Activates on component design, splitting, architecture decisions, module organization, and any work involving component structure. Use when creating new components, refactoring growing components, deciding where components live, choosing between props and composition, splitting responsibilities, handling permissions or feature flags in components, sharing UI across features, or organizing modules. Triggers on questions like "how do I design this component", "should I use props or composition", "my component is getting too big", "where does this component belong", "how do I share this between modules". When in doubt about a frontend architecture question, use this skill.

Guides test writing for components, hooks, API integrations, and E2E flows. Activates when creating or editing test files, spec files, or when implementing features that need test coverage. Use when writing unit tests, integration tests, E2E tests, deciding what to test, choosing testing strategies, identifying edge cases, setting up mocks, or evaluating test quality. Triggers on questions like "how do I test this", "what tests do I need", "how do I mock this API", "what edge cases am I missing", "should this be a unit or integration test", "how do I write E2E tests for this flow".

Guides contributors when editing wiki documentation files. Provides dependency context, related file suggestions, and style enforcement.