atomic-framework-overview

Map Atomic Framework architecture and bootstrap flow across web, API, CLI, telemetry, and plugin subsystems.

9|1|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/MADEVAL/Atomic-Framework-Skills --skill atomic-framework-overview
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: atomic-framework-overview
Source: https://github.com/MADEVAL/Atomic-Framework-Skills/tree/main/atomic-framework-overview
Command: npx skills add https://github.com/MADEVAL/Atomic-Framework-Skills --skill atomic-framework-overview

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes guesswork when working inside Atomic Framework by giving you a reliable map of the bootstrap sequence, module boundaries, routing flow, and the correct place to make changes.

Core Features & Use Cases

  • Architecture Orientation: Understand how Atomic wraps Fat-Free Framework, how the hive is used, and where runtime state lives.
  • Boot and Routing Guidance: Trace the startup chain from engine entry points through app initialization and route dispatch for web, API, CLI, and telemetry paths.
  • Module Selection: Quickly identify which subsystem owns a behavior so you can load the right follow-up skill before editing code.
  • Use Case: Before implementing a feature or debugging a framework issue, use this skill to determine whether the change belongs in core, auth, queue, theme, plugins, or another module.

Quick Start

Ask for the Atomic Framework overview before changing any engine code so you can follow the correct bootstrap path, module owner, and routing entry point.

Frequently Asked Questions about atomic-framework-overview

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does the Atomic Framework bootstrap sequence work?

The Atomic Framework bootstrap sequence traces startup from engine entry points through app initialization to route dispatch. It maps how Fat-Free Framework hive usage and lifecycle registration handle runtime state across web, API, CLI, and telemetry paths.

What is the best way to find which module owns a behavior in Atomic Framework?

To find the owning module in Atomic Framework, map the subsystem boundaries for core, auth, queue, theme, or plugins. This identifies the correct subsystem owner before loading a follow-up skill to edit code.

How do I trace routing flow for API and CLI requests in Atomic Framework?

Tracing routing flow for API and CLI requests in Atomic Framework involves following the route dispatch chain from app initialization. This maps how Fat-Free Framework hive routes requests through specific subsystem entry points.

Does Atomic Framework use Fat-Free Framework hive for runtime state?

Atomic Framework uses the Fat-Free Framework hive for runtime state management. The architecture wraps Fat-Free Framework, storing lifecycle registration and dispatch data within the hive during the boot sequence.

When do I need to check the Atomic Framework module map before coding?

Check the Atomic Framework module map before implementing a feature or debugging a framework issue. This determines whether the change belongs in core, auth, queue, theme, plugins, or another module.

Why does my route dispatch fail during Atomic Framework startup?

Route dispatch failures during Atomic Framework startup often stem from incorrect lifecycle registration or hive state. Tracing the bootstrap flow from engine entry points through app initialization helps locate the broken dispatch path.