xbxd/pi-config
Pi Workbench
My setup for Pi, the coding agent I use every day. It brings together extensions, skills, keybindings and the little bits of project guidance that make it feel like mine.
Project details
Primary language: TypeScript
Last commit:
Language mix
- TypeScript 81%
- Python 11%
- JavaScript 6%
- Other 2%
Weekly commits
Commit counts by UTC week start for the last 52 weeks.
1047 commits total; busiest week: 2026-07-19 (171 commits).
README
My Pi config
This is the setup I use to make Pi feel like my own coding partner, with the tools, guidance and shortcuts I reach for every day.
What's in here
Most of the setup lives in agent/, alongside the files Pi uses for my agent configuration.
agent/agents/has role instructions for focused tasks like research, review and implementation.agent/APPEND_SYSTEM.mdadds shared guidance to Pi's system instructions.agent/extensions/contains my Pi extensions, including a few small utilities and some larger features kept in their own folders.agent/skills/holds reusable instructions for recurring workflows. Some skills include their own references, scripts, assets or tests.agent/prompts/is for prompts I can call when I want a particular kind of help.agent/docs/keeps notes and guidance for maintaining parts of the setup.agent/packages/contains local Pi packages and their code, tests and examples.agent/tests/covers configuration rules, skills, extensions and helper scripts.agent/scripts/has small maintenance and validation tools.agent/settings.template.jsonis a starting point for Pi settings.agent/keybindings.jsonholds my keyboard shortcuts.agent/models.jsonkeeps model configuration separate.agent/mcp-servers.jsonis another piece of the agent configuration..agents/skills/contains a skill kept at the repository level.mise.tomllists a development tool used by the repo.
How I use it
This is the working setup behind my day-to-day Pi sessions. Extensions add small bits of behavior, skills give Pi reusable context for specific jobs, and the role files help me hand off focused tasks. The keybindings keep common actions close at hand.
I use skills for repeatable workflows and roles when I want to delegate a task with a clear focus. The local packages let me keep a few Pi-specific pieces alongside the rest of the setup.
When I update something, I keep its supporting notes or tests close to it where that makes sense. That makes the collection easier for me to maintain as it grows.
I change the setup as I find something worth keeping, then use the tests and validation scripts to catch mistakes. It's a working collection, so it grows and changes with how I use Pi.
Notes
This is a personal configuration, not a general-purpose starter kit. Pick the parts that suit how you work.