Repository navigation
STUDIO.md: State the core-files rule once, with its reason - #5210
Merged
Merged
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
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.
Related issues
STUDIO.mdinstructions that repeat something else.How AI was used in this PR
Claude (via the Pi coding agent in a Roadie session) found the repeated rule, wrote the change, and drafted this description. I reviewed the change and the reasoning.
Proposed Changes
STUDIO.mdsays "don't editwp-includes/orwp-admin/" five times: in the Constraints table, twice in "Use hooks, not direct edits" (the rule and a code comment), in "When to Create vs. Modify", and again in "Studio-Specific Notes".This keeps it once, in "Use hooks, not direct edits", the only place that gives the reason (core edits are overwritten on every WordPress update) and shows the alternative (the
add_actionexample). The other four go. That paragraph now reads as what to do: extend through hooks in a plugin or theme, and leave core as shipped.Net: 2 lines added, 10 removed, in
skills/STUDIO.mdonly. It's a managed file, so existing sites pick it up the next time they start (updateManagedInstructionFiles).Testing Instructions
STUDIO.md.grep -n "wp-includes" STUDIO.mdreturns one line, under "Use hooks, not direct edits".npx vitest run packages/common/lib/tests/agent-skills.test.tspasses (17). No eval: Studio Code doesn't load this file, which only reaches external agents opened in a site folder. The rule itself is unchanged; only its copies are removed.Pre-merge Checklist