Agent skill · software engineering · enderpuentes
anti-cliche-agent
Enforce strict anti-cliché rules across prose, code, UI/UX, and Next.js/Tailwind/React architecture (2026 Standards). Use this skill whenever the user wants to avoid tropes, banned words, overengineering, UI clichés, excessive abstraction, prop-drilling, legacy React 18 patterns, or generic AI-generated code tells. Also triggers on: 'anti-cliche', 'banned words', 'avoid tropes', 'no clichés', 'clean architecture', 'no overengineering', 'avoid AI writing', 'Next.js best practices', 'React 19'. When in doubt, use this skill — it applies to nearly all code review, UI critique, and writing tasks.
Why this skill is useful
Adds specific guidelines and banned patterns for Next.js, Tailwind, and React architecture that the AI wouldn't reliably generate on its own.
What it needs
About 4k tokens when loaded. Last updated 2026-06-23.
What this skill does
Anti-Cliché Agent — Next.js / Tailwind / React Edition (2026 Standards) Core Principle: Every banned pattern substitutes form for content, or complexity for value. The fix is always: be specific, be cohesive, show consequence, respect what already exists, and embrace modern platform defaults. For detailed reference on each domain, load the relevant file from references/: Architecture & overengineering → references/architecture.md Tailwind & style constants → references/tailwind-constants.md React components & composition → references/components.md Server Components & Server Actions → references/server.md UI/UX patterns → references/ui-ux.md Prose & writing → references/prose.md --- Quick-Reference Banned Patterns React 19+ & Architecture Legacy React Clichés: Do not use useMemo, useCallback, or React.memo (rely on the React Compiler). Do not use forwardRef (use the ref prop). Do not use useContext (favor the use() hook). Types & Naming: Do not use any (use unknown with narrowing). Follow standard ecosystem naming conventions (e.g., PascalCase for React components) without forcing arbitrary naming structures unless defined by the repository. AI Code Tells: Do not write obvious inline comments (e.g., // Check if user exists). Passive-Aggressive Errors: Massive try/catch blocks that just do console.error and return null. Instead, use explicit error returns (like the Result pattern: { success: true, data } or { success: false, error }) and let unexpected system errors bubble up to Error Boundaries. Barrel files (index.ts) that re-export everything from a folder just to look organized. utils/helpers.ts god files — name things by what they do, not that they "help". Tailwind v4 & Constants The @apply Directive: Never use @apply. Use utility classes directly in the markup or compose them via CVA for variants. Over-Configured Variants: Use CVA (Class Variance Authority) for legitimate component variants, but do not create massive JS config files for single-use elements. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills enderpuentes/anti-cliche