Architecture
Promptable or Programmable?
Decide whether the problem belongs in prompts, code, or a hybrid approach with both.
What the tool does
This tool helps you decide whether a problem belongs in prompts, code, or a hybrid design.
Who it's for
It is for builders trying to avoid overusing LLMs where deterministic software would be better.
When to use it
Use it when the team is split between “just prompt it” and “just code it.”
Practical Use Case
Helpful during technical planning when you need a cleaner boundary between language-model judgment and normal application logic.
Share The Result
Export results as a PDF to share in meetings, planning docs, or internal documentation.
Recommendation
Use a hybrid approach
Determinism
Low
Tool Use
Needed
Use a hybrid approach
You need model judgment plus code-enforced tool boundaries, not just one or the other.
Why This Recommendation Fits
- The task still needs model judgment or interpretation, so pure automation would be too rigid.
- Real tool access means the design needs explicit boundaries and system controls.
Design Caution
- Mixed signals usually mean the cleanest design is a hybrid, not an ideological choice.