u/mxriverlynn

one of the largest problems that i constantly run into is unintelligible pseudo technical descriptions that include so many code references, i can't figure what the sentence is trying to say

i hate it 😭

so i built a way to fix it!

my Han (https://github.com/testdouble/han/) plug-in has a research results document and a standardized human readability document set, with rules about making output readable

I've applied this research and these documents to a new agent definition, readability-engineer (https://github.com/testdouble/han/blob/main/docs/agents/han-core/readability-editor.md). it uses the resource files to ensure output confirms to a set of standards, making out far more readable and understandable

I've also applied the readability-editor as a skill called edit-for-readability (https://github.com/testdouble/han/blob/main/docs/skills/han-core/edit-for-readability.md). it directs the readability editor agent at the supplied context (a file, copy and paste text, or whatever) and edits it with those same times, to make the output more understandable

the screenshot attached to this post is an example that came from my work earlier today. I've blanked out specific words for security and privacy reasons. but i think the overall language that's in this screenshot is extremely easy to read and understand - at least, compared to the default output that Claude likes to give

here's the thing, tho... i don't expect a ton of people to jump into using Han just for this. I'd love to see more users, and continue grow the Han ecosystem, overall. but what i would rather see from this post, is people taking the research i did, the documents i wrote, and even the skill and agent definition, so they can improve their own output.

i don't think my solution is perfect. but i do have strong evidence to say it's really good. and i want to share what I've built in the hopes that it helps other people, too.

good luck! and have fun.☺️

a friend gave me a small plant that i harvested and set to the side of my living room. today my partner noticed some small, new growth on it.

other than putting it back in my grow tent and watering it, what should i do to help this little lady grow big and flower again?

what do you mean "it's weird to listen to the same albums 2 to 3 times per day, every day, for months on end"?! 🤨😁🤣

what do i do with this?

a friend of a friend gave me this small plant. i got it set up in my grow tent, but i have not yet had any success with getting anything to grow

i don't know what strain it is. i don't know how old it is. i don't know what kind of dirt it's in. the only thing i do know is that it was kept in a 68°F room, and that's it's incredibly small for already being flowered.

should i try to keep growing it? and maybe let it go to seed so i have seeds to use? should i harvest what little is there?

any and all advice is welcome. i have close to no clue what I'm doing, so please offer some advice if you can

💚

a few of my coworkers have noticed something that feels important, regarding the model selection and effort level chosen for Claude, based on how specialized a skill or custom agent definition is:

• lower specialization requires higher effort and model selection
• higher specialization can work fine with lower effort and model selection

what i mean by "specialization" is illustrated in the Claude skills and agent definitions that I've built into a plug-in. the plug-in has 15 skills, and 21 custom agents. every one of these skills and agent definitions has a very narrow ("specialized") purpose. there is no overlap. there are no general purpose items. most of my skills take advantage of the multitude of agents, as well.

they are all very specialized.

and because of this specialization, my coworkers have noticed that they can use sonnet on medium effort and get results that are nearly identical to opus on xhigh effort, in most cases. the major difference between the output is often how picky opus or xhigh thinking get, which often results in over-engineering and extra noise in the actual implementation plans and final code output.

again, this is because of the specialization in the plug-in.

and it makes sense when i think about how much work Claude does without this specialization in skills or agents. without them, a single call to plan a feature has to try and do everything it can think of within the limits that are specified. and it has to figure out how to do everything, every time you make a call to do anything. this directly leads Claude to producing average plans and solutions, at best.

with each specialization and the coordination of them by a human who is running the skills, tho, Claude already knows what to do. it doesn't have to spend all the time and tokens figuring out what to do before doing it. this clears up a lot of context and a lot of tokens that can be used for the real work.

the result is that i can now run Claude in medium effort as my default. and outside of the work that really needs depth, i can default my model to sonnet.

...

I'm curious, tho: is anyone else seeing this? are you taking advantage of it? and how?