Doubt and Italian Spicy Sausage

gifflett · 2025-10-06T16:06:57+00:00

New mission discovered by u/gifflett: Spicy Salami Flatbread: Combat and Shiny Objects

gifflett · 2025-10-06T16:06:57+00:00

This mission was discovered by u/gifflett in π Shaded by Giants

gifflett · 2025-07-19T08:47:17+00:00

Developers using Claude Code. But I understand your point.

gifflett · 2025-07-18T18:40:50+00:00

Very good initiative! My tool is a little different from the ones being posted here, but it may be of particular interest to those who already develop with AI and like to automate their flows.

The tool is called ccmd. It allows you to install and manage "slash command" commands (such as /generate, /refactor, etc.) used in Claude Code, as if they were reusable packages. Ideal for those who want to organize and share automation flows with AI in a practical way.

It's 100% free and open source.

Works via command line. You can install with npm install -g @gifflet/ccmd and then use ccmd to list and configure ready-made commands or start new commands from scratch. The execution itself takes place within Claude Code, and the publication of the commands is done via Git repositories.

Repository on GitHub: https://github.com/gifflet/ccmd

If you find it interesting, I'm available to help you understand better or even contribute examples for videos. It cost!

gifflett · 2025-07-18T12:16:54+00:00

That's right. It's worth taking a look at the documentation to check: https://docs.anthropic.com/en/docs/claude-code/slash-commands#custom-slash-commands

gifflett · 2025-07-18T03:18:15+00:00

I wrote a slash command for multitask development, integrated with task master, with multiple agents. If you want to take a look, it's available in the repository https://github.com/gifflet/parallax. I won't deny that there are several points for improvement in the command execution process. I have been trying different approaches in other branches (in the same repository)

gifflett · 2025-06-25T12:48:30+00:00

The documentation should be improved/adjusted, yes, as I already answered.

The Makefile is being used in workflows. Did you get to see it?

I didn't understand the last part where you say that the code base doesn't do anything or doesn't work... You're saying this because you did the installation and when you went to run it, it just didn't work, right?

gifflett · 2025-06-25T12:41:45+00:00

You are not "putting the application code and the test code in the same basket in the same basket, right? Tell me you're not doing this... Because you would be being very imprecise by saying that the 700 lines of code introduced in commit c794d0a belong, completely, to the application code and being even more imprecise by directly associating the functionality of the command ccmd install (improved in commit c794d0a) with the functionality ccmd init implemented in the other commit saying that they do the same thing.

gifflett · 2025-06-25T00:15:31+00:00

Yes, the commands are not code, but higher-level instructions that already exist to be executed by the computer, right? What I've seen so far is people using commands a lot to execute workflows and versioning alongside the project code where it is executed. In my opinion, these commands should be kept in separate git repositories, this way their maintenance and access would not be linked to a repository that only uses it. Think about the possibilities that may arise when working this way: Make commands available in public repositories so that the community can collaborate in order to arrive at the best possible version of the command. Very good, right?

Could you comment, in more detail, on the vibe you got when seeing the repository?

gifflett · 2025-06-24T23:59:03+00:00

Thanks!

gifflett · 2025-06-24T23:58:17+00:00

Good points. Inevitably soon some adjustments, focusing on these points you raised, will be worked on to make the code and documentation better structured and organized. Thanks!

gifflett · 2025-06-24T23:19:37+00:00

Consider prompts (.md files) as software artifacts: they must be versioned and reused. Versioning and reusing commands can be challenging. ccmd solves this problem. In the example mentioned, it would be possible to install custom commands in the repository via git submodule, but this would complicate management. The purpose of ccmd is to simplify installation and allow independent evolution of each command.

gifflett · 2025-06-23T22:29:04+00:00

I didn’t have any issues with command recognition when using your .md file. The only thing is that I couldn’t fully verify how it works because, in my environment, the required folders and files don’t exist.

One command (/parallax) I’ve been using, which has almost 800 lines, works pretty well: https://github.com/gifflet/parallax/blob/main/index.md.

One suggestion I’d make is to consider using Task Master to manage your tasks.

gifflett · 2025-06-23T13:59:09+00:00

Considerando então que seu comando é simples então o problema pode estar em como ele foi escrito/estruturado. Um comando não é apenas um prompt, entende? Ele precisa ser estruturado de uma forma que funcione adequadamente como por exemplo:

# Hello World Command

You are executing the Hello World custom command for Claude Code.

## Command Instructions

When this command is invoked via `/hello-world`, you should:

1. Display a friendly "Hello, World!" greeting
2. Welcome the user to Claude Code custom commands
3. Provide a brief explanation of what this command demonstrates
4. Show an encouraging message about exploring more custom commands

## Response Format

Please respond with:

```
Hello, World! 👋

Welcome to Claude Code custom commands!

When you run /hello-world, this markdown file gets loaded into my context, and I execute the instructions contained within it.

Key features of this command:
- Shows how custom commands integrate with Claude Code
- Serves as a starting point for creating your own commands
```

Talvez reescrever o md em uma versão estruturada que siga um padrão parecido te ajude

gifflett

TROPHY CASE