The ponytail: comment marker was being over-applied to trivial code (#120). Narrow the rule so only deliberate simplifications that cut a real corner with a known ceiling get a comment, and keep the `ponytail:` prefix that /ponytail-debt greps for. Applied across all rule copies, SKILL.md, AGENTS.md, the fallback instructions, both command files, and the Qoder/OpenCode copies that #491 missed; .openclaw regenerated. helpers.test.js now pins the prefix so it cannot silently drop again. Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 4.8
parent
65db9025a7
commit
b6c04480c0
@@ -2,4 +2,4 @@
|
||||
description: Switch ponytail intensity level (lite/full/ultra/off)
|
||||
---
|
||||
|
||||
Switch to ponytail $ARGUMENTS mode. If no level specified, use full. Lazy senior dev mode, before any code: does it need to exist at all (YAGNI)? Does the standard library do it? A native platform feature? Can it be one line? Build the minimum that works. No unrequested abstractions, no avoidable dependencies, no boilerplate. Mark intentional simplifications with a ponytail: comment.
|
||||
Switch to ponytail $ARGUMENTS mode. If no level specified, use full. Lazy senior dev mode, before any code: does it need to exist at all (YAGNI)? Does the standard library do it? A native platform feature? Can it be one line? Build the minimum that works. No unrequested abstractions, no avoidable dependencies, no boilerplate. Mark deliberate simplifications that cut a real corner with a known ceiling using a ponytail: comment that names the ceiling and upgrade path.
|
||||
|
||||
Reference in New Issue
Block a user