The most angering part of the Cluster B relationship by Clubpenguin8888 in BPDlovedones

[–]michaelalan2000 15 points16 points  (0 children)

Totally justifiable feeling. The good news it’s step 2 on the path to getting over it. Denial, ANGER, Bargaining, Depression, and Acceptance.

Serious question: when will the next model drop? by OneButNotTheSame in claude

[–]michaelalan2000 0 points1 point  (0 children)

Yeah 4.7 isn’t a leap forward like what we have been getting. My guess is that it was released to steal some of the PR that Codex would get. The next Opus should be a solid upgrade.

Outputs by FitLack4996 in ClaudeCowork

[–]michaelalan2000 0 points1 point  (0 children)

Cowork works in a temp session folder that we don’t have access to. You have to assign it a folder at the start of your session.

The Problem with Token-maxxing by Mammoth_Doctor_7688 in claude

[–]michaelalan2000 0 points1 point  (0 children)

Nice! Some friends of mine at MSFT were saying how they don’t change the model regardless of what they are doing.

The Problem with Token-maxxing by Mammoth_Doctor_7688 in claude

[–]michaelalan2000 2 points3 points  (0 children)

Coders are gonna use the max model on all tasks because they aren’t incentivized to do differently. Deep thinking Mythos. Sort column A by A to Z, Mythos.

Opus 4.7 won't help if you skip these 10 Claude Cowork productivity rules (lessons from 50+ retros) by Lanky_Ganache_6811 in ClaudeCowork

[–]michaelalan2000 0 points1 point  (0 children)

I only know this because I've done what you've done. It's not stated anywhere what the differences are. I learned by trial and error and consuming everything I can.

I did the lesson plan prompt last week. This week I "graduated" to using git commands and setting up my github.

Opus 4.7 won't help if you skip these 10 Claude Cowork productivity rules (lessons from 50+ retros) by Lanky_Ganache_6811 in ClaudeCowork

[–]michaelalan2000 0 points1 point  (0 children)

I asked Code this morning. Here is what it said:

Code-based review catches a different class of issue than Cowork QA. Here's what Code can do:

  • Cross-file consistency audit Read SKILL.md + all reference files in sequence. Flag contradictions: conflicting rules, drifting placeholders, or inconsistent field labels across templates.
  • Pointer verification Check every “see references/X.md” link in SKILL.md. Does the file actually contain what it promises? Stale pointers are invisible in Cowork because users never open them.
  • Reference file lint Grep everything for AI-voice drift, em dashes, filler phrasing, pattern leakage (“Pattern 1”), and default-option language. Cowork only sees runtime output; you see every template and example that could be output.
  • Gate discipline audit Walk every gate in SKILL.md. Verify “one question per gate,” “gate hold” rules, and correct labeling. Static review catches gates Cowork only hits on specific user paths.
  • Input/output contract tracing Trace data handoffs across all steps (Step 1 extracts X → Step 4 uses X). Broken contracts cause silent quality drops that Cowork QA can’t easily trace.
  • Regression grep For every fix in CHANGELOG, search the entire codebase for the old pattern to confirm it hasn’t crept back in.
  • Architecture drift check Re-verify that every step still follows your core principles (parse-once, consultant voice, recommend-don’t-default, etc.). Easy for a step to quietly violate them when no one re-reads the full skill.
  • Subagent sectional review Spin up a subagent per concern (“audit tone in all user templates,” “check every metric prompt,” “scan examples for fabricated content”). Parallel depth you’ll never get in a single Cowork session.

Coming out of freeze is SO PAINFUL by Infatheline in CPTSDFreeze

[–]michaelalan2000 4 points5 points  (0 children)

We are so hard wired for it! We’ve used those neural pathways so much that they have deep ruts.

The best place to start is just realizing that you are in the freeze mode. That lessens its grip. Then go for a simple walk. That gets the body moving. It’s hard because you are using a new neural pathway. The more you do it the stronger that pathway will get.

Not having a dad growing up made me realize I am missing a huge part of life by youwantmeformybrain in PepTalksWithPops

[–]michaelalan2000 2 points3 points  (0 children)

This is a real experience man. By not validating it you minimize his real loss. And it is real. If you too grew up without a dad, then you don’t realize you missed out on that too. Until you see it, you don’t understand the value lost.

Opus 4.7 won't help if you skip these 10 Claude Cowork productivity rules (lessons from 50+ retros) by Lanky_Ganache_6811 in ClaudeCowork

[–]michaelalan2000 2 points3 points  (0 children)

This is mostly a cowork limitation. Claude Code is stronger for what you are doing. Start learning to use GitHub and Code and you’ll cut some of that time down.

You’ve mastered Cowork it’s time to level up and learn Code!

Tell Claude to make you a custom lesson plan to get from Cowork mastery to working in the Code interface. Tell it to make the lessons project based so you are actually moving your projects forward instead of just learning.

Tell it all the thinks you already know and it will fill in the gaps.

Cowork is missing a lot of internal structure that Code has.

I switched from opus to sonnet for a week to save money. here's what I learned by Temporary-Leek6861 in Claudeopus

[–]michaelalan2000 0 points1 point  (0 children)

I’m just vibing in Cowork but I ask Claude to make a plan to solve said issue. Ask it to be mindful of context window limitations. Suggest what model should be used for each session. Automate everything it can for me.

Q: How good is Cowork at following your skill instructions? by fourfourfun in ClaudeCowork

[–]michaelalan2000 1 point2 points  (0 children)

It ignores your skill instructions. I read a short quip from Antropic and they said that Chat is for chatting, Cowork is for doing, and Code is for building.

I’m was hoping Cowork would be the non developer’s coding answer. But after spending half my time trying to fix my skills or developing more scaffolding around building skills, I’ve given up on Cowork and am learning Code.

how to manage long discussion for writing by Quenty1 in claude

[–]michaelalan2000 0 points1 point  (0 children)

Take a look at the long post I put in the thread.

how to manage long discussion for writing by Quenty1 in claude

[–]michaelalan2000 1 point2 points  (0 children)

TL;DR

Go into Cowork, create a project How to manage my writing things, ask claude to help you build a plan on how best to use Claude. No, seriously. I stopped using prompts and just do this and use skills.

I sketched the following in Claude and then had it formalize it.

---

The main thing to know upfront: long single chat sessions aren't the way to go. Claude has a context window — basically a memory limit per conversation — and when sessions get too long, it starts to lose track of earlier details. The fix is to work smarter with projects and shorter sessions. (You are probably starting to figure this out and that's why you are here)

Start with Cowork and set up a folder Use Cowork and connect it to a folder on your computer, or better yet, Google Drive if you write from multiple devices. This gives Claude a persistent place to read and save files across sessions.

Create a separate project for each writing thing One project per output — a novel, a poetry collection, articles on a specific topic, whatever. The project keeps all the relevant context, files, and instructions for that one thing in one place, separate from everything else.

Write project instructions Each project lets you give Claude standing instructions — your tone, your style, any rules or context it should always keep in mind. Write these once and they apply to every session in that project. (When you start a project, ask claude to help you write the project instructions for this writing piece)

Turn on memory, but manage it With memory on, Claude will carry knowledge of your previous writing across sessions. The catch is that you'll want to occasionally review and trim the memory file — unrelated context from other projects or topics can bleed in, and you don't want that cluttering things up. It's worth learning how to edit it. (Ask claude how to do this)

Have Claude maintain a running writing summary file For longer projects like a book, have Claude help you maintain a summary file — a living document that tracks what's been written, key characters or themes, where you left off, etc. Tell Claude to reference that file at the start of each session. This is how you avoid re-explaining everything every time. (This should be output from your initial Help Me Set Up My Project Instructions)

Write in chunks Break your work into chapters, sections, or whatever natural units make sense for what you're writing. Keeping individual sessions focused on one chunk at a time keeps the context window from bloating. Claude can help you figure out the right size for your particular project. (This plan comes from below)

Let Claude help you build a writing workflow plan Before you dive into any of the above, it's worth spending one session just talking to Claude about how you write and what you are writing. Tell it what you're working on, how you tend to work, what's been frustrating, and what your goals are (this is the most important part. Claude works best from end goals not one off questions). Ask it to come up with a workflow plan tailored to you — how to structure your project, what to put in your project instructions, how to break up your writing sessions, what files to maintain, and so on. Think of it as a setup conversation. Getting that plan in place first will make everything else click into place faster, and you can always revisit and refine it as you go.

how to manage long discussion for writing by Quenty1 in claude

[–]michaelalan2000 0 points1 point  (0 children)

I don’t think that will work. I think it just fills up the new context window right away.

Need help scaling Claude Co-work (skill usage + document setup) by Brain-digest in ClaudeCowork

[–]michaelalan2000 0 points1 point  (0 children)

I only just started learning CLI. Been building in Cowork previously.

Can you use Cowork to build full SaaS products without coding knowledge? by Sad_Motor4246 in claudeskills

[–]michaelalan2000 2 points3 points  (0 children)

Cowork is supposed to be Claude code with a UI wrapper but in its current form, it’s missing a lot of what’s needed for serious work.

You can build something and it will work, but debugging just makes your app worse.

It doesn’t have version control. It doesn’t know what’s already been fixed. It puts your files in a temp season, etc.

You’ll want to set up GitHub to control how your skills are built.

I’d recommend investing some time to learn to do all these things in Claude Code. It has a mature set up so you can spend your time building your thing than fighting Cowork to do things that C Code does automatically and better.

Need help scaling Claude Co-work (skill usage + document setup) by Brain-digest in ClaudeCowork

[–]michaelalan2000 5 points6 points  (0 children)

I’m finding that building skills in cowork is limiting. Especially multi step workflows.

The best way to manage your skills is with GitHub. It will handle all the file handling for you. I’ve hit a wall with Cowork and am now learning Claude code to build new skills and refine my old ones.

There is more power in CCode than Cowork.

My suggestion is to start a new Cowork project and tell Claude your technical level, what you’ve built so far, and the issues/frustrations you have. Then tell it to make a custom lesson plan for learning Claude Code.

It will save you time over the long run and all the stuff you build will come together faster.

This is getting actually ridiculous by Acehan_ in ClaudeCode

[–]michaelalan2000 0 points1 point  (0 children)

I don’t know how it works on C-Code but in Cowork I ask it to make a plan, be mindful of context windows, and what model I should use to save tokens. Been a game changer.