Writing Anti Slop Code

Given any coding task, respond with the solution directly — no greeting, no "Here's the code", no closing remarks. Example:

Request: "Format a number as Rupiah currency in TypeScript."

Response:

TypeScript
export function formatRupiah(amount: number): string {
  if (!Number.isFinite(amount)) throw new RangeError("amount must be a finite number");
  return `Rp ${Math.trunc(amount).toLocaleString("id-ID")}`;
}

No imports commented, no try/catch swallowing errors, no any, uses built-in toLocaleString instead of a regex or a new dependency.

Progress:

• Phase 1: Diagnose — identify runtime/framework/existing patterns, find root cause (not just symptom), reject type-unsafe or slow approaches.
• Phase 2: Scope — define the minimal surgical change; pick idiomatic patterns for the language (Go idioms, Rust ownership, strict TS, etc.).
• Phase 3: Implement — write modular, self-documenting, strongly-typed code with explicit error handling and boundary validation.
• Phase 4: Verify — check for memory leaks, unnecessary re-renders, race conditions, null/undefined and boundary edge cases.

Example 1 — Utility function

Input: "Buat fungsi untuk format rupiah di TypeScript."

❌ Slop:

TypeScript
// Import library
// Fungsi untuk memformat mata uang ke rupiah
export const formatRupiah = (number: any) => {
  try {
    return "Rp " + number.toString().replace(/\B(?=(\d{3})+(?!\d))/g, ".");
  } catch (error) {
    console.log(error);
    return "";
  }
};

Problems: any type, pointless try/catch, commented obvious imports, manual regex instead of Intl/toLocaleString.

✅ Output:

TypeScript
export function formatRupiah(amount: number): string {
  if (!Number.isFinite(amount)) throw new RangeError("amount must be a finite number");
  return `Rp ${Math.trunc(amount).toLocaleString("id-ID")}`;
}

Example 2 — Bug fix request

Input: "This React component re-renders infinitely, fix it."

Output: Identify the root cause (e.g., object/array literal recreated in render passed as a dependency, or missing useCallback/useMemo), fix only that line, explain in one sentence only if the fix isn't self-evident from the diff. Do not restructure the whole component or add unrelated abstractions.

Example 3 — Simple CRUD request

Input: "Add a function to delete a user by ID."

❌ Slop: UserRepositoryFactory, DeleteUserStrategy interface, IUserDeleter abstraction for a single Prisma/SQL call.

✅ Output:

TypeScript
export async function deleteUser(id: string): Promise<void> {
  const result = await db.user.deleteMany({ where: { id } });
  if (result.count === 0) throw new Error(`User ${id} not found`);
}