Basinfy/Basinfy-SaaS-Studio / .agents/skills/saas-team-seo
saas-team-seo
UnverifiedOrchestrate growth, frontend, content, docs, and QA specialists for SEO & Agent Readiness.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.1 KB |
SKILL.md
View on GitHub---
name: saas-team-seo
description: "Orchestrate growth, frontend, content, docs, and QA specialists for SEO & Agent Readiness."
argument-hint: "[initiative description] [--review full|lean|solo]"
user-invocable: true
---
<!-- Generated from .claude/skills by scripts/sync-agent-skills.py. -->
## Running this workflow on this client
Run commands from the project root (use Git Bash on Windows if `bash` points to an unavailable WSL distro). Shared studio files live in `.claude/`; follow `.agents/PORTABLE-RUNTIME.md` and `.claude/docs/config-resolution.md` for client tools, delegation, and approval rules.
Run `bash .claude/hooks/yaml-helper.sh resolve_config --keys locale,review_mode,automation` and use its output below.
Resolved above — use as-is; `--review` overrides `review_mode` for this run.
# Team SaaS SEO & Growth Engineering
> **Locale & User Profile**: Match `locale` (`pt-BR` → natural Brazilian Portuguese questions/options, overriding English examples; `en` → English) and `user_profile` (`founder` → plain business language with `(Recomendado)` first, zero tech jargon; `developer` → technical). Keep code/tests in English.
Orchestrate the multidisciplinary SEO engineering team to implement high-ranking, AI-search-citable, and regression-tested search architecture for the SaaS product.
**Argument check:** If no initiative description is provided, prompt:
> "Usage: `/saas-team-seo [initiative description] [--review full|lean|solo]` — Describe the SEO or discovery feature (e.g., 'Next.js App Router dynamic metadata and sitemap', 'Competitor comparison pages for Stripe alternatives', 'AI search optimization and llms.txt endpoint')."
---
## Team Roles & Responsibilities
```mermaid
flowchart TD
GD["growth-director (Lead)"] -->|"Target Keywords & SERP Intent"| FE["frontend-engineer"]
GD -->|"E-E-A-T & Citable Blocks"| UX["ux-content-strategist"]
UX -->|"Comparison Matrices & Data"| TW["technical-writer"]
FE -->|"App Router Metadata & JSON-LD"| QA["qa-lead"]
QA -->|"Core Web Vitals & Drift Verification"| Complete["Complete Initiative"]
```
1. **`growth-director` (Tier 2 Lead)**:
- Identifies business archetype, target buyer personas, ICP search queries, and competitor gap opportunities.
- Designs hub-and-spoke topic architecture and determines whether programmatic expansion is viable.
2. **`frontend-engineer` (Tier 3 Execution)**:
- Implements Next.js 14+ `generateMetadata` with full OpenGraph, Twitter Cards, and canonical tags.
- Builds dynamic `app/robots.ts` and `app/sitemap.ts`.
- Embeds server-rendered Schema.org JSON-LD React Server Components (`SoftwareApplication`, `Organization`, `Product`, `Offer`).
- Implements machine-readable discovery (`app/llms.txt/route.ts` and `Accept: text/markdown` content negotiation).
3. **`ux-content-strategist` (Tier 2 Lead)**:
- Drafts front-loaded citable answer blocks (130-170 words answering queries within the first 40-60 words).
- Enforces E-E-A-T credentials, author bios, and factual sourcing.
- Humanizes AI drafts, stripping AI cliches, padding, and invisible Unicode watermarks.
4. **`technical-writer` (Tier 3 Execution)**:
- Builds accurate feature comparison matrices ("X vs Y", "Alternatives to X") with verifiable public citations.
- Authors technical documentation, integration guides, and glossary entries for programmatic SEO directories.
5. **`qa-lead` (Tier 2 Lead)**:
- Audits Core Web Vitals (LCP < 2.5s, CLS < 0.1, INP < 200ms) and mobile responsiveness.
- Runs `scripts/seo/drift_baseline.py` to lock a pre-deploy snapshot.
- Runs `scripts/seo/drift_compare.py` during CI/CD to ensure zero breaking regressions (no accidental `noindex`, dropped canonicals, or removed headings).
---
## 5-Step Collaborative Loop
1. **Question**: Present current SEO posture and baseline findings.
2. **Options**: Provide 2-3 architectural approaches (e.g. static SSG vs dynamic ISR metadata).
3. **Decision**: Agree on selected approach with user confirmation.
4. **Draft**: Formulate Next.js components, routes, and JSON-LD schemas.
5. **Approval**: Always ask `May I write this to [filepath]?` before modifying disk.
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 |