| name | description |
|---|---|
orchestrating-swarms |
Master multi-agent orchestration using Claude Code's TeammateTool and Task system. Use when coordinating multiple agents, running parallel code reviews, creating pipeline workflows with dependencies, building self-organizing task queues, or any task benefiting from divide-and-conquer patterns. |
Master multi-agent orchestration using Claude Code's TeammateTool and Task system.
This is not a proposal. This documents existing but hidden functionality found in Claude Code v2.1.19 binary, plus speculation on how it could be used.
TeammateTool already exists in Claude Code. We extracted this from the compiled binary at ~/.local/share/claude/versions/2.1.19 using strings analysis. The feature is fully implemented but gated behind feature flags (I9() && qFB()).
Applied rationality for a coding agent. Defensive epistemology: minimize false beliefs, catch errors early, avoid compounding mistakes.
This is correct for code, where:
<core_identity> You are an assistant called Cluely, developed and created by Cluely, whose sole purpose is to analyze and solve problems asked by the user or shown on the screen. Your responses must be specific, accurate, and actionable. </core_identity>
<general_guidelines>
This playbook provides a comprehensive guide to effectively prompting AI coding assistants. The key insight: the quality of AI-generated code is directly proportional to the quality of your prompts.
This gist outlines a highly effective and cost-optimized workflow for software development using Roo Code, leveraging a multi-model approach. This setup has been successfully used to build working applications, such as Baccarat game simulations with betting strategy analysis, and my personal portfolio site.
The power of this setup lies in strategically assigning different Large Language Models (LLMs) to specialized "modes" within Roo Code, optimizing for performance, cost, and specific task requirements.
Note
This is a re-post of the original article in dev.to. Dev.to has an abysmal bug where GIFs aren't displayed properly, rendering the article unreadable.
Around a year ago, I published the article “10 VS Code Vim Tricks to Boost Your Productivity ⚡”, which I shared various tips for the VSCodeVim extension. Turns out that the article was a hit, so allow me to share a few more VS Code Vim tips that I have up my sleeves 😆.
Prerequisites:
| <tutor_mode_instructions> | |
| You are a friendly computer science tutor, and I am the student. Your role is to guide me through learning step by step. | |
| - **Assess my knowledge** | |
| - First, ask me my name and what I want to learn. Determine where to start based on my experience. Also ask me if there's anything I'm interested in that you can incorporate into the lessons (i.e. shows, hobbies, interests, etc). | |
| - Ask me these questions one a a time. | |
| - **Teach using code** | |
| - Teach me concepts in the chat window, and create files as "lessons" when you need to demonstrate something. Use the naming format 001-lesson-[lesson-slug], like 001-lesson-about-file.py, or whatever the equivalent is in the language I'm learning. Start with a 0-padded 3 digit number. | |
| - Write code and explain how to run it. When you are teaching me, do not run any commands for me. Just tell me what to run, and once you've taught me how to run something, encourage me to run commands myself. In the beginning, encourage me to share what I sa |
| # Setup ENV | |
| FZF_TAB_PLUGIN=$HOME/src/fzf-tab/fzf-tab.plugin.zsh | |
| BREW_PREFIX="$(brew --prefix)" | |
| # Enable brew zsh-completions | |
| if type brew &>/dev/null; then | |
| FPATH=${BREW_PREFIX}/share/zsh-completions:$FPATH | |
| autoload -U compinit | |
| compinit |
