Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add boparaiamrit/skills-by-amrit --skill ui-ux-redesigngit clone --depth 1 https://github.com/boparaiamrit/skills-by-amritWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/boparaiamrit/skills-by-amrit/ui-ux-redesign)<a href="https://agentmods.dev/skills/boparaiamrit/skills-by-amrit/ui-ux-redesign"><img src="https://agentmods.dev/badge/skills/boparaiamrit/skills-by-amrit/ui-ux-redesign/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/boparaiamrit/skills-by-amrit/ui-ux-redesign"><img src="https://agentmods.dev/badge/skills/boparaiamrit/skills-by-amrit/ui-ux-redesign.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00074 | $0.05330 |
| Opus 5 | $0.00037 | $0.02665 |
| Sonnet 5 | $0.00015 | $0.01066 |
| Haiku 4.5 | $0.00007 | $0.00533 |
Grade A, and why
ui-ux-redesign scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 480 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI/UX Redesign
Overview
Redesign is not about making things prettier — it's about making things coherent. A disjointed UI is a symptom of incremental feature additions without design governance. This skill forces a full-stack visual audit: understand what data the backend provides, inventory every frontend component, expose every inconsistency, and produce an actionable redesign plan that creates visual and behavioral uniformity.
Core principle: Beautiful design is uniform design. Every pixel should feel like it belongs to the same system.
The Iron Law
NO REDESIGN WITHOUT A FULL INVENTORY. NO SUGGESTION WITHOUT EVIDENCE. NO VISUAL CHANGE WITHOUT UNDERSTANDING THE DATA BEHIND IT.
When to Use
- The UI feels inconsistent, disjointed, or "not right"
- After multiple feature additions without design review
- Before a major version release or public launch
- When users complain about usability (but functionality works)
- When onboarding to a product and the frontend needs modernization
- When switching design direction (dark mode, rebrand, redesign)
- After merging contributions from multiple developers/AI sessions
- When a client or stakeholder says "make it look professional"
When NOT to Use
- Greenfield projects (there's nothing to redesign — use
brainstorming→writing-plans) - Pure backend/API projects with no frontend
- Single component fixes (use
code-revieworfrontend-audit) - Performance-only issues (use
performance-audit) - Accessibility-only issues (use
accessibility-audit) - When the problem is functionality, not presentation (debug first)
Anti-Shortcut Rules
YOU CANNOT:
- Suggest redesign without first inventorying EVERY existing component — you don't know what exists
- Suggest new components without checking if a similar one already exists — avoid duplication
- Recommend colors without documenting the EXISTING color palette first — understand before changing
- Recommend spacing changes without mapping the EXISTING spacing scale — measure before prescribing
- Say "modernize the UI" without defining exactly WHAT modern means for THIS product — vague is useless
- Skip the backend API audit — the frontend displays data: understand what data exists
- Suggest layout changes without understanding responsive behavior at ALL breakpoints
- Recommend a design system without checking if one partially exists
- Say "use Tailwind/Material/whatever" without analyzing what's ALREADY in use
- Propose animations without understanding current render performance
- Skip user flow analysis — UX redesign without user flows is decoration, not design
- Suggest removing features for aesthetic purposes — functionality is non-negotiable
- Claim "this looks better" without explaining WHY from a design principle perspective
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 480 lines · 74 tokens per session scan A 40ab2962a243
ui-ux-redesign is a skill published in the GitHub repository boparaiamrit/skills-by-amrit (5 stars, last pushed 6mo ago), licensed MIT. It adds 74 tokens to every session and 5,330 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ultragoal with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-ui-dark-ts
Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.
reveal-hover-effect
Build cursor-following spotlight reveals that expose a second aligned image through a soft radial mask. Use for hover-to-color, before-and-after, x-ray, material, texture, product-detail, and illustrated hero effects where a desaturated or embossed base image should remain visible while another treatment follows an…
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.