Launched this week
StaffEngineer
Deterministic Claude Code skills for a production stack
15 followers
Deterministic Claude Code skills for a production stack
15 followers
StaffEngineer is a pack of deterministic Claude Code skills that scaffold and wire a production-grade dev stack the same correct way every time — instead of re-prompting Claude each session. Skills run deterministic scripts (e.g. /squidci for CI) over a known toolchain (OrbStack, Doppler, Docker). Free today: squidapp (full-stack scaffold) and squidops (toolchain doctor). The full pack (deploy, observability, real-time, durable workflows) is a one-time purchase you own, not a subscription.
RiteKit Company Logo API
@tamaskalman Hey — congrats on the launch. This scratches a real itch: re-doing the same production setup every session and getting slightly different results each time is maddening, so turning the correct way into deterministic skills is a clever answer. "Prompts improvise; skills ship" is a great line, and the one-time, you-own-it model feels right for dev tooling.
Launch tip: a short video on the page usually converts better than text alone. I made one for you from your own site — here:
Fel free to save it and add it to your launch. It was auto-made by FoxPlug (https://foxplug.com), which turns your real build and launch activity into narrated videos and ready-to-post updates.
Congrats on the launch!
@saulfleischman Saul, this is awesome. I just added your video to the launch list so people can see it as part of the launch. You captured the pain exactly: every session starts drifting unless the setup is deterministic. Really appreciate you making this.
RiteKit Company Logo API
@tamaskalman Cool - that's the idea, and it's your's, use it wherever. I hope you'll take a look at https://foxplug.com - it generates your social posts, gets exposure by doing your GIFs so that they get used and your projects get seen in slack, discord, MS Teams, Facebook Groups... And you know why? Well, it was built by a guy with almost as many products to his name as you, so, I know what it's like to be busy building. No time to get seen. FOxPlug watches your commits and much more and produces your "startup in public" material.
You asked which part of a prod setup people wish was deterministic: for me the initial scaffold was never the pain, the operational routines six months in are. I've ended up encoding my App Store ops, QA regression passes, even a Product Hunt routine as Claude Code skills with scripts behind them, because prose instructions drift a little every session until the output is unrecognizable. Curious how you handle skill updates when the underlying toolchain moves, do users re-download or do skills version themselves?
Curious how this handles updates when Claude Code itself evolves, since the skills rely on specific toolchain versions. Do you ship patches for new model behavior or is that on me to retest?
How does the deterministic scripting actually hold up when my project's toolchain drifts from the defaults you baked in, say if I'm not on OrbStack or I'm already wired into a different secrets manager?