Skip to content
Contact
Engineering

Vercel Composition Patterns

Vercel

Choose composition patterns from actual reuse needs and caller behavior.

SKILL.md

---
name: knoveya-vercel-composition-patterns
description: "Choose composition patterns from actual reuse needs and caller behavior. Use for matching engineering work."
---

# Vercel Composition Patterns

## Scope

Apply this guidance when the requested task matches the description. Honor the user's chosen outcome, repository rules, and existing authorization.

## Workflow

Choose composition patterns from actual reuse needs and caller behavior.

Before acting, inspect the relevant artifact and ask only for information that materially changes the result. Use existing tools and conventions; do not install dependencies, publish, send messages, deploy, or mutate external data unless the user has authorized that operation.

## Acceptance check

Component APIs remain understandable and avoid unnecessary wrapper layers.

## Example task

Use slots for a real layout variation rather than a new component hierarchy.

## Report

State what changed, the evidence checked, and what remains unverified. Do not claim a successful operation or completed test without observing it.
View all

How to use

Copy the full block, including its frontmatter, into a new folder named knoveya-vercel-composition-patterns as SKILL.md. Review the instructions before enabling them. For Codex, a user skill normally lives in ~/.codex/skills/knoveya-vercel-composition-patterns/SKILL.md; check the current documentation for another agent's supported location. Do not overwrite an existing skill.

This is an independent Knoveya skill. No files are installed by this website.

Example

Use slots for a real layout variation rather than a new component hierarchy.

Verify

Component APIs remain understandable and avoid unnecessary wrapper layers.

Test the skill on a small, authorized example. File validation alone does not prove that an agent will make good decisions.

Limits

The skill supplies instructions, not tool access or expertise guarantees. Inspect generated work and preserve the user's approval boundaries.