team-content

Orchestrate content workflows across strategist, designer, localization-lead, and ux-designer roles.

39|6|Updated May 3, 2026
One-click install
npx skills add https://github.com/cenconq25/claude-code-app-studio --skill team-content
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-content
Source: https://github.com/cenconq25/claude-code-app-studio/tree/main/.claude/skills/team-content
Command: npx skills add https://github.com/cenconq25/claude-code-app-studio --skill team-content

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrate the content pipeline across roles to ensure briefs are turned into shipped, localized content with quality gates.

Core Features & Use Cases

  • Orchestrates collaboration among content-strategist, content-designer, localization-lead, and ux-designer.
  • Automates phase progression from brief to shipped state, including localization planning and reviews.
  • Use Case: A new feature requires copy across multiple screens and locales; this skill aligns roles and ensures timely delivery.

Quick Start

Spawn a brief and let the content-strategist coordinate the end-to-end content pipeline from concept to shipped, localized copy.

Frequently Asked Questions about team-content

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage a content pipeline across multiple UX roles and locales?

Managing a content pipeline across roles requires orchestrating phases from brief resolution to drafting, UX review, localization planning, and final package rendering to ensure shipped copy consistency.

What is the best way to coordinate content strategists and localization leads on feature briefs?

The best way to coordinate strategists and localization leads is enforcing a structured workflow that automates phase progression from initial brief to shipped, localized copy while applying necessary quality gates.

How do I ensure consistent voice across multiple screens during content drafting?

To ensure consistent voice across multiple screens, a content-designer must coordinate with UX designers during the drafting and review phases, enforcing structured quality gates before final package rendering.

Does this content workflow approach support feature briefs spanning multiple locales?

Yes, this content workflow approach specifically supports feature briefs spanning multiple locales by integrating a dedicated localization planning phase and localization lead role before final copy packaging.

When do I need a structured end-to-end content pipeline for UX writing?

You need a structured end-to-end content pipeline for UX writing when a feature spans multiple screens and locales, and consistency of voice alongside localization timing are critical for delivery.