# Create and Maintain VibeStart TypeScript Projects

Project scaffolding and template upgrades require consistent choices and careful review of existing code. This skill guides vibestart CLI discovery, previews, capability additions, and maintenance.

## Install

```bash
npx skillstore add vinkydev/vibestart
```

## Metadata

- Status: approved
- Slug: vinkydev-vibestart
- Skillstore revision: r1
- Version status: missing
- Tree hash: 306662dd55119bcf2935ee7f2599a9308fbe0d1d4680e14386f7fe6986e4cf00
- Author: vinkydev
- GitHub username: vinkydev
- License: MIT
- Repository: https://github.com/vinkydev/vibestart/tree/b7f503159fb68dd3e3d5c2c4d9b85d4e13baae13/skills/vibestart
- Ref: e406bf64b5db6e514879399e87b346fa7ff7c2fb
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 50
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/vinkydev-vibestart
- Manifest: https://skillstore.pages.dev/api/skills/vinkydev-vibestart/manifest

## Capabilities

- Guide live discovery of supported stacks, recipes, and valid project choices through CLI help and structured listings.
- Preview project creation and distinguish package-manager choices from Hono runtime choices.
- Guide preview and application of supported Knip, Ultracite, and Docker capability additions.
- Interpret read-only doctor results, including offline limitations and configuration issues.
- Guide version-pinned template upgrades, conflict resolution, and manual porting of starter source changes.
- Report operation status, checks actually run, deferred installation, and remaining work.

## Use Cases

- Start a TypeScript Application: Discover supported stack choices and preview a new project before creating files and installing dependencies.
- Add Project Tooling: Preview supported Knip, Ultracite, or Docker additions while preserving project choices and reviewing resulting changes.
- Review Template Upgrades: Diagnose maintenance state, preview an exact target release, and identify conflicts, manual changes, and required validation.

## Prompt Templates

### Beginner: Inspect Project State

```
Inspect my vibestart project at [directory]. Use an approved CLI version, run offline diagnostics, and report configuration issues without applying changes.
```

### Intermediate: Preview a New Project

```
Preview a TypeScript project at [destination] using [requirements]. Discover supported choices, ask about missing decisions, and do not create files yet.
```

### Intermediate: Add Capabilities

```
Add Knip and Ultracite to [directory]. Pin an approved CLI version, preview changes, preserve unrelated work, and apply only the requested additions.
```

### Advanced: Upgrade and Resolve Changes

```
Upgrade [directory] to [exact version]. Preview changes, preserve business edits, resolve conflicts, review manual source changes, and report checks and remaining work.
```

## Limitations

- Installing the skill does not install the CLI, Vite\+, or project dependencies.
- Capability additions are not framework, database, runtime, or package-manager migrations.
- Doctor results and successful previews do not prove that application tests passed.
- CLI launchers may require registry access; writes can run dependency setup, project checks, services, or browsers.

## Best Practices

- Approve and pin an exact CLI version before discovery, preview, or application; review external installation requirements.
- Preview requested changes and start maintenance writes from a clean worktree without discarding unrelated edits.
- Review conflicts and manual entries, then report only installation and validation steps that actually completed.

## Anti Patterns

- Do not apply a preview when the user requested inspection only.
- Do not hand-edit the project record or use creation to migrate an existing project.
- Do not use blanket rollback commands without reviewing affected files and obtaining approval for deletions.

## Security Audit

- Audited at: 2026-10-10T14:10:03.107\+00:00
- Summary: Ten detections are false positives involving Markdown or ordinary project workflows; six describe commands that fetch and execute an unpinned npm package. Broad rollback instructions can discard unrelated edits and delete untracked files created after the operation starts. No evidence found of prompt injection, credential theft, or malicious exfiltration in the reviewed skill files; external package implementation was not available.

## Stats

- Views: 0
- Downloads: 1
- Favorites: 0
- Popularity score: 0