Basinfy/Basinfy-SaaS-Studio / .agents/skills/saas-test-setup
saas-test-setup
UnverifiedScaffold unit, integration, and E2E test runners plus GitHub Actions CI workflows.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.8 KB |
| references/1-detect.md | markdown | 1.7 KB |
| references/2-plan.md | markdown | 1.3 KB |
| references/3-directories.md | markdown | 2.5 KB |
| references/4-ci.md | markdown | 3.5 KB |
| references/5-smoke-seed.md | markdown | 1.4 KB |
| references/6-summary.md | markdown | 1.7 KB |
references/5-smoke-seed.md
View on GitHub# /saas-test-setup — Phase 5: Create Smoke Test Seed
> 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 5: Create Smoke Test Seed
Create `tests/smoke/critical-paths.md`:
```markdown
# Smoke Test: Critical Paths
**Purpose**: Run these 10-15 checks in under 15 minutes before any QA hand-off.
**Run via**: `/saas-smoke-check` (which reads this file)
**Update**: Add new entries when new core systems are implemented.
## Core Stability (always run)
1. Application boots and serves landing/dashboard route without error (200 OK)
2. New product / session can be started from the landing / dashboard
3. Main navigation responds to all inputs without freezing
## Core Workflow (update per sprint)
<!-- Add the primary feature workflow for each sprint here as it is implemented -->
<!-- Example: "User can sign up, create an organization, and invite a team member" -->
4. [Primary feature workflow — update when first core module is implemented]
## Data Integrity & Persistence
5. Database mutations persist across page reloads and tenant switches
6. Row-Level Security (RLS) prevents unauthorized cross-tenant data access
## Performance & Web Vitals
7. Initial page load completes with LCP < 2.5s and zero layout shift
8. No memory leaks or zombie event listeners over 5 minutes of active usage
```
---
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |