add-neon-docs
Use this skill when the user asks to add documentation, add docs, add references, or install documentation about Neon. Adds Neon best practices reference links to project AI documentation (CLAUDE.md, AGENTS.md, or Cursor rules). Does not install packages or modify code.
Best use case
add-neon-docs is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use this skill when the user asks to add documentation, add docs, add references, or install documentation about Neon. Adds Neon best practices reference links to project AI documentation (CLAUDE.md, AGENTS.md, or Cursor rules). Does not install packages or modify code.
Teams using add-neon-docs should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/add-neon-docs/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How add-neon-docs Compares
| Feature / Agent | add-neon-docs | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use this skill when the user asks to add documentation, add docs, add references, or install documentation about Neon. Adds Neon best practices reference links to project AI documentation (CLAUDE.md, AGENTS.md, or Cursor rules). Does not install packages or modify code.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Add Neon Knowledge References to Project
This skill adds reference links to Neon documentation and best practices in your project's AI documentation file, enabling AI assistants to quickly access Neon-specific patterns and guidelines without cluttering your project with large documentation files.
## How It Works
This skill follows a simple workflow:
1. **Load metadata** - Read skill information from `skill-knowledge-map.json`
2. **Detect documentation file** - Find `CLAUDE.md`, `AGENTS.md`, or Cursor rules files
3. **Ask permission** - Show what will be added and where
4. **Add references** - Insert URLs in a "Resources & References" section
5. **Report completion** - Confirm successful installation
For detailed workflow steps, see `install-knowledge.md`.
## Parameters
### SKILL_NAME Parameter
Optional. Specifies which skill documentation to install (e.g., `"neon-drizzle"`). If not provided, you'll be prompted to choose from available skills defined in `skill-knowledge-map.json`.
## Usage Examples
**Called from another skill:**
```markdown
Execute the add-neon-docs skill with SKILL_NAME="neon-drizzle"
```
**Called directly by user:**
- "Add neon drizzle knowledge to my project"
- "Install neon serverless documentation"
- "Set up Neon best practices for my AI assistant"
## What Gets Added
References are added to a "Resources & References" section in your AI documentation file:
```markdown
## Resources & References
- **Neon and Drizzle ORM best practices**: https://raw.githubusercontent.com/neondatabase-labs/ai-rules/main/neon-drizzle.mdc
- **Serverless connection patterns**: https://raw.githubusercontent.com/neondatabase-labs/ai-rules/main/neon-serverless.mdc
```
### Target Files (in priority order):
- `CLAUDE.md` - Most common for Claude Code projects
- `AGENTS.md` - Custom AI documentation files
- `.cursor/README.md` or `.cursor/rules.md` - Cursor IDE projects
- Creates `CLAUDE.md` if none exist
### Behavior:
- Existing "Resources & References" sections: New links are appended
- No existing section: Section is created at end of file
- No documentation file: `CLAUDE.md` is created with references
## Related Skills
- **neon-drizzle** - Sets up Drizzle ORM, then offers this skill
- **neon-serverless** - Sets up connections, then offers this skill
- **neon-toolkit** - Sets up ephemeral databases, then offers this skill
## Workflow Reference
For complete implementation details:
- **Workflow**: `install-knowledge.md` - Step-by-step agent workflow with error handling
- **Metadata**: `skill-knowledge-map.json` - Skill definitions and reference URLs
---
## Workflow Implementation
Now I'll execute the installation workflow for you.
**Parameter received**: SKILL_NAME = ${SKILL_NAME || "not provided - will ask user"}
Execute `install-knowledge.md` with the specified SKILL_NAME.Related Skills
crawl-docs-skill
Run a Crawl4AI-based doc crawler and save internal pages as Markdown using page titles as filenames. Use when the user provides a docs URL and wants all internal subpages saved as .md files. Environment setup should only use uv.
coder-docs
Index + offline snapshot of coder/coder documentation (progressive disclosure).
cgr-docs-governance
Use this skill when updating project documentation after backend/frontend operational changes, incidents, workflow behavior changes, or new runbooks.
athlete-docs
Documentation guidance for competition athletes and volunteers in WODsmith. Use when writing, reviewing, or improving athlete-facing documentation including registration, scheduling, workout viewing, leaderboards, check-in, and volunteer coordination.
assistant-ui-docs
Extra documentation for `assistant-ui`. Use this to find offline resources about `assistant-ui`.
api-docs
Expert API documentation including OpenAPI specs, endpoint documentation, and SDK guides
anydocs
Generic Documentation Indexing & Search. Index any documentation site (SPA/static) and search it instantly.
ancplua-docs
Search and answer questions about the ANcpLua ecosystem documentation. Use when users ask about ANcpLua.NET.Sdk features, ANcpLua.Analyzers rules, ANcpLua.Roslyn.Utilities APIs, or any configuration/usage questions about these packages.
agentic-docs
Write clear, plain-spoken code comments and documentation that lives alongside the code. Use when writing or reviewing code that needs inline documentation like file headers, function docs, architectural decisions, or explanatory comments. Works well for both human readers and AI coding assistants who see one file at a time.
agent-ops-mkdocs
MkDocs documentation site management: initializing, updating, building, and deploying
agent-ops-docs
Documentation management for README, CHANGELOG, API docs, and user-facing documentation. Use when creating or updating project documentation.
agent-ops-create-technical-docs
Create focused, specific technical documentation for codebase sections. Analyzes code, identifies topics, presents options before writing. Supports code blocks with line numbers.