Skip to main content

Why This Scales

Without architectural guidance, every developer and every AI session can produce different solutions.

Over time:

Button
PrimaryButton
CustomButton
AppButton

appear throughout the codebase.

Similarly:

Redux
Context
Zustand

can coexist in the same project.

  • Architectural drift becomes inevitable.
  • Skills prevent drift.
  • Atomic Bomb enforces structure.
  • Together they create consistency at scale.

Mini Exercise​

Imagine a codebase where three button names and two state management patterns already exist.

Define three rules you would add to SKILLS.md to stop that drift from growing.

Example​

1. Reuse the existing Button atom before creating any new button variant.
2. Use Context for feature state unless the architecture explicitly defines another pattern.
3. New UI components must follow the existing Atom, Molecule, Organism, Template, Page naming structure.