Skip to content

docs: document rules as HCF-only in plugin-design - #165

Open
unional wants to merge 1 commit into
mainfrom
docs/rules-hcf-only
Open

unional wants to merge 1 commit into
mainfrom
docs/rules-hcf-only

Conversation

@unional

@unional unional commented Oct 8, 2026

Copy link
Copy Markdown
Contributor

Adds a Rules vs References section to the plugin-design reference: always-on content is the HCF of all agents, rules/ stays for that narrow case, and role- or task-scoped guidance ships as a reference loaded on demand. Folds the existing always-on decision tree into it and adds a matching anti-pattern.

Closes #4

🤖 Generated with Claude Code

Add a Rules vs References section: always-on content is the highest
common factor of all agents, rules/ stays for that narrow case, and
role- or task-scoped guidance ships as a reference loaded by name.

Closes #4

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@changeset-bot

changeset-bot Bot commented Oct 8, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: b00dc51

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
universal-plugin Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

docs: clarify rules scope — HCF-only in orchestrative multi-agent systems

1 participant