Grounding with Live Docs Playbook
This skill instructs the agent to fetch external or official documentation from official websites or repositories before implementing database schemas, APIs, or libraries. This prevents using outdated schemas or hallucinating options/parameters.
Target Triggers
/grill-with-docs"ground with latest schema""ground with docs"
Operational Steps
When executing tasks requiring database configuration, caching integration, or third-party APIs:
1. Identify Target APIs/Libraries
- Determine the library versions or service endpoints (e.g., Redis, PostgreSQL, Prisma, Stripe, Firebase, AWS SDK, Next.js).
- Pinpoint specific commands, functions, or schemas that need to be implemented.
2. Fetch Documentation Live
- Do not rely entirely on internal model memory if there is ambiguity or a recent version change.
- Use
search_web to locate official guides or API docs.
- Use
read_url_content or read_browser_page to fetch and parse the target doc page.
- Look specifically for syntax changes, deprecated options, error schemas, and configuration requirements.
3. Verify Database/Service Schema Compatibility
- Check that fields, types, and constraints match exactly what the service/database expects.
- Ground database queries against actual schemas defined in migration files, schemas (e.g.,
schema.prisma, SQL init files), or live database inspect outputs.
4. Implement Grounded Code
- Write the schema, configuration, or API caller logic based on the extracted rules.
- Document any specific assumptions or external links inside the codebase for developers.
1---2name: grill-with-docs3description: Forces grounding using live documentation (Redis, Postgres, external API docs, frameworks) fetched via curl or web search before generating integration code or database schemas.4---5# Grounding with Live Docs Playbook67This skill instructs the agent to fetch external or official documentation from official websites or repositories before implementing database schemas, APIs, or libraries. This prevents using outdated schemas or hallucinating options/parameters.89## Target Triggers10- `/grill-with-docs`11- `"ground with latest schema"`12- `"ground with docs"`1314## Operational Steps1516When executing tasks requiring database configuration, caching integration, or third-party APIs:1718### 1. Identify Target APIs/Libraries19- Determine the library versions or service endpoints (e.g., Redis, PostgreSQL, Prisma, Stripe, Firebase, AWS SDK, Next.js).20- Pinpoint specific commands, functions, or schemas that need to be implemented.2122### 2. Fetch Documentation Live23- Do not rely entirely on internal model memory if there is ambiguity or a recent version change.24- Use `search_web` to locate official guides or API docs.25- Use `read_url_content` or `read_browser_page` to fetch and parse the target doc page.26- Look specifically for syntax changes, deprecated options, error schemas, and configuration requirements.2728### 3. Verify Database/Service Schema Compatibility29- Check that fields, types, and constraints match exactly what the service/database expects.30- Ground database queries against actual schemas defined in migration files, schemas (e.g., `schema.prisma`, SQL init files), or live database inspect outputs.3132### 4. Implement Grounded Code33- Write the schema, configuration, or API caller logic based on the extracted rules.34- Document any specific assumptions or external links inside the codebase for developers.
AravindS-Wick