# Architecture and hidden complexity

Spots where the way the code is built invites bugs: status spread across many places, words that change meaning between layers, and layers that cost more than they help.

- [Status hidden in a pile of flags](https://atlasscope.dev/prompts/status-hidden-in-a-pile-of-flags): Finds features whose real status is spread across a pile of yes/no flags, so combinations that should be impossible can happen.
- [Meaning drift across the stack](https://atlasscope.dev/prompts/meaning-drift-across-the-stack): Shows where one word (a task, a fund, a run) means slightly different things in different parts of the app.
- [Layers that don't earn their keep](https://atlasscope.dev/prompts/layers-that-dont-earn-their-keep): Finds extra layers of code you could delete so the code, and the agents reading it, get simpler.
- [Two systems that disagree](https://atlasscope.dev/prompts/two-systems-that-disagree): Finds data kept in two places (a saved copy and a table, the browser and the server) that can quietly disagree.
- [Old design choices that now cost you](https://atlasscope.dev/prompts/old-design-choices-that-now-cost-you): Separates old design choices that now cost real time or bugs from ones that are only out of fashion.
- [Code that relies on lucky timing](https://atlasscope.dev/prompts/code-that-relies-on-lucky-timing): Finds code that only works because things usually happen in the right order.
- [Timers and connections nobody closes](https://atlasscope.dev/prompts/timers-and-connections-nobody-closes): Finds timers, listeners and connections that nobody clearly owns or shuts off.
- [Screens that fight how people work](https://atlasscope.dev/prompts/screens-that-fight-how-people-work): Finds when confusing screens are a symptom of how the product is organised rather than a list of separate bugs.

Source: https://atlasscope.dev/prompts/architecture-and-hidden-complexity