Writing

Generates high-performing paid ad copy for platforms like Google Ads, Meta, LinkedIn, and TikTok. Use to create headlines, descriptions, and primary text at scale, and iterate based on performance data.

Mimics the strategic thinking of Marc Andreessen to provide advice on productivity, startups, and decision-making. Ideal for entrepreneurs seeking an AI mentor.

Generates compelling ad copy and creative assets using AI, optimized for conversions and audience engagement.

Draft a professional customer-facing response tailored to the situation and relationship. Use when answering a product question, responding to an escalation or outage, delivering bad news like a delay or won't-fix, declining a feature request, or replying to a billing issue.

Drafts a publish-ready knowledge base article from a resolved support issue, common question, or documented workaround. Use when the same question keeps coming up, a workaround needs to be published, or a known issue should be communicated to customers.

Updates Noridoc documentation files across the codebase after code changes, using a subagent to ensure architectural and system-level documentation stays accurate.

Creates comprehensive implementation plans with exact file paths, code examples, and verification steps for engineers with minimal domain knowledge. Use when design is complete and detailed tasks are needed.

Author and maintain the Carbon documentation site (Fumadocs+Next.js). Covers editorial Guides, Reference pages, and a grounded-in-source verification workflow.

Researches how best-in-class ERP systems and point solutions implement a feature, producing a structured findings file. Ideal for designing new features, evaluating approaches, or understanding industry standards in accounting, manufacturing, inventory, and more.

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.

Formats Markdown files to follow Liferay’s documentation conventions, including frontmatter structure, title case headings, shell variable syntax, and CLI flag style. Ideal for preparing or polishing Markdown content for the Liferay project.