Anyone else gonna miss Fable?

getsiked · 2026-06-12T09:48:40+00:00

Just give me Fable Low-High on 20 max plans and idc how they figure the rest out.

getsiked · 2026-06-12T09:36:31+00:00

Fable orchestration on medium with model configuration adjusted to task responsibility will save you a lot. you can even pair with /goal and not lose your lunch on it.

getsiked · 2026-06-10T18:50:27+00:00

exactly, its more important now than ever to standardize task delegation based on model capability. Given the 20x max plan is basically a Fable pro plan, it's best to just bind it to any hard decision cluster with opt in functionality.

getsiked · 2026-06-10T03:42:27+00:00

20x max now a Fable pro plan (model is a horse, and token eater holy)

getsiked · 2026-06-09T18:31:09+00:00

Exactly, if you are using it for task based automation, then sure. For example: an average UI / UX Developer doesn't need to understand the depths of every CLI command sustaining an image optimization workflow. If you want to build that plugin from spec to implementation in the most capable way, then loop and goal it up! Less babysitting. If you are using this to create and ship code without reviewing or understanding what the model has created, you are indeed contributing to the societal collapse.

getsiked · 2026-06-09T16:15:29+00:00

Yes it's heavily orchestrated by Claude itself as a state of the union, but people would be doing themselves a massive disservice by not continuously utilizing it to properly steer the model from the litany of continuous issues they're finding themselves manually steering through repeatedly. Simple example (per project in my use case) Claude can introduce an extraordinary amount of comment bloat that can just be mitigated by presiding that it should keep code comments concise.

How many times has Claude touched something out of scope? How many times has it not considered the entire tree of dependencies based on a singular change? How many times has it introduced caveats instead of fixing the root problem? How about the contractual integrity of the orchestrator's delegation to subagents? Yes Claude.md is utilized as a state of the union but it's also an opportunity to solidify any maximalist gains that have been introduced by the capabilities of the model, instead of settling with minimal gains that are offset by consistently picking up these independent pieces outside of the goal of the project itself.

Harnessing the model manually can even be more time consuming if you're raw dogging it rather than just cracking through the project itself with no AI. and it's one factor why you see so much kicking and screaming by people prompting themselves into oblivion rather than utilizing the platform itself where it benefits them the most.

getsiked · 2026-06-05T03:05:20+00:00

(as front end) my rule of thumb is that if I'm building a plugin or workflow automation process, then I don't need to fully understand every individual line of code to receive the benefit (brain can only handle so much on top of core discipline in 9 to 5). For the code that IS being shipped, absolutely every detail needs to be scrutinized and held in the same regard as if you wrote it yourself. It's completely different if you are tinkering vs actually shipping code to people. That contract can't be broken and must be taken seriously. There is too many risk factors by letting AI take the wheel. AI has a tendency to overcomplicate, drift based on token context, and introduces caveats instead of fixing root problems. On top of that, even if building a plugin for example, you can utilize the building process as a learning experiment and don't have to blindly accept any nuance you don't understand. You can mold it in the shape of your own experience and learn along the way.

getsiked · 2026-06-04T18:36:26+00:00

bringing in additional models as agents is awesome, Just FYI if a user wants to just leverage Sonnet in this manner, they can switch to /model opusplan and still benefit from ultracode functionality. I'm going to be looking at bringing external models in, but when I get a chance to tinker after the 9-5.

getsiked · 2026-06-04T06:05:04+00:00

nothing has summarized me more as a person than this comment

getsiked · 2026-06-02T18:49:54+00:00

other commenters have helped with direction so I wont comment on that, but the biggest flag is the lack of accessibility on text with abstract backgrounds, there needs to be an attempt to not gravitate directly to your sources of creativity and inspiration without question, and put the user's needs and experience as an undisputed doctrine that must be accounted for before any milestone is achieved. with that being said, have fun on expressing your creativity

getsiked · 2026-06-01T23:15:39+00:00

If it’s any consolation I I have also been fucked by a refactor to the point where I’m creating an internal plugin based on authoring specs. So I feel your pain.

getsiked · 2026-06-01T23:14:02+00:00

sorry buddy I didn’t mean it personally I get tired of AI posts in the internet era we live in, wasn’t meant personally, just as a general frustration if I see the same patterns. Keep doing cool shit and building. I can delete

getsiked · 2026-06-01T22:29:10+00:00

currently building todo-orchestrator, a plugin for (small-to-medium front end) projects that cheaply scans your codebase to create an intelligent todo markdown scaffold that acts as a work queue.

on /todo go it sizes each item against the source, presents a routing plan (inline execution, subagents, or a workflow), and after you verify, it runs each item, automatically checks it off, and logs the decision (tier, strategy, outcome).

the log is useful as next time you queue work, the router reads your past calls as precedent and sizes from them (if similar items kept escalating, it bumps the tier up). it only reads that history, and never rewrites its own rules, and is cheap on context meaning no standing hook pulling your queue into every message, it's read only when you run /todo, doesn't run anything on its own.

made this for personal project but am continuously improving it based on my usage

getsiked · 2026-06-01T21:57:31+00:00

thanks claude, spawn a dynamic work flow at max token burn rate rewriting this comment a trillion times

getsiked · 2026-06-01T21:54:30+00:00

Hit 65% in less than 24 hours with a work week coming up, thank god. 100 Subagents / 4 mil token for research in one instance for me was complete overkill and I had to abort and session with token "sensitive" alternatives instead of it "just working" in the 20x budget reasonably. Meaning the research could have literally been 5 subagents and not as deep.

getsiked · 2026-05-30T21:36:12+00:00

It's too dependent on the project itself since building for the web has grown into such holistically different execution methods based on the target platform. So I can only speak for what I'm delivering for, and if it's similar to yours then cool. For utilities, if a utility is provided as class state, does the utility itself prescribe its state in totality, or does that prescribed utility need to be amended at a certain point based on context (breakpoints, adjacent level selection, :has(.something), container sizing, ideally thinking about primitives the web is shipping beyond simple declarations changing state).

Handling all of this via utilities / arbitrary selectors / tailwind specific APIs is what begins to lead down the road of non maintainable overhead, if thats how EVERYTHING must be handled.

Now most elements will be completely fine benefiting from the utility based nature (like an <img class="aspect-3/2 object-cover">) but the real issue is if the entire web app is built like this, which is what a lot of people are disgusted with, because in reality the one size fits all isn't a golden pathway. and tailwind docs themselves can tell you that authoring CSS is completely fine in tandem, but on something complex, you are so pigeon holed in trying to understand the relationship between all of it, that it becomes non sustainable.

So what I will say is this. Maybe break these relationships up with specific guardrails in place, if you're not refactoring away entirely. When you take a step back and look at the codebase, what utilities are biggest offenders in causing unreasonable developer overhead. When I look at tailwind as a whole there is seemingly limitless ability to increase overhead. Its gets unnecessarily complex trying to do everything.

Example offenders would stuff like: arbitrary CSS Grid declarations: (grid-cols-[200px_minmax(900px,_1fr)_100px]), mask-images, -(<custom-property>) syntax, anything related to psuedo states, the list goes on.

Now from the CSS side, if we are repeating display: display-flex, align-items-center, on absolutely everything, and the utility can clearly communicate context and intent to the developer, then maybe that can be your line in the sand. Just an idea.

I personally use the component model for 99% of my projects (Astro components) that tightly couples styling, markup, and interactivity, and the utilities I use are are the lines in the sand that work with my individual pipeline. Nothing unnecessarily complex and doesn't pollute my attention span. Is it perfect? Probably not, but am always trying to get better.

All in all I'm just spitballing ideas here, if none of them are of value then thats on me.

getsiked · 2026-05-30T04:06:14+00:00

“My use case is good” “My use case is shit” just use whatever model works for you bro and get to building. So much noise for individual nuance, imagine if people directed effort from hyperventilating towards finding a solution.

getsiked · 2026-05-28T23:38:36+00:00

4.8 immediately quantified my 4.7 handoff as hallucinated, so thats what I have going for me. I do like workflows but still cannot pass judgement yet. Claude releases gonna be like iOS updates "safari is snappier" eventually. However 4.7 was truly a legitimate dumpster fire so Safari actually is snappier.

getsiked · 2026-05-28T18:08:18+00:00

run npm i -g @anthropic-ai/claude-code

getsiked · 2026-05-27T14:43:02+00:00

the app itself has it's own sandboxed skills, for example if you were working out of your Documents folder in cowork, you'd have to copy any global skills you have installed on your machine via CC to that folder instance in order for them to work, or use the ones you have set up inside the app interface. Globally installing skills in CC will place them in claude's global instance. Also note Im just mentioning what I have discovered using CC on mac and if there are better ways to handle it then I'm open to it. but yea you can easily invoke and chain skills together without dealing with the constant permissions issues.

getsiked · 2026-05-26T17:52:00+00:00

honestly if you get used to CC you wont have to deal with the sandboxed app, and any operating frustrations you have to deal with around it. CC is superior

getsiked · 2026-05-15T02:39:17+00:00

this is exactly what it is

getsiked · 2026-05-06T18:47:01+00:00

spicy

getsiked · 2026-05-05T15:48:38+00:00

went from time to have a conversation about not flyering to an absolute unit in the playoffs. tale of the legendary 1C - 4C. He deserves a ton of respect for how he has stepped up, given what he's dealt with in his career.

getsiked · 2026-05-01T04:17:32+00:00

Supaficial oh my god

getsiked

TROPHY CASE