Skip to content

heymegabyte/agent-skills / 01-operating-system

operating-system

Verified

Supreme policy layer governing all agent behavior. Autonomy, one-line prompt interpretation, speed standards, emphasis signal processing, cross-skill coordination, done definitions, conflict resolution. Loaded every prompt.

FileKindSize
SKILL.mdskill md6.4 KB
ai-native-coding.mdmarkdown4.3 KB
architecture-thought-loop.mdmarkdown8.3 KB
autonomous-orchestrator.mdmarkdown9.2 KB
context-engineering.mdmarkdown3.2 KB
one-line-saas.mdmarkdown3.0 KB
output-compression.mdmarkdown3.5 KB

one-line-saas.md

View on GitHub
---
name: "one-line-saas"
description: "Execution chain for one-line SaaS prompts. Chains template→scaffold→parallel build→verify→ship."
version: "2.0.0"
updated: "2026-04-23"
---

# One-Line SaaS Execution Chain

When prompt is a one-liner implying a new product (domain name, product idea, or "build X"):

## Phase 0: Research (parallel agents, ~3min)

- **Agent A** — Firecrawl scrape 3-5 competitors → feature list + pricing + positioning
- **Agent B** — Keyphrase research via web search → primary keyphrase + 3 secondaries
- **Agent C** — Infer product type from domain (skill 02) → generate `PROJECT_BRIEF.md` + `SPEC.md` with all ACs
- **Agent D** — If existing website → scrape all pages, extract content + images + brand colors + logo

Research completes BEFORE any code. Builder receives pre-digested context, never calls APIs.

## Phase 1: Scaffold (<5min, sequential, informed by research)

1. `gh repo create <name> --template megabytespace/saas-starter --clone`
2. `cd` into it
3. Run `scripts/scaffold.sh <name> <domain>`
4. Live URL deployed before any feature code

Research data informs scaffold choices (stack, features, pages).

## Phase 2: Content+Media (parallel, ~5min)

- **Agent E** — Generate all copy: hero headline, features, meta desc, JSON-LD, pricing copy. Replace `SITE_NAME`/`HERO_HEADLINE`/etc placeholders in `index.html`.
- **Agent F** — Ideogram logo → favicon set → OG 1200x630 → hero image. Place in `public/`.
- **Agent G** — Generate project `CLAUDE.md` + `.claude/rules/` from brief.
- **Agent H** — Profile all collected images via GPT Image 2 vision → scores, placements, alt text (see skill 12 image-profiling).

## Phase 3: Build (parallel agents in worktrees, ~15min)

- **Agent I (backend)** — Auth webhooks, Stripe checkout/portal/webhooks, domain-specific API routes, Inngest workflows. Sentry + PostHog instrumentation on every route.
- **Agent J (frontend)** — Replace landing page placeholders with real content. Dashboard with real data. Auth pages via Clerk components. Uses pre-profiled images in suggested placements.
- **Agent K (tests)** — Write failing Playwright tests for every SPEC.md AC. Homepage → navigate → interact → verify. Test account flows.

## Phase 4: Verify (parallel, loop max 3)

1. deploy + purge
2. Parallel: deploy-verifier + seo-auditor + visual-qa + test-writer
3. Fix failures
4. Redeploy
5. Re-verify

## Phase 5: Launch

- Update saas-starter template if patterns improved
- Update `~/.agentskills` if new learnings
- Recommendations loop (skill 14) → implement until zero
- DONE

## Parallelization Map

```
Phase 0 [A|B|C|D] ──all complete──→ Phase 1 ──sequential──→
Phase 2 [E|F|G|H] ──all complete──→ Phase 3 [I|J|K] ──all complete──→
Phase 4 [verify loop] ──green──→ Phase 5 [launch]
```

- Main thread orchestrates only. Never implements.
- 11 parallel agents max across phases.
- Research-first: builder receives pre-digested context files, never calls APIs (see skill 06 pre-digested-builds).
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall