frontend-ui-engineering
Skill0 starsChanged 2 months agoMITView on GitHub
Build or modify production user interfaces when the task requires responsive layout, accessible interaction, component state, forms, loading and error states, or integration with an existing frontend stack. Use for implementation work after the repository stack and visual direction are known.
67 other projects use a version of this.
Adopted by
Most recently taken up by
- ishandutta2007/Awesome-Agent-Skillstheir own version, first seen Nov 8, 2026
- TheAstroByte/astrobyte-agent-skillstheir own version, first seen Nov 8, 2026
- MMACABRE/SKILLStheir own version, first seen Nov 8, 2026
- sagarithm/sagarithm-kittheir own version, first seen Nov 8, 2026
- Rvey/agent-engineering-kittheir own version, first seen Nov 2, 2026
- steven123397/nexuskit-skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use observability-and-instrumentation, constraint-driven-development and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
HK-hubSkillobservability-and-instrumentation
Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.
Also in 30 projects that use this
MrCipherSmithSkillconstraint-driven-development
Use when a project needs a persistent, measurable quality bar — starting a project without documented standards, 'set up constraints', or when coverage/perf/a11y thresholds get re-debated per-PR. Produces CONSTRAINTS.md with enforceable numbers, ratchets, and a guard against silent weakening. NOT for throwaway prototypes or a one-off CI setup.
Also in 13 projects that use this
- HK-hubSkill
deprecation-and-migration
Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when deciding whether to maintain or sunset existing code.
Also in 33 projects that use this
seikaikyoSkilldoubt-driven-development
對非平凡決策啟動新鮮 context 對抗審查（找碴不背書），在修正還便宜的時候抓出錯誤方向。適用：高風險改動（production、資安敏感邏輯、不可逆操作）、不熟的程式碼、要宣稱「這樣是安全的 / 可行的」之前。機械性操作與一行修改不適用。
Also in 29 projects that use this
- seikaikyoSkill
interview-me
需求不明時的意圖萃取訪談：一次一題、每題附上自己的猜測、聽出「真正想要 vs 覺得應該要」，直到能預測使用者反應（約 95% 信心）才動工。適用：需求缺少對象 / 動機 / 成功標準 / 約束，或使用者點名「訪談我」「先確認一下」「我們確定嗎」。明確自足的指示、純資訊查詢、機械性操作不適用。
Also in 31 projects that use this
AnasX7Skillredesign-existing-projects
Upgrades existing websites and apps to premium quality. Audits current design, identifies generic AI patterns, and applies high-end design standards without breaking functionality. Works with any CSS framework or vanilla CSS.
Also in 3 projects that use this
- +2 more from HK-hub
Other versions67 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 67
- addyosmani/agent-skills★ 114ksame name
- ollaya-dev/ollaya★ 1.4ksame name
- shashankswe2020-ux/whoop-mcp★ 174same name
- vinvcn/addyosmani-agent-skills-zh★ 46same name
- jmxt3/gitscape.ai★ 33same name
- sampleXbro/agentsmesh★ 27same name
- jaskirat1616/grok-skills★ 22same name
- ishandutta2007/Awesome-Agent-Skills★ 21same name
- helderberto/agent-skills★ 19same name
- sagarithm/sagarithm-kit★ 17same name
57 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository21 other files it gives its agents.
- global/AGENTS.mdAGENTS.md
- api-designSkill
- backend-patternsSkill
- brandSkill
- contract-firstSkill
- database-migrationsSkill
- engineering-task-workflowSkill
- error-handlingSkill
- fixing-accessibilitySkill
- frontend-designSkill
- intent-driven-developmentSkill
- react-native-patternsSkill
- react-patternsSkill
- react-testingSkill
- security-best-practicesSkill
- shadcnSkill
- supabase-postgres-best-practicesSkill
- systematic-debuggingSkill
- tdd-workflowSkill
- ui-ux-pro-maxSkill
- verification-before-completionSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 60 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Keep data access, business rules, and presentation boundaries consistent with the codebase.
- Distinctive: line 21
Test observable behavior at the lowest reliable level, then run relevant typecheck, lint, build, and browser checks.
- Very specific: line 25
Use frontend-design for a new or materially changed visual direction.
- Very specific: line 26
Use fixing-accessibility for a focused web accessibility audit or repair.
- Very specific: line 27
Use react-patterns only when the repository is React web.
- Distinctive: line 28
Do not add a UI library, state manager, animation package, or icon set unless the task requires it and the repository does not already …
- Distinctive: line 29
Do not present placeholder controls or mock data as working functionality.
“Common” is measured: kept by at least 6 in 10 of the 60 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Frontend UI Engineering
Implement complete user-facing behavior inside the repository's existing framework and design system.
Workflow
- Discover the actual framework, component library, styling system, browser targets, and repository commands.
- Translate the request into visible states: default, loading, empty, error, disabled, success, and responsive variants that apply.
- Reuse established components and tokens before creating new ones.
- Keep data access, business rules, and presentation boundaries consistent with the codebase.
- Implement semantic structure, keyboard behavior, focus handling, labels, and useful status feedback.
- Preserve existing behavior outside the requested flow.
- Test observable behavior at the lowest reliable level, then run relevant typecheck, lint, build, and browser checks.
Boundaries
- Use
frontend-designfor a new or materially changed visual direction. - Use
fixing-accessibilityfor a focused web accessibility audit or repair. - Use
react-patternsonly when the repository is React web. - Do not add a UI library, state manager, animation package, or icon set unless the task requires it and the repository does not already provide a suitable option.
- Do not present placeholder controls or mock data as working functionality.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.