task-observer: docs/ai/writing-docs updates from 2026-05-18#23
Open
divad12 wants to merge 1 commit into
Open
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Target\nglobal-doc: docs/ai/writing-docs.md\n\n## Observations addressed\n- Observation 1 (dotfiles/log.md): Compression can weaken corrective guardrails → changed: added rule to preserve enforcement strength (wording that counters known failure modes) even when cutting for context budget\n- Observation 2 (dotfiles/log.md): Explain why guardrails exist when model behavior depends on it → changed: added rule to keep rationale for judgment-heavy rules, since stripping the "why" turns a calibrated rule into a bare imperative\n- Observation 3 (dotfiles/log.md): Code guardrails need failure-mode rationale → changed: added rule to preserve failure-mode context (what goes wrong, stop-signal thought pattern, safe alternative) for hard rules\n- Observation 4 (dotfiles/log.md): Positive phrasing is better for tradeoff guidance → changed: added rule to prefer positive phrasing when the correct alternative is simple and actionable\n\nAll four observations target the same compression scenario and are grouped into a new "When Tightening Existing Instructions" section in writing-docs.md, placed after the general Contract bullet list.
Generated by Claude Code