skill domain discovery

Other Community

Skill notes

Lightweight path (small libraries)

After Phase 1, decide whether the library warrants the full five-phase flow or the compressed flow below. This is a judgment call — lean toward full discovery unless the library is obviously small (single-purpose utility, 2–3 distinct developer tasks max). Use a compressed flow when the skill surface is small enough that two interview rounds would be

Hard rules — interview phases are mandatory and interactive

These rules override any other reasoning. No exceptions. Phases 2 and 4 are interactive interviews conducted with the maintainer. You must ask the questions specified in each sub-section and wait for the maintainer's response before continuing. Documentation, source code, and other automated analysis are NOT substitutes for the

Phase 1 — Quick scan (autonomous, ~10 minutes)

Orient yourself in the library. You are building a structural map, not reading exhaustively yet.

1a — Read orientation material

README — vocabulary, mental model, what the library does Getting started / quickstart — the happy path Package structure — if monorepo, identify which packages are client-facing vs internal. Focus on the 2–3 packages most relevant to skill consumers (usually client SDKs and primary framework adapters)

1b — Read peer dependency constraints

Check package.json for peerDependencies and peerDependenciesMeta. For each major peer dependency (React, Vue, Svelte, Next.js, etc.): Note the version range required Read the peer's docs for integration constraints that affect this library: SSR/hydration rules, component lifecycle boundaries,

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@TanStack · no license declared
Token usage
Heavy
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 1 — Quick scan (autonomous, ~10 minutes)

Orient yourself in the library. You are building a structural map, not reading exhaustively yet.

02
Phase 2 — High-level interview (interactive — requires maintainer)

The maintainer's mental model of developer tasks IS the skill map. Your job in this phase is to extract it — not to propose your own structure. You must ask the questions below to the maintainer and wait for their responses. Do not infer answers from documentation or source code.

03
Phase 3 — Deep read (autonomous)

You now have the maintainer's task map. Read docs and source to fill each skill area with concrete content — failure modes, code patterns, gotchas.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.