ant-to-shadcn-migration
Migrate Ant Design UIs to shadcn/ui + Tailwind (React/CRA/Vite → Next.js App Router). Use for: component replacement (no wrappers), Tailwind-first styling, canonical component consolidation, global CSS cleanup, route/layout scaffolding, and migration gotchas.
Install with Tessl CLI
npx tessl i github:uzhussain/ant-to-shadcn --skill ant-to-shadcn-migration87
Quality
81%
Does it follow best practices?
Impact
96%
1.05xAverage score across 3 eval scenarios
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly defines a specific migration path between two UI frameworks with comprehensive trigger terms. It uses third person voice appropriately, lists concrete actions, and provides explicit 'Use for:' guidance that makes skill selection unambiguous. The technical specificity ensures it won't conflict with general React or styling skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'component replacement (no wrappers)', 'Tailwind-first styling', 'canonical component consolidation', 'global CSS cleanup', 'route/layout scaffolding', and 'migration gotchas'. These are detailed, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (migrate Ant Design to shadcn/ui + Tailwind) and when ('Use for:' followed by explicit trigger scenarios). The 'Use for:' clause serves as explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Ant Design', 'shadcn/ui', 'Tailwind', 'React', 'CRA', 'Vite', 'Next.js', 'App Router'. These are the exact technology names developers would mention when needing this migration. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a very specific niche: Ant Design → shadcn/ui migration with Next.js App Router. The combination of source framework, target framework, and specific tech stack makes conflicts with other skills extremely unlikely. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a comprehensive migration framework with excellent workflow structure and clear sequencing. However, it lacks concrete executable code examples showing actual component transformations, relying instead on descriptive guidance. The component matrix is valuable but verbose, and the skill would benefit from splitting reference material into separate files.
Suggestions
Add concrete before/after code examples showing actual Ant Design to shadcn/ui component migrations (e.g., Form.Item → shadcn Form with RHF)
Move the component equivalence matrix and rule index to separate reference files (e.g., COMPONENTS.md, RULES.md) and link to them
Replace descriptive guidance like 'Convert Form.Item patterns to shadcn + react-hook-form' with executable code snippets showing the transformation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some verbose sections like the lengthy component equivalence matrix and repeated scan commands that could be condensed. The 'When to Apply' section restates information already in the description. | 2 / 3 |
Actionability | Provides useful component mappings and scan commands, but lacks executable migration code examples. The guidance is mostly descriptive ('rebuild layouts', 'convert Form.Item patterns') rather than showing concrete before/after code transformations. | 2 / 3 |
Workflow Clarity | Clear numbered migration order (0-13) with logical sequencing from setup through verification. Post-migration verification checklist provides explicit validation checkpoints for each category. | 3 / 3 |
Progressive Disclosure | References external rules files (e.g., 'see rules/') but these are mentioned without clear file paths. The component matrix and rule index are inline when they could be separate reference files. Structure is reasonable but could better leverage external files. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.