Skip to content

Commit d500b62

Browse files
KyleAMathewsclaude
andcommitted
fix author name spelling
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1 parent 955de55 commit d500b62

File tree

1 file changed

+1
-5
lines changed

1 file changed

+1
-5
lines changed

src/blog/from-docs-to-agents.md

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: 'From Docs to Agents: Shipping Knowledge That Travels With Your Package'
33
published: 2026-03-04
44
authors:
55
- Sarah Gerrard
6-
- Kyle Matthews
6+
- Kyle Mathews
77
---
88

99
![From Docs to Agents](/blog-assets/from-docs-to-agents/header.png)
@@ -30,10 +30,6 @@ Meanwhile, library maintainers already have the knowledge agents need. It lives
3030

3131
`@tanstack/intent` is the missing lifecycle layer. It's a toolkit for generating, discovering, and maintaining skills for your library — and shipping them as npm packages so they travel with your code.
3232

33-
```bash
34-
pnpm add -D @tanstack/intent
35-
```
36-
3733
The core idea: **intents are npm packages of skills.** They encode how tools work together, what patterns apply for which goals, and what to avoid. Skills travel with the tool via `npm update`, not the model's training cutoff. Not community-maintained rules files in separate repos. Not prompt snippets in READMEs. Versioned knowledge the maintainer owns, shipped through npm, updated when the package updates.
3834

3935
A skill is a focused projection of knowledge you already maintain — the critical constraint an agent must know, the anti-pattern flagged explicitly, the composition rule stated once and clearly. Each skill declares which docs it was derived from:

0 commit comments

Comments
 (0)