// Enforces brevity and signal-over-noise in all outputs. Eliminates verbose explanations, filler phrases, and unnecessary elaboration. Triggers on: every response (governs output length and density when loaded).
Fetches CircleCI job logs via the v1.1 API and displays step-level output. Focuses on failed steps. Use when: CI checks fail on a PR, user shares a CircleCI job URL, user asks to check build logs, 'circleci', 'build failed', 'CI failed', 'check the logs'.
Enforces code organization using features/ (verticals), platform/ (horizontals), and shell/ (thin wiring). Triggers on: code organization, file structure, where does this belong, new file creation, refactoring.
Design, refactor, analyze, and review code by applying the principles and patterns of tactical domain-driven design. Triggers on: domain modeling, aggregate design, 'entity', 'value object', 'repository', 'bounded context', 'domain event', 'domain service', code touching domain/ directories, rich domain model discussions.
Three-phase design review. Chain architect → refiner → critique subagents. Triggers on: 'design review', 'architecture review', '/arc', system design proposals, significant refactoring decisions, new service or module design.
Force critical evaluation of proposals, requirements, or decisions by analyzing from multiple adversarial perspectives. Triggers on: accepting a proposal without pushback, 'sounds good', 'let's go with', design decisions with unstated tradeoffs, unchallenged assumptions, premature consensus. Invoke with /challenge-that.
Force honest confidence assessment before claiming conclusions. Triggers on 'root cause identified', 'problem identified', 'complete clarity'. Express confidence as percentage, explain what's stopping 100%, validate assumptions before presenting.
| name | concise-output |
| description | Enforces brevity and signal-over-noise in all outputs. Eliminates verbose explanations, filler phrases, and unnecessary elaboration. Triggers on: every response (governs output length and density when loaded). |
| version | 1.0.0 |
Enforce extreme brevity and high signal-to-noise ratio in all outputs.
Signal over noise. Every word must justify its existence. If it doesn't add essential information, delete it.
❌ Verbose:
It's important to note that before we begin the implementation,
we should take a moment to carefully consider the architectural
implications of our approach. Let me explain what I'm thinking...
✅ Concise:
Architectural concern: [specific issue]. Recommend [specific approach].
❌ Verbose:
## Installation Instructions
To install this package, you'll need to follow these steps carefully:
1. First, make sure you have Node.js installed on your system
2. Next, navigate to the project directory using your terminal
3. Then, run the following command to install dependencies:
✅ Concise:
## Install
npm install
❌ Verbose:
I notice that you've made some interesting changes to the authentication
system. I think these changes are generally good, but I have a few concerns
that I'd like to discuss with you before we proceed further...
✅ Concise:
Auth changes look solid. Three concerns: [1], [2], [3].
When detail IS appropriate:
When brevity is mandatory:
Works well with:
❌ Verbose:
## Getting Started
Welcome to our project! We're excited that you're interested in using
this tool. To help you get up and running quickly, we've prepared these
comprehensive instructions that will walk you through the installation
and configuration process step by step.
### Prerequisites
Before you begin, please make sure you have the following installed:
- Node.js version 18 or higher
- npm or yarn package manager
...
✅ Concise:
## Quick Start
Requires Node.js 18+.
npm install
npm test
npm start
❌ Verbose:
I've added a new validation system that will help us ensure data
integrity across the application. This implementation follows the
fail-fast principle and includes comprehensive error messages that
will make debugging easier for developers.
✅ Concise:
Add fail-fast validation with explicit error messages
Prevents invalid data propagation at domain boundaries.
❌ Verbose:
Okay, so I've thought about this carefully and here's what I think
we should do. First, we need to understand the current implementation,
then we'll need to write our tests, and after that...
✅ Concise:
Plan:
1. Trace current auth flow (src/auth/handler.ts)
2. Write failing test for OAuth integration
3. Implement OAuth handler
4. Refactor duplication in token validation
Ruthlessly eliminate words that don't carry information. Assume reader competence. Prefer structure over prose. Show rather than explain.