# Add Tanner To Your Codebase

URL: https://tannergodarzi.com/blog/add-tanner-to-your-codebase
Published: 2026-07-09

I had a standing joke in meetings with Designers and Marketing folks: “I’m Where Ideas Go to Die.” Not because the ideas were bad—they were usually great—but because there was exactly one of me and a very long line of work.

It was only half a joke. Across Dropbox, Notion, Square, and Vercel, I’ve built marketing and brand experiences that contributed hundreds of millions of dollars in ARR, and behind a surprising share of that revenue is the same advice, delivered over and over:

- Build brand-forward, user-friendly experiences—those aren’t competing priorities; they’re the whole assignment.
- Make the best damn thing possible.
- Care how it’s delivered—how fast it loads, how it ships, and how it holds up when the whole world arrives.
- Sweat every little pixel. People feel the details before they can name them.

That advice travels the artisanal way: design reviews, code reviews, pairing sessions, onboarding docs, and an ungodly pile of repeated Slack messages. It works. It just doesn’t scale past the number of rooms I can be in at once. The supply of Tanners has historically been capped at one.

Scaling Tanner in an org has been a dream of mine for a while now. (Humble, I know.) Agents finally make it happen.

## Meet Tanner Skills

Tanner Skills are agent skills you add to your codebase. They give your coding agent the standards and review processes I’d bring to a team building a marketing site or brand experience—which means yes, I have finally shipped myself as a dependency.

They’re built on my open-source agent standards: the shared conventions I use across projects so agents understand how I want work planned, built, reviewed, and shipped.

The collection so far:

- **Brand voice:** write and edit copy with a consistent point of view—mine. Install it and your agent talks like Tanner. Treat it as inspiration for writing your own brand voice skill; in the meantime, you can talk like me.
- **Quality:** hold performance, accessibility, design, and content to one shared bar.
- **Code review:** review front-end changes in the browser, not just in the diff.
- **Website review:** audit the live experience across breakpoints, themes, localization, and agent readability.
- **Pull requests:** explain the goal, show the visual changes, and document how the work was tested.
- **Cleanup:** a lightweight pre-commit pass over changed files and new copy.

These aren’t prompts you need to remember to paste into a chat. They live with the project, and your agent of choice will invoke them while doing the work. You can also call for me by name—ask for the `tanner-website-review` skill and a small, opinionated version of me will audit your site.

## Add Tanner to your codebase

If you only want the skills, install them through skills.sh:

```bash
npx skills add tannergodarzi/tanner-agent-standards
```

The installer lists what’s available and adds the ones you choose to your agent’s native skills folder.

One specific skill:

```bash
npx skills add tannergodarzi/tanner-agent-standards --skill tanner-code-review
```

The whole set:

```bash
npx skills add tannergodarzi/tanner-agent-standards --all
```

If you want the complete standards package—the shared `AGENTS.md` rules, skills, hooks, syncing, and drift checks—install it straight from GitHub:

```bash
npm i -D github:tannergodarzi/tanner-agent-standards
npx tanner-agent-standards init
```

Then edit the one-line app description in `AGENTS.md` and commit the generated files. The setup is agent-agnostic: the standards live in `AGENTS.md`, and the skills land in the native homes used by tools like Claude Code and Cursor. Every other agent can find them through the skills index in `AGENTS.md`.

These skills will keep evolving as my own practices do—new skills, sharper guidance, better review processes. I’m learning from every project I run them on, and the package will show it.

To pull the latest and sync it into your project:

```bash
npx tanner-agent-standards update
```

Both `init` and `update` are idempotent, so run them as often as you like.

## Why I’m doing this

Because the only way this advice ever traveled was me repeating it, one Slack message or Notion Doc at a time.

None of it is secret, either. Most of what makes a good marketing or brand experience is small decisions: how the page behaves while it loads, whether the layout holds up between breakpoints, whether the copy sounds like the company, whether anyone looked at the rendered page before approving it. Whether a team makes them usually comes down to who happens to be in the room—or who already learned the lesson the expensive way.

Skills make it portable. A small team starts with the same quality bar I’d share during onboarding. An agent catches the recurring issues before a human ever opens the review. A collaborator sees not just what I’d flag, but the process I’d use to inspect the work. Think of it as a sourdough starter: a small, living culture of opinions that keeps working long after I’ve left the kitchen.

The goal isn’t to replace taste, judgment, or a strong team. A skill can tell you that an enter animation should ease out, that a layout shifts while loading, or that a call to action falls apart on mobile. It can’t give you the eye to notice when something feels off, or the taste to know what *right* feels like. That part is still yours.

But it can make the fundamentals available.  That’s what Tanner Skills are: the advice I’d repeat to your team, packaged so anyone—and any agent—can use it. I’m one npx command away.

```bash
npx skills add tannergodarzi/tanner-agent-standards
```