interface-design
Interface Design
Design Principles
1. Clarity
Make the interface obvious. Users shouldn't have to guess.
2. Consistency
Same actions, same results. Maintain patterns throughout.
3. Feedback
Respond to every action. Show progress, confirm success, explain errors.
4. Efficiency
Minimize steps. Optimize common workflows.
5. Forgiveness
Allow undo. Confirm destructive actions. Recover gracefully.
UI Patterns
Navigation
- Top Nav: Primary navigation, global actions
- Side Nav: Section navigation, hierarchical content
- Breadcrumbs: Show location in hierarchy
- Tabs: Switch between related views
Forms
- Label above input
- Clear validation messages
- Inline validation where helpful
- Logical field grouping
- Clear call-to-action
Feedback
- Loading states
- Success confirmations
- Error messages
- Empty states
- Progress indicators
Actions
- Primary action prominent
- Secondary actions subtle
- Destructive actions require confirmation
- Disabled states clear
Layout Principles
Visual Hierarchy
- Size indicates importance
- Color draws attention
- Spacing groups elements
- Alignment creates order
Grid System
.container {
display: grid;
grid-template-columns: repeat(12, 1fr);
gap: 1rem;
}
Responsive Design
- Mobile-first approach
- Breakpoints: 640px, 768px, 1024px, 1280px
- Fluid typography
- Flexible images
Design Specification
When handing off to development:
- Color values (hex/RGB)
- Typography (font, size, weight, line-height)
- Spacing (margins, padding)
- Component states (default, hover, active, disabled)
- Responsive behavior
- Animations/transitions
More from nguyenhuuca/assessment
compliance
Ensure regulatory compliance. Use when implementing GDPR, HIPAA, PCI-DSS, or SOC2 requirements. Covers compliance frameworks and controls.
17requirements-analysis
Analyze and refine product requirements. Use when clarifying scope, identifying gaps, or validating requirements. Covers requirement types and analysis techniques.
16security-review
Conduct security code reviews. Use when reviewing code for vulnerabilities, assessing security posture, or auditing applications. Covers security review checklist.
13identity-access
Implement identity and access management. Use when designing authentication, authorization, or user management. Covers OAuth2, OIDC, and RBAC.
12execution-roadmaps
Create execution roadmaps for projects. Use when planning multi-phase projects or feature rollouts. Covers phased delivery and milestone planning.
12cloud-native-patterns
Apply cloud-native architecture patterns. Use when designing for scalability, resilience, or cloud deployment. Covers microservices, containers, and distributed systems.
12