원클릭으로 Manus에서 모든 스킬 실행

uncodixfy

Codex facade for anti-generic UI correction. Use on frontend work to remove Codex-looking patterns and chain to ultra-ui/ux-compiler.

Manus에서 실행

스타4

포크0

업데이트2026년 5월 29일 20:19

출처

InugamiDev

InugamiDev/ultrathink

GitHub 저장소 열기 Creator 저장소 보기

설치 명령

다운로드

Manus에서 실행

유용한 대상SOC

소프트웨어 개발자컴퓨터 및 수학직15-1252L4

SKILL.md

readonly

name	uncodixfy
description	Codex facade for anti-generic UI correction. Use on frontend work to remove Codex-looking patterns and chain to ultra-ui/ux-compiler.

Uncodixfy Facade

Use when UI looks generic, AI-generated, overdesigned, or like default Codex output. This starts before layout/component decisions, not at final polish.

Required:

Run the Uncodixfy start gate first: name the default AI moves you would normally make, ban them, and choose normal product replacements.
Classify docs/design sources before using them: product/page brief, token-only, architecture-only, guideline-only, stale, or ignored.
For non-trivial UI, create or consume DESIGN-CONTRACT.md: product intent, user journey, IA, page shell, states, accessibility, Codex rules, and anti-patterns.
Keep DESIGN.md as the token/visual-system contract; do not stuff product strategy or implementation process into it.
Run ux-compiler for product intent when the change is more than mechanical styling.
Use existing app tokens, components, typography, density, and icon system before inventing a style.
Avoid glass, gradients, oversized radii, hero dashboards, decorative copy, KPI filler, badge spam, fake charts, and hover transforms unless the product explicitly needs them.
Chain the full skill at .claude/skills/uncodixfy/SKILL.md, plus ultra-ui and ui-polish as needed.

이 저장소의 다른 Skills

같은 저장소

ultra-ui

InugamiDev/ultrathink

Ultra UI skill - human-centered UI pipeline plus Google's DESIGN.md spec, ui-ux-pro-max knowledge base, source relevance filtering, and Uncodixfy anti-generic reasoning gate. Generates source relevance, UX, concept, composition, 2D/3D scene, motion, state, implementation, QA, and lint-clean DESIGN.md artifacts before coding.

2026-05-304

uncodixfy

InugamiDev/ultrathink

Anti-Codex UI correction skill for removing generic AI/Codex visual patterns from app screens: soft gradients, glass panels, oversized radii, fake dashboards, decorative copy, hero blocks inside products, blue-purple SaaS defaults, and overdesigned AI-looking UI.

2026-05-294

ux-compiler

InugamiDev/ultrathink

Compile raw product or UI intent into a User Journey Intelligence Brief and Codex Implementation Brief before code. Supports Claude-orchestrated and Codex solo mode with a required critique pass.

2026-05-294

ux-compiler

InugamiDev/ultrathink

Codex solo UI/product-flow compiler: create a User Journey Intelligence Brief, critique it, then produce a Codex Implementation Brief before writing code.

2026-05-274

debug-fix

InugamiDev/ultrathink

Debug and apply targeted fixes: reproduce symptoms, identify root cause, patch narrowly, and verify with focused commands.

2026-05-264

goal

InugamiDev/ultrathink

Define the task goal and provider runtime contract before implementation: Codex, Claude, API hosts, Studio, CLI, TUI, docs, verification, and image placeholders.

2026-05-264

name	uncodixfy
description	Codex facade for anti-generic UI correction. Use on frontend work to remove Codex-looking patterns and chain to ultra-ui/ux-compiler.

Uncodixfy Facade

Use when UI looks generic, AI-generated, overdesigned, or like default Codex output. This starts before layout/component decisions, not at final polish.

Required:

Run the Uncodixfy start gate first: name the default AI moves you would normally make, ban them, and choose normal product replacements.
Classify docs/design sources before using them: product/page brief, token-only, architecture-only, guideline-only, stale, or ignored.
For non-trivial UI, create or consume DESIGN-CONTRACT.md: product intent, user journey, IA, page shell, states, accessibility, Codex rules, and anti-patterns.
Keep DESIGN.md as the token/visual-system contract; do not stuff product strategy or implementation process into it.
Run ux-compiler for product intent when the change is more than mechanical styling.
Use existing app tokens, components, typography, density, and icon system before inventing a style.
Avoid glass, gradients, oversized radii, hero dashboards, decorative copy, KPI filler, badge spam, fake charts, and hover transforms unless the product explicitly needs them.
Chain the full skill at .claude/skills/uncodixfy/SKILL.md, plus ultra-ui and ui-polish as needed.