From pubdoc-skills
Answers questions about Dart/Flutter packages by exploring version-accurate documentation generated from the project's actual dependencies. Use this skill whenever you need to understand a package API — don't rely on training knowledge, as APIs may have changed. This includes implementing features with a third-party package, debugging errors or stack traces involving one, looking up method signatures or class behavior, figuring out how to configure or integrate a package, or migrating/upgrading to a new version. If you're about to call into a package, especially when adopting a new one, use this skill first.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pubdoc-skills:doc-explorerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Answers questions about Dart/Flutter packages by exploring version-accurate documentation generated from the project's actual dependencies.
Answers questions about Dart/Flutter packages by exploring version-accurate documentation generated from the project's actual dependencies.
Run a Dart script at ${CLAUDE_SKILL_DIR}/scripts/prepare_documentation.dart to get the documentation locations for the packages you want to explore. Note that you must know the canonical package names. The script's usage is:
prepare_documentation.dart --project <path/to/dart/project/root> <package-name1> <package-name2> ...
IMPORTANT: Make sure to specify the path to the Dart/Flutter project root, which contains the pubspec.yaml file.
Then, read the JSON output:
{
"packages": {
"dio": {
"documentation": "/Users/you/.pubdoc/cache/dio/dio-5.3.x"
}
},
"error": null
}
IMPORTANT: If the script ends with an error, stop and ask the user how to proceed, rather than attempting to debug or recover on your own.
Spawn a subagent to delegate the exploration:
documentation paths from step 1If you can use a built-in read-only agent optimized for searching and analyzing codebases (e.g., Explore agent), use it here. If you cannot spawn a subagent, read and follow agents/doc-explorer.md yourself.
Always use this prompt template:
Read the package documentation and answer the query:
- Documentation: <documentation-path>
- Query: <describe what you want to know about the package>
Read and follow this for additional instructions: ${CLAUDE_SKILL_DIR}/agents/doc-explorer.md.
Wait for the findings, then use them to proceed with your task.
Rely on the subagent's findings — do not read the documentation yourself unless the subagent's report is insufficient and further reading is clearly needed.
npx claudepluginhub fujidaiti/claude-plugin-marketplace --plugin pubdoc-skillsGenerates on-demand API documentation for Swift package dependencies by extracting symbols from Xcode DerivedData using interfazzle. Useful for unfamiliar imports, dependency API exploration, or queries like "what's import X?".
Forces Claude to web-search and read current official documentation before implementing, integrating, or debugging third-party APIs, libraries, frameworks, and services when latest behavior or correctness matters.
Fetches current library documentation via Context7 REST API for npm/PyPI packages. Use when the user needs official APIs, code examples, or migration guidance.