skill-tree-generator
Generate, update, and version a complete skill tree (collection of SKILL.md files) for any JavaScript or TypeScript library. Produces core skills (framework-agnostic) and framework skills (React, Solid, Vue bindings) with dependency linking. Activate when producing skill files from a domain map, updating existing skills after a library version change, or auditing skill accuracy. Takes domain_map.yaml and skill_spec.md from skill-domain-discovery as primary inputs.
TanStack · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add TanStack/intent --skill skill-tree-generator技能说明
name: skill-tree-generator description: > Generate, update, and version a complete skill tree (collection of SKILL.md files) for any JavaScript or TypeScript library. Produces core skills (framework-agnostic) and framework skills (React, Solid, Vue bindings) with dependency linking. Activate when producing skill files from a domain map, updating existing skills after a library version change, or auditing skill accuracy. Takes domain_map.yaml and skill_spec.md from skill-domain-discovery as primary inputs. metadata: version: '3.0' category: meta-tooling input_artifacts: - skills/_artifacts/domain_map.yaml - skills/_artifacts/skill_spec.md output_artifacts: - skills/_artifacts/skill_tree.yaml skills: - skill-domain-discovery
Skill Tree Generator
You produce and maintain a tree of SKILL.md files for a library. Every file you create is read directly by AI coding agents across Claude, GPT-4+, Gemini, Cursor, Copilot, Codex, and open-source models. Your output must be portable, concise, and grounded in actual library behavior.
Skill types
Every skill has a type field in its frontmatter. Valid types:
| Type | Purpose | Example |
|---|---|---|
core | Framework-agnostic concepts, configuration, patterns | db-core |
sub-skill | A focused sub-topic within a core or framework skill | db-core/live-queries |
framework | Framework-specific bindings, hooks, components | react-db |
lifecycle | Cross-cutting developer journey (getting started, go-live) | electric-quickstart |
composition | Integration between two or more libraries | electric-drizzle |
security | Audit checklist or security validation | electric-security-check |
Agents discover skills via npx @tanstack/intent list and read them directly
from node_modules. Framework skills declare a requires dependency on
their core skill so agents load them in the right order.
There are two workflows. Detect which applies.
Workflow A — Generate: Build a complete skill tree from a domain map. Workflow B — Update: Diff a library version change and update skills.
Workflow A — Generate skill tree
Prerequisites
You need one of:
skills/_artifacts/domain_map.yamlandskills/_artifacts/skill_spec.mdfrom skill-domain-discovery- Raw library documentation and source code (run a compressed domain discovery first)
If starting from raw docs without a domain map, run a compressed discovery. This produces lower-fidelity output than the full skill-domain-discovery skill — prefer running that when time permits.
- Build a concept inventory (every export, config key, constraint, warning)
- Group into capability domains using work-oriented names (let library complexity drive the count — 2–3 for focused libraries, more for large frameworks)
- Enumerate 10–20 task-focused skills from the intersection of domains and developer tasks
- Extract 3+ failure modes per skill (plausible, silent, grounded)
- Proceed to Step 1 below
Scaffold flow output
If the maintainer uses a custom skills root, replace skills/ in the paths
below with their chosen directory.
For the scaffold workflow, produce a single artifact before writing any SKILL.md files:
skills/_artifacts/skill_tree.yaml
This file enumerates every skill that must be generated in the next step. Do not write SKILL.md files yet unless explicitly asked.
Use this format:
# skills/_artifacts/skill_tree.yaml
library:
name: '[package-name]'
version: '[version]'
repository: '[repo URL]'
description: '[one line]'
generated_from:
domain_map: 'skills/_artifacts/domain_map.yaml'
skill_spec: 'skills/_artifacts/skill_spec.md'
generated_at: '[ISO date]'
skills:
- name: '[task-focused skill name]'
slug: '[kebab-case]'
type: 'core | sub-skill | framework | lifecycle | composition | security'
domain: '[domain slug]'
path: 'skills/[path]/SKILL.md'
package: '[package directory, e.g. packages/client]' # monorepo only — which package this skill belongs to
description: '[1–2 sentence agent-facing routing key]'
requires:
- '[other skill slugs]' # omit if none
sources:
- '[Owner/repo]:docs/[path].md'
- '[Owner/repo]:src/[path].ts'
subsystems:
- '[adapter/backend name]' # omit if none
references:
- 'references/[file].md' # omit if none
Monorepo layout: For monorepos, each skill's path is relative to its
package directory (e.g. packages/client/skills/core/SKILL.md). Set the
package field so generate-skill knows where to write the file. The domain
map artifacts stay at the repo root.
Minimal library fast path
If the domain map contains fewer than 5 skills and no framework adapter packages, skip the core overview + sub-skill registry pattern. Instead:
- Use flat structure — each skill gets its own
skills/[skill-name]/SKILL.md - No router skill — the intent CLI
listcommand is sufficient for discovery - No core overview skill — go directly to individual skill files
- Each skill is type
core(notsub-skill) and stands alone without a parent registry - Skip Step 2 (core overview) and Step 3 (sub-skills) — go directly to writing individual skills as standalone core skills using Step 3's body format
This avoids unnecessary scaffolding for focused libraries where the overhead of a hierarchical skill tree exceeds the navigation benefit.
Step 1 — Plan the file tree
From the domain map, each entry in the skills list becomes a SKILL.md
file. The type field on each skill (core, framework, lifecycle,
composition) determines where it goes. Determine the file