4 ms·

I've been having a fantastic time telling it to use ASD-STE100 Simplified Technical English (or use a skill for it, I've been playing with [1]) It's a very cle

I've been having a fantastic time telling it to use ASD-STE100 Simplified Technical English (or use a skill for it, I've been playing with [1]) It's a very clear and understandable way of writing that puts priority on clarity. It gets rid of the flowery language, the dense jaron, and the weird corporate marketing speak they tend to do. It is a bit repetitive, and it sometimes doesn't always wfit well in every situation, but for technical writing or explanations it's been such an incredible breath of fresh air! [1] https://github.com/AminBlg/SimpleEnglish https://github.com/AminBlg/SimpleEnglish

physix 2mo ago
This just might save me. Claude has been driving me nuts with incomprehensible summaries after a long task, where it's actually really important to understand what was done (and what wasn't). But I'd like that skill to only be used at the final step, when it finishes something.
- ctxc 2mo ago
  agreed with "the final step". I worry adding commands like these might affect quality of responses at each step, which then stack up to result in an overall worse outcome.
  - abhijat 2mo ago
    This whole thread is what the original post arrives at too, including ASD-STE100.
plaguuuuuu 2mo ago
So far hasn't really worked that well for me. Getting Haiku to rewrite everything user-facing has been way better. I'm tired boss.
suttontom 2mo ago
The OP is literally an explanation of why you should not do this, using ASD-STE100 Simplified Technical English as an example of what not to do.