What is in the zip
Ten directories, and four of them are the ones you will open. The rest is there so nothing has to be fetched.
The whole thing, once
There is no package to install and nothing is fetched at build time. What you downloaded is the application, its component source and its documentation, in one tree.
viliha-admin-nextjs-pro/
app/ The screens, grouped by Next route group
(shell)/ 113 screens behind the sidebar
(auth)/ 5 screens: sign in, sign up, recovery
nav.ts The sidebar. Adding a page means adding a row here
src/vui/ The component source, one file per family
theme.css Every design token, light and dark
core/ The framework-free half: theming, table import and export
docs/ The documentation, offline, as markdown
agent/ A machine-readable description of the theme
mcp/server.mjs The MCP server, runnable with no network
protocol/ The compiled design protocol the server answers from
public/ Fonts, images and the demo data the screens render
AGENTS.md The rules a coding agent follows in this project
CLAUDE.md The same, for Claude Code
.mcp.json Registers the MCP server for any client that reads it
package.json Four scripts: dev, build, start, check-types
tsconfig.json Where the @viliha/vui-react alias pointsWhat is not in it
- No lockfile. Nothing pins your package manager, so npm, pnpm, yarn and bun all work.
- No tests. Ours are not part of your product, and a test file importing a runner you do not install is dead weight in your repository.
- No backend, and no client for one. Every screen renders demo data held in the page.
- No build output. No
.next, nonode_modules.
The component source is yours to edit, and you rarely need to
Almost everything worth changing is a token in
src/vui/theme.css, which moves every component at once. Editing a component is for when the token layer genuinely cannot express what you want.