From shipshitdev-library
Orchestrates project initialization: agent folders, ESLint/Prettier linting, Husky test coverage, and scaffolding for NestJS, Next.js, Expo, Plasmo. Use for new projects or adding infrastructure.
npx claudepluginhub shipshitdev/skillsThis skill uses the workspace's default tool permissions.
This skill orchestrates multiple initialization skills to set up a complete, production-ready project environment. Instead of manually invoking each skill, this orchestrator coordinates them in the correct sequence with proper dependencies.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Analyzes competition with Porter's Five Forces, Blue Ocean Strategy, and positioning maps to identify differentiation opportunities and market positioning for startups and pitches.
This skill orchestrates multiple initialization skills to set up a complete, production-ready project environment. Instead of manually invoking each skill, this orchestrator coordinates them in the correct sequence with proper dependencies.
This skill activates automatically when users:
| Order | Skill | Purpose | Required |
|---|---|---|---|
| 1 | agent-folder-init | AI documentation & standards | Yes |
| 2 | linter-formatter-init | ESLint + Prettier + pre-commit | Yes |
| 3 | husky-test-coverage | Test coverage enforcement | Optional |
| 4 | Component scaffolding | Backend/Frontend/Mobile/Extension | Optional |
┌─────────────────────────────────────────────────────────────┐
│ PROJECT INIT ORCHESTRATOR │
└─────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────┐
│ PHASE 1: GATHER CONTEXT │
│ • Project name and path │
│ • Tech stack (Next.js, NestJS, Expo, Plasmo) │
│ • Package manager preference (bun, pnpm, npm) │
│ • Test coverage threshold (default: 80%) │
│ • Additional scaffolding needs │
└─────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────┐
│ PHASE 2: AGENT FOLDER INIT │
│ • Create .agents/ directory structure │
│ • Set up SESSIONS/, TASKS/, SYSTEM/ folders │
│ • Generate coding standards and rules │
│ • Copy agent configs (.claude/, .codex/, .cursor/) │
│ ──────────────────────────────────────────────────────────│
│ Invocation: │
│ python3 scripts/scaffold.py │
│ (from agent-folder-init skill) │
│ --root /path/to/project │
└─────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────┐
│ PHASE 3: LINTER FORMATTER INIT │
│ • Detect project tech stack │
│ • Install ESLint + Prettier (or Biome) │
│ • Configure framework-specific rules │
│ • Set up lint-staged for pre-commit │
│ • Create .vscode/settings.json │
│ ──────────────────────────────────────────────────────────│
│ Invocation: │
│ Use linter-formatter-init skill guidance │
└─────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────┐
│ PHASE 4: HUSKY TEST COVERAGE (if tests exist) │
│ • Detect test runner (Jest, Vitest, Mocha) │
│ • Configure coverage thresholds │
│ • Add pre-commit hook for test coverage │
│ ──────────────────────────────────────────────────────────│
│ Invocation: │
│ Use husky-test-coverage skill guidance │
└─────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────┐
│ PHASE 5: COMPONENT SCAFFOLD (optional) │
│ • Scaffold additional components if requested: │
│ - Backend (NestJS + MongoDB + Swagger + Dockerfile) │
│ - Frontend (Next.js + Tailwind + App Router) │
│ - Mobile (Expo + Expo Router + React Native) │
│ - Extension (Plasmo + React + Tailwind) │
│ • Supports monorepo (workspaces) or separate repos │
│ ──────────────────────────────────────────────────────────│
│ Invocation: │
│ python3 scripts/scaffold.py │
└─────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────┐
│ PHASE 6: VERIFICATION │
│ • Verify all configurations created │
│ • Run lint check (should pass) │
│ • Confirm git hooks installed │
│ • Generate setup summary │
└─────────────────────────────────────────────────────────────┘
When user says "initialize my project" or "set up new project":
1. Ask for project context:
- Project path (default: current directory)
- Tech stack (Next.js, NestJS, Node.js, etc.)
- Package manager (bun, pnpm, npm)
- Test coverage threshold (default: 80%)
- Need additional scaffolding? (backend, frontend, mobile, extension)
2. Execute phases in order:
Phase 2 → Phase 3 → Phase 4 → Phase 5 (if needed) → Phase 6
If you need to run phases individually:
Phase 2: Agent Folder Init
python3 scripts/scaffold.py --root /path/to/project # from agent-folder-init skill
Phase 3: Linter Formatter
Follow the linter-formatter-init skill to:
Phase 4: Test Coverage
Follow the husky-test-coverage skill to:
Phase 5: Component Scaffold (optional)
python3 scripts/scaffold.py
Supports scaffolding:
isDeleted), multi-tenancy (filter by organization), Dockerfile@components/, @services/, @hooks/)Structure options:
Phases: 2, 3
Output:
├── .agents/
├── .eslintrc.js
├── .prettierrc
├── .husky/pre-commit (lint-staged)
└── .vscode/settings.json
Phases: 2, 3, 4
Output:
├── .agents/
├── .eslintrc.js
├── .prettierrc
├── .husky/pre-commit (lint-staged + tests)
├── jest.config.js (coverage thresholds)
└── .vscode/settings.json
Phases: 2, 3, 4, 5
Output:
├── .agents/
├── apps/
│ ├── web/ (Next.js)
│ ├── api/ (NestJS)
│ ├── mobile/ (Expo)
│ └── extension/ (Plasmo)
├── packages/
│ └── shared/
├── .eslintrc.js
├── .prettierrc
├── .husky/pre-commit
└── .vscode/settings.json
After full orchestration, your project will have:
project-root/
├── .agents/ # AI-first documentation
│ ├── SESSIONS/ # Daily session logs
│ ├── TASKS/ # Task tracking
│ │ └── INBOX.md
│ ├── SYSTEM/ # Architecture docs
│ │ ├── ARCHITECTURE.md
│ │ └── RULES.md
│ └── README.md
│
├── .claude/ # Claude Code configs
│ ├── commands/
│ ├── rules/
│ └── skills/
│
├── .husky/ # Git hooks
│ └── pre-commit # Runs lint-staged + tests
│
├── .vscode/ # Editor settings
│ └── settings.json # Format on save
│
├── .eslintrc.js # ESLint configuration
├── .prettierrc # Prettier configuration
├── .lintstagedrc # Lint-staged configuration
│
└── [app directories if scaffolded]
After orchestration, verify:
.agents/ folder exists with proper structurenpm run lint or bun lint worksnpm run format or bun format worksUser: "Set up my new project at ~/projects/my-saas"
Orchestrator Response:
I'll initialize your project with full AI-first infrastructure.
Let me gather some context:
1. Tech stack: [Next.js / NestJS / Node.js / Other]
2. Package manager: [bun / pnpm / npm]
3. Test coverage threshold: [80% default]
4. Need scaffolding? [backend / frontend / mobile / extension]
[After user responds]
Starting orchestration...
✓ Phase 2: Agent Folder Init
- Created .agents/ with 13 files
- Copied agent configs (.claude/, .codex/, .cursor/)
✓ Phase 3: Linter Formatter Init
- Detected: Next.js + TypeScript
- Installed: eslint, prettier, lint-staged
- Created: .eslintrc.js, .prettierrc, .lintstagedrc
✓ Phase 4: Husky Test Coverage
- Detected: Jest
- Set threshold: 80%
- Added pre-commit hook
✓ Phase 6: Verification
- All configs created ✓
- Lint check passed ✓
- Git hooks installed ✓
Project initialized successfully!
node, python3)npm run lint:fix to auto-fix.eslintrc.js matches your stacknpx husky install manually.husky/pre-commit exists and is executableprepare script in package.json