atomic-framework-doc-map

To find Atomic Framework documentation, request the documentation map entry for your target subsystem. The Skill returns the exact doc file, engine path, and owning skill needed for fast source navigation.

The best way to navigate Atomic Framework source code is using the documentation map to link features like core runtime or auth to their canonical engine paths and owning skills before investigating behavior.

Yes, the Atomic Framework documentation map covers CLI, events, and queue subsystems alongside architecture, data, theme, mutex, plugins, and testing documentation for comprehensive cross-reference tasks.

To trace implementation details across overlapping topics, use the documentation map to identify the exact doc file and owning skill for each Atomic Framework subsystem before comparing features.

You need a documentation map for Atomic Framework source navigation when editing, investigating behavior, or tracing implementation details and must move accurately from a feature name to the correct document.

Yes, you can identify which skill owns the documentation for Atomic Framework plugins and tools by requesting the map entry, which provides the doc file, engine path, and skill ownership for source navigation.