You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: update READMEs, docs, and homepage for new skill structure
Remove references to old granular skills (core, cli, scopes-and-context,
sessions-and-tags, testing) and replace with the two-skill setup:
agentcrumbs (top-level) and agentcrumbs/init.
|`agentcrumbs/sessions-and-tags`|`session()`, tags, grouping crumbs for replay and filtering |
56
55
57
-
|`agentcrumbs/cli`|`collect`, `tail`, `query`, `strip`, `session`, and other CLI commands |
58
-
59
-
## What each skill contains
60
-
61
-
**Patterns.** Correct usage examples the agent can copy. These show the right way to use each API, with proper markers, at module scope, with structured data.
62
-
63
-
**Common mistakes.** Explicitly marked with severity levels (CRITICAL, HIGH, MEDIUM). Things like: checking `process.env.AGENTCRUMBS` on every call instead of using the noop, creating `trail()` inside request handlers, forgetting `// @crumbs` markers. The agent learns what to avoid, not just what to do.
64
-
65
-
**Constraints.** Hard rules: every crumb line must have a marker, don't invent namespaces without checking the catalog, create trails at module scope.
56
+
The top-level `agentcrumbs` skill covers the essentials an agent needs to use crumbs correctly: the write-collect-query-strip workflow, core API (`trail`, `crumb`, `child`, `scope`), marker syntax, and the most common mistakes. For deeper functionality like sessions, tags, scopes, and testing patterns, it points agents to CLI help (`agentcrumbs --help`), type definitions, and the docs.
66
57
67
58
## The init skill
68
59
69
-
The `agentcrumbs/init` skill deserves special mention. It's the entry point for setting up agentcrumbs in any project.
60
+
The `agentcrumbs/init` skill is the entry point for setting up agentcrumbs in any project.
70
61
71
62
When the agent runs init, it:
72
63
@@ -81,9 +72,8 @@ After init, every agent working in the repo uses the same consistent namespaces.
81
72
If you don't use @tanstack/intent, you can point agents to skills directly:
Copy file name to clipboardExpand all lines: docs/src/app/page.tsx
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -248,7 +248,7 @@ export default function HomePage() {
248
248
</div>
249
249
250
250
<divclassName="hp-skills-detail">
251
-
<p>agentcrumbs ships 5 skills via <ahref="https://tanstack.com/blog/from-docs-to-agents"target="_blank">@tanstack/intent</a>, covering the full API, CLI, and common mistakes. Skills travel with the package version, so the agent always has docs matching the installed code.</p>
251
+
<p>agentcrumbs ships 2 skills via <ahref="https://tanstack.com/blog/from-docs-to-agents"target="_blank">@tanstack/intent</a>: one covering the core workflow, API, and common mistakes, and an init skill that sets up your repo. Skills travel with the package version, so the agent always has docs matching the installed code.</p>
252
252
<p>Compatible with Claude Code, Cursor, GitHub Copilot, and any agent that supports the <ahref="https://agentskills.io"target="_blank">Agent Skills spec</a>.</p>
0 commit comments