Your assets keep overlapping

Two or more “assets” describe the same underlying output, so the system feels redundant.

Run the Asset Definition prompt on each overlapping item. If their purpose,
inputs, and outputs match, they're one asset — merge them and keep the clearer
name. If only the outputs match, you likely have one asset with two formats:
define it once, with a "formats" field.

The mock-up teardown comes back vague

The asset list is generic and could describe almost any product.

Vague output usually means thin input. Give the teardown prompt more to work
with: the actual screenshot, any screenshot-to-code output, and one line on
what the product is for. Then ask it to name assets specifically, and to flag —
not guess — anything it can't determine.

Generated docs drift from the code

Documentation was accurate once, but the repo moved on and the docs didn't.

Treat docs as generated artifacts, not hand-maintained ones. Re-run the Repo
Audit and SOP Generator prompts against the current code on a fixed cadence —
e.g. each release. Store the prompts next to the docs so regeneration is one
step, not a research project.

Flow capture misses steps behind auth

Capture scripts stop at a login wall, so protected flows go undocumented.

If a capture stops at a login wall, the script isn't carrying a session. Sign
in once at the start of the script and reuse that browser context for every
flow. For anything you can't safely screenshot, document the step in words
instead of capturing real data.

Outputs don't paste cleanly into Notion

Workshop outputs lose their structure when pasted into an ops system.

Run the Notion Ops Export prompt as a final pass — don't paste raw workshop
output. Ask it for a flat page hierarchy and simple heading and bullet blocks,
and to avoid tables and deep nesting, which paste handlers tend to mangle.