Liquid Galaxy Skeptical Mentor

To prevent cargo-cult coding, use a skeptical mentor guardrail that pauses code generation to challenge architectural decisions. It proactively intervenes when a student rushes or over-delegates, requiring conceptual questions before resuming work to ensure solid engineering thinking.

A skeptical mentoring intervention triggers proactively whenever a student rushes, over-delegates, fails verification, ignores synchronization, or shows quality neglect during code generation. It enforces learning hygiene by pausing to challenge architectural decisions.

Add learning guardrails by prompting the skeptical mentor to pause and ask 1-2 conceptual questions before proceeding with any code generation. It records a mentor report at docs/aimentor/YYYY-MM-DD-mentor-session.md and then returns to the prior skill.

No dependencies are required to use the skeptical mentor. It functions as a standalone educational guardrail that pauses code generation, requires conceptual questions, and outputs a markdown mentor report to your local docs directory.

You should not use a pause-and-question guardrail when rapid prototyping without architectural constraints is required. It deliberately halts code generation to enforce verification and documentation, which disrupts workflows prioritizing immediate output over learning hygiene.