How do I install the Venuscn Repo skill?

Run npx skillmds@latest add tomevault-io/venuscn-repo in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Venuscn Repo safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Venuscn Repo?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Venuscn Repo free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Venuscn Repo?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Venuscn Repo by tomevault-io — Agent Skill

Name: Venuscn Repo
Author: tomevault-io

Venuscn Repo

Use when working in a repository that uses the VenusCN component library, or when building React and Next.js interfaces that should match the Contentstack Venus visual language. Helps agents orient quickly, find the right source files, prefer existing components over ad hoc UI, use the demo app as a reference implementation, and run the correct validation commands.

tomevault-io Updated Sep 17, 2026

File contents

VenusCN Repo Skill

Use this skill when the task involves building, editing, or reviewing interfaces in a repo that contains @contentstack/venuscn or follows the same Venus-inspired design language.

Quick Start

Read these files first:

README.md
packages/venuscn/README.md
apps/demo/HOW_THE_DEMO_WORKS.md
docs/guides/design-system.md

If the task is still unclear after that, read references/repo-map.md.

Core Working Model

Treat packages/venuscn as the reusable design-system package.
Treat apps/demo as the visual reference implementation and pattern library.
Prefer existing VenusCN components before creating new app-specific UI.
Reach for shadcn/ui app components only when the reusable package does not cover the need.
Match existing spacing, typography, borders, and page structure before inventing new patterns.

Build UI The VenusCN Way

For interface work, follow this order:

Find the closest matching demo page or gallery example.
Reuse an existing @contentstack/venuscn component if one exists.
Compose with existing tokens and layout patterns.
Add a new reusable component only if the pattern is clearly repeated or design-system-worthy.

Use references/interface-patterns.md when you need a fast pattern map.

Editing Rules

Preserve the repo's existing visual language.
Keep reusable logic in packages/venuscn and app-specific behavior in apps/demo.
Prefer token-based colors and spacing over one-off values unless the repo already uses a hardcoded value for that exact pattern.
When changing docs or repo behavior, update linked documentation in docs/ and the root README.md if needed.

Validation

Default validation command after code changes:

pnpm check

If only docs changed, validate links and docs references instead of running the full code pipeline.

When To Read More

Read references/repo-map.md for package and file ownership.
Read references/interface-patterns.md for common UI composition patterns in this repo.

Source: lytics/venus — distributed by TomeVault.

---name: venuscn-repodescription: Use when working in a repository that uses the VenusCN component library, or when building React and Next.js interfaces that should match the Contentstack Venus visual language. Helps agents orient quickly, find the right source files, prefer existing components over ad hoc UI, use the demo app as a reference implementation, and run the correct validation commands.---# VenusCN Repo SkillUse this skill when the task involves building, editing, or reviewing interfaces in a repo that contains `@contentstack/venuscn` or follows the same Venus-inspired design language.## Quick StartRead these files first:1. `README.md`2. `packages/venuscn/README.md`3. `apps/demo/HOW_THE_DEMO_WORKS.md`4. `docs/guides/design-system.md`If the task is still unclear after that, read `references/repo-map.md`.## Core Working Model- Treat `packages/venuscn` as the reusable design-system package.- Treat `apps/demo` as the visual reference implementation and pattern library.- Prefer existing VenusCN components before creating new app-specific UI.- Reach for shadcn/ui app components only when the reusable package does not cover the need.- Match existing spacing, typography, borders, and page structure before inventing new patterns.## Build UI The VenusCN WayFor interface work, follow this order:1. Find the closest matching demo page or gallery example.2. Reuse an existing `@contentstack/venuscn` component if one exists.3. Compose with existing tokens and layout patterns.4. Add a new reusable component only if the pattern is clearly repeated or design-system-worthy.Use `references/interface-patterns.md` when you need a fast pattern map.## Editing Rules- Preserve the repo's existing visual language.- Keep reusable logic in `packages/venuscn` and app-specific behavior in `apps/demo`.- Prefer token-based colors and spacing over one-off values unless the repo already uses a hardcoded value for that exact pattern.- When changing docs or repo behavior, update linked documentation in `docs/` and the root `README.md` if needed.## ValidationDefault validation command after code changes:```bashpnpm check```If only docs changed, validate links and docs references instead of running the full code pipeline.## When To Read More- Read `references/repo-map.md` for package and file ownership.- Read `references/interface-patterns.md` for common UI composition patterns in this repo.---> Source: [lytics/venus](https://github.com/lytics/venus) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions