A checklist to stop AI coding tools from making glue code
can solve framework problems by adding glue code instead of using the built-in features the framework already provides. That code may work at first, but it can be harder to maintain and may not match the normal style of the framework.
The proposed workflow adds a called a native-path receipt before and after code changes. Before editing, the AI must identify the framework’s built-in features or s and explain why they fit.
After editing, it must confirm that the code followed that choice and meets the framework’s expectations, not only that it runs. The goal is to make tools like duce code that is more standard, easier to maintain, and less patched together.
Key points
- may create glue code when a framework already has a built-in way to solve the problem.
- A native-path receipt forces the AI to name the framework-native option before editing.
- The same receipt checks after editing that the code followed that option.
- The workflow focuses on , not just whether the code runs.
- It is most useful for agent-style coding tools such as Claude Code.