OpenSource/agent-skills
1
0 Fork 0
mirror of https://github.com/addyosmani/agent-skills.git synced 2026-10-26 15:05:04 +00:00
Code Issues Packages Projects Releases Wiki Activity

Soften prescriptive language for Claude 4.6 compatibility

Browse Source 
Anthropic's Claude 4 prompting best practices document warns that
newer models overtrigger on strong directive language (Never/Always/MUST)
that was necessary for older models. This replaces aggressive directives
with natural phrasing across skills and agents while preserving all
security-critical rules (OWASP, prompt injection, secrets) unchanged.

Also reframes trunk-based development as "Recommended" with a note
acknowledging alternative branching strategies like gitflow.
This commit is contained in:
Federico Bartoli committed 2026-03-31 19:29:59 +02:00
1 parent 9aed668c49
commit 702a894889
13 files changed
+32 -30
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

skills/code-simplification/SKILL.md
+3 -3
View File
@@ -31,7 +31,7 @@ Simplify code by reducing complexity while preserving exact behavior. The goal i
### 1. Preserve Behavior Exactly
Never change what the code does — only how it expresses it. All inputs, outputs, side effects, error behavior, and edge cases must remain identical. If you're not sure a simplification preserves behavior, don't make it.
Don't change what the code does — only how it expresses it. All inputs, outputs, side effects, error behavior, and edge cases must remain identical. If you're not sure a simplification preserves behavior, don't make it.
```
ASK BEFORE EVERY CHANGE:
@@ -156,7 +156,7 @@ Scan for these patterns — each one is a concrete signal, not a vague smell:
### Step 3: Apply Changes Incrementally
Make one simplification at a time. Run tests after each change. **Always submit refactoring changes separately from feature or bug fix changes.** A PR that refactors and adds a feature is two PRs — split them.
Make one simplification at a time. Run tests after each change. **Submit refactoring changes separately from feature or bug fix changes.** A PR that refactors and adds a feature is two PRs — split them.
```
FOR EACH SIMPLIFICATION:
@@ -166,7 +166,7 @@ FOR EACH SIMPLIFICATION:
4. If tests fail → revert and reconsider
```
Never batch multiple simplifications into a single untested change. If something breaks, you need to know which simplification caused it.
Avoid batching multiple simplifications into a single untested change. If something breaks, you need to know which simplification caused it.
**The Rule of 500:** If a refactoring would touch more than 500 lines, invest in automation (codemods, sed scripts, AST transforms) rather than making the changes by hand. Manual edits at that scale are error-prone and exhausting to review.