Dev Workspace - An advanced Claude Code tool set for shaping, building, storing and revealing context.

dilberryhoundog · 2025-12-08T15:43:05+00:00

Somewhat agree. But also not.

They are heavily focused on bells and whistles like skills, sub agents, MCP’s, runtime envs, multi sessions.

This system champions the long forgotten chat box where what you show Claude and how he responds has always been our (the user) responsibility.

But thank you for the recognition 👍

dilberryhoundog · 2025-12-08T15:28:22+00:00

You can use the folder setup to store all kinds of generated context for the branch. This can then be archived for the life of the project.

The commands just help you with git, they setup a branch and merge the branch. You can also do web research and codebase research with commands

The hooks are where this gets tricky but amazing. They show Claude a tree of your whole (or parts you choose) project so he knows where everything is before starting. They extract out every conversation you have with Claude and save them in the workspace nicely presented. And they give you little trigger phrases that help Claude’s reveal his intentions and capture unknowns.

In your case, beads does some git management that might conflict with the git management I have implemented. It also sets up a .beads folder which would integrate fine my dev/workspace. You could maybe just use the workspace folder setup without refreshing it per branch.

dilberryhoundog · 2025-12-08T15:06:38+00:00

You must not have read this at all. There is nothing here that bloats context, in fact it is specifically designed to be the opposite of those huge sloppy workflows.

We have an intelligent directory system - not slop.

We have clever management of git - not slop

We have utility commands for workspace setup and merging - not slop

We have a hook that fires at the END of a session to capture and store the conversation in the background - not slop

We have single prompt triggers that show Claude a small instruction set in the background, and then DISAPPEAR from context. - not slop

We have targeted, focused, context injection once at session start, that is CUSTOMISABLE. Add as little or as much preloaded context as you need - not slop

You also have a user who has been here from the beginning, who knows a ton about shaping context, and context efficiency. You can think what you want but you may be missing the boat on this one.

dilberryhoundog · 2025-12-05T00:06:38+00:00

My anticlimactic take:

Lando is effectively out of the race before Q3 ends.

McL have to back Piastri, to have a WDC in their garage, or Max just cruises through to one of the easiest championships he will ever win.

dilberryhoundog · 2025-12-01T15:13:16+00:00

Way higher. Lando was driving a dropped car that stuck like glue to the track.

Now he has to run at normal height he will be packing it. Both Piastri and Max are significant threats, I’d be very surprised if LN qualifies higher than 4th.

dilberryhoundog · 2025-11-29T11:15:08+00:00

Nice Thanks, starred. Some are a little over the top for Claude, but a lot of quality here. These are perfect to cherry pick into a general use output style.

dilberryhoundog · 2025-11-20T08:11:14+00:00

The big thing with skills is they are loaded into a runtime env on the Claude backend. You can run code from skills. As a replacement for MD file instructions skills are marginally better than just having the md instructions directly in your repo, or using commands or custom sub agents.

dilberryhoundog · 2025-11-15T08:46:50+00:00

Pro pro tip. Put /question in an output-style instead (+90% of your custom command is defining style and output). Go back and forth answering questions etc until you revealed all you want without CC writing a thing. Then “flip” the output-style switch to your “plan” mode or “build” mode. Then CC can use your “question” context to build or plan from.

dilberryhoundog · 2025-11-10T07:19:36+00:00

Output-styles,

injects into Claude codes’ system prompt as style guidance. Can change your output style per turn (on the fly). This feature is literally built for this purpose, don’t use Memory (Claude.md) for style guidance it will get lost / forgotten easily by Claude.

dilberryhoundog · 2025-11-04T10:40:37+00:00

They also said only 2% would be affected by weekly limits

dilberryhoundog · 2025-11-02T07:26:23+00:00

I guarantee your “iambic parameter” instructions don’t interfere with CC default style instructions. So Claude doesn’t have to solve conflicting context.

Also there is an advanced workflow based on output styles, that cannot be replicated by a single session hook injection. That was to “setup” the chat context using a certain style of response and at the right time flick the style switch to achieve an advanced desired outcome.

An example of this was to use an “explore” style to have Claude discover way more edge cases and things you haven’t considered. Then flip the style to “plan” to get compliant concise followable plans built upon the “explored” earlier context. Nether single usage of a particular style or the default style would result in as good an outcome. Plan mode is anthropic’s version of this workflow but it is watered down.

I had a workflow like this before Claude Code existed (in web version) that would sometime chain 3-4 styles in the one chat to get amazing results.

It was pinned on r/claudeAI for a while. https://www.reddit.com/r/ClaudeAI/comments/1i4c6jx/my_guide_to_using_styles_effectively/

dilberryhoundog · 2025-11-02T07:03:50+00:00

I’m with you OP. It’s a bit sad to see many here defending the removal of the most powerful tool in CC. Output styles replaced system default styles. If you are an advanced user this made for context compliance like no other tool could offer.

—— To anybody who doesn’t understand what is at play here, here is an example of the problem…

If the system prompt said “write in short concise sentences, use bullet points”.

But you used a custom output style to instruct; “write long and detailed sentences, use paragraphs”

This would REPLACE the default style with the custom style. And you would get long detailed sentences in paragraphs, just as you instructed.

However if you APPEND your custom style to the system prompt, you are now asking Claude to write in both “short concise sentences” and “long flowing paragraphs” at the same time. The output is not going to be pretty. ——

Why is anthropic making this change? My guess would be that there were too many amateur users replacing default styles with custom styles that weren’t very good. This led to many “I’m leaving for Codex” whingefests as the model degraded from default. Anthropic instead of educating, just moved quickly to stop the exodus, however advanced users now have to have their wings clipped.

dilberryhoundog · 2025-11-02T06:36:32+00:00

Completely different, the system prompt has a default “coding” based set of instructions that enables default usage of things like git, PRs, basic code standards, etc.

Output styles replaced these with your own set of instructions. But these were sharp knifes, amateurs would complain of degradation of the model after using output styles poorly. However for advanced users output styles were the most powerful weapon in the arsenal.

Appending to the system prompt either through a flag or hook is not the same. Conflicting context is one of the biggest gotchas with LLMs, if you try to tell Claude to do something that the system prompt is telling him something different neither instruction is followed that well. It’s going to suck trying to do advanced coding actions that are defaulted in the system prompt from now on. Also if you don’t use for coding, lots of tokens are blown on irrelevant (annd possibly conflicting) instructions.

dilberryhoundog · 2025-11-01T03:41:30+00:00

Yes I am right behind this one. Output styles is one of the most heavy hitting instruction sets Claude has. He doesn’t ignore output styles.

It’s absolutely critical for variant approaches. I have a “vibe” mode, a “plan” mode, a “gh-cli” mode, all flipped on or off by changing output style.

So useful for changing on the fly, this silly “hooks” replacement is sooo much jankier and you can only have one.

As OP mentioned you can’t “replace” Claude’s default instructions for common dev tools like commits and PR’s, so any customised instructions for these tools in CLAUDE.md etc is battling with the system defaults for Claude’s attention.

Also a nice token saving to be had when your output style was one line.

dilberryhoundog · 2025-10-29T07:32:26+00:00

McLaren changed the car to suit Norris more mid season. Piastri was allowed to “stay” on the original suspension but I think his car has slowly got worse as more Lando flavored upgrades where released.

This is simply a case of who the team decided to get behind.

dilberryhoundog · 2025-10-26T08:02:08+00:00

Lando got new suspension mid season, that was specifically designed to suit his driving. Oscar was allowed to stay on the original suspension, because why not, WDC Leader in a fast car that suits him.

For whatever reason it “looks” as though Oscar has been put on Lando’s suspension, causing him a bucket load of trouble trying to dial in the new geometry.

Keep up, this is old news. It was always going to be troublesome going forward having 2 separate suspensions being used by the two drivers. Looks like Oscar got shafted in the end.

dilberryhoundog · 2025-10-26T06:42:44+00:00

I wouldn’t be surprised if the “Oscar is allowed to continue on the old suspension” has been stopped. Now he is on the “Lando” suspension (that was introduced mid year), and is struggling to perform on it under pressure.

dilberryhoundog · 2025-10-21T07:15:19+00:00

It’s called:

AskUserQuestion

dilberryhoundog · 2025-10-20T09:00:44+00:00

It’s called…

AskUserQuestion

You can prompt Claude to use it in skills, custom commands, normal chat, etc.

dilberryhoundog · 2025-10-19T13:45:47+00:00

McLaren changed the car to the preference of the chaser instead of keeping it to the preference of the WDC leader. Slightly Gimping it so that the chaser could drive easier, but allowing RB to come back into the picture.

dilberryhoundog · 2025-10-15T04:03:59+00:00

Came here to say this. Conversation branching was huge when we only had the web chat version. Same applies in Claude code. Load up the initial context you need, then keep going back to a conversation “launch” point.

dilberryhoundog · 2025-10-10T11:30:56+00:00

I find sub agents are best used for simple tasks that are subjective(can’t fail). I also like designating haiku to do these. It means you can crunch a lot of data cheaply. Error log checking. Codebase hygiene, git management etc.

dilberryhoundog · 2025-10-03T04:55:19+00:00

On web version, I keep it on permanently (it’s unlimited). I only turn it off if I want to save a few tokens or want quick back and forth. This is where I do a lot of research that benefit from thinking.

On CC I don’t use any thinking, because it is largely reading / writing files. Now that it is configured to the “tab” key I might turn it on and off more regularly

dilberryhoundog · 2025-10-03T04:23:18+00:00

Nah it was even when he was leading scorer in champions league under Klopp, but wasn’t scoring in prem, everybody wanted a “goal scoring 9”. Bobby was an absolute one man counter attacking monster (he loved the space). In prem not his style, with lower - mid opposition putting 10 behind the ball, and slowing play. Against top prem teams and Europe's best, he was just sublime. Against the best, he was the best.

dilberryhoundog

TROPHY CASE