web-design-guidelines
Web Design & Interface Guidelines Skill
This skill provides a framework for reviewing and implementing high-quality web interfaces. It focuses on the intersection of aesthetics, usability, and technical performance.
Design Framework
1. Information Hierarchy
- F-Pattern: Align critical information and navigation along the F-shaped scanning pattern.
- Emphasis: Use font weight, scale, and color depth to guide the user's eye to the Primary Action.
- Proximity: Group related elements closely to signal relationship (Law of Proximity).
2. Form Design & Interaction
- Feedback: Provide inline validation as the user types (debounce). Use distinct "Success" and "Error" states.
- Aids: Use appropriate input types (
tel,email,number) and autocomplete attributes to assist the user. - Labels: Always use
<label>tags. Never rely on placeholders alone for accessibility.
3. Interactive Feedback
- Affordance: Buttons must look clickable. Links must be distinguishable from body text.
- Stateful UI: Every interactive element must reflect its current state (Initial, Loading, Success, Error).
More from inselfcontroll/ai-agent-skills
rust_dioxus_framework
Acts as a Rust Dioxus Framework Specialist for building cross-platform UIs. Use when building desktop, web, or mobile apps using the Dioxus framework.
15clerk
Expert for Clerk authentication integration. Use when setting up Clerk in React, implementing Clerk Go middleware for session validation, or managing Clerk user profiles.
2testing_qa
Acts as a Testing and QA Agent. Use when writing unit, integration, or E2E tests, or when auditing code for test coverage.
2code-review
Expert for codebase-wide code reviews. Use when auditing Pull Requests, refactoring complex logic, or enforcing architectural and security standards across the ecosystem.
2principal_architect
Acts as a Principal Software Architect to design blueprints and enforce architectural rules. Use when designing system architecture, defining API contracts, or planning data flows.
2requirements_analyst
Acts as a Requirements Analyst to translate requests into specifications. Use when gathering user requirements, defining user stories, or creating technical specifications.
2