Awesome-omni-skill context7

Context7 MCP usage patterns for framework documentation lookups

install

source · Clone the upstream repo

git clone https://github.com/diegosouzapw/awesome-omni-skill

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skill "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/development/context7-george-popescu" ~/.claude/skills/diegosouzapw-awesome-omni-skill-context7-566fb4 && rm -rf "$T"

manifest: skills/development/context7-george-popescu/SKILL.md

source content

Context7 Integration

When to Use

Use Context7 MCP to fetch up-to-date framework documentation in three contexts:

During research (plan-phase Step 2): fetch relevant framework docs per task to populate research notes
During implementation (execute-phase): look up specific API details when building features
During review/fixing: verify patterns match the current framework version before flagging issues

How to Use

Two-step process for every lookup:

Resolve the library ID: Call
```
mcp__context7__resolve-library-id
```
with the library name (e.g.,
```
laravel/framework
```
). This returns the correct Context7 identifier.
Query the docs: Call
```
mcp__context7__query-docs
```
with the resolved ID and a specific query string.

Rules:

Always use specific queries: "Inertia useForm validation display" -- not "Inertia docs"
One concept per query. Do not combine unrelated lookups.
Do not re-fetch the same documentation multiple times in one session. Cache results mentally and reuse them.

Library IDs Per Stack

Stack	Libraries to Query
laravel-inertia-vue	`laravel/framework` , `inertiajs/inertia` , `vuejs/core`
laravel-inertia-react	`laravel/framework` , `inertiajs/inertia` , `facebook/react`
react	`facebook/react`
nextjs	`vercel/next.js`
nestjs	`nestjs/nest`
react-native-expo	`facebook/react-native` , `expo/expo`

Read

config.json

to determine the project stack, then query only the relevant libraries from this table.

Graceful Fallback

Context7 enhances research but is never required. Follow this three-tier check:

Check config: Read
```
config.json
```
for the
```
"context7"
```
field. If
```
false
```
, skip Context7 entirely.
Attempt the call: If enabled, call the MCP tools. If the tools are not available (error, not configured), fall back to codebase analysis.
Log and proceed: When falling back, note "Context7 not available, using codebase patterns only" and continue. Never hard-fail because Context7 is unavailable.

Query Strategies

Keep queries focused and practical:

Component patterns: Query component API and composition patterns (e.g., "Vue defineModel two-way binding")
API details: Query function signatures and configuration options (e.g., "Laravel FormRequest authorize method")
Testing: Query testing utilities and patterns (e.g., "Pest assertInertia page component")
Configuration: Query setup and configuration options (e.g., "Inertia shared data middleware")
Migrations/models: Query schema and relationship patterns (e.g., "Laravel belongsToMany pivot table")

Prefer specific framework features over general queries. A targeted query returns more useful context than a broad one.

If a query returns no useful results, refine it with more specific terms rather than broadening it.