Use when the task involves Midway framework docs, package selection, API lookup, version compatibility, MCP/HTTP/framework components, or migration guidance. Resolve the requested Midway version first, then query the local Midway skill bundle with `midway-skill` commands.
Use the local @midwayjs/skill-midway bundle before relying on memory.
Resolve the user's requested version first.
Run npm exec midway-skill -- resolve-version <version> or pnpm exec midway-skill resolve-version <version>.
If no version is given, use current.
Query the right source for the question.
Use npm exec midway-skill -- lookup-docs --query "<topic>" or pnpm exec midway-skill lookup-docs --query "<topic>".
Use npm exec midway-skill -- lookup-api --symbol "<symbol>" or pnpm exec midway-skill lookup-api --symbol "<symbol>" for current-major API lookups.
Use npm exec midway-skill -- lookup-packages --query "<package or feature>" or pnpm exec midway-skill lookup-packages --query "<package or feature>".
Use npm exec midway-skill -- lookup-changelog --package "<package>" or pnpm exec midway-skill lookup-changelog --package "<package>" for release history.
Cite what the bundle resolved. Include the requested version, resolved version, and whether it was an exact match or major-version fallback.
docs and changelog.resolve-version reports api: false, do not claim exact historical API details.@midwayjs/ scope in answers when known.