npm-pkg-config
Initialize TypeScript projects with proper tooling, type checking, and framework setup.
Reference documentation: package.md, workspace.md, typescript.md, oxc.md, hono.md, tanstack-spa.md, shadcn-ui.md, dev-tools.md, ci.md
<configuration_decisions>
Key Configuration Decisions
Project visibility:
- Public → Include LICENSE file
- Private → Omit license
Package structure:
- Single package → Root-level configuration
- Workspace (monorepo) → Root shared config + per-package configs
Application type:
- Frontend only → TanStack Router + shadcn/ui
- Backend only → Hono
- Full-stack → Hono + TanStack Router + shadcn/ui
- npm library → No framework, focus on build/publish config </configuration_decisions>
<setup_principles>
Setup Dependencies and Order
Required setup sequence (due to configuration dependencies):
- Base package (
package.md): Foundation for all subsequent configs - Workspace structure (
workspace.md): Only if monorepo - must precede package setup - Linting/formatting (
oxc.md): Requires package structure to be established - Application setup: Location depends on package structure
- Single package: Root directory
- Workspace: Separate
packages/*/directories - TypeScript (
typescript.md): Required for all projects - Backend:
hono.md - Frontend SPA:
tanstack-spa.md - UI components:
shadcn-ui.md
- Development tools (
dev-tools.md): Requires application structure - CI/CD (
ci.md): Final step after all configs established
Location constraints:
- Single package: All configs at root
- Workspace: Shared configs at root, app-specific in
packages/*/</setup_principles>
<reference_index>
Setup Reference Documents
Core setup (all projects):
package.md: Package configuration (package.json, pnpm)typescript.md: TypeScript strict configurationoxc.md: Linting and formatting with oxcdev-tools.md: Development utilitiesci.md: CI/CD pipelines
Structure-specific:
workspace.md: Monorepo/pnpm workspace setup
Framework-specific:
hono.md: Backend API with Honotanstack-spa.md: Frontend SPA with TanStack Routershadcn-ui.md: UI component library setup
</reference_index>
<best_practices>
Configuration Best Practices
TypeScript:
- Always use strict type checking
- Configure path aliases for clean imports
Package management:
- Use pnpm for all TypeScript projects
- Configure workspace protocol for monorepo dependencies
Tooling consistency:
- oxc for linting and formatting (faster than ESLint/Prettier)
- Consistent script names across workspace packages
</best_practices>
More from d-kimuson/dotfiles
article-writing
箇条書きコンテンツを技術記事に仕上げる際に使用する。自然な文体とスタイルで執筆するためのガイドライン。
18n8n
Core n8n automation software using n8n-MCP tools.
17typescript
Must always be enabled when writing/reviewing TypeScript code.
16react
Must always be enabled when writing/reviewing React code.
14shadcn-ui
Must always be enabled when working with shadcn-ui.
14frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
13