Anti Slop Code

Detect and fix AI-generated frontend implementation slop: isolated helpers that ignore other modules, needless useEffect, type lies, empty wrappers, and boilerplate error handling that misses field edge cases. Trigger for “kode terasa AI”, “rapikan kode”, “dampak ke modul lain”, “edge case”, “error handling generik”, “too many useEffect”, or “over-engineered”. Visual slop stays on anti-slop-design; copy stays on content-design.

9 stars 1 forksSoftware Development Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add sukirman1901/frontend-expert

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sukirman1901/frontend-expert --skill anti-slop-code
Manual install
git clone --depth 1 https://github.com/sukirman1901/frontend-expert.git /tmp/frontend-expert
mkdir -p ~/.claude/skills
cp -r /tmp/frontend-expert/skills/anti-slop-code ~/.claude/skills/anti-slop-code

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Anti-slop Code

## Overview

Generated code often looks tidy **inside one function** while ignoring callers, shared cache, server round-trips, and failures seen in the field. Scan blast radius first. Do not treat a visual restyle or a folder rewrite as a code-slop fix.

## When to use

- Implementing or reviewing React/FE modules that look generated
- “Rapikan kode” / over-engineered hooks / eslint-disable spray
- A change that may hit other modules, cache, or server load
- Generic `try/catch` or toast that skips real failure modes
- Cleaning a screen **without** changing layout, brand, or copy

## When to skip

- Purple/gradients/Lorem-as-layout → `anti-slop-design`
- Generic marketing/UI sentences → `content-design`
- Public props/`show*` soup → `components`
- Feature folders / state ladder / global store → `architecture`
- Query/loader chrome (skeleton, retry control) → `data-fetching`
- Measured LCP/INP/CLS campaigns → `performance`
- Security hardening (XSS, CSP, secrets) — out of this skill

## MUST

| Rule | Detail |
|------|--------|
| **Blast radius** | Name callers, sibling modules, shared types, cache keys, and server calls this change touches |
| **Not isolated** | Do not “fix” one helper by duplicating fetch, invalidating the world, or shifting load onto the client |
| **Preserve intended UX** | Same product behavior unless the user asked to change it; covering missed failures is required |
Read the full skill on GitHub

Details

Skill name
anti-slop-code
Path
skills/anti-slop-code/SKILL.md
License
MIT
Repo updated
5 November 2026

FAQ

What does the Anti Slop Code skill do?

Detect and fix AI-generated frontend implementation slop: isolated helpers that ignore other modules, needless useEffect, type lies, empty wrappers, and boilerplate error handling that misses field edge cases. Trigger for “kode terasa AI”, “rapikan kode”, “dampak ke modul lain”, “edge case”, “error handling generik”, “too many useEffect”, or “over-engineered”. Visual slop stays on anti-slop-design; copy stays on content-design.

How do I install the Anti Slop Code skill?

Claude Code plugin: /plugin marketplace add sukirman1901/frontend-expert. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Anti Slop Code popular?

It lives in sukirman1901/frontend-expert, which has 9 GitHub stars and 1 forks.

Related skills

Accessibility

9

sukirman1901/frontend-expert

Enforce WCAG 2.2 AA by default (keyboard, ARIA, focus, contrast, semantics, target size, dragging alternatives, accessible authentication). Use for accessibility work, pre-ship UI checks, and as a light pass on every UI build or design review — including "a11y", "keyboard", "screen reader", or shipping user-facing changes.

Frontend & Design

Anti Slop Design

9

sukirman1901/frontend-expert

Detect and fix AI aesthetic anti-patterns (purple/indigo defaults, gradients, rounded-2xl everywhere, generic heroes, Lorem ipsum, shadow-heavy cards). Use whenever building, restyling, or reviewing visual UI quality — including "terlalu generik", "AI slop", "rapihin UI", or design audit requests — without requiring /design.

Frontend & Design

App Shell

9

sukirman1901/frontend-expert

App shell, navigation, layouts, breadcrumbs, deep links, 404/empty routes. Use when building dashboard shells, side nav, top nav, multi-page flows, "routing", "layout app", "404", or information architecture for web apps. Requires modern chrome: logo, topbar theme icon, avatar→account menu, custom filter selects — not a bare settings page or native OS selects.

Frontend & Design

Architecture

9

sukirman1901/frontend-expert

Frontend structure — feature folders, state ownership, server/client boundary, when not to add a global store. Use for "arsitektur FE", folder structure, refactor large UI, state management choice, or modularizing an app.

Software Development

Prior Art Scout

5

tlzmw001/naiyue-skills

项目开工前的技术方案调研引擎——给定项目想法,优先核验用户明确提供的项目、URL、工具或技术方向,再搜索最相关的整体方案并把任务拆成流程环节;从 GitHub、Web、X 等来源广泛保留轻量候选,覆盖开源、托管 API、SDK+闭源后端、MCP 等供应形态,对方向命中、完整方案和流程补位候选先核验是否真实可用、文档是否详细、接入是否不过度复杂,每个来源最多选择 5 个做代码或一手材料深验,最终聚焦回答别人解决什么问题、使用什么工具/流程/技术、能否直接使用或借鉴,并给出证据可追溯的评估与建议。当用户说“我想做一个 XX,先调研一下”“优先看看这个项目/方向”“看看有没有人做过类似的”“找现有方案/竞品/prior art”“开工前查一查”时使用。

Software Development

Network Debug

5

franco-bianco/claude-skills

Inspect HTTP traffic captured by PowHTTP MCP proxy. Use when fixing request mismatches in existing code or building new API flows from browser traffic.

Software Development

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.