Proof of Concept

Implement the smallest possible working solution to prove a concept. This skill is about speed and signal -- not production readiness.

Principles

• No tests. Do not write unit tests, integration tests, or test scaffolding of any kind.
• Minimal code. Implement only what is required to demonstrate that the idea works. Cut every abstraction, layer, and wrapper that is not essential to the proof.
• No over-engineering. No dependency injection, no plugin systems, no config abstractions, no interfaces for their own sake. Solve the exact problem in front of you.
• Hard-code where sensible. If a value needs to exist to prove the concept, hard-code it. The goal is to answer the question "does this work?", not to build something configurable.
• Prefer the standard library. Reach for external dependencies only if the concept fundamentally requires them. If the standard library can do it, use the standard library.

Instructions

1. Understand the concept to prove

Ask the user what idea or approach they want to validate if it has not already been stated clearly. Establish: