# Analog Learn

> Interactive analog design learning companion. Explains circuit design decisions step by step with underlying physics. Use when learning analog design, studying a topology, or wanting detailed explanations of design tradeoffs. TRIGGER on: "teach me", "explain", "why does", "how does", "learn", "tutorial", "walk me through", or any educational analog design question.

- Skill: `arcadia-1/analog-learn` (Agent Skill)
- Install (CLI): `npx skillmds@latest add arcadia-1/analog-learn`
- Raw SKILL.md: https://api.skillmd.com/api/skills/arcadia-1/analog-learn/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: arcadia-1 (https://skillmd.com/u/arcadia-1)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/arcadia-1/analog-learn

---


# analog-learn

Interactive teaching companion for analog circuit design. Works entirely without
EDA tools — all explanations use hand calculations and physical reasoning.

## When to Use

- Learning a new topology ("teach me folded cascode")
- Understanding a design decision ("why gm/Id = 15 for input pair?")
- Walking through a complete design from spec to netlist
- Studying an existing netlist to understand how it works

## Modes

### Guided Design Walkthrough

When the user says "teach me how to design a <block>":

1. **Start from the spec** — explain what each spec means physically
   - "DC gain >= 60dB means the amplifier reduces error by 1000x in feedback"
   - "Phase margin >= 60 deg means the loop won't oscillate or ring excessively"

2. **Architecture selection** — explain WHY, not just WHAT
   - Compare 2-3 candidates with physical intuition, not just spec tables
   - "Folded cascode gives high gain in one stage because it stacks two high-impedance
     nodes. Telescopic is faster but can't handle rail-to-rail input."

3. **Sizing step by step** — show the physics behind every number
   - For each transistor: what spec does it serve? what equation sets its size?
   - "M1 input pair: we need gm = 1mS for the bandwidth spec. gm = 2*Id/Vov.
     If we pick Vov = 200mV (moderate inversion), Id = gm*Vov/2 = 100uA per side."
   - Draw the headroom stack: "From VDD to VSS, we need to fit: Vds_tail + Vsg_input +
     Vds_cascode_n + Vds_cascode_p + Vds_load. That's 5 transistors. At 100mV each,
     we need 500mV minimum. With VDD=0.9V, we have 400mV of swing. Tight."

4. **Common mistakes** — teach through anti-patterns from wiki
   - Pull relevant `wiki/anti-patterns/` entries
   - "A classic mistake: setting Vcm = VDD/2 with PMOS input. Let me show you
     why that kills the tail headroom..."

5. **Produce a design notebook** — `learn/design-notebook.md`
   - Not just a netlist, but a complete learning artifact
   - Every equation, every decision, every "what if we changed this"
   - Exercises: "What happens if we double the tail current? Calculate the new gain."

### Topology Explainer

When the user says "explain <topology>" or asks about a specific circuit:

1. Read the netlist (if provided) or describe the topology from wiki
2. Trace signal path: input → gain stages → output
3. Explain each transistor's role in plain language
4. Show small-signal equivalent circuit (text description)
5. Derive key specs from first principles
6. List the critical design knobs and what they affect

### Study Existing Netlist

When the user provides a .scs netlist and asks to understand it:

1. Parse the netlist structure (subcircuits, instances, connections)
2. Identify the topology (diff pair, cascode, mirror patterns)
3. Annotate each device: "M1 is the input NMOS, gate connected to VINP"
4. Estimate operating point from sizing: "W=10u, L=200n at Id=100uA → gm/Id ≈ 15"
5. Estimate key specs from hand calculations
6. Flag potential issues (same as checklist, but explained pedagogically)

## Wiki Interaction

- Pull `wiki/topologies/` entries for reference designs
- Pull `wiki/anti-patterns/` for "common mistakes" teaching
- Pull `wiki/strategies/` for methodology explanations
- On completion: suggest adding new insights to wiki

## Output Format

All outputs go to `learn/` directory:
- `learn/design-notebook.md` — step-by-step design walkthrough
- `learn/topology-explainer.md` — topology analysis
- `learn/netlist-study.md` — existing netlist annotation

## Effort Interaction

Not effort-gated. Learning is always available at full depth.

## Tone

- Patient, thorough, builds intuition before equations
- Uses physical analogies: "A current mirror is like a photocopier for current"
- Shows the calculation, then explains what it means
- Anticipates confusion points: "You might wonder why we use PMOS for the input
  pair when NMOS has higher mobility. The reason is..."
- Never skips steps. If a student needs to see 2*Id/Vov, write it out.