When defining the feature set for a project, it is important to make sure all those features fit within architectural and experience standards that are already in place on that project and for the organization as a whole.
This involves reviewing user stories and confirming that the features they outline are consistent with standards established on the project. The focus is to smooth the runway and avoid having to ask questions of standards or integration at the Team level.
For example, if a new story requires a component that has not yet been integrated into the overall project visual style guide, validation should catch that and ensure that the new component is added to the style guide prior to the story being transitioned for work at the Team level. The same concepts apply to new development paradigms as well.