Loading...
Loading...
Found 7 Skills
When implementing or reviewing web interfaces, refer to this set of practical guidelines from the Traditional Chinese version of raunofreiberg/interfaces' *Web Interface Guidelines* to ensure that details such as interactivity, visuals, and accessibility meet the expectations of a 'good interface'.
Use when designing, reviewing, or implementing web UIs and you need concrete MUST/SHOULD/NEVER rules for accessibility, interaction patterns, forms, layout, animation, performance, content, or visual design decisions.
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
Review UI code against Rauno Freiberg's interface guidelines. Use when checking interactivity, typography, motion, touch, optimizations, accessibility, and design details.
Review UI code for Web Interface Guidelines compliance. Use when asked to review UI, check accessibility, audit design, review UX, or check against best practices.
(NS) Security/compat/a11y hygiene + Vercel Web Interface Guidelines review (headers, CSP, deps, accessibility). Use when hardening security, fixing CSP/CORS/headers, reviewing UI / checking a11y / auditing UX, or applying Web Interface Guidelines — even without saying "best practices"; also at ns-proto-creator close-out. Do NOT use for MR/SOLID review (ns-reviewer), visual redesign (ns-frontend-design), or feature implementation (ns-coder / ns-spec-driven).
Review UI code against Vercel Web Interface Guidelines. Use when asked to review UI, check accessibility, audit design, review UX, or check a site against web interface best practices.