SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillsnew-project-setup

new-project-setup

Coding & development

View repository

Updated 10-15 21:42

About this skill

New FMC project setup

Orchestration only. Read sibling skills for how-to; this skill defines order, plan defaults, and three commits.

Plan

Ask: project name, copyright holder, app type (TanStack Start default, or TanStack Router SPA), maps?

Present the checklist below; confirm all ask items before executing.

Action Meaning
default Do/install unless the user overrides
ask Confirm with the user first
skip Omit unless the user asks
report Summary only — do not install or commit

Repo & license

  • git init — default when no .git; skip when repo exists
  • AGPL-3.0 LICENSE.md — default; ask copyright holder if unknown (README only)

Skills — default (bunx skills add FixMyBerlin/fixmyskills … -a cursor -y)

  • finish-work, tech-stack, agent-orchestration
  • react-dev — TanStack/React; skip non-UI
  • tanstack-router-conventions — TanStack Router (SPA or Start); skip non-TanStack
  • tanstack-start-conventions — TanStack Start only; skip for Router SPA and other frameworks
  • review-dependabot — GitHub FMC; skip non-GitHub

Skills — ask

  • react-map-gl — maps? (skip when no maps)
  • tanstack-start-auth — auth? (skip unless Start) · playwright-skill — E2E? · prisma — DB?
  • zustand-state-management — client global state? · user-changelog — public releases?
  • rust-wasm-geo — WASM geo? · tanstack-better-upload — S3 uploads? (skip unless Start)

Dev tooling — default: skill tech-stack (skip empty meta-repo). Ask/report: CI now or later; MCP → report ~/.cursor/mcp.json only; touch-ipad-review / unslop-code / unslop-text → report on-demand.

Run order

- [ ] Plan confirmed
- [ ] git init (if needed)
- [ ] License → finish-work commit 1
- [ ] Skills + orchestration → finish-work commit 2
- [ ] Dev tooling → finish-work commit 3
- [ ] Summary
Step Do Skill
Git test -d .git || git init —
License Verbatim AGPL-3.0 as tilda-geo LICENSE.md; README links it finish-work → commit 1
Skills bunx skills add … per plan; then init-cursor.sh agent-orchestration → commit 2
Dev tooling bunfig, oxc, dependabot, tsconfig, vscode when package.json exists tech-stack → commit 3
Each commit Separate commit; never batch finish-work

End with summary: installed skills, skipped items, follow-ups, three commit SHAs.