- Home
- Skills
- Frontend & Web Apps
- frontend design transformation architect master
More screenshots
Works with the AI Agents you already use
frontend design transformation architect master
Evidence-based frontend redesign system that transforms UI screenshots and code into accessible, developer-ready specs.
Free
frontend design transformation architect master
Example session with this skill installed
Redesign this SaaS pricing table. I need a SYSTEMIZE and ACCESSIBILITY mode audit. The current version is a single-column list with low contrast. Tech stack is Tailwind and React.
- Read your context and instructions
- Compiled the frontend design transformation
I have analyzed the pricing table evidence. The redesign focuses on horizontal scannability, clear visual hierarchy for the "Pro" tier, and WCAG 2.1 AA contrast compliance using your Tailwind stack.
Pricing Table Transformation
| Element | OBSERVED (Before) | RECOMMENDATION (After) | Rationale |
|---|---|---|---|
| Layout | Vertical list, single column | 3-column grid (Desktop) | Improved plan comparison |
| Hierarchy | All tiers equal weight | Scaled "Pro" card with shadow | Drives attention to primary CTA |
| Typography | 14px centered gray text | 16px sans-serif, high contrast | Improved legibility/accessibility |
| Action | Small "Buy" link | Full-width primary button | Better touch targets (44px+) |
Visual Design System (Tailwind)
{
"colors": {
"surface": "bg-slate-50",
"border": "border-slate-200",
"primary": "bg-blue-600",
"text-main": "text-slate-900",
"text-muted": "text-slate-600"
},
"spacing": {
"card-padding": "p-8",
"gap": "gap-6"
},
"typography": {
"price": "text-4xl font-bold tracking-tight",
"label": "text-sm font-semibold uppercase"
}
}
Accessibility Specification
- Contrast: Ensured all text-to-background ratios exceed 4.5:1.
- Semantics: Use
<ul>for feature lists; ensure price is wrapped in a clear heading level. - Focus States: Applied
focus-visible:ring-2 ring-blue-500to all CTA buttons. - Screen Readers: Added
aria-current="true"recommendation for the selected plan.
Next steps
- Review the proposed Tailwind token mapping for brand alignment.
- Implement the 3-column responsive grid with a mobile-first stacking rule.
- Run a screen reader test on the component once the React structure is built.
Connects securely to your tools. The creator never sees your data.
About this skill
The problem
Design feedback is often subjective, vague, or detached from technical reality. Translating a messy UI screenshot or a legacy codebase into a systematic, accessible, and implementation-ready redesign is a manual process prone to "hand-wavy" suggestions that break during development.
What it does
- Performs visual audits of screenshots and URLs using an evidence-based labeling system to separate facts from inferences.
- Generates "Before → Transformation → After" redesign blueprints that preserve your original content and legal copy while fixing UX friction.
- Defines semantic design tokens for typography, color architecture, and 8px-grid spacing systems.
- Specifies component behavior across all interaction states including hover, focus-visible, and disabled.
- Produces responsive stacking rules and accessibility checklists for semantic HTML and ARIA compliance.
Frameworks & tools
Works with HTML/CSS, React components, and design systems. Includes specialized scripts for static accessibility audits and DOM structure validation.
Why this beats prompting it yourself
Generic prompts often hallucinate fake business metrics or invent new product features to make a design "look better." This skill enforces strict integrity rules that preserve your verified copy and data, ensuring the redesign is actually buildable and rooted in your specific technical constraints.
Use cases
- Transforming a legacy dashboard into a modern, tokenized design system.
- Performing a technical design audit of a landing page before a high-stakes launch.
- Generating developer handoff specs from a rough UI screenshot or sketch.
- Reviewing a frontend implementation for accessibility gaps and responsive bugs.
Known limitations
Static visual analysis cannot verify actual DOM behavior, screen-reader performance, or production load speeds. Requires manual verification for complete WCAG compliance.
Cannot verify live DOM behavior or screen-reader performance from static images. Automated accessibility checks are structural only and do not replace a full manual WCAG audit.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
1 use
Times used to date
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 2 months ago
- Free with an Agensi account
Permissions
No special permissions declared or detected