emil-frontend
Skill0 starsChanged 17 days agoMITView on GitHub
Emil 前端设计与动效系列的兼容入口。用户明确沿用 emil-frontend 名称时，将需求交给 ui-design 总入口，再按设计、动效、审查或平台选择专长；一般界面需求使用 ui-design。
In this repository6 other files it gives its agents.
- development-workflowSkill
- document-workflowSkill
- f-d-u-dSkill
- skill-curatorSkill
- ui-designSkill
- writing-workflowSkill
The file
Files
Emil 前端入口兼容转接
本地 UI 系列已统一使用 ui-design 进行任务选择。
读取该入口并按用户原始目标、平台、改动范围和已选技术继续执行；明确点名的专长直接保留。普通 UI 请求不自动启用 Taste、选库或多方案原型等需要显式请求的专长。
如果 ui-design 未安装，明确报告缺少总入口；用户明确点名的现有专长仍可直接读取，不猜测其他机器的绝对路径或自动安装。
此兼容入口只转接一次，ui-design 直接选择实际专长，避免在两个入口之间来回加载。
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.