Agent-Native Docs Lookup

Rule

Before implementing or explaining non-trivial Agent-Native behavior, read the version-matched docs installed with @agent-native/core. When examples, imports, or implementation details matter, inspect the packaged source corpus too.

Why

Generated apps and workspaces may be on a different framework version than the public docs or model memory. The installed package is the source that matches the app in front of you. A version-matched @agent-native/core-corpus package provides first-party template source when an app needs those examples, without adding the corpus to every Core installation.

How

From a generated app directory:

pnpm action framework-search --pattern "defineAction"
pnpm action framework-search \
  --pattern "defineAction" \
  --scope source \
  --path "templates/*/actions/*.ts"
pnpm action framework-search --pattern "Agent(?:Panel|Sidebar)" --mode regex --scope source

Use framework-search first when a question may cross the docs and source boundary. It searches version-matched framework docs, runtime-visible skills, readable Core or Toolkit package source, and first-party template source when the optional corpus is installed, in one bounded read-only call. Use scope: docs or scope: source to narrow it, then use the focused readers for the page or file you need.

The headless pnpm agent loop and built-in app agents expose read-only framework-search, docs-search, and source-search tools when Core's docs scripts are bundled. The default substring mode is safest for ordinary questions; use glob for wildcard paths, sql-like for % and _ wildcards, and regex for precise structural matches. Results are bounded, so refine the pattern or path instead of treating a truncated result as exhaustive.

From a generated app directory, the lower-level readers remain available: