Business-folder skill: user-facing copy is never a private copy - #93
Draft
lucasrcezimbra wants to merge 1 commit into
Draft
Business-folder skill: user-facing copy is never a private copy#93lucasrcezimbra wants to merge 1 commit into
lucasrcezimbra wants to merge 1 commit into
Conversation
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
lucasrcezimbra
marked this pull request as draft
August 18, 2026 00:57
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.
The lesson
The business-folder skill's shared-utility preference list says a small utility two files need should stay a private copy in each. Applied to a utility that carries user-facing copy, that rule tells a future agent to fork error messages — and two copies of the same owner-facing sentence drift apart the first time one is reworded, which is a product bug the gates cannot see.
The change
One paragraph under the preference list, mirroring the existing 'Option 3 is not available to Kysely query fragments' carve-out: option 2 is not available to user-facing copy — it lives once in the owning domain's
.common.ts(already 'importable from anywhere' by the skill's own definition), and every consumer imports it.Evidence
PR #90 gave
messages_fetchthe same Discord-link validationbookmarks_addperforms. At two consumers, the skill as written prescribed a private copy in each domain file, which would have forked the three refusal sentences between two tools; the build diverged —messageLinkTargetand its copy moved tomessages.common.ts, shared verbatim — and argued the divergence in that PR. This codifies the ruling so the next copy-bearing utility doesn't have to re-argue it.Note: this contingently assumes #90's divergence is accepted — if you reject that shape there, reject this PR with it.
🤖 Generated with Claude Code