- Home
- Skills
- Frontend & Web Apps
- Interface Craft Router
Works with the AI Agents you already use
Interface Craft Router
Eight-tier UI routing that puts accessibility and stable rendering before style, turning rough requests into consistent, implementable design decisions.
Free
Interface Craft Router
Example session with this skill installed
We're building Ledger, a fintech SaaS checkout flow in Next.js with Tailwind. The design feels off — colors look flat, the mobile layout jumps when payment options load, and our accessibility review flagged low-contrast gray text and icon-only buttons with no labels. Can you review the checkout page, fix the contrast and focus issues, pick a visual direction that reads as trustworthy and calm for finance users, and make sure every interactive element has proper loading, error, and disabled states? Give me a prioritized fix list with concrete code suggestions for the worst offenders.
- Read your context and instructions
- Compiled the interface craft router
Summary
Audited the Ledger checkout flow against the eight-tier interface hierarchy. Two accessibility blockers and one layout-stability risk fixed; visual direction locked to a quiet fintech dialect (deep slate + one trust-blue accent).
| Metric | Before | After |
|---|---|---|
| Contrast failures (muted gray body text) | 4 | 0 |
| Icon-only buttons without accessible names | 3 | 0 |
| Touch targets under 44x44 CSS px | 6 | 0 |
| CLS when payment options load | 0.21 | 0.02 (space reserved with skeletons) |
| Delete-confirm dialog focus trap | Missing | Implemented |
Validation errors now sit next to the affected field, submission is disabled during pending payment, and step transitions animate only transform/opacity with a reduced-motion fallback.
Next steps
- Apply the full state matrix (default/hover/focus/active/disabled/loading/empty/error) to the order-summary card
- Add a table fallback for the order-total breakdown so values stay checkable
- Persist this brief to design/pages/checkout.md so later pages inherit the same dialect
Connects securely to your tools. The creator never sees your data.
About this skill
The problem
Interfaces often break under real-world conditions, failing accessibility standards or jumping during layout shifts. Developers struggle to balance aesthetic trends with stable, performant code that actually works for the end user.
What it does
- Evaluates UI requests against an eight-tier priority system, putting accessibility and stability before visual style.
- Generates semantic, accessible code for web and mobile surfaces including React, Next.js, SwiftUI, and Tailwind CSS.
- Ensures interactive elements handle all states including hover, focus, loading, error, and empty data.
- Architects responsive layouts that survive variable viewports without unintended horizontal scrolling or layout shifts.
- Applies specific visual dialects for healthcare, finance, commerce, and dev tools to match industry expectations.
Frameworks & tools
React, Next.js, Vue, Svelte, SwiftUI, Flutter, Jetpack Compose, Tailwind CSS, and shadcn/ui.
Why this beats prompting it yourself
Generic prompts often produce "happy path" code that ignores focus states, touch targets, and ARIA labels. This skill enforces a strict pre-delivery audit and routing logic that guarantees production-ready UI components by default.
Use cases
- Building accessible SaaS dashboards with complex data visualization and filtering.
- Creating resilient commerce checkout flows that handle async states and errors.
- Refactoring legacy UI components to meet modern WCAG contrast and focus standards.
- Designing internal admin panels optimized for high-density data and keyboard navigation.
Known limitations
Requires explicit runtime definitions for specific component library integrations. Does not generate custom icon assets or brand logos from scratch.
The optional facet-search script may not be bundled in every install, in which case the skill falls back to its self-contained guidance. Runtime adapters stay high-level, so niche or in-house component libraries need manual judgment.
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
This skill has been used 5 times.
Trust & safety
Security scan
Security scan passed 1 month ago
- Free with an Agensi account
Permissions
File Scopes
Reads project markup and style files to review UI and optionally persists design briefs under design/; an optional local Python lookup script uses the shell, with no network access required.