Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By mattrobenolt
Zig development toolkit — writing, reviewing, and Tiger Style compliance for Zig 0.15 projects
npx claudepluginhub mattrobenolt/pi-configs --plugin zigTigerBeetle's coding style guide for writing safe, performant Zig code. Enforces strict safety rules (assertions, bounded control flow, static memory), performance discipline (mechanical sympathy, batching), and naming/formatting conventions. Use this skill when: (1) Writing or generating Zig code — apply Tiger Style rules during generation, (2) Reviewing Zig code — run a detailed review against all Tiger Style principles, (3) User asks about Tiger Style conventions, naming, assertions, or formatting. Triggers on: writing Zig code, code review requests, style questions, "tiger style", "tiger review".
Write correct, idiomatic Zig 0.15 code. Use when writing new Zig code, editing existing Zig files, debugging Zig compilation errors, reviewing Zig code, or working with build.zig files. Triggers on any task involving .zig files. Critical: LLM training data contains outdated Zig patterns (0.11-0.13) that will produce broken code — this skill provides the current 0.15 patterns.
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Access thousands of AI prompts and skills directly in your AI coding assistant. Search prompts, discover skills, save your own, and improve prompts with AI.
Complete developer toolkit for Claude Code
Orchestrate multi-agent teams for parallel code review, hypothesis-driven debugging, and coordinated feature development using Claude Code's Agent Teams
Intelligent draw.io diagramming plugin with AI-powered diagram generation, multi-platform embedding (GitHub, Confluence, Azure DevOps, Notion, Teams, Harness), conditional formatting, live data binding, and MCP server integration for programmatic diagram creation and management.
Comprehensive .NET development skills for modern C#, ASP.NET, MAUI, Blazor, Aspire, EF Core, Native AOT, testing, security, performance optimization, CI/CD, and cloud-native applications
Unity Development Toolkit - Expert agents for scripting/refactoring/optimization, script templates, and Agent Skills for Unity C# development
Opinionated LSP configurations for Go, Zig, Python, Nix, Rust, Ruby, and YAML
Personal pi configuration. Extensions, agents, skills, and themes that shape how I work with AI day-to-day.
This is an evolving workbench — some things are battle-tested, some are experimental, some exist because they seemed interesting and haven't been fully evaluated yet.
extensions/ Pi-only TypeScript extensions: tools, UI, hooks, and session behavior
agents/ Pi subagent definitions loaded by the subagent package/tool
skills/ Loose pi-local skills and compatibility adapters
plugins/ Claude Code plugin bundles exposed through the local marketplace
packages/ Local package/fork code and workspace packages
scripts/ Repo-local automation and eval helpers
themes/ Color themes
The portability boundary is intentional:
plugins/. A plugin may contain skills, slash commands, agents, LSP settings, MCP config, or other Claude Code plugin metadata.extensions/. These files call the pi extension API directly and are not portable to Claude Code or Codex without being rewritten as MCP tools, CLIs, or skills.packages/. If it has its own package.json, tests, changelog, README, and source tree, it does not belong at the repo root.skills/. If a skill belongs to a shareable domain such as Zig, the plugin copy is canonical and the root skill should be a pi compatibility adapter.Extensions are loaded automatically from the extensions/ directory on session start.
| Extension | What it does |
|---|---|
answer.ts | /answer command and Ctrl+. shortcut — presents an interactive TUI for answering questions extracted from the last assistant message |
btw.ts | /btw — floating side-chat overlay for tangential questions without polluting the main session |
compaction-model.ts | Uses a local llamacpp model for compaction when the active model is local |
cost.ts | /cost [days] — token usage summary broken down by date, project, and model |
cwd.ts | /cd command plus CWD-aware path handling for bash/read/write/edit/grep/find/ls, with zoxide support |
direnv.ts | Loads direnv environments for the current working directory and reports blocked/error status in the footer |
execute-command.ts | execute_command tool — lets the agent queue a slash command or message to fire after its current turn ends |
notion.ts | NotionRead and NotionSearch tools — read/search Notion using NOTION_TOKEN or the local macOS Notion app token |
notify.ts | Sends a native desktop notification (OSC 777) when the agent finishes a turn — requires Ghostty with desktop-notifications = true |
prompt-editor.ts | Named "modes" for model + thinking combinations — cycle with Ctrl+Space, pick with /mode or Ctrl+Shift+M |
setup.ts | Session defaults: activates grep, find, ls; auto-expands tool outputs; registers get_system_prompt, get_tools, get_last_payload introspection tools |
statusline.ts | Footer showing repo/directory, branch, dirty state, current time, extension statuses, model, thinking level, and token usage |
temporal-context.ts | Injects hidden temporal context only after long pauses, currently gaps of 30+ minutes between user/assistant messages |
webfetch.ts | webfetch and websearch tools — GitHub-URL-aware fetching and Exa-powered web search |
whimsical.ts | Animated loading messages with shimmer effect. Purely cosmetic. |
Custom agent definitions invoked as subagents via the subagent tool/package.
General purpose: