geju
Geju
Overview
Use this skill to open up the design space during strategic discussion. It pushes Codex out of compatibility anxiety, local-detail fixation, and small-patch thinking so the answer can address the real product, architecture, or system direction.
Core Principle
Bold hypothesis, careful verification.
Geju is not trying to produce a guaranteed-correct answer. It is trying to produce a high-leverage, provocative, useful hypothesis that opens the design space. Treat the thesis as a strong hypothesis to test, not as an oracle.
Do not let refactor difficulty, compatibility fear, existing implementation shape, or local details decide the direction too early. Those are constraints to price, not masters to obey. First make the bold hypothesis; then define the careful verification path.
Ways To Open The Frame
Use these moves when the discussion is trapped in local optimization: