Generate beginner-friendly code with assumption checks.

TASK:
Help turn the supplied technical goal into minimal, understandable code.

BEFORE WRITING CODE:
- Restate the goal in one sentence.
- Check whether the requested approach is technically sound.
- Identify missing context that may affect the solution.
- Identify assumptions that are not supported by the supplied materials.
- Do not automatically agree with the user’s proposed approach if it appears incomplete, risky, or technically incorrect.
- Prefer the simplest maintainable solution that a beginner can understand.

SCOPE:
Focus on beginner-friendly implementation.
Do not claim the solution is production-ready unless production requirements were supplied and reviewed.
Do not perform a large refactor unless the user explicitly asks for one.
Do not invent project files, framework setup, package versions, API behavior, environment variables, command outputs, test results, or runtime results.

ASSUMPTION RULES:
- Use only the supplied goal, code, error messages, and project context.
- If a required detail is missing, list it under MISSING CONTEXT.
- If the solution depends on an assumption, state the assumption explicitly under ASSUMPTIONS USED.
- If multiple approaches are possible, choose the simplest suitable approach and briefly explain why.
- If the user’s requested approach is likely wrong, explain the issue and propose a clearer minimal alternative.
- If exact code cannot be written without inventing context, provide a plan and the missing inputs instead of inventing code.

CODE RULES:
- Write minimal code that directly addresses the stated goal.
- Keep names clear and beginner-readable.
- Avoid unnecessary abstractions.
- Avoid unrelated optimizations.
- Do not add new dependencies unless they are required and supported by the supplied context.
- Add comments only where they help a beginner understand the code.
- Include only imports, dependencies, files, or commands that are supported by the supplied context.
- Do not claim the code was run, tested, or verified unless execution evidence was supplied.

OUTPUT:
A) Goal check
B) Missing context
C) Assumptions used
D) Recommended approach
E) Short implementation plan
F) Minimal code
G) Beginner explanation
H) Checks the user should run
I) What was not assumed
J) Confidence

MATERIALS:
"""
Replace this block with:
- the technical goal
- language/framework, if known
- existing code, if any
- runtime/environment, if known
- package/dependency constraints, if any
- error message, if relevant
- what the user already tried, if relevant
"""
