Basinfy/Basinfy-SaaS-Studio / .agents/skills/saas-setup-stack
saas-setup-stack
UnverifiedConfigure engine and version. Pins it in CLAUDE.md; WebSearch fills reference docs when the version is beyond LLM training data.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.3 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 | 3.7 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 | 2.4 KB |
| references/saas-stack-config.md | markdown | 4.5 KB |
references/7-reference-docs.md
View on GitHub# /saas-setup-stack — Section 7: Populate Engine Reference Docs
> 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. Populate Engine Reference Docs
**In this file:**
- First: does a reference set already exist for this engine?
- Sourcing rule for everything written in this section
- If WITHIN training data (LOW RISK):
- If BEYOND training data (MEDIUM or HIGH RISK):
### First: does a reference set already exist for this engine?
**Check before doing anything else.** The template ships
`docs/engine-reference/nextjs/`, `fastapi/` and `cloudflare/` **already populated**, so
"the directory exists and pins a version" is the state of *every* fresh project,
not an edge case. Both branches below say "create", and following either one
literally on a pre-populated directory either overwrites curated content or
leaves `project.yaml` and the CLAUDE.md-imported reference disagreeing.
Read `docs/engine-reference/<engine>/VERSION.md` and compare its
**Engine Version** to the version chosen in Section 3:
- **No directory, or no `VERSION.md`** → create, using the risk branch below.
- **Same version** → nothing to regenerate. Refresh `Last Docs Verified` only if you
actually re-verified against the docs this run. Do not restamp a date you did
not check. The one row still written is `Installed at pin time`, from
Section 3 — its probe result is recorded whatever the outcome, after asking
"May I record `Installed at pin time: [result]` in
`docs/engine-reference/<engine>/VERSION.md`?" (it is a tracked file).
- **Directory pins an OLDER version than the one chosen** → **update, do not
replace.** This is the common case. Show the changes below, then ask "May I
update the `docs/engine-reference/<engine>/` files for [version]?" before editing.
1. Edit `VERSION.md` in place: new **Engine Version**, new **Project Pinned**
and **Last Docs Verified**, the `Installed at pin time` row from Section 3,
and a new row in the post-cutoff timeline for each version added.
2. **Append** to `breaking-changes.md`, `deprecated-apis.md` and
`current-best-practices.md` under a heading naming the version span
(`## 4.6 → 4.7`). Never truncate the older spans — a project migrating
across two versions still needs the earlier one.
3. Re-grade the older timeline rows if the cutoff moved past them.
- **Directory pins a NEWER version than the one chosen** → stop and ask. Someone
pinned forward deliberately, or the version choice is wrong. Do not silently
downgrade a curated reference.
### Sourcing rule for everything written in this section
**Never fill a gap from training data. Write the gap down instead.**
The whole purpose of these files is to be the thing agents consult *instead of*
their training data. A confidently wrong entry here is worse than no entry: it
produces work that looks verified and is not.
- Every claim must come from a page you fetched this run. Record the URL.
- If the official docs do not state something the template asks for — a release
date, a subsystem's behaviour, web-export specifics — write
**`NOT SOURCEABLE — <what>, not stated at <url>`** and move on.
- A `NOT SOURCEABLE` line is a successful outcome, not a failure to finish.
- Do not infer one fact from an adjacent one. "The migration guide lists no
ORM change" is not "the database ORM default is unchanged"; if you record the
inference, label it as an inference and name what it rests on.
### If WITHIN training data (LOW RISK):
Ask: "May I create `docs/engine-reference/<engine>/VERSION.md`?" Wait for
confirmation, then create this minimal file:
```markdown
# [Engine] — Version Reference
| Field | Value |
|-------|-------|
| **Engine Version** | [version] |
| **Project Pinned** | [today's date] |
| **Installed at pin time** | [Section 3 result — the installed version, or NOT DETERMINED] |
| **LLM Knowledge Cutoff** | [the cutoff from the Section 6 coverage table] |
| **Risk Level** | LOW — version is within LLM training data |
## Note
This engine version is within the LLM's training data. Stack reference
docs are optional but can be added later if agents suggest incorrect APIs.
Run `/saas-setup-stack refresh` to populate full reference docs at any time.
```
Do NOT create breaking-changes.md, deprecated-apis.md, etc. — they would
add context cost with minimal value.
### If BEYOND training data (MEDIUM or HIGH RISK):
Create the full reference doc set by searching the web:
1. **Search for the official migration/upgrade guide**:
- `"[engine] [old version] to [new version] migration guide"`
- `"[engine] [version] breaking changes"`
- `"[engine] [version] changelog"`
- `"[engine] [version] deprecated API"`
2. **Fetch and extract** from official documentation:
- Breaking changes between each version from the training cutoff to current
- Deprecated APIs with replacements
- New features and best practices
Ask: "May I create the stack reference docs under `docs/engine-reference/<engine>/`?"
Wait for confirmation before writing any files.
3. **Create the full reference directory**:
```
docs/engine-reference/<engine>/
├── VERSION.md # Version pin + knowledge gap analysis
├── breaking-changes.md # Version-by-version breaking changes
├── deprecated-apis.md # "Don't use X → Use Y" tables
├── current-best-practices.md # New practices since training cutoff
└── modules/ # Per-subsystem references (create as needed)
```
4. **Populate each file** using real data from the web searches, following
the format established in existing reference docs. Every file must have
a "Last verified: [date]" header.
5. **For module files**: Only create modules for subsystems where significant
changes occurred. Don't create empty or minimal module files.
---
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 467k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 196k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |