@tanstack/intent 0.0.13 → 0.0.19

package/README.md

@@ -10,9 +10,9 @@ Docs target humans who browse. Types check individual API calls but can't encode
 
 The ecosystem already moves toward agent-readable knowledge — Cursor rules, CLAUDE.md files, skills directories. But delivery is stuck in copy-paste: hunt for a community-maintained rules file, paste it into your config, repeat for every tool. No versioning, no update path, no staleness signal.
 
-## Skills: versioned knowledge in npm
+## Skills: versioned knowledge in your package manager
 
-A skill is a short, versioned document that tells agents how to use a specific capability of your library — correct patterns, common mistakes, and when to apply them. Skills ship inside your npm package and travel with the tool via `npm update` — not the model's training cutoff, not community-maintained rules files, not prompt snippets in READMEs. Versioned knowledge the maintainer owns, updated when the package updates.
+A skill is a short, versioned document that tells agents how to use a specific capability of your library — correct patterns, common mistakes, and when to apply them. Skills ship inside your package and travel with the tool via your normal package manager update flow — not the model's training cutoff, not community-maintained rules files, not prompt snippets in READMEs. Versioned knowledge the maintainer owns, updated when the package updates.
 
 Each skill declares its source docs. When those docs change, the CLI flags the skill for review. One source of truth, one derived artifact that stays in sync.
 
@@ -20,20 +20,32 @@ The [Agent Skills spec](https://agentskills.io) is an open standard already adop
 
 ## Quick Start
 
+### Command runners
+
+Use whichever command runner matches your environment:
+
+| Tool | Pattern                                      |
+| ---- | -------------------------------------------- |
+| npm  | `npx @tanstack/intent@latest <command>`      |
+| pnpm | `pnpm dlx @tanstack/intent@latest <command>` |
+| bun  | `bunx @tanstack/intent@latest <command>`     |
+
+If you use Deno, support is best-effort today via `npm:` interop with `node_modules` enabled. First-class Deno runtime support is not implemented yet.
+
 ### For library consumers
 
 Set up skill-to-task mappings in your project's agent config files (CLAUDE.md, .cursorrules, etc.):
 
 ```bash
-npx @tanstack/intent install
+npx @tanstack/intent@latest install
 ```
 
-No per-library setup. No hunting for rules files. Install the package, run `npx @tanstack/intent install`, and the agent understands the tool. Update the package, and skills update too.
+No per-library setup. No hunting for rules files. Install the package, run `npx @tanstack/intent@latest install` through your preferred command runner, and the agent understands the tool. Update the package, and skills update too.
 
 List available skills from installed packages:
 
 ```bash
-npx @tanstack/intent list
+npx @tanstack/intent@latest list
 ```
 
 ### For library maintainers
@@ -41,7 +53,7 @@ npx @tanstack/intent list
 Generate skills for your library by telling your AI coding agent to run:
 
 ```bash
-npx @tanstack/intent scaffold
+npx @tanstack/intent@latest scaffold
 ```
 
 This walks the agent through domain discovery, skill tree generation, and skill creation — one step at a time with your review at each stage.
@@ -49,39 +61,64 @@ This walks the agent through domain discovery, skill tree generation, and skill
 Validate your skill files:
 
 ```bash
-npx @tanstack/intent validate
+npx @tanstack/intent@latest validate
+```
+
+In a monorepo, you can validate a package from the repo root:
+
+```bash
+npx @tanstack/intent@latest validate packages/router/skills
 ```
 
 Check for skills that have fallen behind their sources:
 
 ```bash
-npx @tanstack/intent stale
+npx @tanstack/intent@latest stale
 ```
 
+From a monorepo root, `intent stale` checks every workspace package that ships skills. To scope it to one package, pass a directory like `intent stale packages/router`.
+
 Copy CI workflow templates into your repo so validation and staleness checks run on every push:
 
 ```bash
-npx @tanstack/intent setup-github-actions
+npx @tanstack/intent@latest setup-github-actions
 ```
 
+## Compatibility
+
+| Environment    | Status      | Notes                                              |
+| -------------- | ----------- | -------------------------------------------------- |
+| Node.js + npm  | Supported   | Use `npx @tanstack/intent@latest <command>`        |
+| Node.js + pnpm | Supported   | Use `pnpm dlx @tanstack/intent@latest <command>`   |
+| Node.js + Bun  | Supported   | Use `bunx @tanstack/intent@latest <command>`       |
+| Deno           | Best-effort | Requires `npm:` interop and `node_modules` support |
+| Yarn PnP       | Unsupported | `@tanstack/intent` scans `node_modules`            |
+
+## Monorepos
+
+- Run `npx @tanstack/intent@latest setup-github-actions` from either the repo root or a package directory. Intent detects the workspace root and writes workflows to the repo-level `.github/workflows/` directory.
+- Generated workflows are monorepo-aware: validation loops over workspace packages with skills, staleness checks run from the workspace root, and notify workflows watch package `src/` and docs paths.
+- Run `npx @tanstack/intent@latest validate packages/<pkg>/skills` from the repo root to validate one package without root-level packaging warnings.
+- Run `npx @tanstack/intent@latest stale` from the repo root to check all workspace packages with skills, or `intent stale packages/<pkg>` to check one package.
+
 ## Keeping skills current
 
-The real risk with any derived artifact is staleness. `npx @tanstack/intent stale` flags skills whose source docs have changed, and CI templates catch drift before it ships.
+The real risk with any derived artifact is staleness. `npx @tanstack/intent@latest stale` flags skills whose source docs have changed, and CI templates catch drift before it ships.
 
-The feedback loop runs both directions. `npx @tanstack/intent feedback` lets users submit structured reports when a skill produces wrong output — which skill, which version, what broke. That context flows back to the maintainer, and the fix ships to everyone on the next `npm update`. Every support interaction produces an artifact that prevents the same class of problem for all future users — not just the one who reported it.
+The feedback loop runs both directions. `npx @tanstack/intent@latest feedback` lets users submit structured reports when a skill produces wrong output — which skill, which version, what broke. That context flows back to the maintainer, and the fix ships to everyone on the next package update. Every support interaction produces an artifact that prevents the same class of problem for all future users — not just the one who reported it.
 
 ## CLI Commands
 
-| Command                                     | Description                                         |
-| ------------------------------------------- | --------------------------------------------------- |
-| `npx @tanstack/intent install`              | Set up skill-to-task mappings in agent config files |
-| `npx @tanstack/intent list [--json]`        | Discover intent-enabled packages                    |
-| `npx @tanstack/intent meta`                 | List meta-skills for library maintainers            |
-| `npx @tanstack/intent scaffold`             | Print the guided skill generation prompt            |
-| `npx @tanstack/intent validate [dir]`       | Validate SKILL.md files                             |
-| `npx @tanstack/intent setup-github-actions` | Copy CI templates into your repo                    |
-| `npx @tanstack/intent stale [--json]`       | Check skills for version drift                      |
-| `npx @tanstack/intent feedback`             | Submit skill feedback                               |
+| Command                                            | Description                                         |
+| -------------------------------------------------- | --------------------------------------------------- |
+| `npx @tanstack/intent@latest install`              | Set up skill-to-task mappings in agent config files |
+| `npx @tanstack/intent@latest list [--json]`        | Discover intent-enabled packages                    |
+| `npx @tanstack/intent@latest meta`                 | List meta-skills for library maintainers            |
+| `npx @tanstack/intent@latest scaffold`             | Print the guided skill generation prompt            |
+| `npx @tanstack/intent@latest validate [dir]`       | Validate SKILL.md files                             |
+| `npx @tanstack/intent@latest setup-github-actions` | Copy CI templates into your repo                    |
+| `npx @tanstack/intent@latest stale [dir] [--json]` | Check skills for version drift                      |
+| `npx @tanstack/intent@latest feedback`             | Submit skill feedback                               |
 
 ## License
 

package/dist/cli.d.mts

@@ -1 +1,6 @@
-export { };
+#!/usr/bin/env node
+//#region src/cli.d.ts
+declare const USAGE = "TanStack Intent CLI\n\nUsage:\n  intent list [--json]           Discover intent-enabled packages\n  intent meta [name]             List meta-skills, or print one by name\n  intent validate [<dir>]        Validate skill files (default: skills/)\n  intent install                  Print a skill that guides your coding agent to set up skill-to-task mappings\n  intent scaffold                Print maintainer scaffold prompt\n  intent add-library-bin         Generate bin/intent.{js,mjs} bridge file\n  intent edit-package-json       Wire package.json (files, bin) for skill publishing\n  intent setup-github-actions    Copy CI workflow templates to .github/workflows/\n  intent stale [dir] [--json]    Check skills for staleness";
+declare function main(argv?: Array<string>): Promise<number>;
+//#endregion
+export { USAGE, main };