ryanthedev

lol wait until self driving becomes popular.

Those will be fun times.

> These release notes are painstakingly and lovingly hand-crafted by human Ghostty maintainers

Artisan call out work starts. The hipster stance in the AI world.

If you ever need a home. I built it mainly for me and all the stuff that I work on.

https://upubli.sh/

Very nice collection. Enjoyed the history lesson as well.

I think the eye roll is the need to shout that you don’t use AI.

It’s the new web dev, imo.

This post wasn’t about sparking conversation. It’s about using AI makes me lose the human touch in what I do, blah blah, heard it all before.

Sorry, not sorry.

You can also do this cross computer. It’s how I debug problems.

I actually built a memory system off git. https://github.com/ryanthedev/grug-brain.mcp

Finally some sanity when it comes to AI.

You must be new to skill creation.

Your hand rolling skills? You know they created a thing called a skill creator…

I wrote a skill for this! But I’m sure a lot of you have as well lol.

For those curious https://github.com/ryanthedev/oberskills/blob/main/commands/...

I believe most detailed prompts are AI generated.

> The older I get, the more I appreciate dynamic languages. Fuck, I said it. Fight me.

Ahh, I tend to find software based engineering skills and workflows as the agentic engineering patterns.

I distilled multiple software books into these flows and skills. With more books to come.

Here is an example https://github.com/ryanthedev/code-foundations

You haven’t heard of spec driven development?!? Haha.

CLIs are dead. Long live the skill. Which is a wrapper around the CLI! Haha.

Love the article and happy to have a framework but I don’t think those are good SWE skills.

I imagine some more like. https://github.com/ryanthedev/code-foundations

Based of an actual software book.

I created my own Claude skill to enforce this and be sure it weaves in all the best practices we learned.

https://github.com/ryanthedev/code-foundations

I’m currently working on a checklist and profile based code review system.

Skills? Money?

doh! I messed up. Thank you

turtle, turtle...

It's really going to be interesting to see how this tech evolves.

FUCKING AI HAHAHA, thank you! fixed.

ohhh! I'm gonna have to try that out. Thankfully everybody is still playing nice hahah!

Ahhhh. I see now.

Now that you mention it, i can see a future where claude may offer a "skills" feature and codex offers a "talent" feature. where they are essentially the same things, but specific to that vendor.

reminds me how each cloud has the same offerings but different products.

1000000% agree. That's a problem I'm working on right now. I did learn about hooks, which is a way to constantly remind it. But that's too generic.

At some point I plan to do some ralph wiggum loop stuff maybe to hash out the best way for triggers to work.

i see it as skills being logical grouping of a set of prompts, which achieve a goal. Like my optimize-critical-path skill.

It's more than a single prompt, but less than an entire agent. I find skills to be the tools you use on the fly. Like how I might have a wrench,screw-driver, hammer in my tool box.

tools vs skills is all about context efficiency from what I see. and yes, this isn't novel of claude. but they are the first to offer this abstraction.

No need to be sorry! That's why I posted this.

That's what I have been doing as I'm building these skills out. There is a really fun testing/tdd loop that runs these skills through multiple prompts with baselines and tests it all out.

If you come across any other skills that could be fun to combine, lmk!

you're not wrong. my goal was for more playful.