init-project
SKILL.md
Project Initialization Best Practices
When creating new projects, always prefer official CLI tools and scaffolding commands over manually creating files and directories. These tools:
- Set up correct project structure and config
- Install dependencies with compatible versions
- Configure build tools, linting, testing
- Follow framework best practices
JavaScript/TypeScript
| Framework | Command |
|---|---|
| Vite | bun create vite or npm create vite@latest |
| Next.js | bunx create-next-app or npx create-next-app@latest |
| Remix | bunx create-remix or npx create-remix@latest |
| Astro | bun create astro or npm create astro@latest |
| SvelteKit | bun create svelte or npm create svelte@latest |
| Nuxt | bunx nuxi init or npx nuxi@latest init |
| React Native | npx @react-native-community/cli init |
| Expo | bunx create-expo-app or npx create-expo-app |
| Electron | npm init electron-app@latest |
| Tauri | bun create tauri-app or npm create tauri-app@latest |
TypeScript Package Preference
- Prefer
pnpmas the package manager for TypeScript packages/libraries.
Key Principles
- Don't manually create config files - Let the CLI generate them
- Use interactive prompts - Most CLIs ask about TypeScript, linting, testing
- Check framework docs - Commands change; verify current syntax
- Prefer package-manager conventions - use
pnpmfor TypeScript packages unless project constraints require otherwise - Use templates - Many CLIs offer starter templates (e.g.,
--template react-ts)
When Manual Setup is OK
- Adding to existing monorepo with specific conventions
- Learning how tools work under the hood
- Very minimal projects (single script)
- Custom build requirements not covered by templates
Weekly Installs
8
Repository
linct96/aiFirst Seen
14 days ago
Security Audits
Installed on
opencode8
antigravity8
claude-code8
github-copilot8
codex8
kimi-cli8