Orchestrate the content & communication team — ux-content-strategist, copywriter, api-documentation-engineer, frontend-engineer — UX writing, API docs, transactional emails, and onboarding.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys locale,review_mode,automation
Resolved above — use as-is; --review overrides review_mode for this run.
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.
Orchestrate the content and technical documentation team to author clear product microcopy, transactional email sequences, OpenAPI specifications, and interactive developer docs.
Argument check: If no description is provided, output:
"Usage:
/saas-team-content [content description] [--review full|lean|solo]— Describe the content or documentation deliverable (e.g. Transactional email notification suite, Developer API reference documentation, Onboarding empty states and tooltips, Product knowledge base)."
When this skill is invoked with a valid argument, orchestrate the team:
UX Writing & Microcopy:
ux-content-strategist: Craft clear, human, error messages, empty-state descriptions, tooltip helpers, and modal confirmationsTransactional Emails:
copywriter: Author responsive transactional emails (Welcome & verification, Workspace invite, Password reset, Invoice receipt, Usage threshold warning)frontend-engineer: Implement email templates using React Email / HTML with responsive mobile stylingAPI & Developer Documentation:
api-documentation-engineer: Generate OpenAPI 3.1 schema from route handlers, write curl and SDK code examples, document error status codes and authentication schemesReview & Proofing:
Verdict:
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Turn your AI session into an autonomous SaaS and software engineering studio with 49 specialized agents, 74 workflow skills (/saas-*), 28 director gates, and complete architecture across Next.js, FastAPI, Supabase, Tailwind, and Stripe.
The English summary is being prepared. Showing the original description.
Brownfield audit — do existing artifacts actually work? Numbered migration plan. Unlike /saas-project-stage-detect, checks compliance not existence.
The English summary is being prepared. Showing the original description.
Create an ADR documenting a technical decision: context, alternatives considered, consequences.
The English summary is being prepared. Showing the original description.
Traceability matrix mapping PRD requirements to ADRs. Finds gaps, cross-ADR conflicts, stack compatibility. PASS/CONCERNS/NOT ASSESSED/FAIL.
The English summary is being prepared. Showing the original description.
Audit assets against naming conventions, file size budgets, format standards. Finds orphaned assets, missing references.
The English summary is being prepared. Showing the original description.
Author per-asset visual specs, SVG dimensions, and generation prompts from PRDs and design tokens. After design tokens.
The English summary is being prepared. Showing the original description.