Create distinctive, production-grade static sites with React, Tailwind CSS, and shadcn/ui — no mockups needed. Generates bold, memorable designs from plain text requirements with anti-AI-slop aesthetics, mobile-first responsive patterns, and single-file bundling. Use when building landing pages, marketing sites, portfolios, dashboards, or any static web UI. Supports both Vite (pure static) and Next.js (Vercel deploy) workflows.
Security Analysis
high confidenceThe skill is internally consistent with its stated purpose (scaffolding and bundling front-end projects); it relies on Node/npm and includes init and bundling scripts that match the documentation — no unexplained credentials or hidden endpoints were found.
Name/description claim React + Tailwind + shadcn workflows; required binaries (node, npm), init scripts (vite/nextjs), bundling script, and template config are all directly aligned with that purpose. No unrelated credentials or tools are requested.
SKILL.md and README instruct the agent/user to run the included shell scripts (init-vite.sh, init-nextjs.sh, bundle-artifact.sh) and to run npm/npx commands. The instructions remain inside the domain of project scaffolding and bundling, but they do tell the agent to execute networked package installs (npm/npx) and to run developer tooling (e.g., vercel) which will interact with external services if invoked.
The skill itself has no install spec (lowest install risk), but its runtime scripts call npx and npm to fetch packages (shadcn CLI, parcel, framer-motion, etc.) from public registries. These are expected for the stated purpose but carry the normal moderate risk of executing third-party packages pulled from npm via npx.
No environment variables, secrets, or external config paths are required. References to deploying with Vercel are optional and do not demand credentials in the skill metadata. The requested environment access is proportional to scaffolding/building static sites.
The skill does not request always:true and does not modify other skills or system-wide settings; its scripts create project files and .nvmrc in the current working directory and install dependencies into project folders — expected behavior for a scaffolding tool. Note: autonomous agent invocation is allowed by default; if the agent runs these scripts autonomously it will write files and run network installs.
Guidance
This skill appears to do exactly what it says: scaffold Vite/Next.js projects and bundle them into a single HTML using standard npm tools. Before running it (especially if you let an agent execute it autonomously): - Review the included scripts (init-*.sh and bundle-artifact.sh) yourself — they run npm/npx and will download and execute packages from the public npm registry. - Run the scripts in a disposable/project directory (not your home or a sensitive location) to avoid accidental file overwrites. - Prefer manual invocation the first time so you can inspect package.json and node_modules before running dev/build commands. - Be cautious with any follow-up 'vercel' or other deploy commands — those may prompt for credentials or require tokens you should not share automatically. - If you need stronger guarantees, audit the specific npm packages the scripts install (shadcn CLI, parcel, html-inline, etc.) or pin versions in your own fork before use.
Latest Release
v1.0.0
Initial release: React + Tailwind + shadcn/ui, anti-AI-slop design
More by @kesslerio
Published by @kesslerio on ClawHub
