Hosting the AI Slop Party

House Rules

The file set from The AI Slop Party. Rooms by blast radius, gates at the door, and agents that read the fridge.

Source on GitHub

Platform rules

Additive to the root AGENTS.md. A diff usually needs a language file plus a target file. The root AGENTS.md table maps paths to files; this is the same map as a picture.

Contents

Which files apply

flowchart LR
  KT[".kt .kts"] --> KOT[AGENTS.kotlin.md]
  KOT --> AND["+ AGENTS.android.md<br/>Android, Jetpack Compose"]
  KOT --> KMP["+ AGENTS.kmp.md<br/>shared/, expect/actual"]
  KOT --> SPR["+ AGENTS.spring.md<br/>Spring Boot"]
  JV[".java pom.xml"] --> JAV[AGENTS.java.md] --> SPR
  SW[".swift Package.swift"] --> SWI[AGENTS.swift.md] --> IOS["+ AGENTS.ios.md<br/>SwiftUI, UIKit, Xcode"]
  TS[".ts .tsx .js .jsx package.json"] --> TYP[AGENTS.typescript.md] --> RCT["+ AGENTS.react.md"]

Files

File Covers CI that checks it
AGENTS.kotlin.md Kotlin on any target: nullability, coroutines, types, Gradle, tests jvm-quality
AGENTS.android.md Android and Jetpack Compose: state hoisting, lifecycle, design tokens, navigation jvm-quality + android-quality
AGENTS.kmp.md shared/: no platform APIs in commonMain, expect/actual pairs, wire contracts shared-kmp-quality
AGENTS.swift.md Swift on any target: unwraps, concurrency, SPM, server and CLI Swift, tests swift-quality
AGENTS.ios.md iOS apps: SwiftUI, UIKit, Xcode project ios-quality
AGENTS.java.md Java: records, nulls, exceptions, logging, Gradle/Maven, tests jvm-quality
AGENTS.spring.md Spring Boot in Java or Kotlin: injection, thin controllers, DTOs, transactions, migrations jvm-quality
AGENTS.typescript.md TypeScript and JavaScript, browser and Node: strictness, any, boundaries, lockfiles web-quality
AGENTS.react.md React: components render, hooks rules, effects, data layer, a11y web-quality

Shape of every file

Each file has the same sections, so an agent knows where to look:

  1. Build and check: the exact commands to run before saying “done”.
  2. Rules: the stack’s non-negotiables, each one short.
  3. Testing: the frameworks, plus the rule that a bug fix lands with a test that fails before the fix.
  4. Anti-patterns seen in this repo: FILL IN from your own review comments. See STYLE-RULES-TO-FILL.md.

Delete the files for stacks your repo doesn’t have.