Add portable component-set guidance - #278
Closed
chailandau wants to merge 2 commits into
Closed
Conversation
A repo with a shared component set has already answered most composition questions in code. Enumerating that set in prose creates a list that goes stale the day a component is added, so the node carries how to read the set instead: props are the contract, usage frequency is the paved-road signal, and the smallest nearby view is the assembly reference. The node names no component and no path, so it holds for any repo. Repos bind their own directories and lookup commands in a context node beside it. Co-authored-by: Goose <opensource@block.xyz> Ai-assisted: true
Count across an area before treating one nearby view as the pattern. This keeps a singleton deviation from becoming precedent, and prompts agents to check whether a shared component already owns structural utility classes. Co-authored-by: Goose <opensource@block.xyz> Ai-assisted: true
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.
Why
Repos with shared component sets already encode their component contracts and composition patterns in source. Writing a parallel component inventory in a ghost package creates another list that can quietly drift.
What
standard.component-setnode to the default init skeletonRisk Assessment
Low. This adds one provisional guidance node to newly scaffolded packages and does not change existing packages or runtime behavior.
References
Validated through a Berd A/B exercise: the initial binding reproduced a singleton hand-rolled settings layout; the strengthened guidance selected the shared
SettingsSectioncomposition and passed the 8-item component-choice rubric.Generated with Goose