[Copilot]

Codify the guidance from #8450: prefer React elements for slot-based props such as leadingVisual, trailingVisual, and icon, enabling composition across Server/Client Component boundaries.

Changelog

New

• API guidance: Prefer elements over component types; distinguish ReactElement from ReactNode and reserve render props for state-dependent content.
• Examples: Contrast component-type and element-based usage, preserving backwards compatibility for existing APIs.

Changed

• Updated the style guide table of contents.

Removed

None.

Rollout strategy

• None

Testing & Reviewing

Review the new Props guidance against #8450; no component APIs change.

[changeset-bot]

⚠️ No Changeset found

Latest commit: f8526ed

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[joshblack]

@copilot instead of putting this in our style guide, put it in our style guide skill

[Copilot]

@copilot instead of putting this in our style guide, put it in our style guide skill

Moved the guidance and examples into .github/skills/style-guide/SKILL.md and restored contributor-docs/style.md to its pre-PR state in 5e7f868. Formatting and Markdown lint passed.

[joshblack]

@copilot update the style-guide skill to include instructions on how to update it. The skill itself should be minimal, with the table linking out to topics. When updating or adding to the skill, things should go under existing topics or new topics. This addition should be under a new topic for component prop types

[Copilot]

@copilot update the style-guide skill to include instructions on how to update it. The skill itself should be minimal, with the table linking out to topics. When updating or adding to the skill, thing...

Updated in ac37b2c: SKILL.md now has maintenance instructions and a table entry linking to docs/component-prop-types.md, which contains the slot-prop guidance and examples. Formatting and Markdown lint passed.

[Copilot]

Copilot review overview

🟢 Approval recommended

The documentation is accurate, consistent with the referenced API direction, and requires no changeset.

Review effort: Balanced
Findings: None

What changed in this PR

Documents preferred React element usage for slot-based props, improving Server/Client Component interoperability without API changes.

Changes:

• Adds prop-type guidance and examples.
• Links the guidance from the style-guide index.

File	Description
.github/​skills/​style-guide/​SKILL.md	Adds the prop-types topic and maintenance guidance.
.github/​skills/​style-guide/​docs/​component-prop-types.md	Documents element-based slot prop conventions.

---

💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.

[joshblack]

@copilot prefer React.ReactNode over React.ElementType since it makes it easier to use (for example, you can conditionally apply a leadingVisual with React.ReactNode but with ElementType you cannot)

[Copilot]

@copilot prefer React.ReactNode over React.ElementType since it makes it easier to use (for example, you can conditionally apply a leadingVisual with React.ReactNode but with ElementType you cannot)

Updated the style-guide topic to recommend React.ReactNode for slot props and show conditional visual content. Committed as f297618.

[joshblack]

@copilot prefer React.ReactNode actually instead of React.ElementType. Also don't call out to the PR for this.

[Copilot]

@copilot prefer React.ReactNode actually instead of React.ElementType. Also don't call out to the PR for this.

The topic now foregrounds React.ReactNode for slot props and no longer references the PR. Committed as f8526ed.