Writing

Analyzes a project's niche to inject domain-specific knowledge, regulations, and UX standards. Use after defining the niche to produce a dossier of sector-specific intelligence for product, design, and technology alignment.

Create, iterate, and scale paid ad creative for Google Ads, Meta, LinkedIn, TikTok, and similar platforms. Use when generating headlines, descriptions, primary text, or large sets of ad variations for testing and performance optimization.

Generates compelling ad copy and creative concepts for marketing campaigns using Claude AI. Ideal for marketers needing quick, high-quality ad variations.

Drafts professional customer-facing responses tailored to the situation and relationship. Use for answering product questions, handling escalations, delivering bad news, declining feature requests, or resolving billing issues.

Draft knowledge base articles from resolved support tickets, recurring questions, or known issues to enable customer self-service.

Provides title styles, body templates, and section guidance for writing consistent, review-ready pull request descriptions in the Fluid Framework repository.

Author, edit, or extend Carbon's documentation site — a Fumadocs + Next.js app. Use for reader-facing guides, reference pages, and documentation IA. Grounds every claim in source code and follows a warm-paper house style.

Generates or refreshes AGENTS.md files for Carbon packages and ERP modules by analyzing the actual source code. Ensures every documentation claim is verified against real functions, tables, and exports.

Guides the design of a feature by researching competitors, identifying open questions, and resolving them with users before writing a structured specification document. Ideal for new modules, cross-module changes, or data model updates that touch 3+ files.

Helps write and maintain documentation for the Carbon manufacturing platform (ERP+MES) using its Fumadocs site. Guides authoring in the house style with real MDX components and source-grounded verification.

Guides feature design by researching competitors, surfacing open questions, and interviewing stakeholders before writing the spec. Use for new modules, data model changes, or changes across 3+ files.

Format a Markdown file to match Liferay conventions — frontmatter order, Title Case headings, braced shell variables, long-form CLI flags, and professional prose. Use when the user asks to format, clean up, polish, or copy-edit a Markdown file destined for the Liferay repository.