SuperAPI AI Directory

project-initializer

Coding & development

View repository

Updated 10-15 20:08

About this skill

Project Initializer

Initialize a new project to fit the framework. Research the latest information with WebSearch, ask the user about ambiguous parts, and automatically generate the default rules upon completion.

Core Principles

  1. Web Search First - Always search for the latest version before installation/configuration
  2. Ask if ambiguous - Wait for the user's decision after presenting options
  3. User confirmation required - Confirm the entire tech stack in Phase 3
  4. Automatic rule setup - Generate the default rules with the rule-manager workflow in Phase 5

Multiple expert perspectives

Perform the initialization from the following expert perspectives:

Expert Perspective
Architect Project structure, module design, scalability
DevOps Engineer Build tools, CI/CD, environment configuration
DX Specialist Developer experience, linting, formatting, scripts

5-Phase Workflow

Phase 1        Phase 2        Phase 3        Phase 4        Phase 5
Discovery  →   Research   →   Decision   →   Execution  →   Finalize
요구사항 파악   최신 정보 수집  기술 스택 확정  프로젝트 생성   검증 + 규칙

Phase 1: Discovery (Identifying requirements)

Confirm the following with the user. Skip items you already know.

Item Question Default
Project type "Which would you like to build: a web app, API, CLI, or library?" -
Framework "Which framework are you using?" Recommendation based on purpose
Project name "What is the project name?" -
Creation path "Where should the project be created?" Current directory
Special requirements "Are there any additional features you need?" (DB, authentication, etc.) None

If the framework is undecided, recommendations:

Purpose Recommended framework
Web app (full-stack) Next.js, Nuxt
Web app (SPA) Vite + React/Vue
API server NestJS, FastAPI, Go
CLI tool Commander.js, Click, Cobra
Library tsup, setuptools, cargo

Detailed framework information: references/framework-profiles.md


Phase 2: Research (Collecting the latest information)

Be sure to use WebSearchto search for the following items:

Search item Query pattern Purpose
Latest framework version {framework} latest stable version {year} Check the latest stable version
Runtime LTS {runtime} LTS version {year} Check the compatible runtime version
CLI/scaffold tool {framework} create project CLI {year} Check the official generation tool
Recommended project structure {framework} recommended project structure Check the best-practice structure

Search result recording format:

## 검색 결과 요약
- 프레임워크: {name} v{version} (출처: {source})
- 런타임: {runtime} v{version} (LTS)
- CLI 도구: {tool} v{version}
- 권장 구조: {brief description}

Detailed search strategy: references/web-search-strategy.md


Phase 3: Decision (Finalize Tech Stack)

Based on the search results, propose a tech stack and get user confirmation.

Common decision items:

Item Example options Default
Package manager npm, pnpm, yarn, bun / pip, uv, poetry Ecosystem recommended value
Language settings TypeScript, JavaScript / Python version TypeScript
Linting tool Biome, ESLint, Ruff, golangci-lint Framework default
Formatter Biome, Prettier, Black, gofmt Linter integration
Test framework Vitest, Jest, pytest, go test Framework default
Git hooks husky, lefthook, pre-commit Optional

Confirmation format:

## 기술 스택 확인

| 항목 | 선택 |
|------|------|
| 프레임워크 | {framework} v{version} |
| 런타임 | {runtime} v{version} |
| 패키지 매니저 | {pm} |
| 언어 | {lang} |
| 린팅 | {linter} |
| 포맷팅 | {formatter} |
| 테스트 | {test_framework} |
| 추가 기능 | {features} |

이 스택으로 프로젝트를 생성할까요?

Do not proceed to Phase 4 without user confirmation.


Phase 4: Execution (Project Creation)

Create the project with the approved stack. Follow this order:

Step 1: Environment check

# 런타임 버전 확인
{runtime} --version

# 패키지 매니저 확인 (없으면 설치)
{pm} --version

Step 2: Project scaffold

# 프레임워크 공식 CLI로 프로젝트 생성
{scaffold_command} {project_name}
cd {project_name}

Step 3: Install additional packages

Install packages according to the additional features finalized in Phase 3.

# 런타임 의존성
{pm} add {runtime_deps}

# 개발 의존성
{pm} add -D {dev_deps}

Step 4: Configure configuration files

  • Linter/formatter configuration files
  • Environment variable file (.env, .env.example)
  • Editor settings (.editorconfig)

Step 5: Git initialization

# scaffold에서 이미 생성된 경우 건너뜀
git init
git add .
git commit -m "Initial commit: {framework} project setup"

Detailed phase-by-phase procedure: references/phases.md


Phase 5: Finalize (Verification + Rule Generation)

5-1. Build verification

Verify that the project works correctly:

# 1. 린트 검사
{pm} {lint_script}

# 2. 빌드 테스트
{pm} {build_script}

# 3. 테스트 실행
{pm} {test_script}

# 4. 개발 서버 실행 (빠르게 확인 후 종료)
{pm} {dev_script}

If verification fails, fix immediately and re-verify.

5-2. Automatic generation of basic rules

Refer to the rule-manager workflow to generate basic rules for the project.

Target path: of the initialized project .claude/skills/

Basic rule categories:

Category Rule content user-invocable
Coding conventions Naming, formatting, file structure false
Git conventions Commit messages, branching strategy false
Project structure Directory rules, module composition false

Detailed rule generation guide: references/rule-integration.md

5-3. Completion report

## 프로젝트 초기화 완료

### 프로젝트 정보
- **이름**: {project_name}
- **경로**: {project_path}
- **프레임워크**: {framework} v{version}
- **런타임**: {runtime} v{version}

### 설치된 패키지
| 패키지 | 버전 | 용도 |
|--------|------|------|
| ... | ... | ... |

### 사용 가능한 스크립트
| 명령어 | 설명 |
|--------|------|
| `{pm} dev` | 개발 서버 실행 |
| `{pm} build` | 프로덕션 빌드 |
| `{pm} test` | 테스트 실행 |
| `{pm} lint` | 린트 검사 |

### 생성된 규칙
| 규칙 | 경로 |
|------|------|
| ... | .claude/skills/... |

### 다음 단계 권장사항
1. {recommendation_1}
2. {recommendation_2}
3. {recommendation_3}

Execution checklist

[ ] Phase 1: 프로젝트 종류, 프레임워크, 이름, 경로 확인
[ ] Phase 2: 최신 버전 WebSearch 완료 (4개 항목)
[ ] Phase 2: 검색 결과 기록 완료
[ ] Phase 3: 기술 스택 제안 완료
[ ] Phase 3: 사용자 확인 완료
[ ] Phase 4: 환경 확인 완료
[ ] Phase 4: scaffold 실행 완료
[ ] Phase 4: 추가 패키지 설치 완료
[ ] Phase 4: 설정 파일 구성 완료
[ ] Phase 4: Git 초기화 완료
[ ] Phase 5: 빌드 검증 통과
[ ] Phase 5: 기본 규칙 자동 생성 완료

Error handling

Situation Response
Scaffold failure Check CLI tool version → reinstall → retry
Package conflict WebSearch for compatible versions → adjust versions
Build failure Analyze error logs → fix configuration → re-verify
Runtime not installed Provide installation instructions → install after user confirmation

Detailed guide