Cleanup Specialist
ahaodev/shadmin
Safe cleanup of Shadmin's Go backend, React frontend, Go CLI, and docs — remove dead code, consolidate duplication, and improve maintainability without changing behavior or adding features.
Use the vibestart CLI to create a TypeScript project, choose a stack or recipe, add capabilities such as Knip, Ultracite or Docker, diagnose project state, or upgrade templates while preserving…
Install Vibestart
$ npx skills add VinkyDev/vibestart --skill vibestart -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install VinkyDev/vibestart vibestart --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/VinkyDev/vibestart.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/vibestart .claude/skills/vibestart && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "vibestart" agent skill from https://github.com/VinkyDev/vibestart/tree/main/skills/vibestart into .claude/skills/vibestart/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibestart", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/VinkyDev/vibestart/tree/main/skills/vibestartType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add VinkyDev/vibestart --skill vibestart -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install VinkyDev/vibestart vibestart --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/VinkyDev/vibestart.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/vibestart .agents/skills/vibestart && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vibestart" agent skill from https://github.com/VinkyDev/vibestart/tree/main/skills/vibestart into .agents/skills/vibestart/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibestart", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add VinkyDev/vibestart --skill vibestart -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install VinkyDev/vibestart vibestart --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/VinkyDev/vibestart.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/vibestart .cursor/skills/vibestart && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "vibestart" agent skill from https://github.com/VinkyDev/vibestart/tree/main/skills/vibestart into .cursor/skills/vibestart/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibestart", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/VinkyDev/vibestart.git --path skills/vibestart--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add VinkyDev/vibestart --skill vibestart -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install VinkyDev/vibestart vibestart --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/VinkyDev/vibestart.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/vibestart .gemini/skills/vibestart && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "vibestart" agent skill from https://github.com/VinkyDev/vibestart/tree/main/skills/vibestart into .gemini/skills/vibestart/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibestart", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install VinkyDev/vibestart vibestartInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add VinkyDev/vibestart --skill vibestart -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/VinkyDev/vibestart.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/vibestart .github/skills/vibestart && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "vibestart" agent skill from https://github.com/VinkyDev/vibestart/tree/main/skills/vibestart into .github/skills/vibestart/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibestart", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add VinkyDev/vibestart --skill vibestart -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install VinkyDev/vibestart vibestart --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/VinkyDev/vibestart.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/vibestart .opencode/skills/vibestart && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "vibestart" agent skill from https://github.com/VinkyDev/vibestart/tree/main/skills/vibestart into .opencode/skills/vibestart/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibestart", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
vibestart- GitHub stars
- 103
- Used in
- 1 other repo
- Token cost
- ~1.4k tokens
- SKILL.md length
- 646 words
- Files
- 3 (incl. references)
- Repo updated
- First seen
- Licence
- MIT
At a glance
Use the vibestart CLI to create a TypeScript project, choose a stack or recipe, add capabilities such as Knip, Ultracite or Docker, diagnose project state, or upgrade templates while preserving…
- Works in 4 steps: Identify the target directory and… → Run the CLI from npm with npx --yes… → Installing this skill does not install… → …
- The user mentions vibestart
- SKILL.md covers Establish the context, Choose the workflow, Execute within the requested… and Report the actual result
- Calls npx, pnpm and git
What it does
Vibestart is an agent skill from VinkyDev/vibestart. Use the vibestart CLI to create a TypeScript project, choose a stack or recipe, add capabilities such as Knip, Ultracite or Docker, diagnose project state, or upgrade templates while preserving business edits, including resolving conflicts and porting template changes to starter source. Use when the user mentions vibestart, asks to maintain a project with a vibestart.jsonc, or needs help with these CLI workflows. Not for ordinary application feature development unrelated to the CLI.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/create.md` and `references/maintenance.md`).
It sits in DevOps & Cloud. It works with TypeScript, Docker, Vite and React. The repository describes itself as: Compose a full-stack TypeScript stack and get a cutting-edge, verified project made for AI coding agents, with type safety, lint, and tests built in. | 自由组合全栈 TypeScript… The licence is MIT.
When your agent uses it
- The user mentions vibestart
- Asks to maintain a project with a vibestart.jsonc
- Needs help with these CLI workflows
Example prompts
- “/vibestart”
Requirements
- Node.js
- Docker
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Identify the target directory and whether the request is creation or maintenance. Read the project's instructions. For an existing…
- Run the CLI from npm with npx --yes vibestart-cli (or pnpm dlx vibestart-cli); a global install is not required. Resolve its version with…
- Installing this skill does not install the CLI, Vite+, or project dependencies. If a required tool is unavailable, follow its installation…
- Read npx --yes vibestart-cli --help for creation or npx --yes vibestart-cli COMMAND --help for maintenance. Prefer --json for operations…
What it can do on your machine
Read from SKILL.md and the folder at commit b7f5031. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npxpnpmgitbun
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npx, pnpm and git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Vibestart loads about 1.4k tokens when it runs, and up to ~4.1k if it reads all its reference files. Until then it costs about 124 tokens; SKILL.md has 646 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from VinkyDev/vibestart at commit b7f5031, republished under its MIT licence (© VinkyDev). 646 words, ~1,418 tokens.
Download SKILL.mdSave it as
.claude/skills/vibestart/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- vibestart
- description
- Use the vibestart CLI to create a TypeScript project, choose a stack or recipe, add capabilities such as Knip, Ultracite or Docker, diagnose project state, or upgrade templates while preserving business edits, including resolving conflicts and porting template changes to starter source. Use when the user mentions vibestart, asks to maintain a project with a vibestart.jsonc, or needs help with these CLI workflows. Not for ordinary application feature development unrelated to the CLI.
VibeStart CLI
Use the CLI to resolve stacks and maintain generated projects. Let its current help, capability list, and change plan determine what is supported; do not reconstruct templates or hand-edit the project record.
Establish the context
- Identify the target directory and whether the request is creation or maintenance. Read the project's instructions. For an existing project, inspect
vibestart.jsonc(itsname,version, and choices),package.json, and Git status. Preserve unrelated edits. - Run the CLI from npm with
npx --yes vibestart-cli(orpnpm dlx vibestart-cli); a global install is not required. Resolve its version withnpx --yes vibestart-cli --version. For a preview followed by application, append@and that exact published version to the package name in both commands so a new release cannot change the target between them. - Installing this skill does not install the CLI, Vite+, or project dependencies. If a required tool is unavailable, follow its installation instructions within the user's scope rather than changing the selected stack.
- Read
npx --yes vibestart-cli --helpfor creation ornpx --yes vibestart-cli COMMAND --helpfor maintenance. Prefer--jsonfor operations executed by an agent; keep stdout separate from stderr. Do not parse a task runner's banner as JSON.
Choose the workflow
Read the relevant reference before acting. Paths are relative to this skill's directory, not the user's project.
| User intent | First action | Reference |
|---|---|---|
| Create a project or use a recipe | npx --yes vibestart-cli --list --json | Creating projects |
| Add a capability | npx --yes vibestart-cli add --list --json | Maintenance |
| Diagnose an existing project | npx --yes vibestart-cli doctor --offline --json | Maintenance |
| Update a generated project | npx --yes vibestart-cli upgrade --dry-run --json | Maintenance |
| Finish a write: conflicts, manual changes, checks | Read the write's JSON result and git diff | Maintenance |
Run maintenance from the generated project root, or pass --cwd /actual/project/path. Creation instead takes a positional destination directory; it has no --cwd option.
Show full SKILL.md (336 more words)Show less
Execute within the requested scope
- Preview changes before writing. When the user has requested the operation and the plan meets that scope, proceed without an extra permission loop. Ask only about missing product choices or material changes outside the request. A request to inspect or preview does not authorize applying the plan.
- Creation uses
--jsonto disable prompts. Maintenance writes additionally require--yes. Do not pass--yesto creation. - A maintenance write needs a clean Git worktree. When the worktree holds the user's uncommitted work, ask whether to commit or stash it before writing.
- The package manager and Hono runtime are separate choices:
--package-manager bunselects dependency installation;--runtime bunselects Hono execution. Neither changes the other or moves the Vite+ test toolchain to Bun. Do not replacevp testwithbun testor force the CLI to run under Bun. - Existing projects use
addandupgrade. Change choices only through those commands; keepvibestart.jsonc'snameandversionas the CLI wrote them, since upgrades regenerate the original templates from them. - Respect the environment's installation and service restrictions. Normal creation and maintenance writes run setup/checks. If these are unavailable, use a read-only preview, or explicitly defer installation when file writes are in scope.
--full-checkcan start services and browsers.
Report the actual result
State the CLI version, target project, selected changes, returned status, checks actually run, and any remaining action, including conflicts and manual changes still to port. For machine output, inspect both exit code and JSON fields. A successful preview, doctor result, or historical stack verification record is not evidence that this project's tests passed. needs-install is an unfinished operation even though its exit code is zero.
Use the project's generated tasks for subsequent work: vp install, vp check, and the tasks present in package.json or vite.config.ts. vp run ready runs the full project validation chain. Do not assume a task exists when its optional capability is absent. The generator repository's vp run deps update is a maintainer command, not the generated project's upgrade command.
© VinkyDev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (references) in skills/vibestart of VinkyDev/vibestart.
- SKILL.md
- references/create.md
- references/maintenance.md
Open the folder on GitHubat commit b7f5031
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in VinkyDev/vibestart, which our catalogue first saw on October 11, 2026.
Compare with similar skills
Vibestart next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Vibestart this skillVinkyDev/vibestart | 103 | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Cleanup Specialistahaodev/shadmin | 174 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Shadmin CLIahaodev/shadmin | 174 | — | ~1.1k | Automated safety check: Notes | MIT | |
| Web Artifacts Builderanthropics/skills | 180k | 40 repos | ~769 | Automated safety check: Pass | Apache-2.0 | |
| Shadmin Devahaodev/shadmin | 174 | — | ~2.8k | Automated safety check: Pass | MIT | |
| Redesign My Landingpageinstructa/agent-skills | 139 | — | ~1.8k | Automated safety check: Pass | None |
Similar skills
Shadmin CLI
ahaodev/shadmin
A skill your agent uses when the user asks to query Shadmin admin platform resources (users, roles, menus, registered API resources) from a terminal — for example "list shadmin users", "show shadmin…
- Official
Web Artifacts Builder
anthropics/skills
Builds multi-component claude.ai HTML artifacts as a small React, TypeScript and Tailwind project, then bundles it into one shareable HTML file.
Shadmin Dev
ahaodev/shadmin
Apply Shadmin feature-development standards (backend Go/Gin/Ent + frontend React/TS).
Redesign My Landingpage
instructa/agent-skills
Build, critique, and iterate high-converting marketing or product landing pages using React + Vite + TypeScript + Tailwind and shadcn/ui components, with all icons sourced from Iconify.
Vite Shadcn Tailwind4
IgorWarzocha/Opencode-Workflows
Initialize shadcn/ui + Tailwind CSS v4 in Vite projects (Vite-specific, not Next.js/Remix).
More from VinkyDev/vibestart
Update Deps
VinkyDev/vibestart
Move the pinned dependencies to their latest targets, verify, and open a pull request.
Related
Categories
Questions about Vibestart
What does Vibestart do?
Use the vibestart CLI to create a TypeScript project, choose a stack or recipe, add capabilities such as Knip, Ultracite or Docker, diagnose project state, or upgrade templates while preserving…. Vibestart is an agent skill from VinkyDev/vibestart. Use the vibestart CLI to create a TypeScript project, choose a stack or recipe, add capabilities such as Knip, Ultracite or Docker, diagnose project state, or upgrade templates while preserving business edits, including resolving conflicts and porting template changes to starter source.
When should I use Vibestart?
Vibestart fits situations like: the user mentions vibestart; asks to maintain a project with a vibestart.jsonc; needs help with these CLI workflows.
How do I install Vibestart in Claude Code?
Run `npx skills add VinkyDev/vibestart --skill vibestart -a claude-code`. Or copy the skill folder (skills/vibestart in VinkyDev/vibestart) into .claude/skills/vibestart in your project. Claude Code loads it when a task matches its description.
How do I install Vibestart in Codex?
Run `npx skills add VinkyDev/vibestart --skill vibestart -a codex`. Or copy the skill folder (skills/vibestart in VinkyDev/vibestart) into .agents/skills/vibestart in your project. Codex loads it when a task matches its description.
Can I use Vibestart in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add VinkyDev/vibestart --skill vibestart -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vibestart, .gemini/skills/vibestart, .github/skills/vibestart and .opencode/skills/vibestart in your project.
What does Vibestart need to run?
Going by SKILL.md and its folder, Vibestart needs the command-line tools its instructions call (npx, pnpm, git and bun). Our summary lists: Node.js; Docker.
Does Vibestart access the network?
SKILL.md contains no URLs. Its commands use npx and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Vibestart safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Vibestart use?
Vibestart is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Vibestart use?
About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.7k tokens, read only when the agent opens those files.
What are the alternatives to Vibestart?
Skills that share tags, products or a category with Vibestart: Cleanup Specialist (ahaodev/shadmin, 174 stars), Shadmin CLI (ahaodev/shadmin, 174 stars), Web Artifacts Builder (anthropics/skills, 180k stars) and Shadmin Dev (ahaodev/shadmin, 174 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vibestart?
VinkyDev (a GitHub user) maintains it in VinkyDev/vibestart, which has 103 GitHub stars. The repository was last updated on October 10, 2026.
Source: VinkyDev/vibestart on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.