antislop

Filters generic AI-generated UI patterns using 38 purpose-gate design rules.

Updated Dec 17, 2025
One-click install
npx skills add https://github.com/faidzagustiawan/portofolio --skill antislop-faidzagustiawan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: antislop
Source: https://github.com/faidzagustiawan/portofolio/tree/main/agent/skills/antislop
Command: npx skills add https://github.com/faidzagustiawan/portofolio --skill antislop-faidzagustiawan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding agents tend to produce recognizable, generic interface designs: blue-purple gradients, glassmorphism everywhere, template landing pages, fake testimonials, and dead buttons. This Skill acts as a filter that rejects technique without purpose and holds every UI decision to a craftsmanship standard, so output feels designed rather than generated. ## Core Features & Use Cases - Rule-Based UI Filter: Applies 38 grouped rules (Hard Gate, Purpose-Gate, Quality Locks) covering color, typography, layout, copywriting, accessibility, and functionality. - Two Usage Modes: Works during development to prevent slop while building, or after completion as an audit producing a numbered findings list with priorities. - Install Wizard & Skill Ecosystem: Optionally installs companion skills (UI, copywriting, accessibility, mobile layout, code comments) and appends a pointer block to the project's agent entry file. - Use Case: While building a landing page with an AI agent, the filter blocks fake statistics, requires real navigation targets, enforces WCAG contrast and keyboard access, and demands a stated purpose for every gradient, badge, or icon. ## Quick Start Ask the agent to read the antislop core file and apply its rules while building or auditing your website UI.

Frequently Asked Questions about antislop

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

FAQPage Schema
How do I stop AI agents from generating generic UI designs?▼

Load the antislop core rules before UI work so the agent applies a purpose test to every visual technique. It rejects defaults like blue-purple gradients, glassmorphism stacks, and template layouts unless a written reason ties them to hierarchy or identity.

What is the difference between the during and after modes?▼

During mode applies the rules while the agent writes UI, preventing slop from the start. After mode audits a finished project, producing a numbered findings list with priorities; you pick which findings to fix before anything changes.

Does antislop work with Claude Code, Codex, or Gemini CLI?▼

Yes. The install wizard appends a pointer block to whichever entry file the tool reads at session start: CLAUDE.md for Claude Code, AGENTS.md for Codex, or GEMINI.md for Gemini CLI. The pointer takes effect from the next session.

Do I need a DESIGN.md file to use antislop?▼

No, but without design direction the output is labeled a draft with low energy, rhythm, and motion dials. Antislop is a filter, not a source of direction, so a DESIGN.md or explicit brand guidance is recommended for shippable results.

What design patterns does antislop forbid outright?▼

Hard Gate rules forbid em dashes in UI text, fake statistics and testimonials, dead buttons and navbar links, poor color contrast, missing keyboard access, fabricated security claims, and UIs without empty, loading, and error states.