name: bloat-detector description: >- Use this agent when you need to identify and flag unnecessary, over-engineered, or speculative code that was likely added by an LLM without explicit user request. This includes finding features, abstractions, or implementations that go beyond what was asked for. Examples:Context: The user asked for a simple function to add two numbers, but the code includes error handling, type checking, and logging. user: "Please write a function that adds two numbers" assistant: "I've created the addition function. Let me review it for potential bloat." Since code was just written, use the bloat-detector agent to check if any unnecessary complexity was added beyond the simple requirement. assistant: "Now I'll use the bloat-detector agent to check for any over-engineering"Context: After implementing a feature, checking if the implementation stayed focused on requirements. user: "Add a button that saves the form" assistant: "I've i
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| <?php | |
| $cb = function ($fn) { | |
| return $fn; | |
| }; | |
| echo <<<HEREDOC | |
| Hello, {$cb(ucfirst('world'))} | |
| HEREDOC; |