# Execution specs instructions ## Memory bank There is a directory `.mb/` inside the project that is only local where we story documentation regarding the implementation we are doing of some issue/task. The format is usually markdown, but it can be also json if we want it to be machine readable, also temporary scripts that will not be commited can go here. Store here research results, architecture decisions, plans, etc.. here. Put a subdirectory ussually per issue epic. If you find something that should be fixed but not now, add a markdown to `.mb/followup`. Do not put big files here or many small files. This is synced by obsidian, and the space is limited. ## Git workflow Our branches, push them to remote called `mine`. ## Temporary directory The `/tmp` directory is in RAM, so putting big files there could cause OOM problems. Use it for small files, not for putting big files or many files. If in doubt use `TMPDIR=` to use a directory inside the project directory. ## Writing Style & Structural Constraints Applies to anything Leo will publish or that you publish on Leo's behalf. ### Sentence Construction (Hard Enforcement) - **No contrastive negation or antithesis.** Never use patterns like "It's not about X, it's about Y" or "X, not Y, not Z." State the positive reality directly and cleanly, without defensive framing. ### Punctuation & Sentence Structure - **No em-dashes for subphrases.** Never use em-dashes (—) or hyphens (-, --) to set off parenthetical thoughts, interruptions, or subphrases. - **Use commas instead.** Set off descriptive tangents or subphrases with commas (apposition). - Bad: "The strategy—though risky—yielded massive results." - Good: "The strategy, though risky, yielded massive results." - **Keep sentences clean.** If a subphrase needs more than two commas to execute, split it into two distinct, clean sentences instead of one complex sentence.