←
Patrick Robinson1,085 posts
Patrick Robinson avatar

Patrick Robinson

@onpardev

Husband, dad of 2 boys | AI Whisperer and all things Agents and AI | Founder of onpardev.com and alamoagents.org

◷ Joined July 2025▧ 104 Photos and videos
Patrick Robinson avatar
Patrick Robinson@onpardev·Nov 17

I'd been wondering why I hadn't seen more people referencing scripts in their skills more broadly. I'm a HUGE fan of having the deterministic bits be scripted and the judgment be agentic. Great video, @kentcdodds!

Skills stink because they broke a process that had been working in this industry that has worked for decades. But all is not lost! Let me show you the right way to build skills.

9:58
Cory House avatar
⟳ Patrick Robinson retweeted
Cory House@housecor·Nov 17

If I ask a human for a review, I want a human’s input. If I want an AI’s input, I’ll just run it myself. So, here’s a team rule we just implemented: “If you’re asked to do a code review, you must do a human review.” No AI comments allowed.

Cory House avatar
⟳ Patrick Robinson retweeted
Cory House@housecor·Nov 16

Problem I keep seeing: Teams with one product owner making tickets for 3-10 developers. This doesn’t work anymore. In the age of coding agents, one PO can’t create tickets fast enough to keep developers busy. Code isn’t the bottleneck. Requirements are. Reorgs are coming.

Cory House avatar
⟳ Patrick Robinson retweeted
Cory House@housecor·Nov 15

AI is blurring roles. Developers are operating as product owners. Product owners are doing development. QA is generating automated tests. Prediction: These roles will unify into a “Product Engineer” role that owns the entire app (or a vertical slice of a large app).

Cory House avatar
⟳ Patrick Robinson retweeted
Cory House@housecor·Nov 14

True. If a process *must* be deterministic, then skills are the wrong answer. Write code instead.

I like skills but relying on the markdown ones to get deterministic results isn’t ideal

Cory House avatar
⟳ Patrick Robinson retweeted
Cory House@housecor·Nov 14

Skills are like functions. They do something specific. They accept arguments. They can have one or more outputs. I can invoke them or schedule them. They’re composable (skills can call other skills). I can share them with my team, my company, or the world.

Cory House avatar
⟳ Patrick Robinson retweeted
Cory House@housecor·Nov 13

Nearly every process in the SDLC warrants a custom skill: /create-ticket /fix-bug /implement-ticket /review-code /open-pr /fix-pr-comments If our team repeats a process, a skill means we can standardize, automate, and continually improve the process.

Zach Lloyd avatar
⟳ Patrick Robinson retweeted
Zach Lloyd@zachlloydtweets·Nov 12

My definition of a software factory: A measurable, improvable cloud-based system for scaling coding agents for maximum ROI and productivity across your organization.

Patrick Robinson avatar
Patrick Robinson@onpardev·Nov 12

Shout it for the people in the back! :)

I see tweets that imply setting up a software factory can be done simply with a string of prompts tying together cloud agents. My experience working with a large number of customers is that this is false. Companies start with this approach and then regret it because it doesn’t scale. They want resilient, improvable, low-latency factories that integrate deeply with their existing tools. They also want a high level of configurability and measurement, audit logs, and security guarantees. In short, they want the same level of production quality for their factories as they do for their products, because they are betting on software factories as the future of how they ship those products more quickly.

Cory House avatar
⟳ Patrick Robinson retweeted
Cory House@housecor·Nov 12

> I open a PR > Coworker uses Claude to review. It requests minor changes. > I fix the comments and request review > Coworker takes awhile to respond, then uses Claude to review again. It requests minor changes. This loop has repeated for *two weeks* on a single PR.

Patrick Robinson avatar
Patrick Robinson@onpardev·Nov 11

We're trying to come up with a good name for our new puppy. So far, the kids have said: - Lightning McQueen - Batman - Scooby Doo - Ralph Open to others...

Post attachment
mark avatar
⟳ Patrick Robinson retweeted
mark@markletree·Nov 9

I recently joined @AnthropicAI to work on our platform for production agents. I'm excited to help teams safely take on long-running tasks with thousands of agents working together. If you're building with agents, I'd love to hear from you.

Post attachment
Cory House avatar
⟳ Patrick Robinson retweeted
Cory House@housecor·Nov 11

Realization: Avoid personal skills. They lead to process fragmentation and wide variations in developer productivity. Instead, I strive to share skills across the team. Shared skills benefits: - Solve problems using a consistent process - We can iterate and improve our shared skills over time. - Fosters team-wide learning - Avoids "works on my machine"

Patrick Robinson avatar
Patrick Robinson@onpardev·Nov 11

Some photos from Alamo Agents' first Builders' Night! Had a blast collaborating with great people building some awesome stuff here in San Antonio! Next event is in January!

Post attachmentPost attachment
Patrick Robinson avatar
Patrick Robinson@onpardev·Nov 10

Alamo Agents Builders Night is tonight in San Antonio. Bring a laptop, group up or go solo, and demo what you built. I'll be there the whole time to help. 6 to 7:30 PM at Zelifcam. Free. Details and RSVP: alamoagents.org

0:28