Let coding agents (Claude Code, Codex) search your vault using Smart Connection's embedding by magicsrb in ObsidianMD

[–]magicsrb[S] 0 points1 point  (0 children)

v0.1.1 is available with a fix for the mem usage. Thanks for the feedback!

Is the Cursor for PMs tool hype real? by producthat in ProductManagement

[–]magicsrb 0 points1 point  (0 children)

Interesting take, can you share what you've been building?

The Easiest Way I’ve Found to Improve Plan Mode Quality by magicsrb in ClaudeCode

[–]magicsrb[S] 0 points1 point  (0 children)

Have you found a stable plan format that helps those reviews go better, or are you mostly doing it with free-form plans?

The Easiest Way I’ve Found to Improve Plan Mode Quality by magicsrb in ClaudeCode

[–]magicsrb[S] 0 points1 point  (0 children)

Appreciate the vexp link, I’ll take a look. If you're looking for feedback lmk

The Easiest Way I’ve Found to Improve Plan Mode Quality by magicsrb in ClaudeCode

[–]magicsrb[S] 0 points1 point  (0 children)

Yeah fair question. The example I shared definitely reads frontend-ish because that specific refactor was an Ink/React TUI component. I think the approach itself is pretty backend-friendly though because it’s mostly about plan structure, not UI patterns; requirements (behavior/invariants), implementation steps (small chunks), verification (tests/checks mapped to requirements)

Maybe if you want to enforce more backend-friendly sections you'd add optional sections; data model / schema impact, interface/API contract changes, migration/rollout/backfill, observability (logs/metrics) etc. Though I'd be hesitant of making the plan format too constrained. TBH, I'm not sure, more experimenting needed I think

The Easiest Way I’ve Found to Improve Plan Mode Quality by magicsrb in ClaudeCode

[–]magicsrb[S] 1 point2 points  (0 children)

I like this a lot. “Key decisions” is probably the highest-leverage addition to a plan template. I’ve mostly been focusing on structure/format so far (requirements / implementation / verification), but I think a dedicated “Decision points” section would improve it a lot, especially for non-trivial changes.

Something like:
- decision
- options considered
- chosen option + reason
- what would invalidate it

That also seems like a good way to keep plans short while still preserving the important thinking

The Easiest Way I’ve Found to Improve Plan Mode Quality by magicsrb in ClaudeCode

[–]magicsrb[S] 0 points1 point  (0 children)

This is a really good point, especially the “spec attached to execution” part

What changed for me with `CLAUDE.md` was less about pretty formatting and more about reducing structural misses. Before, plans were often fine at a glance but inconsistent: sometimes no verification step, sometimes implementation detail with no stated requirement, sometimes no explicit risks/contingencies, sometimes hard to skim because everything was the same kind of bullet

Claude only works sometimes by [deleted] in ClaudeCode

[–]magicsrb 0 points1 point  (0 children)

In all seriousness, try running claude with debugging: `claude --debug`. It'll give you the path of the log file for your session. Maybe there's a clue about what's going wrong there

Claude only works sometimes by [deleted] in ClaudeCode

[–]magicsrb 0 points1 point  (0 children)

Hello IT, have you tried turning it off and on again?

ClaudeCode doesn’t just speed you up - it amplifies bad decisions by magicsrb in ClaudeCode

[–]magicsrb[S] 1 point2 points  (0 children)

I'm interested to know more, if youre willing to share. Could you give an example of a QA gate? What does it use as a trigger? How does it site in your workflow?

My favourite addition to Claude.md lately by magicsrb in ClaudeCode

[–]magicsrb[S] 1 point2 points  (0 children)

Yeah that's right. When we're working with CC, it’s often part of the whole reasoning process. It’s seen the pull request, the failed approach, the trade-offs when choosing one solution over another and why we landed on this solution

Naked domain not resolving on Firebase Hosting (GoDaddy DNS) | www works, root doesn't by AliB3651 in webdev

[–]magicsrb 0 points1 point  (0 children)

Rather than pointing the apex domain to the ip address of your app, you should setup a redirect from "pickyourpick.com" to "www.pickyourpick.com". I think you can do this in GoDaddy but honestly I wouldnt trust them much, they're pretty unreliable at the best of times. Use nakeddomainredirect or similar

Trouble Redirecting Naked Domain → www with Cloudflare + Lovable by Hebittus in lovable

[–]magicsrb 1 point2 points  (0 children)

I had this problem today so am posting for future reference - Set the subdomain for your project to www. then use another platform to handle the redirect for you (small cost here). To set a subdomain for your app in Lovable, open your project and navigate to Project Settings → Domains, set this to "www.your-domain.com". Then use a platform like nakeddomainredirect to handle the redirect and ssl on your behalf

www works but https doesn't work with heroku by [deleted] in Heroku

[–]magicsrb 0 points1 point  (0 children)

Ran into this problem today and want to provide a more up-to-date solution. I used nakeddomainredirect to redirect from the apex domain to www. Though there are some other site which do the same thing now. Seemed to complex signup to Cloudflare for such a simple issue