dotmike

Hi HN!

So I built Claude Code Kit - a CLI that brings auto-activating skills to your tech stack. It makes Claude Code so more reliable.

Background:

A few days ago, u/JokeGold5455 (https://www.reddit.com/user/JokeGold5455/) on Reddit shared an amazing (https://www.reddit.com/r/ClaudeAI/comments/1oivjvm/claude_co...) post about their 6 months using Claude Code with custom skills, agents, and hooks. The "Holy Trinity" approach really resonated with me.

The problem the post highlighted stuck with me: skills just sit there unless you remember to use them.

What's a "kit"?

A kit is a framework-specific package (Next.js, React, Prisma, Express, etc.) that includes:

- Skill with best practices and patterns - Auto-activation triggers - skills activate when you mention keywords, edit specific files, or use framework terminology - Documentation organized by topic - Detection logic - automatically detects frameworks in your project

One command installs everything:

npx github:blencorp/claude-code-kit

It detects your stack, asks which kits to install, copies hooks/agents/skills to .claude/, and configures skill-rules.json for auto-activation.

Current kits (10):

Frontend: Next.js, React, shadcn/ui, Tailwind CSS, MUI, TanStack Router, TanStack Query

Backend: Express, Node.js, Prisma

This is brand new (literally a few hours old). I'm sure there are bugs and rough edges. Would love to get feedback on the approach, kit contributions (Vue, Angular, Svelte, Django, FastAPI, etc.) and issue requests for kits you'd like to see

Thanks again to u/JokeGold5455 for the inspiration!

I thought this document was so damning. What are your thoughts?

Decisions can be really useful to see not only why other users selected the stack they use, but also what related tools they used. The conversation that come out of that can be really informative to make a long term decision.

Not a problem; here are the answers

1. No, you do not need to format your calendar in any special way. We've developed a machine learning algorithm that automatically figures out the correct phone number and PIN number (if available). It works in 99.98% of the cases. In those rare cases that it misses, Callr will ask the user for a feedback and adjusts the algorithm based on that input.

2. There are a couple of important points; Callr only looks at a few days worth of events at a time and we did that by design. This will ensure that Callr does not have more information than it actually needs. Once the data is pulled, Callr is built like a fortress; we encrypt it with AES-256 to make sure it's fully locked. We wrote about clearly on our privacy page: http://www.getcallr.com/privacy-policy/

rhaco31, you are right. Callr, in its current form, solves the first big pain point which is remembering when your calls are and dialing them in. If it's a conference call with long PIN, it becomes really handy as well.

For the scenario you mentioned, the hope is the other party will start using Callr as well so that s/he will be on time. We built a 'Share the Love' feature so that our users can show them the light :-)

Does this adequately answers your question?

Thank you so much for the thoughtful response, prawn. Great suggestions and we'll make changes.

Hi yummyfajitas-

My apologies. I did not mean to spam anyone at all. I'll stop sending the emails.

Sorry again.

-Mike

Hello everyone, I'm Mike, co-founder and CEO of Callr. We're really excited to be able to share Callr with the community.

We built out of frustration we had of being late to conference calls and getting annoyed with PIN numbers. Instead of you remembering the time and number or pin to call, Callr will call you and then connects you to your calls (yes, it enters PIN numbers too!)

Hope you all find Callr useful to organize your day. It's been a Godsent for our team.

If you have any questions, I'll be happy to answer.

It's most likey the varnish cache playing trick. Please try it and let me know if you're seeing the Drupal favicon.

Good catch. We've updated it. Thanks for the heads up

dc_ploy-

the site is back up.. check it again.

The site is back up. Check it out at http://unfurlough.us

Also did some write up on the background if you're interested: http://www.blencorp.com/blog/2013/10/unfurlough-us-freelance...

josh_fyi-

We partnered with @1776dc who started a Google spreadsheet to pull together the information. They had about 30 or so gigs and freelancers and we imported it to our site.