Create, read, edit, and manipulate Word documents (.docx files) with full formatting control. Create new .docx files from scratch using JavaScript with support for headings, tables, images, hyperlinks, footnotes, headers/footers, and table of contents Edit existing documents by unpacking XML, making targeted changes (including tracked changes and comments), and repacking with validation Extract text and analyze content using pandoc or raw XML access; convert legacy .doc files to .docx format Handle professional formatting: page sizes (US Letter/A4), margins, multi-column layouts, tab stops, and styled lists without manual unicode characters
Structured workflow for collaboratively authoring documentation, proposals, specs, and similar content. Guides users through three stages: Context Gathering (closing knowledge gaps), Refinement & Structure (building sections iteratively), and Reader Testing (validating the doc works for fresh readers) Supports integration with shared documents, team channels, and templates to pull in context directly when connectors are available Uses brainstorming and curation cycles for each section, with surgical edits and iterative refinement based on user feedback Includes reader testing via sub-agents (when available) or manual testing instructions to catch blind spots before others read the document
Templates and guidelines for writing company-standard internal communications across multiple formats. Covers seven communication types: 3P updates, company newsletters, FAQ responses, status reports, leadership updates, project updates, and incident reports Each format has a dedicated guideline file in the examples/ directory with specific instructions for tone, structure, and content Helps maintain consistency across internal communications by enforcing company-preferred formats and styles Falls back to general communication guidelines for formats not explicitly covered by specialized templates
Expert technical writer for Diátaxis-framework documentation creation across tutorials, how-to guides, reference, and explanation formats. Structures documentation into four distinct types: tutorials for learning, how-to guides for problem-solving, reference for technical specifications, and explanations for conceptual understanding Follows a three-step workflow: clarify document type and audience, propose a detailed outline for approval, then generate full markdown content Maintains consistency through guiding principles of clarity, accuracy, user-centricity, and uniform tone and terminology across all documents Integrates context from existing project documentation to match established style without duplicating content
Convert Markdown documents to HTML using marked.js, pandoc, gomarkdown, or static site generators. Supports multiple conversion tools: marked.js for Node.js/CLI workflows, pandoc for cross-format conversion, gomarkdown for Go projects, and Jekyll/Hugo for static site generation Handles all standard Markdown flavors including CommonMark, GitHub Flavored Markdown, and extended syntax for tables, code blocks, math expressions, and collapsed sections Provides CLI and programmatic workflows for single-file conversions, batch processing, and integration with web templating systems Includes security guidance for sanitizing untrusted input and configuration examples for each tool's specific options and troubleshooting
Generates concise, actionable meeting minutes for internal meetings under 60 minutes with standardized metadata, decisions, and assigned action items. Captures attendees, agenda, decisions with rationale, and action items with owner and due date for immediate task tracking Follows a strict schema covering metadata, decisions, action items, notes by agenda item, parking lot, risks, and follow-ups Accepts multiple input formats: transcripts, recordings, slides, raw notes, or live meeting capture Asks up to three clarifying questions upfront if critical details (title, date, organizer, source material) are missing before drafting
Detect and remove AI-generated patterns from Finnish text to match native speaker voice. Identifies 26 patterns across Finnish-specific structures (passive overuse, missing particles, translation calques, genitive chains) and universal markers (hedging, filler phrases, artificial enthusiasm) Preserves meaning, register, and technical content while replacing AI patterns with natural Finnish constructions Includes adaptive workflow: analyzes short texts directly, flags patterns in longer documents for review before rewriting Emphasizes Finnish voice principles: directness, brevity, particle use, and strategic understatement over AI's tendency toward formality and padding
Structured prompt for generating Epic-level Product Requirements Documents with consistent output format. Guides product managers through a standardized PRD structure covering goals, user personas, journeys, functional and non-functional requirements, success metrics, and scope boundaries Outputs markdown-formatted PRDs saved to a consistent directory path ( /docs/ways-of-work/plan/{epic-name}/epic.md ) for use as single source of truth Includes built-in prompting for clarifying questions when information is incomplete, ensuring comprehensive epic definition before handoff to engineering Designed as input preparation for downstream technical architecture specification generation
Convert plain text documentation to markdown with flexible formatting options. Supports three conversion approaches: explicit instructions, documented options, or reference file templates for consistent formatting patterns Includes predefined instruction shortcuts for common tasks like removing header digits, adjusting heading levels, and reducing indentation Handles code block detection with language identification, proper list nesting, and markdown syntax compliance across multiple target platforms (GitHub, GitLab, VS Code, CommonMark, StackOverflow) Optional finalization mode trims formatting inconsistencies, escapes special characters, and standardizes spacing throughout the document
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
ERROR - NOT ENOUGH TEXT ON PAGE
Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when…
SEO and AEO best practices for metadata, Open Graph, sitemaps, robots.txt, hreflang, JSON-LD structured data, EEAT, and content optimized for search engines…
Draft marketing content across channels — blog posts, social media, email newsletters, landing pages, press releases, and case studies. Use when writing any…
Structured content modeling guidance for schema design, content architecture, content reuse, references versus embedded objects, separation of concerns, and…