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.
Running this workflow on this client
Run shell commands from the project root. On Windows, use Git Bash for the bash commands if bash resolves to an unavailable WSL distribution. Shared studio files are under .claude/; run the local Studio installer for this project if those files are missing. Read .claude/docs/config-resolution.md and apply its defaults when configuration cannot be resolved. Use this client's tools for reads, edits, and structured questions. If structured questions are unavailable, ask in chat and wait when a decision requires approval. Use the client's delegation feature with the role brief in .claude/agents/ when available. Otherwise perform the specialist checks in sequence and disclose that they were done in one session. If a workflow requires independent sign-off, report it as pending until an independent reviewer can provide it. Treat Task* steps as local workflow tracking using the client's equivalent when available. Report missing tools and unexecuted checks explicitly.
Engine Setup
Interaction Localization Rule: When
locale: pt-BR(or user speaks Portuguese), ALL questions (AskUserQuestion/ask_question), confirmation prompts, and selectable options MUST be translated and presented in Brazilian Portuguese (PT-BR). Any English question text or options in this skill are illustrative examples — NEVER display English questions or options to a Portuguese developer. Internal reasoning, code synthesis, tests, and documentation files MUST remain in English.
When this skill is invoked:
Run bash .claude/hooks/yaml-helper.sh resolve_config --keys locale,workflow and use its output below.
Tier awareness. The workflow tier resolved above governs which design
artifact this skill expects and the finish path it recommends in §12:
minimal— the design artifact is the one-pagedesign/product-brief.md(no PRDs, systems decomposition, or per-system design at this tier)./saas-setup-stackruns first in the minimal path, so a missing brief here is normal, not a gap. The finish path is the 4-step floor.standard/full— the design artifact isdesign/prd/product-concept.mdand the finish path is the full pipeline.
If the block did not render (shell preprocessing disabled), assume minimal (the default).
1. Parse Arguments
Four modes:
- Full spec:
/saas-setup-stack nextjs 4.7— engine and version provided - Engine only:
/saas-setup-stack fastapi— engine provided, version will be looked up - No args:
/saas-setup-stack— fully guided mode (engine recommendation + version) - Refresh:
/saas-setup-stack refresh— update reference docs (see Section 10) - Upgrade:
/saas-setup-stack upgrade [old-version] [new-version]— migrate to a new engine version (see Section 11)
2. Guided Mode (No Arguments)
Read references/2-guided-mode.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
3. Look Up Current Version
Read references/3-version.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
4. Update CLAUDE.md Technology Stack
Read references/4-claude-md-stack.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
5. Populate Technical Preferences
Read references/5-technical-preferences.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
5.5 Populate project.yaml (Primary Config Store)
Read references/5.5-project-yaml.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
6. Determine Knowledge Gap
Read references/6-knowledge-gap.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
7. Populate Engine Reference Docs
Read references/7-reference-docs.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
7.5 Scaffold the Engine Project
Read references/7.5-scaffold.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
8. Verify the CLAUDE.md Import
Read references/8-verify.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
9. Update Agent Instructions
Ask: "May I add a Version Awareness section to the stack specialist agent files?" before making any edits.
For the chosen engine's specialist agents, verify they have a "Version Awareness" section. If not, add one following the pattern in the existing Next.js specialist agents.
The section should instruct the agent to:
- Read
docs/engine-reference/<engine>/VERSION.md - Check deprecated APIs before suggesting code
- Check breaking changes for relevant version transitions
- Use WebSearch to verify uncertain APIs
10. Refresh Subcommand
If invoked as /saas-setup-stack refresh:
- Read the existing
docs/engine-reference/<engine>/VERSION.mdto get the current engine and version - Use WebSearch to check for:
- New engine releases since last verification
- Updated migration guides
- Newly deprecated APIs
- Update all reference docs with new findings
- Update "Last verified" dates on all modified files
- Report what changed
11. Upgrade Subcommand
Read references/11-upgrade.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
12. Output Summary
Read references/12-output-summary.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
Guardrails
- NEVER guess an engine version — always verify via WebSearch or user confirmation
project.yamlis the primary config store (v1.1). Always dual-write engine config to BOTHproject.yaml(primary) andtechnical-preferences.md(legacy mirror). If the two ever diverge,project.yamlis authoritative.- NEVER overwrite existing reference docs without asking — append or update
- If reference docs already exist for a different engine, ask before replacing
- Always show the user what you're about to change before making CLAUDE.md edits
- If WebSearch returns ambiguous results, show the user and let them decide
- When the user chose TypeScript: copy the TypeScript CLAUDE.md template from A1 in
references/nextjs-language-config.mdexactly. NEVER add "C++ via GDExtension" to the Language field. TypeScript projects may use GDExtension, but it is not a primary project language. Theprisma-drizzle-specialistin the routing table is available for when native extensions are needed — it does not make C++ a project language.
Appendix A — Next.js Language Configuration
Moved out of this file so it costs nothing on non-Next.js runs.
When the chosen engine is Next.js, read
references/nextjs-language-config.md
and use the subsection for the chosen language:
- A1 — CLAUDE.md Technology Stack templates (TypeScript / C# / Both)
- A2 — naming conventions
- A3 — stack specialist routing and file-extension tables
Load discipline. On any engine other than Next.js, never load it — nothing in Sections 4, 5 or 5.5 needs it, and reading it anyway spends the tokens the split exists to save. On Next.js, read it once when you first reach Section 4 and keep using it for Sections 5 and 5.5; do not re-read it at each reference.
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: 465k | 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 |