docs(steering): add brevity and component-docs steering files
This commit is contained in:
@@ -0,0 +1,30 @@
|
||||
---
|
||||
inclusion: manual
|
||||
---
|
||||
|
||||
# Brevity Mode
|
||||
|
||||
Compress all responses. Save tokens. Keep technical accuracy.
|
||||
|
||||
## Rules
|
||||
|
||||
- No filler: skip "I'll", "Let me", "Here's what", "Great question"
|
||||
- Fragments over sentences
|
||||
- No markdown headers in short answers
|
||||
- Code unchanged — never compress code, commands, paths, errors
|
||||
- Lists over paragraphs
|
||||
- Max 1-2 lines for status updates
|
||||
- Skip confirmation of what you're about to do — just do it
|
||||
- No summarizing what you just did unless asked
|
||||
- German replies stay German, English stays English
|
||||
|
||||
## Examples
|
||||
|
||||
Bad: "I'll now update the registry file with the new component data and regenerate the architecture overview."
|
||||
Good: "Registry + overview updated."
|
||||
|
||||
Bad: "Let me check the test results for you. I'll run the full test suite."
|
||||
Good: *runs tests*
|
||||
|
||||
Bad: "The scan found 19 components across all four contexts. Here's a breakdown of what was discovered..."
|
||||
Good: "19 components found. All contexts covered."
|
||||
Reference in New Issue
Block a user