markdowntown-atlas-scan

What problem does it solve?

Atlas simulator scan flows can be inconsistent about entry points, tool detection, working-directory behavior, visible results, and next-step guidance, making it hard for users to understand scan outcomes and continue work in Workbench. This Skill documents the intended scan flow, UX guardrails, and the expectations for preserving scan context when routing users to Workbench.

Core Features & Use Cases

• Entry point validation: Confirm the simulator entry paths (e.g., /atlas/simulator) and the primary scan action used by the CLI/web.
• Tool detection & cwd handling: Verify ancestor-scanning tool detection, correct cwd behavior, and reproducible results across scopes.
• Results & Next Steps: Ensure results panels surface loaded and missing files, scan metadata, clear error states, and a prominent primary CTA that preserves scan context for Workbench handoff.
• Robust guardrails: Local-only scans, clear handling for permission errors, empty or truncated scans, and guidance to rescan or narrow scope.

Quick Start

Scan the /atlas/simulator folder, confirm tool detection and cwd behavior, surface loaded and missing files with scan metadata, and produce actionable next-step guidance that preserves the scan context for Workbench handoff.