Amazon Q DeveloperJavaScriptGeneral AI
Generic Frontend UI Rules for Amazon Q Developer
Generic Frontend UI Rules adapted for Amazon Q Developer. High-signal generic engineering guidance for real projects.
rules file
# Generic Frontend UI Rules for Amazon Q Developer ## UX fundamentals - Prioritize clarity over visual novelty. - Every state has explicit UI: loading, empty, error, success. - Accessibility is default: keyboard support, contrast, ARIA labels where needed. ## Components - Reusable primitives first, page composition second. - Keep presentation and data-fetching concerns separated. - Avoid prop drilling beyond 2 levels—use context/store intentionally. ## Reliability - Defensive rendering for null/undefined API data. - Optimistic UI only where rollback is clearly handled.
How to use with Amazon Q Developer
#frontend#ui#accessibility#amazon-q#generic-rules#javascript#ai-coding-rules
Related Rules
Alpine.js Performance Rules for Aider
AiderJavaScript
SEO-ready Aider rules for Alpine.js performance with copy-paste instructions, testing guardrails, and production-safe patterns.
Performance
aider · javascriptCopy Ready
Alpine.js Performance Rules for Claude Code
Claude CodeJavaScript
SEO-ready Claude Code rules for Alpine.js performance with copy-paste instructions, testing guardrails, and production-safe patterns.
Performance
claude-code · javascriptCopy Ready
Alpine.js Performance Rules for Cline
ClineJavaScript
SEO-ready Cline rules for Alpine.js performance with copy-paste instructions, testing guardrails, and production-safe patterns.
Performance
cline · javascriptCopy Ready
Alpine.js Performance Rules for Continue
ContinueJavaScript
SEO-ready Continue rules for Alpine.js performance with copy-paste instructions, testing guardrails, and production-safe patterns.
Performance
continue · javascriptCopy Ready