| Architecture thinking | Designs maintainable component boundaries and predictable data flow. | Builds tightly coupled UI with unclear state ownership. |
| Performance reasoning | Diagnoses bottlenecks with profiling and targeted optimizations. | Suggests generic optimizations without measurement strategy. |
| Accessibility execution | Applies semantic structure and keyboard/screen-reader considerations. | Treats accessibility as optional polishing after implementation. |
| Delivery communication | Explains tradeoffs clearly between UX quality, scope, and timelines. | Presents implementation details without product impact framing. |