Professional Services
Custom Software
Managed Hosting
System Administration
See my CV here.
Send inquiries here.
Open Source:
tCMS
trog-provisioner
Playwright for Perl
Selenium::Client
Audit::Log
rprove
Net::Openssh::More
cPanel & WHM Plugins:
Better Postgres for cPanel
cPanel iContact Plugins
No, not that PCP. Nor "Praise, Correct Praise". Perl::Critic::Policy.
The core issue when dealing with LLM tooling to generate programs is the same problem working with other people. Unstated preferences means you get output which is unacceptable, but understandable because mind-reading is beyond both. Encoding this in things like skills is still not enough. Just like with your own internal wiki documenting how you "do things around here", you can be sure it will be routinely ignored.
No, you need something tighter in the OODA loop. This is the same reason that LSPs and IDEs are so popular with people too. Programming languages have so much to remember that "teacher, my brain is full" is a serious problem, only remediated by near-instant feedback. Given LLM agents are dumber and more forgetful than the any fauna you have ever worked with (it is a computer after all), the rule applies.
Sometimes even this isn't enough, and you need hooks. The earlier in the process, the better (as always). This also will save you tokens, as it doesn't waste work on things that won't pass muster.
The process that works (which I tentatively call "rudra" - "he who eliminates problems by their roots") is like this:
The usage model here has similar limitations to SA. You will quickly find there are points at which you reach diminishing returns as regards encoding your preferences. This is no problem for most people, because "good enough" is.