A plugin and skill list for a working agent

1. The rule

A good prompt helps once. A good skill turns behavior into a habit.

• If you're writing the same explanation again, it's a skill candidate.
• If the agent forgets how to work, you're missing a work contract.
• If every run looks different, you're missing a process that forces verification.
• If the tool adds noise, it's not a good plugin for you.

2. Superpowers

The first plugin I install when I want an agent to work through a process, not improvise.

• Forces thinking before execution.
• Helps break work into steps.
• Keeps a plan, execute, verify loop.
• Fits code, content, research and recurring improvement tasks.

When to use it:
- The task is unclear.
- You need a plan before editing.
- You need to pass through verification before "done".
- There are several files or several decisions.

3. Caveman

When an agent starts writing speeches instead of delivering work, cut its language down.

• Strips filler and long-winded talk.
• Leaves output short, direct and precise.
• Especially good for long work sessions.
• Helps you see real status without a layer of politeness.

4. Ponytail

This is the skill that reminds the agent not to build a factory for one screw.

• Checks whether you need to build anything at all.
• Prefers existing code, a standard, or an existing platform.
• Prevents premature abstractions.
• Fits small fixes and features that can stay simple.

5. Frontend Design

When the result looks like a generic dashboard, this is the skill that raises the bar.

• Connects design to the audience and the real use case.
• Forces hierarchy, density, interface states and flow.
• Prevents marketing pages when what's needed is a working tool.
• Good for any UI the user is meant to work in over and over.

6. Design Review

Not every bug is code. Sometimes the problem is truncated text, a button that's invisible, or a screen that doesn't work on mobile.

• Checks a screenshot before you publish.
• Looks for overlaps, broken hierarchy, contrast and readability.
• Separates 'looks nice' from 'works for the user'.
• Good before you show a client or publish a post.

7. Fullstack Eval

'It works on my machine' is not enough. You need a real check against the screen and the system.

• Defines a sprint contract before code.
• Opens a browser and checks the live experience.
• Looks for gaps between code, data, interface and the promise.
• Especially good for features that meet a user.

8. How to choose what to install first

• Starting from improvisation? Install Superpowers.
• Output too long? Install Caveman.
• Agent building too much? Install Ponytail.
• Interface looks generic? Install Frontend Design, then Design Review.
• Feature needs live proof? Install Fullstack Eval.

9. A short work template

Before the task:
- Which skill keeps the way of working intact?
- What counts as done?
- What check proves it worked?
- What is the agent not allowed to do without approval?
- What comes back to me at the end?