I've found it to be great for planning code changes (or new projects). I use the superpowers plug-in which I think guides the planning.

Then I switch models (to luna) before implementation. I find this combo nearly always does what I want.

I also use a skill called ponytail, its goal is to keep things terse and edits small. It may have contributed to the successes above.

I like that skills are easy to try out, too.

You would probably get better results with Luna for the real simple tasks, or Sol with low thinking effort.

I find that I get exactly the effort that I asked for, which is pretty nice. The other side of that coin is that these are the least lazy models I’ve used so far. They will go on elaborate tangents to complete the task when I want them to.

I've found it's worse for simple tasks too, and I have to give it stricter guidelines, and sometimes it doesn't follow the same patterns I've grown to expect. I've found using 5.6 (sol) is good for diagnosing issues though, especially in terms of optimization of some given path

Yep. I have not yet had a single good experience with Sol or the 5.6 models on a variety of harnesses and configurations. It overthinks, overcomplicates and often makes my code into an unmaintainable sludge. It'll usually take 5+ turns of steering to get it in the right direction.

It's your responsibility to set an appropriate level of Thinking. For simple tasks, I use the instant model. As an approximation, the choice is proportional to the amount of time I want it spending on the task. Also, you can always ask it to respond succinctly.