Basinfy/Basinfy-SaaS-Studio / .agents/skills/saas-setup-stack
saas-setup-stack
UnverifiedConfigure SaaS stack (Golden Stack for founders or custom Next.js/FastAPI/Go/Cloudflare).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.4 KB |
| references/11-upgrade.md | markdown | 4.4 KB |
| references/12-output-summary.md | markdown | 1.8 KB |
| references/2-guided-mode.md | markdown | 1.7 KB |
| references/3-version.md | markdown | 2.0 KB |
| references/4-claude-md-stack.md | markdown | 2.0 KB |
| references/5-technical-preferences.md | markdown | 5.9 KB |
| references/5.5-project-yaml.md | markdown | 1.8 KB |
| references/6-knowledge-gap.md | markdown | 1.7 KB |
| references/7-reference-docs.md | markdown | 5.9 KB |
| references/7.5-scaffold.md | markdown | 2.5 KB |
| references/8-verify.md | markdown | 921 B |
| references/saas-stack-config.md | markdown | 4.5 KB |
references/11-upgrade.md
View on GitHub# /saas-setup-stack — Section 11: Upgrade Subcommand
> 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.
## 11. Upgrade Subcommand
**In this file:**
- Step 1 — Read Current Version State
- Step 2 — Fetch Migration Guide
- Step 3 — Pre-Upgrade Audit
- Step 4 — Confirm Before Updating
- Step 5 — Update VERSION.md
- Step 6 — Post-Upgrade Reminder
If invoked as `/saas-setup-stack upgrade [old-version] [new-version]`:
### Step 1 — Read Current Version State
Read `docs/engine-reference/<engine>/VERSION.md` to confirm the current pinned
version, risk level, and any migration note URLs already recorded. If
`old-version` was not provided as an argument, use the pinned version from this
file.
### Step 2 — Fetch Migration Guide
Use WebSearch and WebFetch to locate the official migration guide between
`old-version` and `new-version`:
- Search: `"[engine] [old-version] to [new-version] migration guide"`
- Search: `"[engine] [new-version] breaking changes changelog"`
- Fetch the migration guide URL from VERSION.md if one is already recorded,
or use the URL found via search.
Extract: renamed APIs, removed APIs, changed defaults, behavior changes, and
any "must migrate" items.
### Step 3 — Pre-Upgrade Audit
Scan the **code root** (resolve per `.claude/docs/code-root-resolution.md`) for code that uses APIs known to be deprecated or changed in the
target version:
- Use Grep to search for deprecated API names extracted from the migration
guide (e.g., old function names, removed node types, changed property names)
- List each file that matches, with the specific API reference found
Present the audit results as a table:
```
Pre-Upgrade Audit: [engine] [old-version] → [new-version]
==========================================================
Files requiring changes:
File | Deprecated API Found | Effort
--------------------------------- | -------------------------- | ------
src/core/billing_service.ts | old_api_name | Low
src/ui/app-shell.tsx | removed_node_type | Medium
Breaking changes to watch for:
- [change description from migration guide]
- [change description from migration guide]
Recommended migration order (dependency-sorted):
1. [system/layer with fewest dependencies first]
2. [next system]
...
```
If no deprecated APIs are found in the code root, report: "No deprecated API usage
found in the code root — upgrade may be low-risk."
### Step 4 — Confirm Before Updating
Ask the user before making any changes:
> "Pre-upgrade audit complete. Found [N] files using deprecated APIs.
> Proceed with upgrading VERSION.md to [new-version]?
> (This will update the pinned version and add migration notes — it does NOT
> change any source files. Source migration is done manually or via stories.)"
Wait for explicit confirmation before continuing.
### Step 5 — Update VERSION.md
After confirmation:
1. Update `docs/engine-reference/<engine>/VERSION.md`:
- `Engine Version` → `[new-version]`
- `Project Pinned` → today's date
- `Last Docs Verified` → today's date
- Re-evaluate and update the `Risk Level` and `Post-Cutoff Version Timeline`
table if the new version falls beyond the LLM knowledge cutoff
- Add a `## Migration Notes — [old-version] → [new-version]` section
containing: migration guide URL, key breaking changes, deprecated APIs
found in this project, and recommended migration order from the audit
2. If `breaking-changes.md` or `deprecated-apis.md` exist in the engine
reference directory, append the new version's changes to those files.
3. If `project.yaml` exists at the repo root and has an `engine` block, Read it
first, then update `stack.version` to `[new-version]` so the primary config
store stays in sync with VERSION.md.
### Step 6 — Post-Upgrade Reminder
After updating VERSION.md, output:
```
VERSION.md updated: [engine] [old-version] → [new-version]
Next steps:
1. Migrate deprecated API usages in the [N] files listed above
2. Run /saas-setup-stack refresh after upgrading the actual engine binary to
verify no new deprecations were missed
3. Run /saas-architecture-review — the engine upgrade may invalidate ADRs that
reference specific APIs or engine capabilities
4. If any ADRs are invalidated, run /saas-propagate-design-change to update
downstream stories
```
---
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| 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: 194k | Updated | Claude CodeCodex | Verified | Install |