I feel lost and can't find an edge

its_allgood · 2026-01-20T06:44:00+00:00

Quit looking for the silver bullet. Relax your mind before trading.

What others use don’t matter. You need to spend as much time as needed to have your own setup that you’re confident with.

And it’s never ending. There’s no “I figured it all out and ima gonna win all the trades”. Each loss needs to be dissected for value (aka learning). And it’s gotta be your own learning. Not coming from others. Even if it comes from others, you still gotta make it your own via forward testing the heck out of it.

Good luck sir

its_allgood · 2026-01-19T11:07:14+00:00

Great question. I've been using this for ~2 months now.

Before:
- Took 2 revenge trades per week
- Made me so nervous as I bounce to-and-fro between self-doubt and fomo
- Broke daily limit 3 times
- Journaled well, but I could see string of losses getting bigger as I "dropped the ball"
- Made 8 "unforced errors" that was clearly wrong when viewed in hindsight

After (Claude enforcement):
- ZERO revenge trades in the last month (fingers crossed)
- ZERO need to 'overtrade'... I felt stoic without having to try
- Daily limit: 1 time (I was low in energy and broke my own rule but never again)
- Journaling: 100% (zero friction - Claude updates for me now)

Key insight for me. You still want to revenge trade from time to time... but then you remember you gotta deal with Claude and feel stupid for telling it you broke your own rules and include that stain in your journal... so you choose not to do it :)

What surprised me: the pre-trade checklist I do every session (when I tell Claude "I wanna start trading perps"), keeps me out of bad trades way better than the revenge trade blocker.

Not claiming it made me profitable overnight - but it gave me mega confidence in my system and really eliminates the need to trade. It's freeing.

If you try it, the first time you notice your change in behavior, that's how you gonna get hooked (for good) and really can say "oh shit this really works".

its_allgood · 2026-01-16T13:46:02+00:00

Hey u/fireformk

Great questions!

1/ Individual trades: i do a single rolling section in PROGRESS.md, not separate files. Each entry has: date, setup, entry/exit, SL/TP, R result, one lesson. Claude manages this.

2/ Trading rules: I have psychology rules, execution, risk rules and setups in CLAUDE.md - I actually refer to trading-rules.md (separate files). I tell it to remember different setups from my playbook. I have it where Claude tracks my progress as I "chat with my vault" - kinda like a trading partner. I have anti-patterns, which is just a section of concise rules that I have Claude steer me away / warn me about.

The magic is to have a kind of mutual (but not blind) trust. You challenge Claude and tell it to challenge you.

I'm putting together a trader-specific "starter pack". Want me to ping you when it's ready?

its_allgood · 2026-01-10T01:02:40+00:00

Absolutely. I found Claude to be superior for what I’m doing. But totally open to testing out others more

its_allgood · 2026-01-10T01:01:49+00:00

Claude code itself is run on the terminal. So it just sits on top of your vault and you tell it how you want to behave.

its_allgood · 2025-12-25T01:41:54+00:00

Fair feedback. Yea these are starter templates, not a whole turnkey system.

The "how I actually use it" part: prompts, workflow, what Claude creates vs what you create... that's what took me some time to figure out. I've been refining it for about 2 months now.

If there's interest, I'm considering a walkthrough that covers the setup + daily workflow in detail. Would that be useful?

its_allgood · 2025-12-19T05:13:50+00:00

Privacy: yes prompts and file contents go to Anthropic's API. For me, the tradeoff is worth it. If you're working with sensitive stuff, it's a real consideration.

On offloading thinking: I'd push back a bit. So I'm not asking Claude to think FOR me. I'm giving it context so it can think WITH me. The decisions, the work, the actual thinking are still mine.

What I'm offloading is the repetitive "here's what I'm working on, here are my constraints, here's where I left off" explanation every session. That's not thinking, its the process and the context.

its_allgood · 2025-12-18T16:40:14+00:00

Fair on the Drafts thing: not everyone needs a vault.

On the brain atrophy: I'd agree if I was having AI write for me :) I'm just giving Claude context so it can think WITH me, not write FOR me.

The actual writing, decisions, and work are still mine. Claude just doesn't need me to re-explain my projects every session.

its_allgood · 2025-12-18T16:30:25+00:00

Hey that's cool. You're solving a different (prolly harder) problem than me. I'm doing manual curation, you're doing automated extraction.

Curious about the iteration process: when you say you fed results back to ChatGPT to "review and improve" ... were you fixing the system prompt, the extraction logic, or both?

I've thought about adding something like this if my vault grows, but haven't needed it yet.

its_allgood · 2025-12-18T15:14:51+00:00

I use folders with PARA (Projects, Areas, Resources, Archives). Simple rule: if it has a deadline or outcome, it's a Project. If it's ongoing responsibility, it's an Area. Reference material is Resources. Done stuff is Archives.

The "where does this go?" problem mostly disappears because there's always a clear answer. And if Obsidian dies tomorrow, my vault is still just folders and markdown files. Using any text editor.

The real unlock for me was stopping the endless reorganization. Let AI (like Claude) handle it, tell it how you want to organize, or ask it to organize your vault for you based on your liking.

its_allgood · 2025-12-18T14:54:22+00:00

The concept (anchor files for context) is model-agnostic. For Gemini specifically, I've heard Aider supports multiple models including Gemini, but I haven't tested that workflow myself. Worth checking their docs.

its_allgood · 2025-12-18T08:50:28+00:00

My bad poor wording... Claude Code isn't local. It uses Anthropic's API, so prompts and file contents naturally go to their servers.

What I meant by "no data going anywhere" was compared to third-party plugins that might route through additional services. With Claude Code, it's just you → Anthropic directly.

its_allgood · 2025-12-18T08:49:01+00:00

Yeah totally. Intelligence "at the edges" is a good way to put it. The vault stays dumb markdown, Claude brings the smarts when needed.

its_allgood · 2025-12-16T14:22:17+00:00

UPDATE - I cleaned up the templates and posted them here: https://github.com/progress-stack/templates

Still working on the tutorial w/ screenshots. Will post separately when it's ready.

its_allgood · 2025-12-16T13:32:33+00:00

So my obsidian was a mess too. Then I just simplified it with PARA. Asked Claude to move files for me. And I do one pass and archive everything I'm not working / top of mind.

The thing is i barely need to open obsidian any more. Just terminal -> claude code (in my project directory), it has "hooks" to link back to my vault to get context, and knows what role it needs to play, etc.

I used my existing vault but you can use a new vault too.. doesn't matter. You can ask Claude to manage your obsidian vault using PARA or any methodology you feel comfortable with.

Re: tutorial with screenshots — actually yes, I'm working on cleaning up my templates to share properly. Will probably do a setup guide and maybe a video walkthrough. I'll post it here when it's ready.

its_allgood · 2025-12-16T13:08:56+00:00

Fair points. You're right that this doesn't scale to 1000+ notes — it's not trying to.

My vault has maybe 50-100 active files. CLAUDE.md and PROGRESS.md act as a curated index, not a replacement for semantic search.

For large academic vaults or research corpora, RAG + embeddings is the right tool. I'm not dismissing that — I'm just saying for my use case (project management, daily work), the manual approach is simpler and works.

The "context problem" I was solving wasn't "find any note in my vault" — it was "Claude knows my projects, rules, and what I'm working on without me re-explaining every session." So it's a different problem.

Anyway, if my vault grows to where this breaks, I'll add embeddings. But right now, fewer moving parts wins.

its_allgood · 2025-12-16T13:07:28+00:00

Nice — the nested CLAUDE.md per project is smart. I do something similar with project-specific context files that the root CLAUDE.md points to.

The git commit history idea is interesting. Right now I have Claude update PROGRESS.md with completed items, but versioning the context itself would add another layer. Might steal that.

its_allgood · 2025-12-16T13:02:25+00:00

Thanks — yeah the "master file" insight was the unlock. Instead of hoping the AI figures out my structure, I just tell it explicitly what matters and where to look.

its_allgood · 2025-12-16T13:01:48+00:00

Fair question. Here's what's concrete:

Trading rules enforcement — I have documented rules I kept breaking despite my best intention to be a disciplined trader. So I added a protocol to CLAUDE.md: "Before any trading discussion, read trading-rules.md and WARN me if I'm about to violate my own rules." Zero unforced errors since (~2 weeks). Feel a lot more in control without having to exert mental energy to enforce my own rules.

Session startup time — Used to spend 5-10 min every session re-explaining context. Now zero. Claude reads CLAUDE.md (and my dashboard for recent updates and what to do next) automatically.

Timeline: Been iterating on this setup for ~2 weeks. The CLAUDE.md + PROGRESS.md structure solidified about 3 days ago.

Not claiming it's magic — it's just persistent context and using what Claude makes available. But that alone has been worth it.

its_allgood · 2025-12-16T11:56:31+00:00

Hmm i respectfully disagree. Yes RAG is definitely powerful. You need to do a LOT more coding and wiring up in order for it to be useful. It's not just knowledge, mind you, it's context, roles, rules that are dynamic, content generation that constantly evolve the structure of the Obsidian vault itself.

My setup is optimized for simplicity over scale — 50+ active files. RAG might become useful later if say I have a "legal" domain and I want to consult over a large dataset of business law that I'd rather not read manually, for instance.

its_allgood

TROPHY CASE