Explore AI Agent Skills & Claude Prompts

Rank mental models from Noah Zender's curated 468-item idea library by leverage for your current situation, with one concrete way to apply each. Use when you're at a decision point — naming, positioning, writing, picking a project, scoping work — and you want frameworks that actually fit your case, not generic mental-models advice. Default source library: noahzender.com/ideas.

code-review

Multi-lens code review — spawns parallel sub-agents to independently review branch changes for bugs, security, and design, then validates and reports only high-signal findings. Use when you want a thorough review before merging or when self-reviewing your own changes.

brand-name-explore

Multi-persona naming exploration with consensus. Spawns parallel sub-agents — each embodying a different naming philosophy (David Placek's Lexicon methodology, the Poet, the Linguist, the Culture Hacker, the Futurist) — to explore divergent naming directions for a product or company, then synthesizes into a ranked shortlist. Based on David Placek's naming framework (Lexicon Branding — Swiffer, BlackBerry, Impossible, Sonos, Pentium). Use when naming a product, company, feature, or brand and you want breadth, surprise, and strategic advantage before committing.

interview-me

Interview the user about a plan, design, or idea until reaching shared understanding. Walks down every branch of the decision tree, resolving dependencies one by one. Maintains a durable transcript on disk so the interview survives context loss. Use when you want to stress-test a plan, think through a design, or need the agent to gather all the context it needs before building.

ai-journa

PROACTIVE SKILL - Observe and document how Adam works with AI. This skill MUST be triggered automatically at the START of every conversation and periodically during long sessions. It runs silently in the background using a sub-agent. Use this skill PROACTIVELY whenever Adam is: coding, debugging, building, implementing, refactoring, planning, reviewing, deploying, testing, designing, configuring, researching, fixing bugs, adding features, writing scripts, setting up infrastructure, asking questions, brainstorming, or doing ANY software engineering task. Triggers on: code, debug, build, implement, refactor, plan, review, deploy, test, design, configure, research, fix, feature, script, infrastructure, question, brainstorm, create, update, delete, modify, change, add, remove, install, setup, migrate, optimize, improve, analyze, explore, search, find, write, edit, commit, push, pull, merge, branch, release, CI, CD, API, database, server, client, frontend, backend, fullstack, react, next, node, python, rust, go, d

tour

Take a guided tour of a codebase subsystem — explore the code in parallel, then produce a self-contained HTML tour document that teaches the architecture so the reader doesn't need to read the code themselves. Optionally critiques the architecture for issues.

devs-roundtable

5 legendary engineers debate your problem in parallel using the most powerful AI model available. Spawns sub-agents as John Carmack, Rich Hickey, Sandi Metz, Linus Torvalds, and Kent Beck — each explores independently, then synthesizes into a ranked consensus. Use when facing architectural decisions, non-obvious implementation choices, or when you want to stress-test an approach from multiple angles before committing.

skill-feedback

Submit concise feedback about AZ skills directly to PostHog. Use when a skill was useful, confusing, broken, missing context, or worth improving.

plan-for-goal

Turn whatever's in the current conversation into one prompt to hand to the agent's `/goal` orchestration loop (Claude Code, Codex, or any harness with the same shape). The prompt is re-injected on every turn of the loop, so it must hold direction, taste, and a self-verification path across many iterations. Use when you're ready to hand a piece of work to `/goal`.

plan-for-mega-goal

Turn a multi-objective piece of work into a roadmap on disk plus a small pointer prompt for the agent's `/goal` orchestration loop. Each sub-goal in the roadmap is shaped like a single `plan-for-goal` output; the roadmap holds the multi-goal scaffolding that wouldn't fit in `/goal`'s 4000-character objective limit. Use when the conversation has 3+ distinct objectives that share a destination.

greenlight-pr

Greenlight a PR — fix CI failures, triage review comments, iterate until green.

repo-history-book

Build a durable, evidence-backed "book" of how an engineering project evolved by mining git history, PRs, releases, and docs. Use when the user wants repository archaeology, commit-by-commit walkthroughs, engineering learning extraction, pivot analysis, or a readable chronology of what the team changed, learned, reverted, and refined over time.