Install
$ agentstack add skill-developersglobal-ai-agent-skills-frontend-engineering ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
Overview
Frontend code touches every user. Poor UI engineering causes accessibility barriers, performance degradation, and broken experiences on non-standard devices. This skill enforces the discipline of building UI that works for everyone.
When to Use
- Building any user-facing UI component
- Reviewing frontend PRs
- Before any UI ships to production
Process
Step 1: Accessibility First
- Every interactive element has a visible focus state.
- All images have meaningful alt text (or
alt=""for decorative). - Color contrast ratio ≥ 4.5:1 for normal text.
- All functionality operable by keyboard alone.
- Use semantic HTML: `
not,not`.
Verify: Run axe DevTools or Lighthouse accessibility audit. Score ≥ 90.
Step 2: Performance (Core Web Vitals)
- LCP (Largest Contentful Paint) < 2.5s: Optimize images, preload critical resources.
- FID/INP < 100ms: Avoid long tasks on the main thread.
- CLS (Cumulative Layout Shift) < 0.1: Reserve space for dynamic content.
- Lazy load below-the-fold images and non-critical JS.
- Bundle size: measure before and after. No unneeded dependencies.
Verify: Lighthouse performance score ≥ 80. CWV within targets.
Step 3: Responsive Design
- Test at 320px, 768px, 1024px, 1440px viewports.
- No horizontal scrolling at any standard viewport.
- Touch targets ≥ 44px × 44px.
Step 4: State Management Discipline
- Server state vs. client state are separate concerns — don't mix.
- No prop drilling more than 2 levels — use context or state management.
- Loading, error, and empty states handled for every async operation.
Verify: Loading, error, and empty states all visible in Storybook/dev environment.
Common Rationalizations (and Rebuttals)
| Excuse | Rebuttal | |--------|----------| | "Accessibility is for edge cases" | 1 in 4 adults has a disability. It's not an edge case. | | "We'll optimize performance later" | Users leave after 3 seconds. "Later" is too late. |
Verification
- [ ] Accessibility audit score ≥ 90
- [ ] Core Web Vitals within targets
- [ ] Responsive at 320px/768px/1024px/1440px
- [ ] Loading, error, empty states handled
- [ ] All interactive elements keyboard-operable
References
- [references/accessibility-checklist.md](../../references/accessibility-checklist.md)
- [performance-optimization skill](../performance-optimization/SKILL.md)
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: DevelopersGlobal
- Source: DevelopersGlobal/ai-agent-skills
- License: MIT
- Homepage: https://developersglobal.github.io/ai-agent-skills/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.