---
name: amplifier
description: >
  When adaptation-observer or emergence-detector surfaces something good, amplifier figures
  out how to strengthen it. Not "add a feature" but "create conditions for more of this
  behavior." Use when a positive pattern is identified and needs to be reinforced.
metadata:
  author: nirav
  version: "1.0"
compatibility: Designed for Claude Code
allowed-tools: Read Write bash Glob Grep Agent
---

# Amplifier — Strengthening What Works

The instinct when something works is to "add more features." The AI-native instinct is different: **create conditions for more of this behavior to emerge naturally.**

Amplification is not addition. It's cultivation.

## Amplification Strategies

### Reduce Friction

If something is working despite obstacles, remove the obstacles. The behavior will naturally increase.

- **Question:** What makes it hard for users to experience this good behavior?
- **Action:** Remove barriers, simplify paths, reduce steps
- **Measure:** Does the behavior frequency increase?

### Strengthen the Loop

If a reinforcing loop is producing good behavior, make the loop tighter and faster.

- **Question:** What's the feedback cycle time? Can it be shortened?
- **Action:** Make signals more visible, make responses faster, make effects more noticeable
- **Measure:** Does the loop accelerate?

### Expand the Conditions

If good behavior emerges in one context, create similar conditions in adjacent contexts.

- **Question:** What conditions produced this emergence? Where else do similar conditions exist?
- **Action:** Replicate the capability combination in new contexts
- **Measure:** Does the behavior emerge in the new context?

### Make It Visible

Sometimes the best amplification is just making the behavior visible to the user.

- **Question:** Does the user know this is happening?
- **Action:** Surface the behavior. Show the user what the system is doing well.
- **Measure:** Does awareness increase usage?

### Connect to Other Surfaces

Good behavior in one surface might enhance another.

- **Question:** Could this pattern benefit other products in the portfolio?
- **Action:** Cross-pollinate — share the conditions or capabilities with other surfaces
- **Measure:** Does the behavior emerge in connected surfaces?

## Amplification Anti-Patterns

- **Over-engineering:** Adding complex systems to support something that was working naturally. If it ain't broke, don't optimize it — just remove friction.
- **Premature amplification:** Amplifying a pattern before confirming it's genuinely valuable (not just novel). Wait for repeated observation.
- **Amplification-as-addiction:** Creating reinforcing loops that maximize engagement but not value. The system should be useful, not addictive.

## Output

```markdown
# Amplification Plan: {pattern name}

## Pattern Observed
{What's working and where}

## Strategy
{Which amplification approach — reduce friction / strengthen loop / expand conditions / make visible / connect}

## Specific Actions
1. {action}
2. {action}

## Expected Effect
{What we expect to see if amplification works}

## Watch For
{Potential negative side effects of amplification}
```