frontend-project

Generate deterministic React, TypeScript, and Vite project files with validated candidate manifests.

7|5|Updated Jul 22, 2025
One-click install
npx skills add https://github.com/nebius/nebius-ps-services --skill frontend-project-nebius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frontend-project
Source: https://github.com/nebius/nebius-ps-services/tree/main/skills/frontend-project
Command: npx skills add https://github.com/nebius/nebius-ps-services --skill frontend-project-nebius

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Scaffolding React, TypeScript, and Vite frontends often relies on network generators, floating dependency versions, and inconsistent configuration, producing non-reproducible projects and unsafe public environment variables. This Skill renders deterministic, repo-owned templates with exact versions and strict validation so every generated frontend is byte-for-byte reproducible and auditable. ## Core Features & Use Cases - Deterministic scaffolding: Renders package.json, tsconfig files, Vite/Vitest configs, entrypoints, tests, and plain-CSS baseline from closed templates without running create-vite or any network generator. - Coordinated candidate manifests: In coordinated mode, produces digest-bound candidate files in a private 0700 directory with SHA-256 manifest validation for handoff to a scaffold coordinator. - Public environment safety: Accepts only names-only VITE_* variables, rejecting secret-like names such as API_KEY or ACCESS_KEY (including compact forms) and forbidding values or defaults. - Use Case: A platform team assigns a new web component under apps/web; the skill renders the exact assigned file set with pinned React 19, Vite, and Vitest versions, returns a validated manifest, and reports lint, typecheck, test, and build as pending until dependencies are installed. ## Quick Start Ask the agent to use frontend-project to scaffold a new React, TypeScript, and Vite app with pnpm, Vitest tests, and a names-only VITE_API_ORIGIN environment variable.

Frequently Asked Questions about frontend-project

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scaffold a React TypeScript Vite project without create-vite?

Use this skill's deterministic renderer, which writes package.json, tsconfig files, Vite and Vitest configs, entrypoints, and tests from repo-owned templates. It never runs create-vite or any network generator, and all dependency versions must be exact pinned values.

What package managers are supported for Vite project scaffolding?

Only npm, pnpm, yarn, and bun are accepted, each with an exact manager version. Arbitrary command tokens fail closed during request validation, and no lockfile is generated without running the approved package manager.

Can I use Next.js, Vue, or Svelte with this frontend scaffolding skill?

No. The supported materialization profile is React, TypeScript, and Vite only. Requests for Next.js, Remix, Vue, Svelte, Angular, mobile, Electron, or Node backends are explicitly rejected and belong to other owners.

Why does my VITE environment variable name get rejected?

Names must match VITE_[A-Z][A-Z0-9_]* and must not contain secret-like markers such as SECRET, TOKEN, PASSWORD, API_KEY, or ACCESS_KEY, even in compact forms like APIKEY. Values, defaults, and examples are also forbidden because VITE_* variables are public client data.

How does coordinated candidate mode work with scaffold-project?

The skill renders exact assigned files into a private 0700 directory and returns a canonical manifest with normalized inputs, SHA-256 input and file digests, modes, and bound validation records. It never writes the target repository; the coordinator finalizes and validates the handoff.

When are lint, test, and build checks run after scaffolding?

Dependency-backed checks such as lint, format, typecheck, test, and build run only when dependencies are already installed or separately authorized. Otherwise they are reported as pending post-apply validations, while offline JSON, placeholder, digest, and permission checks always run.