Skip to content

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

saas-test-setup

Unverified

Scaffold unit, integration, and E2E test runners plus GitHub Actions CI workflows.

FileKindSize
SKILL.mdskill md3.8 KB
references/1-detect.mdmarkdown1.7 KB
references/2-plan.mdmarkdown1.3 KB
references/3-directories.mdmarkdown2.5 KB
references/4-ci.mdmarkdown3.5 KB
references/5-smoke-seed.mdmarkdown1.4 KB
references/6-summary.mdmarkdown1.7 KB

references/1-detect.md

View on GitHub
# /saas-test-setup — Phase 1: Detect Engine and Existing State

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

## Phase 1: Detect Engine and Existing State

1. **Read engine config**:
   - Read `stack.frontend` from `project.yaml`; if that key is absent or empty
     (including when `project.yaml` has no `engine:` block), fall back to the
     `Engine:` value in `.claude/docs/technical-preferences.md`.
   - If neither source yields a configured engine (project.yaml `stack.frontend`
     absent/empty and technical-preferences.md shows `[TO BE CONFIGURED]` or is
     missing), stop:
     "Engine not configured. Run `/saas-setup-stack` first, then re-run `/saas-test-setup`."

2. **Check for existing test infrastructure**:
   - Glob `tests/` — does the directory exist?
   - Glob `tests/unit/` and `tests/integration/` — do subdirectories exist?
   - Glob `.github/workflows/` — does a CI workflow file exist?
   - Glob `node_modules/vitest/` (Next.js / Vitest),
     `tests/` or `pytest.ini` (FastAPI / Pytest), or
     `node_modules/wrangler/` (Cloudflare) for stack-specific artifacts.

3. **Report findings**:
   - "Engine: [engine]. Test directory: [found / not found]. CI workflow: [found / not found]."
   - If everything already exists AND `force` argument was not passed:
     "Test infrastructure appears to be in place. Re-run with `/saas-test-setup force`
     to regenerate. Proceeding will not overwrite existing test files."

If the `force` argument is passed, skip the "already exists" early-exit and
proceed — but still do not overwrite files that already exist at a given path.
Only create files that are missing.

---
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall