
Uncodixfy
Enforce human-grade, product-style UI (Linear, Raycast, Stripe, GitHub) whenever your agent generates HTML, CSS, or component code so dashboards and landing sections do not look like default AI chrome
Overview
Uncodixify is an agent skill most often used in Build (also Validate, Ship) that blocks generic AI/Codex UI tropes and steers frontend output toward clean, human-designed product aesthetics.
Install
npx skills add https://github.com/cyxzdev/uncodixfy --skill uncodixfyWhat is this skill?
- Explicit ban list for Codex-default AI aesthetics: soft gradients, floating shells, eyebrow labels, hero blocks inside d
- Enforces restrained layouts inspired by Linear, Raycast, Stripe, and GitHub instead of decorative premium chrome
- Concrete layout rules such as normal sidebars (240–260px fixed width, solid background, simple border-right)
- Triggers on HTML, CSS, React, Vue, Svelte, and any frontend UI generation context
- Framed as what NOT to do plus normal implementations to follow strictly
- Sidebar standard: 240–260px fixed width with solid background and simple border-right
Adoption & trust: 4.4k installs on skills.sh; 2.5k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your agent keeps producing soft-gradient, floating-panel dashboards and landing chrome that instantly reads as AI-generated and undermines trust.
Who is it for?
Solo founders implementing admin UIs, settings pages, and marketing surfaces who want consistent non-generic visuals from Claude Code, Cursor, or Codex.
Skip if: Pure backend or CLI work, data-only scripts, or teams that already have a locked design system and only need token-strict codegen without aesthetic guardrails.
When should I use this skill?
Whenever generating HTML, CSS, React, Vue, Svelte, or any frontend UI code to avoid generic AI/Codex aesthetics.
What do I get? / Deliverables
Generated frontend code follows restrained, product-native patterns so interfaces feel closer to Linear, Raycast, Stripe, or GitHub than a template marketplace.
- Frontend code and structure that omit listed Codex UI anti-patterns
- Layouts aligned to documented normal implementations (e.g. standard sidebars)
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Primary shelf is Build frontend because the skill governs how UI code is written during implementation. Frontend subphase is where React, Vue, Svelte, and static UI markup are produced and styled.
Where it fits
Sketch a clickable settings layout in React without hero sections or decorative eyebrow labels.
Generate an analytics sidebar and table views with fixed 240–260px navigation instead of floating glass panels.
Regenerate marketing sections to strip dramatic shadows and transform hovers before launch QA.
Refine a landing page implementation so CTAs and layout match Stripe-like restraint for conversion tests.
How it compares
Aesthetic and layout checker for agent-written UI, not a component library install or Figma-to-code pipeline.
Common Questions / FAQ
Who is uncodixfy for?
Indie builders using AI coding agents on React, Vue, Svelte, or plain HTML/CSS who want product-credible UI instead of default AI styling.
When should I use uncodixify?
Use it during Validate when prototyping UI, throughout Build for pages and dashboards, and at Ship review when polishing UI before launch—any time the agent generates visible frontend surfaces.
Is uncodixify safe to install?
It is guidance-only prose with no runtime hooks; still review the Security Audits panel on this page like any third-party skill package.
SKILL.md
READMESKILL.md - Uncodixfy
# Uncodixify This document exists to teach you how to act as non-Codex as possible when building UI. Codex UI is the default AI aesthetic: soft gradients, floating panels, eyebrow labels, decorative copy, hero sections in dashboards, oversized rounded corners, transform animations, dramatic shadows, and layouts that try too hard to look premium. It's the visual language that screams "an AI made this" because it follows the path of least resistance. This file is your guide to break that pattern. Everything listed below is what Codex UI does by default. Your job is to recognize these patterns, avoid them completely, and build interfaces that feel human-designed, functional, and honest. When you read this document, you're learning what NOT to do. The banned patterns are your red flags. The normal implementations are your blueprint. Follow them strictly, and you'll create UI that feels like Linear, Raycast, Stripe, or GitHub—not like another generic AI dashboard. This is how you Uncodixify. ## Keep It Normal (Uncodexy-UI Standard) - Sidebars: normal (240-260px fixed width, solid background, simple border-right, no floating shells, no rounded outer corners) - Headers: normal (simple text, no eyebrows, no uppercase labels, no gradient text, just h1/h2 with proper hierarchy) - Sections: normal (standard padding 20-30px, no hero blocks inside dashboards, no decorative copy) - Navigation: normal (simple links, subtle hover states, no transform animations, no badges unless functional) - Buttons: normal (solid fills or simple borders, 8-10px radius max, no pill shapes, no gradient backgrounds) - Cards: normal (simple containers, 8-12px radius max, subtle borders, no shadows over 8px blur, no floating effect) - Forms: normal (standard inputs, clear labels above fields, no fancy floating labels, simple focus states) - Inputs: normal (solid borders, simple focus ring, no animated underlines, no morphing shapes) - Modals: normal (centered overlay, simple backdrop, no slide-in animations, straightforward close button) - Dropdowns: normal (simple list, subtle shadow, no fancy animations, clear selected state) - Tables: normal (clean rows, simple borders, subtle hover, no zebra stripes unless needed, left-aligned text) - Lists: normal (simple items, consistent spacing, no decorative bullets, clear hierarchy) - Tabs: normal (simple underline or border indicator, no pill backgrounds, no sliding animations) - Badges: normal (small text, simple border or background, 6-8px radius, no glows, only when needed) - Avatars: normal (simple circle or rounded square, no decorative borders, no status rings unless functional) - Icons: normal (simple shapes, consistent size 16-20px, no decorative icon backgrounds, monochrome or subtle color) - Typography: normal (system fonts or simple sans-serif, clear hierarchy, no mixed serif/sans combos, readable sizes 14-16px body) - Spacing: normal (consistent scale 4/8/12/16/24/32px, no random gaps, no excessive padding) - Borders: normal (1px solid, subtle colors, no thick decorative borders, no gradient borders) - Shadows: normal (subtle 0 2px 8px rgba(0,0,0,0.1) max, no dramatic drop shadows, no colored shadows) - Transitions: normal (100-200ms ease, no bouncy animations, no transform effects, simple opacity/color changes) - Layouts: normal (standard grid/flex, no creative asymmetry, predictable structure, clear content hierarchy) - Grids: normal (consistent columns, standard gaps, no creative overlaps, responsive breakpoints) - Flexbox: normal (simple alignment, standard gaps, no creative justify tricks) - Containers: normal (max-width 1200-1400px, centered, standard padding, no creative wid