Development: Documentation building and serving with MkDocs Material. Builds HTML documentation from markdown sources with auto-reload for development. Run from repository root with 'just docs-build' or 'just docs-serve'. Use when developers need to build or preview docs.
/plugin marketplace add atrawog/bazzite-ai-plugins/plugin install atrawog-bazzite-ai-dev-bazzite-ai-dev@atrawog/bazzite-ai-pluginsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
The docs development commands build and serve the bazzite-ai documentation using MkDocs Material. It supports live preview with auto-reload for efficient documentation development.
Key Concept: This is a development command - run with just from the repository root, not ujust. Documentation is built during CI/CD and deployed to GitHub Pages automatically.
| Action | Command | Description |
|---|---|---|
| Install deps | just docs-install | Install pixi dependencies |
| Build docs | just docs-build | Build HTML documentation |
| Serve locally | just docs-serve | Serve with auto-reload |
| Full rebuild | just docs-rebuild | Clean + build |
Installs Python dependencies via pixi:
just docs-install
Requirements: pixi must be installed (curl -fsSL https://pixi.sh/install.sh | bash)
Builds HTML documentation:
just docs-build
Output: docs/_build/html/
Serves documentation locally with auto-reload:
just docs-serve
Press Ctrl+C to stop the server.
Full rebuild (clean + build):
just docs-rebuild
| Tool | Purpose |
|---|---|
| MkDocs Material | Static site generator |
| pixi | Python environment management |
| MyST Markdown | Extended markdown syntax |
# 1. Install dependencies
just docs-install
# 2. Start development server
just docs-serve
# 3. Open browser
# http://localhost:3000
# 1. Start server (auto-reloads on changes)
just docs-serve
# 2. Edit markdown files in docs/
# 3. Browser auto-refreshes
# 4. When done, build for verification
just docs-build
# Build docs before committing
just docs-build
# Verify no broken links or errors in output
docs/
├── index.md # Home page
├── os/ # OS documentation
├── pods/ # Pod documentation
├── development/ # Development docs
├── hooks/ # MkDocs hooks
│ ├── skills_generator.py # Skills auto-generation
│ └── r2_asset_rewriter.py # Asset handling
└── _build/ # Build output (gitignored)
└── html/ # HTML output
| File | Purpose |
|---|---|
mkdocs.yml | MkDocs configuration |
pixi.toml | Python dependencies |
docs/hooks/*.py | Custom MkDocs hooks |
The documentation includes auto-generated content:
plugins/*/skills/*/SKILL.mdSymptom: pixi: command not found
Fix:
# Install pixi
curl -fsSL https://pixi.sh/install.sh | bash
# Add to PATH
source ~/.bashrc
Symptom: Python import errors
Fix:
# Reinstall dependencies
just docs-install
Symptom: Port already in use
Fix:
# Find process using port 3000
lsof -i :3000
# Kill it
kill <PID>
# Or use different port (edit pixi.toml)
Symptom: Build warnings about broken links
Fix:
# Check build output for specific files
just docs-build 2>&1 | grep -i "warning"
# Fix the referenced files
Documentation is automatically built and deployed:
testing branch → Preview at testing.bazzite-ai.pages.devmain → Deploy to bazzite-ai.pages.devWorkflow: .github/workflows/docs.yml
lint (validate markdown), clean (clean build output)mkdocs.yml, pixi.tomlUse when the user asks about:
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.