Designs decentralized apps from brief to production — user + trust-boundary mapping, contract architecture, client layer, indexing strategy, off-chain components, deployment pipeline, and ops. Use when starting a new dApp and needing a coherent plan before code, auditing an existing dApp for architectural gaps, or teaching a team to think through dApp design instead of stumbling into it.
Turns one piece of content into multiple surfaces — blog post → Twitter/X thread → LinkedIn post → newsletter issue — matching each platform's conventions. Use when a user has shipped a long-form piece and wants to extract shorter variants for other channels, or is planning a content launch across multiple platforms.
Drafts emails in the right tone and length for the situation — cold outreach, follow-up, introduction, apology, thank-you, difficult conversation. Use when a user needs to write an email they're stuck on, rewrite an email that sounds off, or draft a template they'll reuse for similar situations.
Produces meeting notes that capture decisions and action items — not transcription. Attendees, agenda, decisions, action items with owners and deadlines. Use when a user needs notes from a meeting that's about to happen, is happening, or just ended, or wants a template for recurring meetings.
Produces research briefs that answer a question — sources, synthesis, gaps, recommendation — rather than summaries that describe a topic. Use when a user needs to research a decision, investigate a market or tool, understand an unfamiliar domain quickly, or present findings to a stakeholder who wants an answer, not a report.
Tailors a résumé to a specific job description — parses the JD for priorities, reorders and rewrites bullets to match, quantifies achievements, and passes ATS filters. Use when a user is applying to a specific role and wants their résumé to match the JD, or when their bullets are weak ("responsible for...") and need tightening.
Tightens prose — removes fluff, varies sentence length, prefers concrete verbs, matches a target voice. Use when a user wants to edit or rewrite a draft (email, post, README, memo), when copy reads "AI-generated" and needs to sound human, or when matching a specific writer's voice.
Ready-to-use git recipes for the operations people actually run every day — undoing mistakes, safe rebasing, resolving conflicts, rescuing lost work, and PR-friendly history cleanup. Use when a user asks how to undo a git operation, clean up a branch before merging, recover from a bad push, or make a branch PR-ready.