frontend-engineering

Name: frontend-engineering
Author: DevelopersGlobal

64stars10forks

How to install frontend-engineering?

developersglobal/ai-agent-skills/frontend-engineering

$npx -y skills add DevelopersGlobal/ai-agent-skills --skill frontend-engineering

Installs into the current project.

Summary

Accessible, performant, responsive UI patterns. Component design, state management discipline, and Core Web Vitals compliance.

Files · 1

View on GitHub

SKILL.md

1	## Overview
2
3	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.
4
5	## When to Use
6
7	- Building any user-facing UI component
8	- Reviewing frontend PRs
9	- Before any UI ships to production
10
11	## Process
12
13	### Step 1: Accessibility First
14
15	1. Every interactive element has a visible focus state.
16	2. All images have meaningful alt text (or `alt=""` for decorative).
17	3. Color contrast ratio ≥ 4.5:1 for normal text.
18	4. All functionality operable by keyboard alone.
19	5. Use semantic HTML: `<button>` not `<div onclick>`, `<nav>` not `<div class="nav">`.
20
21	Verify: Run axe DevTools or Lighthouse accessibility audit. Score ≥ 90.
22
23	### Step 2: Performance (Core Web Vitals)
24
25	6. LCP (Largest Contentful Paint) < 2.5s: Optimize images, preload critical resources.
26	7. FID/INP < 100ms: Avoid long tasks on the main thread.
27	8. CLS (Cumulative Layout Shift) < 0.1: Reserve space for dynamic content.
28	9. Lazy load below-the-fold images and non-critical JS.
29	10. Bundle size: measure before and after. No unneeded dependencies.
30
31	Verify: Lighthouse performance score ≥ 80. CWV within targets.
32
33	### Step 3: Responsive Design
34
35	11. Test at 320px, 768px, 1024px, 1440px viewports.
36	12. No horizontal scrolling at any standard viewport.
37	13. Touch targets ≥ 44px × 44px.
38
39	### Step 4: State Management Discipline
40
41	14. Server state vs. client state are separate concerns — don't mix.
42	15. No prop drilling more than 2 levels — use context or state management.
43	16. Loading, error, and empty states handled for every async operation.
44
45	Verify: Loading, error, and empty states all visible in Storybook/dev environment.
46
47	## Common Rationalizations (and Rebuttals)
48
49	\| Excuse \| Rebuttal \|
50	\|--------\|----------\|
51	\| "Accessibility is for edge cases" \| 1 in 4 adults has a disability. It's not an edge case. \|
52	\| "We'll optimize performance later" \| Users leave after 3 seconds. "Later" is too late. \|
53
54	## Verification
55
56	- [ ] Accessibility audit score ≥ 90
57	- [ ] Core Web Vitals within targets
58	- [ ] Responsive at 320px/768px/1024px/1440px
59	- [ ] Loading, error, empty states handled
60	- [ ] All interactive elements keyboard-operable
61
62	## References
63
64	- [references/accessibility-checklist.md](../../references/accessibility-checklist.md)
65	- [performance-optimization skill](../performance-optimization/SKILL.md)

People who liked this also viewed

6 picks

Type

web-design-guidelinesReview 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".SkillsJul 2026483k29k
lark-slides飞书幻灯片：创建和编辑幻灯片。创建演示文稿、读取幻灯片内容、管理幻灯片页面（创建、删除、读取、局部替换）。当用户需要创建或编辑幻灯片、读取或修改单个页面时使用。当用户给出 doubao.com 的 /slides/ URL/token 时，也应直接使用本 skill，不要因为域名不是飞书而回退到 WebFetch；路由依据是 URL 路径模式和 token，而不是域名。不负责：云文档内容编辑（走 SkillsJul 2026332k16k
design-taste-frontendTaste-Skill - gives your AI good taste. stops the AI from generating boring, generic slop SkillsJul 2026280k66k
ui-ux-pro-maxUI/UX design intelligence for web and mobile. Searchable local database with 84 styles, 192 color palettes, 74 font pairings, 192 product types, 98 UX guidelines, 104 icon entries, 16 GSAP motion presSkillsJul 2026280k109k
caveman-helpQuick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".SkillsJul 2026249k92k
codebase-designShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-nSkillsJul 2026225k182k

frontend-engineering

64stars10forks

View on GitHub

How to install frontend-engineering?

developersglobal/ai-agent-skills/frontend-engineering

$npx -y skills add DevelopersGlobal/ai-agent-skills --skill frontend-engineering

Installs into the current project.

Summary

Accessible, performant, responsive UI patterns. Component design, state management discipline, and Core Web Vitals compliance.

Files · 1

View on GitHub

SKILL.md

1	## Overview
2
3	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.
4
5	## When to Use
6
7	- Building any user-facing UI component
8	- Reviewing frontend PRs
9	- Before any UI ships to production
10
11	## Process
12
13	### Step 1: Accessibility First
14
15	1. Every interactive element has a visible focus state.
16	2. All images have meaningful alt text (or `alt=""` for decorative).
17	3. Color contrast ratio ≥ 4.5:1 for normal text.
18	4. All functionality operable by keyboard alone.
19	5. Use semantic HTML: `<button>` not `<div onclick>`, `<nav>` not `<div class="nav">`.
20
21	Verify: Run axe DevTools or Lighthouse accessibility audit. Score ≥ 90.
22
23	### Step 2: Performance (Core Web Vitals)
24
25	6. LCP (Largest Contentful Paint) < 2.5s: Optimize images, preload critical resources.
26	7. FID/INP < 100ms: Avoid long tasks on the main thread.
27	8. CLS (Cumulative Layout Shift) < 0.1: Reserve space for dynamic content.
28	9. Lazy load below-the-fold images and non-critical JS.
29	10. Bundle size: measure before and after. No unneeded dependencies.
30
31	Verify: Lighthouse performance score ≥ 80. CWV within targets.
32
33	### Step 3: Responsive Design
34
35	11. Test at 320px, 768px, 1024px, 1440px viewports.
36	12. No horizontal scrolling at any standard viewport.
37	13. Touch targets ≥ 44px × 44px.
38
39	### Step 4: State Management Discipline
40
41	14. Server state vs. client state are separate concerns — don't mix.
42	15. No prop drilling more than 2 levels — use context or state management.
43	16. Loading, error, and empty states handled for every async operation.
44
45	Verify: Loading, error, and empty states all visible in Storybook/dev environment.
46
47	## Common Rationalizations (and Rebuttals)
48
49	\| Excuse \| Rebuttal \|
50	\|--------\|----------\|
51	\| "Accessibility is for edge cases" \| 1 in 4 adults has a disability. It's not an edge case. \|
52	\| "We'll optimize performance later" \| Users leave after 3 seconds. "Later" is too late. \|
53
54	## Verification
55
56	- [ ] Accessibility audit score ≥ 90
57	- [ ] Core Web Vitals within targets
58	- [ ] Responsive at 320px/768px/1024px/1440px
59	- [ ] Loading, error, empty states handled
60	- [ ] All interactive elements keyboard-operable
61
62	## References
63
64	- [references/accessibility-checklist.md](../../references/accessibility-checklist.md)
65	- [performance-optimization skill](../performance-optimization/SKILL.md)

People who liked this also viewed

6 picks

Type