Skip to content

Basinfy/Basinfy-SaaS-Studio / .agents/skills/saas-setup-stack

saas-setup-stack

Unverified

Configure SaaS stack (Golden Stack for founders or custom Next.js/FastAPI/Go/Cloudflare).

references/7.5-scaffold.md

View on GitHub
# /saas-setup-stack — Section 7.5: Scaffold the Engine Project

> Part of `/saas-setup-stack`. `SKILL.md` names when to read this file; the settings it
> resolved and the rules under its later headings still apply here.

## 7.5 Scaffold the Engine Project

**Without this step the framework produces source files no engine can open.**
`/saas-dev-story` writes `.ts`/`.cs`/`.cpp` under the resolved code root, and the `minimal` path
advertises "four steps to running code" — but no other skill writes a
a valid `package.json` or `requirements.txt` for the stack to run.

### Next.js — write `package.json` if one is absent

**Never overwrite an existing `package.json`.** If the file is already there,
say so and skip to Section 8 — the developer has a project and its settings are
theirs.

Show the proposed file, then ask: *"May I create `package.json` at the repo
root?"* On approval, write:

```json
{
  "name": "<project-name>",
  "version": "0.1.0",
  "private": true,
  "scripts": {
    "dev": "next dev",
    "build": "next build",
    "start": "next start",
    "lint": "next lint",
    "test": "vitest run"
  },
  "dependencies": {
    "next": "^15.0.0",
    "react": "^19.0.0",
    "react-dom": "^19.0.0"
  },
  "devDependencies": {
    "typescript": "^5.0.0",
    "@types/node": "^20.0.0",
    "@types/react": "^19.0.0",
    "@types/react-dom": "^19.0.0",
    "tailwindcss": "^3.4.0",
    "vitest": "^2.0.0"
  }
}
```

Fill `<project-name>` from the brief's working title, or the repo directory name.

**Then verify the installation.** Run `node -v` and `npm -v` to ensure the Node.js runtime is operational.

### FastAPI and Cloudflare — instruct, do not fabricate

Tell the user, in one short block, how to initialize the environment:

- **FastAPI** — initialize the Python environment and scaffold via `poetry init` or `uv init` / `pip install -r requirements.txt` at the repo root, then re-run `/saas-setup-stack`.
- **Cloudflare** — initialize the project via `npm create cloudflare@latest` (Wrangler), then re-run `/saas-setup-stack`.

Report the outcome in the Section 12 summary either way — created, already
present, or "not created, instructions provided" — so the user leaves this
skill knowing whether a runnable project exists.

> **Deliberately not a `project.yaml` key.** An `engine.project_scaffolded` flag
> would be written here and read by nothing, which is a dead setting. The filesystem is
> the source of truth: any skill that needs to know globs for `package.json` or `pyproject.toml`.

---
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall