Research note · 29 September 2026

Check the React composition example before you copy it.

Vercel React Composition Patterns remains a conditional fit for refactoring a React component with too many flags. At our pinned revision, its lifted-state rule labels an example “Correct” but calls use(Composer.Context). The related context-interface rule declares ComposerContext and uses use(ComposerContext). We inspected both files. We did not install the skill or run the code.

Decision: Use the skill for component architecture if it fits your task, but inspect and correct the lifted-state example in your project before copying it. Do not treat the example as a tested implementation.

What we checked

• The pinned lifted-state rule at 063bee94 contains the Composer.Context call.
• The pinned context-interface rule defines ComposerContext and uses it directly.
• The current main rule still shows the first call. Issue #286 reports it, and PR #304 proposes a correction but is open.

What this does and does not mean

The mismatch is in source text, not a pool-observed runtime result. It is a reason to check one example, not to reject every rule in the skill. We have not verified Codex loading, full package behavior, or whether an agent follows this example in a real refactor.

Why a directory listing is not enough

skills.sh provides an install command and popularity information for the skill. Those facts help discovery; they do not test each rule example. A recent r/codex question asks for a frontend skill while replies differ on whether a skill or design process is the useful next step. That discussion is not a comparison test.

Next check

Use a small React component with a known context interface. Compare a careful brief with a Codex run using this skill, record the exact source revision, and inspect whether the generated code uses a defined context. That test has not been run.