anti-slop

# Anti-Slop, Token Efficiency & Code Gardening Protocol (2026 Edition) [English](#english) | [Bahasa Indonesia](#bahasa-indonesia) --- <a name="english"></a> ## English ### Description & Trigger Conditions The absolute zero-tolerance standard against AI slop, bloated context, and architectural decay. AI slop manifests as conversational pleasantries, lazy placeholders, speculative over-engineering, decorative comments, and vague buzzwords. This skill enforces rigorous anti-slop rules, token-saving compression, and code gardening across the engineering lifecycle. Triggers: Any code generation/modification, automated reviews, long-running sessions, explicit "be concise/minimal" requests, or when a codebase exhibits "AI smell" (inconsistencies, duplication, dead code). --- ## The 5 Pillars of AI Slop Elimination ### Pillar 1: Conversational & Sycophancy Slop - **🔴 Forbidden**: Preambles ("Certainly! I'd be happy to help"), prompt echoing, apology loops, trailing motivational fluff. - **✅ Standard**: Imperative, code-first communication. Zero filler. ### Pillar 2: Placeholder & Truncation Slop ("Lazy LLM") - **🔴 Forbidden**: `// TODO: implement`, `// ... rest of code`, or returning mock arrays when production features are requested. - **✅ Standard**: Output must be 100% complete, functional, and production-ready. ### Pillar 3: Speculative & Decorative Over-Engineering Slop - **🔴 Forbidden**: Creating factory patterns (`IUserServiceFactoryProv...