project-tech-designlisted

# Technical designs A technical design settles an architecture. An implementation plan settles tasks. Write the design first. Send every design to the Loupe app for review. **Invoke `loupe-documents` before you write.** That skill gives the format rules for the review UI. This skill gives the content rules. Write the document in ASD-STE100 Simplified Technical English. The writing rules are in `compressing-skills`. ## Verify each claim against the code Read the code before you state a fact about it. Never write a count from memory. One audit design stated five wrong numbers. It claimed 11 security call sites, and the code had 14. It claimed 22 silent handlers, and the code had 27. It claimed one privacy violation, and the code had 26. It also described a renaming workstream that did not exist, because every operation name was already correct. Run the search. Count the result. Put the number in the document. Say what you could not verify. Silence reads as confidence. ## Separate the trigger from the problem The trigger is the event that made you look. The problem is what the code gets wrong. A lapsed trial blocked an agent. That was the trigger. One status column cannot hold two facts. That was the problem. Write both, and keep them apart. A design that fixes the trigger leaves the problem in place. ## Make the change easy, then make the easy change Kent Beck states the rule. Apply it when a small feature does not fit the model. A comped account had to stack wit