Ready-made commands
for every task

Slack Replies

Use Slack Answer when you are looking at a Slack conversation and want a quick, natural-sounding reply without overthinking the wording. It reads your screen context to understand the thread, then writes a short reply that matches the tone and energy of the conversation. Perfect for when you know what you want to say but want to get the phrasing right in two seconds.

Type in your language, get natural English. Keeps your tone, uses simple words.

Use To English when you think or draft in your native language and need the result in natural-sounding English. It detects the source language automatically and produces fluent English that matches your original tone, whether casual, formal, or frustrated. Unlike machine translation, the output reads like a native English speaker wrote it from scratch.

Refactor and optimize code following best practices and clean code principles.

Use Code Improver when you have working code that needs a quality pass. It applies clean code principles, adds proper error handling, improves naming, and follows language-specific conventions. Ideal for preparing code for review or upgrading legacy snippets to modern standards.

Convert any text into well-structured, clean Markdown.

Use To Markdown when you have raw notes, meeting dumps, or unformatted text that needs to look polished. It automatically selects the right Markdown elements such as headings, lists, tables, and code blocks to represent your content. Great for turning rough drafts into documentation-ready output.

Rewrite for professional context - emails, Slack, docs.

Use Professional Tone when drafting emails, Slack messages, or documents that need to sound polished without being stiff. It cleans up casual language, removes filler words, and adjusts phrasing to suit a business context while keeping your original meaning intact.

Write LinkedIn posts that actually get seen - built on 2026 algorithm guidelines for reach, hooks, and engagement.

Use LinkedIn when you have an idea, story, or opinion you want to share as a LinkedIn post optimized for reach. It structures your input with an attention-grabbing hook, proper spacing, and a conversation-starting question at the end. The output follows 2026 algorithm best practices including ideal character count, no external links, and natural hashtags.

Extract clear action items, owners, and deadlines from any text.

Use Action Items after meetings, calls, or long Slack threads to pull out every task, decision, and open question into a structured checklist. It identifies owners and deadlines mentioned in the text and formats everything as markdown checkboxes. Ideal for turning messy meeting notes into a clear list your team can act on immediately.

Generate a comprehensive technical design document from a feature description.

Use Tech Design when you need to turn a feature idea into a structured engineering plan. It generates architecture decisions, API contracts, data models, and effort estimates. Ideal for kicking off a project, aligning with your team, or creating a lightweight RFC before writing code.

Provide one distinct rewritten variation of the same text.

Use Generate Alternative when your first draft feels flat or you want a fresh angle on the same idea. It rewrites your text with different word choices, sentence structures, and framing while keeping the core message. Useful for landing pages, pitch decks, or any writing where you want options to compare.

Generate multiple creative ideas and approaches for any topic or problem.

Use Brainstorm when you are stuck on a problem, exploring a new initiative, or need multiple angles on a topic fast. It generates five to eight distinct ideas ranging from quick wins to ambitious bets, each with a punchy title and actionable explanation. Perfect for product planning sessions, marketing campaigns, or any creative challenge where you want diverse options to evaluate.

Generate a Product Requirements Document from a feature idea or brief.

Use PRD Gen when you need to transform a rough feature idea into a structured product requirements document. It covers problem statements, user stories, scope, success metrics, and open questions. Perfect for product managers kicking off a new feature or engineers who need to write lightweight specs.

Rewrite in natural everyday English that doesn't feel AI-edited.

Use Casual Tone when your writing sounds too stiff, robotic, or overly formal and you want it to read like a real person wrote it. It rewrites text in natural everyday English with contractions and conversational flow while keeping your meaning intact. Great for softening corporate-speak in Slack messages, internal docs, or blog drafts.

Paste any error message or stack trace and get a plain-English explanation with specific fix suggestions.

Use Explain Error when you hit a confusing error message or stack trace and want to understand what went wrong without digging through documentation. It translates the error into plain English, identifies the root cause, and gives you two to three specific steps to fix it. Works with any language or framework including Python, JavaScript, Java, Go, SQL, and shell errors.

Explain any concept, paragraph, or document as if you're talking to a curious 12-year-old - using everyday analogies and zero jargon.

Use ELI5 when you encounter a dense paragraph, technical concept, or jargon-heavy document and want it explained simply. It breaks down any topic using everyday analogies and zero jargon, ending with a clear one-line summary. Ideal for learning new domains, explaining technical decisions to non-technical stakeholders, or making sense of legal or financial text.