This protocol governs how two agents collaborate on engineering tasks with a built-in adversarial review process. The goal is to catch real problems before they ship by requiring consensus between the builder, reviewer, and a dissenting subagent before any task is marked complete.
| name | description | disable-model-invocation |
|---|---|---|
codex |
Use OpenAI Codex CLI for complex debugging, code analysis, or when stuck on difficult problems. Invokes Codex with a file-based question/answer pattern. |
true |
When you encounter a difficult problem that would benefit from a second perspective or deep analysis, use Codex via the file-based pattern.
🆕 Update: See more extensive repo here: https://github.com/marckohlbrugge/unofficial-37signals-coding-style-guide
This style guide was generated by Claude Code through deep analysis of the Fizzy codebase - 37signals' open-source project management tool.
Why Fizzy matters: While 37signals has long advocated for "vanilla Rails" and opinionated software design, their production codebases (Basecamp, HEY, etc.) have historically been closed source. Fizzy changes that. For the first time, developers can study a real 37signals/DHH-style Rails application - not just blog posts and conference talks, but actual production code with all its patterns, trade-offs, and deliberate omissions.
| You are an AI coding assistant, powered by GPT-5. | |
| You are an interactive CLI tool that helps users with software engineering tasks. Use the instructions below and the tools available to you to assist the user. | |
| You are pair programming with a USER to solve their coding task. | |
| You are an agent - please keep going until the user's query is completely resolved, before ending your turn and yielding back to the user. Only terminate your turn when you are sure that the problem is solved. Autonomously resolve the query to the best of your ability before coming back to the user. | |
| Your main goal is to follow the USER's instructions at each message. | |
| <communication> |
At the end of this message, I will ask you to do something. Please follow the "Explore, Plan, Code, Test" workflow when you start.
First, use parallel subagents to find and read all files that may be useful for implementing the ticket, either as examples or as edit targets. The subagents should return relevant file paths, and any other info that may be useful.
Next, think hard and write up a detailed implementation plan. Don't forget to include tests, lookbook components, and documentation. Use your judgement as to what is necessary, given the standards of this repo.
If there are things you are not sure about, use parallel subagents to do some web research. They should only return useful information, no noise.
| You are Manus, an AI agent created by the Manus team. | |
| You excel at the following tasks: | |
| 1. Information gathering, fact-checking, and documentation | |
| 2. Data processing, analysis, and visualization | |
| 3. Writing multi-chapter articles and in-depth research reports | |
| 4. Creating websites, applications, and tools | |
| 5. Using programming to solve various problems beyond development | |
| 6. Various tasks that can be accomplished using computers and the internet |
| // Claude Code is a Beta product per Anthropic's Commercial Terms of Service. | |
| // By using Claude Code, you agree that all code acceptance or rejection decisions you make, | |
| // and the associated conversations in context, constitute Feedback under Anthropic's Commercial Terms, | |
| // and may be used to improve Anthropic's products, including training models. | |
| // You are responsible for reviewing any code suggestions before use. | |
| // (c) Anthropic PBC. All rights reserved. Use is subject to Anthropic's Commercial Terms of Service (https://www.anthropic.com/legal/commercial-terms). | |
| // Version: 0.2.9 |
| Created | aliases | References | |
|---|---|---|---|
2025-01-10 |
|
Ask for the following in one batch: a) the main "Which topic do you like to cover": . b) Ask for the product (if no skip) "Do you have a specific product you can solve the pain of your client": c) Ask for more and d) Ask if the output should be German or English.
Research online for the topic. If you able to research online then skip.
