skills.rest
jecg2804
jecg2804COMMUNITY
Explore all skills by this author →
GitHub

iconsa-library-docs-check

Verifies external library APIs against current Context7 documentation before writing code.

Updated May 7, 2026
Search Tags:#documentation#supabase#next.js#breaking changes#dependency check#context7#api verification
One-click install
npx skills add https://github.com/jecg2804/HumanOS --skill iconsa-library-docs-check-jecg2804
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: iconsa-library-docs-check
Source: https://github.com/jecg2804/HumanOS/tree/main/.claude/skills/iconsa-library-docs-check
Command: npx skills add https://github.com/jecg2804/HumanOS --skill iconsa-library-docs-check-jecg2804

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Training data has knowledge cutoffs, so AI-generated code often uses deprecated or changed APIs from libraries like Next.js 16, React 19, Tailwind 4, Supabase, and Zod 4, causing build warnings or production breakage. ## Core Features & Use Cases - Pre-implementation verification: Resolves the library via Context7 and fetches current docs before writing any code that imports an external dependency. - Breaking-change awareness: Covers known breaking changes such as Next.js middleware-to-proxy migration, Tailwind 4 CSS-first config, and Zod 4 deprecations. - Workflow integration: Records API changes in docs/CONTEXT.md, creates ADRs for non-trivial decisions, and pins package versions. - Use Case: Before writing a Next.js 16 route handler or Supabase server client, the Skill fetches the latest docs so the generated code matches the current API signatures. ## Quick Start Before implementing any feature that imports Next.js, React, Tailwind, Supabase, Resend, Twilio, Documenso, or Zod, ask the assistant to verify the current API via Context7 first.

Frequently Asked Questions about iconsa-library-docs-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify a library API is current before writing code?▼

Resolve the library name with the Context7 resolve-library-id tool, then fetch topic-specific docs with get-library-docs before writing any code. This ensures the generated code matches the current API rather than outdated training data.

What breaking changes exist in Next.js 16 and Tailwind 4?▼

Next.js 16 renamed middleware.ts to proxy.ts, made Turbopack the default, and requires async params. Tailwind 4 uses CSS-first configuration, removing the need for tailwind.config.js in the base setup.

Does Zod 4 have breaking changes from Zod 3?▼

Yes, Zod 4 deprecates methods like .partial(), .strict(), and .passthrough() that were common in v3. Checking current docs before writing schema validation code avoids using removed APIs.

When can I skip checking library documentation?▼

Skip the check for pure internal project code with no external imports, when you already consulted docs for the same library and topic in the current session, or for trivial usage verified recently in the session.

Why does AI-generated code use deprecated APIs?▼

Model training data has knowledge cutoffs, so patterns from old tutorials and memory may reference APIs that changed in newer releases. Verifying against live documentation prevents build warnings and production breakage.

Related Skills

Explore More Software Engineering Skills→
gkganesh12gkganesh12
1

gk-spec-review

Audit planning documents for gaps, contradictions, and untestable criteria.

Community
Advanced
logo-solutionslogo-solutions

source-driven-development

Detect dependency versions and implement framework code from official documentation.

Official
Advanced
dsonyydsonyy

plan-validating

Validates that implementation plans were correctly executed against git history and automated checks.

Community
Intermediate
Ilenburg1993Ilenburg1993
3

context7-docs-ops

Retrieve external library documentation via Context7 MCP with version-specific details.

Community
Intermediate