بنقرة واحدة
docs-lookup
Look up official Astro documentation and answer version-sensitive Astro questions accurately.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Look up official Astro documentation and answer version-sensitive Astro questions accurately.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Add and configure Astro integrations, adapters, and UI framework tooling.
Set up and evolve Astro content collections with typed schemas and reliable querying patterns.
Plan and execute migrations to Astro or between Astro versions with minimal regressions.
Apply performant, accessible, and maintainable defaults when building or reviewing Astro projects.
Create Astro components, pages, and layouts with accessible markup and minimal client-side JavaScript.
| name | docs-lookup |
| description | Look up official Astro documentation and answer version-sensitive Astro questions accurately. |
Use this skill when answering Astro questions that depend on current documentation, exact API names, integration setup, upgrade paths, or version-sensitive behavior.
Reduce the request to a specific topic before searching:
If the user includes an error message, search that message directly as part of the lookup.
Start with the official Astro documentation and related official references. If the agent has Astro docs tooling or an MCP available, use it. If not, search the official docs site directly.
Avoid relying on blog posts or community snippets when the question is about syntax, configuration, or breaking changes.
Use specific search terms, not broad ones:
content collections schemaview transitionsnetlify adapter output serverupgrade guideWhen version drift is possible, verify the current version behavior instead of assuming older examples still apply.
When replying:
Try one of these before giving up:
A good answer usually includes:
If you cannot verify the behavior from current official docs, say so explicitly instead of guessing.