Opinionated and Easy Pi.dev Configuration

This seems to be like the antithesis of pi, it's supposed to be this minimal thing you customise

I guess it's the same kinda friction with vanilla vim/neovim vs vim 'distributions' that provide a bunch of stuff out of the box.

Currently using Oh My Pi (https://github.com/can1357/oh-my-pi) and appreciate the batteries included approach.

From my limited time using pure Pi, I found quite a few of the plugins lacking and had no desire to upgrade/fix and maintain them myself. I know others feel differently though.

I like the idea of keep Pi minimal but having “official”, high quality optional plugins to make it more usable.

Pi makes you think about what you’re doing with it on purpose. This defeats that, as the Mario quote on the page says, and therefore isn’t worth using.

People really need to try out “less is more”. The new models are quite smart, so suffocating their context with dozens of MCPs and skills isn’t necessary like it used to be. A cli tool with good built in help and good errors is amazingly easy for the model to figure out.

If Pi is too minimal for you and you don’t want to dig into it, OpenCode is pretty good out of the box. I use it for general work I haven’t setup Pi for. The only thing I add to OpenCode is some commands that are shortcuts to save me typing frequent prompts, and a subagent with a fixed model for implementing changes.

What AGENTS.md and skills are people relying on these days?

I have little to none and am successful building full stack Go apps Claude Code, Codex, and Shelley which covers the spectrum of crazy black box to simple `bash` clanker.

It makes me think the models are continually improving in knowing what to do on their own.

I do put some major work into the classic "Developer Experience" (DX) of my code base. Standard Go tooling, idiomatic Go, well designed initial test harnesses, GitHub actions that enforce some linting.

I think that works better than any markdown instructions ever will.

This thing defeats the whole purpose of Pi.

I've been using oh-my-pi for a while and I'm very happy with it. If you're not going to build out your own Pi setup I'm not sure why you'd pick this over oh-my-pi.

I like peeping at other people's skills but it is unclear to me what/where the claimed 60+ skills are actually located. Compound Engineering conveys a few but nowhere near 60.

"One command installs 60+ community skills, 67 themes, MCP support, sub-agent support, Claude Code CLI provider support, memory, and more."

What, no kitchen sink?

On the one hand, sure, why not have a default install throw a bunch of bells+whistles via skills and extensions.

But I like pi precisely because it is so minimal. I want understand and work around the simplest possible agentic coding setup, find the sharp edges, maybe even improve my prompting ability. And doing all three with a locally hosted LLM.

At some point, if I don't understand the foundations, am I just punting on actually thinking about what I'm doing?

Of course, making individual choices about how to do agentic coding are precisely just making individual choices. People should do what makes them happy and productive.

I think the developers of Pi made a supply chain mistake by stripping down the core agent and requiring features like subagents to load plugins written by some random person.

haha i was waiting for this exact thing lazyvim:vim::pi:lazypi, thanks for sharing

i think to fall in love with Pi, bundled skills are a bit antithetical - you realistically only need a couple of skills that you maybe design yourself

Why does this makes more sense over OpenCode?