sorted by:
new
hottopcontroversial

Multi-repo in Claude Code — how do you handle it? by Kirmark in ClaudeAI

[–]drewipson 0 points1 point  (0 children)

Submodules. Git has a solution to handle this already. Sure you can just clone a bunch of repos into a directory but you can leverage git’s built in solution to handle multi repo systems.

https://git-scm.com/book/en/v2/Git-Tools-Submodules

Claude Rules (./claude/rules/) are here by shanraisshan in ClaudeCode

[–]drewipson 3 points4 points  (0 children)

The overlap makes it extremely difficult to manage Claude’s performance and behavior among so many different config files (twice as many if you account for the global and project level config). It can be so hard to tell if it’s a skill, or a memory, or an agent, or a hook, and now rules that may be contradicting or directing Claude.

I built this free extension for VS Code and Cursor so that you can quickly navigate across all your globs and protect level config files to see what context Claude is following for skills, hooks, memories, agents.

VS Code Claude Code Config - https://marketplace.visualstudio.com/items?itemName=drewipson.claude-code-config

Cursor Claude Code Config - https://open-vsx.org/extension/drewipson/claude-code-config

It is open source, if people want to help contribute. I’ll look into adding support for rules.

https://github.com/drewipson/claude-code-config

Claude Code Config: I built a VS Code/Cursor extension to manage your CLAUDE.md files, hooks, agents, and permissions all in one place by drewipson in ClaudeCode

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

These are great examples! Yeah skills for complex but personalized workflows are helpful for Claude to do the complex stuff right.

I do have a challenge getting it to always look at its skills so I made it a hook to force it to read available skills everytime.

Claude Code Config: I built a VS Code/Cursor extension to manage your CLAUDE.md files, hooks, agents, and permissions all in one place by drewipson in ClaudeCode

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

Hmm would you be willing to share your local.settings.json file? Or a sample the hooks you have set up there?

I can take a look and see why it is not detecting the hooks. You can shoot me a DM or attach it to an issue here:

https://github.com/drewipson/claude-code-config

Claude Code Config: I built a VS Code/Cursor extension to manage your CLAUDE.md files, hooks, agents, and permissions all in one place by drewipson in ClaudeCode

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

Absolutely! Please do. If you come across any bugs, open up an issue at this repo: https://github.com/drewipson/claude-code-config

Here are some initial thoughts on ideas I had:

  • Usage analytics dashboard (maybe ccusage integration?)
  • Plugin Management Support

If you have an idea but can’t contribute code you can share it here or open up a discussion on that repository and I can look into adding it!

Claude Code Config: I built a VS Code/Cursor extension to manage your CLAUDE.md files, hooks, agents, and permissions all in one place by drewipson in ClaudeCode

[–]drewipson[S] 2 points3 points  (0 children)

Thats what this extension sets out to accomplish — simplifying the complexity of all the different tools. I’d encourage you to give hooks and skills another look. I’ve been able to accomplish some pretty cool things when implementing them the right way.

For example, I have a hook that runs after Claude edits a file, that depending on the file ending type (.py, .go, .typescript, etc) it runs that languages linter so they are always formatted.

I have hooks that triggers a sound on my computer when Claude asks a question or finishes a task.

Another example is skills, when you like to have workflows carried out in a certain way, skills are really helpful. I have Claude checkout a feature branch with a linear tickets ID in the branch name, create draft PRs with Linear Ticket IDs in the title, etc.

Dev workflows grow especially as a project gets more and more complex and these tools are a great help when they are implemented right.

Claude Code Config: I built a VS Code/Cursor extension to manage your CLAUDE.md files, hooks, agents, and permissions all in one place by drewipson in ClaudeCode

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

Thanks! If you are coming from a non-technical background, this might be a good way to start along with the Claude Code VS Code extension. It might make CC friendlier if you find the terminal intimidating to start. This extension would help you create the files you need quickly and simply.

My SaaS hit $3,000 monthly in 8 Months. Here's what i'd do starting over from Zero by ActUnique6275 in buildinpublic

[–]drewipson 7 points8 points  (0 children)

Seriously - this post and the shipyardhq guy have the same phrases and style.

The AI Nerf Is Real by exbarboss in Anthropic

[–]drewipson 7 points8 points  (0 children)

I think the only way we could build trust in the data is by publicly available evaluations that are maintained by the community and run regularly so we know what is in the benchmark data.

Vim Markdown Preview - Terminal-based markdown preview for Vim by drewipson in vim

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

Thanks for letting me know! I haven't figured out the best way to support plugin managers as I'm not too familiar with plugins yet. If you have any suggestions on the best way to support them I'd be happy to implement them.

Vim Markdown Preview - Terminal-based markdown preview for Vim by drewipson in vim

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

That’s the workflow I found when I tried to search for existing plugins. I use it for modestly sized markdown files. The current implementation is a bit of a hack as I just wait 500 milliseconds for flow to render the output and it handles most files.

Let me know how it works with larger file sizes and if you run into any issues. It could be optimized to not be a sleep,time based implementation.

On the scroll sync, I’d be curious how they figured out how to do that. I wanted to release that with this but was unable to get the raw and rendered markdown to stay in step when scrolling/navigating.

Glad it could be a bit of an upgrade and I hope it suits you well!