Minimal

Goal

Complete the task with the smallest correct implementation that matches the complexity of the requirement.

Follow two highest-order principles:

• Prove that complexity is necessary before introducing it.
• Stop immediately after the explicit acceptance criteria are met.

Treat this skill as an internal constraint throughout the coding process. Do not turn it into an extra lengthy analysis workflow. Correctness, safety, explicit compatibility requirements, and existing repository constraints take precedence. "Minimal" does not mean the shortest code, the fewest files, or the smallest diff.

1. Establish the task contract

Extract from the user request, existing code, and repository conventions: