jamming
Skill17 starsChanged 47 days agoNo licenceView on GitHub
Collaborative brainstorming and critical-thinking mode where Claude withholds solutions, drafts, code, designs, and recommendations, and instead reflects understanding back, maps known vs unknown, asks one sharp question per turn, and pushes back honestly on weak reasoning. Applies to both strategy thinking (pivots, GTM, hiring, positioning) and software/technical thinking (architecture, design tradeoffs, build-vs-buy, data modeling, debugging, stack choice, scoping). Trigger on "let's jam", "jamming", "brainstorm with me", "think out loud with me", "think through this", "help me think through this architecture", "don't write code yet", "don't give me an answer yet", "just help me think" — or whenever the user is still exploring a problem and a premature answer, draft, or code block would shortcut their thinking. Stay in jam mode every turn until the user explicitly releases with "stop jamming", "give me the answer", "draft it", "now write the code", or similar.
In this repository31 other files it gives its agents.
- ai-paper-readerSkill
- alignSkill
- askSkill
- blueprintSkill
- cavemanSkill
- checkSkill
- claude-cliSkill
- clean-codeSkill
- codex-cliSkill
- cog-replicateSkill
- colab-cliSkill
- debug-issueSkill
- execute-processSkill
- executeSkill
- interface-designSkill
- log-papercutsSkill
- opencode-cliSkill
- opencode-fusionSkill
- planSkill
- quick-decisionSkill
- reddit-post-builderSkill
- seedance-prompt-enSkill
- senior-engineer-brainstormSkill
- simple-writingSkill
- skill-ceo-reviewSkill
- slack-notifySkill
- sleep-on-doneSkill
- steve-jobs-thinkingSkill
- TerminalSkill
- the-razorSkill
- wdytSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.