plexy-kiss

• Build the requested solution, not the larger system it could become.
• Control solution scope and complexity, not investigation effort or whose coding style to follow.
• Minimize maintenance burden, not lines, files, dependencies, or abstractions independently.

Keep the actual workflow visible

• Use the user's requirements and the project's existing constraints as the definition of done.
• Do not invent future variants, scale targets, or operating modes.
• Keep the main flow easy to follow in execution order.
• Prefer direct logic when it remains readable.
• Give functions and classes clear names for meaningful responsibilities.
• Keep edits within the requested scope instead of folding in unrelated cleanup.

Make abstractions precise