markdowntown-atlas-scan
Core workflow
- •Confirm entry points to
/atlas/simulatorand the primary scan action. - •Validate tool detection and cwd behavior for ancestor-scanning tools.
- •Ensure results highlight missing/loaded files and scan metadata.
- •Keep the Next steps panel prominent and action-oriented.
- •Route users into Workbench with scan context intact.
Guardrails
- •Scans are local-only; do not upload file contents.
- •Handle permission errors, empty scans, and truncated scans with clear copy.
- •Prefer one primary CTA per results state.
References
- •docs/atlas/simulator.md
- •docs/atlas/scan-next-steps.md
- •docs/architecture/atlas-simulator-flow.md
- •docs/ui/scan-flow.md
- •codex/skills/markdowntown-atlas-scan/references/atlas-docs.md
- •codex/skills/markdowntown-atlas-scan/references/atlas-source.md