bundles/content/skills/nextra-writer/SKILL.md
Expert in creating clear, comprehensive technical documentation with Nextra (Next.js-based docs framework), MDX, and modern documentation patterns. Use for documentation sites that need Next.js integration.
npx skillsauth add shipshitdev/library nextra-writerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Expert technical writer for creating documentation using Nextra, the Next.js-based documentation framework.
Why Nextra: Next.js integration, fast builds, automatic routing, full-text search, dark mode, and MDX support out of the box.
| Technology | Version | |------------|---------| | Nextra | 3.x | | Next.js | 14.x / 15.x | | React | 18.x / 19.x | | TypeScript | 5.x | | MDX | 3.x |
# Create new Nextra docs
bun create next-app docs --example nextra-docs-template
# Or add to existing Next.js project
bun add nextra nextra-theme-docs
docs/
├── pages/
│ ├── _meta.json # Navigation config
│ ├── index.mdx # Home page
│ ├── getting-started.mdx
│ └── api/
│ ├── _meta.json
│ └── endpoints.mdx
├── theme.config.tsx # Theme configuration
├── next.config.mjs # Next.js + Nextra config
└── package.json
Configure via _meta.json:
{
"index": "Introduction",
"getting-started": "Getting Started",
"---": {
"type": "separator"
},
"api": "API Reference"
}
| Feature | Pattern |
|---------|---------|
| Callouts | <Callout type="info"> |
| Tabs | <Tabs items={['npm', 'yarn']}> |
| Cards | <Cards> component |
| Steps | <Steps> component |
| File Tree | <FileTree> component |
| Skill | When to Use |
|-------|-------------|
| docs | General technical writing |
| api-design-expert | API documentation structure |
| frontend-design | Custom documentation UI |
For detailed configuration, MDX patterns, and component examples: references/full-guide.md
development
Coordinates a weekly engineering review of board accuracy, recent code changes, operational health, and scoped cleanup. Use for a recurring repository health review or a review of the last several days.
testing
Audits project board configuration and prepares explicitly requested setup, copy, or normalization changes while preserving the existing workflow and provider boundaries. Use when inspecting a board's fields, columns, scope, or configuration.
testing
Reconciles a project board with current work and delivery evidence, reports incomplete coverage and metadata gaps, and applies only approved provider-supported field changes. Use when auditing board drift, reviewing blocked work, or assessing upcoming delivery.
development
Walk through how a subsystem works. Use for "how does X work", code walkthroughs before changing something, and placement or ownership questions. Explains architecture, runtime flow, and onboarding mental models. Can critique architecture. Use why for motivation.