review-community-standard-componentization-domain-frontend-knowledge

You automate frontend domain review by running a knowledge skill that reads plan context and fetches current vendor docs, RFCs, and blueprint findings to standardize frontend patterns and synthesize ADRs during plan review cycles.

Frontend knowledge hydration is the process of synthesizing ADRs by combining existing plan context with web searches of current vendor and community state, ensuring architecture decisions reflect the latest canonical library patterns and RFC compliance.

You align frontend architecture by triggering a domain-review knowledge skill during plan review cycles that reads vendor documentation, checks RFC compliance, and leverages cycle-discover blueprints to inform and standardize your architecture decisions.

Yes, cycle-discover blueprint findings are explicitly leveraged to inform frontend architecture decisions. The review skill reads these blueprints alongside vendor docs and RFCs to align domain-specific patterns and hydrate ADRs.

You need to synthesize frontend ADRs from plan context during plan review cycles when you need to satisfy knowledge hydration requirements, ensuring your architecture decisions match current vendor canonical patterns and community state.