When should I use the Amplifier Philosophy skill?

Use it when you are designing new system modules, deciding where a specific feature should live in your codebase, or setting up observability standards for a complex application.

How does this skill help with AI-native development?

It promotes a workflow where humans act as architects defining specifications, and AI acts as the builder generating entire modules from those specs, rather than performing fragmented line edits.

What does 'Bricks and Studs' mean in this context?

It refers to a LEGO-like modularity where self-contained components (bricks) connect via stable, documented interfaces (studs), allowing for easier replacement and regeneration without affecting the whole system.

What is the 'Mechanism vs. Policy' principle?

It is the architectural concept that the core system (mechanism) should provide stable capabilities, while external modules (policy) define how those capabilities are orchestrated and configured.

Amplifier Design Philosophy

Name: Amplifier Design Philosophy
Author: drillan

bydrillan

Learning & Documentation

Guides software architecture decisions using a Linux kernel-inspired metaphor for modular, event-driven systems.

About

This skill empowers Claude to apply the Amplifier framework's core principles, such as separating mechanism from policy and prioritizing ruthless simplicity. By using the Linux kernel as a metaphor, it helps developers build stable kernels and flexible modules through a 'bricks and studs' design pattern. It is particularly useful for establishing long-term architectural stability, implementing event-first observability, and adopting an AI-native workflow where modules are regenerated from specifications rather than manually patched.

Key Features

Bricks and Studs modular architecture for independent component regeneration
0 GitHub stars
Event-first observability patterns using canonical JSONL streams
Mechanism vs. Policy decision framework based on Linux kernel principles
Regenerative AI-native development workflow guidance
Stable kernel-module contract design to ensure backward compatibility

Use Cases

Designing regeneratable software components for more efficient AI-assisted development
Defining clear boundaries between core system logic and modular extensions
Implementing a standardized event-driven logging and monitoring system

About

Key Features

Bricks and Studs modular architecture for independent component regeneration
0 GitHub stars
Event-first observability patterns using canonical JSONL streams
Mechanism vs. Policy decision framework based on Linux kernel principles
Regenerative AI-native development workflow guidance
Stable kernel-module contract design to ensure backward compatibility

Use Cases

Designing regeneratable software components for more efficient AI-assisted development
Defining clear boundaries between core system logic and modular extensions
Implementing a standardized event-driven logging and monitoring system