ui-modernization
Skill2 starsChanged 5 months agoMITView on GitHub
Plan migration of a legacy UI to a modern React component architecture. Produces a component inventory, a target component tree, and starter React + test stubs. Trigger on: modernize UI, convert to React, UI migration, frontend modernization.
In this repository15 other files it gives its agents.
- change-impact-analysisSkill
- legacy-discoverySkill
- spec-governanceSkill
- task-decompositionSkill
- test-generationSkill
- topology-planningSkill
- jira-ticketSkill
- servicenow-ticketSkill
- speckit-constitutionSkill
- speckit-planSkill
- speckit-specifySkill
- speckit-tasksSkill
- my-skillSkill
- text-statisticsSkill
- xquik-social-dataSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 46
When modernizing a front end.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
ui-modernization
Plan a legacy UI migration to a modern component framework (React by default): component inventory, target tree, and starter stubs.
When to use
When modernizing a front end. Triggers: modernize UI, convert to React, UI migration, frontend modernization.
Inputs
screens(array of strings, required) — legacy screen/page names.framework(string, optional, defaultreact).
Outputs
plan_markdown— inventory, target tree, approach, definition of done.components— derived component names.sample_component— a starter component stub.
How it works
Derives PascalCase component names from screen names, builds a target tree, and emits a strangler migration approach with a per-screen DoD.
User stories
- As a front-end lead, I get a component map and a sample to start porting.
Edge cases
- A single screen passed as a string is accepted.
- Empty screen list → clear error (nothing to plan).
- Messy names with punctuation → sanitised into valid component identifiers.
Files
See DOCS.md. Figma mapping guidance lives in figma/.
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.