redesign-existing-projects

Audit web and app codebases for UI deficiencies and recommend non-breaking fixes.

1|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/lagarcess/argus --skill redesign-existing-projects-lagarcess
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: redesign-existing-projects
Source: https://github.com/lagarcess/argus/tree/main/.agent/skills/redesign-existing-projects
Command: npx skills add https://github.com/lagarcess/argus --skill redesign-existing-projects-lagarcess

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill upgrades existing websites and applications that suffer from generic, inconsistent, or AI-template design patterns by providing a disciplined audit and targeted visual improvements that do not break functionality. It focuses on improving typography, color systems, layout rhythm, interactive states, and component polish while respecting the project's current tech stack.

Core Features & Use Cases

  • Design audit and diagnosis: Scan the codebase to identify framework, styling method, and specific weak patterns such as oversaturated accents, flat surfaces, or poor typographic scale.
  • Non-destructive fixes: Recommend and implement focused improvements — font swaps, palette cleanup, hover/active states, layout constraints, and improved empty/loading/error states — without rewriting the stack.
  • Upgrade techniques: Provide high-impact enhancements like refined typographic hierarchy, subtle textures, asymmetrical layouts, and motion upgrades for marketing pages, dashboards, and consumer apps.
  • Use case: Take a Tailwind-based marketing site with bland defaults, produce a prioritized audit, and apply targeted CSS and markup edits to elevate visual quality while keeping all interactions intact.

Quick Start

Run a design audit on the project, list the top visual and interaction issues, and propose prioritized, non-breaking fixes that match the existing framework and styles.

Frequently Asked Questions about redesign-existing-projects

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I improve typography and color palette in an existing web project without breaking functionality?

A design audit identifies weak UI patterns like oversaturated accents and poor typographic scale in your existing codebase. It then applies non-destructive fixes such as font swaps, palette cleanup, and improved hover states without rewriting your current tech stack or breaking functionality.

What is the best way to fix generic UI design patterns in a Tailwind-based marketing site?

The best way to fix generic UI in a Tailwind-based marketing site is to run a prioritized audit of visual and interaction issues. You then apply targeted markup and CSS edits to refine typographic hierarchy and add subtle textures while keeping all existing interactions intact.

Does this design audit approach work with vanilla CSS and existing dashboards?

Yes, this design audit works with vanilla CSS and existing dashboards. It scans project source files to identify the styling method and applies non-breaking upgrade techniques like refined layout constraints and improved empty, loading, and error states across marketing sites and consumer apps.

How do I remediate flat surfaces and poor typographic scale in a web app codebase?

To remediate flat surfaces and poor typographic scale, scan your web app codebase to produce a prioritized audit of typography, color, and layout issues. You then implement high-impact enhancements like subtle textures, asymmetrical layouts, and motion upgrades without changing your stack.

Can I upgrade interactive states and component polish without rewriting my tech stack?

Yes, you can upgrade interactive states and component polish without rewriting your tech stack. The process involves recommending focused improvements like hover and active states, layout constraints, and motion upgrades that respect your project's current framework and preserve functionality.

When should I not use non-breaking CSS fixes for a design refactor?

You should not use non-breaking CSS fixes for a design refactor when your project requires a complete tech stack rewrite rather than visual improvements. This approach targets specific weak patterns in existing markup and styles, so it is unsuitable if the underlying architecture must change.