菜单
Fetch up-to-date library documentation using Context7 API. Use this skill when the user asks for docs, examples, or help with a specific library/framework (e.g., "look up React docs", "context7 nextjs routing", "fetch docs for fastapi").
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Full-stack Python framework for interactive web apps. Server-driven React UI with WebSocket sync. This skill should be used when building Pulse applications, components, state management, data fetching, routing, forms, or real-time features.
Python bindings for Mantine React components. Wraps all @mantine/core components plus forms, dates, and charts packages. Use when building UI with Pulse Mantine components, adapting Mantine docs to Python, or working with MantineForm validation.
Railway deployment utilities for Pulse applications. Use this skill when deploying Pulse apps with pulse-railway, configuring RailwayPlugin or RailwaySessionStore, running pulse-railway scaffold/ensure/deploy/redeploy/remove, migrating from pulse-aws to Railway, or debugging Railway router/session/deployment affinity behavior.
AWS deployment utilities for Pulse applications on ECS Fargate. Use this skill when deploying Pulse apps with pulse-aws, configuring AWSECSPlugin, tuning ECS task settings or health checks, or wiring a repo-specific deploy wrapper around the current pulse-aws CLI and rollout model.
Python bindings for Mantine React components. Wraps all @mantine/core components plus forms, dates, and charts packages. Use when building UI with Pulse Mantine components, adapting Mantine docs to Python, or working with MantineForm validation.
| name | context7 |
| description | Fetch up-to-date library documentation using Context7 API. Use this skill when the user asks for docs, examples, or help with a specific library/framework (e.g., "look up React docs", "context7 nextjs routing", "fetch docs for fastapi"). |
| allowed-tools | WebFetch |
This skill fetches up-to-date documentation and code examples from libraries using the Context7 API.
Context7 requires a two-step process:
First, search for the library to get its ID:
GET https://context7.com/api/v2/libs/search?libraryName=<library>&query=<context>
Parameters:
libraryName: The library name (e.g., "react", "nextjs", "fastapi")query: Search context to help find the right libraryThe response contains a results array with library objects. Use the id field from the first result.
Use the library ID to fetch relevant documentation:
GET https://context7.com/api/v2/context?libraryId=<id>&query=<question>
Parameters:
libraryId: The ID from step 1 (e.g., "/vercel/next.js")query: Natural language question about the documentationThis returns ranked code snippets and documentation matching your query.
When the user asks about a library:
Search for the library: Use WebFetch to call:
https://context7.com/api/v2/libs/search?libraryName=nextjs&query=routing
Extract the library ID from the response (e.g., "/vercel/next.js")
Fetch documentation: Use WebFetch to call:
https://context7.com/api/v2/context?libraryId=/vercel/next.js&query=How to setup dynamic routes
Present the results to the user with the relevant code examples and documentation.
| Status | Meaning | Action |
|---|---|---|
| 200 | Success | Process and present results |
| 202 | Processing | Library still indexing; inform user to try later |
| 301 | Redirect | Use the redirectUrl from response |
| 429 | Rate Limited | Inform user about rate limit; suggest waiting |
| 404 | Not Found | Library doesn't exist; suggest alternative search |