u/bjl218

This doesn't seem to be handled in the UI. I found some references to this which suggested a delete the project folder under ~/.claude/projects. I did that, but the project still shows up in the desktop app. I assume it must be cached somewhere that I can hopefully delete, but where? AIs including Claude itself give me incorrect information.

I have 2 Vercel + Supabase projects. Let's call them Project A and B. Project A already exists and will be used as the IdM. That is, Project B will authenticate against Project A*. I'm currently designing Project B. Project B will also need to access certain tables in Project A. Exact tables are TBD. AFAIK, the 2 primary ways to accomplish this are:

1. Project B uses the JWT obtained after authenticating with Project A to access Project A's tables via the Supabase API. Or use the service role (all business logic is in Vercel functions).
2. Use PostgresQL Foreign Data Wrappers (FDW). This seems conceptually straightforward, but the devil is in whatever details I'm not familiar with. AI tells me that this is not too difficult to configure.

There are, of course, other options like syncing the required Project A tables to Project B, but aside from the latency issues, that doesn't seem very robust.

I'd be interested in any other experiences and/or recommendations on best practices here.

*I'd actually like to use a 3rd-party IdM like Auth0 or Keycloak, but I haven't gotten that past the team yet.

I'm creating a skill which will be hosted in our private github repo. I've successfully configured that repo and installed my in-progress skill from that repo in Claude Code. Now I'm going to do iterative development on that skill and I don't want to have to push it to the Github repo and re-install it each time. I want to be able to modify the skill locally and have that change immediately available to Claude. I've learned about the --plugin-dir command-line argument to Claude. However, that apparently doesn't work in the Claude desktop app which where I'd prefer to test it.

I've noticed that when the skill is installed at user scope, a ~/.claude/plugins/installed_plugins.json file is created that includes the install path of the plugin. The install path includes the short commit SHA and there are additional properties including timestamps and the full commit SHA. I thought about creating a symlink from the installPath in the installed_plugins.json file to my local project. OR just continuing my development in Claude terminal rather than the Claude desktop app.

I think the correct approach might be to remove the marketplace-based install and do I manual install by creating a symlink in ~/.claude/skills:

cd ~/.claude/skills
ln -s <local_repo_root>/skills/<skill-name>

and this should work in both the Claude terminal and desktop apps. I've asked Claude about this, but its response was unclear.

How are other folks managing their local skill development environments?

All,

I am relatively new to Supabase although I have lots of experience deploying to Cloud environments where I had to roll my own environment/branching workflow. Typically, I'd define 3 full standalone environments/branches: dev, staging, production each with its own client and server stacks and database instance. Developers typically work directly in the dev branch or there own branches and then merges are done manually when its time to promote something to staging or production.

In my current gig, we are using Vercel and Supabase and so I'm wondering what branching/environment strategies folks are using. I know that both Vercel and Supabase support branches. And Supabase has some magic that will automatically instantiate an ephemeral DB instance when it detects a new PR and automatically apply schema migrations when the PR is merged into main (or whatever the production branch is).

But I can also see that with a little less magic and bit more work, Vercel/Supabase can support the "persistent" multi-environment branching to which I'm more accustomed as described above.

So I'm wondering what folks are doing in this area. Magic always worries me, but I'm willing to learn.

I had my first appointment with my provider since being on Medicare. My PCP is part of Beth Israel Lahey Health and is located in one of the hospital buildings. I received the eMSN for this visit and the claim included a note that said:

>B Payment was reduced because this service was performed in a hospital outpatient setting rather than a provider's office.

I haven't met my deductible yet and so I'm responsible for the (relatively small) amount. So, would I have been charged less if I had seen a provider that was not within the hospital? Or is this saying that they reduced the allowed amount, but the cost to me is still the same?

Edit: Just a note that I did chat with Medicare about this online, but their responses were confusing.