u/Brain-digest

A few months ago I asked whether a PM should work in Claude Code or Cowork. The answer was almost unanimous: Claude Code, better output, more control.
Both tools have changed a lot since then, so I'm asking again.
My context: I'm not a developer. My work is docs, briefs, research synthesis, spreadsheets and slides. No code.
If you've used both recently:
• Do you still see a quality gap on non-code work? On which tasks?
• Were you using the same model on both?
• Is the IDE/terminal overhead worth it for a non-technical user?
Concrete examples are the most useful. "I gave X to both and got Y" beats "Code is just better."

Hello everyone! Is anyone here currently working at Revolut in France?
I’ve seen quite a few negative reviews about Revolut’s work culture globally: high pressure, unrealistic targets, tough probation periods, etc.
With Revolut expanding in France and Paris becoming its Western European HQ, I’m curious: does the French office feel different because of local employment laws and work culture, or is it broadly the same?
Would love to hear first-hand experiences.

I’m starting to feel a bit overwhelmed by Claude. Every day I see new advice, new workflows, new files, new settings… and I’m honestly a bit lost.

I’m not a developer. I’m a Product manager, and I’m trying to use Claude better for product work: research synthesis, framing problems, writing specs, structuring ideas, improving prompts, etc.

So far, I’ve used Claude Chat with memory and custom instructions. I added things like how I want Claude to talk to me, the kind of outputs I prefer, my work context, tone of voice, etc.

But now I keep seeing people talk about "claude . MD" , especially in Claude Code / Claude workspaces, and I don’t really understand how it fits with memory and instructions.

A few basic questions:

• Is "claude . MD" global, or is it linked to one specific project?
• Is it basically the equivalent of memory/custom instructions, but for Claude Code or cowork ?
• What should actually go inside a "claude . MD" file? Tone of voice? Project context? Working rules? Output formats?
• Should you have one "claude . MD" per project, or one reusable structure across projects?
• If my projects often follow the same broad framework, should I repeat the same instructions in each project?
• I’ve seen people mention /init to create a "claude . MD", but it seems to be available in Claude Code, not Claude cowork or Chat. Is that right?
• As a non-dev, should I still be using Claude Code? What can I actually do with it for product work?
• And if "claude . MD" is already the reference file, why do people also create separate reference files?

I’ve asked Claude to explain this, but it usually gives me a very long answer that makes things even less clear.

Could someone explain the overall logic in simple terms? Maybe with a concrete example of how a non-dev PM could structure this properly?

I’m starting to feel a bit overwhelmed by Claude. Every day I see new advice, new workflows, new files, new settings… and I’m honestly a bit lost.

I’m not a developer. I’m a Product manager, and I’m trying to use Claude better for product work: research synthesis, framing problems, writing specs, structuring ideas, improving prompts, etc.

So far, I’ve used Claude Chat with memory and custom instructions. I added things like how I want Claude to talk to me, the kind of outputs I prefer, my work context, tone of voice, etc.

But now I keep seeing people talk about "claude . MD" , especially in Claude Code / Claude workspaces, and I don’t really understand how it fits with memory and instructions.

A few basic questions:

• Is "claude . MD" global, or is it linked to one specific project?
• Is it basically the equivalent of memory/custom instructions, but for Claude Code or cowork ?
• What should actually go inside a "claude . MD" file? Tone of voice? Project context? Working rules? Output formats?
• Should you have one "claude . MD" per project, or one reusable structure across projects?
• If my projects often follow the same broad framework, should I repeat the same instructions in each project?
• I’ve seen people mention /init to create a "claude . MD", but it seems to be available in Claude Code, not Claude cowork or Chat. Is that right?
• As a non-dev, should I still be using Claude Code? What can I actually do with it for product work?
• And if "claude . MD" is already the reference file, why do people also create separate reference files?

I’ve asked Claude to explain this, but it usually gives me a very long answer that makes things even less clear.

Could someone explain the overall logic in simple terms? Maybe with a concrete example of how a non-dev PM could structure this properly?

I'm curious how other UX Designers, UX Researchers, Product Designers, and Product Strategists are getting the most out of Claude today.

A bit of context about my role:

- I work in fintech/banking.
- I run qualitative and quantitative user research.
- I write interview guides and research plans.
- I analyze large amounts of user feedback, Airtable data, survey results, and usability tests.
- I synthesize insights and turn them into product recommendations.
- I create benchmark studies and competitive analyses.
- I work on UX writing, behavioral design, nudges, and conversion optimization.
- I prepare strategic presentations for product, marketing, and leadership teams.

I feel like Claude is incredibly powerful, but I'm not sure I'm using it in the most efficient way.

A few questions:

1. What are your highest-ROI use cases?
2. How do you structure projects, knowledge, and context?
3. Do you use sub-agents or keep everything in a single chat?
4. How do you handle large research datasets?
5. Any prompts, workflows, or setups that completely changed the way you work?

I'd love to hear from people using Claude for UX research, product strategy, service design, design ops, or product management.

What's your current workflow?

I'm curious how other UX Designers, UX Researchers, Product Designers, and Product Strategists are getting the most out of Claude today.

A bit of context about my role:

- I work in fintech/banking.
- I run qualitative and quantitative user research.
- I write interview guides and research plans.
- I analyze large amounts of user feedback, Airtable data, survey results, and usability tests.
- I synthesize insights and turn them into product recommendations.
- I create benchmark studies and competitive analyses.
- I work on UX writing, behavioral design, nudges, and conversion optimization.
- I prepare strategic presentations for product, marketing, and leadership teams.

I feel like Claude is incredibly powerful, but I'm not sure I'm using it in the most efficient way.

A few questions:

1. What are your highest-ROI use cases?
2. How do you structure projects, knowledge, and context?
3. Do you use sub-agents or keep everything in a single chat?
4. How do you handle large research datasets?
5. Any prompts, workflows, or setups that completely changed the way you work?

I'd love to hear from people using Claude for UX research, product strategy, service design, design ops, or product management.

What's your current workflow?

Hey everyone,
Quick question because I’m honestly pretty surprised lately.
I’ve been using Anthropic Claude for several years now with a Pro account, and until recently things were mostly fine. I knew there were usage limits, obviously, but they always felt reasonable.
But over the past few weeks, it feels like a single prompt can completely destroy my entire capacity.
Claude suddenly starts calling agents/tools on its own even though I didn’t ask for any of that, goes into massive reasoning chains, explores tons of stuff… and somehow after just 1 or 2 prompts I’m basically out of usage.
So I wanted to ask:
are other people experiencing the same thing?
are there prompting tricks or settings to prevent this?
or is this just the normal behavior now?
Honestly I find it pretty absurd, especially considering I’ve always been on a Pro account and I’m not even using it in a particularly crazy way.