Loading source

Preparing the source view

Pulling the file list, source metadata, and syntax-aware rendering for this listing.

Source from repo

Convex Create Component

Design and build reusable Convex components with isolated tables, backend functions, and app-facing wrappers.

get-convexGitHub get-convexSource repo Original GitHub link Publisher page

Files

7

Skill

n/a

Size

18.6 KB

Entrypoint

SKILL.md

Format

git-repo

Repo map

Skill files

agents/openai.yaml

assets/icon.svg

references/advanced-patterns.md

references/hybrid-components.md

references/local-components.md

references/packaged-components.md

SKILL.md

markdown10.2 KBentry

Open file

references/hybrid-components.md

Syntax-highlighted preview of this file as included in the skill package.

Rendered Source

markdown39 linesFree

Hybrid Convex Components

Read this file only when the user explicitly wants a hybrid setup.

What This Means

A hybrid component combines a local Convex component with shared library code.

This can help when:

the user wants a local install but also shared package logic
the component needs extension points or override hooks
some logic should live in normal TypeScript code outside the component

boundary

Default Advice

Treat hybrid as an advanced option, not the default.

Before choosing it, ask:

Why is a plain local component not enough?
Why is a packaged component not enough?
What exactly needs to stay overridable or shared?

If the answer is vague, fall back to local or packaged.

Risks

More moving parts
Harder upgrades and backwards compatibility
Easier to blur the component boundary

Checklist

[ ] User explicitly needs hybrid behavior
[ ] Local-only and packaged-only options were considered first
[ ] The extension points are clearly defined before coding