Cross-project referencing

Pull a component, schema, or pattern from one of your projects into another. The way vly users build their own personal libraries.

Once you’ve shipped a few projects, you’ll have built useful patterns — a billing flow, a custom date picker, a multi-tenant auth setup — that you’d like to reuse. Cross-project referencing lets you pull these into new projects by reference.

How it works

1. In a target project, prompt with a reference

   “Add billing to this project — use the same setup as in my acme-corp project.”

2. vly fetches the relevant code

   From the named project, with proper auth scoping (you must own both).

3. Adapts and inserts

   The agent ports the pattern to the target project, adjusting for differences in schema and naming.

The new project gets its own copy of the code — there’s no live link. Updates to the source project don’t propagate.

Example uses

Reuse a billing setup

“Use the Stripe subscription flow from my payments-template project.”

Reuse a component library

“Bring over the <DataTable /> and <DateRangePicker /> from internal-tools.”

Reuse a schema pattern

“Use the same multi-tenant schema (workspaces, memberships, invites) as previous-saas.”

Reuse an integration

“Bring over the Slack notification action from team-tools.”

Permissions

You can reference any project you own or have admin access to in the same workspace. To reference across workspaces, the source project’s owner must explicitly mark it as “shareable” in project settings.

Tips

Build a personal library. Many vly users keep a templates workspace with their favorite patterns. Reference from there into new projects.

Reference is one-way. Once code is copied into the target, edits don’t sync back. For shared, evolving code, use a shared component library (npm package) — coming to vly soon; see roadmap.

Related

Templates

Curated, maintained starting points.

Knowledge base

Project-scoped reference for the agent.

GitHub integration

For sharing code as actual repos / npm packages.