pm-claude-skills-mcp Server

Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.

Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.

Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.

Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.

Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.

Plan a trip that actually works with a disability or access need — confirm real accessibility (not just 'accessible' labels), book the assistance in advance, plan for equipment and medication, and build in the contingencies for when access breaks down. Use when someone says 'plan an accessible trip', 'travelling with a wheelchair/disability', 'book assistance for my flight', or 'will this hotel actually work for me'. Produces an access-verified itinerary, an assistance-booking checklist, an equipment/medication plan, and contingency scripts. Verify specifics with providers.

Request a reasonable accommodation at work or in education — frame it around the barrier and the adjustment (not your diagnosis), cite the right process, and navigate the back-and-forth constructively. Use when someone says 'I need a workplace accommodation', 'request reasonable adjustments', 'ADA/Equality Act accommodation', or 'how do I ask for accommodations for my disability/condition'. Produces the request letter, a barriers-and-adjustments map, disclosure guidance, and a plan for the interactive process. Not legal advice — routes to the formal process and to advocacy where needed.

Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.

Get back into a locked or hacked account the right way — the official recovery routes, what proof you'll need, and how to re-secure it so it doesn't happen again. Use when asked I'm locked out of my account, my account got hacked, help me recover my [email/social/bank] account, or I lost access to 2FA. Produces the official recovery path for the account type, the identity proof to prepare, a re-securing checklist for after you're back in, and warnings about fake 'recovery' services and support scams.

Simulate the acquirer's diligence team hunting for reasons to cut your price — their internal red-flags memo with a price-chip estimate per finding. Use when asked to red-team my company before a sale, how will an acquirer attack our valuation, pre-diligence audit, or what will DD find. Produces the acquirer's internal memo (revenue quality, key-person, tech debt, concentration, legal) and a debrief on which flags are fixable before a process.

Turn a skill's recommendations into real, executed actions — open the tickets, file the issues, post the updates — safely: dry-run preview, risk-classified, approval-gated, then recorded back to the brain. Use when asked to act on a plan, file tickets from a checklist, create issues from a PRD, execute the recommended next steps, or wire a skill's output into GitHub/Linear/Slack. Produces a dry-run actions plan with per-action risk, executes only after approval via the connected action MCP, and logs what was done. Nothing acts silently.

Write platform-native paid ad copy with multiple angles to test. Use when asked to write ad copy, Google/Facebook/LinkedIn/Instagram ads, PPC headlines, or paid social creative copy. Produces ready-to-ship variants per platform (headlines, primary text, descriptions, CTAs) across distinct angles, sized to each platform's limits, with a note on what each variant tests.

Optimize an article for Answer Engine Optimization (AEO) so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines. Produces an AEO-optimised rewrite with question headings, 50–80 word answer capsules, a paragraph-length audit, and flagged trust signals.

Work through the first hours and days after a disaster — a fire, flood, storm, or evacuation — in the right order: safety and people first, then documenting for insurance and aid, then the immediate recovery steps, without missing the things that cost money or health later. Use when someone says 'my house flooded/burned', 'what do I do after the disaster', 'we just evacuated, now what', or 'the storm damaged everything'. Produces a triaged action plan (safety → document → claim → recover), the do-not-miss list, and where to get help. Not legal advice; routes to emergency services and official aid.

Enforce the simplest meeting rule that works — no agenda, no meeting — with the three-line agenda format (purpose, decisions sought, pre-reads), the 24-hour rule, and the graceful cancel scripts. Use when asked write an agenda for this meeting, should this meeting happen, our meetings have no agendas, or cancel this meeting politely. Produces the three-line agenda, the happen-or-cancel verdict, the cancel/convert scripts, and the team norm rollout.

Review an LLM agent design and find where it will be unreliable, expensive, or unsafe. Use when asked to review an agent architecture, critique a multi-step/tool-using agent, debug an agent that loops or goes off-task, or harden an agent before launch. Produces a structured review — task fit, control flow, tools, memory/context, failure handling, cost, and safety — with prioritised findings and fixes.

Redesign seat-based pricing for the agent era — when one human runs ten agents, per-seat models collapse. Use when agents are eroding seat counts, when asked to migrate to usage- or outcome-based pricing, to price an agent/API tier, or to defend revenue as customers automate their own usage. Produces a pricing migration plan: the new value metric, fences, agent-tier design, cannibalisation math, and a phased migration for existing customers. For general pricing and packaging strategy use pricing-strategy.

Hire an AI agent the way you'd hire an employee — a role spec with success criteria, a structured work-sample interview run on your real tasks, reference checks (what do actual users report), probation KPIs, and termination criteria written before day one. Use when choosing between AI agents/tools/copilots for a job, formalizing an AI pilot, or 'which agent should we use for X'. Produces the role spec, interview pack with scoring rubric, a decision record, and a probation plan.

Run a blameless postmortem for an incident caused by an AI agent or LLM feature — hallucinated facts shipped to users, runaway tool use, prompt injection, cost blowouts, or wrong actions taken autonomously. Use when asked to write up an AI incident, analyse why an agent did something wrong, or produce corrective actions after an LLM failure. Produces a structured postmortem with trace reconstruction, a root-cause layer analysis, and corrective actions including a permanent regression case. For non-AI production incidents use incident-postmortem.

Specify the tracing, metrics, and alerting for an AI agent or LLM feature in production. Use when asked what to log for an LLM app, design agent tracing or spans, define quality and cost monitors, or answer 'how do we know if the agent is misbehaving?'. Produces an observability spec with a trace schema, metric definitions with owners and alert thresholds, sampling and retention policy, and a privacy note for logged content.

Audit whether AI agents can actually use your product — docs, APIs, onboarding, errors, and discoverability, evaluated from a non-human user's perspective. Use when asked if a product is agent-ready, to audit a site or API for AI usability, to prepare for agentic traffic, or when agents keep failing against your product. Produces a scored readiness report with per-surface findings and a prioritised fix list. For optimising a single article for AI citation use aeo-optimizer; for designing the MCP server itself use mcp-server-spec.

Offboard an AI agent the way you'd offboard an employee — inventory what it knew and touched, export then purge its memory, revoke every credential and access grant, and write the handover for its successor (human or agent). Use when decommissioning an agent or bot, switching agent vendors, ending an AI pilot, or when someone asks 'what did this thing have access to?'. Produces a severance checklist, an access-revocation table, a memory disposition record, and a successor handover.

Specify an autonomous or tool-using AI agent before building it. Use when asked to design an AI agent, define an agent's tools and guardrails, scope what an agent is allowed to do, or write an agent spec/PRD. Produces an agent spec — goal & scope, tools with permissions, the control loop, guardrails & approval gates, memory, escalation/handoff, evaluation, and failure handling.

Prepare the conversations with aging parents that everyone postpones — the driving talk, the money talk, the care-options talk, the moving talk — each with an opener that doesn't ambush, a dignity-first script, rehearsal against realistic resistance, and the fallback when it goes badly. Use when someone says 'I need to talk to my dad about driving', 'my mum won't discuss her finances', 'we need to talk about care', or is dreading a visit for exactly this reason. Produces the conversation plan, a rehearsal, and the small-steps fallback. A preparation tool, not family therapy — and it says so when the situation needs more.

Assess whether and how someone can safely stay in their own home as they age — the home hazards, the support gaps, and the modifications and services that make it work. Use when asked can my parent stay in their home safely, aging in place assessment, is it safe for them to live alone, or what do we need for them to stay home. Produces a room-by-room safety read (fall hazards, accessibility), an honest look at the daily-living and support gaps, the modifications and services that could close them, warning signs that home may no longer be safe, and how to raise it respectfully — helping a family make a clear-eyed, dignity-preserving decision. Not medical advice.

Run a club, PTA, or association AGM that finishes on time and holds up later — the notice and agenda done right, a quorum plan, minutes that capture decisions not conversations, elections without awkwardness, and the follow-up that makes decisions real. Use when a volunteer says 'I have to run the AGM', 'what goes in the agenda', 'nobody comes to our meetings', or 'our elections are a mess'. Produces the notice, agenda, chair's script, minutes template, and quorum rescue plan.

Review AI-authored code for its characteristic failure modes — plausible-but-wrong logic, hallucinated APIs, over-engineering, dead scaffolding, and silent security shortcuts. Use when reviewing an AI-generated or heavily AI-assisted PR, when AI-written code keeps shipping subtle bugs, or when setting review standards for a team using coding agents. Produces a focused review with AI-specific findings, verification steps per risk class, and a team checklist for AI-authored changes. For general PR review use code-review-checklist — this skill covers what that one assumes a human wouldn't do.

Audit a content library, docs site, or blog for AI-generated filler that's eroding trust and search performance — and triage what to fix, rewrite, or delete. Use when asked to find slop in a content library, audit AI-written content quality, explain why content engagement or rankings dropped after scaling with AI, or set a quality bar for AI-assisted publishing. Produces an audited inventory with per-piece verdicts, the detection signals used, a triage plan, and a publishing quality gate that prevents recurrence. For a single article's AI-citability use aeo-optimizer; for the strategy itself use content-calendar or seo-content-brief.

Decide when and how your product and communications must (or should) label AI-generated content, and write the disclosure policy — surface-by-surface rules, exact label wording, and the review trigger for regulations like the EU AI Act's transparency obligations. Use when asked 'do we have to label AI content', 'write our AI disclosure policy', 'are we covered for the AI Act', or when marketing/support/product start shipping AI-generated output. Produces a disclosure policy with a per-surface matrix and ready-to-use label copy. Not legal advice.

Conduct a structured ethical review of an AI or ML feature, model, or product. Use when preparing to deploy an AI system, assessing algorithmic risk, auditing a model for bias, or producing a responsible AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with a risk tier score, pre-deployment checklist, and prioritised mitigations.

Design an evaluation plan for an LLM or AI feature before shipping it. Use when asked how to evaluate a prompt/model/agent, set up an eval harness, define quality metrics for an AI feature, or build a regression gate. Produces an eval plan — task definition, datasets, metrics & rubrics, baselines, automated + human evals, a pass bar, and a regression gate.

Write a PRD for an AI-powered feature, covering the things normal PRDs miss. Use when asked to spec an AI/LLM feature, write a PRD for a feature that uses a model, or plan an AI capability (assistant, summarizer, generator, classifier). Produces an AI feature PRD — problem & UX of uncertainty, model approach, eval criteria, guardrails, fallback behaviour, the data flywheel, and cost/latency budget.

Structure AI and ML product decisions with the rigour of any product decision. Use when building AI-powered features, evaluating LLM integrations, designing AI products, or assessing AI readiness. Produces a complete AI product canvas covering problem definition, model approach, data requirements, evaluation framework, UX design, responsible AI checklist, and launch monitoring plan.

Audit whether the organisation's AI spend actually paid — measured against baselines, not vendor math or vibes. Use when a CFO asks what the AI tools returned, when renewing AI contracts, when consolidating overlapping AI subscriptions, or to build the measurement plan before the next spend. Produces an ROI audit with per-tool verdicts (keep/consolidate/cut), the honest-measurement method behind each number, and a baseline plan for whatever can't be scored yet. To forecast ROI before an investment use roi-estimator; this skill measures what already happened.

Write an AI usage policy people can actually follow — approved tools, data rules, disclosure duties, and review obligations, in one page instead of legal fog. Use when asked for a company AI policy, acceptable-use rules for ChatGPT/Claude/Copilot at work, guidance on what data may go into AI tools, or to fix a policy nobody reads. Produces a one-page usable policy plus the decision log behind it. Not a substitute for legal advice; pairs with compliance-checklist for regulatory mapping and ai-ethics-review for system-level assessments.

Make an AI agent or automation reliable enough to trust — the tests, checks, and guardrails that catch its failures before they reach anything real. Use when asked how do I test my AI agent, make my automation reliable, my agent works sometimes, or how do I trust an AI workflow in production. Produces a map of where the agent can fail (bad input, hallucination, wrong tool call, edge cases, silent errors), the checks that catch each (validation, evals on real cases, human-in-the-loop gates, monitoring), a right-sized reliability plan scaled to the stakes, and a rollout that earns trust incrementally — so an agent that works in a demo becomes one that works in reality. For builders putting AI agents into real workflows.

Evaluate performance fairly when output is AI-assisted — what still measures the human, what now measures the tooling, and how to run the review conversation. Use when reviewing someone whose work is heavily AI-assisted, when output volume stopped meaning anything, when calibrating a team with uneven AI adoption, or when writing review criteria for the AI era. Produces review guidance: a what-measures-whom analysis, rewritten criteria, calibration rules for mixed-adoption teams, and conversation scripts. For the general review document use performance-review; for redesigning the role itself use role-redesign-for-ai.

Build the context an AI needs to do a task well — the background, constraints, examples, and format it can't guess — so you get a great result on the first try instead of a generic one you have to keep correcting. Use when asked why does AI give me generic answers, how do I give AI better context, my AI results are mediocre, or how do I get it right the first time. Produces the specific context this task needs (who/what/constraints/examples/format), a reusable primer you can paste ahead of the request, the difference between a starved prompt and a well-briefed one, and what to leave out — turning vague back-and-forth into a strong first result.

Check AI output before you trust or use it — where it's likely wrong, what to verify, and how to catch confident-sounding errors. Use when asked can I trust this AI answer, how do I verify what AI told me, fact-check this AI output, or is this AI response reliable. Produces a risk read on the specific output (the claims most likely to be wrong or made up), the parts that need independent verification vs the parts that are low-risk, how to actually verify each, the tells of AI hallucination and overconfidence, and a habit for building verification into your AI use — because AI is confidently wrong often enough that unchecked trust is a real risk.

Figure out which AI tool actually fits the task in front of you — chatbot, coding assistant, image model, agent, or none — instead of forcing one tool onto everything. Use when asked which AI tool should I use for, what's the best AI for, do I even need AI for this, or should I use ChatGPT or something else. Produces a match between your task and the right kind of AI tool (with why), the trade-offs that matter for your case, when the answer is a non-AI tool or plain human effort, and how to try it cheaply before committing — so you pick by fit, not by hype or habit.

Design an AI-assisted workflow for a recurring task — which steps to hand to AI, which to keep human, and how they connect — so you get leverage without losing quality or control. Use when asked how do I use AI for [process], automate this with AI, design an AI workflow, or where does AI fit in my process. Produces a map of the task's steps split into AI-does / human-does / human-checks, the right tool/prompt for each AI step, the hand-offs and review points, the failure modes to guard against, and a start-small rollout — turning a manual process into a reliable AI-assisted one that keeps you in control.

Check live air quality anywhere with zero API keys — Open-Meteo's air-quality API via curl, decoded from raw PM2.5 and AQI numbers into what they mean for going outside. Use when asked what's the air quality, is it safe to run outside, AQI in my city, or pollution levels right now. Produces the current AQI and pollutant levels, the plain-language health read with the standard bands, and the rerunnable command.

Build an all-hands that lands with everyone from intern to VP — the mixed-altitude structure (the story for all, the numbers for some), the wins-with-names section done right, the hard-news slide handled straight, and the Q&A design that gets real questions. Use when asked build the all-hands deck, make the monthly town hall not boring, how do we share the numbers with everyone, or announce this change at all-hands. Produces the segment structure, the altitude-mixed content rules, the hard-news handling, and the Q&A mechanics.

Re-pitch one piece of content for four audiences — the board, the engineers, a customer, a new hire — with a delta table showing what changed between altitudes and why. Use when asked to rewrite this for execs, explain this to the team, make this customer-facing, or say this four ways. Produces the four versions plus the delta table of what was cut, added, and reframed per altitude.

Structure vague opportunities and unclear briefs into actionable one-page problem statements. Use when asked to clarify a vague brief, frame an undefined problem, make sense of an unclear opportunity, or when the user says 'we need to figure out what to do about X' or 'I've been asked to look into Y'. Produces a structured problem brief with reframed questions, scoped boundaries, and a minimum viable research plan.

Prepare for an industry analyst briefing (Gartner, Forrester, IDC and similar). Use when asked to prep an analyst briefing, write an AR briefing document, build talking points for an analyst call, or prepare a Magic Quadrant / Wave submission narrative. Produces a briefing kit — objective, company/product narrative, differentiation, proof points, the demo storyline, anticipated questions, and follow-up commitments.

Write a short, punchy announcement designed to be shared as an image or social card. Use when asked to announce a launch, milestone, feature, hire, funding, or win — something to post on LinkedIn/X/Slack. Produces a tight, visually-structured announcement (headline, one-liner, 2-3 proof points, CTA) that looks great exported as a PNG card from the playground.

Write clear, developer-facing API documentation. Use when asked to document an API endpoint, write API reference docs, create a developer guide, or turn a raw spec/Postman collection into documentation. Produces endpoint documentation with descriptions, parameters, request/response examples, and error codes.

Publish 'how to work with me' as a literal API spec — endpoints (what to ask me for and what you'll get back), rate limits (meeting and interrupt tolerance), error codes (what happens when you surprise me Friday 5pm), auth (how to earn trust), and a changelog. Use when onboarding to a new team, when a new manager or report arrives, for a team working-styles session, or 'write my README/user manual'. Produces a personal API spec that's genuinely funny and secretly the best onboarding doc on the team.

Plan tests for an API endpoint or service — functional, negative, and contract. Use when asked to test an API, write API test cases, plan REST/GraphQL endpoint testing, or validate an API contract. Produces an API test plan — per-endpoint cases (status codes, schema, auth, validation, errors), boundary/negative cases, contract checks, and non-functional notes — so the API is verified beyond the happy 200.

Write an API versioning strategy document for a service or API platform. Use when asked to define versioning policy, plan API deprecation, classify breaking changes, or document version lifecycle. Produces a complete versioning strategy with breaking-change classification table, deprecation timeline, migration guide template, and client communication template.

Write a sincere, effective apology to a customer, group, or the public. Use when asked to write an apology, say sorry to a customer or community, make amends after a mistake, or respond to a complaint with an apology. Produces a genuine apology — acknowledgement, taking responsibility, empathy for the impact, the concrete fix and prevention, and an offer to make it right — in the right tone, without excuses or non-apologies.

Cut through the model soup to buy the right appliance — the features that actually matter for you, the ones that are marketing, and when to buy. Use when asked which [fridge/washer/dishwasher] should I buy, help me choose an appliance, what features do I need, or is this appliance worth it. Produces a needs-based feature shortlist (must-have vs nice-to-have vs marketing fluff), fit and capacity checks, reliability and running-cost considerations, warranty/extended-warranty guidance, and timing tips — flagging to verify current models, prices, and specs before buying.

Plan an apprentice's or new laborer's first week so they're useful by Friday and safe from hour one — day-by-day teaching order, the safety non-negotiables stated before anything else, what they're allowed to touch unsupervised, and the check-out conversation that decides week two. Use when a tradesperson says 'my apprentice starts Monday', 'how do I train the new guy', or 'the apprentice is useless and I don't have time to teach'. Produces a first-week plan, a can/can't-touch list, and the Friday review script.

Create an Architecture Decision Record (ADR) for any technical decision. Use when asked to document a technical decision, write an ADR, record an architecture choice, or capture why a technology or approach was selected. Produces a structured ADR with context, decision, consequences, and tradeoffs.

Diagram a system or technical architecture — services, data stores, and how they connect. Use when asked to draw an architecture, show how components fit together, map a system/data flow, or visualize services and dependencies. Produces a ready-to-render Mermaid diagram with grouped subgraphs (renders live, exportable as PNG/SVG) plus a component legend and notes.

Design the archive layer that keeps current workspaces lean without losing history — what moves, when, to where, findable-by-search, with the project-close ritual that makes archiving automatic instead of aspirational. Use when asked set up an archiving system, our workspace is drowning in old projects, when should things get archived, or make history findable without cluttering today. Produces the archive triggers, the destination structure, the findability rules, and the close-out ritual.

Set up the essentials in the right order after moving to a new country — the ID/registration, bank account, phone, address, and social/tax number that unlock each other — so you don't get stuck in the chicken-and-egg loops that trap newcomers. Use when someone says 'I just moved to a new country', 'what do I do first after arriving', 'set up my life in [country]', or 'I can't open a bank account without an address but can't rent without a bank'. Produces a sequenced arrival checklist with dependencies and the official offices for each. Routes to official sources; rules are local.

Build and deliver a raise request that actually works — the evidence, the number, the timing, and the exact words — instead of hoping it gets noticed. Use when asked how do I ask for a raise, I deserve more money, prepare me to ask for a raise, or negotiate a pay increase at my job. Produces a value case built on your actual contributions and market rate, a specific target number with justification, the right timing and person, a script for the conversation, and responses to the likely pushbacks — turning 'I want more' into a business case your manager can say yes to.

Surface the hidden assumptions a plan or belief rests on, then test what happens when each one is wrong. Use when asked what am I assuming here, check my assumptions, what if I'm wrong about, or stress-test my thinking. Produces the unstated assumptions your conclusion depends on (ranked by how load-bearing they are), a flip of each to see which one breaking would change everything, and the cheapest way to check the riskiest ones — because the assumption you didn't know you were making is what sinks plans.

Extract every hidden assumption from a plan or document and put a price on each one — what it costs if wrong, what it costs to test. Use before committing to anything whose author says 'obviously' or whose spreadsheet has hardcoded cells: the bounty hunt makes the invisible load-bearing beliefs explicit and tells you which three to test this week. Produces the assumption ledger (priced and ranked), the cheapest test for each dangerous one, and the document's honest confidence statement.

Extract and risk-rate hidden assumptions in a product brief or PRD. Use when asked to review a product brief for assumptions, audit a PRD for risks, find hidden assumptions, validate product plans, or run an assumption analysis. Produces a prioritised assumption map with confidence and impact scores, recommended validation methods, and critical assumption flags.

Run a decision asynchronously — the memo, the silent-read window, the comment protocol, and the deadline that makes it land without a meeting. Use when asked to decide something async, replace a decision meeting with a document, run an Amazon-style written decision process, or when a decision keeps stalling in comment threads. Produces the decision memo plus the process wrapper: reader roles, response windows, comment-resolution rules, and the tie-breaker. For the document structure alone use decision-memo; this skill runs the process around it.

Convert a meeting into async work that actually decides — the doc-plus-deadline format that replaces the room, the comment-window rules, the decision-closure step that async usually fumbles, and the honest test for what still needs synchronous. Use when asked can this meeting be async, replace our status meeting with a doc, run this decision without a call, or async isn't working for us. Produces the conversion design, the async artifact format, the closure protocol, and the still-needs-a-room list.

Compile the team's REAL updates into one async standup — pull what people posted in Slack (and moved in Notion/Linear), not a template for running standups. Use when asked to compile today's standup, pull the team's updates into one post, what did the team ship, or run async standup in Cowork. Reads a Slack channel and (optionally) the tracker via connectors, groups updates by person into shipped / in-progress / blocked, surfaces the blockers needing attention, and produces a standup-digest artifact ready to post back.

Write status updates people actually read — the traffic-light-plus-narrative format (state first, story second), the blockers-are-asks rule, and the skimmable structure that respects a reader with thirty seconds. Use when asked write my weekly update, format our team's status posts, nobody reads my updates, or what goes in a good async check-in. Produces the update format with a filled example, the blockers-as-asks discipline, and the reader-time contract.

Get your attention back with a 30-day protocol that assumes you'll break it — a screen-time ledger without moralizing, friction engineering (what to delete, grayscale, where the phone sleeps), planned relapses, and honest replacement activities for the boredom that shows up on day 3. Use when someone says 'my screen time is 7 hours', 'I want a dumbphone', 'digital detox', 'I can't read books anymore', or 'my attention span is gone'. Produces the ledger, a personal friction plan, and the 30-day protocol with expected failure points.

Decode an auto repair estimate — what each line actually is, which items are urgent vs upsell, and the questions that separate a fair shop from a fishing expedition. Use when someone asks 'is this repair quote fair', 'decode my mechanic's estimate', 'do I really need all this', or 'is the shop ripping me off'. Produces a line-by-line decode with urgency triage, parts/labor sanity checks, ranked red flags, and the exact questions to ask the shop before authorizing.

Decide which of your recurring rituals to put on autopilot — and which to keep manual. Use when asked what to automate, how to set up recurring AI runs, which reports or briefings could run on a schedule, or to design an automation charter for a team. Produces a ritual inventory with automate/assist/keep-manual calls, guardrails per ritual, and a rollout order.

Draft the hard personal message you keep putting off — chasing money a friend owes, backing out of plans, checking in after a fight, following up on an unanswered text. Use when asked to help send an awkward text, how to say something uncomfortable to a friend, word a difficult personal message, or bring up something touchy. Produces a couple of calibrated options, the one line to open with, and the send/wait/call judgement call — warm, honest, and not a doormat.

Set up a backup system that actually protects your photos, files, and devices — built on the 3-2-1 rule and, crucially, tested so it works when you need it. Use when asked how to back up my data, set up backups, protect my photos/files, or what's a good backup strategy. Produces a 3-2-1 plan tailored to your devices and data, specific what-to-back-up priorities, an automation setup so it happens without you, a restore-test step, and protection against the failure that ruins backups (ransomware/sync-deletes reaching the backup).

Write the band agreement before the money or the breakup arrives — who owns the songs, how money splits (writing vs performing distinguished), who owns the name, what happens when someone quits, and the decision rules for offers — decided while everyone still shares a van. Use when a band asks 'how should we split money', 'who owns our songs', 'our drummer quit, what happens', or is about to record/release/sign anything. Produces a plain-language band agreement and the meeting script to agree it. Not legal advice — it's the conversation that makes the lawyer cheap later.

Get a bank fee waived or refunded — overdraft, late, maintenance, ATM, or foreign-transaction — with the ask written and the leverage that works. Use when asked to get a bank fee refunded, waive my overdraft fee, the bank charged me a fee, or how to get charges reversed. Produces a read on which fees are commonly reversible, the script to request a refund (in person, chat, or call), the loyalty/first-time/error leverage to use, and how to prevent the fee recurring — plus when to escalate or switch banks.

Think clearly about whether bankruptcy is the right move, or whether another path fits better — without shame and without a sales pitch. Use when asked should I file for bankruptcy, is bankruptcy my best option, alternatives to bankruptcy, or what happens if I file. Produces an honest read on whether your situation is the kind bankruptcy actually helps, the main types and what each does (and doesn't) discharge, the real trade-offs (what you keep, the credit impact and its recovery, what's not dischargeable), the alternatives to weigh first (negotiation, debt management, doing nothing on time-barred debt), and a strong push to consult a bankruptcy attorney — so the decision is informed, not driven by fear or a debt-relief ad. Not legal advice; centers a real attorney consult.

Build a tiered classroom behavior intervention plan (BIP) for a K-12 student, grounded in the function of the behavior. Use when asked to plan a behavior intervention, address a disruptive or off-task pattern, write a BIP, or set up positive behavior supports. Produces a function hypothesis, prevention/antecedent strategies, teaching of a replacement behavior, a response plan for when it happens, and a simple data-tracking method — positive and skill-building, not punitive.

Audit the beneficiary designations that quietly override wills — the account-by-account sweep, the life-event triggers that make them stale, and the coordination check against actual intentions. Use when asked check my beneficiaries, does my 401k go to my ex, do beneficiary forms beat a will, or what should I update after marriage/divorce/a birth. Produces the account sweep list, the stale-designation red flags, the intent-vs-paperwork comparison table, and the update checklist with the verify-in-writing step.

Decode an employment benefits package into what it's actually worth and where the fine print bites. Use when someone asks 'is this offer good', 'decode my benefits package', 'what does my equity actually mean', or 'what should I ask HR before signing'. Produces a benefit-by-benefit decode with real dollar values, ranked red flags (vesting cliffs, clawbacks, 'discretionary' bonuses, unlimited-PTO economics), and the questions to ask HR before signing.

Check whether a raise, more hours, or a new job could cost you more in lost benefits than you gain — the 'benefits cliff' — before you accept it. Use when asked will a raise hurt my benefits, benefits cliff, if I make more will I lose my food stamps or medicaid, or should I take more hours. Produces a plain map of which benefits phase out at what income (and which cut off suddenly vs. taper), a rough read on whether a specific income change helps or hurts net, the ones with hard cliffs to watch (childcare, Medicaid, housing), the moves that soften a cliff, and where to get a real benefits screening — so you make an income decision with eyes open, not a nasty surprise. Not financial/benefits advice; points to a benefits counselor.

Audit a week the way Arnold Bennett's 'How to Live on 24 Hours a Day' (1908) prescribes — time as the one income that cannot be increased, the day-within-the-day, and starting with 90 minutes, not a life overhaul. Use when someone says 'I have no time', 'work eats everything', 'I want to learn X but can't fit it', or asks for a time audit or evening routine. Produces a time ledger, one reclaimed 'inner day' block, and Bennett's own warnings about overreach.

Analyse a construction bid or tender package for scope gaps, risk-shifting exclusions, unit-rate red flags, and front-loading in the schedule of values. Use when asked to review a bid, level bids, check a tender for gaps, compare sub quotes, or vet a schedule of values before award. Produces a structured bid review with a gap register, exclusion risk table, pricing red flags, and an award recommendation with pre-award clarifications.

Decide when to buy a big-ticket item to get the best price — the sales cycles, model-refresh timing, and 'buy now vs wait' math for the specific thing you want. Use when asked when's the best time to buy [item], should I wait for a sale, is now a good time to buy, or when do [products] go on sale. Produces the typical discount calendar for that category, whether a new model/version is due (and if the current one will drop), a buy-now-vs-wait recommendation for your timeline, and price-tracking tactics — flagging that timing is a guide, not a guarantee.

Get started birding from where you are — what you're likely to see, how to tell confusing species apart, and a simple life-list to track sightings. Use when asked to start birdwatching, what bird did I see, help me identify a bird, or set up a birding log. Produces a likely-species list for your area and season, ID prompts (the field marks and sounds that separate look-alikes), a beginner gear-and-timing note, and a lightweight life-list format — pointing you to a live ID app to confirm any specific sighting.

Run the worst-case drill before an agent goes autonomous — the 'if this agent were fully hijacked right now, what's the damage' walk-through, the containment controls (caps, kill-switch, reversibility, isolation), and the recovery plan. Use when asked what's the worst my agent could do, run a blast-radius assessment, prepare for an agent going rogue, or am I ready to let this run unattended. Produces the worst-case walk-through, the containment controls, the reversibility audit, and the incident-recovery runbook.

Plan the merging of two families thoughtfully — roles, rules, routines, and relationships — so a blended household starts on the right foot instead of a collision. Use when asked to help blend our families, moving in with my partner and their kids, step-parenting help, or how to merge two households. Produces a read on the situation and its sensitivities, an approach to step-parent roles and discipline, a plan to align house rules and routines across homes, ways to build relationships at each child's pace, and how to handle exes and loyalty binds — realistic, not idealized. Not therapy.

Build the storyline and slide structure for a board presentation. Use when asked to create a board deck, board presentation narrative, board meeting slides, or quarterly board update. Produces a complete slide-by-slide structure with narrative beats, talking points, and slide content guidance.

Take a board game idea from 'wouldn't it be cool if' to a playtestable prototype — core loop, tension source, components you can make tonight, balance starting-points, and a real playtest protocol with kill criteria. Use when someone says 'I have a board game idea', 'design a game about X', 'my game drags in the midgame', or 'how do I playtest this'. Produces a design one-pager, a print-and-play prototype spec, and a 3-session playtest plan.

Plan a board game night that actually lands — the right games for your group size, mix, and time, in a running order that keeps energy up. Use when asked to plan a game night, what board game should we play, games for [N] people, or what to play with a mixed group. Produces game picks matched to player count and experience, a warm-up-to-main running order, teach-time and play-time estimates, and swaps for the non-gamers or the one player who hates losing.

Write formal board meeting minutes from an agenda, notes, transcript, or discussion summary. Use when asked to draft board minutes, governance minutes, meeting minutes for a board, or a formal record of decisions and actions. Produces structured board minutes with attendees, agenda items, resolutions, decisions, action register, and approval-ready wording.

Write a board pre-read that's sent before the meeting so the meeting is about decisions, not status. Use when asked to prepare a board pre-read, a board update/package, or pre-meeting materials for a board. Produces a board pre-read — a TL;DR, the metrics dashboard vs. plan, what's working / what's not, the decisions and asks for the board, and risks — designed to be read in advance.

Set up and run a body-doubling session — using another person's presence (in the room, on a call, or a chat check-in) to start and stay on the task your ADHD brain keeps bouncing off. Use when someone says 'I can't start this task', 'body double with me', 'I only work when someone's around', or has ADHD/executive-dysfunction and a task that won't begin. Produces a session plan, the exact ask to send a body-double partner, and a solo fallback for when no one's available.

Act as a body-double for a work session — a present, low-pressure companion that keeps you accountable and moving through the task without doing it for you. Use when asked be my body double, keep me company while I work, help me focus on this task, or I work better with someone there. Produces a session structure (goal, time block, check-in cadence), gentle presence and momentum nudges at intervals, distraction rescue when you drift, and an end-of-session acknowledgment — recreating the focus that comes from someone just being there.

Review a bill of materials for cost, risk, and supply exposure — cost rollup, top-10 cost drivers, single-source and EOL risk, MOQ vs forecast mismatch, cost-down candidates, and tariff/logistics sensitivity. Use when asked to review a BOM, find cost-down opportunities, check component sourcing risk, or sanity-check BOM cost against target. Produces a structured BOM review with a cost driver Pareto, risk flags per line, and a prioritised cost-down list.

Set up a chart of accounts and rules for categorizing transactions. Use when asked how to categorize expenses/transactions, set up a chart of accounts, organize bookkeeping, or sort bank transactions into the right buckets. Produces a practical chart of accounts for the business, categorization rules with examples and edge cases, and a clean-books routine — so the books are consistent and ready for an accountant. Not tax/accounting advice.

Build boolean and X-ray search strings to source candidates. Use when asked to build a boolean search, source candidates on LinkedIn/Google, write an X-ray search, or find people with specific skills. Produces ready-to-paste boolean strings (with synonyms, must-haves, and exclusions), X-ray variants for LinkedIn/GitHub, and a refinement plan to widen or narrow the result set.

Set a boundary with someone — a friend, family member, coworker, or partner — clearly and kindly, with the actual words and a plan for the pushback. Use when asked how do I set a boundary with, I need to say no to, someone keeps overstepping, or help me set limits with. Produces a read on the boundary you actually need, a warm-but-firm script to state it (without over-explaining or apologizing it away), how to hold it when they push back or guilt-trip, and what to do if they don't respect it — because a boundary you can't state and hold isn't a boundary.

Keep a running brag document of your accomplishments so reviews and promo cases write themselves. Use when asked to start or update a brag doc, log a win, track accomplishments, or prep evidence for a review/promotion. Produces a structured, dated accomplishment log — impact-first entries with metrics, scope, and the evidence link — grouped so it drops straight into a self-review or promo packet.

Run a real brainstorm — divergent generation without judgment, then convergent selection with explicit criteria — instead of listing ten obvious ideas and calling it creativity. Use when asked to brainstorm, generate ideas or options, explore a solution space, or name something. Produces a genuinely wide option set (including the weird tail), then a shortlist selected against named criteria with the rejects preserved.

Extract a brand's visual and verbal identity into an applicable guideline kit — tokens, voice rules, and do/don't pairs — then apply it consistently to any artifact. Use when asked to apply brand guidelines to a document/deck/page, to extract a brand kit from existing materials or a website, to keep AI-produced artifacts on-brand, or to write lightweight brand guidelines for a startup. Produces a compact brand kit (visual tokens + voice rules + application examples) and/or an artifact restyled to it. For a creator's personal voice use creator-brand-kit; for building new UI systems use frontend-design.

Respond to a brand or executive impersonation incident — deepfaked executives, cloned support lines, fake apps, spoofed domains, or AI-generated scam content wearing your name. Use when a deepfake of a leader is circulating, customers report a fake version of your product or support channel, or to prepare the impersonation playbook before it happens. Produces an incident response: verification protocol, takedown sequencing by platform, customer and public communications, and the hardening plan. For general crisis comms use press-release/pm-crisis skills; for security incidents inside your systems use security-incident-response.

Interview the user with sharp, one-at-a-time questions to turn a vague request into a tight, complete brief any other skill can run on. Use when a request is fuzzy, under-specified, or 'help me think this through', or before running a skill that needs inputs the user hasn't given. Produces a structured brief (goal, audience, constraints, success criteria) and hands off to the right skill — by interrogating, not guessing.

Turn a folder of accumulated documents into one decision-ready brief — the skim-map pass over the pile, the extraction against the brief's actual questions, the conflict reconciliation when documents disagree, and the provenance trail back to sources. Use when asked read all this and tell me what matters, synthesize this folder for the new lead, turn these 20 docs into a brief, or what does all this material actually say. Produces the pile map, the question-driven extraction, the reconciled brief with per-claim sources, and the didn't-read honesty ledger.

Write a one-page briefing note that gets a busy principal up to speed fast. Use when asked to brief a minister/executive/official, prepare a briefing note or read-ahead, or summarize an issue for a decision or meeting. Produces a tight, single-page note: purpose, background, key facts/considerations, and a recommendation or the decision sought — scannable in two minutes.

Run the pre-flight checklist before an agent drives a browser — the untrusted-web-content threat (every page is attacker-controllable), the credential and session-cookie exposure, the action-confirmation gates for purchases and posts, and the sandboxing that limits the damage. Use when asked let my agent browse safely, is it safe to give the agent computer/browser use, guardrails before the agent uses my browser, or review my browser agent's setup. Produces the sandbox decision, the content-injection defenses, the action gates, and the credential-isolation rules.

Build a realistic personal monthly budget from someone's income and expenses. Use when asked to make a budget, plan monthly spending, allocate income, or get finances under control. Produces a categorized budget (a 50/30/20-style allocation tuned to their reality), a surplus/shortfall number, and concrete next moves. Educational, not regulated financial advice.

Design a budget-vs-actuals tracker that stays alive past February — the category grain that matches real statements, the variance view that answers 'are we okay', the update ritual small enough to survive, and the honest handling of irregular expenses. Use when asked build me a budget spreadsheet, track team spend against budget, why do we always blow the budget invisibly, or design a household/project budget tracker. Produces the tracker structure, the variance logic, the irregulars ledger, and the monthly fifteen-minute ritual.

Produce a structured budget variance analysis from actual vs budget figures. Use when asked to analyse budget variances, explain underspend or overspend, write a variance commentary, or investigate why actuals differ from plan. Produces a categorised variance table with root cause analysis and management commentary.

Diagnose a bug systematically instead of guessing — reproduce, isolate, form hypotheses, and test them to root cause. Use when debugging, chasing a defect, an intermittent failure, or 'why is this happening?'. Produces a structured diagnosis: a reliable repro, the narrowed-down location, ranked hypotheses with how to test each, and the root cause + fix once found.

Write a clear, reproducible bug report that gets fixed fast. Use when asked to write a bug report, file a defect, report an issue, or turn 'it's broken' into an actionable ticket. Produces a structured report — a precise title, steps to reproduce, expected vs. actual, environment, severity/priority, and evidence — so a developer can reproduce and fix it without a back-and-forth.

Triage a raw bug report into something a team can act on — clean repro steps, a defensible severity/priority, environment, likely area/owner, and duplicate check. Use when asked to triage this bug, set severity and priority, is this a P1, or clean up this bug report for the backlog. Produces the normalized repro, a severity and priority with the reasoning (impact × frequency × workaround), the environment/metadata, a suspected component and owner queue, and a duplicate/related-issue check — flagging when info is missing rather than guessing.

Interview you into a durable personal MEMORY.md — your decision rules, patterns, past failures, and preferences — that any AI can read to help you better, with privacy guardrails built in. Use when asked to build my memory file, help my AI remember me, create a MEMORY.md, or set up context about myself. Produces a structured personal-context file drawn out through good questions (how you decide, what you keep repeating, what you don't want to repeat), organized for an AI to use — while explicitly refusing to store sensitive data like credentials, financial, health, or others' personal info.

Build a realistic recovery plan for burnout — address the causes, not just the symptoms — with changes you can actually make at work and outside it. Use when asked to help with burnout, I'm burnt out, how to recover from burnout, or I'm exhausted and dread work. Produces a read on what's driving the burnout (load, control, reward, fairness, values, community), immediate relief steps, the boundary and workload changes that address the root, a recovery timeline with realistic expectations, and a flag that severe or persistent burnout/depression warrants a professional. Not medical advice.

Pressure-test a business or side-hustle idea before you sink money and months into it — find the real demand, the risky assumptions, and the cheapest way to test them. Use when asked to validate my business idea, is this a good business idea, test my side hustle, or should I start this. Produces a read on the core assumptions the idea depends on, who the customer really is and whether the pain is real, the cheapest experiments to test demand before building, a rough viability check (market, competition, economics), and a go/refine/rethink call — honest, not a cheerleader.

Defragment a work calendar through a tool-using agent — find the meeting debt, propose the consolidation, and (approval-gated) execute the moves. Use when asked to defrag my calendar, get me focus time, audit my meetings, or fix my week. Produces the calendar audit (cost per meeting, fragmentation map), a defrag proposal with focus blocks, and an approval-gated execution plan.

Turn interview notes into a structured candidate scorecard and hire recommendation. Use when asked to write an interview scorecard, a candidate evaluation, an interview debrief, or to summarize feedback into a hire/no-hire call. Produces a per-competency assessment with evidence and ratings, an overall recommendation with confidence, and the open questions for the next round — evidence-based, bias-aware, and decision-ready.

Explain a cap table, dilution, SAFEs, option pools, and round mechanics in plain English with the actual math. Use when asked to explain dilution, model a SAFE or priced round, size an option pool, understand a term sheet's economics, or figure out who owns what after a raise. Produces a worked ownership breakdown before/after the round, the dilution math step by step, and the traps founders miss. Not legal or financial advice.

Produce a capacity planning document for a service covering traffic forecasts, resource requirements, and scaling strategy. Use when asked to plan infrastructure capacity, forecast resource needs, model traffic growth, define scaling strategy, or produce a capacity review for a service. Produces a structured capacity plan covering current baseline metrics, growth projections, resource requirements per tier, scaling strategy, cost projections, capacity triggers, and an infrastructure action roadmap.

Allocate a finite budget or headcount across competing initiatives by return and strategic fit. Use when asked to allocate budget, decide where to invest, build a funding/portfolio plan, or make trade-offs across initiatives under a cap. Produces a capital-allocation plan — initiatives scored by expected return × strategic fit per dollar, a funded/unfunded split against the cap, the cut line, and the reasoning.

Decode a car lease offer — the money factor converted to APR, the cap-cost math, mileage and disposition traps, and what to negotiate. Use when asked to decode my car lease, is this lease deal good, what's a money factor, or review this lease before I sign. Produces the real-numbers decode (money factor → APR, total lease cost), the trap list with dollar exposure, and the negotiation points dealers expect to concede.

Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly payment. Use when asked should I lease or buy a car, is it cheaper to keep my old car, what does this car really cost per month, or new vs used total cost. Produces the ranked scenario totals, per-month true cost, the assumption ledger, and the not-modeled list.

Negotiate a car purchase without getting played — know the real target price, handle the dealership tactics, and keep the financing and add-ons from eating your savings. Use when asked to help me negotiate a car, buy a car without getting ripped off, what should I pay for this car, or dealership negotiation tips. Produces a target-price approach (research the out-the-door price), the dealer tactics to expect and counters, guidance on separating price/trade/financing, the add-ons to decline, and a walk-away plan — flagging to verify current pricing and rates.

Sanity-check a greenhouse gas inventory before it goes into a report or gets audited. Use when asked to review a carbon footprint, check a GHG inventory, validate scope 1/2/3 numbers, explain a year-over-year emissions change, or prepare emissions data for assurance. Produces a boundary review, data-quality assessment, emission-factor sensitivity list, YoY bridge, and a fix-before-publishing list.

Run a family meeting to make a big care decision together — so it's a shared, informed decision instead of a fight or one person deciding alone. Use when asked help me run a family meeting about care, we need to decide together about mom's care, my siblings and I disagree about our parent, or facilitate a care decision. Produces an agenda and structure for the meeting, how to prepare (facts, options, everyone's input), ground rules to keep old family dynamics from derailing it, how to include the person being cared for, ways to work through disagreement toward a decision, and clear next steps with owners — turning an emotional, conflict-prone conversation into a productive one. Not legal, medical, or financial advice.

Organize the people and information involved in caring for someone — family, doctors, helpers — so care doesn't fall through the cracks or all land on one person. Use when asked help me coordinate care for, organize caregiving for my parent, set up a care system, or I'm drowning coordinating everyone. Produces a map of who does what (medical, daily, financial, emotional), a shared-information system so everyone's on the same page, a way to divide tasks fairly among family, a communication rhythm, and how to keep the key information (meds, contacts, wishes) in one accessible place — turning caregiving chaos into a coordinated effort.

Map where you are against the next level and build a concrete plan to close the gap. Use when asked to map a career ladder, find the gap to the next level, build a development/growth plan, or figure out what to work on to get promoted. Produces a level-gap map — current vs. target competencies side by side, the specific gaps, and a prioritised 1–2 quarter plan of evidence-generating projects to close them.

Build a realistic plan to change careers — mapping your transferable skills, the real gaps, and a bridge that doesn't require torching your income overnight. Use when asked to help me change careers, career pivot plan, how do I switch to [field], or I want a new career but don't know how. Produces a transferable-skills map, an honest gap analysis to the target role, a staged bridge (skill-building, positioning, side-door entry), a financial-runway reality check, and a narrative that reframes your background as an asset — not a starting-from-zero story.

Organize care for an aging or ill family member across multiple helpers — the shared care map, a fair rotation with backup rules, the information binder, and family-meeting agendas that prevent the one-sibling-does-everything spiral. Use when asked help me coordinate care for my mom, my siblings and I need to split caregiving, organize care for a sick family member, or set up a care schedule. Produces the care map of needs and coverage, the rotation schedule with escalation rules, the binder outline, and the family meeting agenda.

Check whether you're burning out as a caregiver — and get a realistic plan to protect yourself before you can't keep going. Use when asked I'm exhausted from caregiving, am I burning out caring for my parent, caregiver stress help, or I have nothing left to give. Produces an honest read on your burnout signs and how depleted you are, permission and reasons to accept help (which caregivers resist), specific ways to get support and respite, the guilt and identity traps to address, and a realistic self-care plan that fits a caregiver's actual life — because a caregiver who collapses can't care for anyone. Not medical or mental-health treatment.

Write a fundraising case for support that makes donors want to give. Use when asked to write a case for support, a fundraising case statement, a major-gift or campaign case, or the core argument for a donation appeal. Produces a persuasive case — the need, your solution and why you, the impact a gift makes, specific funding opportunities with amounts, and a clear ask — donor-centred, not org-centred.

Write a client case study that sells future work — challenge, approach, results. Use when asked to write a case study, a client success story, a project write-up, or a portfolio case for consulting/agency work. Produces a results-led case study — the client & challenge, your approach, quantified outcomes, a client quote slot, and a takeaway — structured to win the next client. Ready to export as a designed PDF.

Build a short-term (13-week) cash flow forecast to see if you can cover what's due. Use when asked to build a cash flow forecast, a 13-week cash flow, a cash projection, or to plan around a cash crunch. Produces a week-by-week forecast structure — opening cash, expected inflows, scheduled outflows, net movement, and closing/low-point — with the formulas and a worked example, plus the levers if cash goes tight. Not financial advice.

Plan an e-commerce category / collection page that ranks and merchandises well. Use when asked to design a category page, a PLP (product listing page), a collection page, or to improve category SEO and merchandising. Produces a brief — search intent & keywords, intro copy, merchandising/sort logic, filters & facets, internal links, and SEO/technical notes — so the page converts browsers and earns organic traffic.

Draft a firm, professional cease-and-desist letter to stop harassment, defamation, IP misuse, or unwanted contact — clear about what must stop and what happens if it doesn't. Use when asked to write a cease and desist, make someone stop [harassing/using my work/defaming me], or send a formal letter to stop. Produces a structured letter stating the conduct, why it's wrongful, the specific demand and deadline, and the consequence, plus guidance on delivery and records — flagging when the matter needs a real lawyer. Not legal advice.

Create a structured change management plan for any organisational change. Use when asked to write a change management plan, manage a change initiative, plan a system rollout, or lead an organisational transformation. Produces a plan covering stakeholder analysis, impact assessment, communication strategy, and resistance management.

Draft a defensible construction change order with entitlement basis, scope delta, itemised pricing, and schedule impact. Use when asked to write a change order, price extra work, draft a CO or COR/PCO, respond to a directive for changed work, or paper a field change. Produces a complete change order request with contract-clause entitlement, labour/material/equipment/OH&P breakdown, time impact statement, and reservation of rights.

Write changelogs and release notes readers actually benefit from — changes translated to so-whats, grouped by reader impact (breaking first, gifts second, plumbing last), with the upgrade path stated and the marketing kept honest. Use when asked write the release notes, turn this commit list into a changelog, announce this update to users, or why does nobody read our changelogs. Produces the impact-grouped changelog, the so-what translations, the breaking-changes block with migration steps, and the two-audience split when needed.

Write a human changelog from the REAL commit history — read the actual commit range via the GitHub connector, not a template. Use when asked to write the changelog for this release, what changed since the last tag, draft release notes from my commits, or summarise this range for users in Cowork. Reads commits/PRs between two refs via the GitHub connector, groups them into user-facing changes (features / fixes / breaking), translates commit-speak into human benefit, and produces a changelog artifact ready for the release.

Convert a git log, commit list, or release notes into a polished, user-facing changelog. Use when writing release notes, generating a CHANGELOG.md entry, or documenting what changed in a version. Produces a structured changelog section with version header, categorised changes, and migration notes. For an already-curated change list use changelog-writer instead.

Turn a list of changes, commits, or PRs into clean release notes / a changelog entry. Use when asked to write release notes, a changelog, or a version announcement from raw changes. Produces a Keep-a-Changelog-style entry grouped by type (Added/Changed/Fixed/etc.), written for users — surfacing breaking changes and upgrade notes up top. To go straight from a raw git log use changelog-generator instead.

Fix a team's chat sprawl — the channel map with one purpose per channel, the naming scheme that makes purpose findable, the archive pass for the dead and duplicated, and the posting norms (threads, @-discipline, urgency signals) that keep signal findable. Use when asked clean up our Slack/Teams, we have 90 channels and nothing is findable, set channel norms, or where should things get posted. Produces the channel audit and map, the naming scheme, the norms card, and the archive pass.

Win a chargeback dispute — read the reason code, assemble the evidence packet, and write the rebuttal that actually persuades the bank. Use when asked to fight a chargeback, respond to a payment dispute, write a chargeback rebuttal, or contest a customer chargeback. Produces the reason-code decode, the required-evidence checklist for that code, the structured rebuttal letter, and an honest read on whether this one is winnable — so you fight the right disputes and concede the rest. For merchants.

Turn numbers into a chart — bar, line, area, pie, or doughnut. Use when asked to chart or graph data, visualize metrics/trends/breakdowns, or show numbers as a picture instead of a table. Produces a ready-to-render chart spec (renders live in the playground and exports as PNG) plus a one-line read of what the chart shows.

Pick the chart the data and the point actually need — the question-to-chart mapping (comparison, trend, composition, distribution, relationship), the honesty rules (axes, baselines, dual-axis traps), and the one-chart-one-point discipline. Use when asked what chart should I use, make this data visual, why does this chart feel misleading, or fix this graph for the deck. Produces the chart verdict with its reasoning, the honesty checklist applied, and the labeling that lets the chart travel without its author.

Extract pixel-level data from an image of a chart or graph and produce a structured data table. Use when asked to extract data from a chart image, transcribe numbers from a graph, digitise a chart, or turn a screenshot of data into a table. Produces a structured table with extracted values, confidence levels, and a reconstructed chart source. Best used with Claude Opus 4.7 or newer for reliable chart data extraction.

Build a small, coherent opening repertoire that fits your style and level — the few lines actually worth learning, plus the plans and traps behind them. Use when asked what chess opening should I learn, build me a repertoire, help with my openings, or what to play against [opening]. Produces a compact repertoire for White and Black keyed to your rating and style, the main ideas and typical plans (not just moves to memorize), the common traps to know from both sides, and what to study next — kept small enough to actually learn.

Compare childcare options — nursery/daycare, childminder, nanny, family, or a mix — for your family's real needs, budget, and values. Use when asked to compare childcare options, nursery vs nanny, how to choose childcare, or find the right childcare. Produces a needs-and-values profile, a side-by-side of the realistic options on cost/flexibility/socialization/control, the questions to ask and red flags to check on visits, a total-cost read (including subsidies), and a decision that fits your priorities — not a generic ranking.

Produce a structured churn analysis that separates avoidable from unavoidable churn. Use when investigating why customers are leaving, identifying at-risk segments, calculating net revenue retention, or building a retention intervention plan. Produces a churn report with rate calculations, categorised reasons by avoidability, segment breakdown, timing analysis, early warning signals, and prioritised interventions ranked by estimated impact.

Write a CI/CD pipeline playbook for a service or team. Use when asked to document a CI/CD pipeline, write a deployment process, define release gates, document build and test stages, or create a deployment guide. Produces a structured playbook covering pipeline stages, environment definitions, deployment gates, rollback procedures, and on-call responsibilities.

Keep citations honest in business documents — every load-bearing claim sourced, links that actually contain the claim, the as-of dates that keep numbers honest, and the internal-vs-external sourcing rules for decks and memos. Use when asked check the sourcing in this deck, add citations to this doc, our slide says 'studies show' — which studies, or set citation norms for the team. Produces the claim-by-claim audit, the fixes (source found, claim softened, or cut), the citation format for the venue, and the team norm card.

Decode an insurance claim denial letter — what the cited reason actually means, whether it's commonly overturnable, and the appeal letter that answers it point by point. Use when someone asks 'my insurance claim was denied what do I do', 'decode this denial letter', 'can I appeal this denial', or 'write my insurance appeal'. Produces the denial decode with overturn-likelihood framing, the evidence checklist, the point-by-point appeal letter, and the escalation ladder past the insurer.

Triage an incoming insurance claim: check the coverage trigger against policy wording, band severity and complexity, screen for fraud indicators, set a first-pass reserve range, and route with an SLA. Use when asked to triage a claim, review a first notice of loss (FNOL), assess a new claim, decide fast-track vs adjuster routing, or screen a claim for SIU referral. Produces a structured triage note with coverage view, severity band, indicator screen, reserve range, and a routing recommendation.

Work out whether you're eligible for a class-action settlement or refund program — and actually file the claim before the deadline. Use when asked am I owed money from a settlement, is there a class action for [product/company], how do I claim a settlement, or did I qualify for that refund. Produces a way to check for relevant settlements, an eligibility read against the class definition, the proof you need and how to file, deadline tracking, and honest expectations on payout size — plus how to avoid fake-settlement scams. Not legal advice.

Set up a repo or project so an AI coding agent works well in it — the CLAUDE.md, the context, the guardrails, and the conventions the agent needs to be useful instead of lost. Use when asked how do I set up CLAUDE.md, configure my repo for Claude Code, my AI agent keeps getting my project wrong, or onboard an AI agent to my codebase. Produces a structured CLAUDE.md/project-context file (architecture, conventions, commands, do-nots), the right level of detail (enough to orient, not a novel), the guardrails that keep the agent safe (what not to touch, how to test), and a maintenance habit so it stays current — turning a repo an agent flails in into one it navigates like a teammate.

Activate a 4-stage coding discipline framework that forces Claude to plan before coding, isolate changes on a branch, write tests first, and self-review output twice before presenting it. Use when starting a complex coding task, when past Claude sessions produced broken first drafts, or when you want to prevent rework cycles. Produces a confirmed written plan, isolated feature branch, test-first implementation, and a double-reviewed output with a correctness and code-quality checklist.

Explain a contract clause in plain English — what it means, who it favours, the realistic risk, and what to negotiate. Use when asked what a clause means, to decode legal language, explain a term in a contract, or assess whether a provision is standard or aggressive. Produces a plain-language translation, a who-does-this-favour read, a risk rating, and concrete redline suggestions. Not legal advice; confirm with counsel.

Write clear at-home care instructions for a pet owner after a veterinary visit, procedure, or hospitalization. Use when asked to write discharge instructions, go-home notes, post-op care, or medication instructions for a pet owner. Produces plain-language home-care instructions: medications (what/how much/when/how), activity restrictions, what to watch for, warning signs that mean call-now, the recheck plan, and emergency contacts — written so a worried owner can actually follow them.

Run a consulting client discovery session — uncover the real problem, scope, and decision process. Use when asked to prepare for a client discovery call, qualify a consulting lead, scope an engagement, or run a kickoff. Produces a discovery plan — the questions that surface the real problem (not the stated one), budget/authority/timeline qualifiers, success criteria, red flags, and a follow-up that leads to a proposal.

Wrap up a client project the right way — a clean handoff, a strong final impression, and the moves that turn a finished project into referrals and repeat work. Use when asked to wrap up a client project, offboard a client, end a client relationship well, or project handoff. Produces a closeout checklist (deliverables, access, final invoice, documentation), a handoff/wrap-up message, the referral/testimonial/repeat-work asks to make at the peak moment, a graceful process for ending an ongoing relationship, and how to leave the door open — so the ending builds your business instead of just stopping.

Spot a bad client before you sign — the warning signs of the projects that turn into unpaid, scope-creeping nightmares, and how to screen, price, or decline them. Use when asked is this client a red flag, should I take this client, screening a difficult client, or how to avoid bad clients. Produces a read on the warning signs present (haggling, vagueness, disrespect, urgency, unrealistic expectations), what each predicts, screening questions to ask before committing, protective terms if you proceed anyway, and how to decline gracefully — so you avoid the clients who cost more than they pay.

Build a smooth client-onboarding process that starts projects on the right foot — clear expectations, the info you need, and a professional first impression that prevents problems later. Use when asked to onboard a new client, create an onboarding process, kick off a client project, or client welcome packet. Produces a welcome and kickoff flow, the intake you need to start, expectation-setting on scope/comms/timeline/payment, a kickoff-meeting agenda, and the templates to reuse — so onboarding is consistent, not improvised, and prevents the scope and communication problems that sink projects.

Assess physical and transition climate risk for a site, product, or portfolio with scenario-based structure. Use when asked to run a climate risk assessment, evaluate physical or transition risk, prepare TCFD/ESRS-style climate risk analysis, or assess how climate scenarios affect an asset or business. Produces a hazard-exposure-vulnerability matrix across 2030/2040/2050 horizons and labelled scenarios, with financial-impact ranges, confidence levels, and adaptation options.

Write a structured clinical case summary or case presentation. Use when asked to write a clinical case summary, case presentation, patient case report, or clinical handover. Produces a structured summary using SBAR or SOAP format. For educational and documentation purposes only — not a substitute for clinical judgement.

Draft a clinical trial protocol synopsis with the elements regulators and IRBs expect. Use when asked to write a clinical trial protocol, a study protocol synopsis, a trial design, or to structure endpoints/eligibility/statistics for an interventional study. Produces a structured protocol synopsis — objectives, design, population with eligibility, interventions, endpoints, statistics, and safety/ethics — for expert review. (For non-clinical/UX research, use research-protocol.)

Turn one long video, podcast, or stream transcript into 8-12 short-form clips — each with a hook line, cut timestamps, captions, and a platform note for TikTok/Reels/Shorts — plus an honesty gate that kills clips that misrepresent the source. Use when someone says 'clip this podcast', 'make shorts from my video', 'what's clippable here', or runs a clipping side hustle. Produces a ranked clip sheet ready for an editor or a clipping app.

Send your position to a meeting instead of your body — a one-page brief carrying your stances, fallbacks, red lines, tradables, and delegation limits, readable by the colleague (or agent) representing you. Use when you can't attend a decision-making meeting, when double-booked, when briefing someone to negotiate for you, or 'what would you need from me to represent me?'. Produces the clone brief plus a 60-second verbal version for the person carrying it.

Decode a mortgage Closing Disclosure line by line — which fees are real, which are shoppable or junk, and what changed since the Loan Estimate. Use when asked to decode my closing disclosure, review my closing costs, why did my costs go up, or which fees can I negotiate. Produces a section-by-section decode, the Loan-Estimate comparison with tolerance flags, the challenge list with scripts, and the cash-to-close verification.

Plan a co-marketing partnership — two brands reaching each other's audiences for mutual gain. Use when asked to plan a partnership, joint campaign, co-branded content/webinar, integration launch, or partner outreach. Produces the partner fit rationale, a fair value exchange, the joint campaign plan, the partner pitch, and how success is split and measured.

Write calm, businesslike co-parenting messages that keep the focus on the kids and stay out of the old conflict — for scheduling, expenses, decisions, and hard topics. Use when asked to write a message to my co-parent, respond to my ex about the kids, co-parenting communication help, or how to reply without a fight. Produces a message drafted in a neutral, child-centered tone (the 'BIFF'-style brief/informative/friendly/firm approach), the bait removed, a clear ask or answer, and a note on documentation — steering away from anything that escalates. Not legal advice.

Make a genuinely good drink from the bottles already on your shelf — no special trip, no 12-ingredient recipe. Use when asked what can I make with [spirits], cocktail from what I have, I've got [bottles] what can I drink, or make me a drink without buying anything. Produces two or three cocktails you can build right now with ratios, a method, sensible substitutions for what you're missing, and a zero-proof version — scaled to how many you're making.

Explain what a piece of code does in plain English, at the depth the reader needs. Use when asked to explain code, walk through a function, understand an unfamiliar snippet, or onboard to a file. Produces a one-line summary, a step-by-step walkthrough, the non-obvious parts called out, and any bugs or smells spotted along the way.

Generate a tailored code review checklist for any pull request based on the language, type of change, and risk level. Use when asked to review code, check a PR, review a pull request, or generate a code review checklist. Produces a focused checklist with language-specific checks, risk-level-appropriate depth, and a clear approve/request-changes recommendation.

Review a pull request or diff like a thoughtful senior engineer — prioritized, kind, and focused on what matters. Use when reviewing code, giving PR feedback, or asked to 'review this change'. Produces a structured review: a correctness/design pass, comments ranked by severity (blocking → nit), what's done well, and a clear approve / request-changes call — feedback that improves the code and the author.

Simplify code that works — remove speculative abstraction, dead flexibility, and needless indirection while keeping behaviour identical and verified. Use after a feature lands ('now simplify it'), when AI-generated code arrives over-engineered, when a file has grown hard to follow, or as the cleanup pass before review. Produces a smaller, flatter version with identical behaviour, plus a ledger of what was removed and why it was safe. For finding bugs use code-review-checklist / ai-code-review — this skill assumes it works and makes it simple.

Structure a cohort analysis for retention, LTV, or behavioural patterns. Use when asked to run a cohort analysis, analyse retention by cohort, segment users by behaviour over time, or calculate lifetime value by acquisition period. Produces a complete cohort analysis framework with methodology, cohort definitions, retention curves, and prioritised interventions.

Fit a retention curve to observed cohort data and project LTV — computed, not estimated. Use when someone has real cohort retention numbers (month 0, 1, 2…) and asks what lifetime value, lifetime periods, or long-run retention they imply, or whether retention is flattening or leaking. Produces a fitted power curve (parameters, R², retention floor), a 24-36 period projection, and a real .xlsx with live formulas where editing ARPU recalculates LTV — via the bundled zero-dependency script.

Write a cold sales/B2B outreach email that earns a reply. Use when asked to write a cold email, a sales outreach email, a prospecting email, or a cold email sequence to a business prospect. Produces a short, personalised email — subject, a relevant opener, one clear value-led ask, and a low-friction CTA — plus 2 follow-ups, written to be replied to, not deleted.

Write cold outreach to potential clients that gets replies — specific, useful, and about them — instead of the templated pitch that gets deleted. Use when asked to write a cold email to a prospect, get clients through outreach, cold pitch help, or reach out to potential customers. Produces a researched, personalized message that leads with their problem, a clear low-friction ask, proof you're credible without bragging, a subject line, and a short follow-up sequence — plus who to target and what to avoid so it lands as a helpful note, not spam.

Start a cross-team project with the collaboration contract that prevents the classic collisions — who decides what, how work flows between teams, the communication channels and cadence, and what done means — agreed before the first collision instead of during it. Use when asked kick off this cross-team project right, our two teams keep colliding, define how we'll work with the other team, or set up the partnership before we start. Produces the one-page contract: decision rights, interfaces, cadence, and the done-definition.

Write a polite-but-firm payment-reminder / collections email sequence for overdue invoices. Use when asked to write a collections email, a payment reminder, a dunning sequence, or to chase an overdue invoice. Produces a staged sequence — gentle pre-due nudge through escalating overdue reminders to a final notice — that stays professional, keeps the relationship intact, and makes paying easy. Not legal advice.

Support a teenager through college applications without taking them over — the parent's actual jobs (logistics, finances, emotional ballast), the ownership lines that keep the application theirs, and the scripts for the hard moments. Use when asked how do I help my kid with college apps, how involved should I be, my teenager won't start their essays, or we disagree about the college list. Produces the role split, the family timeline, the money conversation framework, and the scripts for deadlock, rejection, and the essay you must not write.

Compute what a degree will actually cost — sticker minus real aid, inflated per year, split into cash and loans, with the loan's decade-long monthly tail made visible before enrollment instead of after. Use when asked what will college really cost, compare these two offers' real prices, how much loan payment after graduation, or is this school affordable. Produces the all-in number from the script, the offer-letter decode (grants vs loans untangled), the monthly-tail reality check, and the two-school comparison.

Prepare and rehearse a coming-out conversation, tuned to the specific person and the real risk — what to say, how to open, how to handle the likely reactions, and a safety-first plan if it could go badly. Use when someone says 'I want to come out to my parents/boss/friend', 'help me tell them I'm [gay/trans/bi/etc.]', 'rehearse this conversation with me', or is planning any identity disclosure. Produces an opener, a rehearsal against realistic reactions, and a safety plan. Safety and the user's autonomy come first — it never pushes anyone to come out.

Capture everything an outgoing club secretary, chair, or organizer carries in their head before they disappear — accounts and logins with owners, the annual rhythm calendar, key relationships and their quirks, the unwritten rules, and the first-90-days guide for the successor. Use when a committee member is stepping down, when someone says 'it all lives in Linda's head', or right after elections. Produces a complete handover pack plus the one-hour handover meeting agenda.

Build a community management playbook for a brand's social media channels. Use when asked to create guidelines for managing comments, DMs, and community interactions, define a moderation policy, or build response frameworks for social media community managers. Produces a complete playbook with response templates, escalation paths, moderation rules, and tone guidelines.

Write a fair, enforceable community moderation policy. Use when standing up or overhauling moderation for a forum, Discord, Slack, subreddit, or any user community. Produces a clear code of conduct with examples, a graduated enforcement ladder tied to specific triggers, an appeals process, moderator guidelines, and the handling for the severe cases (threats, doxxing, brigading) that need immediate action. Governs member conduct in a user community — distinct from [[community-management-playbook]], which manages a brand's own social-media channels (comments, DMs, tone, response templates).

Build a candidate's research brief on a company before an application or interview. Use when asked to research a company for a job, prep a company brief before an interview, or understand a prospective employer fast. Produces a one-page brief — what they do & how they make money, recent news & trajectory, product & competitors, likely challenges, culture signals, and smart questions to ask.

Run a company event — the launch party, the customer day, the team celebration — as the operation it is: the goal that shapes every choice, the budget with its forgotten lines, the vendor and venue coordination, the run-of-show with owners, and the day-of roles that keep hosts hosting. Use when asked plan the company event, organize our customer day/holiday party/launch event, what am I forgetting for this event, or be the run-of-show for Thursday. Produces the goal-shaped plan, the budget with the forgotten lines, the run-of-show, and the day-of role card.

Build a comparative market analysis (CMA) to price a property. Use when asked to do a CMA, a comparative market analysis, price a home, or estimate a property's value from comparables. Produces a structured CMA — the subject property, selected comparables with adjustments, an estimated value range, market context, and a pricing recommendation with rationale — for a real-estate professional to review. Not a formal appraisal.

Analyze competitors and create competitive landscape documentation with feature matrices, positioning maps, and strategic recommendations. Use when asked to analyze competitors, create competitive analysis, compare features with competitors, build a competitive landscape, track competitive positioning, or prepare sales battlecard inputs. Produces structured competitor profiles, feature comparison matrix, win/loss analysis, and prioritised strategic recommendations. For a one-off teardown of a single rival use competitor-teardown; for a recurring market briefing use competitive-intelligence-monitor.

Monitor competitor signals and surface strategic implications for your roadmap. Use when asked to monitor competitors, track the competitive landscape, produce a competitive briefing, or understand what has changed in the market this week or month. Produces a structured intelligence brief with high/medium/low priority signals, roadmap implications, and a strategic landscape summary. For a single competitor announcement use competitor-signal-tracker; for a one-off deep dive use competitor-teardown.

Run a fast, honest competitive scan — the dimension table built from public evidence (sites, docs, pricing pages, changelogs, reviews), the claims-vs-observed discipline, and the so-what synthesis that ends in moves, not a landscape mural. Use when asked what are competitors doing, quick scan of these three rivals, how does our pricing/feature set compare, or prep the competitive slide honestly. Produces the evidence-based comparison table, the marketing-vs-reality flags, the so-what synthesis, and the staleness date.

Analyse competitor moves and translate them into strategic implications for your product roadmap. Use when a competitor announces a new feature, pricing change, partnership, or strategic shift, or when producing a periodic competitive intelligence report. Produces a categorised signal analysis with reactive-vs-proactive assessment, threat ratings, specific roadmap implications, and recommended responses with owners. For a recurring whole-market briefing use competitive-intelligence-monitor instead.

Produce a structured competitive analysis for any product or market. Use when asked for a competitor analysis, competitive teardown, market comparison, SWOT, or positioning map. Generates a structured teardown with positioning map, feature comparison, messaging gaps, and strategic recommendations. For a full landscape doc with feature matrix and win/loss analysis use competitive-analysis instead.

Write a firm, effective complaint letter that gets a resolution. Use when asked to write a complaint letter, complain to a company about a product/service, escalate poor service, or demand a refund/replacement. Produces a structured complaint — the facts, the impact, the specific resolution you want, and a deadline — in a firm, professional tone that's hard to ignore and easy to act on.

Generate a prioritised compliance checklist for GDPR, SOC 2, ISO 27001, FCA, HIPAA, or other frameworks with a gap analysis. Use when asked for a compliance checklist, gap analysis, readiness assessment, or audit preparation for any regulatory framework. Produces a structured checklist with prioritised gaps, quick wins, and evidence requirements. Optimised for Opus 4.7 and newer models. Not a substitute for legal or compliance professional advice.

Make compound growth actually click — see how small, consistent amounts become large over time, and why starting now beats starting bigger later. Use when asked explain compound interest, how does compounding work, is it worth investing small amounts, or why should I start now. Produces an intuitive explanation of compounding with concrete illustrative examples for your situation, the outsized effect of time (why an early start beats a later larger one), how fees and inflation eat into it, and the honest caveats — turning an abstract concept into the motivation to start now. Educational, not financial advice.

Write a sincere condolence or sympathy message when someone has died or a friend is grieving — warm, personal, and free of the clichés that hurt more than help. Use when asked what to say when someone dies, write a sympathy/condolence message, my friend lost their [person], or I don't know what to say. Produces a heartfelt message tuned to your relationship and the situation, drawn from a specific memory or quality where possible, an honest acknowledgment (not toxic-positive platitudes), an offer of concrete support, and guidance on what to avoid saying.

Write a conference talk proposal / CFP submission for a tech or developer conference. Use when asked to submit to a CFP, propose a talk, or write a session abstract. Produces a compelling title, abstract, audience takeaways, an outline, and the speaker pitch — tuned to what selection committees actually look for.

Calm a heated conflict — in person or in writing — before it does damage, by lowering the temperature instead of winning the point. Use when asked help me de-escalate this, this argument is getting heated, calm this situation down, or how do I respond without making it worse. Produces a read on what's actually driving the heat (often an unmet need under the surface argument), the de-escalation moves (acknowledge, slow down, find the shared ground), what to say and what to avoid, and how to steer toward resolution once the temperature drops — because you can't solve anything while everyone's activated.

Write a consulting proposal that wins the engagement — outcomes over hours. Use when asked to write a consulting proposal, a project proposal, a pitch for a client engagement, or to respond to an RFP. Produces a proposal — the client's problem in their words, your approach & deliverables, outcomes/value, timeline & phases, investment with options, and why-you — framed around results, not a task list. Ready to export as a designed PDF.

Generate a structured content calendar for any brand, product, or creator. Use when asked for a content plan, editorial calendar, social media schedule, or weekly/monthly content strategy. Produces a calendar with topics, formats, channels, and copy hooks.

Turn one piece of content into a full multi-platform pack — X/Twitter thread, LinkedIn post, newsletter section, Instagram carousel, and a short-form video script — each rewritten natively for its platform, not copy-pasted. Use when asked to repurpose content, atomize a blog post or video, turn one idea into many posts, or get more mileage from a piece. Produces ready-to-post drafts per platform with hooks, formatting, and CTAs tuned to each.

Create a content style guide / voice & tone guide so everyone writes consistently. Use when asked to write a content style guide, a voice and tone guide, editorial guidelines, or UX-writing standards. Produces a usable guide — voice principles with do/don't examples, tone-by-context, mechanics (grammar, capitalisation, formatting), terminology/word list, and accessibility/inclusivity rules — that a team can actually apply.

Declare bankruptcy on a long-lived AI agent's accumulated memory — audit what it currently believes, separate ground truth from stale and wrong, purge deliberately, restate the truths that survive, and log what was lost. Use when an agent keeps acting on outdated facts, contradicts itself across sessions, 'remembers' things wrong, or after a reorg/pivot makes its worldview obsolete. Produces a belief audit, a keep/correct/purge ledger, a restated ground-truth file, and the bankruptcy record.

Plan a session's context window like the budget it is — what loads up front, what gets linked instead, what stays fetch-on-demand, and how to keep the stable prefix cache-friendly so repeated turns cost cents instead of dollars. Use when asked my agent keeps blowing its context, plan what to load into the session, why is every turn so expensive, or design the context for this workflow. Produces the load/link/fetch allocation, the cache-aware prefix layout, the per-turn cost shape, and the eviction rules for when the window fills anyway.

Compress tool outputs, logs, and JSON before they enter the context window — structural compression via a deterministic stdlib script (schema + samples + stats instead of 300 raw rows), no API, no summarization loss. Use when asked shrink this tool output, my context is full of JSON, compress these logs before analysis, or stop wasting tokens on raw data. Produces the crushed artifact with its token math shown, the crush-or-keep decision rules, and the fetch-the-original escape hatch.

Review what an LLM feature or agent actually puts in its context window — and find what's bloating, missing, or fighting itself. Use when asked to review a system prompt and context assembly, cut token usage without losing quality, debug an agent that ignores instructions, or audit how retrieval results, history, and tool definitions are packed into the window. Produces a context inventory with a keep/cut/restructure verdict per component, ordering and caching fixes, and a token budget. For wording-level prompt tuning use prompt-optimizer.

Keep Claude Code sessions productive across resets with output filtering, session logging, and auto-resume. Use when starting a long or complex coding session, when previous sessions lost context mid-task, or when you need Claude to resume exactly where it left off after a reset. Produces a session.log at the project root, filtered command output that preserves context, and automatic resume of in-progress tasks after any reset.

Treat context switches as the budget line they are — the switch census (how fragmented the week really is), the batching moves that consolidate scattered same-kind work, the calendar defrag that turns Swiss cheese into slabs, and the switch-cost line for saying no. Use when asked my day is fragmented to death, count my context switches, batch my meetings and reviews, or defend against calendar Swiss cheese. Produces the fragmentation census, the batching plan, the defrag moves, and the protective phrases.

Reconstruct where you were and what's next after an interruption, so a broken focus doesn't cost you the whole thread. Use when asked where was I, I got interrupted and lost my place, help me pick back up, or I forgot what I was doing. Produces a quick rebuild of the task's state from what you remember (what you'd done, what you were mid-thought on), the single next action to re-enter it, and a 'breadcrumb' habit for next time — cutting the expensive re-immersion cost that interruptions inflict, especially on ADHD brains.

Scan a contract you're about to sign in plain language — surface the clauses that could bite you, what they mean, and what to question or renegotiate. Use when asked to check this contract before I sign, what am I agreeing to, are there red flags in this agreement, or explain this contract's risky bits. Produces a plain-English flag list of the risky/unusual clauses (auto-renewal, lock-in, liability, IP, termination, fees), what each means for you, questions to ask, and suggested changes — flagging when it's important enough for a lawyer. Not legal advice.

Never get auto-renewed into another year again — the contract inventory with the dates that matter (notice deadlines, not renewal dates), the calendar system with decision-time buffers, and the renewal-decision ritual that renegotiates instead of rubber-stamping. Use when asked track our contracts and renewals, we got auto-renewed again, when do we have to decide on this vendor, or set up renewal management. Produces the inventory with notice-deadline math, the alert system, the renewal-decision checklist, and the negotiation-window playbook.

Review and summarise any contract or legal agreement. Use when asked to review a contract, check an agreement, flag legal risks, or summarise key clauses. Produces a structured review with key terms, flagged clauses, risk rating, and plain English summary. Not a substitute for qualified legal advice.

Handle a dispute with a contractor — unfinished work, poor quality, overcharging, or a no-show — with a path that protects your money and your options. Use when asked to deal with a contractor dispute, my contractor did bad work / won't finish / overcharged, or how to get a builder to fix their work. Produces a read on your position (contract, payments, evidence), a firm-but-professional communication and demand path, documentation and payment-leverage guidance, and escalation options (mediation, licensing board, chargeback, small claims) — flagging that it's not legal advice.

Write a CONTRIBUTING guide that helps people contribute to an open-source project without friction. Use when asked to write a CONTRIBUTING.md, set up contribution guidelines, or make a repo welcoming to contributors. Produces a clear guide: how to set up, the contribution workflow, standards, PR expectations, and how to get help — lowering the barrier to a first PR.

Audit a landing page or funnel step and produce a prioritised CRO test plan. Use when asked to improve conversion rate, audit a landing/signup/checkout page, reduce funnel drop-off, or plan A/B tests for a page. Produces a CRO plan — a heuristic conversion audit, the diagnosed friction, prioritised test hypotheses (ICE), test designs with sample-size math, and the measurement guardrails.

Build a beginner running plan from wherever you are to a real goal — first nonstop mile, 5K, or 10K — that builds up slowly enough to avoid injury. Use when asked for a couch to 5k plan, help me start running, train for a [distance], or a running plan for beginners. Produces a week-by-week walk/run progression to the goal, session detail, pacing and form basics, rest and cross-training, and an injury-prevention note — with a 'check with a doctor if you have health conditions' flag.

Decode a counteroffer after you resign — what the raise, promotion promise, or title bump really signals, the statistics-informed risks of staying, and a clear-eyed decision framework. Use when asked my company countered my resignation, should I accept a counteroffer, they offered me more to stay, or decode this retention offer. Produces a component-by-component decode with 🔴🟡🟢 severity, the questions that expose which promises are real, and the stay/go decision sheet.

Write a specific, non-generic cover letter that connects your evidence to the role. Use when asked to write a cover letter, an application letter, or a note to accompany a resume. Produces a tight 3–4 paragraph letter — a real hook, two evidence paragraphs mapping your proof to the job's needs, and a confident close — tailored to the company, ready to export as a designed PDF.

Map an organisation's risks against its insurance policy portfolio to find what's uncovered, underinsured, or double-covered. Use when asked to run a coverage gap analysis, review an insurance programme against a risk register, check what risks aren't insured, or audit a policy portfolio. Produces a risk-by-coverage matrix, flagged gaps and overlaps, a deductible stack review, and recommendations ranked by expected-loss severity.

Define a creator's brand foundation — niche, audience, positioning, content pillars, voice/tone, and bio — so every post is consistent and on-brand. Use when asked to define a creator brand, find a niche, set content pillars, write a voice guide, craft a bio, or build a brand kit for a personal brand or channel. Produces a reusable one-page brand kit that other content skills can read so output sounds like you, every time.

Decode a brand deal or UGC contract before signing — usage rights, exclusivity windows, whitelisting, payment terms, and kill clauses ranked 🔴🟡🟢 by what they can cost a creator, plus the counter-ask email. Use when a creator says 'is this brand deal fair', 'what does perpetual usage mean', 'they sent me a contract', or 'should I sign this collab agreement'. Produces a clause-by-clause decode, a money-math check on the rate, and a ready-to-send negotiation email. Not legal advice.

Build a creator's sponsorship media kit and brand-deal outreach — the one-pager brands ask for, plus a pitch email and a rate card. Use when asked to make a media kit, pitch a brand, land a sponsorship, write a brand-deal email, or set creator rates. Produces a structured media kit (audience, stats, offerings, past work), a personalised outreach email, and a defensible rate card. The creator side of a sponsorship — distinct from a brand briefing a creator.

Get foreign qualifications, degrees, or professional licenses recognised in a new country — figure out whether recognition is even needed, which body assesses it, what evidence they want, and the bridging route if there's a gap. Use when someone says 'get my degree recognised abroad', 'is my foreign license valid here', 'credential evaluation', or 'can I work as a [nurse/engineer/teacher] in [country] with my qualifications'. Produces a recognition roadmap, the assessing body, an evidence checklist, and the bridging options. Routes to official assessment bodies; requirements are country- and profession-specific.

Build a credit history from zero in a new country — understand that credit doesn't transfer across borders, get the first products that report, avoid the newcomer traps, and reach a usable score in months not years. Use when someone says 'I have no credit history in [country]', 'build credit as a newcomer/immigrant', 'why was I rejected with a great score back home', or 'how do I get a credit card/loan as a new arrival'. Produces a credit-building plan, the starter products that report, a timeline, and the traps to avoid. Educational, not financial advice; routes to official credit sources.

Write a credit memo for a lending decision: borrower story, facility structure, repayment sources, financial-ratio spread with covenant headroom, risk factors with mitigants, risk-rating rationale, and a recommendation. Use when asked to write a credit memo, credit application, credit paper, loan write-up, or prepare a deal for credit committee. Produces a complete credit memo ready for committee review.

Stress-test a decision or claim through a sharp, fair Q&A — the questions a good lawyer or skeptical friend would ask before you commit. Use when asked to cross-examine me, ask me hard questions about this, interrogate my plan, or make me defend this. Produces a sequenced line of probing questions (from clarifying to challenging to the killer question), space to answer, and a debrief on where your answers were strong, evasive, or exposed a gap — so weaknesses surface in private before they surface in public.

Fetch live cryptocurrency prices with zero API keys — CoinGecko's public endpoints primary, Coinbase spot fallback, via plain curl. Use when asked what's bitcoin at, ETH price in euros, how's the crypto market today, or price of some altcoin. Produces the current price with 24h context, the source and timestamp, the rerunnable command, and the volatility caveat that crypto answers must carry.

Analyse CSAT / NPS / CES survey results and turn the score into actions. Use when asked to analyse NPS, CSAT, or CES data, compute an NPS score, interpret survey verbatims, or build a voice-of-customer readout. Produces a readout — the computed score, the trend & benchmark, themed analysis of the comments (what drives promoters vs. detractors), and prioritised actions. Includes a stdlib NPS/CSAT calculator.

Convert currencies and fetch live exchange rates with zero API keys — Frankfurter (ECB rates) primary, open.er-api.com fallback, via plain curl. Use when asked convert 500 dollars to euros, what's the USD-INR rate, how much is this in my currency, or historical exchange rate for a date. Produces the conversion with the rate and its date quoted, the rerunnable command, and the not-a-trading-quote caveat.

Plan and run a customer advisory board (CAB). Use when asked to design a customer advisory board, plan a CAB meeting agenda, choose CAB members, or write CAB invitations and follow-ups. Produces a CAB program plan — objectives, member selection criteria, a meeting agenda, discussion guides, roles, logistics, and a follow-up and value-capture plan.

Write a structured escalation brief for an at-risk customer account. Use when an account has escalated, when a customer is threatening churn, when a P1 customer issue needs executive attention, or when preparing an internal save play. Produces a crisp escalation brief with account context, timeline, root cause, business impact, and a clear resolution plan.

Build a customer health scorecard for a specific account. Use when asked to score account health, assess renewal risk, build a health dashboard, or evaluate an account's likelihood to renew or expand. Produces a structured health scorecard with a RAG status, dimension scores, key risks, and recommended actions.

Write the customer-facing incident update during an outage — status-page post or email — that's honest about impact without over-promising. Use when asked to write a status page update, draft customer comms for an outage, post an incident notice, or tell customers about downtime. Produces the update in the right tense for the incident stage (investigating / identified / monitoring / resolved), with impact scope, any workaround, and a concrete next-update time. Distinct from incident-postmortem (the internal retro).

Build a customer journey map for a product, service, or experience. Use when asked to map a customer journey, create a user journey, document touchpoints and pain points, or design an experience map. Produces a complete journey map with stages, touchpoints, emotions, pain points, and prioritised opportunities.

Write clear customer-facing outage and service-disruption notifications. Use when asked to write an outage notice, a status-page update, a service-disruption email, a maintenance notice, or an incident update sequence. Produces status-page updates for each phase (investigating → identified → monitoring → resolved), a customer email, and a resolved/post-incident summary, in plain, reassuring language.

Build a joint customer success plan for a specific account. Use when asked to create a success plan, joint success plan, mutual action plan, or customer onboarding plan. Produces a structured success plan with business goals, milestones, success metrics, ownership, and a 90-180 day roadmap.

Convert a business question into a complete dashboard specification. Use when asked to design a dashboard, create a dashboard spec or brief, plan a BI report, or define what charts and metrics a dashboard should include. Produces a structured spec with metrics, dimensions, chart types, filters, and layout guidance.

Structure a product data analysis, metric deep-dive, funnel analysis, or cohort study. Use when asked to analyse product metrics, investigate a drop in conversion, explain a data change to stakeholders, or find the root cause of a metric movement. Produces a structured analysis with question, root cause, confidence level, and recommended action.

Respond to your data being breached — triage by what actually leaked, the freeze/rotate/monitor ladder in the right order, and the calibrated watchfulness that follows, without panic or paralysis. Use when someone asks my data was in a breach what do I do, I got a breach notification letter, my SSN/ID number leaked, or should I freeze my credit. Produces the leaked-data triage, the ordered response ladder with the do-today items, the monitoring plan, and the breach-letter decode (including what the free credit monitoring offer is and isn't).

Clean a messy dataset methodically — the profiling pass that finds what's actually wrong (dupes, format drift, phantom spaces, mixed types), the fix order that doesn't corrupt while correcting, and the log that makes the cleaning defensible. Use when asked clean this export, why is my pivot double-counting, these names don't match between sheets, or prep this data for analysis. Produces the profile of what's wrong, the ordered cleaning plan, the join-key repairs, and the cleaning log.

Define a data contract between a producer and consumers of a dataset/event/API. Use when asked to write a data contract, define a schema agreement, set data SLAs, or stop a producer from silently breaking downstream consumers. Produces a contract — schema with types & constraints, semantics, quality SLAs (freshness/completeness/validity), ownership, versioning & breaking-change policy, and a change process.

Design an ETL/ELT data pipeline specification. Use when asked to design a data pipeline, spec an ETL or ELT process, document a data ingestion workflow, or plan a data integration. Produces a complete pipeline spec with sources, transforms, destinations, SLAs, error handling, and data quality rules.

Audit a dataset for the quality problems that silently break analysis — missingness, duplicates, outliers, type and range errors, consistency, and freshness — and produce a prioritised fix list. Use when asked to assess data quality, audit a dataset, check data before analysis, or explain why numbers look off. Produces a structured quality report across the standard dimensions, the specific issues found (with the checks to run), severity, and how to fix each.

Design the data quality checks for a table or pipeline across the standard dimensions. Use when asked to add data quality tests, define DQ checks, catch bad data before it hits dashboards, or set up monitoring for a dataset. Produces a checks plan across completeness, validity, uniqueness, freshness, consistency, and accuracy — each with the rule, severity, and where it runs (dbt test / Great Expectations / SQL assertion).

Build a data retention and deletion schedule grounded in legal basis. Use when asked to create a data retention policy, set retention periods, plan data deletion/minimisation, or answer 'how long can we keep this data?'. Produces a retention schedule — data categories with their retention period, legal/business basis, deletion trigger and method, plus flags for data kept with no basis or no defined period.

Design slides where the data makes the argument — the takeaway-titled chart, the one-chart-per-slide rule, the annotation layer that guides the eye to the point, and the honesty pass on projected data. Use when asked make this data slide land, my chart slide confuses people, how do I present these numbers, or the audience missed the point of my graph. Produces the redesigned slide: takeaway title, the chart stripped and annotated, the eye-path check, and the honesty audit.

Get your personal info off people-search and data-broker sites — a prioritized opt-out plan that targets the sites that matter and keeps them from reappearing. Use when asked to remove my info from the internet, opt out of data brokers, my address/phone is on people-search sites, or reduce my digital footprint. Produces a prioritized target list (the high-traffic brokers first), the opt-out method for each, a suppression-at-source plan so data stops flowing back, a recheck cadence, and safe-handling cautions for the personal data you'll be submitting.

Write a safe, zero-downtime database migration plan for a schema change. Use when asked to plan a database migration, design a zero-downtime schema change, document an expand/contract migration, produce a rollback procedure for a database change, or coordinate a database schema update with a deployment. Produces a structured migration plan covering migration objectives, backward compatibility analysis, expand/contract phase breakdown, exact SQL, rollback steps per phase, data validation queries, and a deployment runbook.

Document or design a database schema with entity relationships, table definitions, constraints, indexes, and access patterns. Use when asked to design a database, document an existing schema, model entities and relationships, define table structures, plan an index strategy, or produce a data model for review. Produces a structured schema document covering an ER diagram, table DDL definitions, index strategy, access pattern analysis, normalization decisions, and migration notes.

Document a dataset so others know what it is, how it was made, and when not to use it. Use when asked to write a datasheet for a dataset, document training/eval data, or assess whether a dataset is fit for a use. Produces a datasheet — motivation, composition, collection process, preprocessing, recommended uses & limits, distribution, and maintenance.

Rewrite a dating profile so it sounds like you on a good day — mined from how you actually talk, specific instead of generic, with photo order feedback and first-message craft — under one hard rule: nothing you can't back up in person. Use when someone says 'fix my dating profile', 'why am I getting no matches', 'what do I say first', or 'roast my Hinge prompts'. Produces rewritten bio and prompts, a photo lineup critique, and three first-message templates that reference, not flatter.

Run the real math on a parent leaving work versus paying for childcare — the second income net of daycare, marginal taxes, and work costs, AND the career-trajectory cost of years out, over horizons instead of one brutal year. Use when asked does it make sense for me to keep working, daycare costs my whole salary, stay-home vs daycare math, or what does leaving work for 5 years really cost. Produces both sides of the ledger from the script, the horizon comparison, and the decision sheet that lets the non-financials vote.

Spec a dbt model — its grain, sources, transformations, tests, and materialization. Use when asked to design a dbt model, plan a data transformation, write a staging/intermediate/mart model spec, or define dbt tests for a table. Produces a model spec — purpose & grain, lineage (sources → refs), the transformation logic, column definitions, dbt tests, materialization choice, and the skeleton SQL/YAML.

Respond to a debt collector correctly — know your rights, make them prove the debt, and avoid the mistakes that reset the clock or admit liability. Use when asked how to deal with a debt collector, a collection agency is contacting me, is this debt real, or respond to a collections letter. Produces a validation/proof-of-debt request, a rights-aware read on what collectors can and can't do, guidance on statute-of-limitations and not accidentally restarting it, a communication and record-keeping plan, and escalation if they break the rules. Not legal advice.

Build a debt payoff plan — avalanche vs snowball simulated month by month on your actual debts, the real payoff dates, and the psychology-vs-arithmetic tradeoff priced in dollars. Use when asked how do I pay off my debts, avalanche or snowball, make me a debt payoff plan, or when will I be debt-free. Produces the month-by-month comparison from the script, the payoff order with dates, the interest cost of choosing morale over math, and the plan-survival rules.

Build a debt-payoff plan across multiple debts using the avalanche or snowball method. Use when asked to pay off debt, tackle credit cards/loans, or choose between avalanche and snowball. Produces an ordered payoff schedule, the total interest and time for each method, and a clear recommendation. Educational, not regulated financial advice.

Handle debt collectors without getting bullied or tricked — what to say, what never to say, and the rights that protect you from harassment and illegal tactics. Use when asked how do I deal with debt collectors, a collector keeps calling, can they do this, or how to respond to a collection notice. Produces ready scripts (request written validation, dispute, cease-contact, set boundaries), the phrases that accidentally restart the clock or admit the debt (and to avoid them), your rights under fair-debt-collection rules (harassment limits, validation, what's illegal), how to check the debt is real and yours, and safe next options — so you deal from a position of rights, not fear. Not legal advice; points to consumer-protection agencies and legal aid.

Parse error logs, stack traces, and crash reports into a structured root cause diagnosis. Use when an application is throwing exceptions, crashing, or producing unexpected errors and you need to understand why and what to fix. Produces a structured diagnosis with error classification, stack trace walkthrough, probable root cause with confidence level, affected code path, a concrete code-level fix suggestion, and ordered next debugging steps.

Judge a past decision by its PROCESS, not its outcome — because good decisions lose and bad decisions win, and teams that can't tell the difference learn the wrong lessons. Use when reviewing a big call after the fact (a bet that failed, a pass that haunts, a hire, a pivot) and the room is about to conclude 'it failed so it was wrong.' Produces a process-forensics report: what was knowable then, the quality grade of the decision as-made, the luck accounting, and the ONE process change worth keeping.

Reconstruct the decision actually made in a messy Slack, email, or meeting thread into a proper decision record — commitments named, silent assumptions surfaced, non-decisions called out. Use when asked what did we actually decide, turn this thread into a decision record, who committed to what, or reconstruct this discussion. Produces a decision record with quoted evidence, a commitments table, reconstructed assumptions, dismissed options, and a confidence note on the reconstruction itself.

Help me decide between options with a weighted pros/cons that actually reaches a recommendation — not just two lists. Use when asked should I take job A or B, which one should I buy, help me decide, or make a pro/con list. Produces the criteria that matter (weighted by what you care about), the options scored against them, a clear recommendation with its confidence, and the single question that would flip the decision if you're still torn.

Record decisions the way good judgment compounds — the reasoning, the alternatives, the probabilities, and what would change your mind, written down BEFORE the outcome arrives, then reviewed against reality. Use when asked help me think through this decision, start a decision journal, review my past decision, or why do I keep making the same mistake. Produces the pre-registered decision entry, the review-date trigger, and the outcome review that separates bad luck from bad process.

Set up the team decision log that ends relitigation — the one-line-per-decision format (what, why, who, when, reopening rule), the capture moments wired into existing rituals, and the lookup habit that makes it pay. Use when asked set up a decision log, we keep re-deciding the same things, where do decisions get recorded, or new people keep asking why we do X. Produces the log format, the capture wiring, the reopening rule, and the retrieval habits.

Run meetings that actually decide — the pre-read-then-decide format, the options-on-the-table rule, the decider named before debate starts, and the recorded-or-it-didn't-happen close. Use when asked run this decision meeting, we discuss forever and never decide, structure the meeting where we pick the vendor/plan/design, or why do our decisions get relitigated. Produces the meeting design: pre-read, the in-room sequence, the decision rule, and the recording that makes it stick.

Write a crisp decision memo that drives a clear decision, not a discussion. Use when asked to write a decision memo, a recommendation memo, a one/six-pager for a decision, or to get leadership to decide something. Produces a decision memo — the decision & recommendation up front, the context, options with trade-offs, what you'd need to believe, risks, and the explicit ask with a deadline.

Run a decision past a panel of clashing advisors — an optimist, a pessimist, a numbers person, an ethicist, and future-you — then get a chair's verdict. Use when asked to help me decide, weigh this decision, what should I do about, or run this by different advisors. Produces each advisor's honest take on the decision (each committed to their lens), where they disagree most, the question that would break the tie, and a chair's recommendation that weighs the panel — turning a lonely choice into a structured board meeting.

Make a decent decision when you're too depleted to think well — a low-energy protocol that protects you from bad tired-brain choices. Use when asked I'm too tired to decide, help me choose I'm exhausted, I can't think straight right now, or should I even decide this now. Produces a first check on whether this decision can simply wait until you're rested, and if not, a minimal-effort path to a safe-enough choice (default to reversible, avoid the tired-brain traps, use a simple rule) — because decisions made depleted are predictably worse, and the best move is often not to make them now.

Autopsy a slide deck from photos or screenshots of its slides — the narrative arc, the numbers, and what each slide is hiding. Use when given slide images (a competitor's pitch, a conference talk, your own deck before a big meeting) and asked what the deck argues, whether it holds up, or how to counter or improve it. Produces a slide-by-slide read, the reconstructed argument chain, weak links, and the questions the deck is engineered to avoid. Requires image input.

Turn the user's REAL doc into a slide deck — open the source, structure the narrative, and build the actual .pptx — not slide-writing tips. Use when asked to make a deck from this doc, turn my brief into slides, build the presentation from my Drive doc, or deckify this in Cowork. Reads the document via the Google Drive/Docs connector, maps it to a one-idea-per-slide narrative, and produces a real presentation artifact (.pptx) with speaker notes plus a slide-by-slide outline.

Give a deck a spine the room can follow — the situation-complication-resolution arc, the tension that makes the recommendation feel necessary, the transitions that carry the thread between slides, and the arc-check that catches sag. Use when asked make this deck flow, my presentation feels like disconnected slides, structure the story of this pitch/readout, or the room got lost in the middle. Produces the arc mapping, the tension line, the transition script, and the sag diagnosis.

Outline a deck as headline sentences before opening the slide tool — each slide a claim that reads as an argument top to bottom, the audience-and-ask header, and the skim test that catches broken decks while they're still bullet points. Use when asked start this presentation, structure my deck, why does my deck feel like a data tour, or get sign-off before I build slides. Produces the headline outline, the per-slide evidence notes, the skim test result, and the build rules.

Review a deck against a rubric instead of taste — the five dimensions (argument, evidence, density, arc, honesty), the severity-sorted feedback that separates broken from suboptimal, and the review conversation that improves the deck without rewriting it in the reviewer's voice. Use when asked review my deck, give feedback on this presentation, is this ready for the board, or our deck reviews are just font opinions. Produces the rubric scores with evidence, the severity-sorted feedback, the two-fixes-that-matter-most call, and the reviewer discipline notes.

Declutter a room (or a whole home) with a plan that actually finishes — a sensible order, quick decision rules, and a way to keep it from creeping back. Use when asked how to declutter, help me declutter my [room], I'm overwhelmed by clutter, or a decluttering plan. Produces a room-by-room order, a decision framework for keep/donate/sell/toss, time-boxed sessions sized to your energy, where to route the outflow, and habits to stop the clutter returning — without demanding you become a minimalist or do it all in one heroic weekend.

Protect focus time that actually survives the week — the block placement matched to real energy hours, the defense rules (what moves a block, what never), the entry ritual that beats the blank-stare start, and the honest sizing that stops 8-hour fantasy blocks. Use when asked block focus time that keeps getting eaten, when should I schedule deep work, my calendar has no room to think, or I block time and then waste it. Produces the block design, the defense tiers, the entry ritual, and the meeting-culture negotiation.

Run a tabletop drill of a voice-clone or deepfake fraud attempt — the 'CEO needs this wire today' call — against your actual approval process, before a real attacker does, then debrief the tells and fix the process gap. Use when someone asks to train the team on deepfake fraud, test wire-transfer controls, run a social-engineering tabletop, or 'could we get CEO-frauded?'. Produces a drill scenario pack, a facilitator script, a tells checklist, and the process fixes the drill exposed. Defensive training only.

Respond to false, damaging statements about you or your business — decide what actually counts as defamation, preserve evidence, and choose the right response from correction to takedown to legal action. Use when asked someone posted lies about me, respond to a false review/statement, is this defamation, or protect my reputation online. Produces a read on whether it likely crosses from opinion into actionable falsehood, evidence-preservation steps, a tiered response (platform report, correction/retraction request, cease-and-desist, legal), and a caution against reactions that make it worse. Not legal advice.

Draft a construction delay notice or delay claim letter with contract clause citation, cause classification, and critical-path impact narrative. Use when asked to write a delay notice, put the owner or GC on notice of delay, draft a time extension request, respond to weather or owner-caused delay, or paper a delay for a claim. Produces a notice/claim letter with the excusable-compensable classification, critical-path impact narrative, quantum placeholder, reservation of rights, and a records-preservation list.

Decide what in your workload to hand to AI and what to keep yourself — like managing a fast, capable, but unreliable new hire — so you get leverage without offloading the things that need you. Use when asked what should I delegate to AI, what can AI take off my plate, where should I use AI in my work, or what should I keep doing myself. Produces a sort of your tasks into delegate-fully / delegate-with-review / keep-human, the reasoning behind each line, how to brief the AI on the delegated ones, and where your judgment is the actual value — a delegation map that frees your time without giving away your edge.

Delegate so the work comes back right the first time — the brief that transfers outcome, context, and constraints (not just the task), the autonomy level stated explicitly, and the check-in design that catches drift without hovering. Use when asked hand this off properly, my delegations come back wrong, write a brief for this task I'm giving away, or how much detail do I give. Produces the delegation brief with the outcome and guardrails, the autonomy level, the check-in points, and the questions-welcome contract.

Design deliberate practice that actually builds a skill — targeted, effortful, feedback-driven — instead of mindless repetition that just entrenches your current level. Use when asked how do I practice X effectively, my practice isn't working, design a practice routine, or deliberate practice for. Produces a breakdown of the skill into trainable sub-skills, drills that target your specific weaknesses at the edge of your ability, a feedback mechanism, and a session structure — because time spent practicing is not the same as time spent improving.

Make a recurring brief report what changed since the last edition instead of restating everything. Use when a weekly or monthly report keeps repeating itself, when setting up a scheduled monitor or digest, or when asked to make a recurring update delta-aware. Produces a changes-first brief plus the state record the next run will diff against.

Interrogate a demand forecast before the business commits supply and inventory to it. Use when asked to review a demand plan, challenge a forecast, check forecast accuracy, decompose baseline vs uplift, or find hockey sticks in the numbers. Produces a forecast credibility review with baseline/uplift decomposition, MAPE and bias history, hockey-stick flags, an assumption register, and consensus-vs-statistical divergence analysis.

Draft a firm, professional demand letter that states the facts, the legal/contractual basis, the specific demand, and a deadline. Use when asked to write a demand letter, send a formal demand for payment, draft a cease-and-desist, or formally request resolution before legal action. Produces a structured, factual letter with a clear ask and consequences — assertive but not threatening or defamatory. Not legal advice; have counsel review before sending.

Script a product demo that lands — the audience's-workflow storyline (their day, not your feature list), the golden path rehearsed with fallbacks, the wow moment placed early, and the demo-death contingencies (the backup video, the reset state, the narration bridge). Use when asked script our product demo, demo this to a customer/exec, our demos meander through features, or the demo broke live last time. Produces the demo storyline, the click-path script with fallbacks, the wow placement, and the contingency kit.

Audits project dependencies for security vulnerabilities, license compliance issues, outdated packages, and transitive dependency risk. Use when asked to audit dependencies, review package security, check license compliance, assess dependency health, or produce a vulnerability report. Produces a vulnerability findings table, license compliance matrix, update priority matrix, dependency health score, and 30-day remediation plan.

Honestly measure how dependent you've become on a tool, app, substance-free habit, or even AI itself — and reclaim the capability you've outsourced. Use when asked am I too reliant on, help me check my dependence on, could I function without, or I feel like I can't do anything without X. Produces a candid read on where the reliance actually is, a low-stakes test to measure it (go without, briefly), what capability has atrophied, and a plan to rebuild the muscle — because unmeasured dependence is the dangerous kind, and the fix starts with noticing.

Resolve a dependency or version conflict (npm, pip, yarn, pnpm, Maven, Go modules) step by step. Use when an install fails with peer-dependency or version-conflict errors, packages won't co-exist, or a lockfile is fighting you. Produces the conflict explained, the resolution options ranked by safety, exact commands, and how to keep it from recurring.

Plan the communications for deprecating a product, API, endpoint, or feature that customers depend on. Use when winding down or sunsetting something, planning a breaking change, or migrating customers off a legacy path. Produces a staged timeline with grace periods, tiered customer messaging, a migration-guide outline, the channel plan, and an internal escalation playbook for the highest-risk accounts. This is the customer-communications program — distinct from [[feature-sunset-plan]] (the kill decision, data handling, and code removal) and [[api-versioning-strategy]] (the technical versioning mechanics).

Give structured, constructive feedback on any design using UX frameworks. Use when asked to critique a design, review a UI, give feedback on a Figma file or wireframe, assess a user flow, or evaluate a design against UX principles. Produces actionable critique applying Jobs-to-be-Done, Gestalt principles, and usability heuristics, with prioritised issues and specific recommendations.

Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context, success criteria, constraints, edge cases, and out-of-scope boundaries.

Audit a design system for consistency, coverage, and quality. Use when asked to audit a design system, review a component library, assess design token coverage, or evaluate the health of a shared design system. Produces a structured audit with a health score, component coverage gaps, token inconsistencies, accessibility issues, and a prioritised remediation roadmap.

Generate a complete, accessibility-checked design system from scratch — colour ramps, type scale, spacing, elevation, and exports for CSS, Tailwind, design tokens, Figma, VS Code and PowerPoint. Use when asked to create a design system, pick a colour palette, build a starter theme, produce design tokens for a new product, or apply an existing brand colour to a full system. For auditing a system that already exists use design-system-audit; for extracting one from a live site use brand-guidelines.

Audit your desk setup and fix what's hurting your neck, back, wrists, or eyes — with specific, mostly-free adjustments before you buy anything. Use when asked to check my desk setup, ergonomics help, my [wrists/neck/back] hurt from my desk, or how to set up my workstation. Produces a point-by-point setup check (chair, screen, keyboard, mouse, lighting), the specific fixes ranked free-first, cheap upgrades only if needed, and micro-break habits — with a 'see a professional for persistent pain/numbness' flag.

Run a timeboxed desk-research sprint that ends with an answer instead of forty tabs — the question decomposition, the source plan by question type, the capture discipline that prevents re-reading, and the stop rule that beats completionism. Use when asked research this market/tool/topic by Friday, I have two hours to get smart on X, structure my desk research, or I keep researching and never concluding. Produces the decomposed questions, the source plan, the capture format, and the timeboxed synthesis with confidence labels.

Clear the desktop that's become a hundred-icon guilt mosaic — the fast triage that empties it today, the honest read of what the desktop was being used for (it's a to-do list wearing icons), and the replacement systems that keep it clear. Use when asked clean up my desktop, my desktop has 200 files on it, why does my desktop keep filling up, or set up a clean-desktop habit. Produces the today-pass, the function-replacement mapping, and the two-minute weekly habit.

Write a developer onboarding document for a service, codebase, or team. Use when asked to write a developer guide, service README, onboarding doc for a new engineer, codebase orientation, or getting-started guide for a technical team. Produces a structured doc covering service overview, architecture, local setup, key patterns, testing, deployment, and who to ask for what.

Argue hard against whatever you just concluded — so your decision has to survive a real challenge instead of an echo chamber. Use when asked to play devil's advocate, argue against this, challenge my conclusion, or talk me out of it. Produces the strongest case against your position, the uncomfortable questions you're avoiding, the evidence that cuts the other way, and an honest read on whether your conclusion survives the challenge — deliberately countering the 'that's a great idea!' agreement bias.

The strongest possible case AGAINST what you just wrote — argued to win, not to check a box. Use when a document is about to ship and everyone around it already agrees: the twin writes the opposition's best memo (not a critique of yours), so you meet the real counter-argument before your audience does. Produces the opposing memo, the map of which of your claims it defeats/dents/leaves standing, and the pre-emption paragraph worth adding.

Run the multi-year campaign of being chronically ill with no diagnosis — track patterns across specialists so nothing resets, avoid the 'it's just anxiety' dead-end, chase referrals that stall, and arrive at each new doctor with the longitudinal case instead of starting from zero again. Use when someone says 'I've been sick for years and no one can tell me why', 'every specialist starts over', 'they keep saying it's stress', or is stuck in diagnostic limbo. Produces a longitudinal symptom dossier, a specialist-handoff brief, and a next-move plan. Not medical advice — it organizes YOUR information so clinicians can use it.

Look up word definitions, pronunciation, etymology and synonyms with zero API keys — the Free Dictionary API via curl, with honest handling of words it doesn't know. Use when asked define a word, how do you pronounce this, what's the origin of a word, or synonyms for something. Produces the definition set organized by part of speech, IPA pronunciation with audio link, and the rerunnable command — with the model's own knowledge clearly separated from the fetched source.

Prepare for and script a hard conversation — conflict, bad news, a boundary, an apology. Use when asked to prepare for a difficult conversation, address a conflict, deliver bad news, confront a colleague, or have a hard talk with a manager/report/peer. Produces a prep brief — the real goal, the other side's likely view, an opening line, the key points, anticipated reactions with responses, and the outcome you want.

Plan what happens to your digital life when you die — accounts, photos, passwords, money, and social profiles — so someone you trust can actually find, access, memorialize, or close them without a legal nightmare. Use when someone says 'what happens to my accounts when I die', 'digital legacy', 'help my family access my stuff if something happens', or is doing estate planning and forgot the online half. Produces a digital asset inventory, an access plan using built-in legacy tools, and instructions for your person. Not legal advice — pairs with a real will.

Plan what happens to your digital life — the account inventory, the access plan that doesn't violate terms or law, platform legacy settings, and the memorialize/delete/preserve decisions, written down while it's easy. Use when asked what happens to my accounts when I die, set up a digital legacy plan, help an executor deal with online accounts, or how does my family get into my stuff. Produces the tiered inventory, the legal-access setup (password-manager emergency access + platform legacy tools), the wishes document, and the executor's digital checklist.

Appeal a denied disability benefit (SSDI/SSI, PIP, DLA, ESA and similar) — decode the denial reason, build the evidence-backed case that answers it, hit the deadline, and prepare for the hearing. Use when someone says 'my disability benefit was denied', 'appeal my PIP/SSDI decision', 'they said I don't qualify', or 'how do I challenge a benefits decision'. Produces a decoded denial, an appeal strategy mapped to the criteria, an evidence checklist, and a statement draft. Not legal advice — it organizes YOUR case and routes to free specialist advice.

Decide whether, when, how, and to whom to disclose a disability or health condition at work — weighing the real benefits (accommodations, protection, honesty) against the real risks (bias, gossip), tuned to your specific situation. Use when someone says 'should I tell work about my disability/condition', 'disclose my ADHD/chronic illness at work', 'when do I tell my employer', or 'how much do I share'. Produces a decision framework for the situation, a disclosure script if you choose to, and the minimum-disclosure options. Your choice throughout; it never pushes disclosure.

Decode a disability insurance policy or employer LTD plan — own-occupation vs any-occupation, the benefit math after offsets and taxes, and the definitions that decide whether it pays. Use when someone asks 'is my disability insurance any good', 'decode my LTD policy', 'what does own-occupation mean', or 'how much would I actually get'. Produces a definition decode of the clauses that decide claims, the real benefit math after offsets, ranked red flags, and the questions to ask before relying on the coverage.

Write a disaster recovery plan for a service or system — covering RPO/RTO targets, failure scenario runbooks, backup and restore procedures, DR testing cadence, and communication templates. Use when asked to write a DR plan, document failover procedures, create recovery runbooks, define RTO/RPO targets, or prepare for a disaster recovery game day. Produces a full DR document with per-scenario recovery runbooks, backup validation procedures, testing schedule, and communication templates.

Turn a hospital stay into a complete, well-structured discharge summary. Use when asked to write a discharge summary, a hospital discharge note, or to document a patient's admission-to-discharge course for handoff. Produces a standard discharge summary — admission reason, hospital course, diagnoses, procedures, discharge medications, condition, and follow-up/return precautions — from the provided details.

Prepare a structured discovery call plan for any prospect. Use when asked to prepare for a sales call, discovery call, prospect meeting, or first call with a potential customer. Produces a call brief with research, hypotheses, questions, and success criteria.

Read your team's messages the way opposing counsel would in litigation discovery — prevention training that makes communication hygiene visceral. Use when asked how would our Slack look in discovery, train my team on communication hygiene, review this thread like a plaintiff's lawyer, or what shouldn't we put in writing. Produces the highlighted-exhibit reading of sample messages, the patterns that create legal risk, and a debrief with the write-it-this-way rules — strictly for prevention, never for concealment.

Create a structured user discovery interview guide with screener questions, a discussion guide, and a synthesis framework. Use when planning user interviews, customer discovery sessions, Jobs-to-be-Done research, or problem validation. Produces a complete guide covering warm-up, problem exploration, and a per-session synthesis template.

Write a letter to dispute an incorrect charge, bill, or record. Use when asked to dispute a credit-card charge, contest a bill or invoice, challenge a credit-report error, or formally dispute a fee. Produces a clear dispute letter — what's being disputed, why it's wrong, the evidence, and the correction requested — in the firm, paper-trail tone these situations need.

Query DNS records and domain registration data with zero API keys — DNS-over-HTTPS via dns.google and domain registration via RDAP, through plain curl. Use when asked what does this domain resolve to, check the MX or TXT records, who registered this domain, when does it expire, or has DNS propagated. Produces the records decoded (SPF/DKIM/DMARC read, not just dumped), the registration facts from RDAP, and the rerunnable commands.

Restructure the user's REAL Google Doc — open it, tighten and reorganise it, and return a clean version — not advice on how to edit it. Use when asked to clean up this doc, restructure my draft in Drive, make this readable, or tighten the doc for review in Cowork. Reads the document via the Google Drive/Docs connector, applies a structure-and-concision pass (BLUF, one idea per section, cut the filler), and produces a restructured-document artifact plus a change summary — as a new copy, never overwriting the original.

Keep living documents trustworthy over time — the status header (draft/active/superseded) that tells readers what they're holding, the change-log-for-decisions inside the doc, the supersession chain that kills zombie versions, and the review-date heartbeat. Use when asked which version of this doc is current, our wiki is full of stale pages, set up doc lifecycle rules, or people keep following the old process doc. Produces the status-header standard, the in-doc change log, the supersession protocol, and the staleness heartbeat.

Write a 'get started in 5 minutes' quickstart for a tool, library, or API. Use when asked to write a quickstart, getting-started guide, or onboarding docs for developers. Produces a copy-paste-friendly quickstart that takes a developer from zero to a first working result fast, with install, a minimal working example, and clear next steps.

Prepare for a doctor's appointment so the 12 minutes actually get used — the symptom timeline in the format clinicians think in, the prioritized question list, and the advocacy scripts for being heard. Use when asked help me prepare for my doctor appointment, what should I tell my doctor, organize my symptoms, or I always forget what to ask. Produces the one-page visit sheet: symptom history with timeline, medications, the top-3 questions, and the phrases that get concerns taken seriously.

Decide what documents to keep, for how long, and where — the personal/small-biz retention map by category (tax, legal, medical, warranties, employment), jurisdiction-flagged periods, and the destruction discipline for what's past its date. Use when asked how long do I keep tax documents, can I shred this, set up a document retention system, or what papers does my small business need to keep. Produces the category map with keep-periods (flagged verify-locally), the keep-forever list, the digitize rules, and the annual purge ritual.

Write a warm donor update or stewardship message that makes a supporter feel their gift mattered. Use when asked to write a donor update, a thank-you/stewardship email, a supporter newsletter, or a gift acknowledgement. Produces a donor-centred update — sincere thanks, the specific impact of their support, a brief story, and a light, optional next step — that strengthens the relationship and sets up the next gift.

Make introductions that respect both sides — the double-opt-in flow (ask each party privately before connecting them), the forwardable blurb that makes saying yes easy, and the connecting email that sets both up to succeed. Use when asked introduce me to someone, can you connect us, write an intro email, or someone asked me for an intro. Produces the opt-in asks for both sides, the forwardable blurb, the intro email itself, and the graceful decline path.

Empty the Downloads folder that's become a junk drawer — the four-bucket pass (file, delete, action, quarantine), the age-based bulk rules that make 2,000 items tractable, and the tiny habit that keeps it empty. Use when asked clean up my downloads folder, 2000 files in downloads help, what's safe to delete here, or stop my downloads from piling up. Produces the bucket pass with bulk rules, the safe-delete classes, the keeper-filing routes, and the weekly sweep habit.

Respond fast and safely if your personal information has been exposed or you're being doxxed — contain the spread, protect your safety and accounts, and report it. Use when asked what to do if I've been doxxed, someone posted my personal info, my address is being shared online, or I'm being targeted online. Produces an immediate safety-and-containment checklist, takedown/report steps for the platforms hosting the info, account and physical-safety hardening, an evidence-preservation step for authorities, and escalation to police/support when there are threats. Not legal advice.

Read a Data Processing Agreement before you sign it — sub-processors, transfer mechanism, breach-notice window, deletion, audit rights — in plain language with 🔴🟡🟢 risk. Use when asked to review a DPA, check a data processing agreement, is this DPA safe to sign, or what am I agreeing to on data. Produces the plain-English summary, the risk-ranked findings, the missing-clause checklist, and the questions to send back before signature.

Check recent earthquakes worldwide with zero API keys — USGS real-time GeoJSON feeds via curl, filtered by magnitude, region, and time window. Use when asked was there an earthquake just now, recent quakes near a place, any big earthquakes today, or monitor seismic activity somewhere. Produces the matching events with magnitude, depth, location and time, the felt/damage context bands, and the rerunnable command — with the official-guidance line safety questions require.

Protect aging parents from the scams that target them — the conversation that doesn't condescend, the family code word, the top patterns aimed at seniors, and the guardrails that help without taking over. Use when asked how do I talk to my parents about scams, my mom almost sent money to someone, set up scam protection for my dad, or what scams target the elderly. Produces the briefing conversation script (dignity-first), the household defenses, the pattern one-pager to leave behind, and the if-it-already-happened response.

Write to an elected representative in a way that actually gets action — a specific ask, your local stake, why it's in their interest to respond, and the follow-up — instead of an angry email that gets auto-filed. Use when someone says 'write to my MP/congressperson/councillor', 'contact my representative about X', 'how do I get my rep to act', or 'my letter to the council got ignored'. Produces a targeted letter (or call script), tuned to the right representative and level of government, plus a follow-up plan.

Run the pre-flight checklist before an agent touches an inbox — the read-vs-send permission line, the injection-in-email-body threat, the send-guard rules, and the blast-radius limits that keep a compromised agent from mailing the company. Use when asked let my agent read/send email safely, set up guardrails before the agent touches my inbox, is it safe to give the agent email access, or review my email agent's permissions. Produces the permission tier, the injection defenses, the send-gate rules, and the incident kill-switch.

Write and sequence multi-email nurture or launch campaigns. Use when asked for an email sequence, drip campaign, onboarding emails, product launch emails, or nurture flow. Produces subject lines, preview text, full email body, and send-timing recommendations for each email in the sequence.

Write a multi-email nurture/onboarding/launch sequence with a goal per email. Use when asked to write an email sequence, a welcome/onboarding series, a nurture drip, a launch sequence, or a re-engagement series. Produces the sequence map (trigger, timing, goal per email) plus the full copy for each email — subject, body, and one CTA — designed to move the reader one step at a time.

Convert an email (or a whole thread) into real tasks — the actual asks extracted from the prose, each with owner, deadline, and the done-test, so nothing lives in the inbox as its own reminder. Use when asked what am I actually being asked to do here, turn this thread into a task list, extract the action items from this email, or I keep re-reading this thread. Produces the ask extraction with quoted sources, the task list in owner-verb-deadline form, and the reply that confirms the commitments.

Triage a Gmail inbox down to only what needs you. Use when asked to triage email, clear an inbox, find what needs a reply, or summarise recent mail. Produces a prioritised list of items needing action — replies, decisions, follow-ups — for a configurable window (default last 8 hours), filtering out receipts, notifications, and newsletters.

Turn an overflowing inbox into a four-verb system — archive, reply-now, task, or park — with the two-minute rule enforced and a daily cadence that survives busy weeks. Use when asked help me get to inbox zero, my email is out of control, build me an email triage system, or process this backlog. Produces the triage pass on the actual inbox, the four-verb rules, the folder/label minimal set, and the daily cadence.

Assemble the grab-and-go document and information kit for a disaster — the IDs, insurance, medical, financial, and property records (physical copies + secure digital backups) you'd need to prove who you are, get aid, and rebuild after a fire, flood, or evacuation. Use when someone says 'what documents for an emergency', 'important papers for a disaster', 'emergency document checklist', or 'what would I need if my house burned down'. Produces a documents checklist, a physical + digital storage plan, and the info that isn't a document (contacts, med lists). Pairs with the go-bag.

Size an emergency fund from essential spend and real risk factors — not a one-size 'six months' — with the funding timeline and where the money should sit. Use when asked how big should my emergency fund be, do I have enough saved, emergency fund or invest, or how many months of expenses do I need. Produces the risk-adjusted target from the script, the essential-spend worksheet, the funding plan, and the what-counts-as-an-emergency rules.

Design an employee engagement survey and analyse results. Use when asked to create an employee survey, engagement questionnaire, pulse survey, or eNPS survey. Also use when asked to analyse survey results. Produces a complete survey with questions, rating scales, and an analysis framework.

Write empty-state content that turns a blank screen into a next step. Use when asked to write an empty state, a zero-data / first-run state, a no-results state, or onboarding placeholder content. Produces empty-state copy — a clear headline, a helpful line, and a primary action — for each type (first-use, user-cleared, no-results, error/permission), so a blank screen guides instead of confuses.

Have the conversation about someone's end-of-life wishes — before a crisis forces it — gently, respectfully, and thoroughly enough to actually guide decisions later. Use when asked how do I talk about end-of-life wishes, discuss my parent's wishes, advance care planning conversation, or ask about their medical and final wishes. Produces a way to open this hard conversation without it feeling morbid or forced, the areas to cover (medical wishes, care preferences, where they want to be, what matters to them, practical/legal), how to listen rather than impose, and how to document and share what's decided — so their wishes are known and honored. Not legal or medical advice.

Schedule work by energy, not just time — the week of self-observation that maps your real peaks and troughs, the work-to-energy matching (hard creative work on peaks, admin on slopes, meetings on shoulders), and the calendar rebuild that honors the map. Use when asked when should I do my hardest work, I waste my best hours on email, map my energy levels, or why is 3pm always useless. Produces the observation protocol, the personal energy map, the work-type matching, and the rebuilt week.

Run a close-out retrospective on a client engagement — capture lessons, results, and the renewal/referral path. Use when asked to wrap up a client project, run an engagement retro, write a project close-out, or plan the follow-on. Produces a close-out — outcomes vs. goals, what worked / what didn't, profitability/scope reality, a reusable lessons log, and the next-engagement or referral ask.

Build an engineering hiring rubric and technical interview scorecard for evaluating software engineers at a specific level. Use when asked to create an interview rubric, design a hiring process, build a technical scorecard, or standardize engineer evaluation. Produces a full interview scorecard, behavioral question bank, technical question set with evaluation criteria, system design rubric, and debrief agenda.

Write a weekly engineering status report for a team, service, or initiative. Use when asked to write a team update, weekly engineering report, sprint status email, or standing team communication to stakeholders. Produces a concise, scannable weekly report covering shipping progress, metrics, decisions, blockers, and next-week priorities.

Turn a data model into an entity-relationship (ER) diagram. Use when asked to design a schema, model data, show how tables/entities relate, or diagram a database. Produces a ready-to-render Mermaid ER diagram (renders live, exportable as PNG/SVG) plus key attributes, cardinality, and design notes.

Report on an epic or initiative deeper than a status bullet — child work broken down by status, the riskiest unfinished pieces, and honest suggested cuts to hit the date. Use when asked for an epic progress report, where are we on this initiative, break down epic status, or what can we cut to ship on time. Produces the completion picture by child status, the critical-path and riskiest remaining work, a scope-cut menu with impact, and a straight call on whether the target date is realistic.

Decode an error message or stack trace into a plain-English cause, the exact fix, and how to prevent it. Use when asked to explain an error, debug a stack trace, figure out why code is throwing, or make sense of a cryptic exception. Produces a structured diagnosis: what the error means, the most likely cause, a concrete fix with code, and a prevention tip.

Write clear, helpful error messages that tell users what happened and how to fix it. Use when asked to write an error message, validation text, a failure/empty-error state, or to rewrite a cryptic system error. Produces human, blame-free error copy — what went wrong, why (if useful), and the next step — with options per surface (inline, toast, full page) and the related success/empty states.

Escalate an issue up the chain without burning the person you're escalating past — the facts-first structure, the tried-already section that earns the escalation, and the specific ask that makes action easy. Use when asked I need to escalate this, write an email to my boss's boss, this vendor issue needs to go up, or how do I go over someone's head professionally. Produces the escalation email with its evidence spine, the pre-escalation courtesy step, and the relationship-preserving framing.

Design a support/incident escalation tree — who handles what, when it escalates, and to whom. Use when asked to design an escalation path, an escalation matrix, support tiers, an on-call escalation policy, or to fix 'tickets bounce around / nothing gets escalated in time'. Produces an escalation tree — tiers & ownership, severity definitions, time-based triggers, routing rules, contacts/roles, and the customer-communication cadence per level.

Draft an honest, audit-ready ESG disclosure section in a CSRD/ESRS-flavored structure, adaptable to other frameworks. Use when asked to write a sustainability report section, draft an ESRS or CSRD disclosure, prepare an ESG section for an annual report, or turn raw sustainability data into disclosure text. Produces a disclosure draft with double-materiality framing, metric-methodology-limitation triplets, based forward statements, and explicit data-gap handling.

Get your affairs in order before you need to — a will/beneficiary/healthcare-directive checklist and the 'what my family needs to find' document, in the right order. Use when asked to help with estate planning, make a will checklist, get my affairs in order, or prepare what my family needs if something happens to me. Produces the estate-planning checklist ranked by priority, the document-locator sheet, the key decisions to make, and the professional-help flags — for the living, not the executor. Complements the estate/after-death pack.

Organize an executor's work — the settlement ladder from will-to-probate-to-distribution, the asset/debt inventory, the creditor and beneficiary communications, and the records that keep an executor protected. Use when asked I'm the executor what do I do, organize settling an estate, what's the probate process roughly, or track estate assets and debts. Produces the phased task ladder (jurisdiction-flagged), the inventory workbook structure, communication templates, and the executor's self-protection rules.

Write a eulogy or obituary for someone you loved when you're grieving and the words won't come — a true, warm piece that sounds like them and like you. Use when asked help me write a eulogy for my father, write an obituary, I have to speak at the funeral, or I don't know what to say about them. Produces a eulogy or obituary drafted from your memories (not clichés), the right structure and length for the setting, the specific stories and details that make it theirs, guidance on tone and delivery (including reading it aloud through tears), and what to include in an obituary (facts, survivors, service details) — so you can honor them well without facing the blank page alone. Written in your voice from your memories.

Help someone write a eulogy — the hardest writing most people ever do, at the worst possible time. Use when someone must speak at a funeral or memorial and doesn't know where to start, or has fragments and no shape. Produces a 3-5 minute eulogy built from their memories in their voice, plus a delivery copy formatted for shaking hands — gentle process, no interrogation, nothing invented.

Guide a veterinary team through a compassionate end-of-life conversation with a pet owner — quality-of-life assessment, the recommendation, and the logistics. Use when asked to help discuss euthanasia, assess quality of life, prepare for a difficult end-of-life conversation, or support an owner facing the decision. Produces a quality-of-life framework, empathetic language for the conversation, how to answer the hard questions (is it time, will it hurt, should the kids be there), and the practical steps (the process, aftercare options, grief support).

Compare an EV against a comparable gas car on total cost — upfront gap after incentives, energy vs fuel per year, maintenance delta, and the crossover year when the EV pulls ahead (or doesn't). Use when asked is an EV worth it, EV vs gas total cost, when does an EV pay for itself, or should my next car be electric. Produces the year-by-year cumulative comparison from the script, the crossover year, the per-mile energy math, and the honest not-modeled list.

Design a scoring rubric and LLM-as-judge prompt to evaluate the quality of an AI feature's output. Use when asked to create an eval rubric, define quality dimensions, build an LLM judge, or decide how to measure whether AI output is good. Produces a rubric with weighted dimensions and concrete 1–5 anchors, a ready-to-run judge prompt, a labelling guide, and notes on judge reliability.

Grade the evidence behind a claim before betting on it — the hierarchy for business evidence (experiments > usage data > surveys > interviews > anecdotes > opinion), the fit-for-decision test, and the mixed-evidence verdicts that real questions produce. Use when asked how strong is our evidence for this, grade what we know before the decision, is this enough to bet on, or we have three anecdotes and a survey — now what. Produces the evidence inventory with grades, the sufficiency verdict against the decision's stakes, and the cheapest-upgrade path.

Write or rewrite a document in evidence-locked mode: no unsourced sentences — every substantive claim carries a footnote citing the exact passage in the user's provided sources, and anything unsupportable is explicitly marked. Use when asked to make a document fully sourced, add citations from my docs, ground a draft in the attached material, or produce something for audiences that will check (legal, board, regulators, enterprise buyers). Produces the document with numbered citations, a source map quoting each cited passage, and an unsupported-claims register.

Run an NPI phase-gate review for EVT, DVT, or PVT — exit criteria per phase, open-issue triage, yield readout, waiver discipline, and a go/no-go call. Use when asked to run a gate review, decide EVT exit or DVT entry, review build results, assess whether to proceed to the next build, or triage open issues before a phase gate. Produces a gate review document with criteria scoring, waiver register, yield analysis, and a defensible go/conditional-go/no-go recommendation.

Build a realistic exam-prep schedule with spaced repetition and retrieval practice — the plan that survives contact with an actual week. Use when asked to plan my exam prep, make a study schedule, I have N weeks until finals, or how do I study for multiple exams. Produces a day-by-day plan across all exams: spaced blocks, retrieval-first sessions, weak-topic weighting, and built-in slack for the days that go wrong.

Build a backward-planned study schedule for an exam — using proven learning methods, not just re-reading — so you cover what matters and actually retain it. Use when asked to make a study plan, help me study for [exam], I have an exam in [time], or how do I revise. Produces a week-by-week plan working back from the exam date, prioritized by weighting and your weak spots, sessions built on active recall and spaced repetition, past-paper/practice integration, and a realistic pace with breaks — not an unsustainable cram that forgets everything by exam day.

Build a real, formula-driven Excel (.xlsx) model — not a static table. Use when asked to build an Excel model, a financial model, a budget/forecast spreadsheet, or any .xlsx with live formulas a user can edit. Produces an actual .xlsx file via a generated openpyxl script: an inputs/assumptions sheet, calculation sheets with real cell formulas, and formatting — so changing an input recalculates the model. Requires a code-execution environment (Claude Code, the API code tool, or Claude.ai).

Stop presenting the working deck to executives — the two-deck split (answer-first exec cut vs. exploration-rich working deck), the compression rules from 40 slides to 8, and the appendix strategy that keeps the depth one click away. Use when asked turn this analysis into an exec version, my leadership readout went badly, how do I compress 40 slides to 10 minutes, or what do execs actually want in a deck. Produces the exec cut with the answer-first order, the compression map (what survived, where the rest went), and the Q&A appendix plan.

Execute a written plan with discipline — verify each step before advancing, surface deviations instead of improvising around them, and keep a visible execution log. Use when working through a plan (yours or another agent's), resuming multi-session work, or when execution keeps drifting from what was agreed. Produces completed work plus an execution log showing what matched the plan, what deviated and why, and what the plan got wrong. Pairs with writing-plans.

Sharpen how you show up in high-stakes rooms — communicate with gravitas, concision, and confidence. Use when asked to improve executive presence, prepare to present to leadership, sound more senior, command a room, or get coaching before a big meeting. Produces specific guidance — how to open, structure answers (BLUF/headline-first), handle tough questions, project calm, and the habits to drop, tuned to the moment.

Write an executive summary for any document, report, or proposal. Use when asked to write an executive summary, management summary, briefing paper, or one-pager for senior stakeholders. Produces a structured summary that busy executives can read in under 3 minutes and act on.

Transform detailed product updates into concise executive briefings. Use when asked to write an executive update, leadership update, product update for the exec team, or a C-suite product briefing. Produces a structured 250-word briefing with headline, key metrics, progress, risks, decisions needed, and next steps.

Walk into an exit interview knowing what it's for, what to say, and what to keep — honest-but-strategic answers that protect references and leave the door open. Use when asked what do I say in my exit interview, should I be honest in my exit interview, prep me for my exit interview, or is the exit interview confidential. Produces the goals-and-risks brief, prepared answers for the standard questions, the say/soften/skip sorting of your real feedback, and the scripts for the questions that are traps.

Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses. Use when asked to model an exit waterfall, what do I get if we sell for X, explain liquidation preferences on my cap table, or compare payouts across exit prices. Produces a per-stakeholder payout table across exit values with conversion decisions shown, plus the plain-English reading of what the structure means for each party.

Audit spending to find leaks — recurring subscriptions, creep, and cuttable costs — ranked by impact. Use when asked to cut expenses, review subscriptions, find where money is going, or free up cash. Produces a categorized spend breakdown, a ranked list of cuts with dollar amounts, and the annualized savings. Educational, not regulated financial advice.

Submit expenses that sail through approval — the capture-at-spend habit, the policy-fluency that prevents rejections (thresholds, receipt rules, the pre-approval traps), the report assembled in minutes, and the approver-side rules for reviewing fairly and fast. Use when asked my expense reports are always late or rejected, set up my expense workflow, what does the policy actually require, or review expenses as a manager without being a receipt cop. Produces the capture habit, the policy crib, the submission routine, and the approver's rubric.

Turn a pile of receipts into a filed expense report through a tool-using agent — extraction, policy checks, and categorization done for you; submission gated on your approval. Use when asked to file my expenses, process these receipts, build my expense report, or expense this trip. Produces the itemized report with policy flags and an approval-gated filing plan.

Write a clear company expense & reimbursement policy. Use when asked to write an expense policy, a reimbursement policy, a travel & expense (T&E) policy, or spending guidelines. Produces a practical policy — what's covered, limits by category, the approval and submission process, timelines, and what's not reimbursable — that's fair, easy to follow, and reduces finance back-and-forth. Not tax/legal advice.

Design an expense-tracking sheet that survives real receipts — the capture-at-spend habit, the category set that matches reimbursement or tax rules, the receipt-link discipline, and the month-end close that takes minutes because the work happened at spend-time. Use when asked track my business expenses, build an expense sheet for the team, get ready for reimbursement/tax season, or my shoebox of receipts needs a system. Produces the sheet structure, the capture ritual, the category mapping to the real downstream rules, and the month-end close.

Design statistically rigorous A/B tests and interpret experiment results. Use when asked to design an experiment, run an A/B test, calculate sample size, interpret test results, or assess whether an experiment was successful. Produces a complete experiment design with hypothesis, sample size, run time, success criteria, and risk flags — or a results interpretation with ship/iterate/kill recommendation.

Analyse a finished A/B test and write an honest results readout with real statistics. Use when asked to read out an A/B test, analyse experiment results, check if a result is statistically significant, or decide ship/no-ship from test data. Produces a readout — the computed lift, p-value & confidence interval, a significance verdict, guardrail check, and a clear ship / no-ship / iterate recommendation. Includes a stdlib significance calculator.

Get the most from an hour with an expert — the do-your-homework floor (never ask what's googleable), the question arc from calibration to the frontier, the follow-up discipline that goes deep instead of wide, and the capture that survives the call. Use when asked prep me for the expert call, what should I ask this advisor/analyst/practitioner, we get an hour with X, or our expert calls are pleasant but shallow. Produces the homework brief, the question arc, the follow-up toolkit, and the capture plan.

Talk through a decision out loud with a patient thinking partner that reflects your reasoning back, so the answer you already half-know becomes clear. Use when asked help me think this through, I need to talk this out, be my sounding board, or I don't know what I actually think. Produces a structured reflection of your own reasoning — what you've actually said, the values driving it, the contradictions and gaps, and the question that would clarify it — acting as a rubber-duck / sounding board rather than handing you an answer you didn't reach yourself.

Explain anything in plain language — a contract clause, a medical term, a tax rule, a tech acronym, a news story — layered from a one-liner to as much depth as you want. Use when asked to explain like I'm 5, explain this simply, break this down in plain English, or what does this even mean. Produces the one-sentence version, a plain-language explanation with a concrete analogy, the 'why it matters to you,' and an honest note on anything genuinely uncertain or oversimplified.

Write session-based exploratory testing charters to find what scripted tests miss. Use when asked to plan exploratory testing, write a test charter, design a testing session, or do risk-based exploration of a feature. Produces focused charters — a mission, areas/risks to explore, tactics and oracles, and timeboxed sessions — so exploration is purposeful and accountable, not random clicking.

Figure out whether your record can be sealed or expunged, and map the steps to do it — eligibility, waiting periods, forms, and where to get help. Use when asked can I get my record expunged, how do I seal my criminal record, clear my background, or am I eligible for expungement. Produces a plain-language read on likely eligibility (offense type, dispositions, waiting periods), the document and step sequence to petition, the costs and fee-waiver options, the realistic timeline, and where to get free or low-cost legal help — so a record that can be cleared actually gets cleared. Not legal advice; expungement law is highly jurisdiction-specific and this points you to the right help.

Run a claim-by-claim fact-check pass on a draft article, script, or report before publication. Use when asked to fact-check a piece, verify claims before publishing, or do editorial verification. Produces a claim inventory (every checkable assertion pulled out), a verification status and source for each (confirmed / needs sourcing / unverifiable / wrong), the fixes, and a flag on the high-risk claims (numbers, quotes, names, legal/defamatory statements) that must not go out unverified.

Write a factory acceptance test (FAT) plan or report — test coverage matrix against spec, AQL sampling plan, pass/fail criteria, golden-sample handling, deviation log, and sign-off structure. Use when asked to write a FAT plan, define outgoing quality inspection, set AQL levels, prepare for a factory acceptance or pre-shipment inspection, or document FAT results. Produces a complete FAT plan or report with sampling tables, defect classification, and a sign-off block.

Navigate questioning, leaving, or changing your religion — especially a high-control or all-encompassing one — with the relationship-preservation scripts for family who stayed, a way to grieve the community and certainty you're losing, and support for rebuilding meaning. Use when someone says 'I'm losing my faith', 'I left my religion and my family is devastated', 'religious deconstruction', 'how do I tell my believing parents', or is leaving a high-demand group. Produces conversation scripts, a grief-and-identity map, and a rebuilding plan. Not persuasion in any direction, and not therapy — a companion for a hard passage.

Build a family emergency plan — contacts, meeting points, key documents, and 'if something happens to me' info — so your household isn't scrambling in a crisis. Use when asked to make a family emergency plan, be prepared for an emergency, what if something happens to me, or organize our important info. Produces a household plan covering communication and meeting points, an emergency contact/ICE setup, a key-documents and info location list, a basic go-bag/supplies checklist, and a 'someone needs to find this' plan — tailored to your household and likely local risks.

Build a fantasy-sports draft strategy and weekly plan that fits your league's exact settings — so you draft with a plan instead of vibes. Use when asked to help with my fantasy draft, who should I draft, fantasy league strategy, or set my lineup this week. Produces a settings-aware draft approach (positional strategy by round, tiers over rankings, targets and values), a snake/auction plan for your slot, weekly start/sit and waiver logic, and honest reminders that player values shift — verify current status before locking anything in.

Build an FAQ from the questions people actually ask — mined from tickets, chats, and repeated explanations, answered once and well, organized by the asker's words, and maintained by a capture loop instead of annual archaeology. Use when asked create an FAQ for this product/process/team, I answer the same questions weekly, turn our support threads into docs, or why does nobody find our answers. Produces the mined question list with frequencies, the answers in ask-language, the structure, and the capture loop.

Write a feature flag management guide and lifecycle playbook for a service or team — covering flag taxonomy, creation checklist, rollout strategy, monitoring requirements, cleanup policy, and governance. Use when asked to document feature flag practices, create a flag rollout plan, write a feature flag policy, or guide a team on flag lifecycle management. Produces a flag lifecycle playbook, taxonomy reference, per-flag creation template, rollout decision tree, and cleanup checklist.

Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items. Use when asked to prioritise features, rank a backlog, decide what to build next, or evaluate tradeoffs between competing ideas. Produces a scored, ranked feature list with framework-specific tables, recommended build order, deprioritised items, and assumptions made.

Plan the retirement of a product feature — the kill decision made honest, user migration, data handling, comms sequencing, and the code actually deleted. Use when deprecating or sunsetting a feature, killing an underused capability, retiring an AI feature that didn't land, or when a 'deprecated' feature has haunted the codebase for two years. Produces a sunset plan: the decision record, affected-user analysis, migration paths, a staged timeline with comms per stage, and the removal checklist. For API deprecation specifically use api-versioning-strategy.

Learn something deeply by trying to explain it simply — the Feynman technique — surfacing exactly the gaps where your understanding is fake. Use when asked help me really understand X, explain this back to check my understanding, use the Feynman technique on, or do I actually get this. Produces a prompt to explain the concept in plain language yourself, a check that flags where your explanation went vague, hand-wavy, or jargon-hid a gap, the specific things you don't actually understand yet, and how to close each — because if you can't explain it simply, you don't really know it.

Generate structured developer handoff annotations for a Figma screen or component. Use when asked to write Figma annotations, create dev handoff notes, document a Figma design for developers, or write specs for a screen. Produces a complete annotation set covering interactions, states, spacing, accessibility, and edge cases.

Audit a Figma component library for consistency, coverage gaps, and naming issues. Use when asked to audit components, review a design system, check component consistency, identify missing components, or assess Figma library health. Produces a structured audit report with issues prioritised by impact, naming recommendations, and a fix plan.

Write a structured design brief for a Figma design task from a product requirement or feature request. Use when asked to write a design brief, create a design spec for Figma, turn a PRD into design requirements, or brief a designer on what to build in Figma. Produces a brief with goals, scope, user flows, components needed, constraints, and success criteria.

Runs a PM-perspective design critique focused on product outcomes and user goals, not aesthetics. Use when asked for a PM design critique, a product review of a Figma design, or feedback from a product perspective without needing to be a designer. Produces structured outcome-based feedback tied to user goals, business metrics, and requirement coverage.

Runs a pre-handoff QA checklist on a Figma design before it goes to engineering. Use when asked to QA a Figma design, do a pre-handoff check, or validate a Figma file is ready to build. Produces a structured QA report covering file hygiene, component usage, accessibility, and handoff readiness with explicit pass/fail status per item. Optimised for Opus 4.7 and newer models.

Runs a structured PM design review against product requirements. Use when asked to review a Figma design, check a design against requirements, or assess whether a design meets the product spec. Produces a requirements coverage check, UX concerns, open questions, and an explicit approval status — approved, approved with conditions, or not approved.

Plan prototype interactions and flows for user testing in Figma. Use when asked to plan a Figma prototype, set up prototype interactions, define what to prototype for a user test, or prepare a Figma prototype for usability testing. Produces a prototype scope, interaction specification, test task scripts, and Figma setup guide.

Design a spacing and layout token system for a Figma design system. Use when asked to create a spacing system, define layout tokens, set up a grid system, build a spacing scale, or establish layout foundations for a Figma file. Produces a complete spacing scale, grid definition, component spacing conventions, and Figma implementation guide.

Plan user flows and screen states for a Figma design before any designing starts. Use when asked to plan a user flow, map out screens for a feature, define screen states, plan a Figma file structure, or work out what needs to be designed before opening Figma. Produces a complete flow map with all screens, states, entry/exit points, and a suggested Figma page structure.

Define component variants and states systematically for Figma. Use when asked to plan component variants, define states for a component, set up a Figma variant matrix, or work out what properties a component needs before building it. Produces a complete variant matrix with all properties, values, and combinations needed.

Run the pre-flight checklist before an agent gets filesystem access — the scope boundary (which directories, read vs write), the secrets-exposure sweep, the destructive-operation gates, and the path-traversal and untrusted-file defenses. Use when asked let my agent access my files safely, is it safe to give the agent file/computer access, guardrails before the agent touches my filesystem, or scope down my coding agent's reach. Produces the scope boundary, the secrets sweep, the write/delete gates, and the untrusted-content rules.

Set a filename convention that sorts, searches, and survives — date-first ISO format, the descriptor grammar, version suffixes that end the FINAL-final2 era, and the rollout that gets a team actually using it. Use when asked set up file naming rules, our filenames are chaos, what should we call our files, or fix the v2-final-FINAL problem. Produces the convention with its grammar, examples for the team's real file types, the version rule, and the one-line cheat sheet.

Write a financial-aid appeal or scholarship request letter that aid offices act on — factual, documented, and specific about the ask. Use when asked to appeal my financial aid, write a scholarship letter, ask for more aid after circumstances changed, or respond to an aid decision. Produces the appeal letter with the changed-circumstance case documented, the specific dollar ask, the evidence list to attach, and the follow-up plan.

Run an annual (or anytime) financial health check across the key areas — so you catch problems and opportunities instead of drifting. Use when asked do a financial checkup, am I doing okay financially, review my finances, or financial health check. Produces a structured review across the core areas (safety net, debt, spending, saving/investing, protection, and goals), a clear read on what's healthy vs needs attention, the highest-priority fixes, and a couple of easy wins — a financial physical that turns 'I think I'm fine?' into an honest, actionable picture. Educational, not financial advice.

Generate a financial due diligence checklist and analysis framework for any investment, acquisition, or partnership. Use when asked for a due diligence checklist, M&A financial review, investment analysis framework, or vendor financial assessment. Produces a document request list, key analytical questions, red flags checklist, and a summarised financial health assessment.

Turn financial model outputs into a clear written narrative. Use when asked to write a financial narrative, explain a financial model, summarise a P&L, or translate spreadsheet numbers into a board-ready story. Produces an executive narrative with key insights, drivers, and forward-looking commentary.

Explain a financial statement (P&L, balance sheet, or cash flow) in plain English. Use when asked to explain a P&L / income statement, a balance sheet, a cash flow statement, or to make financials understandable to a non-finance reader. Produces a plain-language walkthrough — what each section means, the line items that matter, the key ratios, and the story the numbers tell — so a non-accountant can read and act on it. Not financial advice.

Map a realistic path toward financial independence — the number you'd actually need, your savings rate's massive effect on the timeline, and the honest tradeoffs. Use when asked how do I reach financial independence, explain FIRE, what's my FI number, or plan for financial freedom. Produces an educational read on your rough FI number (and why the savings rate matters more than income), the timeline math at different savings rates, the levers and lifestyle tradeoffs, the different flavors (lean/coast/full), and the traps — turning a vague dream of freedom into a directional plan. Not financial advice.

Appeal a parking ticket, penalty charge, or administrative fine with the grounds that actually get appeals granted — not indignation. Use when someone got a ticket/fine/penalty notice and either has a legitimate case or wants an honest read on whether they do. Produces a short formal appeal letter built on recognised grounds (signage, procedure, mitigation, first-offence discretion), the evidence checklist, and a candid win-likelihood note — or the honest advice to just pay it.

Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer. Use when asked what's my FIRE number, when can I retire early, how much do I need to be financially independent, or model my savings trajectory. Produces the FIRE number, years-to-target at stated assumptions, a return × withdrawal-rate sensitivity grid, and the honest list of what the model ignores.

Build a realistic plan to reach your first major savings/investing milestone — the hardest one — by focusing on the levers that actually move it: income, savings rate, and time. Use when asked how do I save my first 100k, plan to build wealth, reach a savings milestone, or how do I actually get ahead financially. Produces an honest read on your three levers (earn more, spend less, invest consistently), which one has the most room for you, a milestone timeline based on real numbers, the compounding effect once you're rolling, and the traps that stall people — educational, not financial advice.

Build a concrete plan for the first 90 days after release from incarceration — the ID, benefits, housing, check-ins, and money moves that have to happen in order, before they cascade into a crisis. Use when asked I'm getting out of prison what do I do first, reentry plan, just got released and I'm overwhelmed, or first steps after incarceration. Produces a sequenced week-by-week plan for the highest-priority setup (ID and documents, parole/probation compliance, benefits, housing, phone, bank, health/meds), the deadlines that carry real consequences, a triage of what's urgent vs. what can wait, and where to get reentry support — so the first months build stability instead of spiraling. Not legal advice; centers parole/probation compliance and points to reentry services.

Put your first client agreement in writing — the eight clauses a simple service contract must have, in plain language a non-lawyer can use, with the blanks filled from your actual deal. Use when asked write my first client contract, what should a freelance agreement include, my client wants to start without a contract, or review this simple services agreement. Produces the plain-language agreement draft with the eight load-bearing clauses, the per-clause reasoning, the how-to-send-it script, and the when-this-needs-a-lawyer triggers.

Set up a new open-source project's first month so it can grow without eating its maintainer — the README that routes people correctly, CONTRIBUTING boundaries written before there are contributors, issue templates that pre-triage, a release rhythm, and the sustainability defaults (what you owe no one). Use when someone says 'my repo is getting attention', 'I just open-sourced something', 'set up my project properly', or their first PR from a stranger just landed. Produces the docs set, the templates, and the month-one routine.

Plan your first hire — whether to hire at all yet, contractor vs employee, what role to hire, and how to do it right when you've never hired before. Use when asked to help me make my first hire, should I hire someone, contractor or employee, or how do I hire for my small business. Produces a readiness and role read (what to hand off first), a contractor-vs-employee decision for your situation, a lightweight hiring process (role definition, sourcing, a fair evaluation, an offer), the obligations to be aware of, and onboarding basics — flagging that employment/tax/legal rules are local. Not legal or tax advice.

Answer a question five completely different ways — as five independent minds with clashing worldviews — then converge on what survives. Use when asked for multiple perspectives, look at this from every angle, what would different people think, or give me a range of views not one answer. Produces five genuinely distinct takes (each committed to one worldview, not hedged), the tensions between them made explicit, and a final synthesis that keeps what's strongest — deliberately widening the range before narrowing it.

Plan around flare days before they ambush you — spot your early warning signs, pre-build the reduced 'flare mode' version of your life, prepare the cancellation and support scripts in advance, and set up your space so a bad day needs no decisions. Use when someone says 'my flares blindside me', 'I fall apart when a bad day hits', 'help me prepare for flare-ups', or has a relapsing condition (autoimmune, migraine, mental health, chronic pain). Produces a flare early-warning list, a flare-mode plan, and the pre-written scripts. A self-management tool, not medical advice.

Track live aircraft positions with zero API keys — adsb.lol's open ADS-B network primary, OpenSky fallback, via curl: by callsign, registration, or area. Use when asked where is this flight right now, what planes are overhead, track a tail number, or is that flight in the air. Produces the live position with altitude, speed, and heading interpreted, the overhead list for a location, and the rerunnable command — with the positions-not-schedules boundary stated honestly.

Work out whether a delayed, cancelled, or overbooked flight likely owes you compensation — and draft the claim with the right rule cited. Use when asked about flight delay compensation, my flight was cancelled/delayed/overbooked, am I owed money for this flight, or how do I claim EU261. Produces an eligibility read against the likely-applicable regime (EU261/UK261/US DOT-style and airline duty-of-care), the amount band, the claim letter with flight details, and the evidence to attach — flagging what to verify because rules and thresholds change.

Read your team's flow metrics — cycle time, throughput, WIP, aging work — and say what they actually mean and what to try, not just restate the numbers. Use when asked to interpret cycle time, what do our flow/Actionable-Agile metrics mean, why is delivery slow, or read our Kanban metrics. Produces the health read per metric, the likely bottleneck the numbers point to, 2–3 concrete process experiments to run next, and the trap-to-avoid so the team doesn't game the metric instead of fixing the flow.

Turn a process, workflow, or decision logic into a clean flowchart. Use when asked to diagram a process, map a workflow, visualize steps/branches, or show 'how this works' as a chart. Produces a ready-to-render Mermaid flowchart (renders live in the playground, exportable as PNG/SVG) plus a short legend and the assumptions made.

Draft a public-records request (FOIA / FOI / state open-records) that's specific enough to get records and hard to deny. Use when asked to write a FOIA request, records request, or freedom-of-information request to a government body. Produces a properly-scoped request: the records sought, date range and format, fee-waiver and expedited-processing asks where applicable, and citations to the governing statute.

Design a folder structure people actually file into — shallow, purpose-first, with a home for everything and an inbox for the undecided, sized to the team that must maintain it. Use when asked organize our shared drive, design a folder structure for the project, where should things live, or our files are chaos. Produces the structure with its placement rules, the depth and naming constraints, the _inbox convention, and the migration-lite plan for the existing mess.

Chase unanswered emails without being annoying — the escalating-gently sequence with timing rules, the re-ask that makes replying easy, and the close-the-loop discipline that ends zombie threads. Use when asked they haven't replied what do I send, write a follow-up that isn't pushy, how long do I wait before chasing, or manage my waiting-on list. Produces the follow-up sequence with dates, drafts per rung, and the give-up-gracefully exit.

Write the follow-up messages that keep a candidate on the radar without being annoying. Use when asked to write a post-interview thank-you, a follow-up after no reply, a nudge on a stalled application, or a check-in sequence during a job search. Produces a timed sequence — what to send, when, and the exact wording — that adds value or shows interest at each step rather than just 'checking in'.

Sweep the user's REAL mail and calendar for dropped balls — threads awaiting their reply, promises they made, and replies they're owed — then draft the nudges. Use when asked what am I forgetting, what have I not replied to, who owes me a reply, or chase my open threads in Cowork. Reads sent/received mail via the Gmail connector and recent events via Calendar, finds the open loops, and produces a follow-up-list artifact plus ready-to-send draft nudges.

Fill long web forms and applications through a computer-use agent — from a fact sheet you approve, field by field, with a full transcript and nothing submitted without your word. Use when asked to fill this application for me, complete this government/vendor/insurance form, or do this registration. Produces the fact-to-field mapping, the filled form held at review, and a field-level transcript.

Untangle the spreadsheet formula nobody dares touch — decompose the seven-function nest into named readable steps, explain what it actually does (vs. what it's believed to do), and rebuild it maintainably with helper columns and modern functions. Use when asked what does this formula do, this IFERROR-VLOOKUP monster broke, make this formula maintainable, or nobody understands the sheet the analyst left. Produces the plain-language decode, the step decomposition into helper columns, the believed-vs-actual gaps, and the rebuilt version.

Articulate founder-market fit — the why-you and why-now story investors and accelerators (YC-style) probe hardest. Use when asked to write the founder story, answer 'why are you the right team', draft YC / accelerator application answers, or explain founder-market fit. Produces a sharp narrative connecting the founder's unfair insight and earned secrets to this specific opportunity — concrete, not a humble-brag.

Run a hard two-option decision through Benjamin Franklin's 'moral or prudential algebra' — the weighted pro/con method he described to Joseph Priestley in 1772 — including the part everyone skips: striking out reasons that cancel, and letting the ledger sit before deciding. Use when weighing job offers, relocations, build-vs-buy, take-the-promotion, shut-it-down decisions, or any 'I keep going back and forth'. Produces a completed decision ledger with a leaning, its strongest counter, and a revisit date.

Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000. Use when asked what should I charge as a freelancer, how do I set my consulting rate, why is my freelance rate so high, or convert my salary to a contract rate. Produces the required-revenue breakdown, billable-hours math, the hourly and day rate, and the multiplier vs the naive salary÷2000 number.

Strip a problem down to what's actually true — the physics, economics, and human basics — and rebuild the answer from there, ignoring 'how it's normally done'. Use when asked to think from first principles, why is this done this way, challenge the assumptions here, or rebuild this from scratch. Produces the problem reduced to its fundamental truths, the inherited assumptions and conventions named and questioned, and a solution reasoned up from the basics — which often looks nothing like the default because the default was just copied.

Produce frontend UI that actually looks designed — a working spacing/type system, deliberate color use, real states, and restraint — instead of the generic AI-generated interface. Use when asked to build or restyle a UI, landing page, dashboard, or component, when output 'works but looks like a prototype', or to establish the visual system for a new app. Produces working HTML/CSS (or framework components) built on an explicit token system, with hover/focus/empty/loading states included. For critiquing an existing design use design-critique; for auditing a design system use design-system-audit.

Pressure-test a fundraise by anticipating the hard investor questions and arming the founder with crisp answers. Use when asked to prep for investor Q&A, anticipate due-diligence questions, handle pushback on a raise, or build a fundraising FAQ. Produces the toughest questions an investor will ask — grouped by theme — each with the strongest honest answer and the trap to avoid.

Interview your future self about a decision or a stuck moment — a structured perspective-shift that pulls you out of present emotion and into the long view, using your own values and patterns rather than generic advice or woo. Use when someone says 'I don't know what to do', 'help me think long-term about this', 'what would future me say', or is stuck in the fog of a big decision. Produces an interview with your 5-or-10-years-older self, the themes it surfaces, and one concrete next step it points to. A structured reflection, not prediction or fortune-telling.

Bring three versions of future-you into a decision — you in a week, in a year, and in ten years — because they each want different things. Use when asked what would future me want, will I regret this, think long-term about this choice, or help me decide for the long run. Produces each future self's honest take on today's decision, where they conflict (short-term relief vs long-term payoff), whose vote should weigh most given what's at stake, and the choice that best serves the future-you that matters here.

Plan a game night that actually works for the specific people coming — the right lineup for player count, weight tolerance, and time, sequenced from icebreaker to main event, with the fallback for when someone bails. Use when someone says 'planning a game night', 'what should six of us play', 'games for my family Christmas', 'my partner hates long games', or 'we always end up arguing over what to play'. Produces a sequenced lineup with reasoning, timings, and a plan B.

Turn a plan or set of milestones into a timeline / Gantt chart. Use when asked to build a roadmap, schedule phases, show a project timeline, or visualize what happens when. Produces a ready-to-render Mermaid Gantt chart (renders live, exportable as PNG/SVG) — and, because it has real dates, the result also exports to a calendar (.ics) — plus notes on the critical path and risks.

Assess GDPR compliance and build the core records (ROPA, lawful basis, DSAR, DPIA triggers). Use when asked to get GDPR-compliant, build a Record of Processing Activities, decide a lawful basis, handle data-subject requests, or check whether a DPIA is needed. Produces a GDPR assessment — a ROPA, lawful-basis mapping per activity, DSAR workflow, DPIA-trigger screen, and a prioritised gap list.

Separate raw idea-generation from judgment so creativity isn't strangled by your inner critic — diverge with zero evaluation, then switch to hard critique. Use when asked to brainstorm properly, help me come up with ideas without shutting them down, I keep censoring my own ideas, or separate creating from editing. Produces a pure generation pass (quantity, no judging, no hedging, wild allowed), a clean break, then a separate ruthless critique pass that scores and prunes — because doing both at once produces neither.

Level up how you actually use AI — from basic one-shot questions to the techniques that get dramatically better results — matched to what you already do. Use when asked how do I get better at using AI, how do power users use AI, I feel like I'm using AI at 10%, or teach me to use AI better. Produces an honest read of how you use AI now, the two or three highest-leverage techniques to add next (giving context, iterating, showing examples, breaking down tasks, verifying), a concrete before/after on your own use, and a simple practice path — so you close the gap between basic and expert without drowning in tips.

Find a genuinely good gift for a specific person and occasion within a budget — thoughtful and non-obvious, not a generic 'top 10 gifts' list. Use when asked for gift ideas, what should I get [person], help me find a present, or I have no idea what to buy. Produces a short set of tailored ideas across price points, why each fits this person, where to get it and rough price, a safe backup, and an honest flag when you need one more detail to nail it.

Reclaim value stuck in gift cards, store credit, and forgotten balances — check what's left, use it before it's lost, and know your rights on expiry and cash-back. Use when asked to use up a gift card, I have store credit I forgot about, do gift cards expire, or get cash for a gift card. Produces a way to find and check balances, the rules on expiry and dormancy for your region, options to use/convert/sell partial balances, guidance on cashing out small remainders where allowed, and how to avoid the common gift-card scams.

Diagnose a tangled git situation and give the exact, safe commands to fix it. Use when asked to undo a commit, recover lost work, fix a bad merge or rebase, resolve a detached HEAD, unstage files, or get out of a git mess. Produces the diagnosis, the precise commands to run in order, what each does, and a recovery note if something goes wrong.

Read a GitHub repository's vital signs with keyless curl — commit recency, release cadence, issue/PR responsiveness, and bus factor — interpreted into an is-this-project-alive verdict. Use when asked is this repo maintained, check this project before we build on it, how active is this library's development, or compare these repos' health. Produces the vitals with their reads, the responsiveness sampling, the rate-limit-aware command set, and the alive/coasting/abandoned verdict.

Give someone difficult feedback — a report, a peer, a friend — so it actually lands and helps, without crushing them or dodging the point. Use when asked how do I give hard feedback, tell someone something difficult, address a problem with someone, or have a tough conversation about their [work/behavior]. Produces a read on what you actually need to say (the specific behavior and its impact, not a vague vibe), a structure that's direct and kind at once, the exact opening and words, how to invite their side and land on a path forward, and the traps (sandwiching it away, going vague, making it about character).

Turn a vague concern into specific, kind, actionable feedback. Use when asked to give feedback, write a feedback note, prepare to tell someone something hard about their work, or coach a report/peer. Produces ready-to-deliver feedback structured on situation–behaviour–impact, separating observation from judgement, with the change requested and an opening line — calibrated to praise or constructive.

Build a translation/terminology glossary so a product's key terms render consistently everywhere. Use when asked to create a glossary, a termbase, a do-not-translate list, or to keep terminology consistent across translators/locales. Produces a glossary — each source term with its approved translation per locale, part of speech, definition/context, and do-not-translate flags — ready for a CAT tool or style guide.

Build an emergency go-bag tailored to your actual household and your most likely local hazards — not a generic list — covering the people, pets, medications, documents, and hazard-specific items you'd need to grab and leave in minutes. Use when someone says 'build an emergency kit', 'what goes in a go-bag', 'prepare for evacuation', or 'emergency preparedness for my family'. Produces a personalised packing list, a grab-in-2-minutes core, storage and maintenance guidance, and per-person/per-pet additions. Points to official preparedness sources for your region.

Create go-to-market assets for any product or feature. Use when asked for a GTM plan, positioning statement, product launch plan, messaging pillars, use cases, or feature/benefit list. Produces a full GTM pack: positioning statement, messaging pillars, feature-to-benefit mapping, and role-specific use cases. For a tiered launch plan with cross-functional coordination use go-to-market-planner instead.

Build a go-to-market plan for any product launch, feature release, or new market entry. Use when planning a product launch, writing a GTM strategy, defining launch tiers, or coordinating cross-functional launch activities. Produces a tiered GTM plan with messaging, cross-functional activity tracker, success metrics, and launch day checklist. For positioning and messaging content itself use go-to-market instead.

Tell you when to stop polishing and ship — the point where more effort stops adding real value. Use when asked is this good enough, should I keep working on this, when do I stop, or I keep tweaking this and can't let go. Produces a read on whether the thing already meets its actual bar, the diminishing-returns check (is more effort improving it or just moving it around), what genuinely still needs fixing vs what's perfectionism, and a clear ship / one-more-pass / keep-going verdict — freeing you from polishing things past the point anyone will notice.

Write a structured grant proposal or funding application for any grant type. Use when asked to write a grant proposal, funding application, research grant, charitable grant, or innovation fund application. Produces a complete proposal with project summary, rationale, methodology, impact, and budget narrative.

Set up a gratitude practice that survives past week one — a specific format, a realistic cadence, and prompts that avoid the toxic-positivity trap. Use when asked to start a gratitude practice, gratitude journal help, how to be more grateful, or a gratitude routine that sticks. Produces a concrete format (what to write, how many, how specific), an anchor and cadence, variety so it doesn't go stale, and an honest note that gratitude complements — never denies — real difficulty.

Audit your own marketing and report claims for greenwashing risk before a regulator, journalist, or competitor does. Use when asked to review sustainability claims, check marketing copy for greenwash, audit environmental claims on a website or report, or pressure-test green messaging. Produces a claim inventory with substantiation status per claim, vague-term and omission flags, and a fix-or-drop recommendation for every claim.

Get through the brutal logistics after a death — who to notify, what accounts and services to close, in what order, and what genuinely can't wait vs what can wait months — with explicit permission to do it slowly and in pieces. Use when someone says 'my [person] died and I don't know where to start', 'what do I need to do after a death', 'help me handle the admin', or is drowning in the paperwork of loss. Produces a triaged task list (urgent / soon / whenever), notification scripts, and a gentle sequence. Not legal or tax advice — the humane logistics, with pointers to the professional bits.

Handle work while grieving — what to tell your manager and team, how much leave you can take, and how to function (or not) when you're back but not okay. Use when asked how do I tell my boss someone died, going back to work after a death, bereavement leave, or I can't focus at work while grieving. Produces a short message to tell your manager and team (with the boundary of how much to share), what to know about bereavement leave and options, a realistic re-entry plan for the first weeks back, scripts for when grief hits at work or people say the wrong thing, and how to ask for what you need — so work doesn't compound the loss. Not legal/HR advice; points to your policy, HR, and EAP.

Find where the food money actually goes — a no-shame ledger built from real receipts/statements, the four leak categories (waste, convenience markup, brand autopilot, the takeaway blur), a per-leak fix with realistic savings ranges, and a target budget that survives real life. Use when someone says 'we spend how much on food?!', 'audit my grocery spending', 'cut our food bill', or takeaway guilt is the household argument. Produces the ledger, the leak report, and a keep-the-joy budget.

Save the group trip from the group chat — budget alignment before anything gets booked (the awkward conversation, scripted), a decision protocol that actually books things, cost-splitting rules with real numbers for unequal rooms and champagne-taste friends, and the it's-okay-to-split-up daytime clause. Use when someone says 'we're planning a trip with friends and it's chaos', 'how do we split costs', 'one friend wants luxury and one is broke', or the trip has been 'being planned' for three months. Produces the budget-alignment script, the decision protocol, and the money agreement.

Build and prioritise a growth experiment backlog. Use when asked to plan growth experiments, prioritise growth ideas, set up a test backlog, or run a growth process/sprint. Produces a prioritised backlog — each experiment as a hypothesis with the metric it moves, an ICE/PXL score, the minimum test design, and a definition of done; plus the cadence to run it.

Document a guest incident at a hospitality venue — injury, illness, foodborne complaint, altercation, or property loss — into a clear, defensible record. Use when asked to write up a guest incident, log an accident or complaint, document a slip/fall or allergic reaction, or record an incident for insurance/legal. Produces a factual incident report (who/what/when/where, witnesses, actions taken), an immediate-response checklist, notification/escalation steps, and follow-up — objective and liability-aware, without admitting fault.

Design one habit so it actually sticks — small enough to be unmissable, anchored to something you already do, with a plan for the days you slip. Use when asked to build a habit, help me stick to [habit], I keep failing at [routine], or start a new habit. Produces a shrunk-down version of the habit, a concrete cue/anchor and time/place, a tracking method, a friction plan (make good easy, bad hard), and a get-back-on-track rule so one miss doesn't end it.

Write the handbook page that ends the repeated explanation — the answer-shaped structure (task-first, context second), the ownership and freshness header, and the write-once-point-forever discipline that turns tribal knowledge into infrastructure. Use when asked document how we do X, write the wiki page for this process, I explain this every month, or make this knowledge survive me. Produces the page with task-first structure, the header block, the worked example, and the pointer habit.

Write a PRD for a physical hardware product — target cost (BOM and landed), industrial design constraints, regulatory certifications, reliability targets, serviceability, packaging, and forecast assumptions. Use when asked to write a hardware PRD, spec a new device, define requirements for a physical product, or kick off an NPI program. Produces a complete hardware PRD with a cost stack, cert matrix, reliability spec, and EVT/DVT/PVT milestone targets.

Figure out which disasters and emergencies your specific location actually faces — and the concrete prep each one demands — so your readiness targets real risks instead of generic ones. Use when someone says 'what disasters should I prepare for', 'am I in a flood/wildfire/quake zone', 'what emergencies are likely where I live', or 'where do I start with preparedness'. Produces a ranked local-hazard list, the specific prep each demands, warning-signal and alert setup, and where to verify official risk data for your area.

Generate and pressure-test headline options across proven formulas. Use when asked for headlines, a title, a subject line, a hook, or to improve a weak headline for a page, post, email, or ad. Produces 10–15 headline options grouped by formula (benefit, how-to, number, question, curiosity, social proof), each scored for clarity and specificity, with the top 3 recommended and why.

Run a self-audit of a food establishment before the health inspector arrives, focused on the violations that actually close kitchens. Use when asked to prep for a health inspection, do a food-safety self-audit, avoid critical violations, or get ready for the health department. Produces a prioritized checklist organized by risk (critical/priority vs. non-critical), the temperature and hygiene fundamentals, a fix list with owners, and how to handle the inspector on the day.

Understand and enrol in a new country's healthcare system — how it works (public/private/insurance-based), what you're entitled to with your status, how to register with a doctor, get insurance if required, and what to do before you're covered. Use when someone says 'how does healthcare work in [country]', 'register with a doctor abroad', 'do I need health insurance in [country]', or 'I just moved and need to see a doctor'. Produces a system explainer, an enrolment checklist, a coverage-gap plan, and cost expectations. Orients and routes to official sources; not medical or insurance advice.

Write a help-center / knowledge-base article that actually resolves the issue and deflects tickets. Use when asked to write a help doc, KB article, FAQ entry, how-to, or support documentation. Produces a findable, skimmable article — task-based title, the answer up front, numbered steps, screenshots-to-add markers, troubleshooting, and related links — written so users self-serve instead of contacting support.

Scan a bill, contract, or quote for junk and hidden fees — the padding buried in the fine print — and get them questioned or removed. Use when asked to check this bill for hidden fees, are these charges legit, what am I actually paying for, or review this quote for junk fees. Produces a line-by-line read flagging suspicious/vague/padded charges, which are commonly negotiable or bogus, the questions to ask and script to dispute them, and an estimate of what you could save — across bills like telecom, hotels, cars, banking, and services.

Map HIPAA Security Rule safeguards and run a risk analysis for systems handling PHI. Use when asked to become HIPAA-compliant, assess HIPAA safeguards, prepare for handling PHI/ePHI, or scope a BAA. Produces a HIPAA assessment — the administrative/physical/technical safeguards with required-vs-addressable status, a risk analysis, BAA scope, and a prioritised remediation plan.

Generate a structured interview scorecard and interview guide for any role. Use when asked to create a hiring rubric, interview scorecard, structured interview guide, or assessment criteria for a job. Produces a scorecard with competencies, behavioural questions, and scoring guidance.

Pull the current Hacker News front page, top comments, or a topic search with zero API keys — the official Firebase API and Algolia search via curl, digested instead of dumped. Use when asked what's on Hacker News, summarize HN today, what's the discussion on this story, or has HN covered some topic. Produces a ranked digest with scores and comment counts, the discussion's actual argument threads when asked, and the rerunnable commands.

Decode HOA covenants (CC&Rs) and the fee structure before you buy into them. Use when someone asks 'what do these HOA rules actually mean', 'decode these CC&Rs', 'is this HOA going to be a problem', or 'what should I check before buying in an HOA'. Produces a restriction decode ranked by lifestyle impact, special-assessment exposure analysis, enforcement and fine mechanics, and the exact records to request before buying.

Respond to an HOA or condo-association violation notice or fine — decide whether to comply, cure, or dispute, and do it on the record. Use when asked to respond to an HOA violation, my HOA fined me, is this HOA rule enforceable, or fight an HOA notice. Produces a read on whether the citation likely holds (against the governing documents and consistent enforcement), a comply-vs-dispute recommendation, a measured response/appeal letter, the evidence and record-keeping to keep, and escalation options — flagging that HOA rules and rights are governed by your documents and local law. Not legal advice.

Turn 'I want to try [hobby]' into a real first month — the minimal starter gear, the first skills to practice, and a beginner-friendly plan that survives contact with real life. Use when asked how do I start [hobby], I want to get into [activity], what do I need to begin, or help me pick up a new hobby. Produces a cheap-as-possible starter kit (buy now vs buy later), a first-30-days progression, where to learn and find a community, and the honest quitting-points to plan around so you actually stick with it.

Decode a home renovation or repair quote — allowances that aren't prices, exclusions that become change orders, payment schedules that shift risk, and what a comparable-bids check should cover. Use when someone asks 'is this contractor quote fair', 'decode this renovation bid', 'what should be in a contractor contract', or 'why do these three bids differ so much'. Produces a section-by-section decode, the allowance and exclusion audit, payment-schedule risk analysis, and the questions that make bids comparable.

Cut your home energy bills with a prioritized plan — the free and cheap fixes first, then the upgrades that actually pay back. Use when asked how to lower my energy bill, make my home more energy efficient, reduce heating/cooling costs, or save energy at home. Produces a read on where your energy (and money) likely goes, a ranked list of fixes from free behavior changes to low-cost improvements to bigger investments with payback estimates, quick wins to start today, and what to measure — flagging that savings and any rebates depend on your home and region.

Build a home workout plan that fits your gear, time, and goal — a real weekly structure, not a random list of exercises. Use when asked to build a home workout, make me a workout plan, exercise routine at home, or how do I work out with no gym. Produces a weekly plan matched to your equipment and schedule, each session with warm-up, main work, sets/reps, and progression, swaps for missing gear, and a way to make it harder over time — with a plain 'this isn't medical advice, stop if it hurts' note.

Make sense of a home-inspection report before you buy — what's serious vs cosmetic, what to negotiate, and what to investigate further. Use when asked to explain my home inspection, is this inspection finding serious, what should I negotiate after inspection, or decode my inspection report. Produces a triage of findings by severity (safety/structural/expensive vs minor/cosmetic), plain-English translations, the items worth a repair credit or price negotiation, what warrants a specialist follow-up, and a walk-vs-proceed read — flagging that the inspector and specialists are the authority.

Build a seasonal home-maintenance calendar so the small upkeep gets done before it becomes an expensive repair. Use when asked for a home maintenance schedule, what should I do to maintain my house, seasonal home checklist, or home upkeep plan. Produces a month-by-month/seasonal task list tuned to your home type and climate, grouped by system (roof, HVAC, plumbing, exterior, safety), a note of what's DIY vs pro, the highest-consequence tasks not to skip, and a simple way to track it — so upkeep is routine, not reactive.

Generate scroll-stopping hooks — the first line of a post, thread, video, or email that decides whether anyone keeps reading. Use when asked to write a hook, an opener, a first line, a thread starter, a video cold-open, or to make something more clickable. Produces multiple distinct hook options across proven angles (curiosity, contrarian, result, story, stakes), each labelled with why it works and which platform it fits.

Navigate a hospital stay — for yourself or someone you care for — from admission through a safe discharge, so nothing critical falls through the cracks. Use when asked help me through a hospital stay, my parent is in the hospital, prepare for a hospital admission, or what do I need to know for the hospital. Produces what to bring and organize, how to stay informed and involved with the care team, the questions to ask daily, the discharge planning to start early (not at the last minute), and the home-readiness checklist for after — reducing the chaos and the dangerous gaps, especially at discharge. Not medical advice.

Apply a team's writing style consistently — extract the house style from exemplar documents into a checkable rule card, run the conformance pass on new drafts, and fix violations without flattening the author's voice. Use when asked make this match our style, why do our docs all sound different, build a style guide from our best docs, or check this draft against house style. Produces the extracted rule card, the conformance pass with per-fix reasons, and the voice-preservation line.

Diagnose why a houseplant is struggling and set a care routine it'll actually thrive on — matched to your light, home, and how much attention you'll realistically give. Use when asked why is my plant dying, how do I care for a [plant], my plant's leaves are [yellow/brown/drooping], or help me keep this plant alive. Produces a likely-cause diagnosis from the symptoms, the specific fix, a simple ongoing care routine (water/light/feed), and honest 'is this the right plant for your space' guidance.

Find and land a place to live when a criminal record keeps triggering rejections — where to apply, how to present the record, and the rights that limit how it's used against you. Use when asked how do I rent with a criminal record, landlord denied me for my background, second-chance housing, or explain my record to a landlord. Produces a target list of record-tolerant housing (private landlords, second-chance programs, certain nonprofits), a short honest explanation letter, the documents that build trust (references, income proof, rehabilitation evidence), and the fair-housing rights that limit blanket record bans — so a record narrows the search without leaving you unhoused. Not legal advice; points to housing counselors and legal aid.

Design the human approval surface for an agent system — which actions gate, how approvals batch without becoming rubber stamps, and what the audit trail must hold. Use when asked to add human oversight to an agent, design approval workflows for AI actions, decide what an agent may do autonomously, or fix approval fatigue in an existing loop. Produces an action-tier policy, approval UX spec, escalation rules, and audit-trail requirements. For specifying the whole agent use agent-spec; for the per-skill execution gates see the Execution-block pattern in SKILLSPEC §5.

Beat the afternoon crash with a realistic hydration, food-timing, and movement plan — not a caffeine-and-sugar band-aid. Use when asked how to stop the afternoon slump, I'm always tired after lunch, boost my energy, or a hydration routine. Produces a read on likely crash causes, hydration targets tied to your day, food and caffeine timing that avoids the spike-crash, movement and light micro-fixes, and a flag that persistent fatigue is worth a doctor's check.

Give yourself a gentle, structured off-ramp from hyperfocus before it costs you sleep, meals, or the rest of your life. Use when asked I've been at this for hours, help me stop working, I can't pull myself away from this, or I lost track of time again. Produces a quick reality check on how long you've been at it and what you've neglected, a save-your-place ritual so stopping doesn't feel like losing progress, a graceful stopping point, and the transition to what you actually need to do next — because for some brains, stopping is harder than starting.

Review a product/codebase for internationalization readiness before you localize. Use when asked if a product is ready to localize, to review i18n readiness, find hard-coded strings/locale bugs, or prep for going multilingual. Produces a readiness audit — externalized strings, locale-aware formatting, layout/expansion, encoding/RTL, and a prioritised list of i18n fixes to make before translation starts.

Generate a big, wide spread of ideas for anything by running the prompt through many different lenses at once, then clustering and picking. Use when asked to brainstorm ideas for, give me lots of options, help me come up with, or I need ideas for. Produces a high-volume, deliberately varied idea list generated across multiple angles (safe, wild, cheap, ambitious, weird, opposite), grouped into themes, and a shortlist of the most promising — maximizing range so you're not choosing from three obvious options.

Take back control after identity theft — the right first moves, in the right order, so you contain the damage and rebuild. Use when asked what to do about identity theft, someone stole my identity, my details are being used fraudulently, or help me recover from fraud. Produces an immediate-actions checklist (freeze, report, secure), an evidence and reporting plan for the right authorities and institutions, a dispute path for fraudulent accounts/charges, and an ongoing-monitoring setup — flagging where to use official channels and when to involve police/regulators.

Walk into an IEP or 504 meeting prepared and effective — the process decoded in plain language, the parent-input statement that gets read, the questions that make goals measurable, and advocacy that stays collaborative. Use when asked prepare me for my child's IEP meeting, what's the difference between an IEP and a 504, how do I disagree with the school's plan, or make sure the accommodations actually happen. Produces the process map, the parent-input statement, the goal-quality checklist, the meeting scripts, and the paper-trail habits.

Draft SMART IEP goals, accommodations, and present-levels statements that are measurable and compliant in spirit. Use when asked to write an IEP goal, draft special-education goals, list accommodations, or write a present-levels (PLAAFP) statement. Produces measurable annual goals with baselines, criteria, and measurement methods, plus matched accommodations. A drafting aid for educators — not legal advice; the IEP team and local requirements govern.

Write measurable IEP goals and matching accommodations for a K-12 student with an IEP or 504 plan. Use when asked to write an IEP goal, draft annual goals, make a goal measurable, or list accommodations. Produces SMART annual goals (baseline, condition, behavior, criterion, measurement) with short-term objectives and a set of accommodations tied to the student's needs — written to be legally defensible and progress-monitorable.

Organise the document pile for a visa, work-permit, or residency application — what to gather, in what order, and the common rejection triggers to avoid. Use when asked to help with a visa application, build an immigration document checklist, prepare paperwork for a work permit or green card, or organise what an application needs. Produces the categorised document checklist, the gather-in-this-order plan, the common-mistake/rejection-trigger list, and the professional-help flags. Organises the paperwork; complements the visa-interview simulator.

Write a compelling nonprofit impact or annual report that shows donors what their money achieved. Use when asked to write an impact report, an annual report, a grant outcomes report, or to report results to funders/donors. Produces a structured report — mission and year in brief, outcomes with real numbers and a beneficiary story, financials at a glance, and a forward ask — that builds trust and renews giving.

Set a boundary with in-laws or extended family kindly and clearly — the words to say, a united-front approach with your partner, and a plan for the pushback. Use when asked how to set a boundary with my in-laws, my mother-in-law keeps [X], deal with overbearing family, or what to say to my partner's family. Produces a read on the actual issue, a warm-but-firm script for the specific situation, a partner-alignment plan (the couple presents together), how to hold the line when they push back, and de-escalation so it protects the relationships rather than blowing them up.

Triage the user's REAL inbox through the Gmail connector — not a framework they run by hand. Use when asked to clear my inbox, get me to inbox zero on the actual account, triage my unread, or process my email backlog in Cowork. Reads unread via the Gmail connector, sorts every message into archive / reply-now / task / park, applies labels and archives in place, drafts the reply-now messages as real Gmail drafts. Produces a triage-report artifact of what it did and what still needs the user.

Cut inbox volume at the source — the unsubscribe purge that classifies recurring senders into kill/digest/keep, executes safely (real unsubscribes vs. spam-report vs. never-click), and installs the filters that catch the rest. Use when asked my inbox is all newsletters, mass unsubscribe safely, cut my email volume, or set up filters for the noise. Produces the sender census, the kill/digest/keep sort, the safe-unsubscribe rules, and the filter set.

Drive an email inbox to zero through a computer-use or tool-using agent — triage every message into act/delegate/defer/archive with drafts prepared, never a send. Use when asked to get my inbox to zero, triage my email hands-on, process my inbox for me, or run inbox zero. Produces the triage ledger, prepared reply drafts, and an approval-gated action plan the agent then executes read-mostly.

Write a structured incident postmortem or post-incident review. Use when asked to write a postmortem, incident report, P1/P2 review, outage report, or RCA (root cause analysis). Produces a blameless postmortem with timeline, root cause, contributing factors, impact summary, and action items.

Write a single clear, honest public statement about an incident. Use when asked to draft a public statement, a press statement, or an official response to a security breach, outage, data incident, recall, or public controversy. Produces a ready-to-publish statement — acknowledgement, what happened, impact, what you're doing, what affected people should do, and a commitment to update — plus a short and a long version.

Build in small, individually-verified increments that each leave the system working — instead of big-bang changes that fail mysteriously at the end. Use when implementing multi-part features, refactoring anything load-bearing, making large mechanical changes, or when past work produced huge diffs that were wrong somewhere unfindable. Produces the same end state as the big bang, reached through verified checkpoints you can stop at, ship from, or roll back to.

Understand index-fund investing and how to actually get started with the simplest evidence-backed approach — plus the details that quietly matter (fees, account, automation). Use when asked how do index funds work, are index funds good, how do I buy index funds, or set up index fund investing. Produces a plain explanation of what index funds are and why they beat most active investing over time, what to check before buying (expense ratio, what it tracks, the account/wrapper), how to automate contributions, and the mistakes to avoid — educational only, not financial advice.

Create a structured brief for an influencer or creator partnership campaign. Use when asked to brief an influencer, plan a creator collaboration, set up a paid partnership, or define deliverables for a sponsored content campaign. Produces a complete campaign brief with objectives, deliverables, creative guidelines, approval process, and performance metrics.

Prepare for an informational interview — the outreach, the questions, and the follow-up — so a 20-minute chat actually helps your career instead of wasting their time. Use when asked to prep for an informational interview, questions to ask someone in [field], how to reach out for a career chat, or coffee chat prep. Produces a low-friction outreach message, a focused question set tuned to your goal (exploring a field, breaking in, a specific company), how to run the conversation, what NOT to do (don't ask for a job), and a follow-up that keeps the relationship warm.

Write an infrastructure-as-code review checklist and conduct a structured review of Terraform, CloudFormation, Pulumi, or Ansible code. Use when asked to review IaC code, audit infrastructure configurations, check cloud security posture, or produce a reusable IaC review checklist. Produces a structured review report with severity-categorized findings, remediation guidance, and a reusable checklist.

Spot prompt-injection in untrusted content before an agent acts on it — the anatomy of injected instructions across the channels attackers use (email, web, files, tool outputs, documents), the tell-list, and the safe-handling response. Use when asked is this content trying to hijack my agent, check this page or email or file for prompt injection, spot the injection, or why did my agent go off-task. Produces the injection verdict with quoted tells, the channel-specific patterns, and the safe-handling protocol.

Decode a home inspection report into what's cosmetic, what's expensive, and what kills deals — with repair-cost ranges and the negotiation list. Use when asked to decode my inspection report, is this inspection bad, what should I ask the seller to fix, or should I walk after inspection. Produces a findings triage (walk-risk / negotiate / cosmetic), cost ranges per item, the ask-the-seller list, and the questions for your inspector before the objection deadline.

Download and save Instagram posts as high-resolution files. Use when asked to download, save, or archive an Instagram post, reel thumbnail, or carousel. Produces saved high-res images in a named folder, with carousel slides stitched into a single PDF; supports batch downloading of multiple URLs at once.

Write a clear insurance claim letter or appeal that supports a payout. Use when asked to write an insurance claim, file a claim letter, document a loss for insurance, or appeal a denied claim. Produces a structured claim — policy and incident details, the documented loss, the amount claimed, and the evidence — or an appeal that rebuts the denial reason, ready to submit.

Appeal a denied insurance claim — read the real reason for the denial, find the strongest grounds, and draft the appeal with the evidence that answers it. Use when asked to appeal a denied claim, my insurance claim was rejected, the insurer won't pay, or how do I fight a claim denial. Produces a decode of the denial reason, the best grounds to appeal on, a structured appeal letter citing your policy, the evidence checklist, deadlines to watch, and the external-review/ombudsman escalation. Not legal or regulated advice.

Decode a home, renters, or auto insurance policy into what's actually covered, what's excluded, and what the payout math really looks like before you need it. Use when someone asks 'what does my insurance actually cover', 'decode my policy', 'is this deductible normal', or 'actual cash value vs replacement cost'. Produces a coverage decode with real payout scenarios, ranked exclusion red flags, the ACV-vs-replacement-cost math, and the questions to ask your agent before renewal.

Elicit the real requirements by interviewing the requester BEFORE building or writing anything — one question at a time, until the brief is buildable. Use when a request is vague ('make me a dashboard', 'write something for the board'), when past deliverables missed the mark, or when the user says 'interview me' / 'ask me questions first'. Produces a validated brief: goal, audience, constraints, success criteria, and explicit non-goals — then, and only then, the work.

Prepare for a specific interview at a specific company, not just 'an interview'. Use when asked to prep for an interview, prepare answers for a role, practice for a specific company's interview, or get ready for a behavioural/case/PM round. Produces a tailored prep pack — likely questions for this role & round, STAR-structured answers from your background, your stories mapped to their competencies, questions to ask, and the gaps to shore up.

Build a structured, role-specific interview question bank with what good answers look like. Use when asked to create interview questions, an interview guide, a structured interview kit, or competency-based questions for a role. Produces questions mapped to the competencies that matter — behavioral (STAR), role/technical, and values — each with what a strong vs. weak answer shows and follow-up probes, for fair, consistent interviews.

Turn a pile of interview notes into findings that survive scrutiny — the code-then-theme pass, the counting discipline (how many actually said it), the quote selection that illustrates instead of cherry-picks, and the confidence lines a small sample earns. Use when asked synthesize these user/customer/exit interviews, what did we actually learn from the calls, turn 12 transcripts into insights, or are these themes real. Produces the coded themes with counts, the divergences preserved, the illustrative quotes, and the claims sized to the sample.

Set inventory policy for an item class: segmentation, safety stock, and replenishment method. Use when asked to set safety stock levels, segment items by ABC/XYZ, choose reorder points vs min-max, define stocking policy, or review excess and obsolete inventory. Produces a segmentation grid, per-segment service targets and safety-stock logic, a replenishment method choice per segment, and an E&O review cadence.

Solve a problem backwards — ask how to guarantee the worst outcome, then avoid all of it. Use when asked to help me not fail at, what could go wrong with, how do I avoid messing up, or think about this in reverse. Produces the inverted question (how to guarantee failure), the specific ways you'd cause the disaster, and then the plan that is simply the avoidance of each — often clearer and more actionable than trying to plan success directly, because failure modes are more concrete than success factors.

Understand the basics of investing enough to start sensibly — the core concepts, the simple default that works for most people, and the traps that separate beginners from their money. Use when asked how do I start investing, explain investing for beginners, I have money to invest but don't know how, or is investing worth it for me. Produces the essential concepts in plain language (risk, diversification, time, fees, compounding), the boring-but-effective default approach, the order of operations before you invest, and the beginner traps to avoid — educational only, not financial advice, and jurisdiction-neutral.

Draft a personal investing policy statement (IPS) — the rules someone sets for their own investing. Use when asked to define an investment strategy, set a target asset allocation, or write rules to avoid panic-driven decisions. Produces a structured IPS: goals, risk tolerance, target allocation, contribution & rebalancing rules, and what NOT to do. Educational, not regulated financial advice.

Understand which type of investment/savings account to use for your goal — the tax-advantaged vs taxable question, and which wrapper fits which money — so you don't leave free tax benefits on the table. Use when asked which account should I invest in, what's the difference between these account types, where should I put my savings, or tax-advantaged accounts explained. Produces a plain-language explainer of the common account categories (retirement/tax-advantaged, general/taxable, education, short-term), a match of your goals to the right account type, the order to prioritize them, and what to verify locally — because using the wrong wrapper can cost you real money. Not financial advice; account types are jurisdiction-specific.

Write a cold or warm-intro email to an investor that actually gets a reply — short, specific, traction-forward, with a clear ask. Use when asked to email an investor, write a fundraising outreach, request a warm intro, or craft a forwardable blurb. Produces a tight cold email, a forwardable intro blurb a mutual contact can paste, and the follow-up — all skimmable on a phone.

Build the narrative and slide structure for an investor pitch deck. Use when asked to create a pitch deck, investor presentation, fundraising deck, or startup pitch. Produces a slide-by-slide structure with narrative beats, key messages, and what each slide must prove to an investor.

Write a structured monthly or quarterly investor update. Use when asked to write an investor update, investor newsletter, board update, or startup progress report for investors. Produces a clear, credible update with highlights, metrics, challenges, and asks — in the format investors actually want to read.

Create a professional, complete invoice for a client or customer. Use when asked to write an invoice, create a bill, draft a freelance/contractor invoice, or set up an invoice template. Produces a clear invoice — your and the client's details, a unique number, line items with quantities/rates, subtotal/tax/total, payment terms and methods, and due date — ready to send and easy to pay. Not tax/legal advice.

Look up IP addresses and your own public IP with zero API keys — geolocation, ISP/ASN, and hosting flags via ip-api.com and ipify through curl. Use when asked what's my public IP, where is this IP from, whose network is this address, or is this IP a VPN/datacenter. Produces the lookup with ISP, ASN, and location fields interpreted honestly (city-level accuracy caveats included), and the rerunnable command.

Get an honest verdict on whether something you made is actually good — not the reflexive 'this is great!' but a real, criteria-based judgment. Use when asked is this actually any good, be honest is this good enough, rate this honestly, or don't just say it's great. Produces a grounded assessment against real standards for the format, a clear verdict (great / good / fine / not there yet), the specific things holding it back from the next level, and what it would take to get there — deliberately overriding AI's flattery default.

Scope an ISO 27001 ISMS and build the Statement of Applicability across Annex A controls. Use when asked to implement ISO 27001, scope an ISMS, build a Statement of Applicability (SoA), or prepare for ISO 27001 certification. Produces an ISMS plan — scope & context, risk-treatment approach, an Annex A control applicability table (the SoA), and a prioritised implementation roadmap.

Track the International Space Station live with keyless curl — where it is right now, what it's over, and when to look up, with the orbital math translated into human terms. Use when asked where is the ISS right now, is the space station overhead, when can I see the ISS tonight, or track the station for the kids. Produces the live position translated to a place name, the overhead-math explained, the visibility rules of thumb, and the rerunnable command — the library's proof that live data can also just be delightful.

Triage the user's REAL issue tracker — read open issues via the GitHub/Linear connector, label / prioritise / dedupe / flag them, and apply the safe changes — not advice on triage. Use when asked to triage my issues, clean up the backlog, label and prioritise open issues, or sort my GitHub issues in Cowork. Reads open issues via the connector, classifies by type / severity / duplicate, applies labels and priorities, and produces a triage-report artifact with the applied changes and the ones needing a human call.

Decode a job description to find what they actually want beneath the buzzwords. Use when asked to analyse a job description, decode a JD, assess fit for a role, or figure out what a posting really means before applying. Produces a decode — the real must-haves vs. nice-to-haves, hidden priorities & culture signals, red flags, an honest fit assessment, and the exact phrases to mirror in your application.

Tailors a CV and cover letter to a specific job description. Use when asked to write a cover letter, tailor a CV or resume, optimise for ATS, match a job description, or prepare a job application. Produces an ATS-optimised tailored CV summary and a personalised cover letter aligned to the role's requirements.

Write a clear, inclusive, and structured job description for any role. Use when asked to write a job description, job posting, JD, or job advert. Produces a complete JD with role summary, responsibilities, requirements, and inclusive language review.

Run a job search when you have a criminal record — where to apply, when and how to disclose, and how to turn the question into a short, confident answer instead of a dealbreaker. Use when asked how do I get a job with a felony, when do I tell an employer about my record, ban-the-box, or explain my conviction in an interview. Produces a target list of record-friendly employers and roles, a disclosure timing plan, a tight honest disclosure script (own it, pivot to now), answers to the background-check and gap questions, and the rights that protect you — so a record narrows the search without ending it. Not legal advice; points to reentry and legal-aid resources.

Write Jobs-to-be-Done (JTBD) job stories and map customer jobs across functional, social, and emotional dimensions. Use when defining user needs, writing job stories, conducting JTBD research, or reframing features around customer outcomes. Produces a job story map with opportunity scoring, pain intensity ratings, and product opportunity analysis.

Get journaling prompts tuned to what you're actually working through — a decision, a rough patch, a goal, or just building the habit — not generic 'how was your day'. Use when asked for journaling prompts, help me start journaling, writing prompts for [situation], or what should I journal about. Produces a small set of prompts matched to your intent, a simple format and cadence that fits your time, a starter for total beginners, and a gentle note on going deeper vs. when a topic is better taken to a professional.

Understand a jury-duty summons and handle it right — what's required, whether you can defer or be excused, and what to expect on the day. Use when asked what do I do about jury duty, can I get out of jury duty, jury summons help, or how does jury service work. Produces a plain-English read of the summons and obligations, the legitimate deferral/excusal/hardship options and how to request them, what to expect at selection and service, practical prep (work, pay, logistics), and a clear warning that ignoring a summons has consequences. Not legal advice.

Handle a jury summons calmly — confirm it's real, understand what's actually required, request a deferral or excusal the right way if you genuinely need one, arrange work and pay, and know what to expect on the day. Use when someone says 'I got a jury summons', 'can I get out of jury duty', 'how do I defer jury service', or 'what happens at jury duty'. Produces a response plan, a deferral/excusal request if warranted, and a what-to-expect brief. Routes to the court for anything binding; never coaches dodging a legal obligation.

Pick the karaoke song that actually fits your voice and the room — so you land it instead of dying on a key change. Use when asked what karaoke song should I sing, pick me a karaoke song, what should I sing for [occasion], or a song for my voice. Produces a few tailored song picks matched to your range and skill, why each works (and the tricky bit to watch), a crowd-pleaser vs a show-off pick, a group/duet option, and a safe fallback for when nerves hit.

Build an age-appropriate online-safety plan for a child — the settings, the agreements, and the conversations — that protects without just spying or banning everything. Use when asked to keep my kid safe online, parental controls setup, my child's online safety, or screen rules for kids. Produces an age-tuned plan covering device/platform settings, a family agreement, the ongoing conversations that matter more than any filter, warning signs to watch for, and how to respond to trouble — balancing safety with trust and independence.

Audit a knowledge base / help center for coverage, accuracy, and findability. Use when asked to audit a help center, review KB health, find documentation gaps, reduce ticket volume with better docs, or prioritise what to write/fix. Produces an audit — a health scorecard, content gaps (driven by top ticket drivers), stale/duplicate/low-findability articles, and a prioritised fix-and-create backlog.

Keep a team knowledge base alive — the gardener role and its weekly half-hour, the rot signals (stale pages, orphans, duplicates) and their fixes, the capture funnels that feed the garden, and the pruning that keeps search useful. Use when asked our wiki is a graveyard, who maintains the knowledge base, set up knowledge management that lasts, or people can't find anything anymore. Produces the gardener rotation, the weekly tending routine, the rot triage, and the capture funnels.

Map what you don't know about a subject — including the gaps you can't see — so your learning targets the holes instead of re-covering what you already know. Use when asked what don't I know about X, find my knowledge gaps, what should I learn next in, or map my understanding of. Produces a picture of the subject's territory, what you already know vs the gaps, the dangerous unknown-unknowns (things you don't know you're missing), which gaps matter most for your goal, and a prioritized learn-next list — so effort goes where it counts.

Design a KPI tracker that drives decisions instead of decorating them — the few-metrics discipline (5–9, each with an owner and a so-what), targets with honest baselines, the trend-first layout, and the review ritual where the tracker actually gets used. Use when asked set up KPI tracking for the team, build a metrics dashboard in sheets, which numbers should we track, or our dashboard exists but nobody acts on it. Produces the metric selection with kill-list, the tracker structure, the target-setting notes, and the review ritual.

Write an internal KYC/AML escalation memo: a factual time-stamped trigger description, customer-profile vs activity mismatch analysis, red-flag taxonomy mapping, outstanding information, and a recommendation with rationale. Use when asked to escalate a KYC alert, document an AML concern, write up unusual-activity findings for compliance review, or prepare an enhanced due diligence referral. Produces a structured internal escalation memo for a compliance team's decision-makers.

Write full landing-page copy that converts — section by section. Use when asked to write a landing page, homepage copy, a product page, or copy for a marketing site. Produces complete copy for every section (hero, problem, solution, social proof, features-as-benefits, objections/FAQ, final CTA) with a clear single conversion goal and one primary call to action.

Build a realistic plan to learn a language for your actual goal — travel, conversation, work, or fluency — focused on what moves the needle instead of endless app streaks. Use when asked to help me learn [language], make a language learning plan, how do I get conversational, or study a language efficiently. Produces a goal-and-level read, a prioritized plan (the high-frequency vocab and core patterns first), a daily/weekly routine mixing input, speaking, and review, how to get real practice and feedback, milestones, and honest expectations — not a promise of fluency in a month.

Searches Reddit, X/Twitter, and the broader web for recent opinions, sentiment, and signal on any topic. Use when you need to know what real people are saying about a tool, product, trend, or event in the past 30 days — cutting through SEO content to surface genuine community reaction. Produces a structured report with consensus findings, pain points, positive signals, contrarian takes, source links, and a signal confidence rating.

Turn your notice period into a handoff that makes you missed for the right reasons — the transition doc nobody has to call you about, the knowledge-transfer sessions, and the graceful goodbye mechanics. Use when asked I just resigned how do I hand off my work, write my transition document, plan my last two weeks, or what do I do before I leave my job. Produces the handoff inventory, the transition doc template filled with your reality, the KT session plan, and the last-day checklist.

Collect overdue invoices with a graduated escalation ladder — friendly nudge to firm notice to work-stop to final demand, each with send-ready wording and timing, plus the prevention terms that stop the next one. Use when asked my client hasn't paid me, write a payment reminder email, invoice is 60 days overdue what do I do, or client is ghosting my invoices. Produces the situation read, the escalation ladder with dates and verbatim messages, the work-stop decision point, and the payment terms that prevent reruns.

Chase an overdue invoice and actually get paid — a firm-but-friendly escalation ladder that protects the client relationship until it's clear the relationship is the problem. Use when asked to chase an unpaid invoice, my client hasn't paid, write a payment reminder, or how do I get a late-paying client to pay. Produces a staged sequence of messages (gentle nudge → firm reminder → final notice → next steps) timed to the overdue days, with late-fee and work-pause options and a note on what to keep for the record.

Write a developer-audience launch post — Show HN, a Product Hunt blurb, a 'we shipped X' dev blog intro, or a launch tweet thread. Use when launching a tool, library, API, or open-source project to a technical audience. Produces a credible, hype-free post that leads with what it does and why it's different, plus title options and a comment-ready first reply.

Assesses pre-launch readiness across every function and produces an explicit Go / Conditional Go / No-Go recommendation. Use when preparing for any product or feature launch, running a pre-launch review, or determining whether a release is safe to ship. Produces a function-by-function readiness status, a ranked blockers list with owners and deadlines, a risk register, and a clearly reasoned launch recommendation.

Tier a product launch (T1/T2/T3) and scope the right go-to-market effort. Use when asked to decide a launch tier, right-size launch activities, build a launch tiering framework, or plan channels and effort proportional to a launch's impact. Produces a tiering recommendation with the scoring rationale, the activities and channels for that tier, owners, and a lightweight launch checklist.

Write the layoff communications a leader has to get right once — the all-hands script, the affected/unaffected messages, and the external note, without corporate euphemism or legal risk. Use when asked to write a layoff announcement, communicate a RIF, tell the team about job cuts, or draft the difficult all-hands. Produces the full comms set: leader script, same-hour messages for affected and remaining staff, manager talking points, and the external statement — sequenced.

Plan and write the communications for a layoff or restructure with clarity and dignity. Use when asked to communicate a layoff, write a RIF/redundancy announcement, prepare manager talking points for letting people go, or plan workforce-reduction comms. Produces a comms package — sequencing plan, the all-hands/company message, the affected-employee message, a manager guide with talking points, a staying-team message, and an external/press holding line.

The first-72-hours money plan after a layoff — runway computed, deadlines caught, bleeding stopped, in priority order. Use when asked I just got laid off what do I do about money, build my layoff budget, how long can I last, or what needs to happen this week. Produces the runway number, the deadline list (healthcare, unemployment filing, equity exercise windows), the spending triage, and a one-week action checklist.

Steady the first 72 hours after being laid off — the practical, financial, and emotional moves in the right order, before panic-applying to everything. Use when asked I just got laid off what do I do, help me after a layoff, I lost my job, or just got made redundant. Produces a calm first-days checklist (understand the severance/package, protect benefits and finances, secure references and contacts, file for support), what to negotiate before signing anything, an emotional-footing note, and a bridge into the job search — not a frantic same-day scramble. Not legal or financial advice.

Design a real project to learn a skill by building something — the fastest way to actually get good, instead of endless tutorials. Use when asked I'm stuck in tutorial hell, what project should I build to learn, learn by doing, or a project to practice X. Produces a project scoped to your level that forces the skills you want to learn, a breakdown into buildable milestones, the specific skills each milestone teaches, where to get help without copying, and a stretch to grow into — because you learn a skill by using it on something real, not by watching more tutorials.

Turn 'I want to learn X' into a realistic, staged roadmap — the fundamentals to master first, the order that avoids overwhelm, and the milestones that prove progress. Use when asked how do I learn [skill], make me a learning plan for, where do I start with learning, or roadmap to learn X. Produces a staged path from beginner to capable (fundamentals → building blocks → real application), the highest-leverage things to learn first, the traps and dead-ends to skip, milestones to measure progress, and the best resource types for each stage — tuned to your goal and time.

Decode a residential lease into plain English and rank the clauses that can hurt you. Use when someone asks 'what am I signing', 'decode my lease', 'is this rental agreement normal', or 'can my landlord really do this'. Produces a clause-by-clause decode table, ranked red flags, break-clause and deposit math, questions to ask before signing, and what's actually negotiable.

Write a letter to the people you love, to be read later — the things you'd want them to know, the stories only you hold, the permission and the love that outlive you. Use when someone says 'help me write a letter to my kids/partner', 'legacy letter', 'ethical will', 'something for them to have when I'm gone', or is facing illness, aging, deployment, or simply wants to. Produces a warm, true letter in the writer's own voice — one to each person, or one to all — plus a light plan for when and how it's found. An emotional-legacy tool, not legal (it is not a will).

Draft a structured legal brief, case summary, or legal argument outline. Use when asked to write a legal brief, case note, legal memo, argument outline, or position paper. Produces a structured document using IRAC format (Issue, Rule, Application, Conclusion).

Figure out whether your problem car might qualify for a refund or replacement under lemon law or warranty — and build the paper trail to claim it. Use when asked is my car a lemon, my new car keeps breaking, lemon law help, or can I return a defective car. Produces a plausibility read against typical lemon-law criteria (repeated same defect, repair attempts, time out of service, warranty window), the records to gather, the manufacturer-claim and escalation steps, and a strong flag that lemon laws are jurisdiction-specific. Not legal advice.

Write a portfolio-level lending risk brief: concentration analysis by sector, geography and single name, vintage performance, migration matrix narrative, macro-sensitivity scenarios, top watch names, and actions. Use when asked to write a portfolio risk report, credit risk committee brief, loan book review, or quarterly portfolio quality update. Produces a structured risk brief with concentration tables, migration narrative, scenario read, watch list, and recommended actions.

Build a complete, standards-aligned lesson plan with clear objectives, a timed activity sequence, differentiation, and assessment. Use when asked to write a lesson plan, plan a class or lesson, design a teaching session, or structure instruction for a topic. Produces a ready-to-teach plan with measurable objectives, a minute-by-minute flow, materials, checks for understanding, and differentiation for varied learners.

Build a standards-aligned K-12 lesson plan with clear objectives, a timed activity sequence, checks for understanding, and differentiation. Use when asked to plan a lesson, write a lesson plan, align a lesson to a standard, or turn a topic into a class period. Produces measurable objectives, a bell-to-bell timeline (hook → instruction → practice → close), formative checks, differentiation for varied learners, and the materials list.

Write the failure story of your year, relationship, move, or big life bet in advance — imagine it's a year later and it went wrong, tell that story vividly, then mine it for the real risks and the cheap things that would have prevented them. Use when someone says 'I'm about to make a big life change', 'what could go wrong with this', 'de-risk my year', or is committing to something large and irreversible. Produces the failure narrative, the extracted risk list with preventatives, and the early-warning signs to watch. The life-scale sibling of a project premortem.

Design lifecycle marketing / CRM journeys across the customer lifecycle. Use when asked to plan onboarding emails, lifecycle/CRM campaigns, drip sequences, re-engagement or winback flows, or a messaging calendar. Produces a lifecycle plan — stage map, the trigger/message/goal for each journey, channel & timing, segmentation, suppression rules, and success metrics.

Optimise a LinkedIn profile to be found and to convert. Use when asked to write or improve a LinkedIn headline, About section, or profile, or to make a profile recruiter-friendly. Produces an optimised headline, a first-person About section with a hook and keywords, achievement-led experience bullets, and a skills/keyword list tuned for LinkedIn search.

Structure and write a literature review for any research topic. Use when asked to write a literature review, systematic review summary, narrative review, or research background section. Produces a structured review with thematic organisation, critical analysis, and gap identification.

Structure a literature review that argues, not lists — thematic synthesis from your sources with the debate mapped and the gap identified. Use when asked to write or structure a literature review, organize my sources, synthesize these papers, or find the gap for my thesis. Produces a themed review skeleton with your sources placed in conversation, the points of scholarly disagreement, the gap your work addresses, and an honest register of what you haven't read yet.

Model the cost and latency of an LLM feature before it ships and surprises the bill. Use when asked to estimate LLM API costs, set a latency/token budget, decide which model tier to use, or bring down the cost of an AI feature. Produces a cost & latency budget — token math per request, monthly cost projection, model tiering, caching/streaming levers, p95 latency targets, and a guardrail/alert plan.

Specify the safety and reliability guardrails for an LLM feature before it ships. Use when asked to define LLM guardrails, add safety controls to an AI feature, prevent prompt injection or jailbreaks, or harden a chatbot/agent against misuse. Produces a guardrails spec — threats, input/output controls, refusal and escalation policy, logging, and a red-team test set — mapped to where each control runs.

Write a load and performance testing plan for a service. Use when asked to create a performance test plan, write load testing documentation, define stress or soak test scenarios, or set performance regression gates for CI. Produces a complete test plan document with scenario definitions, k6/Locust script skeleton, threshold table, result interpretation guide, and CI integration steps.

Run a quarterly loan covenant compliance review: covenant table with required vs actual vs headroom, trend and trajectory-to-breach analysis, waiver and amendment options with pricing implications, early-warning indicators, and a watch-list recommendation. Use when asked to review covenant compliance, check covenant headroom, assess a potential covenant breach, or prepare a quarterly borrower monitoring review. Produces a structured covenant review with headroom table, trajectory analysis, and recommended actions.

Decode a personal, auto, or mortgage loan offer into what it really costs and where the traps are. Use when someone asks 'is this loan a good deal', 'decode my loan offer', 'what am I signing', or 'what will this mortgage actually cost me'. Produces a total-cost-of-loan number, APR vs advertised-rate reconciliation, ranked red flags (prepayment penalties, junk fees, rate-reset exposure), and the three questions that most change the deal.

Write a local development environment setup guide for a service or project — covering prerequisites, repository setup, environment variables, local service dependencies, database seeding, running the service, running tests, common gotchas, IDE recommendations, and first-contribution checklist. Use when asked to write a dev setup guide, create onboarding documentation for engineers, document local environment setup, or write a getting-started guide for a codebase. Produces a complete setup guide that a new engineer can follow from zero to running tests in under 30 minutes, with a troubleshooting section for the most common setup failures.

Plan the localization of a product/content for a new market — beyond translating the words. Use when asked to localize a product, plan market entry localization, prepare a localization brief, or figure out what to adapt for a new region. Produces a brief — target locales, what to translate vs. adapt vs. rebuild (UI, content, formats, imagery, payments, legal), priorities, and the risks/cultural pitfalls.

Write up a supply chain disruption — port delay, carrier failure, customs hold, or in-transit damage — as a decision-ready incident report. Use when asked to document a shipment delay, write up a logistics failure, report a customs hold, quantify a supply disruption, or draft the customer notice for a late delivery. Produces an impact-quantified incident report with containment actions, root cause, prevention items, and a customer-communication draft.

Build a plan to keep a long-distance relationship close and healthy — communication rhythms, visits, shared experiences, and a shared sense of the finish line. Use when asked to help with a long-distance relationship, how to make LDR work, we're going long distance, or keep our relationship strong apart. Produces a communication rhythm that fits both schedules and time zones, ideas for shared experiences across the distance, a visit and cost plan, ways to handle the hard parts (jealousy, loneliness, resentment), and an honest 'the plan' conversation about the end goal.

Understand the long-term care options for an older or ill loved one — from in-home care to assisted living to nursing care — so you can compare them for your situation. Use when asked what are the care options for my parent, in-home care vs assisted living vs nursing home, help me choose a care option, or explain long-term care. Produces a plain-English explainer of the main care levels and what each is for, a match to the person's needs (care level, budget, preferences), the key questions and red flags when evaluating providers, cost and funding considerations to research, and how to involve the person in the decision — a map for one of the hardest, most emotional decisions a family makes. Not medical or financial advice.

Help you write a heartfelt letter to someone you love — for an anniversary, a hard time, a birthday, or just because — that sounds like you and says what you actually mean. Use when asked to help me write a love letter, say how I feel to my partner, a heartfelt note for [occasion], or I'm not good with words. Produces a letter built from your real feelings and specifics, a structure that carries emotion without cheese, the right tone for your relationship and occasion, and phrasing in your own voice — with prompts to draw out what you want to say if you're stuck.

Negotiate a recurring bill down — internet, phone, insurance, cable, gym — with a ready-to-read script, the competitor leverage that actually moves the price, and exactly what to say when they say no. Use when asked to lower my bill, negotiate my internet/phone bill, my provider raised my price, or how do I get a discount on [service]. Produces a call-or-chat script in your words, the specific leverage for your situation, a fallback ladder (discount → downgrade → cancel lever), and a note of what to write down so the promised deal actually sticks.

Analyse a workplace power situation the way Machiavelli's The Prince (1532) would — who holds power, whose support you need, what fortune can take from you — then give both the Machiavellian read and the honest modern counterweight. Use when navigating a reorg, a new leader arriving, stakeholder politics, a territory dispute, or 'my project is caught in politics'. Produces a power map, a Machiavellian assessment, and an ethical playing-it-straight plan.

Get an open-source repo's issue backlog from 400-and-drowning to triaged-and-honest in one pass — a label taxonomy that encodes decisions, batch triage rules you can apply in seconds per issue, saved replies that stay kind at scale, and stale-bot policy set with a conscience. Use when a maintainer says 'my issues are out of control', 'triage my backlog', 'set up labels for my repo', or dreads opening GitHub. Produces the taxonomy, the triage pass rules, saved replies, and a sustainable weekly routine.

Build a real plan to make friends as an adult — where to meet people you'd actually click with, how to turn acquaintances into friends, and past the awkwardness. Use when asked how do I make friends as an adult, I'm lonely and want more friends, help me build a social life, or I have no friends here. Produces a read on where to meet the right people for you (shared interests + repeated exposure), the specific move that converts acquaintances to friends (initiate + consistency + vulnerability), a low-pressure action plan, and reassurance that the awkwardness is normal — because adult friendship doesn't happen by accident, it's built.

Turn a task you repeat every week into a reusable personal skill or prompt — so you say 'do this' instead of re-explaining it every time. Use when asked help me make a skill for, turn this repetitive task into a template, I do this every week, or create a reusable prompt for this. Produces a captured spec of the repetitive task (its inputs, steps, and what good output looks like), a reusable skill/prompt you can invoke by name, and guidance on saving and refining it — lowering the barrier from AI user to AI author, one weekly task at a time.

Plan a new manager's first 90 days — first-time or new-to-team — as listen/decide/move phases: the 1:1 listening tour with real questions, the early-judgment traps, the quick-wins filter, and the 30/60/90 artifacts. Use when asked I just became a manager what do I do, plan my first 90 days as a manager, taking over an existing team, or new manager 30-60-90 plan. Produces the phased plan, the listening-tour question set, the team assessment framework, and the day-one and week-6 artifacts.

Work more effectively with your manager — communicate, align, escalate, and get what you need. Use when asked how to manage up, work better with a boss, get buy-in from your manager, escalate without overstepping, or prepare to raise something with leadership. Produces a managing-up plan — what your manager needs and how they operate, how to frame your ask, what to bring vs. escalate, and the message.

Plan a full-funnel marketing strategy from awareness to retention. Use when asked to build a marketing funnel, map the customer journey to tactics, plan demand generation, or diagnose where a funnel leaks. Produces a funnel plan — stage definitions, the metric and conversion target per stage, channels & tactics, the biggest leak, and a 90-day focus.

Apply behavioral-psychology principles to a marketing asset or decision — ethically. Use when asked to make copy/a page/an offer more persuasive, apply psychological triggers, reduce friction, or understand why something does/doesn't convert. Produces the relevant principles (social proof, scarcity, anchoring, loss aversion, etc.), how to apply each to the specific asset, and a line on staying ethical (no dark patterns).

Audit and optimize a marketplace listing (Amazon, Etsy, eBay, Walmart) to rank and convert. Use when asked to optimize an Amazon/Etsy listing, improve marketplace SEO, fix a product listing that isn't selling, or write keyword-rich titles and bullets. Produces a prioritised optimization — title, bullets, backend keywords, A+/description, images plan, and conversion fixes — mapped to how that marketplace ranks and shoppers decide.

Treat neurodivergent masking as a daily energy budget — audit what passing as neurotypical actually costs you, where the spend is worth it, where you can safely drop the mask, and how to plan a heavy-masking day so you don't crash after. Use when someone says 'I'm exhausted from masking', 'work drains me and I don't know why', 'how do I unmask safely', or is autistic/AuDHD/ADHD and burning out socially. Produces a mask-cost audit, a spend/drop map, and a recovery plan. A self-knowledge tool, not a diagnosis or therapy.

Design an MCP server for a product — the tool surface, auth model, and safety boundaries that make it genuinely usable by AI agents. Use when asked to spec an MCP server, expose a product to agents, design tools for Claude or other MCP clients, or review why an existing MCP server performs badly. Produces a complete server spec: a small task-shaped toolset with agent-tested descriptions, auth and scoping decisions, error design, and an explicit not-exposed list.

Turn what's actually in the fridge and 90 minutes on Sunday into a week that mostly feeds itself — a cook-once-eat-thrice batch plan, the component method (bases, proteins, sauces that recombine so leftovers don't bore you), honest food-safety day-counts flagged, and the Thursday problem solved in advance. Use when someone says 'meal prep my week', 'what do I cook with what I have', 'we spend too much on takeaway', or 'I'm sick of eating the same thing four days'. Produces the Sunday cook plan, the recombination map, and the shopping delta.

Read a garage quote or invoice like someone who can't be padded — which line items connect to your actual symptom, which are while-we're-in-there additions, the questions that make soft lines disappear, when a second opinion pays for itself, and the scripts for declining work without souring the relationship. Use when someone says 'is this mechanic quote fair', 'the garage called and now it's £900', 'do I really need all this', or before authorizing repairs. Produces a line-by-line decode, the callback questions, and the authorize/decline/second-opinion sort. Not a diagnosis — it's the interrogation of one.

Write a media pitch or press outreach email for any story or announcement. Use when asked to write a media pitch, journalist outreach email, press pitch, or story angle for PR. Produces a concise pitch with a compelling news angle, journalist-specific hook, and clear call to action.

Decode an itemized medical bill or EOB into plain English and find the charges worth disputing. Use when someone asks 'why is my medical bill so high', 'decode my hospital bill', 'what is this EOB saying', or 'can I negotiate this bill'. Produces a line-by-line decode, duplicate and unbundling flags, balance-billing red flags, and ready-to-read scripts for requesting an itemized bill, financial assistance, and a negotiation call.

Request your medical records and actually get them — what to ask for, the request letter that can't be shuffled aside, the timelines and fee rules to cite (jurisdiction-flagged), and the escalation path for stonewalls. Use when asked how do I get my medical records, write a records request, my doctor's office won't send my records, or what records should I collect. Produces the itemized request letter, the delivery and format choices decoded, the follow-up ladder, and the personal health-file structure for keeping them.

Prepare to get the most out of a medical appointment — for yourself or someone you care for — with the right questions, the information to bring, and how to make sure you're heard. Use when asked help me prepare for a doctor's appointment, questions to ask the doctor, advocate for my parent at the doctor, or how do I get the most from this appointment. Produces a focused list of what to raise and ask (prioritized, since time is short), the history and info to bring, note-taking and 'teach-back' tactics so you actually understand, how to speak up if dismissed, and what to confirm before leaving — not medical advice, but better navigation of care.

Set up a system to manage medications safely — for yourself or someone you care for — so doses aren't missed, doubled, or dangerously combined. Use when asked help me manage medications, keep track of my parent's pills, set up a medication system, or I keep forgetting my meds. Produces an organized medication list (what, dose, when, why), a routine and reminder setup that fits the person, a refill-tracking method so nothing runs out, safety checks (interactions and duplications to raise with a pharmacist), and an emergency-ready summary — because medication errors are common and dangerous, and a system prevents most of them. Not medical advice.

Pull the action items and decisions out of meeting notes or a transcript — each with an owner, a due date, and enough context to become a ticket — plus the open questions. Use when asked to extract action items, turn these notes into tasks, who owns what from this meeting, or pull the to-dos from this transcript. Produces the ticket-ready action list (owner + due + context), the decisions made, the open questions with no owner yet, and a flag for any 'someone should…' that never got assigned.

Price meetings in money and focus — the attendee-hours × loaded-rate math, the recurring multiplier that turns a weekly 30-minutes into a real annual number, and the cost-vs-outcome read that decides what the price buys. Use when asked what does this meeting cost, price our meeting culture, is this recurring meeting worth it, or make the case for fewer attendees. Produces the cost computation with stated assumptions, the recurring annualization, the cost-per-outcome read, and the reduction levers ranked.

Structure and format meeting notes following PM best practices. Use when asked to create meeting notes, format discussion notes, capture action items, or document decisions from any meeting type. Produces structured notes with decisions, action items (owner + deadline), open questions, and next steps.

Prepare the user for a REAL upcoming meeting by pulling the actual Calendar event, its attendees, the linked Drive docs, and the last email/Slack thread — then producing a brief. Use when asked to prep me for my next meeting, get me ready for the 2pm, or what do I need for the sync with X in Cowork. Reads the event via the Google Calendar connector, gathers the attached and related material via Drive/Gmail, and produces a one-page meeting-brief artifact with objective, context, open threads, and the questions to ask.

Arrive at a meeting armed in fifteen minutes — the prep pack: what this meeting decides, your position with its reasons, the other attendees' likely stances, the questions to ask, and the outcome you're steering toward. Use when asked prep me for this meeting, what should I know before this call, I have 15 minutes before a big meeting, or help me not wing it. Produces the one-page prep pack with position, stances, questions, and the walk-away-with list.

Set the shared-space norms that end the small daily frictions — meeting room booking discipline (the ghost-booking cure), hybrid-call room behavior, the shared kitchen/space contracts, and the enforcement that works without a hall monitor. Use when asked set office space norms, rooms are always booked but empty, hybrid meetings are terrible for remote people, or write the office etiquette guide. Produces the norms card by space type, the ghost-booking fix, the hybrid-room checklist, and the no-hall-monitor enforcement design.

Build your personal early-warning system for meltdowns or shutdowns — your specific rising signs, the triggers that stack, what actually helps at each stage, and a plain plan you can hand to the people around you. Use when someone says 'my meltdowns come out of nowhere', 'help me not shut down', 'I need a plan for when I'm overwhelmed', or supports someone who melts down or shuts down. Produces a staged warning map, a per-stage response plan, and a shareable one-pager. A self-management tool — not a clinical or crisis service.

Capture a life story — your own or a parent's/grandparent's — into a keepsake, using good interview questions and a structure that turns memories into readable stories. Use when asked to help write a memoir, capture my parent's/grandparent's story, record family history, or preserve someone's life story. Produces a question set that unlocks real memories (not just dates), a session plan for interviewing over time, a structure to organize stories into chapters or themes, prompts to draw out detail and emotion, and options for the final form — so the stories are saved before they're lost.

Keep your AI memory/context file (MEMORY.md, CLAUDE.md, custom instructions) healthy over time — pruning the stale, adding the new, and keeping it sharp so your AI keeps getting you right. Use when asked review my memory file, my AI context is outdated, clean up my CLAUDE.md, or maintain my AI instructions. Produces a review of your existing memory/instructions file (what's stale, contradictory, bloated, or missing), edits to prune and sharpen it, additions from recent patterns worth remembering, and a light maintenance habit — because a memory file that isn't tended drifts from who you actually are, with a privacy check on what should never be stored.

Cost a menu item to a plate cost and food-cost percentage, then price it for a target margin. Use when asked to cost a dish, calculate food cost percentage, price a menu item, or engineer a menu for profitability. Produces a plate-cost breakdown (ingredient × yield × price), the food-cost %, a suggested price for the target margin, and menu-engineering flags (star / plow-horse / puzzle / dog) so the operator knows what to promote, reprice, or cut.

Write the short message you freeze on — a thank-you, condolence, congratulations, apology, or a graceful 'no' to an invite — warm, specific, and in your own voice. Use when asked to write a thank-you note, a sympathy/condolence message, a congratulations, a quick apology, or how to politely decline. Produces two or three ready-to-send options at the right length for the channel, plus the one line that carries the message, never generic filler.

Build a messaging framework (message house) that the whole company can use consistently. Use when asked to create messaging, a value proposition, a message house, key messages, or to make marketing/sales/product say the same thing. Produces a messaging framework — audience & value proposition, the one-line positioning, 3 message pillars with proof points, objection handling, and a words-we-use/avoid list.

Find out how a dashboard, KPI report, or metrics slide is lying to you — before you repeat its story in a bigger room. Use when numbers feel too tidy, a narrative rests on one chart, or you inherited metrics you didn't define. Produces a deception audit: every metric graded for the eleven classic distortions (denominator games, survivorship, y-axis crimes, cherry-picked windows…), the story the data would tell under honest framing, and the three questions to ask the metric's owner.

Define a metric in a semantic layer so it means one thing everywhere. Use when asked to define a metric, build a semantic layer / metrics layer entry, stop 'revenue means three things' problems, or write a metric definition for dbt MetricFlow / Cube / LookML. Produces a metric definition — exact formula, the base measure & aggregation, dimensions, filters, grain, edge cases, and a tool-ready spec.

Decompose a north-star metric into a driver tree — the inputs and sub-inputs that actually move it — so a team knows which levers to pull. Use when asked to build a metric tree, break down a north-star metric, map metric drivers, or find the inputs behind an output metric. Produces a hierarchical tree from the top metric down to actionable input metrics, with the relationships, the highest-leverage levers, and what to instrument.

Build a metrics framework for any product, team, or business. Use when asked for a metrics tree, KPI framework, North Star metric, AARRR funnel, HEART framework, or OKR metrics. Produces a structured metrics hierarchy from North Star down to leading indicators, with measurement guidance.

Plan a deliberate career break — 3 to 12 months off between chapters — with honest runway math, the re-entry story rehearsed before you leave, health/visa/pension admin by country flagged, and kill criteria for coming back early. Use when someone says 'I want to take 6 months off', 'micro-retirement', 'sabbatical planning', 'quit and travel', or 'can I afford a break'. Produces a runway budget, a break charter with kill criteria, and the future-interview answer written in advance.

Write the small UI text that guides users — buttons, labels, tooltips, CTAs, confirmations. Use when asked to write microcopy, button/CTA text, form labels, tooltips, helper text, or to make UI wording clearer. Produces specific, action-oriented microcopy with options and rationale, matched to the moment and the product's voice — concise, scannable, and free of jargon.

Design a microservices decomposition for a monolith or new system, defining service boundaries, ownership, communication patterns, and migration plan. Use when asked to decompose a monolith, define service boundaries, design a microservices architecture, or plan a strangler-fig migration. Produces a bounded context map, service inventory table, communication pattern decisions, data ownership matrix, migration roadmap, and risk register.

Move a team's files to a new platform without losing work or a week — the pre-migration freeze, the verified copy, the permissions remap, the cutover announcement, and the old-system read-only afterlife. Use when asked we're moving from Dropbox to Drive, migrate our files to SharePoint, plan the file migration day, or how do we switch platforms safely. Produces the migration runbook: freeze window, copy-and-verify steps, permissions mapping, the cutover comms, and the rollback line.

Turn a topic, brainstorm, or document into a structured mind map. Use when asked to brainstorm around a theme, organize ideas, break a topic into branches, or summarize something as a mind map. Produces a ready-to-render Mermaid mindmap (renders live, exportable as PNG/SVG) plus a short note on the structure chosen.

Document a deployed ML/AI model so others can use it responsibly. Use when asked to write a model card, document a model's intended use and limitations, or prepare an AI model for review/launch. Produces a complete model card — intended use, training data, evaluation metrics across slices, limitations, ethical considerations, and a deployment checklist.

Plan the migration of an LLM feature from one model to another without breaking production. Use when a model is being deprecated, a newer model looks better or cheaper, or when asked how to upgrade models safely, run shadow traffic, or set rollback criteria for a model change. Produces a phased migration plan with eval gates, shadow/canary stages, prompt-adaptation notes, and rollback triggers. For choosing which model in the first place use model-selection-advisor.

Choose the right LLM for a task by trading off quality, cost, latency, and constraints. Use when asked which model to use, whether to upgrade/downgrade a model, how to cut LLM costs without hurting quality, or to justify a model choice. Produces a recommendation with the decision criteria, a per-option comparison, a routing strategy (cheap-by-default, escalate when needed), and how to validate the choice with an eval.

Break a stuck, stalled week with three tiny wins sequenced for momentum — because motion creates motivation, not the other way around. Use when asked I'm in a rut, help me get unstuck this week, I've stalled on everything, or I need momentum. Produces three small, genuinely-achievable wins ordered so each fuels the next, a deliberately easy first one to prove motion is possible, the dopamine logic behind the sequence, and a reframe that you don't need motivation to start — starting creates it — turning a paralyzed week into a moving one.

Untangle the money beliefs and emotions that quietly sabotage your finances — the scripts from childhood, the avoidance, the guilt or fear — and reset to a healthier relationship with money. Use when asked I have a bad relationship with money, why do I self-sabotage financially, money stresses me out, or fix my money mindset. Produces a look at your money story and where it came from, the specific beliefs driving unhelpful behaviors (avoidance, overspending, scarcity, guilt), a reframe toward a healthier stance, and small behavior shifts that follow — because money behavior is often emotional, not just mathematical. Not therapy or financial advice.

Decide where your next dollar should go — the order to tackle emergency fund, high-interest debt, retirement match, and saving/investing — so you stop guessing and build momentum. Use when asked what should I do with my money first, pay off debt or save, where to put extra money, or help me prioritize my finances. Produces a personalized order-of-operations for your situation, the reasoning for each step, where you are on the ladder and the next concrete move, and honest flags on the judgment calls. Educational — not financial advice.

Write a monitoring setup guide for a service — defining what to measure, how to alert on it, and how to build the observability stack covering the four golden signals, business metrics, log strategy, distributed tracing, alerting rules, dashboard layout, and observability debt. Use when asked to set up monitoring for a service, define alerting strategy, write an observability plan, create a dashboard specification, or document logging standards for a team. Produces a metric definitions table, alert rules specification, dashboard layout wireframe, log schema, tracing setup checklist, and monitoring gap analysis.

Interviews you across 15 questions to capture your role, topics, sources, exclusions, and format preferences, then writes a master prompt you can paste into a scheduled task or Claude Code Routine. Use when you want to set up a personalised daily news brief, build a reusable morning news prompt, or create an automated intelligence briefing. Produces a confirmed summary of your preferences, a ready-to-paste master prompt, and setup instructions for both Cowork Scheduled Tasks and Claude Code Routines.

Decode a moving company estimate — binding vs non-binding, the weight and cubic-feet games, valuation vs insurance, and the red flags that precede hostage-load stories. Use when someone asks 'is this moving quote legit', 'decode my moving estimate', 'binding vs non-binding estimate', or 'how do I avoid moving scams'. Produces an estimate-type decode with what-you'll-actually-pay scenarios, ranked red flags, the valuation decode, and the questions that separate real movers from brokers.

Turn a move date into a calm, timed plan — every address change, utility switch, deposit-recovery step, and packing wave scheduled so nothing gets missed at the worst possible moment. Use when asked to plan a house move, I'm moving and don't know where to start, make a moving checklist, or what do I need to do before I move. Produces a countdown checklist by week, the address-change and utilities list, a deposit/deposit-recovery track for renters, a room-by-room packing plan, and a moving-day and first-night essentials kit — tuned to your situation.

Decode a moving-company quote and spot the lowball, the padding, and the outright scam before you book. Use when asked to check a moving quote, is this mover legit, compare moving estimates, or avoid moving scams. Produces a read on the quote type (binding vs non-binding vs 'not to exceed') and what it really means, the red flags of moving scams (big deposits, no in-home/video survey, low-then-hostage pricing), the questions to ask and credentials to verify, an apples-to-apples comparison, and how to protect yourself on moving day.

Synthesises user signals from multiple research sources into a unified, weighted insight brief. Use when you have data from interviews, support tickets, NPS verbatims, app reviews, or sales calls and need to reconcile contradictions, surface the underlying need behind requests, or answer 'what are users really telling us'. Produces ranked insights with confidence ratings, source weighting rationale, divergent signal analysis by user segment, and a research gap identification section.

Map your real energy through the day and week, then match your tasks to it — hard things when you're sharp, easy things when you're not. Use when asked when should I do my hard work, map my energy, why am I so unproductive at certain times, or schedule around my focus. Produces a picture of your energy peaks, troughs, and patterns from your own observations, a task-to-energy matching plan (deep work at peaks, admin at troughs), the traps you're currently falling into, and a realistic daily shape — because fighting your natural rhythm wastes your best hours on your worst tasks.

Turn a mistake into a reusable lesson — a short, unsentimental 'here's what happened and the rule so it doesn't happen again' entry you can actually keep. Use when asked help me learn from this mistake, I keep making the same error, capture this lesson, or turn this failure into something useful. Produces an honest, blame-free autopsy of what happened, the real root cause (not the surface one), the specific rule or trigger that prevents a repeat, and a one-line entry for your growing 'failure museum' — because unexamined mistakes repeat and examined ones compound into wisdom.

Get through the 40-institution slog of changing your name — after marriage, divorce, transition, or just because — in the right order, so one update doesn't block the next, with nothing important forgotten. Use when someone says 'I changed my name and don't know where to start', 'update my name everywhere', 'name change checklist', or is planning any legal name change. Produces an ordered update checklist (what unlocks what), a personalized institution list, and templates. Not legal advice — the logistics; the legal deed/court step is flagged, not performed.

Turn a vague bad mood or 'off' feeling into a precisely-named emotion and its likely cause — because naming it is what starts to defuse it. Use when asked I feel off and don't know why, help me figure out what I'm feeling, I'm in a weird mood, or why am I upset. Produces a short, gentle inquiry that distinguishes the actual emotion from the fog (anxious vs frustrated vs lonely vs overwhelmed), its most likely trigger, what the feeling might be pointing at, and one small thing that tends to help that specific state — never diagnosing, just helping you locate yourself.

Analyses a Non-Disclosure Agreement clause by clause and flags unusual terms, one-sided provisions, and negotiation points. Use when reviewing an NDA, mutual NDA, confidentiality agreement, or non-disclosure deed before signing or countering. Produces a plain English verdict, clause-by-clause risk analysis, and a prioritised negotiation checklist — always with a disclaimer that qualified legal advice is required before signing.

Handle a neighbor conflict — noise, boundaries, parking, shared costs, pets — with a measured approach that de-escalates first and keeps a paper trail if it has to go formal. Use when asked to deal with a neighbor dispute, my neighbor is [too loud / over the boundary / blocking me], how do I talk to my neighbor about, or write a letter to my neighbor. Produces a read on the situation, a calm first conversation or friendly note, a firmer written follow-up if that fails, the documentation habit for escalation, and the right next step (mediation / landlord / HOA / council) — steering away from making it worse.

Produce a personal net-worth statement — assets minus liabilities — and a way to track it. Use when asked to calculate net worth, summarize finances, or set up net-worth tracking. Produces a categorized assets/liabilities statement, the net-worth figure, liquidity and debt ratios, and a tracking cadence. Educational, not regulated financial advice.

Network in a way that actually works for introverts — depth over breadth, one-on-one over rooms, and energy managed — instead of forcing yourself to work a crowd. Use when asked how do I network as an introvert, networking drains me, help me network without the small talk, or introvert-friendly networking. Produces an approach that plays to introvert strengths (deep 1:1 conversations, listening, follow-up, written outreach), a plan for the events you can't avoid (arrive early, one real conversation, leave), energy-management tactics, and how to build a genuine network without pretending to be an extrovert.

Write networking messages that actually get replies — warm, specific, and easy to say yes to — for reconnecting, cold outreach, referrals, or asking for advice. Use when asked to help me network, write a message to reconnect / to a recruiter / to someone at [company], reach out for a referral, or networking message help. Produces a message tuned to the relationship and the ask, a specific and genuine hook, a low-friction request the person can easily grant, follow-up guidance, and a note on giving value — not a generic 'pick your brain' that gets ignored.

Plan your first 90 days as a new manager — build trust, learn before changing, and avoid the classic first-time-manager mistakes. Use when asked to help me as a new manager, I just became a manager, first-time manager advice, or my first 90 days managing a team. Produces a phased 90-day plan (listen and learn, then set direction, then adjust), how to run your first 1:1s, the mindset shift from doer to enabler, common traps to avoid (doing it all yourself, changing too fast, avoiding hard conversations), and early wins that build credibility.

Turn the pre-baby chaos into a staged logistics plan — leave paperwork, insurance deadlines, the hospital-bag/home-setup checklists, and the first-two-weeks operating plan with named owners. Use when asked help me prepare for a baby, what do I need to do before my due date, set up our parental leave plan, or newborn logistics checklist. Produces the countdown timeline by trimester-week, the deadline-driven paperwork list, and the week-1–2 operating plan both partners can run exhausted.

Turn 'we're having a baby' into a calm, timed logistics plan — the admin, leave, registrations, and prep that has to happen, sequenced so nothing critical is left to the newborn haze. Use when asked to plan for a new baby, what do I need to do before the baby comes, new baby checklist, or help me prepare for a newborn. Produces a trimester/countdown checklist of the non-obvious admin (leave, benefits, insurance, registration, pediatrician, essentials), what to set up before vs after birth, and a lean 'actually need it' gear list — not a fear-driven mega-list.

Turn a pile of newsletters and subscriptions into one skimmable brief — the items that matter to YOUR interests extracted with sources, the noise dropped with a count, on a cadence that replaces daily trickle-reading. Use when asked digest my newsletters, summarize what my subscriptions said this week, what did I miss that I actually care about, or make my reading pile useful. Produces the interest-filtered brief with per-item sources, the dropped-with-reasons ledger, and the cadence that makes trickle-reading obsolete.

Write a full creator newsletter issue — subject line, preview text, hook, body with a clear takeaway, and a CTA — in the writer's voice, for Substack, beehiiv, ConvertKit, or email. Use when asked to write a newsletter, an email issue, a Substack post, or to turn notes/a topic into a sendable newsletter. Produces a ready-to-send issue with subject-line options and a skimmable structure. Distinct from B2B drip/nurture sequences.

Set up a note-taking system that you'll actually use and that makes your notes findable and useful later — not a graveyard of notes you never reopen. Use when asked help me take better notes, set up a note system, my notes are a mess, or how should I organize my notes. Produces a system matched to your actual need (capture, study, or thinking), a simple capture-and-organize flow, a findability method (tags/links/structure), the review habit that keeps notes alive, and a warning against over-engineering the system instead of using it.

Automates NotebookLM from Claude Code using browser automation via the Claude Chrome extension — creating notebooks, adding sources, and triggering outputs without manual clicking. Use when you want to create a NotebookLM notebook, add URLs or documents as sources, or generate mindmaps, audio overviews, or briefing docs programmatically. Produces a confirmed checklist of completed actions and a direct link to the notebook.

Strips AI writing patterns from text and rewrites it to sound genuinely human — removing the statistical defaults, then adding earned voice calibrated to genre (opinion pieces get a person's voice; docs and summaries stay neutral) without ever faking humanity. Use when a draft reads as AI-generated, over-polished, or rhythmically uniform — including blog posts, emails, LinkedIn posts, or any prose that needs to sound like a real person wrote it. Produces a pattern audit, side-by-side comparison, itemised change log, and clean rewritten output ready to paste.

Work through who and what has to be notified after someone dies — the people, agencies, banks, and accounts — in a sane order, so nothing critical is missed while grieving. Use when asked who do I need to notify when someone dies, what to do after a death checklist, or how do I handle my parent's accounts after they died. Produces an ordered notification checklist (immediate people, then government/SSA, then financial, then subscriptions/digital), what each notification needs (death certificates, account numbers), how many death certificates to order, what to stop vs. transfer vs. close, and the scams that target the newly bereaved — so the administrative avalanche becomes a calm sequence. Not legal or financial advice; points to probate/estate resources.

Clean the user's REAL Notion database — read it, find stale/incomplete/duplicate entries, and fix them via the connector — not advice on keeping Notion tidy. Use when asked to clean up my Notion database, my tracker is a mess, find the stale and duplicate entries, or tidy my projects DB in Cowork. Reads the database via the Notion connector, audits for staleness / missing required fields / duplicates / status drift, and produces a hygiene-report artifact plus the applied fixes (with a preview-and-confirm step before any change).

Translate both directions across the neurodivergent↔neurotypical gap at work — decode what an indirect message actually meant ('let's circle back' = no), and rewrite your direct message so it lands without you having to sand off the point. Use when someone says 'what did my manager actually mean', 'my message came across wrong again', 'why do people think I'm blunt', or is ND navigating an NT workplace. Produces a decode of the received message and/or a rewrite of yours, with the reasoning shown so you learn the pattern.

Compare two or more job offers as total-comp curves over four years — vesting cliffs, bonuses, 401(k) match, and the crossover year computed, not vibed. Use when asked to compare job offers, which offer pays more over time, model my equity vesting, or is the startup offer actually worth it. Produces a year-by-year and cumulative comp table per offer, the crossover analysis, and negotiation levers ranked by dollar impact.

Draft a job offer — the written offer letter and a verbal-offer script. Use when asked to write an offer letter, a job offer, an employment offer, or to prepare to extend/verbal an offer to a candidate. Produces a clear, warm offer letter (role, comp, start, key terms, contingencies, acceptance) plus a verbal-offer call script — flagging that employment terms need HR/legal review. Not legal advice.

Replace ad-hoc interruptions with office hours that actually get used — the slot design (cadence, length, format), the routing rules that tell people what goes there vs. what shouldn't wait, and the empty-hours and overflow failure modes handled in advance. Use when asked set up office hours, I'm interrupted constantly but want to stay accessible, my office hours sit empty, or design expert time for the team. Produces the slot design, the routing card, the facilitation format, and the tuning rules.

Run an office move or reconfiguration without losing a week of work — the dependency-ordered plan (internet lead times rule everything), the workstream owners, the comms that keep the team functional through the chaos, and the day-one-that-works checklist. Use when asked plan our office move, we're moving floors/buildings in six weeks, who owns what in the move, or make day one at the new office not a disaster. Produces the workstream map with owners, the dependency timeline, the team comms plan, and the day-one readiness gate.

Plan a team offsite that earns its cost — the purpose split (connection vs. decisions vs. planning, weighted on purpose), the agenda that alternates work and air, the logistics runbook, and the follow-through that makes Monday different from before. Use when asked plan our team offsite, design two days for the team, make this offsite not a waste, or what do we actually do at the offsite. Produces the purpose weighting, the day designs, the logistics checklist, and the commitments-capture that survives re-entry.

Create well-structured OKRs (Objectives and Key Results) for product teams, startups, and individuals. Use when asked to write OKRs, set quarterly goals, define key results, or review existing OKRs. Produces a complete OKR set with objectives, measurable key results, baselines, and a scoring guide.

Write a structured end-of-shift on-call handoff so the incoming engineer inherits state, not surprises. Use when asked to write an on-call handoff, oncall handover, shift handoff, pager handoff, or end-of-week SRE summary. Produces a handoff note with open incidents, watchlist alerts, in-flight investigations, recent changes, and one-line asks.

Write an on-call runbook for a service — covering alert definitions, escalation paths, common incident responses, and on-call handoff procedures. Use when asked to write an on-call guide, create alert runbooks, document escalation procedures, or prepare an on-call handoff document. Produces a structured on-call runbook with per-alert response procedures, escalation matrix, diagnostic commands, and handoff template.

Design the buddy system that makes new-hire onboarding human — the buddy's actual job (context and safety, not training), the 30-day touchpoint plan, the ask-me-anything contract, and the buddy selection that avoids the two classic miscasts. Use when asked set up an onboarding buddy program, I'm buddying the new hire what do I do, our onboarding is docs with no humans, or the new person is drowning quietly. Produces the buddy role definition, the touchpoint schedule, the first-week script, and the escalation line.

Write in-product onboarding copy that gets users to value fast. Use when asked to write onboarding copy, a welcome flow, product tour/tooltips, setup steps, or activation messaging. Produces the copy for an onboarding flow — welcome, the guided steps/tooltips toward the first win, progress and empty-to-active nudges, and a success moment — focused on the activation outcome, not a feature tour.

Create a structured 30/60/90-day onboarding plan for any new hire. Use when asked to write an onboarding plan, new hire plan, 30-60-90 day plan, or first 90 days roadmap. Produces a week-by-week plan with milestones, meetings, learning goals, and success criteria.

Get the single honest thing you're avoiding about a situation — said kindly but not softened away. Use when asked tell me the hard truth, what am I avoiding here, be honest with me about this, or what do I not want to hear. Produces the one thing you already half-know but keep sidestepping, said plainly and with care (not cruelty), why it's hard to face, and what facing it would actually make possible — because the truth you're avoiding is usually the one that would change things, and a kind voice can say what your own keeps ducking.

Prepare for a 1:1 so it drives outcomes instead of becoming a status update. Use when asked to prep for a one-on-one, build a 1:1 agenda, prepare to talk to your manager (or a report), or raise something hard in a 1:1. Produces a focused 1:1 agenda — your top topics with the outcome you want for each, the asks, updates kept brief, and growth/feedback threads, tuned to direction (with your manager vs. with a report).

Distil anything — a startup, product, project, or idea — into a single persuasive page. Use when asked to make a one-pager, a one-page summary, a leave-behind, a startup/product one-sheet, or a tl;dr brief. Produces a structured single page — headline + tagline, the problem, the solution, why-now/proof, and a clear ask/CTA — designed to be skimmed and remembered, ready to export as a typeset PDF.

Plan and promote an open house that draws buyers and generates leads. Use when asked to plan an open house, market an open house, or create an open-house checklist. Produces a plan — timing and promotion across channels, prep and staging checklist, a day-of run sheet, lead capture, and follow-up — so the event drives real interest and the agent leaves with leads, not just foot traffic.

Read a contract the way the counterparty's lawyer will — hunting for leverage, not fairness. Use when someone says 'read this like opposing counsel', 'how would the other side attack this agreement', 'find the weaknesses before they do', or before sending or signing any contract. Produces the demand/position letter opposing counsel would actually send, plus an out-of-character debrief with the clause fixes that defang each attack.

Turn a team or reporting structure into a clean org chart. Use when asked to draw an org chart, show reporting lines, visualize team structure, or map who reports to whom. Produces a ready-to-render Mermaid org chart (renders live, exportable as PNG/SVG) plus headcount notes and any structural observations.

Design an out-of-office that actually protects the time off — the auto-reply that routes instead of apologizes, the coverage map behind it, and the pre-departure handoff that prevents the beach laptop. Use when asked write my out of office message, going on vacation what do I set up, cover my work while I'm out, or I always come back to chaos. Produces the OOO message with routing, the coverage assignments confirmed, the pre-departure checklist, and the re-entry buffer plan.

Record the testable predictions inside a decision, then score them against reality later — so frameworks earn trust from outcomes, not vibes. Use when committing to a prioritisation, forecast, or plan (to log what it predicts), when asked to review what actually happened, or to compute how well-calibrated past RICE scores, forecasts, or bets have been. Produces a prediction record at decision time, and a calibration report with per-framework hit rates at review time.

Outline documents before drafting them — the argument skeleton that gets alignment cheaply, the one-line-per-section discipline, and the review-the-outline step that saves rewriting the prose. Use when asked help me start this document, outline before I write, why do my docs get rewritten from scratch in review, or get sign-off before drafting. Produces the outline with each section's claim (not topic), the reader-and-decision header, the outline review step, and the expansion rules.

Write cold outreach and networking messages that actually get replies. Use when asked to write a cold message to a recruiter/hiring manager, a LinkedIn connection note, a referral request, or a networking/coffee-chat ask during a job search. Produces short, specific, reply-worthy messages — tuned to the recipient and the ask — with a clear subject and a low-friction call to action.

Audit what your public online presence quietly reveals — and tighten it — before a stranger, employer, or scammer uses it. Use when asked what does my online presence reveal, audit my privacy, what can people find out about me, or clean up my social media. Produces a review of what's exposed across profiles and posts (location, routines, identifiers, security-question answers), the specific risks each creates, prioritized fixes (settings + what to remove/stop posting), and habits to prevent future leaks — without demanding you delete everything.

When everything feels urgent and equally impossible, sort it fast into do-now / schedule / drop / delegate — so the panic becomes a short, calm list. Use when asked everything is urgent, I'm drowning in tasks, help me triage, or I can't tell what actually matters right now. Produces your overwhelming pile sorted into four clear buckets, the honest 'actually drop this' calls most people won't make themselves, the one thing to do right now, and relief from the false belief that everything must be done immediately.

Check a package's health before you depend on it — npm and PyPI registry APIs via keyless curl: downloads, release recency, maintenance signals, and the dependency-decision read. Use when asked is this npm package maintained, check this PyPI library before we adopt it, compare these two packages, or is this dependency abandoned. Produces the health read with the signals interpreted (not just listed), the numbers with their commands, and the adopt/avoid/vendor recommendation framing.

Plan a paid acquisition / performance marketing program with unit economics that work. Use when asked to plan paid media, allocate an ad budget across channels, set CAC/LTV targets, or structure a creative-testing program. Produces a paid acquisition plan — economic guardrails (CAC/LTV/payback), channel allocation, account & campaign structure, a creative testing plan, the measurement approach, and scale/kill rules.

Get the take of the specific experts a situation actually needs — a lawyer, a therapist, an accountant, a doctor-minded thinker, whoever fits — each in their own voice. Use when asked what would a [profession] say, get expert perspectives on this, who should I be thinking like here, or what am I missing that a pro would catch. Produces a panel of the right domain experts for your situation, each flagging what a layperson would miss, where they'd disagree, and what to verify with a real professional — never a substitute for licensed advice on serious matters.

Draft clear, warm, professional messages to parents or guardians — progress notes, concerns, positive news, behaviour issues, or meeting requests. Use when asked to email a parent, write home about a student, raise a concern with a guardian, or share an update. Produces a ready-to-send message that is specific, partnership-oriented, and constructive — never accusatory — with the tone matched to the situation.

Prepare for a K-12 parent-teacher conference — including the hard ones. Use when asked to prep for a parent conference, plan what to say to a parent, or handle a difficult conversation about a student's behavior or grades. Produces a structured agenda, strengths-first talking points backed by specific evidence, a plan for the tough message, anticipated parent reactions with responses, and agreed next steps.

Get real information out of a 15-minute parent-teacher conference — the questions that beat 'how's she doing', the data to bring from home, and the follow-up that makes the meeting matter. Use when asked prepare me for the parent teacher conference, what should I ask my kid's teacher, the conference is 15 minutes what do I prioritize, or how do I raise a concern without making it adversarial. Produces the prioritized question list, the home-observations brief, the concern-raising scripts, and the follow-up plan with owners.

Write a B2B partnership proposal or business case. Use when asked to write a partnership proposal, draft a partnership brief, structure a co-marketing proposal, or create a business case for a strategic partnership. Produces a structured proposal with value proposition, partnership model, commercial terms, and mutual commitments.

Cut through passive-income hype to what's actually realistic for you — the real effort, capital, and risk behind each option, and which (if any) fit your situation. Use when asked how do I make passive income, is passive income real, best passive income ideas, or help me build income streams. Produces an honest teardown of the popular passive-income options (what they really require, how 'passive' they actually are, typical returns and risks), a match to your capital/skills/time, the scams and get-rich-quick traps to avoid, and a grounded next step — replacing the fantasy with a realistic path. Not financial advice.

Set up a sane password and two-factor-authentication baseline that's genuinely secure and actually sustainable — a password manager, unique passwords where it counts, and 2FA on what matters. Use when asked to improve my password security, set up a password manager, how do I use 2FA, or make my accounts more secure. Produces a prioritized rollout (secure the crown-jewel accounts first), a password-manager setup, a 2FA plan by method strength, backup-code and recovery safeguards, and a realistic order so it gets done, not abandoned.

Write clear, plain-English patient communications for any healthcare context. Use when asked to write a patient letter, patient information leaflet, appointment letter, test-results letter, discharge summary for patients, or health education content. Produces an accessible patient communication at an appropriate reading level with clear next steps.

Decode a pay stub line by line — every deduction explained, the gross-to-net story, and the errors worth catching. Use when asked to explain my pay stub, why is my paycheck smaller than expected, what are all these deductions, or check my paycheck for mistakes. Produces a line-by-line decode, the gross-to-net waterfall, the error checklist (withholding, benefits, overtime), and the fixes to raise with payroll.

Design or optimize a paywall / upgrade screen to convert free users to paid without killing trust. Use when asked to improve a paywall, upgrade prompt, or free-to-paid conversion, or to decide what to gate. Produces the gating strategy (what's free vs. paid and why), the paywall placement and moment, the screen's copy and plan layout, and the metrics to watch — conversion that respects the user.

Write a clear penetration-test report from findings of an authorized engagement. Use when documenting a pentest, security assessment, or authorized red-team engagement — turning findings into a report clients act on. Produces an executive summary, scope & methodology, findings with severity/evidence/reproduction/remediation, and a risk-ranked remediation plan. For authorized testing only.

Define and document performance budgets for a web service or application. Use when asked to set performance targets, define SLOs for latency or throughput, establish Core Web Vitals targets, create a performance baseline, or document performance regression policy. Produces a structured performance budget covering key user journeys, Core Web Vitals, backend latency SLOs, measurement tooling, CI enforcement, and breach response process.

Write structured, balanced performance reviews from bullet-point inputs. Use when asked to write a performance review, self-assessment, peer review, 360 feedback, or manager evaluation. Produces a complete, fair, professionally written review covering achievements, areas for growth, and development goals.

Make sense of perimenopause symptoms nobody warned you about and prepare the GP conversation that actually helps — a symptom tracker mapped to what's likely hormonal, the prioritized list to raise, the HRT and treatment questions to ask, and how to push back on dismissal. Use when someone says 'is this perimenopause?', 'my doctor won't take my symptoms seriously', 'help me prepare for a menopause appointment', or is 40-55 and blindsided by symptoms. Produces a symptom map, a GP-visit brief, and a treatment-questions list. Not medical advice — it organizes your experience for the clinician who prescribes.

Work out which permits a project actually needs and the order to get them — building/renovation, business licensing, events, signage, home businesses — so you don't build first and discover the permit later. Use when someone says 'do I need a permit for this', 'what permits for my renovation/business/event', 'help me apply for a permit', or 'the council flagged my project'. Produces a permit checklist with the likely permits, their sequence and dependencies, and the official offices to confirm each. Not legal/code advice — it orients and routes to the authority.

Write a professional bio in the three lengths you actually need. Use when asked to write a bio, an 'about me', a speaker/author bio, or a short profile blurb. Produces three ready-to-use versions — a one-liner, a short (~50-word) bio, and a long (~150-word) bio — in a consistent third-person voice, plus a first-person variant.

Five standing advisors — the Operator, the Skeptic, the CFO, the Coach, the Customer — debate your decision on paper and vote. Use when asked to help me decide, pressure-test this decision, what would smart advisors say, or convene my board. Produces five distinct advisor memos, a disagreement map, a vote with a stated decision rule, and the one question to resolve before deciding.

Write the manual for how you work best — your energy, triggers, communication style, and non-negotiables — to share with a manager, team, or partner (or to know yourself). Use when asked to write my user manual, how I work best, a working-with-me guide, or help my team understand me. Produces a clear one-pager covering how you communicate, when you're at your best, what drains you, how you like feedback, and your non-negotiables — turning invisible friction into stated expectations, so people can work with you instead of around you.

Write a personal statement for a university, grad-school, or job application that's specific, coherent, and unmistakably you — showing fit and motivation, not a résumé in prose. Use when asked to write my personal statement, help with my university/grad application essay, statement of purpose, or make my personal statement stronger. Produces a read of what this program/role wants, a clear through-line (your motivation and fit), a structure that shows rather than lists, evidence from your real experience, and an authentic voice — drawing it out of you, not inventing a story.

Cap your work-in-progress so things finish — the personal WIP limit (3 active outcomes, defended), the finish-before-start rule with its exceptions named, the parking lot for the overflow, and the throughput evidence that converts the skeptic. Use when asked I have twelve things half-done, why does nothing ever finish, set a WIP limit for my work, or I start everything and complete nothing. Produces the active-list cap, the parking protocol, the start-gate, and the two-week throughput experiment.

Build the case to win someone over to a decision, idea, or change. Use when asked to persuade someone, build a case for an idea, get buy-in, win over a skeptic, or prepare to pitch a proposal internally. Produces a persuasion brief — the audience's current view and what moves them, the core argument, the proof, objection handling, the emotional and logical appeals, and the ask.

Decide fast whether a suspicious message is a phishing scam — and what to do next — without clicking anything. Use when asked is this email/text a scam, is this message legit, I got a suspicious message, or did I just get phished. Produces a quick verdict with the specific red (and green) flags in the message, a safe way to verify through official channels, exactly what to do next (delete/report, or act if genuine), and recovery steps if you already clicked or entered details.

Rescue a photo library drowning in duplicates, screenshots, and 40,000 unsorted items — the triage order that shrinks first (screenshots, bursts, dupes), the album-vs-search philosophy that ends over-organizing, and the backup rule that comes before any deleting. Use when asked organize my photo library, 40k photos help, delete duplicate photos safely, or set up a photo system that lasts. Produces the backup-first step, the shrink passes in order, the light organizing layer, and the monthly habit.

Respond to a performance improvement plan strategically — decode what the PIP really is, decide fight-vs-land-softly with clear eyes, build the evidence file, and run the parallel job search the situation demands. Use when asked I was just put on a PIP what do I do, help me respond to a performance improvement plan, is my PIP survivable, or write my PIP check-in updates. Produces the honest read of the PIP, the two-track plan (perform + search), the documentation system, and templates for check-ins and the written response.

Write a Performance Improvement Plan a manager can defend and an employee can actually act on — specific concerns, measurable goals, real support, and an honest timeline. Use when asked to write a PIP, put someone on a performance plan, document underperformance, or build a formal improvement plan. Produces the concern statement, the measurable goals with success criteria, the support plan, the check-in cadence, and the consequences — HR/legal-ready. Complements pip-responder (the employee's side).

Know which talk you're giving — the pitch (drive one decision) vs. the teach (build understanding) — because mixing their structures fails both, and most bad presentations are one wearing the other's clothes. Use when asked is this a pitch or a training, my informative deck didn't land the ask, my pitch felt like a lecture, or structure this talk for the right job. Produces the mode diagnosis, the structural implications, the mixed-mandate split, and the mode-check on an existing deck.

Plan pivot-table analysis that answers the actual question — the question-to-layout mapping (rows, values, filters chosen on purpose), the data-shape check that pivots require, and the drill-down path from summary to so-what. Use when asked analyze this data with a pivot, what's driving the total, break this down by category and month, or my pivot shows nonsense. Produces the question decomposition, the pivot layout(s) with reasons, the data-shape fixes needed first, and the reading guide.

Generate retro pixel-text animated GIFs for Slack, Teams, or a PR comment — scrolling marquees, heartbeat pulses, confetti parties, twinkling sparkles — from a bundled pure-stdlib Python script (no PIL, no dependencies, byte-exact deterministic). Use when someone wants a celebration GIF, a 'ship it' GIF, a custom Slack GIF, a launch-day animation, or to make a team win feel like one. Produces a ready-to-drag .gif file.

Rewrite jargon-dense text into plain language without losing precision — the translation pass that keeps every fact and qualifier, the jargon triage (terms to replace, terms to keep-and-define), and the reading-level honesty for the actual audience. Use when asked make this readable, translate this for non-experts, de-jargon this announcement, or rewrite this so my parents/customers/new hires understand it. Produces the rewrite with a fidelity check, the jargon ledger, and the kept-terms glossary line.

Turn a messy to-do brain-dump into a realistic, time-blocked day — top priorities first, everything slotted with buffer, and an honest 'this won't all fit, cut these.' Use when asked to plan my day, time-block my schedule, help me organize today, or I have too much to do. Produces the top 3 priorities, a time-blocked schedule around your fixed commitments, a realistic cut list when it's overloaded, and an if-things-slip fallback — planning for the day you'll actually have.

Structure a PM's weekly review and planning session. Use when doing a weekly PM review, writing a weekly update, preparing for Monday planning, or reviewing sprint health. Produces a shareable weekly update covering metrics movement, shipping progress, blockers, insights, and next week's top 3 priorities.

Get only the weaknesses in something you made — no praise, no encouragement padding, just the holes and how to fix them. Use when asked to poke holes in this, tell me what's wrong with this, critique this honestly, or don't be nice about it. Produces a focused list of the real problems in your draft, plan, argument, or code — ranked by severity, each with why it's a problem and a concrete fix — deliberately stripping the 'this is great!' padding that AI and polite humans add and you don't need.

Draft an internal policy people can actually follow — the rule stated plainly with its reason, the bright lines separated from the judgment zones, the edge cases resolved by principle, and the enforcement reality stated honestly. Use when asked write our expense/remote-work/AI-use/security policy, turn this incident into a policy, our policy doc is unreadable, or people keep asking what's allowed. Produces the policy with rules-plus-reasons, the bright-line/judgment split, the worked edge cases, and the honest enforcement section.

Write a decision-ready policy memo that frames an issue and recommends an option. Use when asked to write a policy memo, options paper, decision memo for a principal/minister/executive, or brief a decision-maker on a policy choice. Produces a tight memo: the issue, background, options with trade-offs, a clear recommendation, and implementation/risks — written for a busy decision-maker who reads the first paragraph.

Run a pre-renewal review of an insurance programme: scan coverage gaps against current operations, test limit adequacy against inflation and exposure growth, read the claims experience into pricing expectations, frame market alternatives, and arm the broker negotiation. Use when asked to prepare for a policy renewal, review cover before renewal, check if limits are still adequate, or build renewal negotiation points. Produces a structured renewal review with gap findings, limit assessment, pricing outlook, and negotiation points.

Structure a portfolio or case-study page that shows your work, not just lists it. Use when asked to write a portfolio page, a project case study, a work showcase, or an 'is this person good?' proof page. Produces a portfolio structure — a positioning header, and per-project case studies (context → your role → what you did → outcome) that demonstrate impact, ready to export as a designed page/PDF.

Fix the screen-hunch with a realistic plan — the desk fixes, the two or three exercises that counter it, and movement habits that beat any single stretch. Use when asked how to fix my posture, I have bad posture from sitting, tech neck, or rounded shoulders help. Produces a quick posture-cause read, immediate desk/setup fixes, a few high-value strengthening and mobility moves, movement-break habits, and honest expectations — plus a 'see a professional for pain/numbness' flag.

Understand power of attorney — which type you need, what it covers, and how to set one up properly — so the right person can act for you or a loved one when needed. Use when asked what is power of attorney, do I need a POA, help me set up power of attorney for a parent, or which type of POA. Produces a plain-English explainer of the main POA types (financial vs health, durable, springing), a which-do-you-need read for the situation, the setup steps and safeguards against abuse, and a strong flag to use proper legal forms/advice for your jurisdiction. Not legal advice.

Plan for an extended power outage — keeping medically-essential devices running, food safe, the home warm or cool enough, and communication alive — before the lights go out, with the special focus on power-dependent medical needs. Use when someone says 'prepare for a power outage', 'what if the power goes out for days', 'blackout plan', or 'I rely on a medical device that needs electricity'. Produces an outage plan tiered by duration, a medical-power priority plan, food/heat/cool/comms guidance, and safety warnings. Not medical advice; medical-device continuity routes to clinicians/utilities.

Audit a PowerPoint presentation for layout issues, text overflow, visual hierarchy problems, and consistency gaps. Use when asked to review a slide deck, check a presentation before a meeting, audit slides for layout problems, or QA a deck before sharing. Produces a slide-by-slide report with issues ranked by severity and specific fixes. Best used with Claude Opus 4.7 or newer for reliable slide-level vision analysis.

Build a crisis communications plan to respond fast and credibly when something goes wrong. Use when asked to handle a PR crisis, draft a crisis comms plan, respond to a public backlash/scandal/incident, or prepare holding statements. Produces a crisis comms plan — situation assessment, stakeholder map, a message house, channel-by-channel statements, a holding statement, an internal brief, and a follow-up timeline.

Write a clear pull-request description that gets reviewed fast and merged with confidence. Use when opening a PR, summarizing a change for review, or asked to write a PR/merge-request description. Produces a structured PR: what changed and why, how it was tested, risk and rollout, and a focused reviewer guide — so the reviewer understands intent before reading a single diff line.

Write a PR description grounded in the REAL diff — read the branch's actual changes via the GitHub connector, not a template the user fills in. Use when asked to write my PR description, describe this pull request, draft the PR body from my branch, or document these changes in Cowork. Reads the commits and diff via the GitHub connector, derives what changed and why from the code itself, and produces a PR-description artifact (summary, changes, testing, risk) ready to paste — matching the repo's PR template if one exists.

Write a clear, structured pull request description from a git diff, branch summary, or commit list. Use when asked to write a PR description, draft a pull request, or document code changes. Produces a description with summary, motivation, changes made, testing steps, and reviewer guidance.

Create a Product Requirements Document following proven PM template structure. Use when asked to write a PRD, product spec, feature specification, or requirements document for a new feature or product. Produces a complete PRD with problem statement, user stories, functional requirements, technical considerations, and success metrics.

Imagine your plan already failed, then get five independent 'here's why it died' stories — before you commit. Use when asked to pre-mortem this, why might this fail, what are the risks before I start, or imagine this went wrong. Produces five distinct failure narratives (each from a different cause — execution, timing, people, external, wrong-assumption), the most likely and most lethal among them, the early warning signs of each, and the specific mitigations worth doing now — catching failures while they're still cheap to prevent.

Kill the plan on paper before reality does it for money. Use when a plan, launch, migration, or strategy is about to be committed to and nobody has tried hard to murder it yet — the assassin attacks through twelve named failure vectors and writes the post-mortem of the failure that hasn't happened. Produces a premortem: the death narrative, the twelve-vector attack with survival verdicts, the three kill-shots most likely to land, and the cheap tripwires that would give early warning.

Work down the cost of a prescription systematically — the generic and therapeutic-alternative conversation, discount programs vs insurance math, pharmacy price variance, and manufacturer/assistance programs, in the order that saves the most first. Use when asked my prescription is too expensive, how do I save on my meds, is there a cheaper version of this drug, or I can't afford my medication. Produces the cost-reduction ladder for the specific prescription, the scripts for pharmacist and prescriber conversations, and the never-do list (skipping doses is not a savings plan).

Write presenter notes that actually help mid-talk — cue-grain phrases instead of scripts, the transitions and numbers that deserve verbatim capture, the timing marks that keep the talk on schedule, and the Q&A crib built in. Use when asked write my speaker notes, I either script everything or wing it, what goes in the notes pane, or I keep running over time. Produces the notes at cue grain, the verbatim-worthy lines, the timing marks, and the Q&A crib.

Build an electronic press kit that bookers and blogs actually read — the three-sentence bio that isn't 'genre-defying', a one-page layout with streaming numbers presented honestly, the photo and live-video requirements, and pitch emails tuned per target (venue, blog, radio, festival). Use when a musician says 'I need an EPK', 'venues keep ignoring my emails', 'write my band bio', or 'what do I send festivals'. Produces the EPK content, the one-page layout spec, and four pitch email templates.

Write a professional press release for any announcement. Use when asked to write a press release, media announcement, news release, or press statement. Produces a structured press release with headline, dateline, body, boilerplate, and media contact — ready to send to journalists.

Announce a price increase without triggering a churn spike — the rationale, grandfathering, effective dates, the FAQ, and the internal brief so support isn't blindsided. Use when asked to announce a price increase, write pricing change comms, raise prices to customers, or communicate new pricing. Produces the customer email, the FAQ with objection handling, the grandfathering/transition terms, and the internal enablement brief. A pricing-comms craft, not a discount.

Get a retailer to match a lower price you found — or refund the difference when the price drops right after you bought — with the request written and the exact proof to show. Use when asked for a price match, I found it cheaper somewhere else, the price dropped after I bought it, or can I get a price adjustment. Produces the policy-aware request, the evidence that qualifies, the eligibility read (what usually counts vs excludes), and a fallback if they won't match.

Model pricing scenarios — tiers, margins, break-even, and the revenue impact of a price change. Use when asked to calculate pricing, model a price increase, find break-even volume, set tier prices to a margin target, or estimate the revenue effect of a pricing change. Produces a computed pricing model (per-tier margin, break-even units, price-change revenue impact with an elasticity assumption) and a recommendation.

Write pricing page copy that helps buyers self-select the right plan and convert. Use when asked to write or improve a pricing page, name and describe pricing tiers, write plan feature lists, pricing CTAs, or a pricing FAQ. Produces complete pricing page copy — a header, tier cards with names, prices, audiences, feature lists, CTAs, an add-on/enterprise section, and an objection-handling FAQ.

Van Westendorp price sensitivity, computed from real survey answers — crossings found by interpolation, not read off a chart by eye. Use when someone has (or plans) the four-question pricing survey (too cheap / cheap / expensive / too expensive) and needs the optimal price point, the acceptable range, and a defensible readout. Produces OPP/IPP and the PMC–PME range, the four cumulative curves as data, and a real .xlsx with a live revenue what-if — via the bundled zero-dependency script.

Structure pricing strategy decisions, packaging options, and tier design for SaaS and digital products. Use when reviewing or setting pricing, designing pricing tiers, evaluating freemium vs paid, or preparing a pricing change. Produces a pricing strategy recommendation with model rationale, tier structure, competitive positioning, and rollout plan.

Design a freelance/consulting pricing structure — hourly vs day-rate vs project vs retainer chosen per engagement type, anchored packages, and the rules for saying the number out loud without flinching. Use when asked how should I price my freelance services, hourly or fixed price, build my pricing packages, or a client asked my rate what do I say. Produces the pricing-model decision per engagement type, a three-tier package structure, the rate-conversation script, and the discount policy with its floor.

Write a persuasive prior-authorization / medical-necessity letter to an insurer. Use when asked to write a prior authorization letter, a letter of medical necessity, or to appeal a denied treatment/medication/procedure. Produces a structured letter — patient and request, clinical justification tied to guidelines, treatments tried, and the specific approval asked for — ready for clinician review and signature.

Draft a clear, plain-language privacy policy tailored to what a product actually collects and does with data. Use when asked to write a privacy policy, draft a data-protection notice, or create a GDPR/CCPA-aware privacy statement. Produces a structured policy covering data collected, purposes, legal bases, sharing, retention, user rights, and contact — written to be readable, not boilerplate. Not legal advice; have counsel review before publishing.

Document any business process in a clear, structured format. Use when asked to document a process, write a process guide, create a workflow document, or map out how something works. Produces a complete process document with steps, roles, inputs, outputs, and edge cases.

Write a product description / listing that sells and ranks. Use when asked to write a product description, e-commerce listing copy, a product page, or to rewrite a flat product blurb. Produces benefit-led listing copy — a hook, scannable feature→benefit bullets, specs, an SEO-aware title and keywords, and trust/again-objection elements — tuned to the buyer and channel.

Interpret product metrics against goals and surface actionable signals. Use when asked to analyse product health, review key metrics, investigate a performance issue, produce a health report, or assess product-market fit signals. Produces a structured health report with RAG status, trend analysis, root cause hypotheses, and prioritised actions.

Generate a comprehensive pre-launch, launch day, and post-launch checklist for any product release. Use when preparing for a product launch, feature release, or major update. Produces a role-assigned, tiered checklist covering engineering readiness, marketing and comms, support, and post-launch monitoring.

Generate and evaluate names for a product, feature, or release. Use when asked to name a product/feature/company, brainstorm naming options, or choose between name candidates. Produces a shortlist of names across naming strategies, each with rationale, plus an evaluation against clear criteria (clarity, fit, memorability, availability checks to run) and a recommendation — not just a random list.

Write a product positioning document and messaging framework. Use when asked to define product positioning, write a positioning statement, build a messaging framework, or create a messaging hierarchy. Produces a complete positioning doc with category definition, target customer, differentiation, proof points, messaging pillars, and persona-specific messaging.

Find out whether something you own — a car, appliance, car seat, food item, or gadget — is under a safety recall, and what to do about it. Use when asked to check for a recall, is my [product] recalled, I heard about a recall on, or how do I find out if my car/appliance is affected. Produces a structured way to check by make/model/batch against the official sources, how to read whether your specific unit is affected, the free remedy you're owed, urgency triage for safety risks, and how to register for future recall alerts — flagging that you must confirm against the current official database.

Maintain a durable, local markdown memory ('brain') of your product context, decisions, hypotheses, and stakeholders that other skills read from and write back to. Use when asked to set up a brain, ingest notes/artifacts into memory, recall what's known about a topic, log a decision with provenance, or run a weekly brain review. Produces a structured brain/ folder (knowledge, decisions, hypotheses, stakeholders, entities, source) with provenance-tagged facts, plus ingest/recall/record/review operations with approval-gated, append-only write-back.

Translate text professionally — preserving tone, register, and meaning, not word-for-word. Use when asked to translate a document, email, or content between languages, or to improve a literal/machine translation. Produces a natural, register-appropriate translation plus translator's notes on choices, untranslatable terms, and anything that needs localization rather than translation.

Plan a programmatic SEO strategy — generate many ranking pages from a data set and a template. Use when asked about pSEO, scaling content with templates/data, building [X] for [Y] pages, or capturing long-tail search at scale. Produces the head-term + modifier model, the page template and data schema, a quality/thin-content guardrail, and an indexation plan — pages worth ranking, not doorway spam.

Write a structured project status report for any project. Use when asked to write a project update, status report, RAG report, project dashboard narrative, or weekly project communication. Produces a clear status report with RAG ratings, milestone progress, risks, and decisions needed.

Build a promotion case that proves you're already operating at the next level. Use when asked to write a promo packet/case, prepare for a promotion committee, or make the case for a level-up or title change. Produces a promotion packet — the level-up thesis, evidence mapped to each next-level competency, scope/impact highlights, peer-quote slots, and the gaps to close before submitting.

Plan a sale or promotion that drives revenue without wrecking margin. Use when asked to plan a promotion, a discount/sale campaign, a BFCM/holiday promo, or a product launch offer. Produces a promo plan — objective, the offer mechanic, margin math, audience & channels, timing, messaging, and how you'll measure it — so the discount is a strategy, not a reflex.

Figure out why a prompt isn't working and fix it — diagnose the actual failure (ambiguity, missing context, wrong format, conflicting instructions) instead of randomly rewording. Use when asked why isn't my prompt working, the AI keeps ignoring my instructions, my prompt gives inconsistent results, or how do I fix this prompt. Produces a diagnosis of the specific failure mode, the targeted fix for it (not a vibes rewrite), a corrected prompt, a check that it generalizes rather than fixing one case, and the principle behind the fix so you stop hitting it — turning prompt frustration into a debuggable, repeatable process.

Diagnose and rewrite an underperforming LLM prompt so it produces reliable, well-structured output. Use when asked to improve a prompt, fix a prompt that gives inconsistent or wrong results, reduce hallucination/refusals, or make output follow a format. Produces a rewritten prompt with a diagnosis of what was failing, the specific changes and why, and a small test set to verify the fix.

Design a regression test suite that catches an LLM feature getting worse when the prompt, model, or context changes. Use when asked to stop prompt changes breaking production, set up golden tests or CI gates for an LLM feature, or test a model/prompt upgrade before shipping it. Produces a golden case set, per-case pass criteria, CI gate thresholds, and a triage protocol for failures. For designing first-time evaluation of a new feature use ai-eval-plan instead.

Build a personal library of reusable prompts for the things you ask AI again and again — so you stop rewriting the same request from scratch. Use when asked help me build a prompt library, save my best prompts, I keep writing the same prompts, or organize my AI prompts. Produces a captured set of your recurring AI tasks turned into reusable, parameterized prompt templates, an organization scheme so you can find them, guidance on what makes a prompt reusable (clear role, inputs, output format), and how to store and improve them — turning ad-hoc prompting into a personal toolkit that compounds.

Analyze a rental / investment property's returns — cash flow, cap rate, cash-on-cash, ROI. Use when asked to analyze a rental property, evaluate a real-estate investment, run the numbers on an investment property, or compute cap rate / cash-on-cash. Produces an investment analysis — income and expenses, NOI, cap rate, monthly cash flow, cash-on-cash return, and a verdict against the investor's criteria — with formulas and a worked example. Not financial advice.

Write a compelling, accurate real-estate listing description. Use when asked to write a property listing, an MLS/Zillow description, a real-estate listing, or to make a property description more appealing. Produces a listing — a hook headline, a flowing description that sells the lifestyle and key features, a highlights list, and neighbourhood notes — accurate and Fair-Housing-compliant. Not legal advice.

Write a buyer's offer cover letter to a seller to strengthen a real-estate bid. Use when asked to write a real-estate offer letter, a buyer's 'love letter' to a seller, an offer cover note, or to make a home offer stand out. Produces a warm, genuine letter — who the buyers are, why they love the home, the strength of their offer, and a respectful close — while avoiding fair-housing risk. Not the legal offer/contract; not legal advice.

Challenge an over-assessed property tax bill — check whether your assessment is too high, build the evidence, and file the appeal before the deadline. Use when asked to appeal my property taxes, my property assessment is too high, lower my property tax, or is my home over-assessed. Produces an over-assessment check (comparables vs your valuation), the evidence pack to build, the appeal steps and the strict deadline to watch, a realistic savings estimate, and what to expect at a hearing — flagging that process and rules are local. Not legal or tax advice.

Structure an internal proposal that gets a decision — the problem-cost-options-recommendation-ask spine, the objection pre-handling that shortens the meeting, and the reversibility framing that makes yes easier. Use when asked write a proposal for the new tool or process or hire, how do I pitch this internally, structure my case for the change, or my proposals keep dying in review. Produces the proposal skeleton filled from the actual case, the objections table, the decision-sized ask, and the one-page discipline.

Write a structured sales proposal or commercial proposal for any deal. Use when asked to write a proposal, sales proposal, commercial proposal, statement of work, or quote document. Produces a complete proposal with problem statement, solution, investment, and next steps.

Draft a persuasive public comment on a proposed rule, regulation, or plan. Use when asked to comment on a rulemaking, respond to a consultation, submit feedback on a proposed regulation, or write a comment to an agency. Produces a structured comment: your position, specific evidence-based arguments tied to the proposal's text, suggested edits, and the impact — the kind agencies must consider on the record.

Look up public holidays for any country and year with zero API keys — the Nager.Date API via curl, with long-weekend detection and cross-country planning. Use when asked what are the holidays in a country, is date X a holiday somewhere, find long weekends this year, or which days is the team in Japan and Germany both off. Produces the holiday list with local names, the specific-date answer, long-weekend candidates, and the rerunnable command.

Prepare for a specific talk, presentation, or speech — a clear structure, a strong open and close, delivery and nerves handling, and a rehearsal plan — so you land it. Use when asked to help me prepare a talk/presentation/speech, prep for public speaking, I have to give a presentation, or calm my speaking nerves. Produces a message-first structure built on your core point and audience, a memorable opening and closing, delivery guidance (pace, pauses, notes vs script), a nerves-management plan, a rehearsal approach, and Q&A prep — tuned to the occasion and your experience.

Turn walkthrough notes, photos, or voice-memo transcripts into a proper construction punch list with location, trade, and spec reference per item. Use when asked to build a punch list, clean up walkthrough notes, organise a deficiency list, prep for substantial completion, or track punch items to closeout. Produces a numbered punch list grouped by location with severity tiers, responsible subcontractor, back-charge candidates, and closeout/retainage linkage.

Write the purchase request that gets approved — the cost-of-not-buying framing, the ROI math at the approver's altitude, the alternatives-considered section that preempts the obvious pushback, and the right-sized ask for the approval tier. Use when asked justify this tool/hire/equipment purchase, write the budget request, my requests keep getting deferred, or make the business case for this spend. Produces the justification memo: the problem priced, the ROI shown, alternatives dispatched, and the ask sized to its approval path.

Turn a story and its change into a clean 'ready for QA' package — test scenarios, edge cases, the data and environment setup, and what's explicitly out of scope. Use when asked to prep a QA handoff, what should QA test here, write test scenarios for this story, or make this ready for QA. Produces the scenarios mapped to acceptance criteria, the edge/negative cases devs forget, the exact data and environment setup to reproduce, the risk areas to probe, and the out-of-scope list so QA doesn't chase the wrong things.

Produce a QA release sign-off / go-no-go readiness report. Use when asked for a release sign-off, a go/no-go QA report, release readiness, or a test summary before shipping. Produces a sign-off — what was tested and the results, open defects by severity, coverage and residual risk, the go/no-go recommendation with conditions, and a rollback note — so the release decision is evidence-based, not a vibe.

Build a Quarterly Business Review (QBR) deck structure and narrative for a customer account. Use when asked to prepare a QBR, business review meeting, executive review, or quarterly check-in with a customer. Produces a slide-by-slide QBR structure with talking points, metrics review, value narrative, and mutual next steps.

Build the tax habit self-employment requires — the setaside percentage from day one, the quarterly calendar, the records that make filing boring, and the no-withholding mindset shift nobody explains. Use when asked how do taxes work for my side income, how much should I set aside, what are estimated quarterly payments, or set up my freelance tax system. Produces the setaside rule with its honest range, the quarterly rhythm calendar (jurisdiction-flagged), the five-minute-a-week records system, and the deduction-tracking habit — framing routed to a local professional for the numbers.

Generate a quiz or test on any topic with a balanced mix of question types and difficulty, plus a complete answer key with explanations. Use when asked to create a quiz, write a test, make practice questions, or build an assessment. Produces well-formed questions aligned to learning objectives, tagged by difficulty and cognitive level, with an answer key and (for MCQs) plausible distractors and rationale.

Pull the single most shareable quote out of a testimonial, review, interview, or long text and format it as a clean quote card. Use when asked to make a pull-quote, testimonial graphic, or 'quote card' for social/marketing. Produces a tightly-edited quote with attribution and 2-3 alternates, structured to look great exported as a PNG from the playground.

Talk to a family member or friend who's gone down a conspiracy, misinformation, or extremism rabbit hole — without blowing up the relationship or entrenching them further — using connection-first techniques that actually work instead of the facts-and-arguments that don't. Use when someone says 'my dad believes X now', 'my friend's gone down a conspiracy hole', 'how do I talk to them without a fight', or is losing someone to a belief spiral. Produces a conversation approach, what-not-to-do list, and a realistic goal. Connection over winning — and it names when to step back for your own wellbeing.

Define a RACI matrix for a cross-functional project or process. Use when asked to build a RACI, create a responsibility matrix, clarify ownership across teams, or document decision rights. Produces a complete RACI matrix with role definitions, decision mapping, and a process for resolving conflicts.

Review an existing Retrieval-Augmented Generation system and find why it underperforms. Use when asked to review or audit a RAG pipeline, diagnose wrong/ungrounded answers from a 'chat with your docs' feature, or improve an already-built knowledge assistant. Produces a staged review — ingestion, chunking, retrieval, reranking, generation, evaluation — with prioritised findings, root causes, and concrete fixes.

Design a Retrieval-Augmented Generation system end to end. Use when asked to design a RAG pipeline, a 'chat with your docs' feature, a knowledge assistant, or to debug why a RAG system gives wrong/ungrounded answers. Produces a RAG design doc — ingestion & chunking, embeddings & index, retrieval & reranking, the generation prompt, grounding/citations, evaluation, and failure modes with mitigations.

Model staying for annual raises vs job-hopping for bigger bumps — cumulative earnings trajectories, the crossover year, and the costs the salary math hides (vesting resets, promotion paths, search risk). Use when asked should I switch jobs for more money, is job hopping worth it, model my salary if I stay vs leave, or raise versus new offer. Produces the year-by-year salary and cumulative-earnings table, the crossover year, and the not-in-the-model checklist that usually decides it.

Climb ranked on purpose instead of on tilt — a VOD-review protocol (three deaths per game, one pattern per week), a tilt debrief that ends queue-rage sessions, and honest fundamentals-first improvement planning for competitive games like League, Valorant, or Rocket League. Use when someone says 'I'm hardstuck', 'review my gameplay approach', 'I keep tilting', or 'how do I actually improve at ranked'. Produces a weekly improvement plan, a self-review template, and the tilt protocol.

Handle the first hour of a suspected ransomware or malware infection calmly and correctly — contain it, preserve options, and avoid the moves that make it worse. Use when asked what to do about ransomware, my files are encrypted with a ransom note, I think I have malware, or my computer's been hacked. Produces an immediate containment checklist, a preserve-evidence-and-options step, a recovery path (backups, known decryptors, professional help), guidance on the ransom-payment decision, and reporting steps — for personal/small-setup use, not a substitute for professional incident response.

Build a consulting/freelance rate card and pricing structure — and the floor rate to not go broke. Use when asked to set freelance/consulting rates, build a rate card, decide what to charge, package services, or move off hourly billing. Produces a rate card — your minimum viable rate (from real targets), tiered packages, pricing models (hourly/day/project/retainer/value), and how to present and defend it.

Figure out the real social dynamics of a situation — the unspoken mood, who holds influence, what's actually going on beneath the surface — so you respond to what's real, not just what's said. Use when asked help me read this situation, what's really going on here, how should I play this socially, or I can't tell the vibe. Produces an interpretation of the likely dynamics from your description (the mood, the power/influence, the unspoken tensions, what people actually want), how to check your read, and how to adjust your approach — with a caution against over-reading and a nudge to verify rather than assume.

Actually remember and use what you read — an active-reading system that beats the highlight-and-forget cycle. Use when asked how do I remember what I read, I forget books right after finishing, help me retain what I study, or take better reading notes. Produces an active-reading method (questions before, engagement during, retrieval after), a lightweight note format that captures the few ideas worth keeping, a spaced review touch, and how to actually apply what you read — turning passive consumption into knowledge you keep.

Write a clear, well-structured README for a software project or open-source repo. Use when asked to write or improve a README, document a project, or make a repo approachable. Produces a complete README — one-line pitch, badges, quickstart, usage, install, contributing, license — that gets someone from landing to running fast.

Audit any document against its own sources — every factual claim extracted and graded as evidenced, partially evidenced, unsupported, or contradicted, with the exact source line that supports or fails it. Use when asked to fact-check a document against its sources, check whether a report's claims are backed up, verify a deck against the data, or ask 'does this doc have receipts?'. Produces a claim ledger, unsupported claims ranked by load-bearingness, a fix-or-drop call per claim, and an honesty score with stated method.

Rebuild relationships with family, kids, and friends after incarceration or a long absence — how to reach out, repair trust at the other person's pace, and handle the hard first conversations. Use when asked how do I reconnect with my kids after prison, rebuild trust with family after being away, or the first conversation after a long absence. Produces a paced reconnection plan (who to reach first and how), opening messages that don't demand forgiveness, a way to rebuild trust through consistency rather than words, scripts for the hard conversations, and realistic expectations about time and rejection — so reconnection is steady and genuine, not a pressured single grand gesture. Centers the other person's pace; points to family therapy and reentry family services.

Reach back out to a friend or person you've lost touch with — past the awkwardness of the gap — with a message that reopens the door warmly. Use when asked how do I reconnect with an old friend, it's been too long and it's awkward, reach out to someone I drifted from, or message someone I lost touch with. Produces a read on why the awkwardness is smaller than it feels, a warm reach-out message that acknowledges the gap without over-apologizing, a specific hook (a memory, a reason, a simple 'you crossed my mind'), and how to move from message to actually reconnecting — because most drifted friendships just needed one person to text first.

Plan a real rest day — active recovery, genuine downtime, and a reset — instead of either grinding through or collapsing into a guilt-scroll. Use when asked how to spend a rest day, plan a recovery day, I'm burnt out and need to recharge, or what should I do on my day off. Produces a recovery plan matched to what you're recovering from (physical, mental, or both), gentle active-recovery options, restorative downtime that actually restores, light admin to reduce next-week stress, and permission to do less.

Write personalized candidate outreach that gets replies. Use when asked to write a recruiter InMail, a candidate outreach email, a sourcing message, or a follow-up sequence. Produces a short, personalized first message (hook tied to the candidate, the role's appeal, a low-friction ask) plus a 2–3 step follow-up sequence — honest and candidate-respectful, not spammy.

Prune your own recurring-meeting load — the personal calendar audit (your role in each, honestly), the four exit moves (leave, delegate, downgrade to notes, halve), and the graceful exit scripts that don't burn standing. Use when asked get me out of some of these meetings, my calendar is 80% recurring, which meetings can I stop attending, or leave a meeting politely. Produces the personal audit with role verdicts, the exit move per meeting, the scripts, and the calendar-shape after.

Attack your own plan the way a smart adversary would — find the weakest point, the thing you're hoping nobody notices, and where it breaks under pressure. Use when asked to red-team this, attack my plan, find the holes, or where does this break. Produces an adversarial breakdown of the plan's weakest points, the single move an opponent (or reality) would make to break it, the part you're quietly hoping holds, and the fixes that close the biggest gaps — a hostile stress-test done by your own side, before someone else does it for real.

Stress-test a plan, strategy, PRD, or launch by simulating hostile expert personas who attack it from every angle. Use when asked to red-team, stress-test, pre-mortem, pressure-test, play devil's advocate, or find the blind spots in a plan before committing. Produces a per-persona critique, a ranked list of the most dangerous risks, a pre-mortem, and the specific changes that would most strengthen the plan.

Structure a redundancy consultation process and draft key communications (UK employment law focus). Use when asked to plan a redundancy process, write a redundancy letter, structure a consultation, or manage a reduction in force. Produces a structured consultation plan and draft letters; always recommends qualified HR/legal advice before proceeding.

Plan a safe, incremental refactor of messy code without changing behavior. Use when code needs restructuring, is hard to change, has grown tangled, or you want to clean it up before adding a feature. Produces a sequenced plan of small behavior-preserving steps, the safety net (tests/characterization) to add first, and the target structure — refactoring as a series of green commits, not a risky big-bang rewrite.

Run a rigorous candidate reference check that surfaces real signal. Use when asked to prepare or conduct reference calls for a job candidate, design reference questions, or build a reference-check rubric. Produces a structured question set, probing follow-ups, a red/yellow/green scoring rubric, and the legal guardrails — designed to get past 'they were great' without leading the referee.

Write a credible, specific letter of recommendation or reference. Use when asked to write a reference letter, a letter of recommendation, a character reference, or to recommend someone for a job, school, or tenancy. Produces a structured reference — your relationship, specific evidence of their strengths, a comparative endorsement, and a clear recommendation — tailored to what the reader is deciding.

Secure strong references after a departure — who to ask, the ask messages, the briefing sheet that makes their reference specific, and the LinkedIn recommendation swap. Use when asked to help me get references, write a reference request, prep my referee, or ask my old manager for a recommendation. Produces the referee shortlist with rationale, tailored ask messages, a one-page referee briefing sheet, and the follow-up etiquette.

Design a referral program that drives real word-of-mouth growth. Use when asked to build a referral or refer-a-friend program, create an incentive/reward structure, or turn happy users into a growth channel. Produces the incentive design (who gets what, when), the mechanics and trigger moment, fraud guardrails, and the unit-economics check — a program that pays back, not one that just burns budget.

Design a referral or viral-loop program that actually drives growth. Use when asked to design a referral program, build a viral/invite loop, set referral incentives, or improve word-of-mouth growth. Produces a referral design — the loop mechanics, incentive structure (who gets what, when), the viral-math estimate (k-factor/cycle time), fraud guardrails, placement & messaging, and success metrics.

Compute the month a refinance actually starts saving money — payment delta, breakeven month, and total interest on both paths including the term-reset trap. Use when asked should I refinance, when does a refi break even, compare my loan to a refi offer, or is this refinance worth the closing costs. Produces the breakeven analysis with both interest totals, the if-you-sell-before-month-N warning, and the cases where the breakeven math lies.

Build a regular expression from a plain-English description, or explain an existing one. Use when asked to write a regex, match/validate/extract a pattern, or understand what a regex does. Produces the regex, a token-by-token breakdown, passing and failing test cases, and notes on flavor/edge cases.

Design and prioritize a regression test suite so changes don't break what worked. Use when asked to plan regression testing, build a regression suite, decide what to re-test after a change, or trim a bloated regression pack. Produces a risk-based regression plan — what to re-test and why, prioritised tiers (smoke → full), automation candidates, and a run strategy per release — so coverage matches risk and the suite stays fast.

Reframe a hard choice through the lens of future regret — which option will you regret less at 80? — to cut through short-term noise. Use when asked which will I regret less, help me decide with the long view, I don't want to look back and wish, or use the regret test on this. Produces each option projected forward to old age (the regret of doing it vs not), a distinction between action-regret and inaction-regret (people regret inactions more), the fear that's really driving the hesitation, and the choice that best minimizes lifelong regret — for the decisions that echo.

Read your marketing claims, landing page, or ad copy the way a consumer-protection investigator would (FTC/ASA framing) and draft the inquiry letter they could send. Use when asked to check my marketing claims, read this like a regulator, audit my landing page for claim risk, or is this ad compliant. Produces a claim inventory with substantiation demands, the inquiry letter, and a fix-or-drop debrief per claim.

Produce a regulatory impact analysis (RIA) weighing the costs, benefits, and alternatives of a proposed rule. Use when asked to assess a regulation's impact, do a cost-benefit analysis of a policy, justify a rulemaking, or compare regulatory options. Produces a structured RIA: the problem and rationale, options including the baseline, costs vs. benefits, distributional effects, and a reasoned recommendation.

Reread a harsh message, criticism, or perceived slight without the emotional spike — separate what was actually said from what your brain is amplifying. Use when asked this message really stung, am I overreacting to this, help me not spiral over this feedback, or did they mean it that way. Produces a calm read of what was literally said vs the story you've layered on, a check on the most likely (usually more neutral) intent, whether any action is actually warranted, and a grounded response option — easing the disproportionate sting that rejection-sensitive brains feel.

Run a calm, regular relationship check-in with your partner — a structured 'how are we doing' conversation that catches small things before they become big ones. Use when asked how to check in with my partner, we need to talk about our relationship, set up a relationship check-in, or improve communication with my partner. Produces a simple check-in structure (appreciations, what's working, what needs attention, needs and asks), ground rules that keep it safe not combative, prompts to surface the real stuff, a cadence that fits you, and a note on when an issue is bigger than a check-in.

Plan an independent music release backwards from release day — the 8-week countdown with distributor upload deadlines flagged, playlist pitch windows, the pre-save decision made honestly, content batched before the chaos, and a release week that doesn't depend on luck. Use when a musician says 'I'm releasing a single/EP', 'when should I submit to playlists', 'plan my release', or uploaded to a distributor with no plan. Produces the week-by-week countdown, the asset checklist, and release-week runbook.

Plan a move — across town or across a border — as a dependency-ordered project: the lease/housing chain, address-change cascade, utilities cutover, movers, and the go-bag for the gap days. Use when asked help me plan my move, relocation checklist, I'm moving in six weeks what do I do, or moving to another country logistics. Produces the dependency-ordered timeline, the address-change cascade list, the cutover schedule for both homes, and the moving-day run sheet.

Build a structured renewal playbook for a customer account. Use when asked to plan a renewal, structure a renewal negotiation, prepare for an expansion conversation, or build a renewal strategy for at-risk or healthy accounts. Produces a renewal brief with health assessment, negotiation strategy, objection responses, expansion levers, and a timeline.

Turn a renovation idea into a realistic scope, budget, and sequence before you hire anyone — so you go in informed instead of getting sticker-shocked or scoped. Use when asked to plan a renovation, budget for a remodel, how much will renovating [X] cost, or scope my home project. Produces a scoped breakdown of the work, a realistic budget range with a contingency, the sequence and rough timeline, must-decide-early choices, where costs balloon, and what to line up before getting quotes — flagging that local prices and permits vary, so verify with real quotes.

Respond to a rent increase strategically — check its validity first, price your alternatives honestly, then negotiate with the leverage tenants forget they have (turnover costs the landlord more than a compromise). Use when asked my rent is going up what can I do, negotiate my rent increase, is this increase even legal, or should I stay or move. Produces the validity checklist, the stay-vs-move math, the negotiation letter with its trade menu, and the decision timeline against the notice period.

Model rent-vs-buy honestly — year-by-year net position for both paths including the assumption everyone drops (the renter invests the difference), with a breakeven horizon instead of a verdict. Use when asked should I rent or buy, does buying beat renting in my city, when does buying break even, or run the rent-vs-buy numbers. Produces the year-by-year comparison table, the breakeven year, the assumption list with defaults labeled, and the not-modeled list.

Write a standout rental application / cover letter to a landlord or letting agent. Use when asked to write a rental application, a letter to a landlord, a renter cover letter, or to strengthen an application for a competitive rental. Produces a concise renter profile and cover letter — who you are, why you're a reliable tenant, your evidence, and a clear ask — that helps a landlord choose you.

Repair a relationship after an argument — reconnect, own your part, and rebuild trust — instead of the cold silence that lets damage set. Use when asked how do I make up after a fight, repair things after an argument, reconnect after we fought, or fix things with someone I hurt. Produces a read on what actually needs repairing (the incident vs the deeper hurt), a genuine repair approach (own your part specifically, acknowledge their hurt, no fake apology), the words to reopen, and how to rebuild rather than just move on — because unrepaired fights compound, and the repair matters more than never fighting.

Get a landlord to actually fix things — the repair request that creates a record, the escalation ladder from reminder to habitability leverage, and the jurisdiction-flagged map of tenant remedies with their prerequisites. Use when asked my landlord won't fix anything, write a repair request, how long can they ignore a broken heater, or what are my options if repairs never happen. Produces the documented request, the severity triage, the escalation ladder with letters, and the remedies decode with the do-not-DIY warnings.

Draft email replies that match the sender's register — formality, length, directness, and emoji-tolerance read from their message, so the reply lands as native instead of off-key. Use when asked reply to this email, draft a response that doesn't sound stiff, match their tone, or answer this without sounding like a robot. Produces the tone read of the incoming message, the reply drafted in that register, and the adjustment knobs.

Navigate a codebase by map instead of reading files wholesale — a deterministic stdlib script that emits the tree with line counts and top-level symbols, plus the read-the-map-first discipline that cuts exploration tokens by an order of magnitude. Use when asked explore this repo efficiently, stop re-reading the whole codebase, make a map of this project, or which files should the agent actually open. Produces the compact map with its token math (map vs. everything), the navigation discipline, and the open-only-what-matches rule.

Report a public hazard or code problem to the authority that can actually fix it — a pothole, broken streetlight, illegal dump, unsafe building, code violation, blocked drain — with the right department, the details that get it actioned, a tracking reference, and an escalation path if it's ignored. Use when someone says 'how do I report a pothole/hazard/violation', 'the council won't fix X', or 'who do I call about Y'. Produces a report ready to submit, the right channel, and a follow-up plan.

Sell secondhand like someone who's done it 500 times — honest condition grading, comps-based pricing with a floor and an anchor, listing titles built from real search terms, photo checklists, and offer/haggle scripts for Vinted, Depop, eBay, and Facebook Marketplace. Use when someone says 'help me sell this', 'price my old jacket', 'write my Depop listing', or 'lowballers keep messaging me'. Produces ready-to-post listings plus a pricing sheet and reply scripts.

Write a structured research protocol or study design document. Use when asked to write a research protocol, study protocol, research plan, methodology section, or research proposal. Produces a complete protocol with objectives, methodology, ethical considerations, and analysis plan.

Set up a research repository the team actually reuses — the atomic-insight format (finding + evidence + source + date), the tagging that makes old research findable by new questions, and the check-the-repo-first norm that stops re-researching. Use when asked set up a research repository, we keep re-learning the same things, where do our user insights live, or make past research findable. Produces the repo structure, the insight-entry format, the intake funnel from studies, and the reuse norms.

Write a resignation letter that closes a chapter without burning it — short, warm, legally clean, and silent on everything that doesn't belong in a permanent file. Use when asked write my resignation letter, how do I resign professionally, what do I say when I quit, or review my resignation email. Produces the letter itself, the tell-your-manager-first script, the timing plan, and the list of things that must NOT go in writing.

Plan a genuine break from caregiving — arrange the coverage, hand off the essentials, and actually rest — because respite is what lets you keep going. Use when asked I need a break from caregiving, how do I arrange respite care, I can't leave them alone, or help me get time off from caring. Produces the coverage options for your situation (family, paid respite, day programs, short-stay), a handoff pack so whoever covers has what they need, how to overcome the barriers (guilt, trust, cost, logistics), and a plan to actually rest during the break rather than worry — turning 'I can never get away' into a real, repeatable break. Not medical advice.

Write a sharp, achievement-led resume/CV that passes ATS and earns the interview. Use when asked to write or rewrite a resume or CV, turn experience into a resume, or tailor a resume to a job. Produces a clean, single-column, ATS-friendly resume — summary, experience as quantified accomplishment bullets, skills, and education — ready to export as a designed PDF.

Structure a retention analysis, churn investigation, or engagement deep-dive for any product team. Use when asked to analyse user retention, investigate churn, measure DAU/MAU, or build a retention improvement plan. Produces a retention snapshot with root cause hypotheses, aha-moment correlation, and prioritised interventions.

Design retention and engagement loops that bring users back. Use when asked to improve retention, design an engagement/habit loop, fix a leaky retention curve, or build a re-engagement system. Produces a retention design — the retention curve diagnosis, the core habit loop (trigger→action→reward→investment), the activation→habit path, re-engagement triggers, and the metrics to watch.

Analyses sprint delivery data and produces a structured retrospective brief. Use when asked to run a retrospective, analyse sprint data, prepare a retro brief, or turn sprint metrics into discussion prompts. Produces a data-grounded retrospective brief with completion stats, pattern analysis, Start/Stop/Continue prompts, and one concrete experiment for next sprint.

Write a clear, fair returns, refunds & exchanges policy for an online store. Use when asked to write a return policy, refund/exchange policy, or store returns page. Produces a customer-friendly policy — window, conditions, process, refund method/timing, exceptions, and shipping — in plain language that reduces support tickets and builds trust. Not legal advice.

Resolve a document's forty review comments systematically — triage by type (accept, push back, conflict, out-of-scope), batch the mechanical fixes, draft the disagreement replies, and reconcile reviewers who contradict each other. Use when asked work through these review comments, two reviewers want opposite things, close out the feedback on this doc, or which comments do I actually have to take. Produces the comment triage, the batched fixes, the push-back replies, the conflict reconciliations, and the closure sweep.

Write the right reply to a customer review — positive, negative, or mixed. Use when asked to respond to a review, reply to a bad/1-star review, handle online reviews, or write review-response templates. Produces tailored, on-brand responses that thank advocates, de-escalate and resolve complaints, and read well to the *future* shopper who's reading them — plus reusable templates.

Figure out the best card or payment route for a purchase (or your everyday spending) to maximize cashback/points — without overspending or drowning in complexity. Use when asked which card should I use for [purchase], maximize my credit card rewards, best card for [category], or optimize my points. Produces the best-value route for the spend from the cards/programs you actually have, a simple everyday cheat-sheet by category, redemption tips, and honest guardrails (pay in full, don't chase points into debt or clutter). Not financial advice.

Write an engineering RFC (Request for Comments) for a technical decision, architectural change, or significant implementation approach. Use when asked to write an RFC, document a technical proposal, create a design doc, write an architecture decision for review, or produce a technical specification for team feedback. Produces a complete RFC document covering problem statement, motivation, proposed solution, alternatives rejected, implementation plan, migration plan, security and performance implications, observability changes, rollout plan, and open questions.

Write a compliant, competitive response to an RFP/RFQ/ITT (government or enterprise procurement). Use when responding to a request for proposal, bidding on a tender, or answering a procurement questionnaire. Produces a compliance-matrix-driven response that answers every requirement, wins on evaluation criteria, and reads as low-risk to the buyer — structured to the scoring, not the seller's ego.

Build a weighted RFP evaluation matrix and defensible award recommendation. Use when asked to score RFP responses, compare vendor bids, build a supplier evaluation matrix, run a sourcing event scorecard, or decide which bidder to award. Produces a criteria tree with weights, scoring anchors, normalized price scores, a consensus-scored comparison table, and an award recommendation with sensitivity check.

Write a clear Request for Proposal that gets comparable, high-quality vendor bids. Use when asked to write an RFP, a request for proposal/quote/tender, or to solicit and compare vendor proposals. Produces a complete RFP — background, scope of work, requirements, evaluation criteria with weights, submission instructions, and timeline — structured so responses are easy to compare apples-to-apples.

Scores features using both RICE and strategic alignment for nuanced prioritisation. Use when asked to prioritise features, build a priority matrix, combine quantitative scoring with strategic fit, or decide what to build next with multiple competing initiatives. Produces a scored priority matrix with RICE scores, strategic alignment ratings, quadrant placement, and sequencing recommendations.

Scores and ranks product initiatives using the RICE framework. Use when asked to prioritise features, rank a backlog using RICE, score initiatives for quarterly planning, or apply an objective framework to a list of competing ideas. Produces a ranked RICE table with scores, quick wins and moonshot flags, dependency notes, and a recommended sequencing order.

Build and maintain a project or product risk register. Use when asked to create a risk register, identify project risks, build a risk matrix, or document risks and mitigations for a programme. Produces a complete risk register with likelihood/impact scoring, RAG status, ownership, and prioritised mitigations.

Turn field returns into a structured failure-analysis report — RMA triage taxonomy (NTF vs real failures), Pareto by verified failure mode, 8D-style containment→root-cause→corrective-action structure, and cost-of-quality framing. Use when asked to analyse RMA data, investigate field returns, run failure analysis on returned units, write an 8D report, or figure out why return rates are climbing. Produces a failure-analysis report with a triage-clean Pareto, 8D actions, and the cost case for fixing each mode.

Transform a prioritised initiative list into a compelling strategic roadmap narrative. Use when asked to write a roadmap narrative, explain the product roadmap to non-technical stakeholders, connect roadmap items to company goals, or produce an exec-shareable roadmap story. Produces a themed narrative with strategic context, quarter progression arc, an executive summary, and a 'what's not on the roadmap' section.

Create structured roadmap presentations calibrated to any audience. Use when asked to build a product roadmap, present roadmap to leadership, create a roadmap slide, or communicate quarterly plans to execs, teams, or customers. Produces an audience-calibrated Now/Next/Later roadmap with strategic context, initiative tables, success metrics, and explicit deprioritisation rationale.

Estimate the ROI, payback, and NPV of an investment, project, or purchase. Use when asked to calculate ROI, build a business case, justify a purchase/initiative, work out payback period, or compare options by return. Produces a computed ROI summary (net benefit, ROI %, payback, simple NPV) with the assumptions made explicit and a sensitivity note, so a business case is defensible.

Redesign a job role that AI now does a large part of — deliberately, instead of quietly expecting the same headcount to absorb 140% output. Use when AI has changed what a role spends time on, when writing a revised role charter or job description post-AI, when a team asks 'what is my job now', or when planning capacity after AI adoption. Produces a role redesign: the task inventory before/after, the redefined core of the role, new expectations and metrics, and the growth-path implications. For hiring rubrics use hiring-rubric; for org-wide skills planning use ai-upskilling or career-ladder-map.

Write a concrete rollback plan for a risky change (deploy, migration, feature-flag flip, config rollout) so the reverse is one command away — not an improvised debate at 2am. Use when asked to write a rollback plan, back-out plan, revert plan, or 'what if we need to undo this'. Produces a rollback plan with the signals that trigger it, exact reverse commands, verification steps, data-safety notes, and a communications template.

Write the flat's constitution before the first passive-aggressive note — money, chores, guests, noise, food, and the exit plan, decided while everyone still likes each other, in language that's firm without being corporate. Use when moving in with roommates, when the dishes cold-war has started, when a partner basically lives there rent-free, or when someone's moving out mid-lease. Produces a signed-feeling one-page agreement plus the house meeting script to agree it.

Fetch and digest any RSS or Atom feed with zero API keys — curl plus disciplined parsing into a ranked, deduplicated briefing instead of a link dump. Use when asked summarize this feed, what's new on this blog, digest these RSS feeds, or build me a morning briefing from these sources. Produces the digest with dates and one-line what-it-is summaries, cross-feed dedup, and the rerunnable commands per feed.

Create a clear grading rubric with criteria and performance-level descriptors that make scoring fair, fast, and consistent. Use when asked to build a rubric, create grading criteria, design an assessment scoring guide, or make grading more objective. Produces an analytic rubric table (criteria × performance levels) with concrete, observable descriptors and a points scheme — plus a short version students can self-check against.

Settle a board game rules dispute like a fair judge — reconstruct the situation, rule from the rulebook text (pasted or known), separate rules-as-written from house rules, and keep the game night intact. Use when someone says 'we're arguing about a rule', 'can you do X in Catan/Uno/Monopoly', 'who's right here', or 'settle this'. Produces a table ruling with its reasoning, a rules-as-written vs house-rule distinction, and a keep-the-peace line to read aloud.

Design a small team of AI agents to tackle a complex task in parallel — who does what, how they hand off, and how to keep them coordinated — instead of one overloaded agent doing everything serially. Use when asked how do I use multiple AI agents, set up an agent team, orchestrate agents for, or run agents in parallel. Produces a decomposition of the task into agent roles, a coordination pattern (parallel vs sequential, how outputs combine), the context each agent needs (and what to keep isolated), a review/quality step, and the guardrails to keep it from going off the rails — practical multi-agent design for real tasks.

Write an operational runbook for a service, incident type, or deployment procedure. Use when asked to write a runbook, create an ops guide, document an operational procedure, or prepare an incident response playbook. Produces a runbook with overview, prerequisites, step-by-step procedures, rollback steps, troubleshooting table, and escalation paths.

Calculate cash runway, burn, and the zero-cash date — and whether you're default alive or dead. Use when asked to work out runway, monthly burn, when the money runs out, or how much to raise/cut to reach a target. Produces a computed runway summary (net burn, months of runway, zero-cash date, default alive/dead) plus what it takes to extend it.

Cash runway as a distribution, not a number — Monte Carlo simulated. Use when someone asks how long their cash lasts, when to start fundraising, or how burn/revenue volatility changes their runway; especially when the naive cash÷burn answer is driving a decision. Produces P10/P50/P90 runway, month-by-month death probabilities, and a real .xlsx with editable assumptions and a live naive-runway formula — via the bundled zero-dependency simulator.

Turn burn and cash into a clear runway picture and a raise decision — months left, default-alive vs default-dead, and what to cut or change. Use when asked to calculate runway, model burn rate, decide when to raise, figure out if the company is default-alive, or plan a scenario with hiring/cuts. Produces the runway math, a default-alive verdict, and dated trigger points for raising or acting. Not financial advice.

Prepare an S&OP cycle readout that surfaces the demand-supply gaps and forces the three decisions the meeting must make. Use when asked to prep an S&OP meeting, build the executive S&OP deck, summarize demand vs supply for the monthly cycle, or prepare a supply review readout. Produces a gap table, scenario levers with costs, an inventory projection, a decisions-required list, and a pre-read package.

Compute the core SaaS metrics — MRR/ARR, growth, NRR/GRR, churn, quick ratio, magic number — from your numbers. Use when asked to calculate SaaS metrics, MRR/ARR, net revenue retention, the quick ratio, or to build a SaaS metrics snapshot for a board/investor update. Produces a computed metrics dashboard with each value, its benchmark, and a one-line read on what it means.

Check whether an online store or seller is legit before you pay — and pay in a way you can get your money back if it isn't. Use when asked is this website legit, is this online store a scam, should I buy from this site, or how to shop safely online. Produces a trust assessment from the store's signals (too-good pricing, contact/policy gaps, domain and review red flags), safe-payment guidance that preserves buyer protection, what to check before checkout, and what to do if you've already paid a scam site.

Build a defensible salary range for a role — what it actually pays given the market, location, level, and your value — so you can ask, counter, or set pay with a real number. Use when asked what should I be paid, is my salary fair, research market pay for [role], or how much to ask for. Produces a structured way to research the range from multiple sources, the factors that move your number (level, location, industry, skills, company size), where you likely sit in the band, and how to frame the number — flagging that pay data varies and should be triangulated, not taken from one source. Not the same as running the negotiation.

Plan a compensation negotiation grounded in numbers and leverage, not nerves. Use when asked to negotiate salary, evaluate or counter a job offer, prepare for a comp conversation, or compare offers. Produces a negotiation plan — total-comp comparison across offers, your target/walk-away and BATNA, the value-based justification, the counter scripts, and what to negotiate beyond base.

Create a competitive sales battlecard for any competitor. Use when asked to build a battlecard, competitive comparison, sales cheat sheet, or objection handling guide for a specific competitor. Produces a one-page battlecard with positioning, differentiators, objection responses, and landmines.

Write a product demo script that tells a value story instead of a feature tour. Use when asked to write a sales demo script, structure a product demo, plan demo talk track and flow, or turn a feature list into a compelling demo. Produces a demo script — the setup and discovery hooks, a scene-by-scene flow tied to buyer pain, talk track, 'aha' moments, transitions, and a close with next steps.

Build a sales enablement kit so reps can sell a product, feature, or launch confidently. Use when asked to create sales enablement materials, a rep-ready one-pager, talk tracks, objection handling, or a launch enablement package. Produces a complete kit — positioning summary, discovery questions, talk track, demo flow, objection handling, competitive counters, and a call-to-action for reps.

Build a structured sales forecast framework for any business or team. Use when asked to build a sales forecast, create a revenue model, project pipeline, or build a bottom-up forecast. Produces a forecast methodology, pipeline model, scenario analysis, and assumption log.

Write a long-form sales page that takes a cold reader to a purchase. Use when asked to write a sales page, a long-form sales letter, a course/offer page, or direct-response copy that has to close on the page. Produces a full long-form structure — hook, problem agitation, the offer & mechanism, proof, offer stack & price framing, risk reversal, urgency, and a repeated CTA — written to sell, ethically.

Turn a savings goal into a month-by-month funding plan. Use when asked to save for something (emergency fund, house deposit, trip, big purchase), or to figure out how much to set aside each month. Produces the required monthly contribution, a timeline, milestones, and trade-offs if the target date is too aggressive. Educational, not regulated financial advice.

Decline a request, push back on scope, or protect priorities without burning the relationship. Use when asked how to say no, turn down a request, push back on your boss/stakeholder, decline extra work, or protect the roadmap from a pet feature. Produces a graceful, firm response — the no, the honest why, an alternative or trade-off, and the exact wording, tuned to who's asking.

Decline requests without damaging relationships or your standing — the fast-clear-warm formula, the alternative-attached no, the no-to-the-boss version (tradeoffs, not refusal), and the scripts for the asks that recur. Use when asked how do I say no to this, decline this project politely, I say yes to everything and drown, or push back on my manager's request. Produces the decline scripts by relationship, the tradeoff framing for upward nos, the alternative menu, and the yes-audit that finds what to stop.

Decode a suspicious message — text, email, call transcript, or DM — against the anatomy of known scam families, with a 🔴🟡🟢 read and the safe next move. Use when someone asks is this a scam, decode this suspicious text, my 'bank' just called me, this job offer seems off, or my parent got a weird message. Produces the verdict with the specific scam-family match, the tells quoted from the message itself, the safe-verification path (never the message's own links or numbers), and the if-you-already-clicked triage.

Project completion as a distribution, not a date — Monte Carlo over the task graph. Use when a plan's finish date came from summing 'likely' estimates (it's wrong, mathematically), when leadership needs a commit date, or when you need to know which tasks actually control the timeline. Produces P10/P50/P90 completion, per-task criticality (how often each task sits on the critical path), and a real .xlsx — via the bundled zero-dependency simulator, deterministic with a seed.

Turn 'run this every Friday at 4pm' into a working, copy-paste schedule on the user's actual runner. Use when asked to schedule a recurring AI task, set up a routine or cron job for a skill, automate a weekly report, or wire a skill into n8n or GitHub Actions. Produces the exact setup for the chosen runner plus the prompt to run, failure alerting, and a first-run test plan.

Generate structured-data (Schema.org / JSON-LD) markup to win rich results in search. Use when asked about schema markup, structured data, rich snippets, JSON-LD, or making a page eligible for stars/FAQ/breadcrumb results. Produces valid JSON-LD for the right schema type, the rich-result it targets, required vs. recommended fields, and validation/guideline notes.

Write a scholarship essay that stands out — a genuine, specific story that answers the prompt and shows why you deserve the award, without clichés. Use when asked to help with a scholarship essay, write my scholarship application, essay about why I deserve this scholarship, or make my application essay stronger. Produces a read of the prompt and what the committee is really looking for, a strong angle drawn from your real story, a structure that hooks and builds, specifics over platitudes, and a voice that's authentically yours — guiding you to write it, not fabricating experiences you didn't have.

Choose the right school for a specific child by weighing what actually matters to them and your family — not just rankings. Use when asked how to choose a school, compare schools for my kid, which school is best, or help me decide on a school. Produces a priorities profile for this child, a comparison of the options on the factors that matter (fit, teaching, environment, logistics, cost), the questions to ask and things to observe on visits, a weighted decision, and a note that a good fit beats a high ranking.

Handle scope creep on client work without torching the relationship — classify the ask against the agreement, respond with the goodwill/change-order/renegotiate move that fits, and install the prevention language for next time. Use when asked my client keeps adding requests, is this scope creep, how do I say that's out of scope nicely, or write a change order email. Produces the classification of the ask, the graduated response with ready-to-send wording, and the contract language that prevents the rerun.

Cut compulsive screen and phone use with a workable plan — friction, environment, and replacement habits — instead of relying on willpower or deleting everything. Use when asked to reduce my screen time, I'm addicted to my phone, help me use my phone less, or a digital detox plan. Produces a read on your worst triggers, targeted friction and environment changes, replacement activities for the itch, boundary settings that stick, and a realistic goal — not an all-or-nothing purge that fails by Tuesday.

Tear down a competitor's product from screenshots of its actual UI — onboarding, pricing page, core flows. Use when given screenshots of a rival's app or website and asked what they're doing, how their flow works, or what to learn/steal/avoid. Produces a UX-and-strategy teardown grounded in what is visibly on screen, with an inferences-vs-observations split. Requires image input. For a market-level teardown without screenshots use competitor-teardown.

Get a second medical opinion without torching the first relationship — when it's warranted, how to raise it with the current doctor, the records package the consulting doctor needs, and how to weigh two opinions that disagree. Use when asked should I get a second opinion, how do I ask for a second opinion without offending my doctor, what records do I send, or the two doctors disagree now what. Produces the warranted-or-not framing, the raising-it scripts, the records checklist, and the disagreement-weighing framework.

Do the right things fast when your phone is lost or stolen — lock it, protect your accounts and money, and decide on wipe vs. locate — in the correct order. Use when asked my phone was stolen, I lost my phone what do I do, someone took my phone, or secure my lost phone. Produces an ordered action checklist (locate/lock, protect SIM and banking, change key passwords, wipe decision), the accounts to prioritize because the phone unlocks them, reporting steps, and prevention setup for next time.

Get your security deposit back — the move-out documentation that wins disputes before they start, the itemized-deduction challenge, the demand-letter ladder, and the small-claims decision point. Use when asked how do I get my deposit back, my landlord is keeping my deposit, dispute these deposit deductions, or write a deposit demand letter. Produces the move-out evidence protocol, the deduction-by-deduction challenge with the wear-and-tear line drawn, the escalation ladder with letters, and the small-claims prep sheet.

Run or document a security incident response — contain, eradicate, recover, and learn. Use when responding to a breach/compromise/security incident, writing an IR plan or runbook, or producing a post-incident report. Produces a phase-by-phase response (triage, contain, eradicate, recover, post-incident) with the immediate actions, comms, evidence-handling, and a blameless review. For incidents on systems you own or defend.

Draft answers to a vendor security questionnaire (SIG, CAIQ, or a custom sheet) from your real controls — fast, consistent, and honest about gaps. Use when asked to fill out a security questionnaire, answer a SIG/CAIQ, respond to a customer's security review, or complete a vendor risk assessment. Produces drafted answers grounded in your stated controls, a gap list of questions you can't truthfully answer yet, and reusable answer snippets for next time — never fabricated compliance.

Review a design, PR, or feature for security issues before it ships. Use when asked to do a security review, security-review a change/PR, or check a feature for vulnerabilities. Produces a structured review across the common risk areas (authn/authz, input handling, secrets, data exposure, dependencies), findings ranked by severity with concrete fixes, and a ship / fix-first verdict. For code and systems you own or are authorized to review.

Write a STRIDE-based threat model for a service or feature. Use when asked to produce a threat model, document security risks, identify attack vectors, assess a service's security posture, or prepare for a security design review. Produces a structured threat model covering assets, trust boundaries, STRIDE threat enumeration per component, risk scores, mitigation controls, and residual risk sign-off.

Write a performance self-review that's specific, evidenced, and balanced. Use when asked to write a self-review, self-assessment, or self-evaluation for a performance cycle. Produces a complete self-review — accomplishments mapped to impact and competencies, growth areas owned honestly, and a forward-looking development plan, in the voice of the person being reviewed.

Walk a space — home, office, commute, classroom — and find the sensory landmines quietly draining or overloading you, with fixes ranked by cost and impact. Use when someone says 'my office wrecks me and I don't know why', 'I'm overstimulated all the time', 'make my home autism/ADHD-friendly', or lives with SPD, autism, migraine, or misophonia. Produces a room-by-room sensory map, a ranked fix list (free → cheap → invest), and a portable kit for spaces you can't change. A self-help audit, not a clinical assessment.

Create a structured SEO content brief for any target keyword or topic. Use when asked to write an SEO brief, content brief, keyword brief, or content strategy document. Produces a complete brief with target keyword, search intent, outline, competitor insights, internal links, and on-page SEO guidance.

Diagram an interaction as a sequence of messages between participants over time. Use when asked to show an API flow, request/response, auth handshake, integration, or 'what calls what in what order'. Produces a ready-to-render Mermaid sequence diagram (renders live, exportable as PNG/SVG) plus notes on edge cases and failure paths.

Build an onboarding and training guide for restaurant front-of-house staff (servers, hosts, bartenders). Use when asked to train a new server, create FOH onboarding, write service standards, or build a restaurant training program. Produces a phased training plan (shadow → hands-on → solo with support), the service-sequence standards, menu and allergen knowledge checks, POS and side-work basics, and a sign-off checklist that says when someone's ready to work a section alone.

Write a service catalog entry for a microservice or internal platform service — covering service identity, purpose, architecture context, SLAs, API contract summary, data classification, dependencies, operational runbooks, and known limitations. Use when asked to document a service for an internal developer portal, write a service README for a platform catalog, create a service overview page, or onboard a new service to a service registry. Produces a complete service catalog entry suitable for an internal developer portal or wiki.

Write a handoff summary so another agent or person (or a fresh session) can pick up the work with full context. Use when ending a work session, hitting a context limit, switching agents, or pausing a task mid-flight. Produces a structured handoff: what the goal is, what's done, the current state, what's next, and the gotchas — so no context is lost across the boundary.

Decode a severance agreement before you sign it — what you're giving up, what's negotiable, and the deadlines that decide your leverage. Use when asked to decode my severance, is this severance offer normal, review my separation agreement, or should I sign this release. Produces a clause-by-clause decode with ranked red flags, the money math (severance vs what you're releasing), the consideration-period clock, and the asks worth making.

Clean up a shared drive nobody owns — the ownership-first move, the top-down audit that finds the 80% (stale projects, duplicates, ex-employee folders), the archive-don't-delete discipline for shared property, and the norms that prevent regrowth. Use when asked our shared drive is a disaster, clean up the team drive, who owns all these folders, or people are scared to delete anything. Produces the audit map, the archive plan with the fear-killing rule, the ownership assignments, and the going-forward norms.

Build a staff shift schedule that matches coverage to demand while hitting a labor-cost target. Use when asked to build a shift schedule, staff a rota, plan coverage for a restaurant/retail/shift-based team, or balance labor cost against service. Produces a day-part coverage plan mapped to forecast demand, role-by-role assignments, the projected labor cost vs. target, and the fairness/compliance guardrails (rest between shifts, overtime, availability).

Write a short-form video script for TikTok, Instagram Reels, or YouTube Shorts — built on the hook→retention→payoff structure that drives watch-time. Use when asked to script a Reel, TikTok, Short, or any 15–60s vertical video. Produces a timed script with a 0–3s hook, retention beats with on-screen text and B-roll cues, a payoff, and a CTA — plus a caption and on-screen-text list. Distinct from long-form YouTube scripting.

Get an honest read on whether to quit or keep going on a project, job, hobby, or goal that's become a slog — distinguishing a dip worth pushing through from a dead end worth leaving. Use when asked should I quit this, is it time to give up on, push through or walk away, or I don't know if I should keep going. Produces a diagnosis of whether you're in a temporary dip or a genuine dead end, the sunk-cost and identity traps clouding the call, honest signals pointing each way, and a clear push / pivot / quit recommendation — because both quitting too early and quitting too late are expensive.

Gut-check a message before you send it — is it going to land the way you intend, or will you regret it in an hour? Use when asked should I send this, is this message okay to send, check this before I hit send, or will I regret this text/email. Produces a read on how the message will actually land for its recipient, the parts that could be misread or that you're sending from emotion, whether now is the right time to send it at all, and a calmer rewrite if needed — catching the hot, snippy, or oversharing message before it does damage you can't undo.

End the workday on purpose — the ten-minute shutdown that closes open loops, stages tomorrow's start, and gives the brain permission to actually stop (the incomplete-task hum has an off switch, and it's written). Use when asked I can't stop thinking about work at night, build an end-of-day routine, my evenings are ruined by open loops, or how do I stop checking one more time. Produces the shutdown checklist, the tomorrow-staging step, the closing phrase, and the after-hours boundary rules.

Get siblings onto one team about aging parents before the crisis does it for them — a structured family meeting with an agenda that prevents old-roles regression, a fair-not-equal division of care work (money, time, and proximity counted honestly), decision rules for when parents can't decide, and the written summary that prevents six months of 'nobody told me'. Use when someone says 'my siblings and I need to talk about mum', 'my brother does nothing', 'we keep fighting about dad's care', or before a parent's health forces it. Produces the summit agenda, the care-share worksheet, and the family memo.

Set up a side business in the right order — the do-first sequence (separate money, basic terms, simple records) vs. the feels-official-but-waits list (logos, LLCs-by-default, office chairs), with the structure question framed honestly and routed properly. Use when asked I'm starting a side business what do I need, do I need an LLC, set up my side hustle properly, or what comes first legally and financially. Produces the ordered setup sequence, the structure-decision framing (jurisdiction-flagged, professional-routed), the money-hygiene rules, and the employer-conflict check most people skip.

Answer 'is this site down or is it just me' properly — curl status/timing diagnostics, DNS cross-check, and TLS certificate reads, assembled into a where-it's-broken diagnosis. Use when asked is this website down, why can't I reach this site, check if my site is up, or is the SSL certificate expired. Produces the layered diagnosis (DNS → TLS → HTTP → content), response timing, cert expiry, and the rerunnable commands.

Produce a toolbox talk or pre-task safety briefing from the day's planned construction work. Use when asked to write a toolbox talk, prepare a pre-task plan or JHA/JSA briefing, brief a crew on today's hazards, or plan safety for a specific task like a crane pick, excavation, or hot work. Produces a crew-ready briefing with task-specific hazards, controls ordered by the hierarchy of controls, required permits, and explicit stop-work triggers.

Fuse two skills from this library into one hybrid brief for a task that sits between them — the meta-skill. Use when a task straddles two skills (a PRD that's also a pitch; a postmortem that must double as a board update) and running them separately would produce two documents where one is needed. Produces the fused operating brief: combined structure, merged quality bar, precedence rules for where the parents disagree, and the fused output itself if input was provided.

Audit a Claude/Agent SKILL.md (or any AI skill / system prompt) for safety before installing or merging it. Use when asked to review a skill for security, check a prompt for injection, vet a community skill, or assess whether an instruction file is safe to run. Produces a risk-rated report of findings (prompt injection, data exfiltration, code execution, secrets, hidden text) with severity, evidence, and a clear install / don't-install recommendation.

Vet an agent skill before installing it — read the SKILL.md and any scripts for the red-flag patterns (credential access, obfuscation, exfiltration, prompt injection), audit its blast radius, and produce a risk-tiered verdict. Use when asked is this skill safe to install, vet this SKILL.md, review this skill from a marketplace, or check what this skill can do to my machine. Produces the risk classification with quoted evidence, the permission-surface audit, the red-flag checklist results, and an install/sandbox/reject recommendation.

Diagnose why you've stopped improving at something and get a plan to break through the plateau. Use when asked I've stopped getting better at, I'm stuck at the same level, how do I improve past this plateau, or why am I not improving. Produces a diagnosis of why you've plateaued (comfort-zone practice, missing feedback, a specific weak sub-skill, or just needing recovery), the specific change that resumes progress, a targeted practice plan for your actual bottleneck, and honest expectations — because plateaus are usually a practice problem, not a talent ceiling.

Build a realistic plan to fix bad sleep — a wind-down routine, a consistent schedule, and the daytime and environment fixes that actually move the needle. Use when asked to fix my sleep, I can't sleep, help me sleep better, or build a bedtime routine. Produces a read on the likely disruptors, a wind-down sequence, schedule and light/caffeine timing, environment tweaks, and a 'what to do when you can't fall asleep' rule — flagging that persistent insomnia or symptoms like snoring/apnea warrant a doctor.

Build a real, editable PowerPoint (.pptx) deck from an outline or brief. Use when asked to make a slide deck, a PowerPoint, a pitch/board/sales deck as an actual file, or to turn a doc/notes into slides. Produces an actual .pptx via a generated python-pptx script — a title slide, one idea per content slide with a clear headline and concise bullets, and consistent styling. Requires a code-execution environment (Claude Code, the API code tool, or Claude.ai).

Fix slides that are documents in landscape mode — the one-point-per-slide rule, the projection-vs-reading fork that decides density, the text diet (headlines and evidence, prose to notes), and the glance test. Use when asked my slides are too busy, how much text per slide, fix this wall-of-bullets deck, or make this readable from the back of the room. Produces the density diagnosis, the per-slide fixes (split, strip, or move-to-notes), the projection/document fork decision, and the glance-test results.

Define Service Level Objectives (SLOs) and an error budget policy for a service. Use when asked to write SLOs, define SLIs, calculate an error budget, set reliability targets, or create an error budget policy. Produces a complete SLO document with SLI definitions, target calculation, error budget policy, burn rate alerts, and review cadence.

Prepare a small-claims case end to end — the demand letter that often settles it first, the evidence pack, what to file, and a plain-English walkthrough of the hearing. Use when asked to take someone to small claims, sue in small claims court, prepare a small claims case, or someone owes me money and won't pay. Produces a final demand letter, the claim summary with amount and legal-ish basis, the organized evidence pack, a filing checklist, and a calm hearing script — flagging jurisdiction limits to verify. Not legal advice.

Survive (and even enjoy) small talk — how to start it, keep it going past the weather, and exit gracefully — for people who find it painful. Use when asked I'm bad at small talk, help me with small talk, what do I say at [event], or how do I make conversation. Produces conversation openers that fit the setting, the technique for keeping it flowing (curiosity, follow-up questions, the little disclosures that deepen it), how to get past surface topics toward something real, graceful exit lines, and the reframe that small talk is a bridge, not the destination — tuned to the specific situation you're dreading.

Structure a clinical encounter into a clean SOAP note. Use when asked to write a SOAP note, document a patient encounter, turn visit notes into clinical documentation, or structure subjective/objective/assessment/plan. Produces a well-organised SOAP note — Subjective, Objective, Assessment (with differential), and Plan — from the provided encounter details, in standard clinical-documentation style.

Assess SOC 2 readiness across the Trust Services Criteria and produce a gap remediation plan. Use when asked to prepare for a SOC 2 audit, run a SOC 2 readiness/gap assessment, scope controls, or get audit-ready. Produces a readiness report — scope & criteria, a control-by-control status, a weighted readiness score, prioritised gaps with owners, and the evidence each control needs.

Plan and write a paid social advertising campaign. Use when asked to build a paid social campaign, create Meta/LinkedIn/TikTok/X ad copy, define a social ad strategy, or plan an advertising funnel across social platforms. Produces a complete campaign plan with audience targeting, ad set structure, copy for each ad format, budget allocation, and measurement framework.

Audit an existing social media presence across all active platforms. Use when asked to review social media performance, analyse a brand's social presence, benchmark against competitors, or identify what's working and what isn't. Produces a scored audit with platform-by-platform analysis, content performance review, competitive benchmarking, and a prioritised action plan.

Build a social media strategy for a brand, product, or creator. Use when asked to create a social media strategy, define a social content strategy, plan content pillars, set social KPIs, or build a posting framework. Produces a complete strategy with audience definition, platform selection, content pillars, posting cadence, KPIs, and a 4-week starter calendar.

Model whether solar panels pay for themselves for your roof — net cost after incentives, bill offset with degradation, electricity inflation, the inverter replacement, and the breakeven year, plus the policy risk no calculator controls. Use when asked are solar panels worth it, when does solar break even, check this solar quote's payback claim, or model solar for my bill. Produces the year-by-year table from the script, the breakeven year, the quote-vs-model comparison, and the not-modeled list led by net-metering risk.

Write a Standard Operating Procedure (SOP) for any operational task. Use when asked to write an SOP, standard operating procedure, work instruction, or operating manual. Produces a formal SOP with purpose, scope, procedure steps, quality checks, and version control.

Prepare a journalist to interview a source or subject — including hostile or accountability interviews. Use when a reporter needs to prep an interview with a source, plan questions for a subject, handle an on-the-record accountability interview, or get a reluctant person to talk. Produces a question plan sequenced from rapport to the hard asks, ground-rules handling (on/off record, attribution), techniques for evasive or hostile subjects, and a capture plan. Distinct from expert-interview-prep (learning from an expert).

Assess and reduce the risk of exposing a confidential journalistic source. Use when a reporter is working with a confidential source, a whistleblower, or sensitive leaked material and needs to protect the source's identity. Produces a risk assessment (how the source could be identified — metadata, comms, patterns, documents), secure-communication and handling practices, a redaction/anonymization plan for what's published, and the promises to make (and not make) about protection. Guidance is defensive; it is not legal advice.

Verify a claim before repeating it — the independent-sources test (three citations of one press release is one source), the provenance trace to the original, and the confidence grading that separates established from echoed. Use when asked is this claim actually true, verify this stat before the deck, everyone cites this number where's it from, or how solid is this source. Produces the provenance trace, the independence assessment, the confidence grade with its reasoning, and the repeat-it-as phrasing.

Build a talent sourcing strategy for a hard-to-fill role. Use when asked to create a sourcing strategy, a candidate sourcing plan, a channel plan for hiring, or to figure out where to find candidates for a role. Produces a strategy — the ideal-candidate profile and where they are, prioritised sourcing channels, outreach approach, a pipeline target with funnel math, and a weekly plan — so sourcing is deliberate, not just posting and praying.

Figure out why the loaf came out dense, flat, or gummy — and what to change next bake. Use when asked why is my sourdough [dense/flat/gummy/not rising], my starter isn't bubbling, help fix my bread, or troubleshoot my sourdough. Produces a likely-cause diagnosis from your symptoms and process, the specific fix for the next bake, a starter-health check, and a simple timing/temperature adjustment — no dogma, just the variable that's actually off.

Set up a spaced-repetition system to actually remember what you learn — good cards, the right review rhythm, and the mistakes that make flashcards useless. Use when asked help me memorize, set up flashcards / Anki, how do I remember what I study, or spaced repetition for. Produces card-writing guidance (atomic, one-fact, testable — not walls of text), a review cadence that leverages the forgetting curve, what's worth making cards for vs not, and the common failure modes that make people quit — turning cramming-and-forgetting into durable memory.

Turn three minutes at a council or community meeting into the version that actually moves the decision — a public comment built as ask-story-evidence-ask, timed to the real decision process, with a neighbor coalition plan and the written follow-up officials can act on. Use when someone says 'I want to speak at the council meeting', 'they're planning X on our street', 'how do I fight this decision', or 'write my public comment'. Produces the 3-minute speech, the one-page leave-behind, and the campaign timeline.

Budget limited energy the way spoon theory describes it — count your realistic daily 'spoons', price what each task actually costs (including the invisible ones), protect the non-negotiables, and plan for the days you'll have far fewer. Use when someone says 'I only have so much energy', 'help me pace with my chronic illness', 'I keep crashing', or lives with ME/CFS, long COVID, fibromyalgia, POTS, MS, or any limited-capacity condition. Produces a spoon budget, a task price list, and a pacing plan that respects payback and post-exertional crashes. A self-management tool, not medical advice.

Get live scores, schedules, and standings for major leagues with zero API keys — ESPN's public JSON endpoints via curl, covering NFL, NBA, MLB, NHL, and world football. Use when asked what's the score, did my team win, today's games, or league standings right now. Produces the scores with game state (live/final/scheduled), the asked-team answer first, and the rerunnable command — with the unofficial-API caveat stated.

Learn to recognize where and how AI tends to go wrong — the specific failure patterns — so you catch its mistakes on sight instead of getting burned by confident errors. Use when asked how do I know when AI is wrong, what are AI's common mistakes, how do I catch AI errors, or where does AI mess up. Produces the failure patterns most relevant to how you use AI (hallucinated facts, fake citations, outdated info, sycophancy, math slips, missed nuance), the tells that give each away, a quick check for the ones that would hurt you, and a calibrated trust level — so you develop the instinct to catch AI's errors before they cost you.

Audit a spreadsheet before trusting it — the error hunt (hardcoded overrides, broken ranges, silent unit mixes), the fragility map (what breaks when rows are added), and the load-bearing-formula review that catches the mistake before the meeting does. Use when asked check this spreadsheet before we present it, why don't these numbers add up, audit this model someone left behind, or is this sheet safe to build on. Produces the findings ranked by damage, the fragility map, the verified-vs-suspect ledger, and the fix list.

Audit the user's REAL spreadsheet by opening it in the Cowork sandbox — not by reading a description of it. Use when asked to check this sheet before we present it, audit the model in my Drive, why don't these numbers add up, or is this spreadsheet safe to build on. Pulls the file via the Google Drive connector (or an uploaded .xlsx), opens it programmatically in the sandbox to trace formulas, hunts hardcodes / broken ranges / unit mixes, and produces a ranked findings artifact with a verified-vs-suspect ledger and a fix list.

Hand over a spreadsheet so it survives its author leaving — the README tab that decodes the sheet's logic, the update runbook with sources and cadence, the fragility warnings, and the walkthrough that transfers the judgment. Use when asked document this spreadsheet before I leave, hand over the model to the team, make this sheet survivable without me, or we inherited a workbook nobody understands. Produces the README tab content, the update runbook, the known-fragilities list, and the handover walkthrough agenda.

Decide honestly when a spreadsheet should become a database or app — the five outgrowth signals (concurrent editing, relational strain, permission needs, scale, process-in-comments), what staying costs vs what migrating costs, and the incremental escape paths. Use when asked should this be a database, our spreadsheet is breaking, is it time to move off sheets, or what should replace this monster workbook. Produces the signal assessment on the actual workbook, the stay-vs-move verdict with costs both ways, and the migration path sized to the team.

Generate a structured sprint brief from sprint data and goals. Use when asked to write a sprint brief, create a sprint summary, document sprint goals and scope, or produce a team-facing sprint overview. Produces a scannable brief with sprint goal, rationale, grouped work, critical path, risks, and definition of done.

Structure and facilitate sprint planning sessions. Use when asked to plan a sprint, organise backlog items, assign story points, create sprint goals, or prepare sprint planning agendas. Produces a sprint goal, velocity-calibrated backlog, capacity plan, risk flags, and a structured sprint planning meeting agenda.

Run a sprint retrospective that produces real change — themes from what actually happened, honest start/stop/continue, and owned action items, not a vent session. Use when asked to facilitate a retro, run a sprint retrospective, prep retro themes, or turn our sprint into a retro. Produces the data-grounded themes (from done/WIP/blocked work and any flow metrics), a start/stop/continue, 2–4 owned action items with checks, and a follow-up on last retro's actions so retros stop repeating themselves.

Analyze sprint velocity data and produce an engineering team health report covering delivery trends, capacity utilization, and improvement recommendations. Use when asked to analyze sprint velocity, review team delivery health, identify delivery risks, or produce a retrospective data analysis. Produces a velocity trend analysis, health diagnosis table, top improvement recommendations with implementation steps, and a next-sprint capacity forecast.

Diagnose a slow SQL query and produce a concrete optimization plan. Use when asked to optimize SQL, speed up a slow query, reduce a query's cost/scan, fix a timeout, or review a query plan. Produces an analysis — the likely bottleneck, what the plan is doing wrong (full scans, bad joins, spills), the specific rewrite and index/partition changes, and the expected impact, with the optimized query.

Explains, optimises, writes, and documents SQL queries. Use when asked to explain a SQL query, optimise slow SQL, translate SQL to plain English for non-technical stakeholders, write a query from a natural language description, or produce query documentation. Produces plain-English explanations, annotated optimised queries, or a data dictionary covering output shape, assumptions, and known limitations. Works across PostgreSQL, MySQL, BigQuery, Snowflake, and standard SQL.

Set up deposits and stage payments that protect a tradesperson from the customer who won't pay AND read as fair to the customer — stage triggers tied to visible milestones, deposit sizing by job type, the payment terms paragraph for quotes, and the scripts for late stages. Use when a tradesperson asks 'how much deposit should I take', 'customer hasn't paid the second stage', 'payment terms for my quotes', or got burned on a big job. Produces a stage-payment schedule, the terms paragraph, and firm-but-professional chase scripts.

Map stakeholders for a product decision and produce a tailored influence strategy with talking points. Use when asked to get alignment, build consensus, get buy-in from engineering or finance or legal, navigate organisational resistance, or plan stakeholder conversations for a major initiative. Produces a stakeholder map, recommended conversation sequence, and tailored talking points per stakeholder.

Create concise executive stakeholder updates using the BLUF (Bottom Line Up Front) framework. Use when asked to write a status update, progress report, project communication, or executive briefing for leadership or stakeholders. Produces a BLUF-led update with status, key metrics, risks, upcoming milestones, and decisions needed — readable in under 2 minutes.

Audit the recurring meetings a team has accreted — each standing slot tested against its original purpose, current attendance reality, and outcomes, with keep/shrink/merge/kill verdicts and the two-week cancellation experiment that settles arguments. Use when asked audit our recurring meetings, our calendar is all standing syncs, which meetings should die, or reset the team's meeting load. Produces the inventory with per-meeting verdicts, the experiment protocol, the merge map, and the re-accretion guard.

Plan a stargazing session for tonight from where you are — what's worth looking for, when and where to look, and how to see it with just your eyes or basic gear. Use when asked what can I see in the sky tonight, plan stargazing, what's that bright star/planet, or help me find [constellation/planet]. Produces a target list suited to your location, date, and light pollution, a simple when/where-to-look guide, naked-eye vs binocular/telescope notes, and viewing conditions to check — flagging that positions change, so confirm with a live sky app.

Pressure-test a startup idea the way a sharp investor or co-founder would — problem, market, wedge, moat, why-now, and the fastest cheap way to test it. Use when asked to validate a startup idea, evaluate a business idea, stress-test a concept, or decide whether something is worth building. Produces an honest assessment with the strongest case, the killer risks, and the next experiment to run — not cheerleading.

Coach a statement of purpose or personal essay to admission strength — structural diagnosis, specific feedback, and revision plans on YOUR draft; the words stay yours. Use when asked to review my personal statement, improve my SOP, give feedback on my application essay, or why is my essay generic. Produces a diagnostic against what committees actually read for, line-level feedback on the draft, a revision plan, and interview-style questions to mine for better material.

Write a tight Statement of Work (SOW) that prevents scope creep and payment disputes. Use when asked to write a SOW, a scope of work, a project agreement, or to formalise what was agreed after a proposal. Produces an SOW — scope (and explicit exclusions), deliverables with acceptance criteria, timeline & milestones, payment schedule, assumptions, change-control, and terms. The contract layer after the proposal sells.

Build the pipeline that turns team updates into the rollup report without the Friday scramble — the collection format that aggregates cleanly, the altitude translation (team detail → leadership signal), and the automation-lite assembly that takes minutes. Use when asked I compile status from five teams every week, streamline our reporting chain, my Friday is spent chasing updates, or make the rollup write itself. Produces the collection design, the translation rules, the assembly routine, and the chase-elimination mechanics.

Take the option you dismissed in two seconds and build the strongest possible case for it — to check whether your fast 'no' was wisdom or just bias. Use when asked to steelman this, make the case for the option I rejected, argue the other side properly, or why might the weird choice be right. Produces the strongest honest argument for the dismissed option, the conditions under which it's actually the best choice, what your quick rejection assumed, and a fair verdict on whether the reconsideration changes anything — the opposite of a strawman.

Fetch a stock quote snapshot with keyless curl — Yahoo Finance's public chart endpoint, read with the discipline unofficial market data demands: timestamped, delayed-flagged, and never advice. Use when asked what's this stock at, how did the market do today, get me a ticker's recent range, or pull basic price history. Produces the quote with change and range context, the source-honesty caveats (unofficial, possibly delayed), the rerunnable command, and a hard no-advice line.

Recover from a professional setback — a failed launch, brutal feedback, a public mistake, a lost deal, a layoff — using the actual exercises from Marcus Aurelius' Meditations: the control sort, the evening review, and turning the obstacle into the task. Use when someone says 'today went badly', 'I blew it', 'the launch failed', 'I got torn apart in that meeting', or before replying to something that stung. Produces a structured debrief that separates what happened from the story, and ends in one next action.

Break an analysis-paralysis loop on a small or reversible decision — set a limit, force a call, and move on. Use when asked I'm overthinking this, help me just decide, I keep going back and forth, or this shouldn't be so hard. Produces a quick read on whether this decision even deserves deliberation (most don't), the realization that the options are probably close enough that it doesn't matter much, a forced pick via a simple rule, and permission to move on — because the overthinking is costing more than a slightly-wrong choice ever would.

When money is in free-fall, triage the crisis — what to pay first, what to let slide, and what to protect at all costs — so you cover the essentials and stop the worst damage. Use when asked I can't pay all my bills, which bills do I pay first, financial emergency, or I'm broke and panicking. Produces a priority order for scarce money (keep-the-lights-on essentials and things with severe consequences first, unsecured debt last), what to protect no matter what (housing, utilities, food, transport to work, essential insurance), which creditors to call and what to ask for (hardship programs, deferrals), the help to tap now (assistance programs, food banks), and a calm next-24-hours plan — so panic becomes a sequence. Not financial advice; points to nonprofit credit counseling and assistance programs.

Pitch a news or feature story to an editor — the angle, why now, and how you'll report it. Use when a reporter or freelancer needs to pitch a story, sell an editor on an angle, or write a query letter to a publication. Produces a tight pitch: the hook and angle, why it matters and why now, the reporting plan and sources, your access/credibility, and the format/length fit. Distinct from media-pitch (PR pitching a story TO journalists).

Generate the strategic story connecting a product roadmap to company goals in a form non-technical stakeholders can repeat. Use when asked to explain the roadmap, present strategy to leadership or the board, write the why behind the roadmap, create a narrative for all-hands, or make the roadmap tell a story. Produces a themed narrative with executive summary, progression arc, hard-question preparation, and what's-not-on-the-roadmap section.

Write a strategy memo that commits to a bet and says what you won't do. Use when asked to write a strategy memo, articulate a strategy, make the case for a strategic direction, or align the team on where to focus. Produces a strategy memo — the strategic question, the diagnosis, the bet/approach, why now, explicit non-goals (what we're NOT doing), how we'll know it's working, and the risks.

Build a targeted stretching or mobility routine for the tightness you actually have — desk-stiff hips, a tight back, post-run legs — not a generic list. Use when asked for a stretching routine, my [back/hips/neck] is tight, mobility routine, or stretches for [activity]. Produces a short routine for the target area with hold times and cues, a warm-up vs recovery distinction, a daily-minimum version, and a plain 'ease in, don't force pain, see a pro for sharp/ongoing pain' note.

Write constructive, specific feedback on student work that motivates and tells the student exactly how to improve. Use when asked to give feedback on a student's work, write grading comments, respond to an essay or assignment, or coach a learner. Produces feedback that names concrete strengths, prioritises the few changes that matter most, and gives an actionable next step — warm in tone, growth-oriented, never just a grade.

Decide what the extra money does about student loans — attack them, invest alongside them, or ride a forgiveness track — with the three paths simulated on your actual loans and the guaranteed-vs-assumed framing kept honest. Use when asked should I pay off my student loans faster, pay loans or invest, is my forgiveness track worth it, or model my student debt. Produces the three-path comparison from the script, the guaranteed-return framing, the forgiveness-track math with its warnings, and the decision sheet.

Turn lecture notes, slides, and readings into one exam-ready study guide — synthesis, not summary. Use when asked to make a study guide, combine my notes, prep me for the exam, or organize this course material. Produces a structured guide: core concepts with plain-language explanations, connections between topics, worked examples where the subject has them, self-test questions, and an honest list of gaps in the source notes.

Study 3-5 documents the user actually shipped and distil a compact style card — so every skill writes in their voice, not the model's. Use when asked to learn my writing style, make outputs sound like me, build a voice profile, or when a user complains AI drafts don't sound like them. Produces a style card (rhythm, register, structure habits, pet phrases, banned moves) saved to the Brain where every other skill reads it.

Decompose work across parallel subagents properly — task slicing that avoids collisions, briefs that stand alone, and result integration that catches contradictions. Use when work can genuinely parallelise (research fan-outs, multi-file changes, independent analyses), when deciding whether to delegate or do it yourself, or when past multi-agent runs produced conflicts and duplicated effort. Produces an orchestration plan: the parallel/sequential split, per-agent briefs, and the integration protocol.

Score a subcontractor's performance across schedule reliability, quality, safety, paperwork, and change-order behaviour with weighted anchors. Use when asked to evaluate a sub, build a subcontractor scorecard, decide whether to rebid or rehire a trade, review sub performance for prequalification, or justify removing a sub from the bid list. Produces a weighted scorecard with per-dimension anchored ratings, evidence notes, and an award/retention recommendation.

Find and rank the recurring-payment leak — every subscription annualized, sorted by real yearly cost, with the keep/cancel/downgrade pass and the where-they-hide checklist. Use when asked audit my subscriptions, how much am I spending on subscriptions, help me cancel stuff, or what recurring charges am I forgetting. Produces the annualized ranking from the script, the hidden-subscription hunt list, the keep/cancel/downgrade decisions with the cancellation friction notes, and the re-audit cadence.

Find the subscriptions you forgot you pay for — a tool-using agent audits statements and inboxes, prices the waste annually, and preps (never executes) the cancellations. Use when asked to audit my subscriptions, find recurring charges, what am I paying for, or help me cancel unused services. Produces the subscription inventory with keep/cancel/downgrade verdicts, the annual-waste number, and approval-gated cancellation prep.

Scrapes a Substack Notes page and exports engagement data to a formatted .xlsx file. Use when asked to download, analyse, or export Substack Notes performance data including likes, comments, and restacks. Produces a formatted spreadsheet with conditional formatting, summary stats, and per-note engagement metrics.

Write or translate subtitles/captions that respect reading speed and timing rules. Use when asked to write subtitles, captions, SRT/VTT content, or to translate subtitles for a video. Produces properly-formatted, readable subtitles — line-length and reading-speed compliant, well-segmented, with translation that fits the time available, plus SDH/caption guidance where relevant.

Turn a long article, email thread, document, or transcript into a tight summary you can act on — the gist, the key points, and what it means for you. Use when asked for a TL;DR, to summarize this, give me the gist, or the key takeaways. Produces a one-line TL;DR, the key points as scannable bullets, any decisions/action items with owners, and open questions — faithful to the source, with nothing invented and important caveats kept.

Get sunrise, sunset, golden hour, day length, and moon phase for any location with zero API keys — sunrise-sunset.org and Open-Meteo via curl, times converted to local. Use when asked when is sunset today, golden hour for a photo shoot, how long is the day, what's the moon phase tonight, or sun times for a date and place. Produces the sun/moon times in the user's local zone (the UTC trap handled), the photography windows, and the rerunnable command.

Prepare for a specific contest — a competitive deal, a negotiation, a market entry, a turf fight — using the actual planning framework from Sun Tzu's Art of War: the five factors, the calculations before battle, and winning without fighting. Use when facing a competitor head-to-head, preparing a bake-off or RFP, entering a rival's market, or picking which fight to have. Produces a strategy brief with a fight/no-fight verdict.

Build a quarterly supplier performance scorecard with a weighted grade and a clear escalate/develop/exit call. Use when asked to review supplier performance, prepare a quarterly business review for a vendor, score a supplier on OTIF and quality, or decide whether to escalate or exit a supplier. Produces a weighted scorecard with trend arrows, per-dimension evidence, corrective-action status, and a recommendation.

Show up well for someone going through something hard — loss, illness, a breakup, a crisis — with the right words, the right presence, and concrete help, instead of freezing or saying the wrong thing. Use when asked how do I support a friend going through, what do I say to someone who's struggling, my friend is in crisis, or how can I help someone grieving. Produces what to actually say (and the clichés to avoid), how to be present rather than fix, specific concrete help to offer, how to keep showing up over time, and how to look after yourself — with a clear flag to steer them to professional/crisis help when it's beyond a friend.

Write reusable support macros / canned responses that sound human, not robotic. Use when asked to write a support macro, a canned response, a saved reply, or a template for a common customer ticket. Produces a macro — an empathetic opener, the clear answer/steps, placeholders for personalisation, and a warm close — plus variants (resolved / need-more-info / escalating), tuned to keep it human.

Write a support runbook for handling a recurring issue type consistently. Use when asked to write a support runbook, a troubleshooting playbook for agents, a handling guide for a common issue, or a tier-1 response procedure. Produces a runbook — issue identification, triage/severity, step-by-step diagnosis & resolution, decision tree, when/how to escalate, and the customer-comms templates — so any agent resolves it the same way.

How many support agents does the queue actually need — Erlang C, computed, not 'tickets per agent' folklore. Use when staffing a support/CS team, defending headcount, or checking whether an SLA is mathematically possible with the current roster. Produces agent counts across load scenarios (with shrinkage), occupancy and average-wait numbers, and a real .xlsx — via the bundled zero-dependency script.

Know what to actually say and do for someone who's grieving — the real help instead of the empty 'let me know if you need anything.' Use when asked what do I say to someone whose parent died, how do I support a grieving friend, what to write in a condolence, or how to help without making it worse. Produces words that land (and the phrases to avoid), specific concrete help to offer instead of vague availability, a condolence message in your voice, guidance on showing up over the long haul (not just week one), and how to support without centering yourself — so your care actually reaches them. Points to grief resources when the person needs more than a friend can give.

Design a survey that measures instead of leads — neutral question wording, answer scales that don't smuggle conclusions, the length that respects completion rates, and the analysis plan written before launch. Use when asked write our customer/employee survey, check these questions for bias, why are our survey results useless, or design the questionnaire for this decision. Produces the question set with bias fixes, the scale choices, the pilot step, and the pre-launch analysis plan.

Flip Claude’s default from validation to adversarial critique. Use when you are about to make a high-stakes decision, commit to a plan, or pitch something you have not stress-tested. Produces structured challenges, steelmanned counter-arguments, and the strongest case against your position — a genuine thinking partner, not a mirror.

Use AI personas for early-stage research signal — with hard guardrails on what synthetic methods can and cannot validate. Use when asked to run synthetic user testing, simulate user reactions with AI personas, pretest a survey or message before fielding it, or decide whether synthetic research is appropriate at all. Produces a fit verdict for the question at hand, a persona-panel design grounded in real data, the findings labelled as synthetic throughout, and the follow-up plan with real humans. Never a substitute for discovery interviews — see discovery-interview-guide and user-research-synthesis for the real thing.

Structure a complete system design answer for interview questions or real architecture sessions. Use when asked to design a system, answer a system design interview question, or architect a solution at scale. Produces a structured answer covering requirements, capacity estimates, high-level design, component deep-dives, trade-offs, and follow-up considerations.

Spin up a tabletop RPG one-shot or a session-zero for a new campaign — a hook, a map of the first adventure, NPCs, and encounters tuned to your party. Use when asked to start a D&D campaign, run a one-shot, help me DM, session zero, or make me an adventure for my party. Produces a premise and hook, a session-zero framework (tone, safety tools, expectations), a first-adventure outline with beats and branches, ready-to-run NPCs and encounters scaled to party level/size, and improv fallbacks for when players go off-script.

Practice the table-talk that wins negotiation board games — play out a Catan-style trade, a Diplomacy-style alliance, or a Monopoly-style deal against an opponent with a hidden agenda, then get an out-of-character debrief scoring your moves. Use when someone says 'I always lose the trading part', 'practice Catan trades with me', 'how do I get better at Diplomacy', or 'roleplay a trade with me'. Produces a played-out negotiation plus a debrief with the reads you missed and one habit to change.

Shrink a task you're avoiding down to a first step so small it's almost impossible not to do — beating activation-energy paralysis. Use when asked I can't get started on, help me start this task, this feels too big to begin, or break this down so I can start. Produces the dreaded task decomposed to a laughably tiny first physical action (open the doc, write one sentence), why that specific step lowers the barrier, and the next couple of micro-steps — so starting stops requiring willpower.

Triage an overwhelming task list into what actually gets done — the urgent/important sort applied honestly (with the two corrections the classic matrix needs), the do/schedule/delegate/drop verbs, and the list hygiene that keeps triage from becoming a weekly archaeology dig. Use when asked my task list is overwhelming, triage my todos, everything feels urgent, or what should I actually work on. Produces the sorted list with verbs, the urgency audit (what's fake-urgent), the drop list with permission, and the intake rule.

Surface the personal tax deductions and credits you might be missing — so you can research them or raise them with your tax preparer before you file. Use when asked what tax deductions can I claim, am I missing any tax breaks, deductions for [job/situation], or help me lower my tax bill. Produces a tailored list of commonly-missed deductions/credits for your situation, what records each needs, the ones worth digging into, and clear flags to verify against current rules or a professional. Educational — not tax advice, and rules vary by country and year.

Generate a structured tax planning checklist and review framework for any individual or business context. Use when asked to review tax planning, prepare for year-end tax, check tax efficiency, or identify tax-saving opportunities. Produces a checklist of considerations, common reliefs, and a review framework. Not a substitute for qualified tax advice.

Orient yourself on your tax-residency situation after moving countries — the questions that determine where you owe tax, the double-taxation and dual-residency traps, and what to pin down before you file — so you know what to ask a cross-border tax professional. Use when someone says 'am I tax resident in [country]', 'do I pay tax in two countries', 'moved countries mid-year, what about tax', or 'tax residency rules'. Produces a residency-question map, the trap list, a document checklist, and the questions for a professional. Strictly not tax advice — it orients and routes to a qualified adviser.

Drive a feature with a disciplined test-driven development loop — red, green, refactor. Use when implementing a feature or fixing a bug and you want tests to lead, or when asked to 'do this with TDD' / write the test first. Produces a step-by-step red-green-refactor plan: the failing test to write first, the minimal code to pass it, and the refactor — one small cycle at a time.

Learn a complex topic in progressive layers — a one-sentence version, then a paragraph, then the real depth — so you build a mental scaffold instead of drowning in detail. Use when asked explain this in layers, teach me X from simple to deep, I need to understand this progressively, or start simple then go deeper. Produces a topic explained at escalating depth (ELI5 → informed-adult → the real thing), each layer building on the last, checkpoints to make sure a layer landed before the next, and where to stop for your actual need — so you never get lost in detail without a frame to hang it on.

Build a 5-minute teach script for any board game so the table starts playing instead of listening — theme first, goal second, a turn third, exceptions only when they come up. Use when someone says 'how do I explain Catan/Wingspan/this game', 'teaching my family a game tonight', 'my rules explanations kill the mood', or 'make a teach script'. Produces a spoken-word teach script with a first-turn walkthrough and a what-to-skip list.

Design a structured lesson plan for any subject, audience, or format. Use when asked to write a lesson plan, course outline, teaching session, workshop curriculum, or training module. Produces a complete lesson plan with learning objectives, activities, timing, assessment, and differentiation guidance.

Track a team's budget so surprises die young — the commitment-based view (spent + committed + planned, not just invoiced), the category grain that matches how the team actually spends, the monthly close with its one-sentence read, and the forecast honesty for the year-end question. Use when asked track my team's budget, are we going to blow the budget, why did finance's number surprise us, or set up budget visibility for the team. Produces the three-lane tracker (spent/committed/planned), the monthly close ritual, the variance signals, and the year-end forecast method.

Runs a structured team health assessment across key dimensions. Use when asked to run a team health check, assess team morale, facilitate a retrospective on ways of working, or evaluate team dynamics. Produces a health assessment with RAG status per dimension, underlying signals, and prioritised improvement actions with named owners.

Plan a team offsite from goals to full agenda. Use when asked to plan a team offsite, away day, team retreat, quarterly offsite, or team-building event. Produces a full agenda, session designs, facilitation notes, and logistics checklist.

Build a technology radar for an engineering team, categorizing technologies into Adopt/Trial/Assess/Hold quadrants following the ThoughtWorks Tech Radar format. Use when asked to create a tech radar, evaluate the team's technology landscape, categorize tools and frameworks, or establish a technology strategy. Produces a full tech radar with quadrant tables, individual blip rationales, a decision trail, and a maintenance process guide.

Document and prioritize a technical debt backlog with business impact, effort estimates, and resolution strategy. Use when asked to audit technical debt, create a debt register, prioritize tech debt for a quarter, document architectural shortcuts, or build a debt reduction roadmap. Produces a structured technical debt register covering debt inventory by category, business impact per item, effort and priority scores, top-item resolution plans, and a quarterly debt reduction roadmap.

Create structured technical specification documents that bridge product requirements and engineering implementation. Use when writing a tech spec, engineering spec, system design doc, or API specification. Produces a complete spec with problem statement, proposed solution, data model, API design, alternatives considered, security considerations, testing plan, and rollout strategy.

Turn a document the team keeps rewriting into a template that actually helps — extract the recurring skeleton, mark what varies with real placeholder prompts, keep it lighter than the ceremony it replaces, and pilot it before decreeing it. Use when asked make a template from this doc, we write this same thing every week, standardize our status updates or briefs, or why does nobody use our templates. Produces the extracted template with prompting placeholders, the keep-it-light rules, the example-filled twin, and the adoption path.

Understand your rights as a renter in a specific situation — repairs ignored, a rent increase, an eviction notice, deposit disputes, or entry without notice — and what to do next. Use when asked what are my tenant rights, my landlord won't fix [X], is this eviction/rent increase legal, or can my landlord [do something]. Produces a plain-English read of the likely rights at play, the practical next steps (in writing, on the record), the evidence to keep, and where to get authoritative help — flagging strongly that tenancy law is local and this isn't legal advice.

Design a fair, consistent tenant screening process for a rental. Use when asked how to screen tenants, set rental criteria, evaluate rental applicants, or build a tenant screening process. Produces a screening framework — written objective criteria, the application & checks, a consistent evaluation method, and applicant communication — built to be fair and Fair-Housing-compliant. Not legal advice.

Turn a requirement or user story into clear, executable test cases. Use when asked to write test cases, test scenarios, a test suite for a feature, or to derive tests from acceptance criteria. Produces structured test cases — preconditions, steps, test data, expected results — across happy path, edge cases, and negative cases, plus a coverage note, so a tester (or automation) can run them without guessing.

Write a test strategy document from a feature spec, PRD, or system description. Use when asked to create a test plan, write a test strategy, define QA approach, or plan testing for a feature or release. Produces a complete test strategy with scope, risk assessment, test types, coverage targets, and a prioritised test case outline.

Ask happy clients for a testimonial or review the right way — timed well, easy to give, and specific enough to actually persuade future clients. Use when asked to get testimonials, ask for a review, how to request a testimonial, or get social proof from clients. Produces the right moment and channel to ask, a message that makes saying yes effortless, guiding questions that yield specific results-based testimonials (not 'great to work with'), how to handle a written vs video ask, and permission/usage basics — without being pushy or fishing for praise.

Break the paralysis on the thing you keep not starting with a 2-minute launch sequence — a countdown into motion before the resistance can win. Use when asked I keep putting this off, help me finally start, I've been avoiding this for days, or I can't make myself begin. Produces a diagnosis of what flavor of resistance is stopping you, a 2-minute launch move matched to it, a literal countdown into action, and a bare-minimum win definition — designed to convert avoidance into motion in the next 120 seconds, not to make a plan for later.

Scan a plan, draft, or idea for the generic, textbook, everyone-would-say-that lines — and push each toward something sharper and more specific. Use when asked is this too generic, make this less boring, why does my plan feel bland, or spot the clichés in my thinking. Produces a line-by-line flag of the mediocre and predictable parts, why each is forgettable, and a sharper, more specific, or more surprising alternative for each — so the output stops sounding like the average of the internet.

Simulate the car-buying gauntlet before you walk in — the four-square worksheet, the payment-question trap, the trade-in shuffle, and the finance office's second sales floor, all run against your actual deal. Use when asked practice negotiating at a dealership, simulate the finance office, what tricks will the dealer use, or prep me before I buy a car. Produces the showroom and finance-office transcripts with the salesperson's playbook notes, the deal outcome vs your targets, and a debrief with the holds that would have worked.

Simulate the exact customer who will quietly cancel in month 4 — their internal monologue through the lifecycle and the honest exit interview they never gave you. Use when asked why do customers really churn, simulate a churning customer, roleplay the customer who cancels, or what does silent churn look like for my product. Produces the customer's lifecycle monologue, their never-given exit interview, and a debrief with the earliest detectable signals and interventions.

Simulate the due-diligence call where an acquirer's or investor's analyst takes your metrics apart — the questions behind the spreadsheet, the moment a number wobbles, and a debrief on which answers create risk. Use when asked simulate due diligence on my startup, stress-test my metrics before the raise, what will the acquirer's analyst ask, or prep me for the DD call. Produces the call transcript with the analyst's private notes, the internal memo they write afterward, and a debrief separating fixable presentation from fix-the-business findings.

Figure out whether 'the ick' about someone you're dating is a real incompatibility, a genuine red flag, or an anxious/avoidant self-sabotage pattern worth pushing through — by interrogating the specific ick honestly. Use when someone says 'I caught the ick and I don't know why', 'is this a red flag or am I just scared', 'I always find a reason to end things', or is talking themselves out of someone good. Produces a decode of the specific ick, a red-flag vs pattern verdict, and a next move. Honest self-reflection, not a permission slip in either direction.

Simulate the adjuster's settlement call after your accident or loss — the recorded-statement asks, the quick-settlement anchor, the friendly minimization — run against your actual claim, with a debrief on every answer that shrank it. Use when asked the adjuster wants a recorded statement, practice the settlement call, is this settlement offer low, or what will the insurance company try. Produces the call transcript with the adjuster's file notes, the offer trajectory, and a debrief separating fair process from pressure tactics — plus the bright lines that protect a claim.

Simulate a hostile-but-fair journalist interview about your company or announcement — the questions you fear, live follow-ups on every dodge, then the story they'd file. Use when asked to media-train me, simulate a press interview, prep me for a journalist call, or how will this announcement be covered. Produces the interview transcript with your likely stumbles, the article they would write from it, and a debrief with bridge lines and the quotes to prepare.

Say no as an open-source maintainer without burning contributors or yourself — the feature that doesn't fit, the PR that took someone a weekend but can't merge, the company that wants free support, the fork suggestion said kindly. Use when a maintainer says 'how do I reject this PR nicely', 'a company is demanding support', 'this feature request won't die', or is avoiding an issue thread out of guilt. Produces the specific no for the situation, with reasoning shown and the relationship kept.

Cut a full plate down to the single highest-leverage move — the one thing that, done today, makes everything else easier or unnecessary. Use when asked what's the one thing I should focus on, help me prioritize, I have too much on and need to focus, or what matters most today. Produces your list weighed by leverage (not urgency or ease), the single most important thing surfaced with why it beats the rest, permission to let the rest wait, and a first step into it — because doing the one thing that matters beats doing ten that don't.

Simulate the open house and the listing agent's read of you — the questions that profile your budget and urgency, the staging that hides what inspection finds, and the offer-pressure choreography, run before you fall in love with anything. Use when asked what is the listing agent thinking, practice viewing a house, what should I not say at an open house, or simulate the offer pressure. Produces the walkthrough transcript with the agent's private profile of you, the what-the-staging-hides checklist, and a debrief on information discipline — what to ask, what to never volunteer.

Stress-test a proposed org change before announcing it — simulate who gains, who loses, who blocks, where friction erupts in the first 90 days, and run the memo leak test: how does this land when it leaks before you announce it? Use when planning a reorg, changing reporting lines, merging or splitting teams, moving a function, or 'how will this org change land?'. Produces a winners/losers map, a friction forecast, the leak-test read, and a sequenced announcement plan.

Simulate the client who grinds on your price — the budget theater, the competitor quote, the scope squeeze — against your actual offer, with a debrief on where you caved and what holding would have sounded like. Use when asked simulate a client negotiating my rate, practice price pushback, they said I'm too expensive, or stress-test my pricing conversation. Produces the negotiation transcript with the client's private playbook notes, the deal outcome, and a debrief on every concession with its stronger alternative.

Simulate enterprise procurement and security review of your product before your first big deal meets it for real — the questionnaire, the gaps, the deal-slowing findings. Use when asked to prep for enterprise procurement, simulate a security review, why do enterprise deals stall, or get ready for vendor assessment. Produces the reviewer's findings memo (security, legal, compliance, vendor-risk), the stall-risk ranking, and a debrief with the artifacts to prepare before the real gauntlet.

Simulate the calibration meeting that discusses your promotion after your manager leaves the room — the debate, the packet's holes, the verdict. Use when asked will I get promoted, simulate the promo committee, stress-test my promotion packet, or why did my promo get rejected. Produces the committee transcript (four archetypes on YOUR packet), the internal verdict with the real reason, and a debrief separating fixable gaps from timing politics.

Deliberately take the opposite position from your leaning and make you defend yours — a forced second opinion that isn't just an echo. Use when asked give me a real second opinion, don't just agree with me, argue the other way, or I need a fresh take not a yes-man. Produces a committed alternative position to whatever you're inclined toward, the strongest reasons it might be right, the questions it forces you to answer, and an honest read on whether your original leaning still stands after the challenge — countering agreement bias by construction.

See an idea through two committed extremes — a true believer and a hard skeptic — so you get the full range before settling in the middle. Use when asked should I believe this, is this hype or real, give me both sides, or how excited should I be about. Produces the believer's fullest bull case and the skeptic's sharpest bear case (each committed, not hedged), the crux question that separates them, and a grounded read on where the truth probably sits — great for evaluating claims, trends, opportunities, and your own enthusiasm.

Find the real reason to NOT do the exciting thing you're about to commit to — the honest case against, before the excitement carries you in. Use when asked talk me out of this, should I really do this, what's the case against, or I'm excited but is this a mistake. Produces the strongest honest argument for not doing it, the excitement biases clouding your judgment, the specific conditions under which this is a bad idea for you, and a clear read on whether the strong no actually wins — protecting you from the plans that feel great and end badly.

Simulate your thesis defense before the real one — a committee of examiner archetypes probing YOUR actual thesis, the questions you hoped nobody would ask, and a debrief with preparation priorities. Use when asked simulate my thesis defense, grill me on my dissertation, what will my committee ask, or prep me for my viva. Produces the defense transcript with your answers stress-tested, the committee's private deliberation, and a debrief ranking the exposed weaknesses by preparability.

Push past the first few obvious answers to a question and surface the non-obvious idea worth having. Use when asked to give me a non-obvious idea, don't give me the generic answer, think outside the box on, or what's the answer nobody else would give. Produces the obvious answers named and set aside (so we don't repeat them), then genuinely different angles found by continuing past where most thinking stops, each with why it's non-obvious and whether it actually holds up — trading textbook-correct for surprising-and-useful.

Write a sealed memo to your future self or successor — the honest state of things, falsifiable predictions with confidence levels, and the advice you suspect they'll need — with an open-on date and a scoring ritual for when it's opened. Use when leaving a role, finishing a big project, at year-end or planning season, before a leave, or 'write a letter to my successor'. Produces the sealed capsule, its prediction ledger, and the opening-day ritual.

Study 3-5 samples of the user's real writing and decisions, build an explicit 'how you think' profile, then draft new work as their understudy — always with a 'what I couldn't infer about you' list so the gaps are visible instead of guessed. Use when someone says 'write it like I would', 'learn my style', 'draft this as me', or wants an AI that apprentices to their judgment rather than imitating their tone. Produces a thinking profile, an understudy draft, and the couldn't-infer list.

Harden a vibe-coded app before strangers use it — the audit for prototypes built fast with AI: exposed secrets, missing auth checks, unvalidated input, data with no deletion path, and the five embarrassing holes every weekend build has. Use when someone says 'Claude built my app, is it safe to launch', 'harden my prototype', 'vibe check my project', or before putting real users on a hackathon build. Produces a ranked findings list with fixes, a launch-blocker line, and a 'what I'd break first' attacker's tour. Defensive review of YOUR OWN app.

Simulate a consular visa interview — the 90-second assessment, the questions behind the questions, and a debrief on which answers helped and hurt. Use when asked prep me for my visa interview, simulate the consular interview, why might my visa be denied, or practice my student visa questions. Produces the interview transcript with the officer's internal read after each answer, the decision with its real basis, and a debrief on answer-shapes — preparation, never coaching to misrepresent.

Turn an anxious spiral into a concrete list — separate the specific worries from the vague dread, sort what you can act on from what you can't, and get one action. Use when asked help me with my anxiety spiral, I can't stop worrying about, my mind won't stop racing, or break down what I'm anxious about. Produces the swirling worry pulled apart into named, specific concerns, each sorted into can-act-on vs can't-control vs not-actually-likely, a single action for the actionable ones, and a way to set down the rest — because a spiral is fog, and a list is manageable. Not therapy.

Get through the first year after losing someone — the birthdays, holidays, and ordinary triggers that ambush you — with a gentle plan for the hard days instead of being blindsided. Use when asked how do I get through the holidays after a death, the first birthday without them, grief is hitting me in waves, or coping with the first year of loss. Produces a map of the anticipated hard days, keep/change/skip options for each, grounding for the ambush waves, ways to include their memory, and gentle markers for when grief needs more support. Not therapy; points to grief counseling and support groups.

Build a defensible thesis or dissertation outline — argument-first structure, chapter by chapter, with the through-line visible. Use when asked to outline my thesis, structure my dissertation, plan my capstone, or organize my research into chapters. Produces a full outline: the one-sentence thesis, chapter map with each chapter's job and claim, evidence allocation, and the risk register of weak links an examiner would probe.

Get unstuck on a problem by deliberately re-framing it through a different lens — a child's, an outsider's, another industry's, the reverse, the extreme. Use when asked I'm stuck on this, look at this differently, reframe this problem, or how else could I think about this. Produces the same problem re-cast through several deliberately different frames (each of which changes what the problem even is), what each reframe reveals, and the most useful new angle to pursue — because being stuck is usually a framing problem, not an effort problem.

Land a sprawling chat thread on an actual decision — the summarize-and-fork move (positions restated, the question isolated), the decider-and-deadline injection, and the recorded close that ends the forty-message orbit. Use when asked this thread is going in circles, get a decision out of this discussion, summarize where we landed, or why do our threads never conclude. Produces the thread summary with positions attributed, the isolated decision question, the closure message, and the decision record.

Turn a REAL Slack thread (or channel) into a logged decision — read it, extract what was decided, who owns what, and record it in Notion — not a template for writing decisions. Use when asked to capture the decision from this thread, log what we agreed, turn this Slack discussion into a decision record, or close this out in Cowork. Reads the thread via the Slack connector, distils the decision / owners / next steps / open questions, and produces a decision-record artifact written to a Notion database (with the source thread linked).

Threat-model a system or feature to find where it could be attacked, before you build it. Use when asked to threat-model, do a security design review, identify attack surface, or apply STRIDE to a design. Produces a structured threat model: assets, trust boundaries and data flows, threats enumerated by category (STRIDE), and prioritized mitigations. Defensive security for systems you own or are authorized to assess.

Generate article or newsletter thumbnail candidates using the Gemini API from inside Claude Code. Claude reads article copy, proposes composition concepts, writes image generation prompts incorporating brand specs, calls Gemini to generate the images, evaluates the results via computer vision, and returns ranked candidates with rationale. Use when asked to create thumbnails, generate cover images, or produce visual candidates for an article or newsletter.

Decode a timeshare contract before signing — the lifetime cost math, the perpetuity and fee-escalation clauses, the rescission window, and the honest resale reality. Use when asked to review this timeshare, decode my timeshare contract, can I get out of a timeshare, or is this vacation ownership worth it. Produces the true-cost projection, the clause decode with the perpetuity traps flagged, the rescission-window computation, and — for existing owners — the legitimate exit paths vs the exit-scam checklist.

Measure before optimizing — estimate token counts locally with stated heuristics, price them at your model's rates, and quantify before/after savings, because token optimization without measurement is vibes. Use when asked how many tokens is this, what does this context cost per call, is this optimization worth it, or compare these two versions' cost. Produces the estimate with both heuristics shown, the cost math at your prices across your call volume, and the before/after comparison that decides whether an optimization earned its complexity.

Cut LLM output tokens 40–70% by stripping grammatical scaffolding while preserving every fact — telegraphic output modes, when they pay (pipelines, long sessions) and when they don't (single shots, human-facing prose), with the mode lines to switch on demand. Use when asked make the model respond tersely, cut output token costs, caveman mode, or compress agent-to-agent messages. Produces the diet-mode instruction block ready to paste, the three compression levels with examples, the economics of when each pays, and the never-diet list.

Rewrite a message to the tone you actually want — less harsh, more confident, warmer, firmer, or shorter — without losing your point. Use when asked to make this sound less rude, soften this email, make me sound more confident, make this nicer/firmer, or fix the tone of a message. Produces two or three rewrites at the target tone, a note on exactly what was changed and why, and a flag if the original's tone was fine as-is.

Review what an agent is actually allowed to do before you turn it loose — the tool-by-tool audit (each capability's blast radius), the least-privilege pass that removes what the task doesn't need, the dangerous-combination check, and the allow/ask/deny tiering. Use when asked review my agent's permissions, what can this agent actually do, lock down my agent's tools, or is this MCP/tool set safe to grant. Produces the permission inventory with blast radius, the least-privilege cuts, the dangerous-combo flags, and the allow/ask/deny assignments.

Evaluate a new tool before it joins the stack — the problem-first framing (tools answer needs, not demos), the trial designed with success criteria upfront, the stack-fit check (integration, overlap, the tool-sprawl tax), and the security/data review sized to the stakes. Use when asked should we buy this tool, evaluate this software for the team, we have three tools that do this already, or run a proper trial before committing. Produces the need statement, the trial design with pre-set criteria, the stack-fit audit, and the adopt/decline verdict with its reasoning.

Assess an injection-mold or production tooling decision before cutting steel — soft vs hard tooling tradeoff, tool life vs forecast, cavitation math, T1 sample timeline, cost of design changes after tooling, and kill criteria. Use when asked whether to kick off tooling, choose soft vs hard tools, size cavities, review a tooling quote, or assess the risk of tooling before the design is frozen. Produces a tooling risk assessment with capacity math, a decision recommendation, and explicit kill criteria.

Which assumption actually moves the answer — one-at-a-time sensitivity, ranked into a tornado. Use when a model's output is being argued about (LTV, ROI, forecast) and the room is debating drivers that don't matter, or before spending diligence effort: swing every driver low→high and see which one owns the outcome. Produces the ranked tornado table, share-of-swing per driver, and a real .xlsx — via the bundled zero-dependency script with a safely restricted formula evaluator.

Decode a terms of service or privacy policy into what you're actually agreeing to, ranked by real-world impact. Use when someone asks 'what am I agreeing to', 'decode this privacy policy', 'is this ToS bad', or 'should I click accept'. Produces a ranked findings table with a 'should I care?' verdict per finding, covering data resale, arbitration and class-action waivers, unilateral changes, content licenses, and what deletion really means.

Build a trade quote that wins the job and protects the margin — materials and labor itemized, assumptions and exclusions stated, variations priced by rule, and the professional one-page layout customers trust. Use when a tradesperson says 'help me quote this job', 'I keep losing money on jobs', 'customer wants a price for X', or 'how do I quote a day rate vs fixed'. Produces a ready-to-send quote plus the internal costing sheet behind it.

Transcreate marketing/brand copy for another language and culture — recreate the impact, not the words. Use when asked to adapt a tagline, ad, slogan, campaign, or brand message for a new market, or when a translation is 'correct but flat'. Produces a transcreated version that lands emotionally in-culture, with the strategic rationale, 2-3 options, and notes on what was changed and why.

Turn a business trip into a one-page brief that runs itself — the itinerary with buffers and failure modes, the meeting logistics pre-solved (addresses, contacts, backup numbers), the packing-and-prep list by trip type, and the expense capture set up before departure. Use when asked prep my business trip, build the travel brief, I always forget something when traveling, or organize this three-city week. Produces the one-page brief: timeline with buffers, the per-meeting logistics, the contingency card, and the expense setup.

Build a veterinary treatment plan with tiered options and a cost estimate to discuss with a pet owner. Use when asked to prepare a treatment plan, create an estimate for an owner, present diagnostic/treatment options, or have the cost conversation in a vet practice. Produces a clear plan (recommended vs. acceptable-alternative vs. minimum), line-item cost ranges, the medical rationale in plain language, and how to frame the money conversation with empathy so the owner can make an informed, unpressured decision.

Turn a destination, some dates, and your vibe into a realistic day-by-day trip itinerary — paced for real humans, with a packing list and a rough budget. Use when asked to plan a trip, build a travel itinerary, what should I do in [place], or help me plan my holiday. Produces a day-by-day plan grouped by area (so you're not criss-crossing the city), must-book-ahead flags, a packing list tuned to the trip, a rough budget range, and honest notes on pace and gaps to fill with local info.

Prep tonight's TTRPG session in 30 minutes — three scenes with stakes, NPC voice cards, a flexible encounter, treasure/clues, and the 'players did something insane' toolkit — plus session-zero safety tools for new tables. Use when a game master says 'prep my D&D session', 'my players derailed everything', 'I need an NPC on the fly', or 'help me start a campaign'. Produces a one-page session plan built to survive contact with the players.

Bridge the gap between your home culture and your adopted one — explain your immigrant parents to your partner (and vice versa), navigate the code-switch that exhausts you, and handle the specific collisions (holidays, money, marriage expectations, 'when are you coming home') without betraying either side. Use when someone says 'my partner doesn't understand my family', 'I'm caught between two cultures', 'help me explain this to my parents', or is a first/second-gen immigrant or third-culture kid. Produces a translation of the specific collision, scripts for both directions, and a boundary that honors both worlds.

Get unstuck on purpose — the stuck-type diagnosis (don't-know-how, can't-decide, waiting, avoiding, too-big), the matched unblock move for each, and the timebox that stops noble struggling before it eats the day. Use when asked I'm stuck on this and don't know why, I keep avoiding this task, how long should I struggle before asking, or unblock my stalled project. Produces the stuck diagnosis, the matched move, the ask-for-help script that preserves standing, and the stuck-log pattern read.

Track down money that's yours but forgotten — dormant accounts, old deposits, uncashed checks, lost pensions, insurance payouts, and unclaimed-property funds. Use when asked to find unclaimed money, is there money owed to me, find a lost account/pension, or search unclaimed property. Produces a checklist of where forgotten money hides, how to search the official (free) registries for each type, what proof you'll need to claim it, and a strong warning to only use official free searches and never pay a 'finder' up front. Not financial advice.

Write the underwriting file narrative for a risk: the risk story, exposure quantification, loss-history read, mitigating and aggravating factors, terms and subjectivities rationale, appetite fit, and a refer-or-bind recommendation. Use when asked to write up an underwriting file, document why we're writing a risk, prepare a referral to a senior underwriter, or justify terms and exclusions on a submission. Produces a complete underwriting narrative ready for the file or referral.

Model the unit economics of a business — CAC, LTV, payback, contribution margin — from real inputs. Use when asked to calculate unit economics, work out LTV:CAC, find the payback period, or check whether a business model is viable per customer. Produces a computed unit-economics summary (LTV, CAC, ratio, payback, contribution margin) with a verdict and the levers that move it most.

Decode a used-car listing before you drive an hour to see it — what the seller's phrasing is hiding, the history-check items that matter, a test-drive and inspection checklist ordered by cost-of-miss, the questions that make evasive sellers visible, and the walk-away signs ranked 🔴🟡🟢. Use when someone says 'is this car listing legit', 'what should I check on a used car', 'decode this ad', or is about to buy their first car. Produces a listing decode, the viewing checklist, and the negotiation frame. Not a mechanic — and it says which checks need one.

Synthesises user interview transcripts into structured research findings. Use when asked to analyse interview notes, synthesise qualitative research, identify themes from interviews, or turn raw interview data into actionable product insights. Produces a themed synthesis with supporting quotes per theme, 'so what' implications, and recommended next steps. For mixed sources beyond interviews (surveys, tickets, feedback) use user-research-synthesis instead.

Map a user's journey through a product or experience, phase by phase, with their actions and how they feel. Use when asked to map a user/customer journey, show the experience end-to-end, or find friction and drop-off points. Produces a ready-to-render Mermaid journey diagram (renders live, exportable as PNG/SVG) plus the friction points and opportunities.

Analyze and synthesize user research findings into structured, actionable insights. Use when given user research data, interview transcripts, survey results, or user feedback that needs to be analyzed and summarised. Produces a themed synthesis with prevalence data, supporting quotes, pain points analysis, feature request prioritisation, and recommended next steps. For interview transcripts specifically use user-interview-synthesis instead.

Write well-structured user stories with acceptance criteria and edge cases. Use when asked to write user stories, create tickets from a feature brief, convert a PRD into stories, or write acceptance criteria. Produces ready-to-estimate stories in the standard format with clear acceptance criteria, edge cases, and definition of done.

Decide whether to switch energy, broadband, or mobile providers — compare the real total cost, dodge the traps, and time it right. Use when asked should I switch energy/broadband/mobile providers, compare utility deals, is this a good energy tariff, or help me switch and save. Produces an apples-to-apples comparison (total annual cost, not headline rate), the traps to check (intro-then-jump pricing, exit fees, contract length), a switch/stay recommendation, the switching steps, and reminders to verify current prices on a comparison source.

Create a structured UX research plan for any product question or feature. Use when asked to write a research plan, design a user study, create a discussion guide, write screener questions, or plan usability testing. Produces a full research plan with objectives, methodology, screener, discussion guide, and synthesis framework.

Craft a sharp value proposition that says who it's for, the outcome, and why you over the alternative. Use when asked to write a value prop, a value proposition, a one-liner, or to clarify 'what do we even say we do?'. Produces a primary value-prop statement, a plain-language one-liner, 3 benefit-led variations, and the before→after transformation it promises — ready to headline a landing page.

Simulate the VC partner meeting that discusses your pitch after you leave the room — four partner archetypes debate, then write the internal verdict memo. Use when asked how will VCs discuss my pitch, simulate the partner meeting, stress-test my fundraise, or what happens after the pitch. Produces the meeting transcript, the internal fund/pass/track memo, and a debrief listing which objections are fixable before the real meeting.

Build a maintenance schedule for your car so it stays reliable and holds value — the service intervals, the DIY-vs-shop split, and the checks that prevent breakdowns and rip-offs. Use when asked for a car maintenance schedule, what maintenance does my car need, how to keep my car running, or am I being upsold at the mechanic. Produces an interval-based schedule keyed to your vehicle and driving, the essential do-not-skip items, DIY vs professional, seasonal checks, and how to spot unnecessary upsells — flagging that your owner's manual is the authority.

End a vendor, freelancer, or service relationship cleanly — the notice email that cites the contract, the transition asks that protect your data and continuity, and the door-open close that costs nothing. Use when asked write a cancellation email to our vendor, we're not renewing how do I tell them, end this contractor relationship professionally, or switch providers without drama. Produces the notice-period check, the breakup email with transition terms, the retention-offer response plan, and the offboarding checklist.

Compare vendors on a matrix that decides instead of decorates — the criteria weighted before the demos (so the shiny demo can't rewrite them), the evidence-based scoring with the marketing-vs-verified flags, the total-cost row that includes switching, and the reference-check questions that get honest answers. Use when asked compare these vendors/tools, build the selection matrix, the demo wowed us now what, or make this procurement decision defensible. Produces the weighted matrix, the scoring evidence rules, the TCO row, and the reference-call script.

Review a vendor/SaaS contract against a practical checklist before you sign. Use when asked to review a vendor contract, check a SaaS/MSA/subscription agreement, flag risky terms, or prepare negotiation points before signing. Produces a structured review — key terms extracted, a risk-flagged checklist (commercial, legal, security, exit), questions to ask, and prioritised negotiation points. Not legal advice.

Create a structured vendor evaluation framework for any procurement decision. Use when asked to evaluate vendors, compare suppliers, run an RFP scoring process, or assess a software or service provider. Produces a weighted scorecard, evaluation criteria, and recommendation framework.

Run a third-party / vendor security review and assign a risk tier with required controls. Use when asked to assess a vendor's security, run a third-party risk assessment, complete a security questionnaire about a vendor, or decide what due diligence a new tool needs. Produces a vendor risk assessment — a data/access-driven risk tier, the questionnaire focus, required evidence (SOC 2, pen test, DPA), residual risk, and an approve/conditional/reject recommendation.

Check whether a specific venue — a restaurant, office, event space, Airbnb, clinic — will actually work for your access needs, before you commit, with the exact questions to ask and the red flags in the answers. Use when someone says 'will this place work for my wheelchair', 'check if this venue is accessible', 'questions to ask a venue about access', or 'is this restaurant/office actually accessible'. Produces a tailored question list, how to read the answers, and a go/adapt/avoid verdict. For personal access decisions; not a formal accessibility audit.

Verify work actually meets its brief BEFORE declaring it done — a structured self-review pass that catches the gaps, unmet requirements, and untested claims that 'looks finished' hides. Use before handing over any deliverable (document, code, analysis, plan), when past work kept coming back with 'you missed…', or as the standing final step of any multi-step task. Produces the verified deliverable plus a short verification record: what was checked, what was found and fixed, what remains open.

Untangle a document that exists in six copies across email, drives, and desktops — establish the canonical version defensibly, merge the divergent edits, and install the single-source rule that prevents the rematch. Use when asked which version is the real one, merge these document copies, we've been editing different files, or stop the version chaos on this doc. Produces the version census with the canonical verdict, the divergence merge plan, the announce-and-redirect step, and the single-source going-forward rules.

Decode a veterinary treatment estimate — what each line is for, which items are core vs precautionary, and how to have the options conversation nobody offers you. Use when someone asks 'is this vet estimate reasonable', 'decode my vet's treatment plan', 'do we need all these tests', or 'I can't afford this vet bill what are my options'. Produces a line-by-line decode with core/precautionary/comfort triage, the questions that surface the tiered options vets keep in reserve, and the payment and assistance paths.

Build a framework for creating shareable, high-reach social media content. Use when asked to plan viral content, develop a shareable content strategy, create a hook writing system, or build a repeatable process for content that gets shared. Produces a platform-specific viral content framework with hook formulas, content structures, shareability triggers, and a content testing system.

Design a voice AI agent for phone or in-app conversations — call flows, interruption handling, escalation to humans, and the metrics that catch a bad voice experience. Use when asked to design a voice agent, automate a phone line, spec an IVR replacement, or review why callers hate an existing voice bot. Produces a voice agent spec: persona and disclosure policy, conversation architecture, barge-in and repair behaviour, human-handoff rules, and a launch scorecard.

Stand up a Voice of Customer (VoC) program that turns feedback into action. Use when asked to build a VoC program, design a customer feedback loop, consolidate feedback sources, or set up a closed-loop feedback process. Produces a VoC program design — objectives, feedback sources and channels, a taxonomy, collection and analysis cadence, closed-loop routing, ownership, and success metrics.

Be a club or association treasurer without being an accountant — the two-column cashbook that's genuinely enough, monthly reconciliation in 20 minutes, the treasurer's report members actually understand, float and subs handling, and the controls that protect YOU from suspicion. Use when a volunteer says 'I just became treasurer', 'how do I do the accounts for our club', 'what goes in the treasurer's report', or inherits a shoebox of receipts. Produces the cashbook setup, a monthly routine, the report template, and the two-signature control list.

Work out how to actually vote in a specific election — am I registered, what's the deadline, how do I vote (in person / mail / early), what ID do I need, and what's on my ballot — with everything routed to the official source to verify. Use when someone says 'how do I vote', 'am I registered', 'what's the deadline to register', 'help me vote by mail', or 'what's on my ballot'. Produces a personal voting plan with dates, steps, and the official links to confirm each one. Non-partisan; procedure only, never who to vote for.

Triage a vulnerability or scanner finding — assess real severity, exploitability, and how urgently to fix. Use when asked to triage a CVE, prioritize scanner/pentest findings, assess a vuln's risk, or decide what to patch first. Produces a triage verdict: CVSS-informed severity adjusted for your context, exploitability, real risk, a fix/mitigation, and an SLA — so you fix what matters, not just what's red.

Respond fast when your wages are being garnished or about to be — the deadlines, the exemptions that can reduce or stop it, and the steps that protect your paycheck. Use when asked they're garnishing my wages, how do I stop wage garnishment, I got a garnishment notice, or can they take my whole paycheck. Produces the urgent-deadline map, the exemptions that may reduce or stop it (income caps, protected funds like benefits, head-of-household), how to file a claim of exemption, options to resolve the underlying debt, and where to get legal aid immediately. Not legal advice; centers fast legal-aid help.

Get a broken product repaired, replaced, or refunded under warranty — with the claim message written, the proof to attach, and the consumer-law backstop for when 'out of warranty' isn't the whole story. Use when asked to make a warranty claim, my [product] broke and it's still under warranty, the manufacturer won't honor the warranty, or how do I get this fixed for free. Produces a ready-to-send claim message, the exact evidence to include, the repair-vs-replace-vs-refund position, and an escalation ladder for when the first answer is no.

Get current weather and forecasts with zero API keys — wttr.in one-liners for humans, Open-Meteo JSON for data, with the exact curl commands and format codes. Use when asked what's the weather, will it rain today, forecast for a city, or get me weather data for a location. Produces the live conditions or forecast pulled via curl, interpreted plainly, with the source timestamp and the command used shown so the user can rerun it.

Build a wedding budget that survives to the wedding — allocation by real shares, the per-guest lever made explicit, the routinely-forgotten line items priced in from day one, and a contingency that isn't decorative. Use when asked make a wedding budget, how do people split X across a wedding, we have N dollars and M guests, or why is our wedding over budget. Produces the allocation table from the script, the guest-count math, the forgotten-items audit, and the track-against-actuals discipline.

Plan the wedding day as the operation it is — the minute-level run sheet, the vendor call sheet, the who-handles-problems roster, and the buffer discipline that keeps the couple out of logistics on the day. Use when asked make our wedding day timeline, day-of run sheet, who tells the vendors where to go, or how do we not deal with problems at our own wedding. Produces the run sheet with buffers, the vendor call sheet, the delegation roster with a named day-of decision-maker, and the contingency cards for the classic failures.

A best-man/maid-of-honour/parent wedding toast that actually lands — funny without roasting, moving without syrup, short enough that nobody checks their phone. Use when someone has to give a wedding speech and has either nothing or a dangerous first draft. Produces a 2-4 minute toast built on one good story, plus delivery notes and the three jokes to cut.

Decode a wedding vendor contract — venue, photographer, caterer, band — before signing: deposits and their refundability, cancellation and postponement terms, the substitute-performer and force-majeure clauses, and overtime math. Use when someone asks review this venue contract, is this photographer contract normal, what if we have to postpone, or decode this caterer agreement. Produces a clause decode with 🔴🟡🟢 severity, the cancellation-cost timeline, the questions to ask this vendor, and what's actually negotiable.

Write personal wedding vows that sound like you — specific, heartfelt, and the right length — instead of generic or cheesy. Use when asked to write my wedding vows, help me with vows, what should I say at my wedding, or vows that aren't cliché. Produces vows built from your real story and specifics, a structure (who you are together, a promise or few, a look forward), the right tone and length for your ceremony, coordination notes with your partner, and a version you can actually deliver out loud without crying through the whole thing.

Install the weekly review that keeps work from managing you — the 30-minute Friday ritual: close the week's loops, sweep the capture points, choose next week's big three before the calendar chooses for you, and the two questions that compound. Use when asked set up a weekly review, my weeks just happen to me, GTD-style review but lighter, or I keep dropping threads between weeks. Produces the ritual's fixed agenda, the sweep checklist, the big-three selection, and the survival rules for busy weeks.

A short weekly ritual that clears the mental backlog, picks the one thing that matters, and keeps you honest about your dependence on autopilot. Use when asked run my weekly reset, help me plan my week, my weekly check-in, or get me unstuck for the week. Produces a quick brain-dump and triage of what's on you, the single most important focus for the week, the stuck things and their tiny first steps, and a self-check on where you're coasting or over-relying — a recurring executive-function reset rather than a one-off fix.

Build a preventive-care (wellness) plan for a pet by species, breed, and life stage. Use when asked to create a wellness plan, plan preventive care, set up a vaccination/parasite schedule, or advise an owner on routine care for a puppy/kitten/adult/senior pet. Produces a life-stage-appropriate schedule — vaccinations, parasite prevention, dental, nutrition, screening diagnostics, and behavioral guidance — with the rationale, so an owner sees preventive care as a plan, not a series of surprise visits.

Surface the blind spot — the missing stakeholder, the ignored option, the risk outside your frame, the thing you're too close to notice. Use when asked what am I missing, what's my blind spot, what haven't I considered, or is there something I'm not seeing here. Produces the considerations outside your current frame: who you haven't accounted for, what you've ruled out without noticing, the second-order effects, and the thing your closeness to the situation hides — the opposite of confirming what you already think.

Get the five questions that matter before you sign, buy, or agree to anything — the front door to the decoder family, routed by situation. Use when asked what should I ask before signing this, I'm about to buy X what do I check, what questions for the landlord/dealer/contractor/HR, or what am I forgetting. Produces the five highest-leverage questions for the specific situation with why each matters and what a bad answer sounds like, plus the pointer to the full decoder when one exists.

Decide what to cook tonight from what you already have and how much time/energy you've got — no shopping trip, no recipe rabbit hole. Use when asked what should I make for dinner, what can I cook with what's in my fridge, quick dinner ideas, or I don't know what to eat. Produces 3 doable options ranked by effort with a quick method for each, honest substitutions, and a 'need one thing' flag if a near-miss is worth a corner-shop run — respecting diets and dislikes.

The first two weeks after a death, organized — what genuinely needs doing now, what only feels urgent, who to notify in what order, and the documents everything else will require. Use when asked someone just died what do I do, checklist after a death, help me handle my parent's affairs, or what needs to happen this week. Produces the triaged timeline (today / this week / can wait), the notification order, the death-certificate math, and the scripts for the hardest calls — written for someone who cannot think straight, because that's who's reading.

Turn a chaotic pile of everything-in-your-head into one clear first action — the antidote to the paralysis of too much at once. Use when asked I don't know where to start, I'm overwhelmed with everything I have to do, help me get going, or just tell me what to do first. Produces your brain-dump organized into a simple ordered list, the single next physical action to take right now, and the rest deliberately hidden so it can't overwhelm — outsourcing the executive-function job of structuring, so you can just execute.

Route a fuzzy request to the right skill in this library. Use when the user is unsure which skill fits, asks 'which skill should I use for X', describes a task without naming a skill, or when a request could plausibly match several skills. Produces a best-fit recommendation with the inputs to gather, a runner-up with the tie-breaker, and a workflow recipe when the job spans multiple skills.

Turn photos of a whiteboard, sticky-note wall, or napkin sketch into a structured spec the team can execute. Use when given whiteboard photos after a workshop, sketch images of a flow or architecture, or asked to 'write up what we drew'. Produces a structured write-up — decisions, flows, open questions, owners — that preserves everything on the board and flags what was ambiguous. Requires image input.

Fetch Wikipedia's current summary of any topic with zero API keys — the REST summary endpoint via curl, for answers that need today's article rather than training-data memory. Use when asked what does Wikipedia say about X, get me the current summary of a topic, check a fact against Wikipedia, or has this article changed. Produces the live extract with the article link, disambiguation handling, and a clean separation between what Wikipedia says and what the model adds.

Turn an at-risk or churned account into a save play — root-cause hypothesis, the offer ladder, the outreach sequence, and the honest call on when to let go. Use when asked to save a churning customer, build a win-back plan, re-engage a lost account, or stop a renewal from slipping. Produces the churn diagnosis, a ranked set of save levers, a timed outreach sequence, and the walk-away line so you don't over-invest in an account that's gone.

Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.

Make a smart plan for a lump sum — a bonus, inheritance, tax refund, settlement, or sale — so it builds your future instead of evaporating into lifestyle. Use when asked what should I do with a windfall, I came into some money, how to use a bonus/inheritance/tax refund, or don't want to waste this money. Produces a cool-off-first plan, a tax/obligations check, an allocation across foundation-building, goals, and a guilt-free fun slice, and cautions against the classic windfall traps and the vultures that appear. Educational — not financial advice.

Pick a wine that flatters tonight's meal — at your budget, from what's actually available — without the sommelier mystique. Use when asked what wine goes with [dish], help me pick a wine, what should I drink with dinner, or recommend a bottle for. Produces a couple of specific bottle styles (not just 'a red'), why each works with the dish, a budget-tier pick, an easy-to-find fallback, and a non-alcoholic option — with a plain reason you can remember next time.

Write a clear, factual witness statement or account of an incident — for an insurance claim, small claims, a workplace matter, or the police — that sticks to what you saw and holds up. Use when asked to write a witness statement, an account of what happened, a statement for [insurance/court/HR], or document an incident I witnessed. Produces a structured, chronological statement of facts (who, what, when, where), a clean separation of observation from opinion, the details that matter, and formatting/sign-off basics — flagging that for legal proceedings you should follow the required format. Not legal advice.

Produce properly-formatted tracked changes for a Word document. Use when asked to redline a document, suggest edits to a contract or document, create tracked changes for review, or mark up a document with proposed revisions. Produces a complete redline with insertions, deletions, and margin comments that can be applied to the source document. Best used with Claude Opus 4.7 or newer for reliable tracked changes handling.

Build a real, formatted Word (.docx) document — headings, styles, tables, TOC-ready. Use when asked to produce a Word doc, a .docx, a formatted report/contract/proposal/letter as an actual file (not markdown). Produces an actual .docx via a generated python-docx script with proper heading styles, body text, tables, and page structure. Requires a code-execution environment (Claude Code, the API code tool, or Claude.ai).

Write a team's working agreements — the small set of explicit norms (communication, meetings, decisions, conflict) that replace the assumptions people were silently violating, built from the team's actual frictions and revisited on a cadence. Use when asked create team working agreements, set norms for our new team, we keep clashing over how we work, or onboard people into how this team operates. Produces the friction-derived agreement set, the specific-behavior phrasing, the disagreement protocol, and the review cadence.

Design working sessions that produce artifacts, not vibes — the outcome-backwards agenda, the activity formats that beat open discussion (silent writing, dot voting, structured rounds), the energy arc, and the output-capture that survives the room. Use when asked design a workshop for X, plan our planning session, facilitate a half-day working session, or our workshops are fun but nothing comes out. Produces the workshop design: the artifact goal, the activity sequence with timings, the facilitation notes, and the capture plan.

Design and facilitate any workshop, working session, or collaborative meeting. Use when asked to plan a workshop, design a facilitated session, run a ideation session, or create a workshop agenda. Produces a complete facilitation guide with session design, activity instructions, timing, and materials.

Get the current time anywhere and convert between time zones with zero API keys — timeapi.io via curl (worldtimeapi fallback), plus the DST-safe meeting-window math. Use when asked what time is it in a city, convert 3pm my time to Tokyo, find a meeting slot across time zones, or what's the UTC offset somewhere. Produces the local time(s), the conversion with DST handled by the API not by memory, and the overlap window for scheduling questions.

Author a high-quality Agent Skill (SKILL.md) that an AI reliably triggers and executes well — strong frontmatter, a sharp description with trigger phrases, a clear output contract, quality checks, and anti-patterns. Use when asked to write a skill, create a SKILL.md, improve a skill, review a skill for quality, or contribute to a skills library. Produces a complete, SkillCheck-passing SKILL.md plus a short rationale for the key choices.

Write an executable work plan BEFORE starting a complex task — decomposed steps with verification points, risks pre-named, and explicit stop conditions — so execution becomes checking boxes instead of improvising. Use when a task will take many steps, when asked to plan before doing, when previous attempts sprawled or stalled, or before delegating work to subagents. Produces a plan document another agent (or future you) could execute without re-deriving the thinking. Pairs with executing-plans.

Run an honest personal year-in-review and set next year's direction — wins, misses, an energy audit, and one theme, not a resolution list that dies in February. Use when asked for a personal year in review, a yearly reflection, to reflect on the past year, or plan next year. Produces the structured retrospective (what worked, what didn't, what you learned), an energy audit of what gave vs. drained you, the honest misses, and a single theme with a few concrete commitments. Personal, not corporate.

Write a long-form video script for YouTube — an explainer, tutorial, video essay, review, or talking-head — built on the packaging→cold-open→value-stack→retention structure that holds watch-time past the drop-off cliffs. Use when asked to script a YouTube video, write a long-form or explainer/tutorial video script, outline a video essay, or turn a blog post/talk into a video. Produces title + thumbnail concepts, a timed cold open, a segmented body with retention devices and B-roll cues, integrated CTAs, an outro/end-screen, and a description with chapter timestamps. Distinct from [[short-form-script]] (15–60s vertical).

Write engaging, high-retention YouTube video scripts with visual and audio cues. Use when asked to write a YouTube script, design a video outline, draft a video hook, or structure a video narrative. Produces a polished script with multiple hook options, step-by-step video body, and clear visual/audio directions.

Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.

Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.

Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.

Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.

Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.

Plan a trip that actually works with a disability or access need — confirm real accessibility (not just 'accessible' labels), book the assistance in advance, plan for equipment and medication, and build in the contingencies for when access breaks down. Use when someone says 'plan an accessible trip', 'travelling with a wheelchair/disability', 'book assistance for my flight', or 'will this hotel actually work for me'. Produces an access-verified itinerary, an assistance-booking checklist, an equipment/medication plan, and contingency scripts. Verify specifics with providers.

Request a reasonable accommodation at work or in education — frame it around the barrier and the adjustment (not your diagnosis), cite the right process, and navigate the back-and-forth constructively. Use when someone says 'I need a workplace accommodation', 'request reasonable adjustments', 'ADA/Equality Act accommodation', or 'how do I ask for accommodations for my disability/condition'. Produces the request letter, a barriers-and-adjustments map, disclosure guidance, and a plan for the interactive process. Not legal advice — routes to the formal process and to advocacy where needed.

Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.

Get back into a locked or hacked account the right way — the official recovery routes, what proof you'll need, and how to re-secure it so it doesn't happen again. Use when asked I'm locked out of my account, my account got hacked, help me recover my [email/social/bank] account, or I lost access to 2FA. Produces the official recovery path for the account type, the identity proof to prepare, a re-securing checklist for after you're back in, and warnings about fake 'recovery' services and support scams.

Simulate the acquirer's diligence team hunting for reasons to cut your price — their internal red-flags memo with a price-chip estimate per finding. Use when asked to red-team my company before a sale, how will an acquirer attack our valuation, pre-diligence audit, or what will DD find. Produces the acquirer's internal memo (revenue quality, key-person, tech debt, concentration, legal) and a debrief on which flags are fixable before a process.

Turn a skill's recommendations into real, executed actions — open the tickets, file the issues, post the updates — safely: dry-run preview, risk-classified, approval-gated, then recorded back to the brain. Use when asked to act on a plan, file tickets from a checklist, create issues from a PRD, execute the recommended next steps, or wire a skill's output into GitHub/Linear/Slack. Produces a dry-run actions plan with per-action risk, executes only after approval via the connected action MCP, and logs what was done. Nothing acts silently.

Write platform-native paid ad copy with multiple angles to test. Use when asked to write ad copy, Google/Facebook/LinkedIn/Instagram ads, PPC headlines, or paid social creative copy. Produces ready-to-ship variants per platform (headlines, primary text, descriptions, CTAs) across distinct angles, sized to each platform's limits, with a note on what each variant tests.

Optimize an article for Answer Engine Optimization (AEO) so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines. Produces an AEO-optimised rewrite with question headings, 50–80 word answer capsules, a paragraph-length audit, and flagged trust signals.

Work through the first hours and days after a disaster — a fire, flood, storm, or evacuation — in the right order: safety and people first, then documenting for insurance and aid, then the immediate recovery steps, without missing the things that cost money or health later. Use when someone says 'my house flooded/burned', 'what do I do after the disaster', 'we just evacuated, now what', or 'the storm damaged everything'. Produces a triaged action plan (safety → document → claim → recover), the do-not-miss list, and where to get help. Not legal advice; routes to emergency services and official aid.

Enforce the simplest meeting rule that works — no agenda, no meeting — with the three-line agenda format (purpose, decisions sought, pre-reads), the 24-hour rule, and the graceful cancel scripts. Use when asked write an agenda for this meeting, should this meeting happen, our meetings have no agendas, or cancel this meeting politely. Produces the three-line agenda, the happen-or-cancel verdict, the cancel/convert scripts, and the team norm rollout.

Review an LLM agent design and find where it will be unreliable, expensive, or unsafe. Use when asked to review an agent architecture, critique a multi-step/tool-using agent, debug an agent that loops or goes off-task, or harden an agent before launch. Produces a structured review — task fit, control flow, tools, memory/context, failure handling, cost, and safety — with prioritised findings and fixes.

Redesign seat-based pricing for the agent era — when one human runs ten agents, per-seat models collapse. Use when agents are eroding seat counts, when asked to migrate to usage- or outcome-based pricing, to price an agent/API tier, or to defend revenue as customers automate their own usage. Produces a pricing migration plan: the new value metric, fences, agent-tier design, cannibalisation math, and a phased migration for existing customers. For general pricing and packaging strategy use pricing-strategy.

Hire an AI agent the way you'd hire an employee — a role spec with success criteria, a structured work-sample interview run on your real tasks, reference checks (what do actual users report), probation KPIs, and termination criteria written before day one. Use when choosing between AI agents/tools/copilots for a job, formalizing an AI pilot, or 'which agent should we use for X'. Produces the role spec, interview pack with scoring rubric, a decision record, and a probation plan.

Run a blameless postmortem for an incident caused by an AI agent or LLM feature — hallucinated facts shipped to users, runaway tool use, prompt injection, cost blowouts, or wrong actions taken autonomously. Use when asked to write up an AI incident, analyse why an agent did something wrong, or produce corrective actions after an LLM failure. Produces a structured postmortem with trace reconstruction, a root-cause layer analysis, and corrective actions including a permanent regression case. For non-AI production incidents use incident-postmortem.

Specify the tracing, metrics, and alerting for an AI agent or LLM feature in production. Use when asked what to log for an LLM app, design agent tracing or spans, define quality and cost monitors, or answer 'how do we know if the agent is misbehaving?'. Produces an observability spec with a trace schema, metric definitions with owners and alert thresholds, sampling and retention policy, and a privacy note for logged content.

Audit whether AI agents can actually use your product — docs, APIs, onboarding, errors, and discoverability, evaluated from a non-human user's perspective. Use when asked if a product is agent-ready, to audit a site or API for AI usability, to prepare for agentic traffic, or when agents keep failing against your product. Produces a scored readiness report with per-surface findings and a prioritised fix list. For optimising a single article for AI citation use aeo-optimizer; for designing the MCP server itself use mcp-server-spec.

Offboard an AI agent the way you'd offboard an employee — inventory what it knew and touched, export then purge its memory, revoke every credential and access grant, and write the handover for its successor (human or agent). Use when decommissioning an agent or bot, switching agent vendors, ending an AI pilot, or when someone asks 'what did this thing have access to?'. Produces a severance checklist, an access-revocation table, a memory disposition record, and a successor handover.

Specify an autonomous or tool-using AI agent before building it. Use when asked to design an AI agent, define an agent's tools and guardrails, scope what an agent is allowed to do, or write an agent spec/PRD. Produces an agent spec — goal & scope, tools with permissions, the control loop, guardrails & approval gates, memory, escalation/handoff, evaluation, and failure handling.

Assess whether and how someone can safely stay in their own home as they age — the home hazards, the support gaps, and the modifications and services that make it work. Use when asked can my parent stay in their home safely, aging in place assessment, is it safe for them to live alone, or what do we need for them to stay home. Produces a room-by-room safety read (fall hazards, accessibility), an honest look at the daily-living and support gaps, the modifications and services that could close them, warning signs that home may no longer be safe, and how to raise it respectfully — helping a family make a clear-eyed, dignity-preserving decision. Not medical advice.

Prepare the conversations with aging parents that everyone postpones — the driving talk, the money talk, the care-options talk, the moving talk — each with an opener that doesn't ambush, a dignity-first script, rehearsal against realistic resistance, and the fallback when it goes badly. Use when someone says 'I need to talk to my dad about driving', 'my mum won't discuss her finances', 'we need to talk about care', or is dreading a visit for exactly this reason. Produces the conversation plan, a rehearsal, and the small-steps fallback. A preparation tool, not family therapy — and it says so when the situation needs more.

Run a club, PTA, or association AGM that finishes on time and holds up later — the notice and agenda done right, a quorum plan, minutes that capture decisions not conversations, elections without awkwardness, and the follow-up that makes decisions real. Use when a volunteer says 'I have to run the AGM', 'what goes in the agenda', 'nobody comes to our meetings', or 'our elections are a mess'. Produces the notice, agenda, chair's script, minutes template, and quorum rescue plan.

Make an AI agent or automation reliable enough to trust — the tests, checks, and guardrails that catch its failures before they reach anything real. Use when asked how do I test my AI agent, make my automation reliable, my agent works sometimes, or how do I trust an AI workflow in production. Produces a map of where the agent can fail (bad input, hallucination, wrong tool call, edge cases, silent errors), the checks that catch each (validation, evals on real cases, human-in-the-loop gates, monitoring), a right-sized reliability plan scaled to the stakes, and a rollout that earns trust incrementally — so an agent that works in a demo becomes one that works in reality. For builders putting AI agents into real workflows.

Evaluate performance fairly when output is AI-assisted — what still measures the human, what now measures the tooling, and how to run the review conversation. Use when reviewing someone whose work is heavily AI-assisted, when output volume stopped meaning anything, when calibrating a team with uneven AI adoption, or when writing review criteria for the AI era. Produces review guidance: a what-measures-whom analysis, rewritten criteria, calibration rules for mixed-adoption teams, and conversation scripts. For the general review document use performance-review; for redesigning the role itself use role-redesign-for-ai.

Review AI-authored code for its characteristic failure modes — plausible-but-wrong logic, hallucinated APIs, over-engineering, dead scaffolding, and silent security shortcuts. Use when reviewing an AI-generated or heavily AI-assisted PR, when AI-written code keeps shipping subtle bugs, or when setting review standards for a team using coding agents. Produces a focused review with AI-specific findings, verification steps per risk class, and a team checklist for AI-authored changes. For general PR review use code-review-checklist — this skill covers what that one assumes a human wouldn't do.

Audit a content library, docs site, or blog for AI-generated filler that's eroding trust and search performance — and triage what to fix, rewrite, or delete. Use when asked to find slop in a content library, audit AI-written content quality, explain why content engagement or rankings dropped after scaling with AI, or set a quality bar for AI-assisted publishing. Produces an audited inventory with per-piece verdicts, the detection signals used, a triage plan, and a publishing quality gate that prevents recurrence. For a single article's AI-citability use aeo-optimizer; for the strategy itself use content-calendar or seo-content-brief.

Build the context an AI needs to do a task well — the background, constraints, examples, and format it can't guess — so you get a great result on the first try instead of a generic one you have to keep correcting. Use when asked why does AI give me generic answers, how do I give AI better context, my AI results are mediocre, or how do I get it right the first time. Produces the specific context this task needs (who/what/constraints/examples/format), a reusable primer you can paste ahead of the request, the difference between a starved prompt and a well-briefed one, and what to leave out — turning vague back-and-forth into a strong first result.

Decide when and how your product and communications must (or should) label AI-generated content, and write the disclosure policy — surface-by-surface rules, exact label wording, and the review trigger for regulations like the EU AI Act's transparency obligations. Use when asked 'do we have to label AI content', 'write our AI disclosure policy', 'are we covered for the AI Act', or when marketing/support/product start shipping AI-generated output. Produces a disclosure policy with a per-surface matrix and ready-to-use label copy. Not legal advice.

Conduct a structured ethical review of an AI or ML feature, model, or product. Use when preparing to deploy an AI system, assessing algorithmic risk, auditing a model for bias, or producing a responsible AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with a risk tier score, pre-deployment checklist, and prioritised mitigations.

Design an evaluation plan for an LLM or AI feature before shipping it. Use when asked how to evaluate a prompt/model/agent, set up an eval harness, define quality metrics for an AI feature, or build a regression gate. Produces an eval plan — task definition, datasets, metrics & rubrics, baselines, automated + human evals, a pass bar, and a regression gate.

Write a PRD for an AI-powered feature, covering the things normal PRDs miss. Use when asked to spec an AI/LLM feature, write a PRD for a feature that uses a model, or plan an AI capability (assistant, summarizer, generator, classifier). Produces an AI feature PRD — problem & UX of uncertainty, model approach, eval criteria, guardrails, fallback behaviour, the data flywheel, and cost/latency budget.

Check AI output before you trust or use it — where it's likely wrong, what to verify, and how to catch confident-sounding errors. Use when asked can I trust this AI answer, how do I verify what AI told me, fact-check this AI output, or is this AI response reliable. Produces a risk read on the specific output (the claims most likely to be wrong or made up), the parts that need independent verification vs the parts that are low-risk, how to actually verify each, the tells of AI hallucination and overconfidence, and a habit for building verification into your AI use — because AI is confidently wrong often enough that unchecked trust is a real risk.

Structure AI and ML product decisions with the rigour of any product decision. Use when building AI-powered features, evaluating LLM integrations, designing AI products, or assessing AI readiness. Produces a complete AI product canvas covering problem definition, model approach, data requirements, evaluation framework, UX design, responsible AI checklist, and launch monitoring plan.

Audit whether the organisation's AI spend actually paid — measured against baselines, not vendor math or vibes. Use when a CFO asks what the AI tools returned, when renewing AI contracts, when consolidating overlapping AI subscriptions, or to build the measurement plan before the next spend. Produces an ROI audit with per-tool verdicts (keep/consolidate/cut), the honest-measurement method behind each number, and a baseline plan for whatever can't be scored yet. To forecast ROI before an investment use roi-estimator; this skill measures what already happened.

Figure out which AI tool actually fits the task in front of you — chatbot, coding assistant, image model, agent, or none — instead of forcing one tool onto everything. Use when asked which AI tool should I use for, what's the best AI for, do I even need AI for this, or should I use ChatGPT or something else. Produces a match between your task and the right kind of AI tool (with why), the trade-offs that matter for your case, when the answer is a non-AI tool or plain human effort, and how to try it cheaply before committing — so you pick by fit, not by hype or habit.

Write an AI usage policy people can actually follow — approved tools, data rules, disclosure duties, and review obligations, in one page instead of legal fog. Use when asked for a company AI policy, acceptable-use rules for ChatGPT/Claude/Copilot at work, guidance on what data may go into AI tools, or to fix a policy nobody reads. Produces a one-page usable policy plus the decision log behind it. Not a substitute for legal advice; pairs with compliance-checklist for regulatory mapping and ai-ethics-review for system-level assessments.

Design an AI-assisted workflow for a recurring task — which steps to hand to AI, which to keep human, and how they connect — so you get leverage without losing quality or control. Use when asked how do I use AI for [process], automate this with AI, design an AI workflow, or where does AI fit in my process. Produces a map of the task's steps split into AI-does / human-does / human-checks, the right tool/prompt for each AI step, the hand-offs and review points, the failure modes to guard against, and a start-small rollout — turning a manual process into a reliable AI-assisted one that keeps you in control.

Check live air quality anywhere with zero API keys — Open-Meteo's air-quality API via curl, decoded from raw PM2.5 and AQI numbers into what they mean for going outside. Use when asked what's the air quality, is it safe to run outside, AQI in my city, or pollution levels right now. Produces the current AQI and pollutant levels, the plain-language health read with the standard bands, and the rerunnable command.

Build an all-hands that lands with everyone from intern to VP — the mixed-altitude structure (the story for all, the numbers for some), the wins-with-names section done right, the hard-news slide handled straight, and the Q&A design that gets real questions. Use when asked build the all-hands deck, make the monthly town hall not boring, how do we share the numbers with everyone, or announce this change at all-hands. Produces the segment structure, the altitude-mixed content rules, the hard-news handling, and the Q&A mechanics.

Re-pitch one piece of content for four audiences — the board, the engineers, a customer, a new hire — with a delta table showing what changed between altitudes and why. Use when asked to rewrite this for execs, explain this to the team, make this customer-facing, or say this four ways. Produces the four versions plus the delta table of what was cut, added, and reframed per altitude.

Structure vague opportunities and unclear briefs into actionable one-page problem statements. Use when asked to clarify a vague brief, frame an undefined problem, make sense of an unclear opportunity, or when the user says 'we need to figure out what to do about X' or 'I've been asked to look into Y'. Produces a structured problem brief with reframed questions, scoped boundaries, and a minimum viable research plan.

Prepare for an industry analyst briefing (Gartner, Forrester, IDC and similar). Use when asked to prep an analyst briefing, write an AR briefing document, build talking points for an analyst call, or prepare a Magic Quadrant / Wave submission narrative. Produces a briefing kit — objective, company/product narrative, differentiation, proof points, the demo storyline, anticipated questions, and follow-up commitments.

Write a short, punchy announcement designed to be shared as an image or social card. Use when asked to announce a launch, milestone, feature, hire, funding, or win — something to post on LinkedIn/X/Slack. Produces a tight, visually-structured announcement (headline, one-liner, 2-3 proof points, CTA) that looks great exported as a PNG card from the playground.

Write clear, developer-facing API documentation. Use when asked to document an API endpoint, write API reference docs, create a developer guide, or turn a raw spec/Postman collection into documentation. Produces endpoint documentation with descriptions, parameters, request/response examples, and error codes.

Publish 'how to work with me' as a literal API spec — endpoints (what to ask me for and what you'll get back), rate limits (meeting and interrupt tolerance), error codes (what happens when you surprise me Friday 5pm), auth (how to earn trust), and a changelog. Use when onboarding to a new team, when a new manager or report arrives, for a team working-styles session, or 'write my README/user manual'. Produces a personal API spec that's genuinely funny and secretly the best onboarding doc on the team.

Plan tests for an API endpoint or service — functional, negative, and contract. Use when asked to test an API, write API test cases, plan REST/GraphQL endpoint testing, or validate an API contract. Produces an API test plan — per-endpoint cases (status codes, schema, auth, validation, errors), boundary/negative cases, contract checks, and non-functional notes — so the API is verified beyond the happy 200.

Write an API versioning strategy document for a service or API platform. Use when asked to define versioning policy, plan API deprecation, classify breaking changes, or document version lifecycle. Produces a complete versioning strategy with breaking-change classification table, deprecation timeline, migration guide template, and client communication template.

Write a sincere, effective apology to a customer, group, or the public. Use when asked to write an apology, say sorry to a customer or community, make amends after a mistake, or respond to a complaint with an apology. Produces a genuine apology — acknowledgement, taking responsibility, empathy for the impact, the concrete fix and prevention, and an offer to make it right — in the right tone, without excuses or non-apologies.

Cut through the model soup to buy the right appliance — the features that actually matter for you, the ones that are marketing, and when to buy. Use when asked which [fridge/washer/dishwasher] should I buy, help me choose an appliance, what features do I need, or is this appliance worth it. Produces a needs-based feature shortlist (must-have vs nice-to-have vs marketing fluff), fit and capacity checks, reliability and running-cost considerations, warranty/extended-warranty guidance, and timing tips — flagging to verify current models, prices, and specs before buying.

Plan an apprentice's or new laborer's first week so they're useful by Friday and safe from hour one — day-by-day teaching order, the safety non-negotiables stated before anything else, what they're allowed to touch unsupervised, and the check-out conversation that decides week two. Use when a tradesperson says 'my apprentice starts Monday', 'how do I train the new guy', or 'the apprentice is useless and I don't have time to teach'. Produces a first-week plan, a can/can't-touch list, and the Friday review script.

Create an Architecture Decision Record (ADR) for any technical decision. Use when asked to document a technical decision, write an ADR, record an architecture choice, or capture why a technology or approach was selected. Produces a structured ADR with context, decision, consequences, and tradeoffs.

Diagram a system or technical architecture — services, data stores, and how they connect. Use when asked to draw an architecture, show how components fit together, map a system/data flow, or visualize services and dependencies. Produces a ready-to-render Mermaid diagram with grouped subgraphs (renders live, exportable as PNG/SVG) plus a component legend and notes.

Design the archive layer that keeps current workspaces lean without losing history — what moves, when, to where, findable-by-search, with the project-close ritual that makes archiving automatic instead of aspirational. Use when asked set up an archiving system, our workspace is drowning in old projects, when should things get archived, or make history findable without cluttering today. Produces the archive triggers, the destination structure, the findability rules, and the close-out ritual.

Set up the essentials in the right order after moving to a new country — the ID/registration, bank account, phone, address, and social/tax number that unlock each other — so you don't get stuck in the chicken-and-egg loops that trap newcomers. Use when someone says 'I just moved to a new country', 'what do I do first after arriving', 'set up my life in [country]', or 'I can't open a bank account without an address but can't rent without a bank'. Produces a sequenced arrival checklist with dependencies and the official offices for each. Routes to official sources; rules are local.

Build and deliver a raise request that actually works — the evidence, the number, the timing, and the exact words — instead of hoping it gets noticed. Use when asked how do I ask for a raise, I deserve more money, prepare me to ask for a raise, or negotiate a pay increase at my job. Produces a value case built on your actual contributions and market rate, a specific target number with justification, the right timing and person, a script for the conversation, and responses to the likely pushbacks — turning 'I want more' into a business case your manager can say yes to.

Surface the hidden assumptions a plan or belief rests on, then test what happens when each one is wrong. Use when asked what am I assuming here, check my assumptions, what if I'm wrong about, or stress-test my thinking. Produces the unstated assumptions your conclusion depends on (ranked by how load-bearing they are), a flip of each to see which one breaking would change everything, and the cheapest way to check the riskiest ones — because the assumption you didn't know you were making is what sinks plans.

Extract every hidden assumption from a plan or document and put a price on each one — what it costs if wrong, what it costs to test. Use before committing to anything whose author says 'obviously' or whose spreadsheet has hardcoded cells: the bounty hunt makes the invisible load-bearing beliefs explicit and tells you which three to test this week. Produces the assumption ledger (priced and ranked), the cheapest test for each dangerous one, and the document's honest confidence statement.

Extract and risk-rate hidden assumptions in a product brief or PRD. Use when asked to review a product brief for assumptions, audit a PRD for risks, find hidden assumptions, validate product plans, or run an assumption analysis. Produces a prioritised assumption map with confidence and impact scores, recommended validation methods, and critical assumption flags.

Run a decision asynchronously — the memo, the silent-read window, the comment protocol, and the deadline that makes it land without a meeting. Use when asked to decide something async, replace a decision meeting with a document, run an Amazon-style written decision process, or when a decision keeps stalling in comment threads. Produces the decision memo plus the process wrapper: reader roles, response windows, comment-resolution rules, and the tie-breaker. For the document structure alone use decision-memo; this skill runs the process around it.

Convert a meeting into async work that actually decides — the doc-plus-deadline format that replaces the room, the comment-window rules, the decision-closure step that async usually fumbles, and the honest test for what still needs synchronous. Use when asked can this meeting be async, replace our status meeting with a doc, run this decision without a call, or async isn't working for us. Produces the conversion design, the async artifact format, the closure protocol, and the still-needs-a-room list.

Compile the team's REAL updates into one async standup — pull what people posted in Slack (and moved in Notion/Linear), not a template for running standups. Use when asked to compile today's standup, pull the team's updates into one post, what did the team ship, or run async standup in Cowork. Reads a Slack channel and (optionally) the tracker via connectors, groups updates by person into shipped / in-progress / blocked, surfaces the blockers needing attention, and produces a standup-digest artifact ready to post back.

Write status updates people actually read — the traffic-light-plus-narrative format (state first, story second), the blockers-are-asks rule, and the skimmable structure that respects a reader with thirty seconds. Use when asked write my weekly update, format our team's status posts, nobody reads my updates, or what goes in a good async check-in. Produces the update format with a filled example, the blockers-as-asks discipline, and the reader-time contract.

Get your attention back with a 30-day protocol that assumes you'll break it — a screen-time ledger without moralizing, friction engineering (what to delete, grayscale, where the phone sleeps), planned relapses, and honest replacement activities for the boredom that shows up on day 3. Use when someone says 'my screen time is 7 hours', 'I want a dumbphone', 'digital detox', 'I can't read books anymore', or 'my attention span is gone'. Produces the ledger, a personal friction plan, and the 30-day protocol with expected failure points.

Decode an auto repair estimate — what each line actually is, which items are urgent vs upsell, and the questions that separate a fair shop from a fishing expedition. Use when someone asks 'is this repair quote fair', 'decode my mechanic's estimate', 'do I really need all this', or 'is the shop ripping me off'. Produces a line-by-line decode with urgency triage, parts/labor sanity checks, ranked red flags, and the exact questions to ask the shop before authorizing.

Decide which of your recurring rituals to put on autopilot — and which to keep manual. Use when asked what to automate, how to set up recurring AI runs, which reports or briefings could run on a schedule, or to design an automation charter for a team. Produces a ritual inventory with automate/assist/keep-manual calls, guardrails per ritual, and a rollout order.

Draft the hard personal message you keep putting off — chasing money a friend owes, backing out of plans, checking in after a fight, following up on an unanswered text. Use when asked to help send an awkward text, how to say something uncomfortable to a friend, word a difficult personal message, or bring up something touchy. Produces a couple of calibrated options, the one line to open with, and the send/wait/call judgement call — warm, honest, and not a doormat.

Set up a backup system that actually protects your photos, files, and devices — built on the 3-2-1 rule and, crucially, tested so it works when you need it. Use when asked how to back up my data, set up backups, protect my photos/files, or what's a good backup strategy. Produces a 3-2-1 plan tailored to your devices and data, specific what-to-back-up priorities, an automation setup so it happens without you, a restore-test step, and protection against the failure that ruins backups (ransomware/sync-deletes reaching the backup).

Write the band agreement before the money or the breakup arrives — who owns the songs, how money splits (writing vs performing distinguished), who owns the name, what happens when someone quits, and the decision rules for offers — decided while everyone still shares a van. Use when a band asks 'how should we split money', 'who owns our songs', 'our drummer quit, what happens', or is about to record/release/sign anything. Produces a plain-language band agreement and the meeting script to agree it. Not legal advice — it's the conversation that makes the lawyer cheap later.

Get a bank fee waived or refunded — overdraft, late, maintenance, ATM, or foreign-transaction — with the ask written and the leverage that works. Use when asked to get a bank fee refunded, waive my overdraft fee, the bank charged me a fee, or how to get charges reversed. Produces a read on which fees are commonly reversible, the script to request a refund (in person, chat, or call), the loyalty/first-time/error leverage to use, and how to prevent the fee recurring — plus when to escalate or switch banks.

Think clearly about whether bankruptcy is the right move, or whether another path fits better — without shame and without a sales pitch. Use when asked should I file for bankruptcy, is bankruptcy my best option, alternatives to bankruptcy, or what happens if I file. Produces an honest read on whether your situation is the kind bankruptcy actually helps, the main types and what each does (and doesn't) discharge, the real trade-offs (what you keep, the credit impact and its recovery, what's not dischargeable), the alternatives to weigh first (negotiation, debt management, doing nothing on time-barred debt), and a strong push to consult a bankruptcy attorney — so the decision is informed, not driven by fear or a debt-relief ad. Not legal advice; centers a real attorney consult.

Build a tiered classroom behavior intervention plan (BIP) for a K-12 student, grounded in the function of the behavior. Use when asked to plan a behavior intervention, address a disruptive or off-task pattern, write a BIP, or set up positive behavior supports. Produces a function hypothesis, prevention/antecedent strategies, teaching of a replacement behavior, a response plan for when it happens, and a simple data-tracking method — positive and skill-building, not punitive.

Audit the beneficiary designations that quietly override wills — the account-by-account sweep, the life-event triggers that make them stale, and the coordination check against actual intentions. Use when asked check my beneficiaries, does my 401k go to my ex, do beneficiary forms beat a will, or what should I update after marriage/divorce/a birth. Produces the account sweep list, the stale-designation red flags, the intent-vs-paperwork comparison table, and the update checklist with the verify-in-writing step.

Check whether a raise, more hours, or a new job could cost you more in lost benefits than you gain — the 'benefits cliff' — before you accept it. Use when asked will a raise hurt my benefits, benefits cliff, if I make more will I lose my food stamps or medicaid, or should I take more hours. Produces a plain map of which benefits phase out at what income (and which cut off suddenly vs. taper), a rough read on whether a specific income change helps or hurts net, the ones with hard cliffs to watch (childcare, Medicaid, housing), the moves that soften a cliff, and where to get a real benefits screening — so you make an income decision with eyes open, not a nasty surprise. Not financial/benefits advice; points to a benefits counselor.

Decode an employment benefits package into what it's actually worth and where the fine print bites. Use when someone asks 'is this offer good', 'decode my benefits package', 'what does my equity actually mean', or 'what should I ask HR before signing'. Produces a benefit-by-benefit decode with real dollar values, ranked red flags (vesting cliffs, clawbacks, 'discretionary' bonuses, unlimited-PTO economics), and the questions to ask HR before signing.

Audit a week the way Arnold Bennett's 'How to Live on 24 Hours a Day' (1908) prescribes — time as the one income that cannot be increased, the day-within-the-day, and starting with 90 minutes, not a life overhaul. Use when someone says 'I have no time', 'work eats everything', 'I want to learn X but can't fit it', or asks for a time audit or evening routine. Produces a time ledger, one reclaimed 'inner day' block, and Bennett's own warnings about overreach.

Analyse a construction bid or tender package for scope gaps, risk-shifting exclusions, unit-rate red flags, and front-loading in the schedule of values. Use when asked to review a bid, level bids, check a tender for gaps, compare sub quotes, or vet a schedule of values before award. Produces a structured bid review with a gap register, exclusion risk table, pricing red flags, and an award recommendation with pre-award clarifications.

Decide when to buy a big-ticket item to get the best price — the sales cycles, model-refresh timing, and 'buy now vs wait' math for the specific thing you want. Use when asked when's the best time to buy [item], should I wait for a sale, is now a good time to buy, or when do [products] go on sale. Produces the typical discount calendar for that category, whether a new model/version is due (and if the current one will drop), a buy-now-vs-wait recommendation for your timeline, and price-tracking tactics — flagging that timing is a guide, not a guarantee.

Get started birding from where you are — what you're likely to see, how to tell confusing species apart, and a simple life-list to track sightings. Use when asked to start birdwatching, what bird did I see, help me identify a bird, or set up a birding log. Produces a likely-species list for your area and season, ID prompts (the field marks and sounds that separate look-alikes), a beginner gear-and-timing note, and a lightweight life-list format — pointing you to a live ID app to confirm any specific sighting.

Run the worst-case drill before an agent goes autonomous — the 'if this agent were fully hijacked right now, what's the damage' walk-through, the containment controls (caps, kill-switch, reversibility, isolation), and the recovery plan. Use when asked what's the worst my agent could do, run a blast-radius assessment, prepare for an agent going rogue, or am I ready to let this run unattended. Produces the worst-case walk-through, the containment controls, the reversibility audit, and the incident-recovery runbook.

Plan the merging of two families thoughtfully — roles, rules, routines, and relationships — so a blended household starts on the right foot instead of a collision. Use when asked to help blend our families, moving in with my partner and their kids, step-parenting help, or how to merge two households. Produces a read on the situation and its sensitivities, an approach to step-parent roles and discipline, a plan to align house rules and routines across homes, ways to build relationships at each child's pace, and how to handle exes and loyalty binds — realistic, not idealized. Not therapy.

Build the storyline and slide structure for a board presentation. Use when asked to create a board deck, board presentation narrative, board meeting slides, or quarterly board update. Produces a complete slide-by-slide structure with narrative beats, talking points, and slide content guidance.

Take a board game idea from 'wouldn't it be cool if' to a playtestable prototype — core loop, tension source, components you can make tonight, balance starting-points, and a real playtest protocol with kill criteria. Use when someone says 'I have a board game idea', 'design a game about X', 'my game drags in the midgame', or 'how do I playtest this'. Produces a design one-pager, a print-and-play prototype spec, and a 3-session playtest plan.

Plan a board game night that actually lands — the right games for your group size, mix, and time, in a running order that keeps energy up. Use when asked to plan a game night, what board game should we play, games for [N] people, or what to play with a mixed group. Produces game picks matched to player count and experience, a warm-up-to-main running order, teach-time and play-time estimates, and swaps for the non-gamers or the one player who hates losing.

Write formal board meeting minutes from an agenda, notes, transcript, or discussion summary. Use when asked to draft board minutes, governance minutes, meeting minutes for a board, or a formal record of decisions and actions. Produces structured board minutes with attendees, agenda items, resolutions, decisions, action register, and approval-ready wording.

Write a board pre-read that's sent before the meeting so the meeting is about decisions, not status. Use when asked to prepare a board pre-read, a board update/package, or pre-meeting materials for a board. Produces a board pre-read — a TL;DR, the metrics dashboard vs. plan, what's working / what's not, the decisions and asks for the board, and risks — designed to be read in advance.

Set up and run a body-doubling session — using another person's presence (in the room, on a call, or a chat check-in) to start and stay on the task your ADHD brain keeps bouncing off. Use when someone says 'I can't start this task', 'body double with me', 'I only work when someone's around', or has ADHD/executive-dysfunction and a task that won't begin. Produces a session plan, the exact ask to send a body-double partner, and a solo fallback for when no one's available.

Act as a body-double for a work session — a present, low-pressure companion that keeps you accountable and moving through the task without doing it for you. Use when asked be my body double, keep me company while I work, help me focus on this task, or I work better with someone there. Produces a session structure (goal, time block, check-in cadence), gentle presence and momentum nudges at intervals, distraction rescue when you drift, and an end-of-session acknowledgment — recreating the focus that comes from someone just being there.

Review a bill of materials for cost, risk, and supply exposure — cost rollup, top-10 cost drivers, single-source and EOL risk, MOQ vs forecast mismatch, cost-down candidates, and tariff/logistics sensitivity. Use when asked to review a BOM, find cost-down opportunities, check component sourcing risk, or sanity-check BOM cost against target. Produces a structured BOM review with a cost driver Pareto, risk flags per line, and a prioritised cost-down list.

Set up a chart of accounts and rules for categorizing transactions. Use when asked how to categorize expenses/transactions, set up a chart of accounts, organize bookkeeping, or sort bank transactions into the right buckets. Produces a practical chart of accounts for the business, categorization rules with examples and edge cases, and a clean-books routine — so the books are consistent and ready for an accountant. Not tax/accounting advice.

Build boolean and X-ray search strings to source candidates. Use when asked to build a boolean search, source candidates on LinkedIn/Google, write an X-ray search, or find people with specific skills. Produces ready-to-paste boolean strings (with synonyms, must-haves, and exclusions), X-ray variants for LinkedIn/GitHub, and a refinement plan to widen or narrow the result set.

Set a boundary with someone — a friend, family member, coworker, or partner — clearly and kindly, with the actual words and a plan for the pushback. Use when asked how do I set a boundary with, I need to say no to, someone keeps overstepping, or help me set limits with. Produces a read on the boundary you actually need, a warm-but-firm script to state it (without over-explaining or apologizing it away), how to hold it when they push back or guilt-trip, and what to do if they don't respect it — because a boundary you can't state and hold isn't a boundary.

Keep a running brag document of your accomplishments so reviews and promo cases write themselves. Use when asked to start or update a brag doc, log a win, track accomplishments, or prep evidence for a review/promotion. Produces a structured, dated accomplishment log — impact-first entries with metrics, scope, and the evidence link — grouped so it drops straight into a self-review or promo packet.

Run a real brainstorm — divergent generation without judgment, then convergent selection with explicit criteria — instead of listing ten obvious ideas and calling it creativity. Use when asked to brainstorm, generate ideas or options, explore a solution space, or name something. Produces a genuinely wide option set (including the weird tail), then a shortlist selected against named criteria with the rejects preserved.

Extract a brand's visual and verbal identity into an applicable guideline kit — tokens, voice rules, and do/don't pairs — then apply it consistently to any artifact. Use when asked to apply brand guidelines to a document/deck/page, to extract a brand kit from existing materials or a website, to keep AI-produced artifacts on-brand, or to write lightweight brand guidelines for a startup. Produces a compact brand kit (visual tokens + voice rules + application examples) and/or an artifact restyled to it. For a creator's personal voice use creator-brand-kit; for building new UI systems use frontend-design.

Respond to a brand or executive impersonation incident — deepfaked executives, cloned support lines, fake apps, spoofed domains, or AI-generated scam content wearing your name. Use when a deepfake of a leader is circulating, customers report a fake version of your product or support channel, or to prepare the impersonation playbook before it happens. Produces an incident response: verification protocol, takedown sequencing by platform, customer and public communications, and the hardening plan. For general crisis comms use press-release/pm-crisis skills; for security incidents inside your systems use security-incident-response.

Interview the user with sharp, one-at-a-time questions to turn a vague request into a tight, complete brief any other skill can run on. Use when a request is fuzzy, under-specified, or 'help me think this through', or before running a skill that needs inputs the user hasn't given. Produces a structured brief (goal, audience, constraints, success criteria) and hands off to the right skill — by interrogating, not guessing.

Turn a folder of accumulated documents into one decision-ready brief — the skim-map pass over the pile, the extraction against the brief's actual questions, the conflict reconciliation when documents disagree, and the provenance trail back to sources. Use when asked read all this and tell me what matters, synthesize this folder for the new lead, turn these 20 docs into a brief, or what does all this material actually say. Produces the pile map, the question-driven extraction, the reconciled brief with per-claim sources, and the didn't-read honesty ledger.

Write a one-page briefing note that gets a busy principal up to speed fast. Use when asked to brief a minister/executive/official, prepare a briefing note or read-ahead, or summarize an issue for a decision or meeting. Produces a tight, single-page note: purpose, background, key facts/considerations, and a recommendation or the decision sought — scannable in two minutes.

Run the pre-flight checklist before an agent drives a browser — the untrusted-web-content threat (every page is attacker-controllable), the credential and session-cookie exposure, the action-confirmation gates for purchases and posts, and the sandboxing that limits the damage. Use when asked let my agent browse safely, is it safe to give the agent computer/browser use, guardrails before the agent uses my browser, or review my browser agent's setup. Produces the sandbox decision, the content-injection defenses, the action gates, and the credential-isolation rules.

Build a realistic personal monthly budget from someone's income and expenses. Use when asked to make a budget, plan monthly spending, allocate income, or get finances under control. Produces a categorized budget (a 50/30/20-style allocation tuned to their reality), a surplus/shortfall number, and concrete next moves. Educational, not regulated financial advice.

Design a budget-vs-actuals tracker that stays alive past February — the category grain that matches real statements, the variance view that answers 'are we okay', the update ritual small enough to survive, and the honest handling of irregular expenses. Use when asked build me a budget spreadsheet, track team spend against budget, why do we always blow the budget invisibly, or design a household/project budget tracker. Produces the tracker structure, the variance logic, the irregulars ledger, and the monthly fifteen-minute ritual.

Produce a structured budget variance analysis from actual vs budget figures. Use when asked to analyse budget variances, explain underspend or overspend, write a variance commentary, or investigate why actuals differ from plan. Produces a categorised variance table with root cause analysis and management commentary.

Diagnose a bug systematically instead of guessing — reproduce, isolate, form hypotheses, and test them to root cause. Use when debugging, chasing a defect, an intermittent failure, or 'why is this happening?'. Produces a structured diagnosis: a reliable repro, the narrowed-down location, ranked hypotheses with how to test each, and the root cause + fix once found.

Write a clear, reproducible bug report that gets fixed fast. Use when asked to write a bug report, file a defect, report an issue, or turn 'it's broken' into an actionable ticket. Produces a structured report — a precise title, steps to reproduce, expected vs. actual, environment, severity/priority, and evidence — so a developer can reproduce and fix it without a back-and-forth.

Triage a raw bug report into something a team can act on — clean repro steps, a defensible severity/priority, environment, likely area/owner, and duplicate check. Use when asked to triage this bug, set severity and priority, is this a P1, or clean up this bug report for the backlog. Produces the normalized repro, a severity and priority with the reasoning (impact × frequency × workaround), the environment/metadata, a suspected component and owner queue, and a duplicate/related-issue check — flagging when info is missing rather than guessing.

Interview you into a durable personal MEMORY.md — your decision rules, patterns, past failures, and preferences — that any AI can read to help you better, with privacy guardrails built in. Use when asked to build my memory file, help my AI remember me, create a MEMORY.md, or set up context about myself. Produces a structured personal-context file drawn out through good questions (how you decide, what you keep repeating, what you don't want to repeat), organized for an AI to use — while explicitly refusing to store sensitive data like credentials, financial, health, or others' personal info.

Build a realistic recovery plan for burnout — address the causes, not just the symptoms — with changes you can actually make at work and outside it. Use when asked to help with burnout, I'm burnt out, how to recover from burnout, or I'm exhausted and dread work. Produces a read on what's driving the burnout (load, control, reward, fairness, values, community), immediate relief steps, the boundary and workload changes that address the root, a recovery timeline with realistic expectations, and a flag that severe or persistent burnout/depression warrants a professional. Not medical advice.

Pressure-test a business or side-hustle idea before you sink money and months into it — find the real demand, the risky assumptions, and the cheapest way to test them. Use when asked to validate my business idea, is this a good business idea, test my side hustle, or should I start this. Produces a read on the core assumptions the idea depends on, who the customer really is and whether the pain is real, the cheapest experiments to test demand before building, a rough viability check (market, competition, economics), and a go/refine/rethink call — honest, not a cheerleader.

Defragment a work calendar through a tool-using agent — find the meeting debt, propose the consolidation, and (approval-gated) execute the moves. Use when asked to defrag my calendar, get me focus time, audit my meetings, or fix my week. Produces the calendar audit (cost per meeting, fragmentation map), a defrag proposal with focus blocks, and an approval-gated execution plan.

Turn interview notes into a structured candidate scorecard and hire recommendation. Use when asked to write an interview scorecard, a candidate evaluation, an interview debrief, or to summarize feedback into a hire/no-hire call. Produces a per-competency assessment with evidence and ratings, an overall recommendation with confidence, and the open questions for the next round — evidence-based, bias-aware, and decision-ready.

Explain a cap table, dilution, SAFEs, option pools, and round mechanics in plain English with the actual math. Use when asked to explain dilution, model a SAFE or priced round, size an option pool, understand a term sheet's economics, or figure out who owns what after a raise. Produces a worked ownership breakdown before/after the round, the dilution math step by step, and the traps founders miss. Not legal or financial advice.

Produce a capacity planning document for a service covering traffic forecasts, resource requirements, and scaling strategy. Use when asked to plan infrastructure capacity, forecast resource needs, model traffic growth, define scaling strategy, or produce a capacity review for a service. Produces a structured capacity plan covering current baseline metrics, growth projections, resource requirements per tier, scaling strategy, cost projections, capacity triggers, and an infrastructure action roadmap.

Allocate a finite budget or headcount across competing initiatives by return and strategic fit. Use when asked to allocate budget, decide where to invest, build a funding/portfolio plan, or make trade-offs across initiatives under a cap. Produces a capital-allocation plan — initiatives scored by expected return × strategic fit per dollar, a funded/unfunded split against the cap, the cut line, and the reasoning.

Negotiate a car purchase without getting played — know the real target price, handle the dealership tactics, and keep the financing and add-ons from eating your savings. Use when asked to help me negotiate a car, buy a car without getting ripped off, what should I pay for this car, or dealership negotiation tips. Produces a target-price approach (research the out-the-door price), the dealer tactics to expect and counters, guidance on separating price/trade/financing, the add-ons to decline, and a walk-away plan — flagging to verify current pricing and rates.

Decode a car lease offer — the money factor converted to APR, the cap-cost math, mileage and disposition traps, and what to negotiate. Use when asked to decode my car lease, is this lease deal good, what's a money factor, or review this lease before I sign. Produces the real-numbers decode (money factor → APR, total lease cost), the trap list with dollar exposure, and the negotiation points dealers expect to concede.

Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly payment. Use when asked should I lease or buy a car, is it cheaper to keep my old car, what does this car really cost per month, or new vs used total cost. Produces the ranked scenario totals, per-month true cost, the assumption ledger, and the not-modeled list.

Sanity-check a greenhouse gas inventory before it goes into a report or gets audited. Use when asked to review a carbon footprint, check a GHG inventory, validate scope 1/2/3 numbers, explain a year-over-year emissions change, or prepare emissions data for assurance. Produces a boundary review, data-quality assessment, emission-factor sensitivity list, YoY bridge, and a fix-before-publishing list.

Run a family meeting to make a big care decision together — so it's a shared, informed decision instead of a fight or one person deciding alone. Use when asked help me run a family meeting about care, we need to decide together about mom's care, my siblings and I disagree about our parent, or facilitate a care decision. Produces an agenda and structure for the meeting, how to prepare (facts, options, everyone's input), ground rules to keep old family dynamics from derailing it, how to include the person being cared for, ways to work through disagreement toward a decision, and clear next steps with owners — turning an emotional, conflict-prone conversation into a productive one. Not legal, medical, or financial advice.

Organize the people and information involved in caring for someone — family, doctors, helpers — so care doesn't fall through the cracks or all land on one person. Use when asked help me coordinate care for, organize caregiving for my parent, set up a care system, or I'm drowning coordinating everyone. Produces a map of who does what (medical, daily, financial, emotional), a shared-information system so everyone's on the same page, a way to divide tasks fairly among family, a communication rhythm, and how to keep the key information (meds, contacts, wishes) in one accessible place — turning caregiving chaos into a coordinated effort.

Map where you are against the next level and build a concrete plan to close the gap. Use when asked to map a career ladder, find the gap to the next level, build a development/growth plan, or figure out what to work on to get promoted. Produces a level-gap map — current vs. target competencies side by side, the specific gaps, and a prioritised 1–2 quarter plan of evidence-generating projects to close them.

Build a realistic plan to change careers — mapping your transferable skills, the real gaps, and a bridge that doesn't require torching your income overnight. Use when asked to help me change careers, career pivot plan, how do I switch to [field], or I want a new career but don't know how. Produces a transferable-skills map, an honest gap analysis to the target role, a staged bridge (skill-building, positioning, side-door entry), a financial-runway reality check, and a narrative that reframes your background as an asset — not a starting-from-zero story.

Check whether you're burning out as a caregiver — and get a realistic plan to protect yourself before you can't keep going. Use when asked I'm exhausted from caregiving, am I burning out caring for my parent, caregiver stress help, or I have nothing left to give. Produces an honest read on your burnout signs and how depleted you are, permission and reasons to accept help (which caregivers resist), specific ways to get support and respite, the guilt and identity traps to address, and a realistic self-care plan that fits a caregiver's actual life — because a caregiver who collapses can't care for anyone. Not medical or mental-health treatment.

Organize care for an aging or ill family member across multiple helpers — the shared care map, a fair rotation with backup rules, the information binder, and family-meeting agendas that prevent the one-sibling-does-everything spiral. Use when asked help me coordinate care for my mom, my siblings and I need to split caregiving, organize care for a sick family member, or set up a care schedule. Produces the care map of needs and coverage, the rotation schedule with escalation rules, the binder outline, and the family meeting agenda.

Write a fundraising case for support that makes donors want to give. Use when asked to write a case for support, a fundraising case statement, a major-gift or campaign case, or the core argument for a donation appeal. Produces a persuasive case — the need, your solution and why you, the impact a gift makes, specific funding opportunities with amounts, and a clear ask — donor-centred, not org-centred.

Write a client case study that sells future work — challenge, approach, results. Use when asked to write a case study, a client success story, a project write-up, or a portfolio case for consulting/agency work. Produces a results-led case study — the client & challenge, your approach, quantified outcomes, a client quote slot, and a takeaway — structured to win the next client. Ready to export as a designed PDF.

Build a short-term (13-week) cash flow forecast to see if you can cover what's due. Use when asked to build a cash flow forecast, a 13-week cash flow, a cash projection, or to plan around a cash crunch. Produces a week-by-week forecast structure — opening cash, expected inflows, scheduled outflows, net movement, and closing/low-point — with the formulas and a worked example, plus the levers if cash goes tight. Not financial advice.

Plan an e-commerce category / collection page that ranks and merchandises well. Use when asked to design a category page, a PLP (product listing page), a collection page, or to improve category SEO and merchandising. Produces a brief — search intent & keywords, intro copy, merchandising/sort logic, filters & facets, internal links, and SEO/technical notes — so the page converts browsers and earns organic traffic.

Draft a firm, professional cease-and-desist letter to stop harassment, defamation, IP misuse, or unwanted contact — clear about what must stop and what happens if it doesn't. Use when asked to write a cease and desist, make someone stop [harassing/using my work/defaming me], or send a formal letter to stop. Produces a structured letter stating the conduct, why it's wrongful, the specific demand and deadline, and the consequence, plus guidance on delivery and records — flagging when the matter needs a real lawyer. Not legal advice.

Create a structured change management plan for any organisational change. Use when asked to write a change management plan, manage a change initiative, plan a system rollout, or lead an organisational transformation. Produces a plan covering stakeholder analysis, impact assessment, communication strategy, and resistance management.

Draft a defensible construction change order with entitlement basis, scope delta, itemised pricing, and schedule impact. Use when asked to write a change order, price extra work, draft a CO or COR/PCO, respond to a directive for changed work, or paper a field change. Produces a complete change order request with contract-clause entitlement, labour/material/equipment/OH&P breakdown, time impact statement, and reservation of rights.

Write changelogs and release notes readers actually benefit from — changes translated to so-whats, grouped by reader impact (breaking first, gifts second, plumbing last), with the upgrade path stated and the marketing kept honest. Use when asked write the release notes, turn this commit list into a changelog, announce this update to users, or why does nobody read our changelogs. Produces the impact-grouped changelog, the so-what translations, the breaking-changes block with migration steps, and the two-audience split when needed.

Write a human changelog from the REAL commit history — read the actual commit range via the GitHub connector, not a template. Use when asked to write the changelog for this release, what changed since the last tag, draft release notes from my commits, or summarise this range for users in Cowork. Reads commits/PRs between two refs via the GitHub connector, groups them into user-facing changes (features / fixes / breaking), translates commit-speak into human benefit, and produces a changelog artifact ready for the release.

Convert a git log, commit list, or release notes into a polished, user-facing changelog. Use when writing release notes, generating a CHANGELOG.md entry, or documenting what changed in a version. Produces a structured changelog section with version header, categorised changes, and migration notes. For an already-curated change list use changelog-writer instead.

Turn a list of changes, commits, or PRs into clean release notes / a changelog entry. Use when asked to write release notes, a changelog, or a version announcement from raw changes. Produces a Keep-a-Changelog-style entry grouped by type (Added/Changed/Fixed/etc.), written for users — surfacing breaking changes and upgrade notes up top. To go straight from a raw git log use changelog-generator instead.

Fix a team's chat sprawl — the channel map with one purpose per channel, the naming scheme that makes purpose findable, the archive pass for the dead and duplicated, and the posting norms (threads, @-discipline, urgency signals) that keep signal findable. Use when asked clean up our Slack/Teams, we have 90 channels and nothing is findable, set channel norms, or where should things get posted. Produces the channel audit and map, the naming scheme, the norms card, and the archive pass.

Win a chargeback dispute — read the reason code, assemble the evidence packet, and write the rebuttal that actually persuades the bank. Use when asked to fight a chargeback, respond to a payment dispute, write a chargeback rebuttal, or contest a customer chargeback. Produces the reason-code decode, the required-evidence checklist for that code, the structured rebuttal letter, and an honest read on whether this one is winnable — so you fight the right disputes and concede the rest. For merchants.

Turn numbers into a chart — bar, line, area, pie, or doughnut. Use when asked to chart or graph data, visualize metrics/trends/breakdowns, or show numbers as a picture instead of a table. Produces a ready-to-render chart spec (renders live in the playground and exports as PNG) plus a one-line read of what the chart shows.

Pick the chart the data and the point actually need — the question-to-chart mapping (comparison, trend, composition, distribution, relationship), the honesty rules (axes, baselines, dual-axis traps), and the one-chart-one-point discipline. Use when asked what chart should I use, make this data visual, why does this chart feel misleading, or fix this graph for the deck. Produces the chart verdict with its reasoning, the honesty checklist applied, and the labeling that lets the chart travel without its author.

Extract pixel-level data from an image of a chart or graph and produce a structured data table. Use when asked to extract data from a chart image, transcribe numbers from a graph, digitise a chart, or turn a screenshot of data into a table. Produces a structured table with extracted values, confidence levels, and a reconstructed chart source. Best used with Claude Opus 4.7 or newer for reliable chart data extraction.

Build a small, coherent opening repertoire that fits your style and level — the few lines actually worth learning, plus the plans and traps behind them. Use when asked what chess opening should I learn, build me a repertoire, help with my openings, or what to play against [opening]. Produces a compact repertoire for White and Black keyed to your rating and style, the main ideas and typical plans (not just moves to memorize), the common traps to know from both sides, and what to study next — kept small enough to actually learn.

Compare childcare options — nursery/daycare, childminder, nanny, family, or a mix — for your family's real needs, budget, and values. Use when asked to compare childcare options, nursery vs nanny, how to choose childcare, or find the right childcare. Produces a needs-and-values profile, a side-by-side of the realistic options on cost/flexibility/socialization/control, the questions to ask and red flags to check on visits, a total-cost read (including subsidies), and a decision that fits your priorities — not a generic ranking.

Produce a structured churn analysis that separates avoidable from unavoidable churn. Use when investigating why customers are leaving, identifying at-risk segments, calculating net revenue retention, or building a retention intervention plan. Produces a churn report with rate calculations, categorised reasons by avoidability, segment breakdown, timing analysis, early warning signals, and prioritised interventions ranked by estimated impact.

Write a CI/CD pipeline playbook for a service or team. Use when asked to document a CI/CD pipeline, write a deployment process, define release gates, document build and test stages, or create a deployment guide. Produces a structured playbook covering pipeline stages, environment definitions, deployment gates, rollback procedures, and on-call responsibilities.

Keep citations honest in business documents — every load-bearing claim sourced, links that actually contain the claim, the as-of dates that keep numbers honest, and the internal-vs-external sourcing rules for decks and memos. Use when asked check the sourcing in this deck, add citations to this doc, our slide says 'studies show' — which studies, or set citation norms for the team. Produces the claim-by-claim audit, the fixes (source found, claim softened, or cut), the citation format for the venue, and the team norm card.

Decode an insurance claim denial letter — what the cited reason actually means, whether it's commonly overturnable, and the appeal letter that answers it point by point. Use when someone asks 'my insurance claim was denied what do I do', 'decode this denial letter', 'can I appeal this denial', or 'write my insurance appeal'. Produces the denial decode with overturn-likelihood framing, the evidence checklist, the point-by-point appeal letter, and the escalation ladder past the insurer.

Triage an incoming insurance claim: check the coverage trigger against policy wording, band severity and complexity, screen for fraud indicators, set a first-pass reserve range, and route with an SLA. Use when asked to triage a claim, review a first notice of loss (FNOL), assess a new claim, decide fast-track vs adjuster routing, or screen a claim for SIU referral. Produces a structured triage note with coverage view, severity band, indicator screen, reserve range, and a routing recommendation.

Work out whether you're eligible for a class-action settlement or refund program — and actually file the claim before the deadline. Use when asked am I owed money from a settlement, is there a class action for [product/company], how do I claim a settlement, or did I qualify for that refund. Produces a way to check for relevant settlements, an eligibility read against the class definition, the proof you need and how to file, deadline tracking, and honest expectations on payout size — plus how to avoid fake-settlement scams. Not legal advice.

Set up a repo or project so an AI coding agent works well in it — the CLAUDE.md, the context, the guardrails, and the conventions the agent needs to be useful instead of lost. Use when asked how do I set up CLAUDE.md, configure my repo for Claude Code, my AI agent keeps getting my project wrong, or onboard an AI agent to my codebase. Produces a structured CLAUDE.md/project-context file (architecture, conventions, commands, do-nots), the right level of detail (enough to orient, not a novel), the guardrails that keep the agent safe (what not to touch, how to test), and a maintenance habit so it stays current — turning a repo an agent flails in into one it navigates like a teammate.

Activate a 4-stage coding discipline framework that forces Claude to plan before coding, isolate changes on a branch, write tests first, and self-review output twice before presenting it. Use when starting a complex coding task, when past Claude sessions produced broken first drafts, or when you want to prevent rework cycles. Produces a confirmed written plan, isolated feature branch, test-first implementation, and a double-reviewed output with a correctness and code-quality checklist.

Explain a contract clause in plain English — what it means, who it favours, the realistic risk, and what to negotiate. Use when asked what a clause means, to decode legal language, explain a term in a contract, or assess whether a provision is standard or aggressive. Produces a plain-language translation, a who-does-this-favour read, a risk rating, and concrete redline suggestions. Not legal advice; confirm with counsel.

Write clear at-home care instructions for a pet owner after a veterinary visit, procedure, or hospitalization. Use when asked to write discharge instructions, go-home notes, post-op care, or medication instructions for a pet owner. Produces plain-language home-care instructions: medications (what/how much/when/how), activity restrictions, what to watch for, warning signs that mean call-now, the recheck plan, and emergency contacts — written so a worried owner can actually follow them.

Run a consulting client discovery session — uncover the real problem, scope, and decision process. Use when asked to prepare for a client discovery call, qualify a consulting lead, scope an engagement, or run a kickoff. Produces a discovery plan — the questions that surface the real problem (not the stated one), budget/authority/timeline qualifiers, success criteria, red flags, and a follow-up that leads to a proposal.

Wrap up a client project the right way — a clean handoff, a strong final impression, and the moves that turn a finished project into referrals and repeat work. Use when asked to wrap up a client project, offboard a client, end a client relationship well, or project handoff. Produces a closeout checklist (deliverables, access, final invoice, documentation), a handoff/wrap-up message, the referral/testimonial/repeat-work asks to make at the peak moment, a graceful process for ending an ongoing relationship, and how to leave the door open — so the ending builds your business instead of just stopping.

Build a smooth client-onboarding process that starts projects on the right foot — clear expectations, the info you need, and a professional first impression that prevents problems later. Use when asked to onboard a new client, create an onboarding process, kick off a client project, or client welcome packet. Produces a welcome and kickoff flow, the intake you need to start, expectation-setting on scope/comms/timeline/payment, a kickoff-meeting agenda, and the templates to reuse — so onboarding is consistent, not improvised, and prevents the scope and communication problems that sink projects.

Spot a bad client before you sign — the warning signs of the projects that turn into unpaid, scope-creeping nightmares, and how to screen, price, or decline them. Use when asked is this client a red flag, should I take this client, screening a difficult client, or how to avoid bad clients. Produces a read on the warning signs present (haggling, vagueness, disrespect, urgency, unrealistic expectations), what each predicts, screening questions to ask before committing, protective terms if you proceed anyway, and how to decline gracefully — so you avoid the clients who cost more than they pay.

Assess physical and transition climate risk for a site, product, or portfolio with scenario-based structure. Use when asked to run a climate risk assessment, evaluate physical or transition risk, prepare TCFD/ESRS-style climate risk analysis, or assess how climate scenarios affect an asset or business. Produces a hazard-exposure-vulnerability matrix across 2030/2040/2050 horizons and labelled scenarios, with financial-impact ranges, confidence levels, and adaptation options.

Write a structured clinical case summary or case presentation. Use when asked to write a clinical case summary, case presentation, patient case report, or clinical handover. Produces a structured summary using SBAR or SOAP format. For educational and documentation purposes only — not a substitute for clinical judgement.

Draft a clinical trial protocol synopsis with the elements regulators and IRBs expect. Use when asked to write a clinical trial protocol, a study protocol synopsis, a trial design, or to structure endpoints/eligibility/statistics for an interventional study. Produces a structured protocol synopsis — objectives, design, population with eligibility, interventions, endpoints, statistics, and safety/ethics — for expert review. (For non-clinical/UX research, use research-protocol.)

Turn one long video, podcast, or stream transcript into 8-12 short-form clips — each with a hook line, cut timestamps, captions, and a platform note for TikTok/Reels/Shorts — plus an honesty gate that kills clips that misrepresent the source. Use when someone says 'clip this podcast', 'make shorts from my video', 'what's clippable here', or runs a clipping side hustle. Produces a ranked clip sheet ready for an editor or a clipping app.

Send your position to a meeting instead of your body — a one-page brief carrying your stances, fallbacks, red lines, tradables, and delegation limits, readable by the colleague (or agent) representing you. Use when you can't attend a decision-making meeting, when double-booked, when briefing someone to negotiate for you, or 'what would you need from me to represent me?'. Produces the clone brief plus a 60-second verbal version for the person carrying it.

Decode a mortgage Closing Disclosure line by line — which fees are real, which are shoppable or junk, and what changed since the Loan Estimate. Use when asked to decode my closing disclosure, review my closing costs, why did my costs go up, or which fees can I negotiate. Produces a section-by-section decode, the Loan-Estimate comparison with tolerance flags, the challenge list with scripts, and the cash-to-close verification.

Plan a co-marketing partnership — two brands reaching each other's audiences for mutual gain. Use when asked to plan a partnership, joint campaign, co-branded content/webinar, integration launch, or partner outreach. Produces the partner fit rationale, a fair value exchange, the joint campaign plan, the partner pitch, and how success is split and measured.

Write calm, businesslike co-parenting messages that keep the focus on the kids and stay out of the old conflict — for scheduling, expenses, decisions, and hard topics. Use when asked to write a message to my co-parent, respond to my ex about the kids, co-parenting communication help, or how to reply without a fight. Produces a message drafted in a neutral, child-centered tone (the 'BIFF'-style brief/informative/friendly/firm approach), the bait removed, a clear ask or answer, and a note on documentation — steering away from anything that escalates. Not legal advice.

Make a genuinely good drink from the bottles already on your shelf — no special trip, no 12-ingredient recipe. Use when asked what can I make with [spirits], cocktail from what I have, I've got [bottles] what can I drink, or make me a drink without buying anything. Produces two or three cocktails you can build right now with ratios, a method, sensible substitutions for what you're missing, and a zero-proof version — scaled to how many you're making.

Explain what a piece of code does in plain English, at the depth the reader needs. Use when asked to explain code, walk through a function, understand an unfamiliar snippet, or onboard to a file. Produces a one-line summary, a step-by-step walkthrough, the non-obvious parts called out, and any bugs or smells spotted along the way.

Generate a tailored code review checklist for any pull request based on the language, type of change, and risk level. Use when asked to review code, check a PR, review a pull request, or generate a code review checklist. Produces a focused checklist with language-specific checks, risk-level-appropriate depth, and a clear approve/request-changes recommendation.

Review a pull request or diff like a thoughtful senior engineer — prioritized, kind, and focused on what matters. Use when reviewing code, giving PR feedback, or asked to 'review this change'. Produces a structured review: a correctness/design pass, comments ranked by severity (blocking → nit), what's done well, and a clear approve / request-changes call — feedback that improves the code and the author.

Simplify code that works — remove speculative abstraction, dead flexibility, and needless indirection while keeping behaviour identical and verified. Use after a feature lands ('now simplify it'), when AI-generated code arrives over-engineered, when a file has grown hard to follow, or as the cleanup pass before review. Produces a smaller, flatter version with identical behaviour, plus a ledger of what was removed and why it was safe. For finding bugs use code-review-checklist / ai-code-review — this skill assumes it works and makes it simple.

Structure a cohort analysis for retention, LTV, or behavioural patterns. Use when asked to run a cohort analysis, analyse retention by cohort, segment users by behaviour over time, or calculate lifetime value by acquisition period. Produces a complete cohort analysis framework with methodology, cohort definitions, retention curves, and prioritised interventions.

Fit a retention curve to observed cohort data and project LTV — computed, not estimated. Use when someone has real cohort retention numbers (month 0, 1, 2…) and asks what lifetime value, lifetime periods, or long-run retention they imply, or whether retention is flattening or leaking. Produces a fitted power curve (parameters, R², retention floor), a 24-36 period projection, and a real .xlsx with live formulas where editing ARPU recalculates LTV — via the bundled zero-dependency script.

Write a cold sales/B2B outreach email that earns a reply. Use when asked to write a cold email, a sales outreach email, a prospecting email, or a cold email sequence to a business prospect. Produces a short, personalised email — subject, a relevant opener, one clear value-led ask, and a low-friction CTA — plus 2 follow-ups, written to be replied to, not deleted.

Write cold outreach to potential clients that gets replies — specific, useful, and about them — instead of the templated pitch that gets deleted. Use when asked to write a cold email to a prospect, get clients through outreach, cold pitch help, or reach out to potential customers. Produces a researched, personalized message that leads with their problem, a clear low-friction ask, proof you're credible without bragging, a subject line, and a short follow-up sequence — plus who to target and what to avoid so it lands as a helpful note, not spam.

Start a cross-team project with the collaboration contract that prevents the classic collisions — who decides what, how work flows between teams, the communication channels and cadence, and what done means — agreed before the first collision instead of during it. Use when asked kick off this cross-team project right, our two teams keep colliding, define how we'll work with the other team, or set up the partnership before we start. Produces the one-page contract: decision rights, interfaces, cadence, and the done-definition.

Write a polite-but-firm payment-reminder / collections email sequence for overdue invoices. Use when asked to write a collections email, a payment reminder, a dunning sequence, or to chase an overdue invoice. Produces a staged sequence — gentle pre-due nudge through escalating overdue reminders to a final notice — that stays professional, keeps the relationship intact, and makes paying easy. Not legal advice.

Support a teenager through college applications without taking them over — the parent's actual jobs (logistics, finances, emotional ballast), the ownership lines that keep the application theirs, and the scripts for the hard moments. Use when asked how do I help my kid with college apps, how involved should I be, my teenager won't start their essays, or we disagree about the college list. Produces the role split, the family timeline, the money conversation framework, and the scripts for deadlock, rejection, and the essay you must not write.

Compute what a degree will actually cost — sticker minus real aid, inflated per year, split into cash and loans, with the loan's decade-long monthly tail made visible before enrollment instead of after. Use when asked what will college really cost, compare these two offers' real prices, how much loan payment after graduation, or is this school affordable. Produces the all-in number from the script, the offer-letter decode (grants vs loans untangled), the monthly-tail reality check, and the two-school comparison.

Prepare and rehearse a coming-out conversation, tuned to the specific person and the real risk — what to say, how to open, how to handle the likely reactions, and a safety-first plan if it could go badly. Use when someone says 'I want to come out to my parents/boss/friend', 'help me tell them I'm [gay/trans/bi/etc.]', 'rehearse this conversation with me', or is planning any identity disclosure. Produces an opener, a rehearsal against realistic reactions, and a safety plan. Safety and the user's autonomy come first — it never pushes anyone to come out.

Capture everything an outgoing club secretary, chair, or organizer carries in their head before they disappear — accounts and logins with owners, the annual rhythm calendar, key relationships and their quirks, the unwritten rules, and the first-90-days guide for the successor. Use when a committee member is stepping down, when someone says 'it all lives in Linda's head', or right after elections. Produces a complete handover pack plus the one-hour handover meeting agenda.

Build a community management playbook for a brand's social media channels. Use when asked to create guidelines for managing comments, DMs, and community interactions, define a moderation policy, or build response frameworks for social media community managers. Produces a complete playbook with response templates, escalation paths, moderation rules, and tone guidelines.

Write a fair, enforceable community moderation policy. Use when standing up or overhauling moderation for a forum, Discord, Slack, subreddit, or any user community. Produces a clear code of conduct with examples, a graduated enforcement ladder tied to specific triggers, an appeals process, moderator guidelines, and the handling for the severe cases (threats, doxxing, brigading) that need immediate action. Governs member conduct in a user community — distinct from [[community-management-playbook]], which manages a brand's own social-media channels (comments, DMs, tone, response templates).

Build a candidate's research brief on a company before an application or interview. Use when asked to research a company for a job, prep a company brief before an interview, or understand a prospective employer fast. Produces a one-page brief — what they do & how they make money, recent news & trajectory, product & competitors, likely challenges, culture signals, and smart questions to ask.

Run a company event — the launch party, the customer day, the team celebration — as the operation it is: the goal that shapes every choice, the budget with its forgotten lines, the vendor and venue coordination, the run-of-show with owners, and the day-of roles that keep hosts hosting. Use when asked plan the company event, organize our customer day/holiday party/launch event, what am I forgetting for this event, or be the run-of-show for Thursday. Produces the goal-shaped plan, the budget with the forgotten lines, the run-of-show, and the day-of role card.

Build a comparative market analysis (CMA) to price a property. Use when asked to do a CMA, a comparative market analysis, price a home, or estimate a property's value from comparables. Produces a structured CMA — the subject property, selected comparables with adjustments, an estimated value range, market context, and a pricing recommendation with rationale — for a real-estate professional to review. Not a formal appraisal.

Analyze competitors and create competitive landscape documentation with feature matrices, positioning maps, and strategic recommendations. Use when asked to analyze competitors, create competitive analysis, compare features with competitors, build a competitive landscape, track competitive positioning, or prepare sales battlecard inputs. Produces structured competitor profiles, feature comparison matrix, win/loss analysis, and prioritised strategic recommendations. For a one-off teardown of a single rival use competitor-teardown; for a recurring market briefing use competitive-intelligence-monitor.

Monitor competitor signals and surface strategic implications for your roadmap. Use when asked to monitor competitors, track the competitive landscape, produce a competitive briefing, or understand what has changed in the market this week or month. Produces a structured intelligence brief with high/medium/low priority signals, roadmap implications, and a strategic landscape summary. For a single competitor announcement use competitor-signal-tracker; for a one-off deep dive use competitor-teardown.

Run a fast, honest competitive scan — the dimension table built from public evidence (sites, docs, pricing pages, changelogs, reviews), the claims-vs-observed discipline, and the so-what synthesis that ends in moves, not a landscape mural. Use when asked what are competitors doing, quick scan of these three rivals, how does our pricing/feature set compare, or prep the competitive slide honestly. Produces the evidence-based comparison table, the marketing-vs-reality flags, the so-what synthesis, and the staleness date.

Analyse competitor moves and translate them into strategic implications for your product roadmap. Use when a competitor announces a new feature, pricing change, partnership, or strategic shift, or when producing a periodic competitive intelligence report. Produces a categorised signal analysis with reactive-vs-proactive assessment, threat ratings, specific roadmap implications, and recommended responses with owners. For a recurring whole-market briefing use competitive-intelligence-monitor instead.

Produce a structured competitive analysis for any product or market. Use when asked for a competitor analysis, competitive teardown, market comparison, SWOT, or positioning map. Generates a structured teardown with positioning map, feature comparison, messaging gaps, and strategic recommendations. For a full landscape doc with feature matrix and win/loss analysis use competitive-analysis instead.

Write a firm, effective complaint letter that gets a resolution. Use when asked to write a complaint letter, complain to a company about a product/service, escalate poor service, or demand a refund/replacement. Produces a structured complaint — the facts, the impact, the specific resolution you want, and a deadline — in a firm, professional tone that's hard to ignore and easy to act on.

Generate a prioritised compliance checklist for GDPR, SOC 2, ISO 27001, FCA, HIPAA, or other frameworks with a gap analysis. Use when asked for a compliance checklist, gap analysis, readiness assessment, or audit preparation for any regulatory framework. Produces a structured checklist with prioritised gaps, quick wins, and evidence requirements. Optimised for Opus 4.7 and newer models. Not a substitute for legal or compliance professional advice.

Make compound growth actually click — see how small, consistent amounts become large over time, and why starting now beats starting bigger later. Use when asked explain compound interest, how does compounding work, is it worth investing small amounts, or why should I start now. Produces an intuitive explanation of compounding with concrete illustrative examples for your situation, the outsized effect of time (why an early start beats a later larger one), how fees and inflation eat into it, and the honest caveats — turning an abstract concept into the motivation to start now. Educational, not financial advice.

Write a sincere condolence or sympathy message when someone has died or a friend is grieving — warm, personal, and free of the clichés that hurt more than help. Use when asked what to say when someone dies, write a sympathy/condolence message, my friend lost their [person], or I don't know what to say. Produces a heartfelt message tuned to your relationship and the situation, drawn from a specific memory or quality where possible, an honest acknowledgment (not toxic-positive platitudes), an offer of concrete support, and guidance on what to avoid saying.

Write a conference talk proposal / CFP submission for a tech or developer conference. Use when asked to submit to a CFP, propose a talk, or write a session abstract. Produces a compelling title, abstract, audience takeaways, an outline, and the speaker pitch — tuned to what selection committees actually look for.

Calm a heated conflict — in person or in writing — before it does damage, by lowering the temperature instead of winning the point. Use when asked help me de-escalate this, this argument is getting heated, calm this situation down, or how do I respond without making it worse. Produces a read on what's actually driving the heat (often an unmet need under the surface argument), the de-escalation moves (acknowledge, slow down, find the shared ground), what to say and what to avoid, and how to steer toward resolution once the temperature drops — because you can't solve anything while everyone's activated.

Write a consulting proposal that wins the engagement — outcomes over hours. Use when asked to write a consulting proposal, a project proposal, a pitch for a client engagement, or to respond to an RFP. Produces a proposal — the client's problem in their words, your approach & deliverables, outcomes/value, timeline & phases, investment with options, and why-you — framed around results, not a task list. Ready to export as a designed PDF.

Generate a structured content calendar for any brand, product, or creator. Use when asked for a content plan, editorial calendar, social media schedule, or weekly/monthly content strategy. Produces a calendar with topics, formats, channels, and copy hooks.

Turn one piece of content into a full multi-platform pack — X/Twitter thread, LinkedIn post, newsletter section, Instagram carousel, and a short-form video script — each rewritten natively for its platform, not copy-pasted. Use when asked to repurpose content, atomize a blog post or video, turn one idea into many posts, or get more mileage from a piece. Produces ready-to-post drafts per platform with hooks, formatting, and CTAs tuned to each.

Create a content style guide / voice & tone guide so everyone writes consistently. Use when asked to write a content style guide, a voice and tone guide, editorial guidelines, or UX-writing standards. Produces a usable guide — voice principles with do/don't examples, tone-by-context, mechanics (grammar, capitalisation, formatting), terminology/word list, and accessibility/inclusivity rules — that a team can actually apply.

Declare bankruptcy on a long-lived AI agent's accumulated memory — audit what it currently believes, separate ground truth from stale and wrong, purge deliberately, restate the truths that survive, and log what was lost. Use when an agent keeps acting on outdated facts, contradicts itself across sessions, 'remembers' things wrong, or after a reorg/pivot makes its worldview obsolete. Produces a belief audit, a keep/correct/purge ledger, a restated ground-truth file, and the bankruptcy record.

Plan a session's context window like the budget it is — what loads up front, what gets linked instead, what stays fetch-on-demand, and how to keep the stable prefix cache-friendly so repeated turns cost cents instead of dollars. Use when asked my agent keeps blowing its context, plan what to load into the session, why is every turn so expensive, or design the context for this workflow. Produces the load/link/fetch allocation, the cache-aware prefix layout, the per-turn cost shape, and the eviction rules for when the window fills anyway.

Compress tool outputs, logs, and JSON before they enter the context window — structural compression via a deterministic stdlib script (schema + samples + stats instead of 300 raw rows), no API, no summarization loss. Use when asked shrink this tool output, my context is full of JSON, compress these logs before analysis, or stop wasting tokens on raw data. Produces the crushed artifact with its token math shown, the crush-or-keep decision rules, and the fetch-the-original escape hatch.

Review what an LLM feature or agent actually puts in its context window — and find what's bloating, missing, or fighting itself. Use when asked to review a system prompt and context assembly, cut token usage without losing quality, debug an agent that ignores instructions, or audit how retrieval results, history, and tool definitions are packed into the window. Produces a context inventory with a keep/cut/restructure verdict per component, ordering and caching fixes, and a token budget. For wording-level prompt tuning use prompt-optimizer.

Keep Claude Code sessions productive across resets with output filtering, session logging, and auto-resume. Use when starting a long or complex coding session, when previous sessions lost context mid-task, or when you need Claude to resume exactly where it left off after a reset. Produces a session.log at the project root, filtered command output that preserves context, and automatic resume of in-progress tasks after any reset.

Treat context switches as the budget line they are — the switch census (how fragmented the week really is), the batching moves that consolidate scattered same-kind work, the calendar defrag that turns Swiss cheese into slabs, and the switch-cost line for saying no. Use when asked my day is fragmented to death, count my context switches, batch my meetings and reviews, or defend against calendar Swiss cheese. Produces the fragmentation census, the batching plan, the defrag moves, and the protective phrases.

Reconstruct where you were and what's next after an interruption, so a broken focus doesn't cost you the whole thread. Use when asked where was I, I got interrupted and lost my place, help me pick back up, or I forgot what I was doing. Produces a quick rebuild of the task's state from what you remember (what you'd done, what you were mid-thought on), the single next action to re-enter it, and a 'breadcrumb' habit for next time — cutting the expensive re-immersion cost that interruptions inflict, especially on ADHD brains.

Scan a contract you're about to sign in plain language — surface the clauses that could bite you, what they mean, and what to question or renegotiate. Use when asked to check this contract before I sign, what am I agreeing to, are there red flags in this agreement, or explain this contract's risky bits. Produces a plain-English flag list of the risky/unusual clauses (auto-renewal, lock-in, liability, IP, termination, fees), what each means for you, questions to ask, and suggested changes — flagging when it's important enough for a lawyer. Not legal advice.

Never get auto-renewed into another year again — the contract inventory with the dates that matter (notice deadlines, not renewal dates), the calendar system with decision-time buffers, and the renewal-decision ritual that renegotiates instead of rubber-stamping. Use when asked track our contracts and renewals, we got auto-renewed again, when do we have to decide on this vendor, or set up renewal management. Produces the inventory with notice-deadline math, the alert system, the renewal-decision checklist, and the negotiation-window playbook.

Review and summarise any contract or legal agreement. Use when asked to review a contract, check an agreement, flag legal risks, or summarise key clauses. Produces a structured review with key terms, flagged clauses, risk rating, and plain English summary. Not a substitute for qualified legal advice.

Handle a dispute with a contractor — unfinished work, poor quality, overcharging, or a no-show — with a path that protects your money and your options. Use when asked to deal with a contractor dispute, my contractor did bad work / won't finish / overcharged, or how to get a builder to fix their work. Produces a read on your position (contract, payments, evidence), a firm-but-professional communication and demand path, documentation and payment-leverage guidance, and escalation options (mediation, licensing board, chargeback, small claims) — flagging that it's not legal advice.

Write a CONTRIBUTING guide that helps people contribute to an open-source project without friction. Use when asked to write a CONTRIBUTING.md, set up contribution guidelines, or make a repo welcoming to contributors. Produces a clear guide: how to set up, the contribution workflow, standards, PR expectations, and how to get help — lowering the barrier to a first PR.

Audit a landing page or funnel step and produce a prioritised CRO test plan. Use when asked to improve conversion rate, audit a landing/signup/checkout page, reduce funnel drop-off, or plan A/B tests for a page. Produces a CRO plan — a heuristic conversion audit, the diagnosed friction, prioritised test hypotheses (ICE), test designs with sample-size math, and the measurement guardrails.

Build a beginner running plan from wherever you are to a real goal — first nonstop mile, 5K, or 10K — that builds up slowly enough to avoid injury. Use when asked for a couch to 5k plan, help me start running, train for a [distance], or a running plan for beginners. Produces a week-by-week walk/run progression to the goal, session detail, pacing and form basics, rest and cross-training, and an injury-prevention note — with a 'check with a doctor if you have health conditions' flag.

Decode a counteroffer after you resign — what the raise, promotion promise, or title bump really signals, the statistics-informed risks of staying, and a clear-eyed decision framework. Use when asked my company countered my resignation, should I accept a counteroffer, they offered me more to stay, or decode this retention offer. Produces a component-by-component decode with 🔴🟡🟢 severity, the questions that expose which promises are real, and the stay/go decision sheet.

Write a specific, non-generic cover letter that connects your evidence to the role. Use when asked to write a cover letter, an application letter, or a note to accompany a resume. Produces a tight 3–4 paragraph letter — a real hook, two evidence paragraphs mapping your proof to the job's needs, and a confident close — tailored to the company, ready to export as a designed PDF.

Map an organisation's risks against its insurance policy portfolio to find what's uncovered, underinsured, or double-covered. Use when asked to run a coverage gap analysis, review an insurance programme against a risk register, check what risks aren't insured, or audit a policy portfolio. Produces a risk-by-coverage matrix, flagged gaps and overlaps, a deductible stack review, and recommendations ranked by expected-loss severity.

Define a creator's brand foundation — niche, audience, positioning, content pillars, voice/tone, and bio — so every post is consistent and on-brand. Use when asked to define a creator brand, find a niche, set content pillars, write a voice guide, craft a bio, or build a brand kit for a personal brand or channel. Produces a reusable one-page brand kit that other content skills can read so output sounds like you, every time.

Decode a brand deal or UGC contract before signing — usage rights, exclusivity windows, whitelisting, payment terms, and kill clauses ranked 🔴🟡🟢 by what they can cost a creator, plus the counter-ask email. Use when a creator says 'is this brand deal fair', 'what does perpetual usage mean', 'they sent me a contract', or 'should I sign this collab agreement'. Produces a clause-by-clause decode, a money-math check on the rate, and a ready-to-send negotiation email. Not legal advice.

Build a creator's sponsorship media kit and brand-deal outreach — the one-pager brands ask for, plus a pitch email and a rate card. Use when asked to make a media kit, pitch a brand, land a sponsorship, write a brand-deal email, or set creator rates. Produces a structured media kit (audience, stats, offerings, past work), a personalised outreach email, and a defensible rate card. The creator side of a sponsorship — distinct from a brand briefing a creator.

Get foreign qualifications, degrees, or professional licenses recognised in a new country — figure out whether recognition is even needed, which body assesses it, what evidence they want, and the bridging route if there's a gap. Use when someone says 'get my degree recognised abroad', 'is my foreign license valid here', 'credential evaluation', or 'can I work as a [nurse/engineer/teacher] in [country] with my qualifications'. Produces a recognition roadmap, the assessing body, an evidence checklist, and the bridging options. Routes to official assessment bodies; requirements are country- and profession-specific.

Build a credit history from zero in a new country — understand that credit doesn't transfer across borders, get the first products that report, avoid the newcomer traps, and reach a usable score in months not years. Use when someone says 'I have no credit history in [country]', 'build credit as a newcomer/immigrant', 'why was I rejected with a great score back home', or 'how do I get a credit card/loan as a new arrival'. Produces a credit-building plan, the starter products that report, a timeline, and the traps to avoid. Educational, not financial advice; routes to official credit sources.

Write a credit memo for a lending decision: borrower story, facility structure, repayment sources, financial-ratio spread with covenant headroom, risk factors with mitigants, risk-rating rationale, and a recommendation. Use when asked to write a credit memo, credit application, credit paper, loan write-up, or prepare a deal for credit committee. Produces a complete credit memo ready for committee review.

Stress-test a decision or claim through a sharp, fair Q&A — the questions a good lawyer or skeptical friend would ask before you commit. Use when asked to cross-examine me, ask me hard questions about this, interrogate my plan, or make me defend this. Produces a sequenced line of probing questions (from clarifying to challenging to the killer question), space to answer, and a debrief on where your answers were strong, evasive, or exposed a gap — so weaknesses surface in private before they surface in public.

Fetch live cryptocurrency prices with zero API keys — CoinGecko's public endpoints primary, Coinbase spot fallback, via plain curl. Use when asked what's bitcoin at, ETH price in euros, how's the crypto market today, or price of some altcoin. Produces the current price with 24h context, the source and timestamp, the rerunnable command, and the volatility caveat that crypto answers must carry.

Write a structured escalation brief for an at-risk customer account. Use when an account has escalated, when a customer is threatening churn, when a P1 customer issue needs executive attention, or when preparing an internal save play. Produces a crisp escalation brief with account context, timeline, root cause, business impact, and a clear resolution plan.

Build a customer health scorecard for a specific account. Use when asked to score account health, assess renewal risk, build a health dashboard, or evaluate an account's likelihood to renew or expand. Produces a structured health scorecard with a RAG status, dimension scores, key risks, and recommended actions.

Analyse CSAT / NPS / CES survey results and turn the score into actions. Use when asked to analyse NPS, CSAT, or CES data, compute an NPS score, interpret survey verbatims, or build a voice-of-customer readout. Produces a readout — the computed score, the trend & benchmark, themed analysis of the comments (what drives promoters vs. detractors), and prioritised actions. Includes a stdlib NPS/CSAT calculator.

Convert currencies and fetch live exchange rates with zero API keys — Frankfurter (ECB rates) primary, open.er-api.com fallback, via plain curl. Use when asked convert 500 dollars to euros, what's the USD-INR rate, how much is this in my currency, or historical exchange rate for a date. Produces the conversion with the rate and its date quoted, the rerunnable command, and the not-a-trading-quote caveat.

Plan and run a customer advisory board (CAB). Use when asked to design a customer advisory board, plan a CAB meeting agenda, choose CAB members, or write CAB invitations and follow-ups. Produces a CAB program plan — objectives, member selection criteria, a meeting agenda, discussion guides, roles, logistics, and a follow-up and value-capture plan.

Write the customer-facing incident update during an outage — status-page post or email — that's honest about impact without over-promising. Use when asked to write a status page update, draft customer comms for an outage, post an incident notice, or tell customers about downtime. Produces the update in the right tense for the incident stage (investigating / identified / monitoring / resolved), with impact scope, any workaround, and a concrete next-update time. Distinct from incident-postmortem (the internal retro).

Build a customer journey map for a product, service, or experience. Use when asked to map a customer journey, create a user journey, document touchpoints and pain points, or design an experience map. Produces a complete journey map with stages, touchpoints, emotions, pain points, and prioritised opportunities.

Write clear customer-facing outage and service-disruption notifications. Use when asked to write an outage notice, a status-page update, a service-disruption email, a maintenance notice, or an incident update sequence. Produces status-page updates for each phase (investigating → identified → monitoring → resolved), a customer email, and a resolved/post-incident summary, in plain, reassuring language.

Build a joint customer success plan for a specific account. Use when asked to create a success plan, joint success plan, mutual action plan, or customer onboarding plan. Produces a structured success plan with business goals, milestones, success metrics, ownership, and a 90-180 day roadmap.

Convert a business question into a complete dashboard specification. Use when asked to design a dashboard, create a dashboard spec or brief, plan a BI report, or define what charts and metrics a dashboard should include. Produces a structured spec with metrics, dimensions, chart types, filters, and layout guidance.

Structure a product data analysis, metric deep-dive, funnel analysis, or cohort study. Use when asked to analyse product metrics, investigate a drop in conversion, explain a data change to stakeholders, or find the root cause of a metric movement. Produces a structured analysis with question, root cause, confidence level, and recommended action.

Respond to your data being breached — triage by what actually leaked, the freeze/rotate/monitor ladder in the right order, and the calibrated watchfulness that follows, without panic or paralysis. Use when someone asks my data was in a breach what do I do, I got a breach notification letter, my SSN/ID number leaked, or should I freeze my credit. Produces the leaked-data triage, the ordered response ladder with the do-today items, the monitoring plan, and the breach-letter decode (including what the free credit monitoring offer is and isn't).

Get your personal info off people-search and data-broker sites — a prioritized opt-out plan that targets the sites that matter and keeps them from reappearing. Use when asked to remove my info from the internet, opt out of data brokers, my address/phone is on people-search sites, or reduce my digital footprint. Produces a prioritized target list (the high-traffic brokers first), the opt-out method for each, a suppression-at-source plan so data stops flowing back, a recheck cadence, and safe-handling cautions for the personal data you'll be submitting.

Clean a messy dataset methodically — the profiling pass that finds what's actually wrong (dupes, format drift, phantom spaces, mixed types), the fix order that doesn't corrupt while correcting, and the log that makes the cleaning defensible. Use when asked clean this export, why is my pivot double-counting, these names don't match between sheets, or prep this data for analysis. Produces the profile of what's wrong, the ordered cleaning plan, the join-key repairs, and the cleaning log.

Define a data contract between a producer and consumers of a dataset/event/API. Use when asked to write a data contract, define a schema agreement, set data SLAs, or stop a producer from silently breaking downstream consumers. Produces a contract — schema with types & constraints, semantics, quality SLAs (freshness/completeness/validity), ownership, versioning & breaking-change policy, and a change process.

Design an ETL/ELT data pipeline specification. Use when asked to design a data pipeline, spec an ETL or ELT process, document a data ingestion workflow, or plan a data integration. Produces a complete pipeline spec with sources, transforms, destinations, SLAs, error handling, and data quality rules.

Audit a dataset for the quality problems that silently break analysis — missingness, duplicates, outliers, type and range errors, consistency, and freshness — and produce a prioritised fix list. Use when asked to assess data quality, audit a dataset, check data before analysis, or explain why numbers look off. Produces a structured quality report across the standard dimensions, the specific issues found (with the checks to run), severity, and how to fix each.

Design the data quality checks for a table or pipeline across the standard dimensions. Use when asked to add data quality tests, define DQ checks, catch bad data before it hits dashboards, or set up monitoring for a dataset. Produces a checks plan across completeness, validity, uniqueness, freshness, consistency, and accuracy — each with the rule, severity, and where it runs (dbt test / Great Expectations / SQL assertion).

Build a data retention and deletion schedule grounded in legal basis. Use when asked to create a data retention policy, set retention periods, plan data deletion/minimisation, or answer 'how long can we keep this data?'. Produces a retention schedule — data categories with their retention period, legal/business basis, deletion trigger and method, plus flags for data kept with no basis or no defined period.

Design slides where the data makes the argument — the takeaway-titled chart, the one-chart-per-slide rule, the annotation layer that guides the eye to the point, and the honesty pass on projected data. Use when asked make this data slide land, my chart slide confuses people, how do I present these numbers, or the audience missed the point of my graph. Produces the redesigned slide: takeaway title, the chart stripped and annotated, the eye-path check, and the honesty audit.

Write a safe, zero-downtime database migration plan for a schema change. Use when asked to plan a database migration, design a zero-downtime schema change, document an expand/contract migration, produce a rollback procedure for a database change, or coordinate a database schema update with a deployment. Produces a structured migration plan covering migration objectives, backward compatibility analysis, expand/contract phase breakdown, exact SQL, rollback steps per phase, data validation queries, and a deployment runbook.

Document or design a database schema with entity relationships, table definitions, constraints, indexes, and access patterns. Use when asked to design a database, document an existing schema, model entities and relationships, define table structures, plan an index strategy, or produce a data model for review. Produces a structured schema document covering an ER diagram, table DDL definitions, index strategy, access pattern analysis, normalization decisions, and migration notes.

Document a dataset so others know what it is, how it was made, and when not to use it. Use when asked to write a datasheet for a dataset, document training/eval data, or assess whether a dataset is fit for a use. Produces a datasheet — motivation, composition, collection process, preprocessing, recommended uses & limits, distribution, and maintenance.

Rewrite a dating profile so it sounds like you on a good day — mined from how you actually talk, specific instead of generic, with photo order feedback and first-message craft — under one hard rule: nothing you can't back up in person. Use when someone says 'fix my dating profile', 'why am I getting no matches', 'what do I say first', or 'roast my Hinge prompts'. Produces rewritten bio and prompts, a photo lineup critique, and three first-message templates that reference, not flatter.

Run the real math on a parent leaving work versus paying for childcare — the second income net of daycare, marginal taxes, and work costs, AND the career-trajectory cost of years out, over horizons instead of one brutal year. Use when asked does it make sense for me to keep working, daycare costs my whole salary, stay-home vs daycare math, or what does leaving work for 5 years really cost. Produces both sides of the ledger from the script, the horizon comparison, and the decision sheet that lets the non-financials vote.

Spec a dbt model — its grain, sources, transformations, tests, and materialization. Use when asked to design a dbt model, plan a data transformation, write a staging/intermediate/mart model spec, or define dbt tests for a table. Produces a model spec — purpose & grain, lineage (sources → refs), the transformation logic, column definitions, dbt tests, materialization choice, and the skeleton SQL/YAML.

Respond to a debt collector correctly — know your rights, make them prove the debt, and avoid the mistakes that reset the clock or admit liability. Use when asked how to deal with a debt collector, a collection agency is contacting me, is this debt real, or respond to a collections letter. Produces a validation/proof-of-debt request, a rights-aware read on what collectors can and can't do, guidance on statute-of-limitations and not accidentally restarting it, a communication and record-keeping plan, and escalation if they break the rules. Not legal advice.

Handle debt collectors without getting bullied or tricked — what to say, what never to say, and the rights that protect you from harassment and illegal tactics. Use when asked how do I deal with debt collectors, a collector keeps calling, can they do this, or how to respond to a collection notice. Produces ready scripts (request written validation, dispute, cease-contact, set boundaries), the phrases that accidentally restart the clock or admit the debt (and to avoid them), your rights under fair-debt-collection rules (harassment limits, validation, what's illegal), how to check the debt is real and yours, and safe next options — so you deal from a position of rights, not fear. Not legal advice; points to consumer-protection agencies and legal aid.

Build a debt payoff plan — avalanche vs snowball simulated month by month on your actual debts, the real payoff dates, and the psychology-vs-arithmetic tradeoff priced in dollars. Use when asked how do I pay off my debts, avalanche or snowball, make me a debt payoff plan, or when will I be debt-free. Produces the month-by-month comparison from the script, the payoff order with dates, the interest cost of choosing morale over math, and the plan-survival rules.

Build a debt-payoff plan across multiple debts using the avalanche or snowball method. Use when asked to pay off debt, tackle credit cards/loans, or choose between avalanche and snowball. Produces an ordered payoff schedule, the total interest and time for each method, and a clear recommendation. Educational, not regulated financial advice.

Parse error logs, stack traces, and crash reports into a structured root cause diagnosis. Use when an application is throwing exceptions, crashing, or producing unexpected errors and you need to understand why and what to fix. Produces a structured diagnosis with error classification, stack trace walkthrough, probable root cause with confidence level, affected code path, a concrete code-level fix suggestion, and ordered next debugging steps.

Judge a past decision by its PROCESS, not its outcome — because good decisions lose and bad decisions win, and teams that can't tell the difference learn the wrong lessons. Use when reviewing a big call after the fact (a bet that failed, a pass that haunts, a hire, a pivot) and the room is about to conclude 'it failed so it was wrong.' Produces a process-forensics report: what was knowable then, the quality grade of the decision as-made, the luck accounting, and the ONE process change worth keeping.

Reconstruct the decision actually made in a messy Slack, email, or meeting thread into a proper decision record — commitments named, silent assumptions surfaced, non-decisions called out. Use when asked what did we actually decide, turn this thread into a decision record, who committed to what, or reconstruct this discussion. Produces a decision record with quoted evidence, a commitments table, reconstructed assumptions, dismissed options, and a confidence note on the reconstruction itself.

Help me decide between options with a weighted pros/cons that actually reaches a recommendation — not just two lists. Use when asked should I take job A or B, which one should I buy, help me decide, or make a pro/con list. Produces the criteria that matter (weighted by what you care about), the options scored against them, a clear recommendation with its confidence, and the single question that would flip the decision if you're still torn.

Record decisions the way good judgment compounds — the reasoning, the alternatives, the probabilities, and what would change your mind, written down BEFORE the outcome arrives, then reviewed against reality. Use when asked help me think through this decision, start a decision journal, review my past decision, or why do I keep making the same mistake. Produces the pre-registered decision entry, the review-date trigger, and the outcome review that separates bad luck from bad process.

Set up the team decision log that ends relitigation — the one-line-per-decision format (what, why, who, when, reopening rule), the capture moments wired into existing rituals, and the lookup habit that makes it pay. Use when asked set up a decision log, we keep re-deciding the same things, where do decisions get recorded, or new people keep asking why we do X. Produces the log format, the capture wiring, the reopening rule, and the retrieval habits.

Run meetings that actually decide — the pre-read-then-decide format, the options-on-the-table rule, the decider named before debate starts, and the recorded-or-it-didn't-happen close. Use when asked run this decision meeting, we discuss forever and never decide, structure the meeting where we pick the vendor/plan/design, or why do our decisions get relitigated. Produces the meeting design: pre-read, the in-room sequence, the decision rule, and the recording that makes it stick.

Write a crisp decision memo that drives a clear decision, not a discussion. Use when asked to write a decision memo, a recommendation memo, a one/six-pager for a decision, or to get leadership to decide something. Produces a decision memo — the decision & recommendation up front, the context, options with trade-offs, what you'd need to believe, risks, and the explicit ask with a deadline.

Run a decision past a panel of clashing advisors — an optimist, a pessimist, a numbers person, an ethicist, and future-you — then get a chair's verdict. Use when asked to help me decide, weigh this decision, what should I do about, or run this by different advisors. Produces each advisor's honest take on the decision (each committed to their lens), where they disagree most, the question that would break the tie, and a chair's recommendation that weighs the panel — turning a lonely choice into a structured board meeting.

Make a decent decision when you're too depleted to think well — a low-energy protocol that protects you from bad tired-brain choices. Use when asked I'm too tired to decide, help me choose I'm exhausted, I can't think straight right now, or should I even decide this now. Produces a first check on whether this decision can simply wait until you're rested, and if not, a minimal-effort path to a safe-enough choice (default to reversible, avoid the tired-brain traps, use a simple rule) — because decisions made depleted are predictably worse, and the best move is often not to make them now.

Autopsy a slide deck from photos or screenshots of its slides — the narrative arc, the numbers, and what each slide is hiding. Use when given slide images (a competitor's pitch, a conference talk, your own deck before a big meeting) and asked what the deck argues, whether it holds up, or how to counter or improve it. Produces a slide-by-slide read, the reconstructed argument chain, weak links, and the questions the deck is engineered to avoid. Requires image input.

Turn the user's REAL doc into a slide deck — open the source, structure the narrative, and build the actual .pptx — not slide-writing tips. Use when asked to make a deck from this doc, turn my brief into slides, build the presentation from my Drive doc, or deckify this in Cowork. Reads the document via the Google Drive/Docs connector, maps it to a one-idea-per-slide narrative, and produces a real presentation artifact (.pptx) with speaker notes plus a slide-by-slide outline.

Give a deck a spine the room can follow — the situation-complication-resolution arc, the tension that makes the recommendation feel necessary, the transitions that carry the thread between slides, and the arc-check that catches sag. Use when asked make this deck flow, my presentation feels like disconnected slides, structure the story of this pitch/readout, or the room got lost in the middle. Produces the arc mapping, the tension line, the transition script, and the sag diagnosis.

Outline a deck as headline sentences before opening the slide tool — each slide a claim that reads as an argument top to bottom, the audience-and-ask header, and the skim test that catches broken decks while they're still bullet points. Use when asked start this presentation, structure my deck, why does my deck feel like a data tour, or get sign-off before I build slides. Produces the headline outline, the per-slide evidence notes, the skim test result, and the build rules.

Review a deck against a rubric instead of taste — the five dimensions (argument, evidence, density, arc, honesty), the severity-sorted feedback that separates broken from suboptimal, and the review conversation that improves the deck without rewriting it in the reviewer's voice. Use when asked review my deck, give feedback on this presentation, is this ready for the board, or our deck reviews are just font opinions. Produces the rubric scores with evidence, the severity-sorted feedback, the two-fixes-that-matter-most call, and the reviewer discipline notes.

Declutter a room (or a whole home) with a plan that actually finishes — a sensible order, quick decision rules, and a way to keep it from creeping back. Use when asked how to declutter, help me declutter my [room], I'm overwhelmed by clutter, or a decluttering plan. Produces a room-by-room order, a decision framework for keep/donate/sell/toss, time-boxed sessions sized to your energy, where to route the outflow, and habits to stop the clutter returning — without demanding you become a minimalist or do it all in one heroic weekend.

Protect focus time that actually survives the week — the block placement matched to real energy hours, the defense rules (what moves a block, what never), the entry ritual that beats the blank-stare start, and the honest sizing that stops 8-hour fantasy blocks. Use when asked block focus time that keeps getting eaten, when should I schedule deep work, my calendar has no room to think, or I block time and then waste it. Produces the block design, the defense tiers, the entry ritual, and the meeting-culture negotiation.

Run a tabletop drill of a voice-clone or deepfake fraud attempt — the 'CEO needs this wire today' call — against your actual approval process, before a real attacker does, then debrief the tells and fix the process gap. Use when someone asks to train the team on deepfake fraud, test wire-transfer controls, run a social-engineering tabletop, or 'could we get CEO-frauded?'. Produces a drill scenario pack, a facilitator script, a tells checklist, and the process fixes the drill exposed. Defensive training only.

Respond to false, damaging statements about you or your business — decide what actually counts as defamation, preserve evidence, and choose the right response from correction to takedown to legal action. Use when asked someone posted lies about me, respond to a false review/statement, is this defamation, or protect my reputation online. Produces a read on whether it likely crosses from opinion into actionable falsehood, evidence-preservation steps, a tiered response (platform report, correction/retraction request, cease-and-desist, legal), and a caution against reactions that make it worse. Not legal advice.

Draft a construction delay notice or delay claim letter with contract clause citation, cause classification, and critical-path impact narrative. Use when asked to write a delay notice, put the owner or GC on notice of delay, draft a time extension request, respond to weather or owner-caused delay, or paper a delay for a claim. Produces a notice/claim letter with the excusable-compensable classification, critical-path impact narrative, quantum placeholder, reservation of rights, and a records-preservation list.

Decide what in your workload to hand to AI and what to keep yourself — like managing a fast, capable, but unreliable new hire — so you get leverage without offloading the things that need you. Use when asked what should I delegate to AI, what can AI take off my plate, where should I use AI in my work, or what should I keep doing myself. Produces a sort of your tasks into delegate-fully / delegate-with-review / keep-human, the reasoning behind each line, how to brief the AI on the delegated ones, and where your judgment is the actual value — a delegation map that frees your time without giving away your edge.

Delegate so the work comes back right the first time — the brief that transfers outcome, context, and constraints (not just the task), the autonomy level stated explicitly, and the check-in design that catches drift without hovering. Use when asked hand this off properly, my delegations come back wrong, write a brief for this task I'm giving away, or how much detail do I give. Produces the delegation brief with the outcome and guardrails, the autonomy level, the check-in points, and the questions-welcome contract.

Design deliberate practice that actually builds a skill — targeted, effortful, feedback-driven — instead of mindless repetition that just entrenches your current level. Use when asked how do I practice X effectively, my practice isn't working, design a practice routine, or deliberate practice for. Produces a breakdown of the skill into trainable sub-skills, drills that target your specific weaknesses at the edge of your ability, a feedback mechanism, and a session structure — because time spent practicing is not the same as time spent improving.

Make a recurring brief report what changed since the last edition instead of restating everything. Use when a weekly or monthly report keeps repeating itself, when setting up a scheduled monitor or digest, or when asked to make a recurring update delta-aware. Produces a changes-first brief plus the state record the next run will diff against.

Interrogate a demand forecast before the business commits supply and inventory to it. Use when asked to review a demand plan, challenge a forecast, check forecast accuracy, decompose baseline vs uplift, or find hockey sticks in the numbers. Produces a forecast credibility review with baseline/uplift decomposition, MAPE and bias history, hockey-stick flags, an assumption register, and consensus-vs-statistical divergence analysis.

Draft a firm, professional demand letter that states the facts, the legal/contractual basis, the specific demand, and a deadline. Use when asked to write a demand letter, send a formal demand for payment, draft a cease-and-desist, or formally request resolution before legal action. Produces a structured, factual letter with a clear ask and consequences — assertive but not threatening or defamatory. Not legal advice; have counsel review before sending.

Script a product demo that lands — the audience's-workflow storyline (their day, not your feature list), the golden path rehearsed with fallbacks, the wow moment placed early, and the demo-death contingencies (the backup video, the reset state, the narration bridge). Use when asked script our product demo, demo this to a customer/exec, our demos meander through features, or the demo broke live last time. Produces the demo storyline, the click-path script with fallbacks, the wow placement, and the contingency kit.

Audits project dependencies for security vulnerabilities, license compliance issues, outdated packages, and transitive dependency risk. Use when asked to audit dependencies, review package security, check license compliance, assess dependency health, or produce a vulnerability report. Produces a vulnerability findings table, license compliance matrix, update priority matrix, dependency health score, and 30-day remediation plan.

Honestly measure how dependent you've become on a tool, app, substance-free habit, or even AI itself — and reclaim the capability you've outsourced. Use when asked am I too reliant on, help me check my dependence on, could I function without, or I feel like I can't do anything without X. Produces a candid read on where the reliance actually is, a low-stakes test to measure it (go without, briefly), what capability has atrophied, and a plan to rebuild the muscle — because unmeasured dependence is the dangerous kind, and the fix starts with noticing.

Resolve a dependency or version conflict (npm, pip, yarn, pnpm, Maven, Go modules) step by step. Use when an install fails with peer-dependency or version-conflict errors, packages won't co-exist, or a lockfile is fighting you. Produces the conflict explained, the resolution options ranked by safety, exact commands, and how to keep it from recurring.

Plan the communications for deprecating a product, API, endpoint, or feature that customers depend on. Use when winding down or sunsetting something, planning a breaking change, or migrating customers off a legacy path. Produces a staged timeline with grace periods, tiered customer messaging, a migration-guide outline, the channel plan, and an internal escalation playbook for the highest-risk accounts. This is the customer-communications program — distinct from [[feature-sunset-plan]] (the kill decision, data handling, and code removal) and [[api-versioning-strategy]] (the technical versioning mechanics).

Give structured, constructive feedback on any design using UX frameworks. Use when asked to critique a design, review a UI, give feedback on a Figma file or wireframe, assess a user flow, or evaluate a design against UX principles. Produces actionable critique applying Jobs-to-be-Done, Gestalt principles, and usability heuristics, with prioritised issues and specific recommendations.

Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context, success criteria, constraints, edge cases, and out-of-scope boundaries.

Audit a design system for consistency, coverage, and quality. Use when asked to audit a design system, review a component library, assess design token coverage, or evaluate the health of a shared design system. Produces a structured audit with a health score, component coverage gaps, token inconsistencies, accessibility issues, and a prioritised remediation roadmap.

Generate a complete, accessibility-checked design system from scratch — colour ramps, type scale, spacing, elevation, and exports for CSS, Tailwind, design tokens, Figma, VS Code and PowerPoint. Use when asked to create a design system, pick a colour palette, build a starter theme, produce design tokens for a new product, or apply an existing brand colour to a full system. For auditing a system that already exists use design-system-audit; for extracting one from a live site use brand-guidelines.

Audit your desk setup and fix what's hurting your neck, back, wrists, or eyes — with specific, mostly-free adjustments before you buy anything. Use when asked to check my desk setup, ergonomics help, my [wrists/neck/back] hurt from my desk, or how to set up my workstation. Produces a point-by-point setup check (chair, screen, keyboard, mouse, lighting), the specific fixes ranked free-first, cheap upgrades only if needed, and micro-break habits — with a 'see a professional for persistent pain/numbness' flag.

Run a timeboxed desk-research sprint that ends with an answer instead of forty tabs — the question decomposition, the source plan by question type, the capture discipline that prevents re-reading, and the stop rule that beats completionism. Use when asked research this market/tool/topic by Friday, I have two hours to get smart on X, structure my desk research, or I keep researching and never concluding. Produces the decomposed questions, the source plan, the capture format, and the timeboxed synthesis with confidence labels.

Clear the desktop that's become a hundred-icon guilt mosaic — the fast triage that empties it today, the honest read of what the desktop was being used for (it's a to-do list wearing icons), and the replacement systems that keep it clear. Use when asked clean up my desktop, my desktop has 200 files on it, why does my desktop keep filling up, or set up a clean-desktop habit. Produces the today-pass, the function-replacement mapping, and the two-minute weekly habit.

Write a developer onboarding document for a service, codebase, or team. Use when asked to write a developer guide, service README, onboarding doc for a new engineer, codebase orientation, or getting-started guide for a technical team. Produces a structured doc covering service overview, architecture, local setup, key patterns, testing, deployment, and who to ask for what.

Argue hard against whatever you just concluded — so your decision has to survive a real challenge instead of an echo chamber. Use when asked to play devil's advocate, argue against this, challenge my conclusion, or talk me out of it. Produces the strongest case against your position, the uncomfortable questions you're avoiding, the evidence that cuts the other way, and an honest read on whether your conclusion survives the challenge — deliberately countering the 'that's a great idea!' agreement bias.

The strongest possible case AGAINST what you just wrote — argued to win, not to check a box. Use when a document is about to ship and everyone around it already agrees: the twin writes the opposition's best memo (not a critique of yours), so you meet the real counter-argument before your audience does. Produces the opposing memo, the map of which of your claims it defeats/dents/leaves standing, and the pre-emption paragraph worth adding.

Run the multi-year campaign of being chronically ill with no diagnosis — track patterns across specialists so nothing resets, avoid the 'it's just anxiety' dead-end, chase referrals that stall, and arrive at each new doctor with the longitudinal case instead of starting from zero again. Use when someone says 'I've been sick for years and no one can tell me why', 'every specialist starts over', 'they keep saying it's stress', or is stuck in diagnostic limbo. Produces a longitudinal symptom dossier, a specialist-handoff brief, and a next-move plan. Not medical advice — it organizes YOUR information so clinicians can use it.

Look up word definitions, pronunciation, etymology and synonyms with zero API keys — the Free Dictionary API via curl, with honest handling of words it doesn't know. Use when asked define a word, how do you pronounce this, what's the origin of a word, or synonyms for something. Produces the definition set organized by part of speech, IPA pronunciation with audio link, and the rerunnable command — with the model's own knowledge clearly separated from the fetched source.

Prepare for and script a hard conversation — conflict, bad news, a boundary, an apology. Use when asked to prepare for a difficult conversation, address a conflict, deliver bad news, confront a colleague, or have a hard talk with a manager/report/peer. Produces a prep brief — the real goal, the other side's likely view, an opening line, the key points, anticipated reactions with responses, and the outcome you want.

Plan what happens to your digital life when you die — accounts, photos, passwords, money, and social profiles — so someone you trust can actually find, access, memorialize, or close them without a legal nightmare. Use when someone says 'what happens to my accounts when I die', 'digital legacy', 'help my family access my stuff if something happens', or is doing estate planning and forgot the online half. Produces a digital asset inventory, an access plan using built-in legacy tools, and instructions for your person. Not legal advice — pairs with a real will.

Plan what happens to your digital life — the account inventory, the access plan that doesn't violate terms or law, platform legacy settings, and the memorialize/delete/preserve decisions, written down while it's easy. Use when asked what happens to my accounts when I die, set up a digital legacy plan, help an executor deal with online accounts, or how does my family get into my stuff. Produces the tiered inventory, the legal-access setup (password-manager emergency access + platform legacy tools), the wishes document, and the executor's digital checklist.

Appeal a denied disability benefit (SSDI/SSI, PIP, DLA, ESA and similar) — decode the denial reason, build the evidence-backed case that answers it, hit the deadline, and prepare for the hearing. Use when someone says 'my disability benefit was denied', 'appeal my PIP/SSDI decision', 'they said I don't qualify', or 'how do I challenge a benefits decision'. Produces a decoded denial, an appeal strategy mapped to the criteria, an evidence checklist, and a statement draft. Not legal advice — it organizes YOUR case and routes to free specialist advice.

Decide whether, when, how, and to whom to disclose a disability or health condition at work — weighing the real benefits (accommodations, protection, honesty) against the real risks (bias, gossip), tuned to your specific situation. Use when someone says 'should I tell work about my disability/condition', 'disclose my ADHD/chronic illness at work', 'when do I tell my employer', or 'how much do I share'. Produces a decision framework for the situation, a disclosure script if you choose to, and the minimum-disclosure options. Your choice throughout; it never pushes disclosure.

Decode a disability insurance policy or employer LTD plan — own-occupation vs any-occupation, the benefit math after offsets and taxes, and the definitions that decide whether it pays. Use when someone asks 'is my disability insurance any good', 'decode my LTD policy', 'what does own-occupation mean', or 'how much would I actually get'. Produces a definition decode of the clauses that decide claims, the real benefit math after offsets, ranked red flags, and the questions to ask before relying on the coverage.

Write a disaster recovery plan for a service or system — covering RPO/RTO targets, failure scenario runbooks, backup and restore procedures, DR testing cadence, and communication templates. Use when asked to write a DR plan, document failover procedures, create recovery runbooks, define RTO/RPO targets, or prepare for a disaster recovery game day. Produces a full DR document with per-scenario recovery runbooks, backup validation procedures, testing schedule, and communication templates.

Turn a hospital stay into a complete, well-structured discharge summary. Use when asked to write a discharge summary, a hospital discharge note, or to document a patient's admission-to-discharge course for handoff. Produces a standard discharge summary — admission reason, hospital course, diagnoses, procedures, discharge medications, condition, and follow-up/return precautions — from the provided details.

Prepare a structured discovery call plan for any prospect. Use when asked to prepare for a sales call, discovery call, prospect meeting, or first call with a potential customer. Produces a call brief with research, hypotheses, questions, and success criteria.

Read your team's messages the way opposing counsel would in litigation discovery — prevention training that makes communication hygiene visceral. Use when asked how would our Slack look in discovery, train my team on communication hygiene, review this thread like a plaintiff's lawyer, or what shouldn't we put in writing. Produces the highlighted-exhibit reading of sample messages, the patterns that create legal risk, and a debrief with the write-it-this-way rules — strictly for prevention, never for concealment.

Create a structured user discovery interview guide with screener questions, a discussion guide, and a synthesis framework. Use when planning user interviews, customer discovery sessions, Jobs-to-be-Done research, or problem validation. Produces a complete guide covering warm-up, problem exploration, and a per-session synthesis template.

Write a letter to dispute an incorrect charge, bill, or record. Use when asked to dispute a credit-card charge, contest a bill or invoice, challenge a credit-report error, or formally dispute a fee. Produces a clear dispute letter — what's being disputed, why it's wrong, the evidence, and the correction requested — in the firm, paper-trail tone these situations need.

Spin up a tabletop RPG one-shot or a session-zero for a new campaign — a hook, a map of the first adventure, NPCs, and encounters tuned to your party. Use when asked to start a D&D campaign, run a one-shot, help me DM, session zero, or make me an adventure for my party. Produces a premise and hook, a session-zero framework (tone, safety tools, expectations), a first-adventure outline with beats and branches, ready-to-run NPCs and encounters scaled to party level/size, and improv fallbacks for when players go off-script.

Query DNS records and domain registration data with zero API keys — DNS-over-HTTPS via dns.google and domain registration via RDAP, through plain curl. Use when asked what does this domain resolve to, check the MX or TXT records, who registered this domain, when does it expire, or has DNS propagated. Produces the records decoded (SPF/DKIM/DMARC read, not just dumped), the registration facts from RDAP, and the rerunnable commands.

Restructure the user's REAL Google Doc — open it, tighten and reorganise it, and return a clean version — not advice on how to edit it. Use when asked to clean up this doc, restructure my draft in Drive, make this readable, or tighten the doc for review in Cowork. Reads the document via the Google Drive/Docs connector, applies a structure-and-concision pass (BLUF, one idea per section, cut the filler), and produces a restructured-document artifact plus a change summary — as a new copy, never overwriting the original.

Keep living documents trustworthy over time — the status header (draft/active/superseded) that tells readers what they're holding, the change-log-for-decisions inside the doc, the supersession chain that kills zombie versions, and the review-date heartbeat. Use when asked which version of this doc is current, our wiki is full of stale pages, set up doc lifecycle rules, or people keep following the old process doc. Produces the status-header standard, the in-doc change log, the supersession protocol, and the staleness heartbeat.

Write a 'get started in 5 minutes' quickstart for a tool, library, or API. Use when asked to write a quickstart, getting-started guide, or onboarding docs for developers. Produces a copy-paste-friendly quickstart that takes a developer from zero to a first working result fast, with install, a minimal working example, and clear next steps.

Prepare for a doctor's appointment so the 12 minutes actually get used — the symptom timeline in the format clinicians think in, the prioritized question list, and the advocacy scripts for being heard. Use when asked help me prepare for my doctor appointment, what should I tell my doctor, organize my symptoms, or I always forget what to ask. Produces the one-page visit sheet: symptom history with timeline, medications, the top-3 questions, and the phrases that get concerns taken seriously.

Decide what documents to keep, for how long, and where — the personal/small-biz retention map by category (tax, legal, medical, warranties, employment), jurisdiction-flagged periods, and the destruction discipline for what's past its date. Use when asked how long do I keep tax documents, can I shred this, set up a document retention system, or what papers does my small business need to keep. Produces the category map with keep-periods (flagged verify-locally), the keep-forever list, the digitize rules, and the annual purge ritual.

Produce properly-formatted tracked changes for a Word document. Use when asked to redline a document, suggest edits to a contract or document, create tracked changes for review, or mark up a document with proposed revisions. Produces a complete redline with insertions, deletions, and margin comments that can be applied to the source document. Best used with Claude Opus 4.7 or newer for reliable tracked changes handling.

Write a warm donor update or stewardship message that makes a supporter feel their gift mattered. Use when asked to write a donor update, a thank-you/stewardship email, a supporter newsletter, or a gift acknowledgement. Produces a donor-centred update — sincere thanks, the specific impact of their support, a brief story, and a light, optional next step — that strengthens the relationship and sets up the next gift.

Make introductions that respect both sides — the double-opt-in flow (ask each party privately before connecting them), the forwardable blurb that makes saying yes easy, and the connecting email that sets both up to succeed. Use when asked introduce me to someone, can you connect us, write an intro email, or someone asked me for an intro. Produces the opt-in asks for both sides, the forwardable blurb, the intro email itself, and the graceful decline path.

Empty the Downloads folder that's become a junk drawer — the four-bucket pass (file, delete, action, quarantine), the age-based bulk rules that make 2,000 items tractable, and the tiny habit that keeps it empty. Use when asked clean up my downloads folder, 2000 files in downloads help, what's safe to delete here, or stop my downloads from piling up. Produces the bucket pass with bulk rules, the safe-delete classes, the keeper-filing routes, and the weekly sweep habit.

Respond fast and safely if your personal information has been exposed or you're being doxxed — contain the spread, protect your safety and accounts, and report it. Use when asked what to do if I've been doxxed, someone posted my personal info, my address is being shared online, or I'm being targeted online. Produces an immediate safety-and-containment checklist, takedown/report steps for the platforms hosting the info, account and physical-safety hardening, an evidence-preservation step for authorities, and escalation to police/support when there are threats. Not legal advice.

Read a Data Processing Agreement before you sign it — sub-processors, transfer mechanism, breach-notice window, deletion, audit rights — in plain language with 🔴🟡🟢 risk. Use when asked to review a DPA, check a data processing agreement, is this DPA safe to sign, or what am I agreeing to on data. Produces the plain-English summary, the risk-ranked findings, the missing-clause checklist, and the questions to send back before signature.

Check recent earthquakes worldwide with zero API keys — USGS real-time GeoJSON feeds via curl, filtered by magnitude, region, and time window. Use when asked was there an earthquake just now, recent quakes near a place, any big earthquakes today, or monitor seismic activity somewhere. Produces the matching events with magnitude, depth, location and time, the felt/damage context bands, and the rerunnable command — with the official-guidance line safety questions require.

Protect aging parents from the scams that target them — the conversation that doesn't condescend, the family code word, the top patterns aimed at seniors, and the guardrails that help without taking over. Use when asked how do I talk to my parents about scams, my mom almost sent money to someone, set up scam protection for my dad, or what scams target the elderly. Produces the briefing conversation script (dignity-first), the household defenses, the pattern one-pager to leave behind, and the if-it-already-happened response.

Write to an elected representative in a way that actually gets action — a specific ask, your local stake, why it's in their interest to respond, and the follow-up — instead of an angry email that gets auto-filed. Use when someone says 'write to my MP/congressperson/councillor', 'contact my representative about X', 'how do I get my rep to act', or 'my letter to the council got ignored'. Produces a targeted letter (or call script), tuned to the right representative and level of government, plus a follow-up plan.

Run the pre-flight checklist before an agent touches an inbox — the read-vs-send permission line, the injection-in-email-body threat, the send-guard rules, and the blast-radius limits that keep a compromised agent from mailing the company. Use when asked let my agent read/send email safely, set up guardrails before the agent touches my inbox, is it safe to give the agent email access, or review my email agent's permissions. Produces the permission tier, the injection defenses, the send-gate rules, and the incident kill-switch.

Write and sequence multi-email nurture or launch campaigns. Use when asked for an email sequence, drip campaign, onboarding emails, product launch emails, or nurture flow. Produces subject lines, preview text, full email body, and send-timing recommendations for each email in the sequence.

Write a multi-email nurture/onboarding/launch sequence with a goal per email. Use when asked to write an email sequence, a welcome/onboarding series, a nurture drip, a launch sequence, or a re-engagement series. Produces the sequence map (trigger, timing, goal per email) plus the full copy for each email — subject, body, and one CTA — designed to move the reader one step at a time.

Convert an email (or a whole thread) into real tasks — the actual asks extracted from the prose, each with owner, deadline, and the done-test, so nothing lives in the inbox as its own reminder. Use when asked what am I actually being asked to do here, turn this thread into a task list, extract the action items from this email, or I keep re-reading this thread. Produces the ask extraction with quoted sources, the task list in owner-verb-deadline form, and the reply that confirms the commitments.

Triage a Gmail inbox down to only what needs you. Use when asked to triage email, clear an inbox, find what needs a reply, or summarise recent mail. Produces a prioritised list of items needing action — replies, decisions, follow-ups — for a configurable window (default last 8 hours), filtering out receipts, notifications, and newsletters.

Turn an overflowing inbox into a four-verb system — archive, reply-now, task, or park — with the two-minute rule enforced and a daily cadence that survives busy weeks. Use when asked help me get to inbox zero, my email is out of control, build me an email triage system, or process this backlog. Produces the triage pass on the actual inbox, the four-verb rules, the folder/label minimal set, and the daily cadence.

Assemble the grab-and-go document and information kit for a disaster — the IDs, insurance, medical, financial, and property records (physical copies + secure digital backups) you'd need to prove who you are, get aid, and rebuild after a fire, flood, or evacuation. Use when someone says 'what documents for an emergency', 'important papers for a disaster', 'emergency document checklist', or 'what would I need if my house burned down'. Produces a documents checklist, a physical + digital storage plan, and the info that isn't a document (contacts, med lists). Pairs with the go-bag.

Size an emergency fund from essential spend and real risk factors — not a one-size 'six months' — with the funding timeline and where the money should sit. Use when asked how big should my emergency fund be, do I have enough saved, emergency fund or invest, or how many months of expenses do I need. Produces the risk-adjusted target from the script, the essential-spend worksheet, the funding plan, and the what-counts-as-an-emergency rules.

Design an employee engagement survey and analyse results. Use when asked to create an employee survey, engagement questionnaire, pulse survey, or eNPS survey. Also use when asked to analyse survey results. Produces a complete survey with questions, rating scales, and an analysis framework.

Write empty-state content that turns a blank screen into a next step. Use when asked to write an empty state, a zero-data / first-run state, a no-results state, or onboarding placeholder content. Produces empty-state copy — a clear headline, a helpful line, and a primary action — for each type (first-use, user-cleared, no-results, error/permission), so a blank screen guides instead of confuses.

Have the conversation about someone's end-of-life wishes — before a crisis forces it — gently, respectfully, and thoroughly enough to actually guide decisions later. Use when asked how do I talk about end-of-life wishes, discuss my parent's wishes, advance care planning conversation, or ask about their medical and final wishes. Produces a way to open this hard conversation without it feeling morbid or forced, the areas to cover (medical wishes, care preferences, where they want to be, what matters to them, practical/legal), how to listen rather than impose, and how to document and share what's decided — so their wishes are known and honored. Not legal or medical advice.

Schedule work by energy, not just time — the week of self-observation that maps your real peaks and troughs, the work-to-energy matching (hard creative work on peaks, admin on slopes, meetings on shoulders), and the calendar rebuild that honors the map. Use when asked when should I do my hardest work, I waste my best hours on email, map my energy levels, or why is 3pm always useless. Produces the observation protocol, the personal energy map, the work-type matching, and the rebuilt week.

Run a close-out retrospective on a client engagement — capture lessons, results, and the renewal/referral path. Use when asked to wrap up a client project, run an engagement retro, write a project close-out, or plan the follow-on. Produces a close-out — outcomes vs. goals, what worked / what didn't, profitability/scope reality, a reusable lessons log, and the next-engagement or referral ask.

Build an engineering hiring rubric and technical interview scorecard for evaluating software engineers at a specific level. Use when asked to create an interview rubric, design a hiring process, build a technical scorecard, or standardize engineer evaluation. Produces a full interview scorecard, behavioral question bank, technical question set with evaluation criteria, system design rubric, and debrief agenda.

Write a weekly engineering status report for a team, service, or initiative. Use when asked to write a team update, weekly engineering report, sprint status email, or standing team communication to stakeholders. Produces a concise, scannable weekly report covering shipping progress, metrics, decisions, blockers, and next-week priorities.

Turn a data model into an entity-relationship (ER) diagram. Use when asked to design a schema, model data, show how tables/entities relate, or diagram a database. Produces a ready-to-render Mermaid ER diagram (renders live, exportable as PNG/SVG) plus key attributes, cardinality, and design notes.

Report on an epic or initiative deeper than a status bullet — child work broken down by status, the riskiest unfinished pieces, and honest suggested cuts to hit the date. Use when asked for an epic progress report, where are we on this initiative, break down epic status, or what can we cut to ship on time. Produces the completion picture by child status, the critical-path and riskiest remaining work, a scope-cut menu with impact, and a straight call on whether the target date is realistic.

Decode an error message or stack trace into a plain-English cause, the exact fix, and how to prevent it. Use when asked to explain an error, debug a stack trace, figure out why code is throwing, or make sense of a cryptic exception. Produces a structured diagnosis: what the error means, the most likely cause, a concrete fix with code, and a prevention tip.

Write clear, helpful error messages that tell users what happened and how to fix it. Use when asked to write an error message, validation text, a failure/empty-error state, or to rewrite a cryptic system error. Produces human, blame-free error copy — what went wrong, why (if useful), and the next step — with options per surface (inline, toast, full page) and the related success/empty states.

Escalate an issue up the chain without burning the person you're escalating past — the facts-first structure, the tried-already section that earns the escalation, and the specific ask that makes action easy. Use when asked I need to escalate this, write an email to my boss's boss, this vendor issue needs to go up, or how do I go over someone's head professionally. Produces the escalation email with its evidence spine, the pre-escalation courtesy step, and the relationship-preserving framing.

Design a support/incident escalation tree — who handles what, when it escalates, and to whom. Use when asked to design an escalation path, an escalation matrix, support tiers, an on-call escalation policy, or to fix 'tickets bounce around / nothing gets escalated in time'. Produces an escalation tree — tiers & ownership, severity definitions, time-based triggers, routing rules, contacts/roles, and the customer-communication cadence per level.

Draft an honest, audit-ready ESG disclosure section in a CSRD/ESRS-flavored structure, adaptable to other frameworks. Use when asked to write a sustainability report section, draft an ESRS or CSRD disclosure, prepare an ESG section for an annual report, or turn raw sustainability data into disclosure text. Produces a disclosure draft with double-materiality framing, metric-methodology-limitation triplets, based forward statements, and explicit data-gap handling.

Get your affairs in order before you need to — a will/beneficiary/healthcare-directive checklist and the 'what my family needs to find' document, in the right order. Use when asked to help with estate planning, make a will checklist, get my affairs in order, or prepare what my family needs if something happens to me. Produces the estate-planning checklist ranked by priority, the document-locator sheet, the key decisions to make, and the professional-help flags — for the living, not the executor. Complements the estate/after-death pack.

Organize an executor's work — the settlement ladder from will-to-probate-to-distribution, the asset/debt inventory, the creditor and beneficiary communications, and the records that keep an executor protected. Use when asked I'm the executor what do I do, organize settling an estate, what's the probate process roughly, or track estate assets and debts. Produces the phased task ladder (jurisdiction-flagged), the inventory workbook structure, communication templates, and the executor's self-protection rules.

Write a eulogy or obituary for someone you loved when you're grieving and the words won't come — a true, warm piece that sounds like them and like you. Use when asked help me write a eulogy for my father, write an obituary, I have to speak at the funeral, or I don't know what to say about them. Produces a eulogy or obituary drafted from your memories (not clichés), the right structure and length for the setting, the specific stories and details that make it theirs, guidance on tone and delivery (including reading it aloud through tears), and what to include in an obituary (facts, survivors, service details) — so you can honor them well without facing the blank page alone. Written in your voice from your memories.

Help someone write a eulogy — the hardest writing most people ever do, at the worst possible time. Use when someone must speak at a funeral or memorial and doesn't know where to start, or has fragments and no shape. Produces a 3-5 minute eulogy built from their memories in their voice, plus a delivery copy formatted for shaking hands — gentle process, no interrogation, nothing invented.

Guide a veterinary team through a compassionate end-of-life conversation with a pet owner — quality-of-life assessment, the recommendation, and the logistics. Use when asked to help discuss euthanasia, assess quality of life, prepare for a difficult end-of-life conversation, or support an owner facing the decision. Produces a quality-of-life framework, empathetic language for the conversation, how to answer the hard questions (is it time, will it hurt, should the kids be there), and the practical steps (the process, aftercare options, grief support).

Compare an EV against a comparable gas car on total cost — upfront gap after incentives, energy vs fuel per year, maintenance delta, and the crossover year when the EV pulls ahead (or doesn't). Use when asked is an EV worth it, EV vs gas total cost, when does an EV pay for itself, or should my next car be electric. Produces the year-by-year cumulative comparison from the script, the crossover year, the per-mile energy math, and the honest not-modeled list.

Design a scoring rubric and LLM-as-judge prompt to evaluate the quality of an AI feature's output. Use when asked to create an eval rubric, define quality dimensions, build an LLM judge, or decide how to measure whether AI output is good. Produces a rubric with weighted dimensions and concrete 1–5 anchors, a ready-to-run judge prompt, a labelling guide, and notes on judge reliability.

Grade the evidence behind a claim before betting on it — the hierarchy for business evidence (experiments > usage data > surveys > interviews > anecdotes > opinion), the fit-for-decision test, and the mixed-evidence verdicts that real questions produce. Use when asked how strong is our evidence for this, grade what we know before the decision, is this enough to bet on, or we have three anecdotes and a survey — now what. Produces the evidence inventory with grades, the sufficiency verdict against the decision's stakes, and the cheapest-upgrade path.

Write or rewrite a document in evidence-locked mode: no unsourced sentences — every substantive claim carries a footnote citing the exact passage in the user's provided sources, and anything unsupportable is explicitly marked. Use when asked to make a document fully sourced, add citations from my docs, ground a draft in the attached material, or produce something for audiences that will check (legal, board, regulators, enterprise buyers). Produces the document with numbered citations, a source map quoting each cited passage, and an unsupported-claims register.

Run an NPI phase-gate review for EVT, DVT, or PVT — exit criteria per phase, open-issue triage, yield readout, waiver discipline, and a go/no-go call. Use when asked to run a gate review, decide EVT exit or DVT entry, review build results, assess whether to proceed to the next build, or triage open issues before a phase gate. Produces a gate review document with criteria scoring, waiver register, yield analysis, and a defensible go/conditional-go/no-go recommendation.

Build a realistic exam-prep schedule with spaced repetition and retrieval practice — the plan that survives contact with an actual week. Use when asked to plan my exam prep, make a study schedule, I have N weeks until finals, or how do I study for multiple exams. Produces a day-by-day plan across all exams: spaced blocks, retrieval-first sessions, weak-topic weighting, and built-in slack for the days that go wrong.

Build a backward-planned study schedule for an exam — using proven learning methods, not just re-reading — so you cover what matters and actually retain it. Use when asked to make a study plan, help me study for [exam], I have an exam in [time], or how do I revise. Produces a week-by-week plan working back from the exam date, prioritized by weighting and your weak spots, sessions built on active recall and spaced repetition, past-paper/practice integration, and a realistic pace with breaks — not an unsustainable cram that forgets everything by exam day.

Build a real, formula-driven Excel (.xlsx) model — not a static table. Use when asked to build an Excel model, a financial model, a budget/forecast spreadsheet, or any .xlsx with live formulas a user can edit. Produces an actual .xlsx file via a generated openpyxl script: an inputs/assumptions sheet, calculation sheets with real cell formulas, and formatting — so changing an input recalculates the model. Requires a code-execution environment (Claude Code, the API code tool, or Claude.ai).

Stop presenting the working deck to executives — the two-deck split (answer-first exec cut vs. exploration-rich working deck), the compression rules from 40 slides to 8, and the appendix strategy that keeps the depth one click away. Use when asked turn this analysis into an exec version, my leadership readout went badly, how do I compress 40 slides to 10 minutes, or what do execs actually want in a deck. Produces the exec cut with the answer-first order, the compression map (what survived, where the rest went), and the Q&A appendix plan.

Execute a written plan with discipline — verify each step before advancing, surface deviations instead of improvising around them, and keep a visible execution log. Use when working through a plan (yours or another agent's), resuming multi-session work, or when execution keeps drifting from what was agreed. Produces completed work plus an execution log showing what matched the plan, what deviated and why, and what the plan got wrong. Pairs with writing-plans.

Sharpen how you show up in high-stakes rooms — communicate with gravitas, concision, and confidence. Use when asked to improve executive presence, prepare to present to leadership, sound more senior, command a room, or get coaching before a big meeting. Produces specific guidance — how to open, structure answers (BLUF/headline-first), handle tough questions, project calm, and the habits to drop, tuned to the moment.

Write an executive summary for any document, report, or proposal. Use when asked to write an executive summary, management summary, briefing paper, or one-pager for senior stakeholders. Produces a structured summary that busy executives can read in under 3 minutes and act on.

Transform detailed product updates into concise executive briefings. Use when asked to write an executive update, leadership update, product update for the exec team, or a C-suite product briefing. Produces a structured 250-word briefing with headline, key metrics, progress, risks, decisions needed, and next steps.

Walk into an exit interview knowing what it's for, what to say, and what to keep — honest-but-strategic answers that protect references and leave the door open. Use when asked what do I say in my exit interview, should I be honest in my exit interview, prep me for my exit interview, or is the exit interview confidential. Produces the goals-and-risks brief, prepared answers for the standard questions, the say/soften/skip sorting of your real feedback, and the scripts for the questions that are traps.

Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses. Use when asked to model an exit waterfall, what do I get if we sell for X, explain liquidation preferences on my cap table, or compare payouts across exit prices. Produces a per-stakeholder payout table across exit values with conversion decisions shown, plus the plain-English reading of what the structure means for each party.

Audit spending to find leaks — recurring subscriptions, creep, and cuttable costs — ranked by impact. Use when asked to cut expenses, review subscriptions, find where money is going, or free up cash. Produces a categorized spend breakdown, a ranked list of cuts with dollar amounts, and the annualized savings. Educational, not regulated financial advice.

Submit expenses that sail through approval — the capture-at-spend habit, the policy-fluency that prevents rejections (thresholds, receipt rules, the pre-approval traps), the report assembled in minutes, and the approver-side rules for reviewing fairly and fast. Use when asked my expense reports are always late or rejected, set up my expense workflow, what does the policy actually require, or review expenses as a manager without being a receipt cop. Produces the capture habit, the policy crib, the submission routine, and the approver's rubric.

Turn a pile of receipts into a filed expense report through a tool-using agent — extraction, policy checks, and categorization done for you; submission gated on your approval. Use when asked to file my expenses, process these receipts, build my expense report, or expense this trip. Produces the itemized report with policy flags and an approval-gated filing plan.

Write a clear company expense & reimbursement policy. Use when asked to write an expense policy, a reimbursement policy, a travel & expense (T&E) policy, or spending guidelines. Produces a practical policy — what's covered, limits by category, the approval and submission process, timelines, and what's not reimbursable — that's fair, easy to follow, and reduces finance back-and-forth. Not tax/legal advice.

Design an expense-tracking sheet that survives real receipts — the capture-at-spend habit, the category set that matches reimbursement or tax rules, the receipt-link discipline, and the month-end close that takes minutes because the work happened at spend-time. Use when asked track my business expenses, build an expense sheet for the team, get ready for reimbursement/tax season, or my shoebox of receipts needs a system. Produces the sheet structure, the capture ritual, the category mapping to the real downstream rules, and the month-end close.

Design statistically rigorous A/B tests and interpret experiment results. Use when asked to design an experiment, run an A/B test, calculate sample size, interpret test results, or assess whether an experiment was successful. Produces a complete experiment design with hypothesis, sample size, run time, success criteria, and risk flags — or a results interpretation with ship/iterate/kill recommendation.

Analyse a finished A/B test and write an honest results readout with real statistics. Use when asked to read out an A/B test, analyse experiment results, check if a result is statistically significant, or decide ship/no-ship from test data. Produces a readout — the computed lift, p-value & confidence interval, a significance verdict, guardrail check, and a clear ship / no-ship / iterate recommendation. Includes a stdlib significance calculator.

Get the most from an hour with an expert — the do-your-homework floor (never ask what's googleable), the question arc from calibration to the frontier, the follow-up discipline that goes deep instead of wide, and the capture that survives the call. Use when asked prep me for the expert call, what should I ask this advisor/analyst/practitioner, we get an hour with X, or our expert calls are pleasant but shallow. Produces the homework brief, the question arc, the follow-up toolkit, and the capture plan.

Talk through a decision out loud with a patient thinking partner that reflects your reasoning back, so the answer you already half-know becomes clear. Use when asked help me think this through, I need to talk this out, be my sounding board, or I don't know what I actually think. Produces a structured reflection of your own reasoning — what you've actually said, the values driving it, the contradictions and gaps, and the question that would clarify it — acting as a rubber-duck / sounding board rather than handing you an answer you didn't reach yourself.

Explain anything in plain language — a contract clause, a medical term, a tax rule, a tech acronym, a news story — layered from a one-liner to as much depth as you want. Use when asked to explain like I'm 5, explain this simply, break this down in plain English, or what does this even mean. Produces the one-sentence version, a plain-language explanation with a concrete analogy, the 'why it matters to you,' and an honest note on anything genuinely uncertain or oversimplified.

Write session-based exploratory testing charters to find what scripted tests miss. Use when asked to plan exploratory testing, write a test charter, design a testing session, or do risk-based exploration of a feature. Produces focused charters — a mission, areas/risks to explore, tactics and oracles, and timeboxed sessions — so exploration is purposeful and accountable, not random clicking.

Figure out whether your record can be sealed or expunged, and map the steps to do it — eligibility, waiting periods, forms, and where to get help. Use when asked can I get my record expunged, how do I seal my criminal record, clear my background, or am I eligible for expungement. Produces a plain-language read on likely eligibility (offense type, dispositions, waiting periods), the document and step sequence to petition, the costs and fee-waiver options, the realistic timeline, and where to get free or low-cost legal help — so a record that can be cleared actually gets cleared. Not legal advice; expungement law is highly jurisdiction-specific and this points you to the right help.

Run a claim-by-claim fact-check pass on a draft article, script, or report before publication. Use when asked to fact-check a piece, verify claims before publishing, or do editorial verification. Produces a claim inventory (every checkable assertion pulled out), a verification status and source for each (confirmed / needs sourcing / unverifiable / wrong), the fixes, and a flag on the high-risk claims (numbers, quotes, names, legal/defamatory statements) that must not go out unverified.

Write a factory acceptance test (FAT) plan or report — test coverage matrix against spec, AQL sampling plan, pass/fail criteria, golden-sample handling, deviation log, and sign-off structure. Use when asked to write a FAT plan, define outgoing quality inspection, set AQL levels, prepare for a factory acceptance or pre-shipment inspection, or document FAT results. Produces a complete FAT plan or report with sampling tables, defect classification, and a sign-off block.

Navigate questioning, leaving, or changing your religion — especially a high-control or all-encompassing one — with the relationship-preservation scripts for family who stayed, a way to grieve the community and certainty you're losing, and support for rebuilding meaning. Use when someone says 'I'm losing my faith', 'I left my religion and my family is devastated', 'religious deconstruction', 'how do I tell my believing parents', or is leaving a high-demand group. Produces conversation scripts, a grief-and-identity map, and a rebuilding plan. Not persuasion in any direction, and not therapy — a companion for a hard passage.

Build a family emergency plan — contacts, meeting points, key documents, and 'if something happens to me' info — so your household isn't scrambling in a crisis. Use when asked to make a family emergency plan, be prepared for an emergency, what if something happens to me, or organize our important info. Produces a household plan covering communication and meeting points, an emergency contact/ICE setup, a key-documents and info location list, a basic go-bag/supplies checklist, and a 'someone needs to find this' plan — tailored to your household and likely local risks.

Build a fantasy-sports draft strategy and weekly plan that fits your league's exact settings — so you draft with a plan instead of vibes. Use when asked to help with my fantasy draft, who should I draft, fantasy league strategy, or set my lineup this week. Produces a settings-aware draft approach (positional strategy by round, tiers over rankings, targets and values), a snake/auction plan for your slot, weekly start/sit and waiver logic, and honest reminders that player values shift — verify current status before locking anything in.

Build an FAQ from the questions people actually ask — mined from tickets, chats, and repeated explanations, answered once and well, organized by the asker's words, and maintained by a capture loop instead of annual archaeology. Use when asked create an FAQ for this product/process/team, I answer the same questions weekly, turn our support threads into docs, or why does nobody find our answers. Produces the mined question list with frequencies, the answers in ask-language, the structure, and the capture loop.

Write a feature flag management guide and lifecycle playbook for a service or team — covering flag taxonomy, creation checklist, rollout strategy, monitoring requirements, cleanup policy, and governance. Use when asked to document feature flag practices, create a flag rollout plan, write a feature flag policy, or guide a team on flag lifecycle management. Produces a flag lifecycle playbook, taxonomy reference, per-flag creation template, rollout decision tree, and cleanup checklist.

Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items. Use when asked to prioritise features, rank a backlog, decide what to build next, or evaluate tradeoffs between competing ideas. Produces a scored, ranked feature list with framework-specific tables, recommended build order, deprioritised items, and assumptions made.

Plan the retirement of a product feature — the kill decision made honest, user migration, data handling, comms sequencing, and the code actually deleted. Use when deprecating or sunsetting a feature, killing an underused capability, retiring an AI feature that didn't land, or when a 'deprecated' feature has haunted the codebase for two years. Produces a sunset plan: the decision record, affected-user analysis, migration paths, a staged timeline with comms per stage, and the removal checklist. For API deprecation specifically use api-versioning-strategy.

Learn something deeply by trying to explain it simply — the Feynman technique — surfacing exactly the gaps where your understanding is fake. Use when asked help me really understand X, explain this back to check my understanding, use the Feynman technique on, or do I actually get this. Produces a prompt to explain the concept in plain language yourself, a check that flags where your explanation went vague, hand-wavy, or jargon-hid a gap, the specific things you don't actually understand yet, and how to close each — because if you can't explain it simply, you don't really know it.

Generate structured developer handoff annotations for a Figma screen or component. Use when asked to write Figma annotations, create dev handoff notes, document a Figma design for developers, or write specs for a screen. Produces a complete annotation set covering interactions, states, spacing, accessibility, and edge cases.

Audit a Figma component library for consistency, coverage gaps, and naming issues. Use when asked to audit components, review a design system, check component consistency, identify missing components, or assess Figma library health. Produces a structured audit report with issues prioritised by impact, naming recommendations, and a fix plan.

Write a structured design brief for a Figma design task from a product requirement or feature request. Use when asked to write a design brief, create a design spec for Figma, turn a PRD into design requirements, or brief a designer on what to build in Figma. Produces a brief with goals, scope, user flows, components needed, constraints, and success criteria.

Runs a PM-perspective design critique focused on product outcomes and user goals, not aesthetics. Use when asked for a PM design critique, a product review of a Figma design, or feedback from a product perspective without needing to be a designer. Produces structured outcome-based feedback tied to user goals, business metrics, and requirement coverage.

Runs a pre-handoff QA checklist on a Figma design before it goes to engineering. Use when asked to QA a Figma design, do a pre-handoff check, or validate a Figma file is ready to build. Produces a structured QA report covering file hygiene, component usage, accessibility, and handoff readiness with explicit pass/fail status per item. Optimised for Opus 4.7 and newer models.

Runs a structured PM design review against product requirements. Use when asked to review a Figma design, check a design against requirements, or assess whether a design meets the product spec. Produces a requirements coverage check, UX concerns, open questions, and an explicit approval status — approved, approved with conditions, or not approved.

Plan prototype interactions and flows for user testing in Figma. Use when asked to plan a Figma prototype, set up prototype interactions, define what to prototype for a user test, or prepare a Figma prototype for usability testing. Produces a prototype scope, interaction specification, test task scripts, and Figma setup guide.

Design a spacing and layout token system for a Figma design system. Use when asked to create a spacing system, define layout tokens, set up a grid system, build a spacing scale, or establish layout foundations for a Figma file. Produces a complete spacing scale, grid definition, component spacing conventions, and Figma implementation guide.

Plan user flows and screen states for a Figma design before any designing starts. Use when asked to plan a user flow, map out screens for a feature, define screen states, plan a Figma file structure, or work out what needs to be designed before opening Figma. Produces a complete flow map with all screens, states, entry/exit points, and a suggested Figma page structure.

Define component variants and states systematically for Figma. Use when asked to plan component variants, define states for a component, set up a Figma variant matrix, or work out what properties a component needs before building it. Produces a complete variant matrix with all properties, values, and combinations needed.

Run the pre-flight checklist before an agent gets filesystem access — the scope boundary (which directories, read vs write), the secrets-exposure sweep, the destructive-operation gates, and the path-traversal and untrusted-file defenses. Use when asked let my agent access my files safely, is it safe to give the agent file/computer access, guardrails before the agent touches my filesystem, or scope down my coding agent's reach. Produces the scope boundary, the secrets sweep, the write/delete gates, and the untrusted-content rules.

Set a filename convention that sorts, searches, and survives — date-first ISO format, the descriptor grammar, version suffixes that end the FINAL-final2 era, and the rollout that gets a team actually using it. Use when asked set up file naming rules, our filenames are chaos, what should we call our files, or fix the v2-final-FINAL problem. Produces the convention with its grammar, examples for the team's real file types, the version rule, and the one-line cheat sheet.

Write a financial-aid appeal or scholarship request letter that aid offices act on — factual, documented, and specific about the ask. Use when asked to appeal my financial aid, write a scholarship letter, ask for more aid after circumstances changed, or respond to an aid decision. Produces the appeal letter with the changed-circumstance case documented, the specific dollar ask, the evidence list to attach, and the follow-up plan.

Run an annual (or anytime) financial health check across the key areas — so you catch problems and opportunities instead of drifting. Use when asked do a financial checkup, am I doing okay financially, review my finances, or financial health check. Produces a structured review across the core areas (safety net, debt, spending, saving/investing, protection, and goals), a clear read on what's healthy vs needs attention, the highest-priority fixes, and a couple of easy wins — a financial physical that turns 'I think I'm fine?' into an honest, actionable picture. Educational, not financial advice.

Generate a financial due diligence checklist and analysis framework for any investment, acquisition, or partnership. Use when asked for a due diligence checklist, M&A financial review, investment analysis framework, or vendor financial assessment. Produces a document request list, key analytical questions, red flags checklist, and a summarised financial health assessment.

Map a realistic path toward financial independence — the number you'd actually need, your savings rate's massive effect on the timeline, and the honest tradeoffs. Use when asked how do I reach financial independence, explain FIRE, what's my FI number, or plan for financial freedom. Produces an educational read on your rough FI number (and why the savings rate matters more than income), the timeline math at different savings rates, the levers and lifestyle tradeoffs, the different flavors (lean/coast/full), and the traps — turning a vague dream of freedom into a directional plan. Not financial advice.

Turn financial model outputs into a clear written narrative. Use when asked to write a financial narrative, explain a financial model, summarise a P&L, or translate spreadsheet numbers into a board-ready story. Produces an executive narrative with key insights, drivers, and forward-looking commentary.

Explain a financial statement (P&L, balance sheet, or cash flow) in plain English. Use when asked to explain a P&L / income statement, a balance sheet, a cash flow statement, or to make financials understandable to a non-finance reader. Produces a plain-language walkthrough — what each section means, the line items that matter, the key ratios, and the story the numbers tell — so a non-accountant can read and act on it. Not financial advice.

Appeal a parking ticket, penalty charge, or administrative fine with the grounds that actually get appeals granted — not indignation. Use when someone got a ticket/fine/penalty notice and either has a legitimate case or wants an honest read on whether they do. Produces a short formal appeal letter built on recognised grounds (signage, procedure, mitigation, first-offence discretion), the evidence checklist, and a candid win-likelihood note — or the honest advice to just pay it.

Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer. Use when asked what's my FIRE number, when can I retire early, how much do I need to be financially independent, or model my savings trajectory. Produces the FIRE number, years-to-target at stated assumptions, a return × withdrawal-rate sensitivity grid, and the honest list of what the model ignores.

Build a realistic plan to reach your first major savings/investing milestone — the hardest one — by focusing on the levers that actually move it: income, savings rate, and time. Use when asked how do I save my first 100k, plan to build wealth, reach a savings milestone, or how do I actually get ahead financially. Produces an honest read on your three levers (earn more, spend less, invest consistently), which one has the most room for you, a milestone timeline based on real numbers, the compounding effect once you're rolling, and the traps that stall people — educational, not financial advice.

Build a concrete plan for the first 90 days after release from incarceration — the ID, benefits, housing, check-ins, and money moves that have to happen in order, before they cascade into a crisis. Use when asked I'm getting out of prison what do I do first, reentry plan, just got released and I'm overwhelmed, or first steps after incarceration. Produces a sequenced week-by-week plan for the highest-priority setup (ID and documents, parole/probation compliance, benefits, housing, phone, bank, health/meds), the deadlines that carry real consequences, a triage of what's urgent vs. what can wait, and where to get reentry support — so the first months build stability instead of spiraling. Not legal advice; centers parole/probation compliance and points to reentry services.

Put your first client agreement in writing — the eight clauses a simple service contract must have, in plain language a non-lawyer can use, with the blanks filled from your actual deal. Use when asked write my first client contract, what should a freelance agreement include, my client wants to start without a contract, or review this simple services agreement. Produces the plain-language agreement draft with the eight load-bearing clauses, the per-clause reasoning, the how-to-send-it script, and the when-this-needs-a-lawyer triggers.

Plan your first hire — whether to hire at all yet, contractor vs employee, what role to hire, and how to do it right when you've never hired before. Use when asked to help me make my first hire, should I hire someone, contractor or employee, or how do I hire for my small business. Produces a readiness and role read (what to hand off first), a contractor-vs-employee decision for your situation, a lightweight hiring process (role definition, sourcing, a fair evaluation, an offer), the obligations to be aware of, and onboarding basics — flagging that employment/tax/legal rules are local. Not legal or tax advice.

Set up a new open-source project's first month so it can grow without eating its maintainer — the README that routes people correctly, CONTRIBUTING boundaries written before there are contributors, issue templates that pre-triage, a release rhythm, and the sustainability defaults (what you owe no one). Use when someone says 'my repo is getting attention', 'I just open-sourced something', 'set up my project properly', or their first PR from a stranger just landed. Produces the docs set, the templates, and the month-one routine.

Answer a question five completely different ways — as five independent minds with clashing worldviews — then converge on what survives. Use when asked for multiple perspectives, look at this from every angle, what would different people think, or give me a range of views not one answer. Produces five genuinely distinct takes (each committed to one worldview, not hedged), the tensions between them made explicit, and a final synthesis that keeps what's strongest — deliberately widening the range before narrowing it.

Plan around flare days before they ambush you — spot your early warning signs, pre-build the reduced 'flare mode' version of your life, prepare the cancellation and support scripts in advance, and set up your space so a bad day needs no decisions. Use when someone says 'my flares blindside me', 'I fall apart when a bad day hits', 'help me prepare for flare-ups', or has a relapsing condition (autoimmune, migraine, mental health, chronic pain). Produces a flare early-warning list, a flare-mode plan, and the pre-written scripts. A self-management tool, not medical advice.

Work out whether a delayed, cancelled, or overbooked flight likely owes you compensation — and draft the claim with the right rule cited. Use when asked about flight delay compensation, my flight was cancelled/delayed/overbooked, am I owed money for this flight, or how do I claim EU261. Produces an eligibility read against the likely-applicable regime (EU261/UK261/US DOT-style and airline duty-of-care), the amount band, the claim letter with flight details, and the evidence to attach — flagging what to verify because rules and thresholds change.

Track live aircraft positions with zero API keys — adsb.lol's open ADS-B network primary, OpenSky fallback, via curl: by callsign, registration, or area. Use when asked where is this flight right now, what planes are overhead, track a tail number, or is that flight in the air. Produces the live position with altitude, speed, and heading interpreted, the overhead list for a location, and the rerunnable command — with the positions-not-schedules boundary stated honestly.

Read your team's flow metrics — cycle time, throughput, WIP, aging work — and say what they actually mean and what to try, not just restate the numbers. Use when asked to interpret cycle time, what do our flow/Actionable-Agile metrics mean, why is delivery slow, or read our Kanban metrics. Produces the health read per metric, the likely bottleneck the numbers point to, 2–3 concrete process experiments to run next, and the trap-to-avoid so the team doesn't game the metric instead of fixing the flow.

Turn a process, workflow, or decision logic into a clean flowchart. Use when asked to diagram a process, map a workflow, visualize steps/branches, or show 'how this works' as a chart. Produces a ready-to-render Mermaid flowchart (renders live in the playground, exportable as PNG/SVG) plus a short legend and the assumptions made.

Draft a public-records request (FOIA / FOI / state open-records) that's specific enough to get records and hard to deny. Use when asked to write a FOIA request, records request, or freedom-of-information request to a government body. Produces a properly-scoped request: the records sought, date range and format, fee-waiver and expedited-processing asks where applicable, and citations to the governing statute.

Design a folder structure people actually file into — shallow, purpose-first, with a home for everything and an inbox for the undecided, sized to the team that must maintain it. Use when asked organize our shared drive, design a folder structure for the project, where should things live, or our files are chaos. Produces the structure with its placement rules, the depth and naming constraints, the _inbox convention, and the migration-lite plan for the existing mess.

Chase unanswered emails without being annoying — the escalating-gently sequence with timing rules, the re-ask that makes replying easy, and the close-the-loop discipline that ends zombie threads. Use when asked they haven't replied what do I send, write a follow-up that isn't pushy, how long do I wait before chasing, or manage my waiting-on list. Produces the follow-up sequence with dates, drafts per rung, and the give-up-gracefully exit.

Write the follow-up messages that keep a candidate on the radar without being annoying. Use when asked to write a post-interview thank-you, a follow-up after no reply, a nudge on a stalled application, or a check-in sequence during a job search. Produces a timed sequence — what to send, when, and the exact wording — that adds value or shows interest at each step rather than just 'checking in'.

Sweep the user's REAL mail and calendar for dropped balls — threads awaiting their reply, promises they made, and replies they're owed — then draft the nudges. Use when asked what am I forgetting, what have I not replied to, who owes me a reply, or chase my open threads in Cowork. Reads sent/received mail via the Gmail connector and recent events via Calendar, finds the open loops, and produces a follow-up-list artifact plus ready-to-send draft nudges.

Fill long web forms and applications through a computer-use agent — from a fact sheet you approve, field by field, with a full transcript and nothing submitted without your word. Use when asked to fill this application for me, complete this government/vendor/insurance form, or do this registration. Produces the fact-to-field mapping, the filled form held at review, and a field-level transcript.

Untangle the spreadsheet formula nobody dares touch — decompose the seven-function nest into named readable steps, explain what it actually does (vs. what it's believed to do), and rebuild it maintainably with helper columns and modern functions. Use when asked what does this formula do, this IFERROR-VLOOKUP monster broke, make this formula maintainable, or nobody understands the sheet the analyst left. Produces the plain-language decode, the step decomposition into helper columns, the believed-vs-actual gaps, and the rebuilt version.

Articulate founder-market fit — the why-you and why-now story investors and accelerators (YC-style) probe hardest. Use when asked to write the founder story, answer 'why are you the right team', draft YC / accelerator application answers, or explain founder-market fit. Produces a sharp narrative connecting the founder's unfair insight and earned secrets to this specific opportunity — concrete, not a humble-brag.

Run a hard two-option decision through Benjamin Franklin's 'moral or prudential algebra' — the weighted pro/con method he described to Joseph Priestley in 1772 — including the part everyone skips: striking out reasons that cancel, and letting the ledger sit before deciding. Use when weighing job offers, relocations, build-vs-buy, take-the-promotion, shut-it-down decisions, or any 'I keep going back and forth'. Produces a completed decision ledger with a leaning, its strongest counter, and a revisit date.

Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000. Use when asked what should I charge as a freelancer, how do I set my consulting rate, why is my freelance rate so high, or convert my salary to a contract rate. Produces the required-revenue breakdown, billable-hours math, the hourly and day rate, and the multiplier vs the naive salary÷2000 number.

Strip a problem down to what's actually true — the physics, economics, and human basics — and rebuild the answer from there, ignoring 'how it's normally done'. Use when asked to think from first principles, why is this done this way, challenge the assumptions here, or rebuild this from scratch. Produces the problem reduced to its fundamental truths, the inherited assumptions and conventions named and questioned, and a solution reasoned up from the basics — which often looks nothing like the default because the default was just copied.

Produce frontend UI that actually looks designed — a working spacing/type system, deliberate color use, real states, and restraint — instead of the generic AI-generated interface. Use when asked to build or restyle a UI, landing page, dashboard, or component, when output 'works but looks like a prototype', or to establish the visual system for a new app. Produces working HTML/CSS (or framework components) built on an explicit token system, with hover/focus/empty/loading states included. For critiquing an existing design use design-critique; for auditing a design system use design-system-audit.

Pressure-test a fundraise by anticipating the hard investor questions and arming the founder with crisp answers. Use when asked to prep for investor Q&A, anticipate due-diligence questions, handle pushback on a raise, or build a fundraising FAQ. Produces the toughest questions an investor will ask — grouped by theme — each with the strongest honest answer and the trap to avoid.

Interview your future self about a decision or a stuck moment — a structured perspective-shift that pulls you out of present emotion and into the long view, using your own values and patterns rather than generic advice or woo. Use when someone says 'I don't know what to do', 'help me think long-term about this', 'what would future me say', or is stuck in the fog of a big decision. Produces an interview with your 5-or-10-years-older self, the themes it surfaces, and one concrete next step it points to. A structured reflection, not prediction or fortune-telling.

Bring three versions of future-you into a decision — you in a week, in a year, and in ten years — because they each want different things. Use when asked what would future me want, will I regret this, think long-term about this choice, or help me decide for the long run. Produces each future self's honest take on today's decision, where they conflict (short-term relief vs long-term payoff), whose vote should weigh most given what's at stake, and the choice that best serves the future-you that matters here.

Plan a game night that actually works for the specific people coming — the right lineup for player count, weight tolerance, and time, sequenced from icebreaker to main event, with the fallback for when someone bails. Use when someone says 'planning a game night', 'what should six of us play', 'games for my family Christmas', 'my partner hates long games', or 'we always end up arguing over what to play'. Produces a sequenced lineup with reasoning, timings, and a plan B.

Turn a plan or set of milestones into a timeline / Gantt chart. Use when asked to build a roadmap, schedule phases, show a project timeline, or visualize what happens when. Produces a ready-to-render Mermaid Gantt chart (renders live, exportable as PNG/SVG) — and, because it has real dates, the result also exports to a calendar (.ics) — plus notes on the critical path and risks.

Assess GDPR compliance and build the core records (ROPA, lawful basis, DSAR, DPIA triggers). Use when asked to get GDPR-compliant, build a Record of Processing Activities, decide a lawful basis, handle data-subject requests, or check whether a DPIA is needed. Produces a GDPR assessment — a ROPA, lawful-basis mapping per activity, DSAR workflow, DPIA-trigger screen, and a prioritised gap list.

Separate raw idea-generation from judgment so creativity isn't strangled by your inner critic — diverge with zero evaluation, then switch to hard critique. Use when asked to brainstorm properly, help me come up with ideas without shutting them down, I keep censoring my own ideas, or separate creating from editing. Produces a pure generation pass (quantity, no judging, no hedging, wild allowed), a clean break, then a separate ruthless critique pass that scores and prunes — because doing both at once produces neither.

Level up how you actually use AI — from basic one-shot questions to the techniques that get dramatically better results — matched to what you already do. Use when asked how do I get better at using AI, how do power users use AI, I feel like I'm using AI at 10%, or teach me to use AI better. Produces an honest read of how you use AI now, the two or three highest-leverage techniques to add next (giving context, iterating, showing examples, breaking down tasks, verifying), a concrete before/after on your own use, and a simple practice path — so you close the gap between basic and expert without drowning in tips.

Reclaim value stuck in gift cards, store credit, and forgotten balances — check what's left, use it before it's lost, and know your rights on expiry and cash-back. Use when asked to use up a gift card, I have store credit I forgot about, do gift cards expire, or get cash for a gift card. Produces a way to find and check balances, the rules on expiry and dormancy for your region, options to use/convert/sell partial balances, guidance on cashing out small remainders where allowed, and how to avoid the common gift-card scams.

Find a genuinely good gift for a specific person and occasion within a budget — thoughtful and non-obvious, not a generic 'top 10 gifts' list. Use when asked for gift ideas, what should I get [person], help me find a present, or I have no idea what to buy. Produces a short set of tailored ideas across price points, why each fits this person, where to get it and rough price, a safe backup, and an honest flag when you need one more detail to nail it.

Diagnose a tangled git situation and give the exact, safe commands to fix it. Use when asked to undo a commit, recover lost work, fix a bad merge or rebase, resolve a detached HEAD, unstage files, or get out of a git mess. Produces the diagnosis, the precise commands to run in order, what each does, and a recovery note if something goes wrong.

Read a GitHub repository's vital signs with keyless curl — commit recency, release cadence, issue/PR responsiveness, and bus factor — interpreted into an is-this-project-alive verdict. Use when asked is this repo maintained, check this project before we build on it, how active is this library's development, or compare these repos' health. Produces the vitals with their reads, the responsiveness sampling, the rate-limit-aware command set, and the alive/coasting/abandoned verdict.

Give someone difficult feedback — a report, a peer, a friend — so it actually lands and helps, without crushing them or dodging the point. Use when asked how do I give hard feedback, tell someone something difficult, address a problem with someone, or have a tough conversation about their [work/behavior]. Produces a read on what you actually need to say (the specific behavior and its impact, not a vague vibe), a structure that's direct and kind at once, the exact opening and words, how to invite their side and land on a path forward, and the traps (sandwiching it away, going vague, making it about character).

Turn a vague concern into specific, kind, actionable feedback. Use when asked to give feedback, write a feedback note, prepare to tell someone something hard about their work, or coach a report/peer. Produces ready-to-deliver feedback structured on situation–behaviour–impact, separating observation from judgement, with the change requested and an opening line — calibrated to praise or constructive.

Build a translation/terminology glossary so a product's key terms render consistently everywhere. Use when asked to create a glossary, a termbase, a do-not-translate list, or to keep terminology consistent across translators/locales. Produces a glossary — each source term with its approved translation per locale, part of speech, definition/context, and do-not-translate flags — ready for a CAT tool or style guide.

Build an emergency go-bag tailored to your actual household and your most likely local hazards — not a generic list — covering the people, pets, medications, documents, and hazard-specific items you'd need to grab and leave in minutes. Use when someone says 'build an emergency kit', 'what goes in a go-bag', 'prepare for evacuation', or 'emergency preparedness for my family'. Produces a personalised packing list, a grab-in-2-minutes core, storage and maintenance guidance, and per-person/per-pet additions. Points to official preparedness sources for your region.

Create go-to-market assets for any product or feature. Use when asked for a GTM plan, positioning statement, product launch plan, messaging pillars, use cases, or feature/benefit list. Produces a full GTM pack: positioning statement, messaging pillars, feature-to-benefit mapping, and role-specific use cases. For a tiered launch plan with cross-functional coordination use go-to-market-planner instead.

Build a go-to-market plan for any product launch, feature release, or new market entry. Use when planning a product launch, writing a GTM strategy, defining launch tiers, or coordinating cross-functional launch activities. Produces a tiered GTM plan with messaging, cross-functional activity tracker, success metrics, and launch day checklist. For positioning and messaging content itself use go-to-market instead.

Tell you when to stop polishing and ship — the point where more effort stops adding real value. Use when asked is this good enough, should I keep working on this, when do I stop, or I keep tweaking this and can't let go. Produces a read on whether the thing already meets its actual bar, the diminishing-returns check (is more effort improving it or just moving it around), what genuinely still needs fixing vs what's perfectionism, and a clear ship / one-more-pass / keep-going verdict — freeing you from polishing things past the point anyone will notice.

Write a structured grant proposal or funding application for any grant type. Use when asked to write a grant proposal, funding application, research grant, charitable grant, or innovation fund application. Produces a complete proposal with project summary, rationale, methodology, impact, and budget narrative.

Set up a gratitude practice that survives past week one — a specific format, a realistic cadence, and prompts that avoid the toxic-positivity trap. Use when asked to start a gratitude practice, gratitude journal help, how to be more grateful, or a gratitude routine that sticks. Produces a concrete format (what to write, how many, how specific), an anchor and cadence, variety so it doesn't go stale, and an honest note that gratitude complements — never denies — real difficulty.

Audit your own marketing and report claims for greenwashing risk before a regulator, journalist, or competitor does. Use when asked to review sustainability claims, check marketing copy for greenwash, audit environmental claims on a website or report, or pressure-test green messaging. Produces a claim inventory with substantiation status per claim, vague-term and omission flags, and a fix-or-drop recommendation for every claim.

Get through the brutal logistics after a death — who to notify, what accounts and services to close, in what order, and what genuinely can't wait vs what can wait months — with explicit permission to do it slowly and in pieces. Use when someone says 'my [person] died and I don't know where to start', 'what do I need to do after a death', 'help me handle the admin', or is drowning in the paperwork of loss. Produces a triaged task list (urgent / soon / whenever), notification scripts, and a gentle sequence. Not legal or tax advice — the humane logistics, with pointers to the professional bits.

Handle work while grieving — what to tell your manager and team, how much leave you can take, and how to function (or not) when you're back but not okay. Use when asked how do I tell my boss someone died, going back to work after a death, bereavement leave, or I can't focus at work while grieving. Produces a short message to tell your manager and team (with the boundary of how much to share), what to know about bereavement leave and options, a realistic re-entry plan for the first weeks back, scripts for when grief hits at work or people say the wrong thing, and how to ask for what you need — so work doesn't compound the loss. Not legal/HR advice; points to your policy, HR, and EAP.

Find where the food money actually goes — a no-shame ledger built from real receipts/statements, the four leak categories (waste, convenience markup, brand autopilot, the takeaway blur), a per-leak fix with realistic savings ranges, and a target budget that survives real life. Use when someone says 'we spend how much on food?!', 'audit my grocery spending', 'cut our food bill', or takeaway guilt is the household argument. Produces the ledger, the leak report, and a keep-the-joy budget.

Save the group trip from the group chat — budget alignment before anything gets booked (the awkward conversation, scripted), a decision protocol that actually books things, cost-splitting rules with real numbers for unequal rooms and champagne-taste friends, and the it's-okay-to-split-up daytime clause. Use when someone says 'we're planning a trip with friends and it's chaos', 'how do we split costs', 'one friend wants luxury and one is broke', or the trip has been 'being planned' for three months. Produces the budget-alignment script, the decision protocol, and the money agreement.

Build and prioritise a growth experiment backlog. Use when asked to plan growth experiments, prioritise growth ideas, set up a test backlog, or run a growth process/sprint. Produces a prioritised backlog — each experiment as a hypothesis with the metric it moves, an ICE/PXL score, the minimum test design, and a definition of done; plus the cadence to run it.

Document a guest incident at a hospitality venue — injury, illness, foodborne complaint, altercation, or property loss — into a clear, defensible record. Use when asked to write up a guest incident, log an accident or complaint, document a slip/fall or allergic reaction, or record an incident for insurance/legal. Produces a factual incident report (who/what/when/where, witnesses, actions taken), an immediate-response checklist, notification/escalation steps, and follow-up — objective and liability-aware, without admitting fault.

Design one habit so it actually sticks — small enough to be unmissable, anchored to something you already do, with a plan for the days you slip. Use when asked to build a habit, help me stick to [habit], I keep failing at [routine], or start a new habit. Produces a shrunk-down version of the habit, a concrete cue/anchor and time/place, a tracking method, a friction plan (make good easy, bad hard), and a get-back-on-track rule so one miss doesn't end it.

Write the handbook page that ends the repeated explanation — the answer-shaped structure (task-first, context second), the ownership and freshness header, and the write-once-point-forever discipline that turns tribal knowledge into infrastructure. Use when asked document how we do X, write the wiki page for this process, I explain this every month, or make this knowledge survive me. Produces the page with task-first structure, the header block, the worked example, and the pointer habit.

Write a PRD for a physical hardware product — target cost (BOM and landed), industrial design constraints, regulatory certifications, reliability targets, serviceability, packaging, and forecast assumptions. Use when asked to write a hardware PRD, spec a new device, define requirements for a physical product, or kick off an NPI program. Produces a complete hardware PRD with a cost stack, cert matrix, reliability spec, and EVT/DVT/PVT milestone targets.

Figure out which disasters and emergencies your specific location actually faces — and the concrete prep each one demands — so your readiness targets real risks instead of generic ones. Use when someone says 'what disasters should I prepare for', 'am I in a flood/wildfire/quake zone', 'what emergencies are likely where I live', or 'where do I start with preparedness'. Produces a ranked local-hazard list, the specific prep each demands, warning-signal and alert setup, and where to verify official risk data for your area.

Generate and pressure-test headline options across proven formulas. Use when asked for headlines, a title, a subject line, a hook, or to improve a weak headline for a page, post, email, or ad. Produces 10–15 headline options grouped by formula (benefit, how-to, number, question, curiosity, social proof), each scored for clarity and specificity, with the top 3 recommended and why.

Run a self-audit of a food establishment before the health inspector arrives, focused on the violations that actually close kitchens. Use when asked to prep for a health inspection, do a food-safety self-audit, avoid critical violations, or get ready for the health department. Produces a prioritized checklist organized by risk (critical/priority vs. non-critical), the temperature and hygiene fundamentals, a fix list with owners, and how to handle the inspector on the day.

Understand and enrol in a new country's healthcare system — how it works (public/private/insurance-based), what you're entitled to with your status, how to register with a doctor, get insurance if required, and what to do before you're covered. Use when someone says 'how does healthcare work in [country]', 'register with a doctor abroad', 'do I need health insurance in [country]', or 'I just moved and need to see a doctor'. Produces a system explainer, an enrolment checklist, a coverage-gap plan, and cost expectations. Orients and routes to official sources; not medical or insurance advice.

Write a help-center / knowledge-base article that actually resolves the issue and deflects tickets. Use when asked to write a help doc, KB article, FAQ entry, how-to, or support documentation. Produces a findable, skimmable article — task-based title, the answer up front, numbered steps, screenshots-to-add markers, troubleshooting, and related links — written so users self-serve instead of contacting support.

Scan a bill, contract, or quote for junk and hidden fees — the padding buried in the fine print — and get them questioned or removed. Use when asked to check this bill for hidden fees, are these charges legit, what am I actually paying for, or review this quote for junk fees. Produces a line-by-line read flagging suspicious/vague/padded charges, which are commonly negotiable or bogus, the questions to ask and script to dispute them, and an estimate of what you could save — across bills like telecom, hotels, cars, banking, and services.

Map HIPAA Security Rule safeguards and run a risk analysis for systems handling PHI. Use when asked to become HIPAA-compliant, assess HIPAA safeguards, prepare for handling PHI/ePHI, or scope a BAA. Produces a HIPAA assessment — the administrative/physical/technical safeguards with required-vs-addressable status, a risk analysis, BAA scope, and a prioritised remediation plan.

Generate a structured interview scorecard and interview guide for any role. Use when asked to create a hiring rubric, interview scorecard, structured interview guide, or assessment criteria for a job. Produces a scorecard with competencies, behavioural questions, and scoring guidance.

Pull the current Hacker News front page, top comments, or a topic search with zero API keys — the official Firebase API and Algolia search via curl, digested instead of dumped. Use when asked what's on Hacker News, summarize HN today, what's the discussion on this story, or has HN covered some topic. Produces a ranked digest with scores and comment counts, the discussion's actual argument threads when asked, and the rerunnable commands.

Decode HOA covenants (CC&Rs) and the fee structure before you buy into them. Use when someone asks 'what do these HOA rules actually mean', 'decode these CC&Rs', 'is this HOA going to be a problem', or 'what should I check before buying in an HOA'. Produces a restriction decode ranked by lifestyle impact, special-assessment exposure analysis, enforcement and fine mechanics, and the exact records to request before buying.

Respond to an HOA or condo-association violation notice or fine — decide whether to comply, cure, or dispute, and do it on the record. Use when asked to respond to an HOA violation, my HOA fined me, is this HOA rule enforceable, or fight an HOA notice. Produces a read on whether the citation likely holds (against the governing documents and consistent enforcement), a comply-vs-dispute recommendation, a measured response/appeal letter, the evidence and record-keeping to keep, and escalation options — flagging that HOA rules and rights are governed by your documents and local law. Not legal advice.

Turn 'I want to try [hobby]' into a real first month — the minimal starter gear, the first skills to practice, and a beginner-friendly plan that survives contact with real life. Use when asked how do I start [hobby], I want to get into [activity], what do I need to begin, or help me pick up a new hobby. Produces a cheap-as-possible starter kit (buy now vs buy later), a first-30-days progression, where to learn and find a community, and the honest quitting-points to plan around so you actually stick with it.

Decode a home renovation or repair quote — allowances that aren't prices, exclusions that become change orders, payment schedules that shift risk, and what a comparable-bids check should cover. Use when someone asks 'is this contractor quote fair', 'decode this renovation bid', 'what should be in a contractor contract', or 'why do these three bids differ so much'. Produces a section-by-section decode, the allowance and exclusion audit, payment-schedule risk analysis, and the questions that make bids comparable.

Cut your home energy bills with a prioritized plan — the free and cheap fixes first, then the upgrades that actually pay back. Use when asked how to lower my energy bill, make my home more energy efficient, reduce heating/cooling costs, or save energy at home. Produces a read on where your energy (and money) likely goes, a ranked list of fixes from free behavior changes to low-cost improvements to bigger investments with payback estimates, quick wins to start today, and what to measure — flagging that savings and any rebates depend on your home and region.

Make sense of a home-inspection report before you buy — what's serious vs cosmetic, what to negotiate, and what to investigate further. Use when asked to explain my home inspection, is this inspection finding serious, what should I negotiate after inspection, or decode my inspection report. Produces a triage of findings by severity (safety/structural/expensive vs minor/cosmetic), plain-English translations, the items worth a repair credit or price negotiation, what warrants a specialist follow-up, and a walk-vs-proceed read — flagging that the inspector and specialists are the authority.

Build a seasonal home-maintenance calendar so the small upkeep gets done before it becomes an expensive repair. Use when asked for a home maintenance schedule, what should I do to maintain my house, seasonal home checklist, or home upkeep plan. Produces a month-by-month/seasonal task list tuned to your home type and climate, grouped by system (roof, HVAC, plumbing, exterior, safety), a note of what's DIY vs pro, the highest-consequence tasks not to skip, and a simple way to track it — so upkeep is routine, not reactive.

Build a home workout plan that fits your gear, time, and goal — a real weekly structure, not a random list of exercises. Use when asked to build a home workout, make me a workout plan, exercise routine at home, or how do I work out with no gym. Produces a weekly plan matched to your equipment and schedule, each session with warm-up, main work, sets/reps, and progression, swaps for missing gear, and a way to make it harder over time — with a plain 'this isn't medical advice, stop if it hurts' note.

Generate scroll-stopping hooks — the first line of a post, thread, video, or email that decides whether anyone keeps reading. Use when asked to write a hook, an opener, a first line, a thread starter, a video cold-open, or to make something more clickable. Produces multiple distinct hook options across proven angles (curiosity, contrarian, result, story, stakes), each labelled with why it works and which platform it fits.

Navigate a hospital stay — for yourself or someone you care for — from admission through a safe discharge, so nothing critical falls through the cracks. Use when asked help me through a hospital stay, my parent is in the hospital, prepare for a hospital admission, or what do I need to know for the hospital. Produces what to bring and organize, how to stay informed and involved with the care team, the questions to ask daily, the discharge planning to start early (not at the last minute), and the home-readiness checklist for after — reducing the chaos and the dangerous gaps, especially at discharge. Not medical advice.

Apply a team's writing style consistently — extract the house style from exemplar documents into a checkable rule card, run the conformance pass on new drafts, and fix violations without flattening the author's voice. Use when asked make this match our style, why do our docs all sound different, build a style guide from our best docs, or check this draft against house style. Produces the extracted rule card, the conformance pass with per-fix reasons, and the voice-preservation line.

Diagnose why a houseplant is struggling and set a care routine it'll actually thrive on — matched to your light, home, and how much attention you'll realistically give. Use when asked why is my plant dying, how do I care for a [plant], my plant's leaves are [yellow/brown/drooping], or help me keep this plant alive. Produces a likely-cause diagnosis from the symptoms, the specific fix, a simple ongoing care routine (water/light/feed), and honest 'is this the right plant for your space' guidance.

Find and land a place to live when a criminal record keeps triggering rejections — where to apply, how to present the record, and the rights that limit how it's used against you. Use when asked how do I rent with a criminal record, landlord denied me for my background, second-chance housing, or explain my record to a landlord. Produces a target list of record-tolerant housing (private landlords, second-chance programs, certain nonprofits), a short honest explanation letter, the documents that build trust (references, income proof, rehabilitation evidence), and the fair-housing rights that limit blanket record bans — so a record narrows the search without leaving you unhoused. Not legal advice; points to housing counselors and legal aid.

Design the human approval surface for an agent system — which actions gate, how approvals batch without becoming rubber stamps, and what the audit trail must hold. Use when asked to add human oversight to an agent, design approval workflows for AI actions, decide what an agent may do autonomously, or fix approval fatigue in an existing loop. Produces an action-tier policy, approval UX spec, escalation rules, and audit-trail requirements. For specifying the whole agent use agent-spec; for the per-skill execution gates see the Execution-block pattern in SKILLSPEC §5.

Beat the afternoon crash with a realistic hydration, food-timing, and movement plan — not a caffeine-and-sugar band-aid. Use when asked how to stop the afternoon slump, I'm always tired after lunch, boost my energy, or a hydration routine. Produces a read on likely crash causes, hydration targets tied to your day, food and caffeine timing that avoids the spike-crash, movement and light micro-fixes, and a flag that persistent fatigue is worth a doctor's check.

Give yourself a gentle, structured off-ramp from hyperfocus before it costs you sleep, meals, or the rest of your life. Use when asked I've been at this for hours, help me stop working, I can't pull myself away from this, or I lost track of time again. Produces a quick reality check on how long you've been at it and what you've neglected, a save-your-place ritual so stopping doesn't feel like losing progress, a graceful stopping point, and the transition to what you actually need to do next — because for some brains, stopping is harder than starting.

Review a product/codebase for internationalization readiness before you localize. Use when asked if a product is ready to localize, to review i18n readiness, find hard-coded strings/locale bugs, or prep for going multilingual. Produces a readiness audit — externalized strings, locale-aware formatting, layout/expansion, encoding/RTL, and a prioritised list of i18n fixes to make before translation starts.

Generate a big, wide spread of ideas for anything by running the prompt through many different lenses at once, then clustering and picking. Use when asked to brainstorm ideas for, give me lots of options, help me come up with, or I need ideas for. Produces a high-volume, deliberately varied idea list generated across multiple angles (safe, wild, cheap, ambitious, weird, opposite), grouped into themes, and a shortlist of the most promising — maximizing range so you're not choosing from three obvious options.

Take back control after identity theft — the right first moves, in the right order, so you contain the damage and rebuild. Use when asked what to do about identity theft, someone stole my identity, my details are being used fraudulently, or help me recover from fraud. Produces an immediate-actions checklist (freeze, report, secure), an evidence and reporting plan for the right authorities and institutions, a dispute path for fraudulent accounts/charges, and an ongoing-monitoring setup — flagging where to use official channels and when to involve police/regulators.

Walk into an IEP or 504 meeting prepared and effective — the process decoded in plain language, the parent-input statement that gets read, the questions that make goals measurable, and advocacy that stays collaborative. Use when asked prepare me for my child's IEP meeting, what's the difference between an IEP and a 504, how do I disagree with the school's plan, or make sure the accommodations actually happen. Produces the process map, the parent-input statement, the goal-quality checklist, the meeting scripts, and the paper-trail habits.

Draft SMART IEP goals, accommodations, and present-levels statements that are measurable and compliant in spirit. Use when asked to write an IEP goal, draft special-education goals, list accommodations, or write a present-levels (PLAAFP) statement. Produces measurable annual goals with baselines, criteria, and measurement methods, plus matched accommodations. A drafting aid for educators — not legal advice; the IEP team and local requirements govern.

Write measurable IEP goals and matching accommodations for a K-12 student with an IEP or 504 plan. Use when asked to write an IEP goal, draft annual goals, make a goal measurable, or list accommodations. Produces SMART annual goals (baseline, condition, behavior, criterion, measurement) with short-term objectives and a set of accommodations tied to the student's needs — written to be legally defensible and progress-monitorable.

Organise the document pile for a visa, work-permit, or residency application — what to gather, in what order, and the common rejection triggers to avoid. Use when asked to help with a visa application, build an immigration document checklist, prepare paperwork for a work permit or green card, or organise what an application needs. Produces the categorised document checklist, the gather-in-this-order plan, the common-mistake/rejection-trigger list, and the professional-help flags. Organises the paperwork; complements the visa-interview simulator.

Write a compelling nonprofit impact or annual report that shows donors what their money achieved. Use when asked to write an impact report, an annual report, a grant outcomes report, or to report results to funders/donors. Produces a structured report — mission and year in brief, outcomes with real numbers and a beneficiary story, financials at a glance, and a forward ask — that builds trust and renews giving.

Set a boundary with in-laws or extended family kindly and clearly — the words to say, a united-front approach with your partner, and a plan for the pushback. Use when asked how to set a boundary with my in-laws, my mother-in-law keeps [X], deal with overbearing family, or what to say to my partner's family. Produces a read on the actual issue, a warm-but-firm script for the specific situation, a partner-alignment plan (the couple presents together), how to hold the line when they push back, and de-escalation so it protects the relationships rather than blowing them up.

Triage the user's REAL inbox through the Gmail connector — not a framework they run by hand. Use when asked to clear my inbox, get me to inbox zero on the actual account, triage my unread, or process my email backlog in Cowork. Reads unread via the Gmail connector, sorts every message into archive / reply-now / task / park, applies labels and archives in place, drafts the reply-now messages as real Gmail drafts. Produces a triage-report artifact of what it did and what still needs the user.

Cut inbox volume at the source — the unsubscribe purge that classifies recurring senders into kill/digest/keep, executes safely (real unsubscribes vs. spam-report vs. never-click), and installs the filters that catch the rest. Use when asked my inbox is all newsletters, mass unsubscribe safely, cut my email volume, or set up filters for the noise. Produces the sender census, the kill/digest/keep sort, the safe-unsubscribe rules, and the filter set.

Drive an email inbox to zero through a computer-use or tool-using agent — triage every message into act/delegate/defer/archive with drafts prepared, never a send. Use when asked to get my inbox to zero, triage my email hands-on, process my inbox for me, or run inbox zero. Produces the triage ledger, prepared reply drafts, and an approval-gated action plan the agent then executes read-mostly.

Write a structured incident postmortem or post-incident review. Use when asked to write a postmortem, incident report, P1/P2 review, outage report, or RCA (root cause analysis). Produces a blameless postmortem with timeline, root cause, contributing factors, impact summary, and action items.

Write a single clear, honest public statement about an incident. Use when asked to draft a public statement, a press statement, or an official response to a security breach, outage, data incident, recall, or public controversy. Produces a ready-to-publish statement — acknowledgement, what happened, impact, what you're doing, what affected people should do, and a commitment to update — plus a short and a long version.

Build in small, individually-verified increments that each leave the system working — instead of big-bang changes that fail mysteriously at the end. Use when implementing multi-part features, refactoring anything load-bearing, making large mechanical changes, or when past work produced huge diffs that were wrong somewhere unfindable. Produces the same end state as the big bang, reached through verified checkpoints you can stop at, ship from, or roll back to.

Understand index-fund investing and how to actually get started with the simplest evidence-backed approach — plus the details that quietly matter (fees, account, automation). Use when asked how do index funds work, are index funds good, how do I buy index funds, or set up index fund investing. Produces a plain explanation of what index funds are and why they beat most active investing over time, what to check before buying (expense ratio, what it tracks, the account/wrapper), how to automate contributions, and the mistakes to avoid — educational only, not financial advice.

Create a structured brief for an influencer or creator partnership campaign. Use when asked to brief an influencer, plan a creator collaboration, set up a paid partnership, or define deliverables for a sponsored content campaign. Produces a complete campaign brief with objectives, deliverables, creative guidelines, approval process, and performance metrics.

Prepare for an informational interview — the outreach, the questions, and the follow-up — so a 20-minute chat actually helps your career instead of wasting their time. Use when asked to prep for an informational interview, questions to ask someone in [field], how to reach out for a career chat, or coffee chat prep. Produces a low-friction outreach message, a focused question set tuned to your goal (exploring a field, breaking in, a specific company), how to run the conversation, what NOT to do (don't ask for a job), and a follow-up that keeps the relationship warm.

Write an infrastructure-as-code review checklist and conduct a structured review of Terraform, CloudFormation, Pulumi, or Ansible code. Use when asked to review IaC code, audit infrastructure configurations, check cloud security posture, or produce a reusable IaC review checklist. Produces a structured review report with severity-categorized findings, remediation guidance, and a reusable checklist.

Spot prompt-injection in untrusted content before an agent acts on it — the anatomy of injected instructions across the channels attackers use (email, web, files, tool outputs, documents), the tell-list, and the safe-handling response. Use when asked is this content trying to hijack my agent, check this page or email or file for prompt injection, spot the injection, or why did my agent go off-task. Produces the injection verdict with quoted tells, the channel-specific patterns, and the safe-handling protocol.

Decode a home inspection report into what's cosmetic, what's expensive, and what kills deals — with repair-cost ranges and the negotiation list. Use when asked to decode my inspection report, is this inspection bad, what should I ask the seller to fix, or should I walk after inspection. Produces a findings triage (walk-risk / negotiate / cosmetic), cost ranges per item, the ask-the-seller list, and the questions for your inspector before the objection deadline.

Download and save Instagram posts as high-resolution files. Use when asked to download, save, or archive an Instagram post, reel thumbnail, or carousel. Produces saved high-res images in a named folder, with carousel slides stitched into a single PDF; supports batch downloading of multiple URLs at once.

Write a clear insurance claim letter or appeal that supports a payout. Use when asked to write an insurance claim, file a claim letter, document a loss for insurance, or appeal a denied claim. Produces a structured claim — policy and incident details, the documented loss, the amount claimed, and the evidence — or an appeal that rebuts the denial reason, ready to submit.

Appeal a denied insurance claim — read the real reason for the denial, find the strongest grounds, and draft the appeal with the evidence that answers it. Use when asked to appeal a denied claim, my insurance claim was rejected, the insurer won't pay, or how do I fight a claim denial. Produces a decode of the denial reason, the best grounds to appeal on, a structured appeal letter citing your policy, the evidence checklist, deadlines to watch, and the external-review/ombudsman escalation. Not legal or regulated advice.

Decode a home, renters, or auto insurance policy into what's actually covered, what's excluded, and what the payout math really looks like before you need it. Use when someone asks 'what does my insurance actually cover', 'decode my policy', 'is this deductible normal', or 'actual cash value vs replacement cost'. Produces a coverage decode with real payout scenarios, ranked exclusion red flags, the ACV-vs-replacement-cost math, and the questions to ask your agent before renewal.

Elicit the real requirements by interviewing the requester BEFORE building or writing anything — one question at a time, until the brief is buildable. Use when a request is vague ('make me a dashboard', 'write something for the board'), when past deliverables missed the mark, or when the user says 'interview me' / 'ask me questions first'. Produces a validated brief: goal, audience, constraints, success criteria, and explicit non-goals — then, and only then, the work.

Prepare for a specific interview at a specific company, not just 'an interview'. Use when asked to prep for an interview, prepare answers for a role, practice for a specific company's interview, or get ready for a behavioural/case/PM round. Produces a tailored prep pack — likely questions for this role & round, STAR-structured answers from your background, your stories mapped to their competencies, questions to ask, and the gaps to shore up.

Build a structured, role-specific interview question bank with what good answers look like. Use when asked to create interview questions, an interview guide, a structured interview kit, or competency-based questions for a role. Produces questions mapped to the competencies that matter — behavioral (STAR), role/technical, and values — each with what a strong vs. weak answer shows and follow-up probes, for fair, consistent interviews.

Turn a pile of interview notes into findings that survive scrutiny — the code-then-theme pass, the counting discipline (how many actually said it), the quote selection that illustrates instead of cherry-picks, and the confidence lines a small sample earns. Use when asked synthesize these user/customer/exit interviews, what did we actually learn from the calls, turn 12 transcripts into insights, or are these themes real. Produces the coded themes with counts, the divergences preserved, the illustrative quotes, and the claims sized to the sample.

Set inventory policy for an item class: segmentation, safety stock, and replenishment method. Use when asked to set safety stock levels, segment items by ABC/XYZ, choose reorder points vs min-max, define stocking policy, or review excess and obsolete inventory. Produces a segmentation grid, per-segment service targets and safety-stock logic, a replenishment method choice per segment, and an E&O review cadence.

Solve a problem backwards — ask how to guarantee the worst outcome, then avoid all of it. Use when asked to help me not fail at, what could go wrong with, how do I avoid messing up, or think about this in reverse. Produces the inverted question (how to guarantee failure), the specific ways you'd cause the disaster, and then the plan that is simply the avoidance of each — often clearer and more actionable than trying to plan success directly, because failure modes are more concrete than success factors.

Understand the basics of investing enough to start sensibly — the core concepts, the simple default that works for most people, and the traps that separate beginners from their money. Use when asked how do I start investing, explain investing for beginners, I have money to invest but don't know how, or is investing worth it for me. Produces the essential concepts in plain language (risk, diversification, time, fees, compounding), the boring-but-effective default approach, the order of operations before you invest, and the beginner traps to avoid — educational only, not financial advice, and jurisdiction-neutral.

Draft a personal investing policy statement (IPS) — the rules someone sets for their own investing. Use when asked to define an investment strategy, set a target asset allocation, or write rules to avoid panic-driven decisions. Produces a structured IPS: goals, risk tolerance, target allocation, contribution & rebalancing rules, and what NOT to do. Educational, not regulated financial advice.

Understand which type of investment/savings account to use for your goal — the tax-advantaged vs taxable question, and which wrapper fits which money — so you don't leave free tax benefits on the table. Use when asked which account should I invest in, what's the difference between these account types, where should I put my savings, or tax-advantaged accounts explained. Produces a plain-language explainer of the common account categories (retirement/tax-advantaged, general/taxable, education, short-term), a match of your goals to the right account type, the order to prioritize them, and what to verify locally — because using the wrong wrapper can cost you real money. Not financial advice; account types are jurisdiction-specific.

Write a cold or warm-intro email to an investor that actually gets a reply — short, specific, traction-forward, with a clear ask. Use when asked to email an investor, write a fundraising outreach, request a warm intro, or craft a forwardable blurb. Produces a tight cold email, a forwardable intro blurb a mutual contact can paste, and the follow-up — all skimmable on a phone.

Build the narrative and slide structure for an investor pitch deck. Use when asked to create a pitch deck, investor presentation, fundraising deck, or startup pitch. Produces a slide-by-slide structure with narrative beats, key messages, and what each slide must prove to an investor.

Write a structured monthly or quarterly investor update. Use when asked to write an investor update, investor newsletter, board update, or startup progress report for investors. Produces a clear, credible update with highlights, metrics, challenges, and asks — in the format investors actually want to read.

Create a professional, complete invoice for a client or customer. Use when asked to write an invoice, create a bill, draft a freelance/contractor invoice, or set up an invoice template. Produces a clear invoice — your and the client's details, a unique number, line items with quantities/rates, subtotal/tax/total, payment terms and methods, and due date — ready to send and easy to pay. Not tax/legal advice.

Look up IP addresses and your own public IP with zero API keys — geolocation, ISP/ASN, and hosting flags via ip-api.com and ipify through curl. Use when asked what's my public IP, where is this IP from, whose network is this address, or is this IP a VPN/datacenter. Produces the lookup with ISP, ASN, and location fields interpreted honestly (city-level accuracy caveats included), and the rerunnable command.

Get an honest verdict on whether something you made is actually good — not the reflexive 'this is great!' but a real, criteria-based judgment. Use when asked is this actually any good, be honest is this good enough, rate this honestly, or don't just say it's great. Produces a grounded assessment against real standards for the format, a clear verdict (great / good / fine / not there yet), the specific things holding it back from the next level, and what it would take to get there — deliberately overriding AI's flattery default.

Scope an ISO 27001 ISMS and build the Statement of Applicability across Annex A controls. Use when asked to implement ISO 27001, scope an ISMS, build a Statement of Applicability (SoA), or prepare for ISO 27001 certification. Produces an ISMS plan — scope & context, risk-treatment approach, an Annex A control applicability table (the SoA), and a prioritised implementation roadmap.

Track the International Space Station live with keyless curl — where it is right now, what it's over, and when to look up, with the orbital math translated into human terms. Use when asked where is the ISS right now, is the space station overhead, when can I see the ISS tonight, or track the station for the kids. Produces the live position translated to a place name, the overhead-math explained, the visibility rules of thumb, and the rerunnable command — the library's proof that live data can also just be delightful.

Triage the user's REAL issue tracker — read open issues via the GitHub/Linear connector, label / prioritise / dedupe / flag them, and apply the safe changes — not advice on triage. Use when asked to triage my issues, clean up the backlog, label and prioritise open issues, or sort my GitHub issues in Cowork. Reads open issues via the connector, classifies by type / severity / duplicate, applies labels and priorities, and produces a triage-report artifact with the applied changes and the ones needing a human call.

Decode a job description to find what they actually want beneath the buzzwords. Use when asked to analyse a job description, decode a JD, assess fit for a role, or figure out what a posting really means before applying. Produces a decode — the real must-haves vs. nice-to-haves, hidden priorities & culture signals, red flags, an honest fit assessment, and the exact phrases to mirror in your application.

Tailors a CV and cover letter to a specific job description. Use when asked to write a cover letter, tailor a CV or resume, optimise for ATS, match a job description, or prepare a job application. Produces an ATS-optimised tailored CV summary and a personalised cover letter aligned to the role's requirements.

Write a clear, inclusive, and structured job description for any role. Use when asked to write a job description, job posting, JD, or job advert. Produces a complete JD with role summary, responsibilities, requirements, and inclusive language review.

Run a job search when you have a criminal record — where to apply, when and how to disclose, and how to turn the question into a short, confident answer instead of a dealbreaker. Use when asked how do I get a job with a felony, when do I tell an employer about my record, ban-the-box, or explain my conviction in an interview. Produces a target list of record-friendly employers and roles, a disclosure timing plan, a tight honest disclosure script (own it, pivot to now), answers to the background-check and gap questions, and the rights that protect you — so a record narrows the search without ending it. Not legal advice; points to reentry and legal-aid resources.

Write Jobs-to-be-Done (JTBD) job stories and map customer jobs across functional, social, and emotional dimensions. Use when defining user needs, writing job stories, conducting JTBD research, or reframing features around customer outcomes. Produces a job story map with opportunity scoring, pain intensity ratings, and product opportunity analysis.

Get journaling prompts tuned to what you're actually working through — a decision, a rough patch, a goal, or just building the habit — not generic 'how was your day'. Use when asked for journaling prompts, help me start journaling, writing prompts for [situation], or what should I journal about. Produces a small set of prompts matched to your intent, a simple format and cadence that fits your time, a starter for total beginners, and a gentle note on going deeper vs. when a topic is better taken to a professional.

Understand a jury-duty summons and handle it right — what's required, whether you can defer or be excused, and what to expect on the day. Use when asked what do I do about jury duty, can I get out of jury duty, jury summons help, or how does jury service work. Produces a plain-English read of the summons and obligations, the legitimate deferral/excusal/hardship options and how to request them, what to expect at selection and service, practical prep (work, pay, logistics), and a clear warning that ignoring a summons has consequences. Not legal advice.

Handle a jury summons calmly — confirm it's real, understand what's actually required, request a deferral or excusal the right way if you genuinely need one, arrange work and pay, and know what to expect on the day. Use when someone says 'I got a jury summons', 'can I get out of jury duty', 'how do I defer jury service', or 'what happens at jury duty'. Produces a response plan, a deferral/excusal request if warranted, and a what-to-expect brief. Routes to the court for anything binding; never coaches dodging a legal obligation.

Pick the karaoke song that actually fits your voice and the room — so you land it instead of dying on a key change. Use when asked what karaoke song should I sing, pick me a karaoke song, what should I sing for [occasion], or a song for my voice. Produces a few tailored song picks matched to your range and skill, why each works (and the tricky bit to watch), a crowd-pleaser vs a show-off pick, a group/duet option, and a safe fallback for when nerves hit.

Audit a knowledge base / help center for coverage, accuracy, and findability. Use when asked to audit a help center, review KB health, find documentation gaps, reduce ticket volume with better docs, or prioritise what to write/fix. Produces an audit — a health scorecard, content gaps (driven by top ticket drivers), stale/duplicate/low-findability articles, and a prioritised fix-and-create backlog.

Build an age-appropriate online-safety plan for a child — the settings, the agreements, and the conversations — that protects without just spying or banning everything. Use when asked to keep my kid safe online, parental controls setup, my child's online safety, or screen rules for kids. Produces an age-tuned plan covering device/platform settings, a family agreement, the ongoing conversations that matter more than any filter, warning signs to watch for, and how to respond to trouble — balancing safety with trust and independence.

Map what you don't know about a subject — including the gaps you can't see — so your learning targets the holes instead of re-covering what you already know. Use when asked what don't I know about X, find my knowledge gaps, what should I learn next in, or map my understanding of. Produces a picture of the subject's territory, what you already know vs the gaps, the dangerous unknown-unknowns (things you don't know you're missing), which gaps matter most for your goal, and a prioritized learn-next list — so effort goes where it counts.

Keep a team knowledge base alive — the gardener role and its weekly half-hour, the rot signals (stale pages, orphans, duplicates) and their fixes, the capture funnels that feed the garden, and the pruning that keeps search useful. Use when asked our wiki is a graveyard, who maintains the knowledge base, set up knowledge management that lasts, or people can't find anything anymore. Produces the gardener rotation, the weekly tending routine, the rot triage, and the capture funnels.

Design a KPI tracker that drives decisions instead of decorating them — the few-metrics discipline (5–9, each with an owner and a so-what), targets with honest baselines, the trend-first layout, and the review ritual where the tracker actually gets used. Use when asked set up KPI tracking for the team, build a metrics dashboard in sheets, which numbers should we track, or our dashboard exists but nobody acts on it. Produces the metric selection with kill-list, the tracker structure, the target-setting notes, and the review ritual.

Write an internal KYC/AML escalation memo: a factual time-stamped trigger description, customer-profile vs activity mismatch analysis, red-flag taxonomy mapping, outstanding information, and a recommendation with rationale. Use when asked to escalate a KYC alert, document an AML concern, write up unusual-activity findings for compliance review, or prepare an enhanced due diligence referral. Produces a structured internal escalation memo for a compliance team's decision-makers.

Write full landing-page copy that converts — section by section. Use when asked to write a landing page, homepage copy, a product page, or copy for a marketing site. Produces complete copy for every section (hero, problem, solution, social proof, features-as-benefits, objections/FAQ, final CTA) with a clear single conversion goal and one primary call to action.

Build a realistic plan to learn a language for your actual goal — travel, conversation, work, or fluency — focused on what moves the needle instead of endless app streaks. Use when asked to help me learn [language], make a language learning plan, how do I get conversational, or study a language efficiently. Produces a goal-and-level read, a prioritized plan (the high-frequency vocab and core patterns first), a daily/weekly routine mixing input, speaking, and review, how to get real practice and feedback, milestones, and honest expectations — not a promise of fluency in a month.

Searches Reddit, X/Twitter, and the broader web for recent opinions, sentiment, and signal on any topic. Use when you need to know what real people are saying about a tool, product, trend, or event in the past 30 days — cutting through SEO content to surface genuine community reaction. Produces a structured report with consensus findings, pain points, positive signals, contrarian takes, source links, and a signal confidence rating.

Turn your notice period into a handoff that makes you missed for the right reasons — the transition doc nobody has to call you about, the knowledge-transfer sessions, and the graceful goodbye mechanics. Use when asked I just resigned how do I hand off my work, write my transition document, plan my last two weeks, or what do I do before I leave my job. Produces the handoff inventory, the transition doc template filled with your reality, the KT session plan, and the last-day checklist.

Chase an overdue invoice and actually get paid — a firm-but-friendly escalation ladder that protects the client relationship until it's clear the relationship is the problem. Use when asked to chase an unpaid invoice, my client hasn't paid, write a payment reminder, or how do I get a late-paying client to pay. Produces a staged sequence of messages (gentle nudge → firm reminder → final notice → next steps) timed to the overdue days, with late-fee and work-pause options and a note on what to keep for the record.

Collect overdue invoices with a graduated escalation ladder — friendly nudge to firm notice to work-stop to final demand, each with send-ready wording and timing, plus the prevention terms that stop the next one. Use when asked my client hasn't paid me, write a payment reminder email, invoice is 60 days overdue what do I do, or client is ghosting my invoices. Produces the situation read, the escalation ladder with dates and verbatim messages, the work-stop decision point, and the payment terms that prevent reruns.

Write a developer-audience launch post — Show HN, a Product Hunt blurb, a 'we shipped X' dev blog intro, or a launch tweet thread. Use when launching a tool, library, API, or open-source project to a technical audience. Produces a credible, hype-free post that leads with what it does and why it's different, plus title options and a comment-ready first reply.

Assesses pre-launch readiness across every function and produces an explicit Go / Conditional Go / No-Go recommendation. Use when preparing for any product or feature launch, running a pre-launch review, or determining whether a release is safe to ship. Produces a function-by-function readiness status, a ranked blockers list with owners and deadlines, a risk register, and a clearly reasoned launch recommendation.

Tier a product launch (T1/T2/T3) and scope the right go-to-market effort. Use when asked to decide a launch tier, right-size launch activities, build a launch tiering framework, or plan channels and effort proportional to a launch's impact. Produces a tiering recommendation with the scoring rationale, the activities and channels for that tier, owners, and a lightweight launch checklist.

Write the layoff communications a leader has to get right once — the all-hands script, the affected/unaffected messages, and the external note, without corporate euphemism or legal risk. Use when asked to write a layoff announcement, communicate a RIF, tell the team about job cuts, or draft the difficult all-hands. Produces the full comms set: leader script, same-hour messages for affected and remaining staff, manager talking points, and the external statement — sequenced.

Plan and write the communications for a layoff or restructure with clarity and dignity. Use when asked to communicate a layoff, write a RIF/redundancy announcement, prepare manager talking points for letting people go, or plan workforce-reduction comms. Produces a comms package — sequencing plan, the all-hands/company message, the affected-employee message, a manager guide with talking points, a staying-team message, and an external/press holding line.

The first-72-hours money plan after a layoff — runway computed, deadlines caught, bleeding stopped, in priority order. Use when asked I just got laid off what do I do about money, build my layoff budget, how long can I last, or what needs to happen this week. Produces the runway number, the deadline list (healthcare, unemployment filing, equity exercise windows), the spending triage, and a one-week action checklist.

Steady the first 72 hours after being laid off — the practical, financial, and emotional moves in the right order, before panic-applying to everything. Use when asked I just got laid off what do I do, help me after a layoff, I lost my job, or just got made redundant. Produces a calm first-days checklist (understand the severance/package, protect benefits and finances, secure references and contacts, file for support), what to negotiate before signing anything, an emotional-footing note, and a bridge into the job search — not a frantic same-day scramble. Not legal or financial advice.

Turn 'I want to learn X' into a realistic, staged roadmap — the fundamentals to master first, the order that avoids overwhelm, and the milestones that prove progress. Use when asked how do I learn [skill], make me a learning plan for, where do I start with learning, or roadmap to learn X. Produces a staged path from beginner to capable (fundamentals → building blocks → real application), the highest-leverage things to learn first, the traps and dead-ends to skip, milestones to measure progress, and the best resource types for each stage — tuned to your goal and time.

Design a real project to learn a skill by building something — the fastest way to actually get good, instead of endless tutorials. Use when asked I'm stuck in tutorial hell, what project should I build to learn, learn by doing, or a project to practice X. Produces a project scoped to your level that forces the skills you want to learn, a breakdown into buildable milestones, the specific skills each milestone teaches, where to get help without copying, and a stretch to grow into — because you learn a skill by using it on something real, not by watching more tutorials.

Decode a residential lease into plain English and rank the clauses that can hurt you. Use when someone asks 'what am I signing', 'decode my lease', 'is this rental agreement normal', or 'can my landlord really do this'. Produces a clause-by-clause decode table, ranked red flags, break-clause and deposit math, questions to ask before signing, and what's actually negotiable.

Write a letter to the people you love, to be read later — the things you'd want them to know, the stories only you hold, the permission and the love that outlive you. Use when someone says 'help me write a letter to my kids/partner', 'legacy letter', 'ethical will', 'something for them to have when I'm gone', or is facing illness, aging, deployment, or simply wants to. Produces a warm, true letter in the writer's own voice — one to each person, or one to all — plus a light plan for when and how it's found. An emotional-legacy tool, not legal (it is not a will).

Draft a structured legal brief, case summary, or legal argument outline. Use when asked to write a legal brief, case note, legal memo, argument outline, or position paper. Produces a structured document using IRAC format (Issue, Rule, Application, Conclusion).

Figure out whether your problem car might qualify for a refund or replacement under lemon law or warranty — and build the paper trail to claim it. Use when asked is my car a lemon, my new car keeps breaking, lemon law help, or can I return a defective car. Produces a plausibility read against typical lemon-law criteria (repeated same defect, repair attempts, time out of service, warranty window), the records to gather, the manufacturer-claim and escalation steps, and a strong flag that lemon laws are jurisdiction-specific. Not legal advice.

Write a portfolio-level lending risk brief: concentration analysis by sector, geography and single name, vintage performance, migration matrix narrative, macro-sensitivity scenarios, top watch names, and actions. Use when asked to write a portfolio risk report, credit risk committee brief, loan book review, or quarterly portfolio quality update. Produces a structured risk brief with concentration tables, migration narrative, scenario read, watch list, and recommended actions.

Build a complete, standards-aligned lesson plan with clear objectives, a timed activity sequence, differentiation, and assessment. Use when asked to write a lesson plan, plan a class or lesson, design a teaching session, or structure instruction for a topic. Produces a ready-to-teach plan with measurable objectives, a minute-by-minute flow, materials, checks for understanding, and differentiation for varied learners.

Build a standards-aligned K-12 lesson plan with clear objectives, a timed activity sequence, checks for understanding, and differentiation. Use when asked to plan a lesson, write a lesson plan, align a lesson to a standard, or turn a topic into a class period. Produces measurable objectives, a bell-to-bell timeline (hook → instruction → practice → close), formative checks, differentiation for varied learners, and the materials list.

Write the failure story of your year, relationship, move, or big life bet in advance — imagine it's a year later and it went wrong, tell that story vividly, then mine it for the real risks and the cheap things that would have prevented them. Use when someone says 'I'm about to make a big life change', 'what could go wrong with this', 'de-risk my year', or is committing to something large and irreversible. Produces the failure narrative, the extracted risk list with preventatives, and the early-warning signs to watch. The life-scale sibling of a project premortem.

Design lifecycle marketing / CRM journeys across the customer lifecycle. Use when asked to plan onboarding emails, lifecycle/CRM campaigns, drip sequences, re-engagement or winback flows, or a messaging calendar. Produces a lifecycle plan — stage map, the trigger/message/goal for each journey, channel & timing, segmentation, suppression rules, and success metrics.

Optimise a LinkedIn profile to be found and to convert. Use when asked to write or improve a LinkedIn headline, About section, or profile, or to make a profile recruiter-friendly. Produces an optimised headline, a first-person About section with a hook and keywords, achievement-led experience bullets, and a skills/keyword list tuned for LinkedIn search.

Structure and write a literature review for any research topic. Use when asked to write a literature review, systematic review summary, narrative review, or research background section. Produces a structured review with thematic organisation, critical analysis, and gap identification.

Structure a literature review that argues, not lists — thematic synthesis from your sources with the debate mapped and the gap identified. Use when asked to write or structure a literature review, organize my sources, synthesize these papers, or find the gap for my thesis. Produces a themed review skeleton with your sources placed in conversation, the points of scholarly disagreement, the gap your work addresses, and an honest register of what you haven't read yet.

Model the cost and latency of an LLM feature before it ships and surprises the bill. Use when asked to estimate LLM API costs, set a latency/token budget, decide which model tier to use, or bring down the cost of an AI feature. Produces a cost & latency budget — token math per request, monthly cost projection, model tiering, caching/streaming levers, p95 latency targets, and a guardrail/alert plan.

Specify the safety and reliability guardrails for an LLM feature before it ships. Use when asked to define LLM guardrails, add safety controls to an AI feature, prevent prompt injection or jailbreaks, or harden a chatbot/agent against misuse. Produces a guardrails spec — threats, input/output controls, refusal and escalation policy, logging, and a red-team test set — mapped to where each control runs.

Write a load and performance testing plan for a service. Use when asked to create a performance test plan, write load testing documentation, define stress or soak test scenarios, or set performance regression gates for CI. Produces a complete test plan document with scenario definitions, k6/Locust script skeleton, threshold table, result interpretation guide, and CI integration steps.

Run a quarterly loan covenant compliance review: covenant table with required vs actual vs headroom, trend and trajectory-to-breach analysis, waiver and amendment options with pricing implications, early-warning indicators, and a watch-list recommendation. Use when asked to review covenant compliance, check covenant headroom, assess a potential covenant breach, or prepare a quarterly borrower monitoring review. Produces a structured covenant review with headroom table, trajectory analysis, and recommended actions.

Decode a personal, auto, or mortgage loan offer into what it really costs and where the traps are. Use when someone asks 'is this loan a good deal', 'decode my loan offer', 'what am I signing', or 'what will this mortgage actually cost me'. Produces a total-cost-of-loan number, APR vs advertised-rate reconciliation, ranked red flags (prepayment penalties, junk fees, rate-reset exposure), and the three questions that most change the deal.

Write a local development environment setup guide for a service or project — covering prerequisites, repository setup, environment variables, local service dependencies, database seeding, running the service, running tests, common gotchas, IDE recommendations, and first-contribution checklist. Use when asked to write a dev setup guide, create onboarding documentation for engineers, document local environment setup, or write a getting-started guide for a codebase. Produces a complete setup guide that a new engineer can follow from zero to running tests in under 30 minutes, with a troubleshooting section for the most common setup failures.

Plan the localization of a product/content for a new market — beyond translating the words. Use when asked to localize a product, plan market entry localization, prepare a localization brief, or figure out what to adapt for a new region. Produces a brief — target locales, what to translate vs. adapt vs. rebuild (UI, content, formats, imagery, payments, legal), priorities, and the risks/cultural pitfalls.

Write up a supply chain disruption — port delay, carrier failure, customs hold, or in-transit damage — as a decision-ready incident report. Use when asked to document a shipment delay, write up a logistics failure, report a customs hold, quantify a supply disruption, or draft the customer notice for a late delivery. Produces an impact-quantified incident report with containment actions, root cause, prevention items, and a customer-communication draft.

Build a plan to keep a long-distance relationship close and healthy — communication rhythms, visits, shared experiences, and a shared sense of the finish line. Use when asked to help with a long-distance relationship, how to make LDR work, we're going long distance, or keep our relationship strong apart. Produces a communication rhythm that fits both schedules and time zones, ideas for shared experiences across the distance, a visit and cost plan, ways to handle the hard parts (jealousy, loneliness, resentment), and an honest 'the plan' conversation about the end goal.

Understand the long-term care options for an older or ill loved one — from in-home care to assisted living to nursing care — so you can compare them for your situation. Use when asked what are the care options for my parent, in-home care vs assisted living vs nursing home, help me choose a care option, or explain long-term care. Produces a plain-English explainer of the main care levels and what each is for, a match to the person's needs (care level, budget, preferences), the key questions and red flags when evaluating providers, cost and funding considerations to research, and how to involve the person in the decision — a map for one of the hardest, most emotional decisions a family makes. Not medical or financial advice.

Help you write a heartfelt letter to someone you love — for an anniversary, a hard time, a birthday, or just because — that sounds like you and says what you actually mean. Use when asked to help me write a love letter, say how I feel to my partner, a heartfelt note for [occasion], or I'm not good with words. Produces a letter built from your real feelings and specifics, a structure that carries emotion without cheese, the right tone for your relationship and occasion, and phrasing in your own voice — with prompts to draw out what you want to say if you're stuck.

Negotiate a recurring bill down — internet, phone, insurance, cable, gym — with a ready-to-read script, the competitor leverage that actually moves the price, and exactly what to say when they say no. Use when asked to lower my bill, negotiate my internet/phone bill, my provider raised my price, or how do I get a discount on [service]. Produces a call-or-chat script in your words, the specific leverage for your situation, a fallback ladder (discount → downgrade → cancel lever), and a note of what to write down so the promised deal actually sticks.

Analyse a workplace power situation the way Machiavelli's The Prince (1532) would — who holds power, whose support you need, what fortune can take from you — then give both the Machiavellian read and the honest modern counterweight. Use when navigating a reorg, a new leader arriving, stakeholder politics, a territory dispute, or 'my project is caught in politics'. Produces a power map, a Machiavellian assessment, and an ethical playing-it-straight plan.

Get an open-source repo's issue backlog from 400-and-drowning to triaged-and-honest in one pass — a label taxonomy that encodes decisions, batch triage rules you can apply in seconds per issue, saved replies that stay kind at scale, and stale-bot policy set with a conscience. Use when a maintainer says 'my issues are out of control', 'triage my backlog', 'set up labels for my repo', or dreads opening GitHub. Produces the taxonomy, the triage pass rules, saved replies, and a sustainable weekly routine.

Build a real plan to make friends as an adult — where to meet people you'd actually click with, how to turn acquaintances into friends, and past the awkwardness. Use when asked how do I make friends as an adult, I'm lonely and want more friends, help me build a social life, or I have no friends here. Produces a read on where to meet the right people for you (shared interests + repeated exposure), the specific move that converts acquaintances to friends (initiate + consistency + vulnerability), a low-pressure action plan, and reassurance that the awkwardness is normal — because adult friendship doesn't happen by accident, it's built.

Turn a task you repeat every week into a reusable personal skill or prompt — so you say 'do this' instead of re-explaining it every time. Use when asked help me make a skill for, turn this repetitive task into a template, I do this every week, or create a reusable prompt for this. Produces a captured spec of the repetitive task (its inputs, steps, and what good output looks like), a reusable skill/prompt you can invoke by name, and guidance on saving and refining it — lowering the barrier from AI user to AI author, one weekly task at a time.

Plan a new manager's first 90 days — first-time or new-to-team — as listen/decide/move phases: the 1:1 listening tour with real questions, the early-judgment traps, the quick-wins filter, and the 30/60/90 artifacts. Use when asked I just became a manager what do I do, plan my first 90 days as a manager, taking over an existing team, or new manager 30-60-90 plan. Produces the phased plan, the listening-tour question set, the team assessment framework, and the day-one and week-6 artifacts.

Work more effectively with your manager — communicate, align, escalate, and get what you need. Use when asked how to manage up, work better with a boss, get buy-in from your manager, escalate without overstepping, or prepare to raise something with leadership. Produces a managing-up plan — what your manager needs and how they operate, how to frame your ask, what to bring vs. escalate, and the message.

Plan a full-funnel marketing strategy from awareness to retention. Use when asked to build a marketing funnel, map the customer journey to tactics, plan demand generation, or diagnose where a funnel leaks. Produces a funnel plan — stage definitions, the metric and conversion target per stage, channels & tactics, the biggest leak, and a 90-day focus.

Apply behavioral-psychology principles to a marketing asset or decision — ethically. Use when asked to make copy/a page/an offer more persuasive, apply psychological triggers, reduce friction, or understand why something does/doesn't convert. Produces the relevant principles (social proof, scarcity, anchoring, loss aversion, etc.), how to apply each to the specific asset, and a line on staying ethical (no dark patterns).

Audit and optimize a marketplace listing (Amazon, Etsy, eBay, Walmart) to rank and convert. Use when asked to optimize an Amazon/Etsy listing, improve marketplace SEO, fix a product listing that isn't selling, or write keyword-rich titles and bullets. Produces a prioritised optimization — title, bullets, backend keywords, A+/description, images plan, and conversion fixes — mapped to how that marketplace ranks and shoppers decide.

Treat neurodivergent masking as a daily energy budget — audit what passing as neurotypical actually costs you, where the spend is worth it, where you can safely drop the mask, and how to plan a heavy-masking day so you don't crash after. Use when someone says 'I'm exhausted from masking', 'work drains me and I don't know why', 'how do I unmask safely', or is autistic/AuDHD/ADHD and burning out socially. Produces a mask-cost audit, a spend/drop map, and a recovery plan. A self-knowledge tool, not a diagnosis or therapy.

Design an MCP server for a product — the tool surface, auth model, and safety boundaries that make it genuinely usable by AI agents. Use when asked to spec an MCP server, expose a product to agents, design tools for Claude or other MCP clients, or review why an existing MCP server performs badly. Produces a complete server spec: a small task-shaped toolset with agent-tested descriptions, auth and scoping decisions, error design, and an explicit not-exposed list.

Turn what's actually in the fridge and 90 minutes on Sunday into a week that mostly feeds itself — a cook-once-eat-thrice batch plan, the component method (bases, proteins, sauces that recombine so leftovers don't bore you), honest food-safety day-counts flagged, and the Thursday problem solved in advance. Use when someone says 'meal prep my week', 'what do I cook with what I have', 'we spend too much on takeaway', or 'I'm sick of eating the same thing four days'. Produces the Sunday cook plan, the recombination map, and the shopping delta.

Read a garage quote or invoice like someone who can't be padded — which line items connect to your actual symptom, which are while-we're-in-there additions, the questions that make soft lines disappear, when a second opinion pays for itself, and the scripts for declining work without souring the relationship. Use when someone says 'is this mechanic quote fair', 'the garage called and now it's £900', 'do I really need all this', or before authorizing repairs. Produces a line-by-line decode, the callback questions, and the authorize/decline/second-opinion sort. Not a diagnosis — it's the interrogation of one.

Write a media pitch or press outreach email for any story or announcement. Use when asked to write a media pitch, journalist outreach email, press pitch, or story angle for PR. Produces a concise pitch with a compelling news angle, journalist-specific hook, and clear call to action.

Prepare to get the most out of a medical appointment — for yourself or someone you care for — with the right questions, the information to bring, and how to make sure you're heard. Use when asked help me prepare for a doctor's appointment, questions to ask the doctor, advocate for my parent at the doctor, or how do I get the most from this appointment. Produces a focused list of what to raise and ask (prioritized, since time is short), the history and info to bring, note-taking and 'teach-back' tactics so you actually understand, how to speak up if dismissed, and what to confirm before leaving — not medical advice, but better navigation of care.

Decode an itemized medical bill or EOB into plain English and find the charges worth disputing. Use when someone asks 'why is my medical bill so high', 'decode my hospital bill', 'what is this EOB saying', or 'can I negotiate this bill'. Produces a line-by-line decode, duplicate and unbundling flags, balance-billing red flags, and ready-to-read scripts for requesting an itemized bill, financial assistance, and a negotiation call.

Request your medical records and actually get them — what to ask for, the request letter that can't be shuffled aside, the timelines and fee rules to cite (jurisdiction-flagged), and the escalation path for stonewalls. Use when asked how do I get my medical records, write a records request, my doctor's office won't send my records, or what records should I collect. Produces the itemized request letter, the delivery and format choices decoded, the follow-up ladder, and the personal health-file structure for keeping them.

Set up a system to manage medications safely — for yourself or someone you care for — so doses aren't missed, doubled, or dangerously combined. Use when asked help me manage medications, keep track of my parent's pills, set up a medication system, or I keep forgetting my meds. Produces an organized medication list (what, dose, when, why), a routine and reminder setup that fits the person, a refill-tracking method so nothing runs out, safety checks (interactions and duplications to raise with a pharmacist), and an emergency-ready summary — because medication errors are common and dangerous, and a system prevents most of them. Not medical advice.

Pull the action items and decisions out of meeting notes or a transcript — each with an owner, a due date, and enough context to become a ticket — plus the open questions. Use when asked to extract action items, turn these notes into tasks, who owns what from this meeting, or pull the to-dos from this transcript. Produces the ticket-ready action list (owner + due + context), the decisions made, the open questions with no owner yet, and a flag for any 'someone should…' that never got assigned.

Price meetings in money and focus — the attendee-hours × loaded-rate math, the recurring multiplier that turns a weekly 30-minutes into a real annual number, and the cost-vs-outcome read that decides what the price buys. Use when asked what does this meeting cost, price our meeting culture, is this recurring meeting worth it, or make the case for fewer attendees. Produces the cost computation with stated assumptions, the recurring annualization, the cost-per-outcome read, and the reduction levers ranked.

Structure and format meeting notes following PM best practices. Use when asked to create meeting notes, format discussion notes, capture action items, or document decisions from any meeting type. Produces structured notes with decisions, action items (owner + deadline), open questions, and next steps.

Prepare the user for a REAL upcoming meeting by pulling the actual Calendar event, its attendees, the linked Drive docs, and the last email/Slack thread — then producing a brief. Use when asked to prep me for my next meeting, get me ready for the 2pm, or what do I need for the sync with X in Cowork. Reads the event via the Google Calendar connector, gathers the attached and related material via Drive/Gmail, and produces a one-page meeting-brief artifact with objective, context, open threads, and the questions to ask.

Arrive at a meeting armed in fifteen minutes — the prep pack: what this meeting decides, your position with its reasons, the other attendees' likely stances, the questions to ask, and the outcome you're steering toward. Use when asked prep me for this meeting, what should I know before this call, I have 15 minutes before a big meeting, or help me not wing it. Produces the one-page prep pack with position, stances, questions, and the walk-away-with list.

Set the shared-space norms that end the small daily frictions — meeting room booking discipline (the ghost-booking cure), hybrid-call room behavior, the shared kitchen/space contracts, and the enforcement that works without a hall monitor. Use when asked set office space norms, rooms are always booked but empty, hybrid meetings are terrible for remote people, or write the office etiquette guide. Produces the norms card by space type, the ghost-booking fix, the hybrid-room checklist, and the no-hall-monitor enforcement design.

Build your personal early-warning system for meltdowns or shutdowns — your specific rising signs, the triggers that stack, what actually helps at each stage, and a plain plan you can hand to the people around you. Use when someone says 'my meltdowns come out of nowhere', 'help me not shut down', 'I need a plan for when I'm overwhelmed', or supports someone who melts down or shuts down. Produces a staged warning map, a per-stage response plan, and a shareable one-pager. A self-management tool — not a clinical or crisis service.

Capture a life story — your own or a parent's/grandparent's — into a keepsake, using good interview questions and a structure that turns memories into readable stories. Use when asked to help write a memoir, capture my parent's/grandparent's story, record family history, or preserve someone's life story. Produces a question set that unlocks real memories (not just dates), a session plan for interviewing over time, a structure to organize stories into chapters or themes, prompts to draw out detail and emotion, and options for the final form — so the stories are saved before they're lost.

Keep your AI memory/context file (MEMORY.md, CLAUDE.md, custom instructions) healthy over time — pruning the stale, adding the new, and keeping it sharp so your AI keeps getting you right. Use when asked review my memory file, my AI context is outdated, clean up my CLAUDE.md, or maintain my AI instructions. Produces a review of your existing memory/instructions file (what's stale, contradictory, bloated, or missing), edits to prune and sharpen it, additions from recent patterns worth remembering, and a light maintenance habit — because a memory file that isn't tended drifts from who you actually are, with a privacy check on what should never be stored.

Cost a menu item to a plate cost and food-cost percentage, then price it for a target margin. Use when asked to cost a dish, calculate food cost percentage, price a menu item, or engineer a menu for profitability. Produces a plate-cost breakdown (ingredient × yield × price), the food-cost %, a suggested price for the target margin, and menu-engineering flags (star / plow-horse / puzzle / dog) so the operator knows what to promote, reprice, or cut.

Write the short message you freeze on — a thank-you, condolence, congratulations, apology, or a graceful 'no' to an invite — warm, specific, and in your own voice. Use when asked to write a thank-you note, a sympathy/condolence message, a congratulations, a quick apology, or how to politely decline. Produces two or three ready-to-send options at the right length for the channel, plus the one line that carries the message, never generic filler.

Build a messaging framework (message house) that the whole company can use consistently. Use when asked to create messaging, a value proposition, a message house, key messages, or to make marketing/sales/product say the same thing. Produces a messaging framework — audience & value proposition, the one-line positioning, 3 message pillars with proof points, objection handling, and a words-we-use/avoid list.

Find out how a dashboard, KPI report, or metrics slide is lying to you — before you repeat its story in a bigger room. Use when numbers feel too tidy, a narrative rests on one chart, or you inherited metrics you didn't define. Produces a deception audit: every metric graded for the eleven classic distortions (denominator games, survivorship, y-axis crimes, cherry-picked windows…), the story the data would tell under honest framing, and the three questions to ask the metric's owner.

Define a metric in a semantic layer so it means one thing everywhere. Use when asked to define a metric, build a semantic layer / metrics layer entry, stop 'revenue means three things' problems, or write a metric definition for dbt MetricFlow / Cube / LookML. Produces a metric definition — exact formula, the base measure & aggregation, dimensions, filters, grain, edge cases, and a tool-ready spec.

Decompose a north-star metric into a driver tree — the inputs and sub-inputs that actually move it — so a team knows which levers to pull. Use when asked to build a metric tree, break down a north-star metric, map metric drivers, or find the inputs behind an output metric. Produces a hierarchical tree from the top metric down to actionable input metrics, with the relationships, the highest-leverage levers, and what to instrument.

Build a metrics framework for any product, team, or business. Use when asked for a metrics tree, KPI framework, North Star metric, AARRR funnel, HEART framework, or OKR metrics. Produces a structured metrics hierarchy from North Star down to leading indicators, with measurement guidance.

Plan a deliberate career break — 3 to 12 months off between chapters — with honest runway math, the re-entry story rehearsed before you leave, health/visa/pension admin by country flagged, and kill criteria for coming back early. Use when someone says 'I want to take 6 months off', 'micro-retirement', 'sabbatical planning', 'quit and travel', or 'can I afford a break'. Produces a runway budget, a break charter with kill criteria, and the future-interview answer written in advance.

Write the small UI text that guides users — buttons, labels, tooltips, CTAs, confirmations. Use when asked to write microcopy, button/CTA text, form labels, tooltips, helper text, or to make UI wording clearer. Produces specific, action-oriented microcopy with options and rationale, matched to the moment and the product's voice — concise, scannable, and free of jargon.

Design a microservices decomposition for a monolith or new system, defining service boundaries, ownership, communication patterns, and migration plan. Use when asked to decompose a monolith, define service boundaries, design a microservices architecture, or plan a strangler-fig migration. Produces a bounded context map, service inventory table, communication pattern decisions, data ownership matrix, migration roadmap, and risk register.

Move a team's files to a new platform without losing work or a week — the pre-migration freeze, the verified copy, the permissions remap, the cutover announcement, and the old-system read-only afterlife. Use when asked we're moving from Dropbox to Drive, migrate our files to SharePoint, plan the file migration day, or how do we switch platforms safely. Produces the migration runbook: freeze window, copy-and-verify steps, permissions mapping, the cutover comms, and the rollback line.

Turn a topic, brainstorm, or document into a structured mind map. Use when asked to brainstorm around a theme, organize ideas, break a topic into branches, or summarize something as a mind map. Produces a ready-to-render Mermaid mindmap (renders live, exportable as PNG/SVG) plus a short note on the structure chosen.

Document a deployed ML/AI model so others can use it responsibly. Use when asked to write a model card, document a model's intended use and limitations, or prepare an AI model for review/launch. Produces a complete model card — intended use, training data, evaluation metrics across slices, limitations, ethical considerations, and a deployment checklist.

Plan the migration of an LLM feature from one model to another without breaking production. Use when a model is being deprecated, a newer model looks better or cheaper, or when asked how to upgrade models safely, run shadow traffic, or set rollback criteria for a model change. Produces a phased migration plan with eval gates, shadow/canary stages, prompt-adaptation notes, and rollback triggers. For choosing which model in the first place use model-selection-advisor.

Choose the right LLM for a task by trading off quality, cost, latency, and constraints. Use when asked which model to use, whether to upgrade/downgrade a model, how to cut LLM costs without hurting quality, or to justify a model choice. Produces a recommendation with the decision criteria, a per-option comparison, a routing strategy (cheap-by-default, escalate when needed), and how to validate the choice with an eval.

Break a stuck, stalled week with three tiny wins sequenced for momentum — because motion creates motivation, not the other way around. Use when asked I'm in a rut, help me get unstuck this week, I've stalled on everything, or I need momentum. Produces three small, genuinely-achievable wins ordered so each fuels the next, a deliberately easy first one to prove motion is possible, the dopamine logic behind the sequence, and a reframe that you don't need motivation to start — starting creates it — turning a paralyzed week into a moving one.

Untangle the money beliefs and emotions that quietly sabotage your finances — the scripts from childhood, the avoidance, the guilt or fear — and reset to a healthier relationship with money. Use when asked I have a bad relationship with money, why do I self-sabotage financially, money stresses me out, or fix my money mindset. Produces a look at your money story and where it came from, the specific beliefs driving unhelpful behaviors (avoidance, overspending, scarcity, guilt), a reframe toward a healthier stance, and small behavior shifts that follow — because money behavior is often emotional, not just mathematical. Not therapy or financial advice.

Decide where your next dollar should go — the order to tackle emergency fund, high-interest debt, retirement match, and saving/investing — so you stop guessing and build momentum. Use when asked what should I do with my money first, pay off debt or save, where to put extra money, or help me prioritize my finances. Produces a personalized order-of-operations for your situation, the reasoning for each step, where you are on the ladder and the next concrete move, and honest flags on the judgment calls. Educational — not financial advice.

Write a monitoring setup guide for a service — defining what to measure, how to alert on it, and how to build the observability stack covering the four golden signals, business metrics, log strategy, distributed tracing, alerting rules, dashboard layout, and observability debt. Use when asked to set up monitoring for a service, define alerting strategy, write an observability plan, create a dashboard specification, or document logging standards for a team. Produces a metric definitions table, alert rules specification, dashboard layout wireframe, log schema, tracing setup checklist, and monitoring gap analysis.

Interviews you across 15 questions to capture your role, topics, sources, exclusions, and format preferences, then writes a master prompt you can paste into a scheduled task or Claude Code Routine. Use when you want to set up a personalised daily news brief, build a reusable morning news prompt, or create an automated intelligence briefing. Produces a confirmed summary of your preferences, a ready-to-paste master prompt, and setup instructions for both Cowork Scheduled Tasks and Claude Code Routines.

Decode a moving company estimate — binding vs non-binding, the weight and cubic-feet games, valuation vs insurance, and the red flags that precede hostage-load stories. Use when someone asks 'is this moving quote legit', 'decode my moving estimate', 'binding vs non-binding estimate', or 'how do I avoid moving scams'. Produces an estimate-type decode with what-you'll-actually-pay scenarios, ranked red flags, the valuation decode, and the questions that separate real movers from brokers.

Turn a move date into a calm, timed plan — every address change, utility switch, deposit-recovery step, and packing wave scheduled so nothing gets missed at the worst possible moment. Use when asked to plan a house move, I'm moving and don't know where to start, make a moving checklist, or what do I need to do before I move. Produces a countdown checklist by week, the address-change and utilities list, a deposit/deposit-recovery track for renters, a room-by-room packing plan, and a moving-day and first-night essentials kit — tuned to your situation.

Decode a moving-company quote and spot the lowball, the padding, and the outright scam before you book. Use when asked to check a moving quote, is this mover legit, compare moving estimates, or avoid moving scams. Produces a read on the quote type (binding vs non-binding vs 'not to exceed') and what it really means, the red flags of moving scams (big deposits, no in-home/video survey, low-then-hostage pricing), the questions to ask and credentials to verify, an apples-to-apples comparison, and how to protect yourself on moving day.

Synthesises user signals from multiple research sources into a unified, weighted insight brief. Use when you have data from interviews, support tickets, NPS verbatims, app reviews, or sales calls and need to reconcile contradictions, surface the underlying need behind requests, or answer 'what are users really telling us'. Produces ranked insights with confidence ratings, source weighting rationale, divergent signal analysis by user segment, and a research gap identification section.

Map your real energy through the day and week, then match your tasks to it — hard things when you're sharp, easy things when you're not. Use when asked when should I do my hard work, map my energy, why am I so unproductive at certain times, or schedule around my focus. Produces a picture of your energy peaks, troughs, and patterns from your own observations, a task-to-energy matching plan (deep work at peaks, admin at troughs), the traps you're currently falling into, and a realistic daily shape — because fighting your natural rhythm wastes your best hours on your worst tasks.

Turn a mistake into a reusable lesson — a short, unsentimental 'here's what happened and the rule so it doesn't happen again' entry you can actually keep. Use when asked help me learn from this mistake, I keep making the same error, capture this lesson, or turn this failure into something useful. Produces an honest, blame-free autopsy of what happened, the real root cause (not the surface one), the specific rule or trigger that prevents a repeat, and a one-line entry for your growing 'failure museum' — because unexamined mistakes repeat and examined ones compound into wisdom.

Get through the 40-institution slog of changing your name — after marriage, divorce, transition, or just because — in the right order, so one update doesn't block the next, with nothing important forgotten. Use when someone says 'I changed my name and don't know where to start', 'update my name everywhere', 'name change checklist', or is planning any legal name change. Produces an ordered update checklist (what unlocks what), a personalized institution list, and templates. Not legal advice — the logistics; the legal deed/court step is flagged, not performed.

Turn a vague bad mood or 'off' feeling into a precisely-named emotion and its likely cause — because naming it is what starts to defuse it. Use when asked I feel off and don't know why, help me figure out what I'm feeling, I'm in a weird mood, or why am I upset. Produces a short, gentle inquiry that distinguishes the actual emotion from the fog (anxious vs frustrated vs lonely vs overwhelmed), its most likely trigger, what the feeling might be pointing at, and one small thing that tends to help that specific state — never diagnosing, just helping you locate yourself.

Analyses a Non-Disclosure Agreement clause by clause and flags unusual terms, one-sided provisions, and negotiation points. Use when reviewing an NDA, mutual NDA, confidentiality agreement, or non-disclosure deed before signing or countering. Produces a plain English verdict, clause-by-clause risk analysis, and a prioritised negotiation checklist — always with a disclaimer that qualified legal advice is required before signing.

Handle a neighbor conflict — noise, boundaries, parking, shared costs, pets — with a measured approach that de-escalates first and keeps a paper trail if it has to go formal. Use when asked to deal with a neighbor dispute, my neighbor is [too loud / over the boundary / blocking me], how do I talk to my neighbor about, or write a letter to my neighbor. Produces a read on the situation, a calm first conversation or friendly note, a firmer written follow-up if that fails, the documentation habit for escalation, and the right next step (mediation / landlord / HOA / council) — steering away from making it worse.

Produce a personal net-worth statement — assets minus liabilities — and a way to track it. Use when asked to calculate net worth, summarize finances, or set up net-worth tracking. Produces a categorized assets/liabilities statement, the net-worth figure, liquidity and debt ratios, and a tracking cadence. Educational, not regulated financial advice.

Network in a way that actually works for introverts — depth over breadth, one-on-one over rooms, and energy managed — instead of forcing yourself to work a crowd. Use when asked how do I network as an introvert, networking drains me, help me network without the small talk, or introvert-friendly networking. Produces an approach that plays to introvert strengths (deep 1:1 conversations, listening, follow-up, written outreach), a plan for the events you can't avoid (arrive early, one real conversation, leave), energy-management tactics, and how to build a genuine network without pretending to be an extrovert.

Write networking messages that actually get replies — warm, specific, and easy to say yes to — for reconnecting, cold outreach, referrals, or asking for advice. Use when asked to help me network, write a message to reconnect / to a recruiter / to someone at [company], reach out for a referral, or networking message help. Produces a message tuned to the relationship and the ask, a specific and genuine hook, a low-friction request the person can easily grant, follow-up guidance, and a note on giving value — not a generic 'pick your brain' that gets ignored.

Turn 'we're having a baby' into a calm, timed logistics plan — the admin, leave, registrations, and prep that has to happen, sequenced so nothing critical is left to the newborn haze. Use when asked to plan for a new baby, what do I need to do before the baby comes, new baby checklist, or help me prepare for a newborn. Produces a trimester/countdown checklist of the non-obvious admin (leave, benefits, insurance, registration, pediatrician, essentials), what to set up before vs after birth, and a lean 'actually need it' gear list — not a fear-driven mega-list.

Plan your first 90 days as a new manager — build trust, learn before changing, and avoid the classic first-time-manager mistakes. Use when asked to help me as a new manager, I just became a manager, first-time manager advice, or my first 90 days managing a team. Produces a phased 90-day plan (listen and learn, then set direction, then adjust), how to run your first 1:1s, the mindset shift from doer to enabler, common traps to avoid (doing it all yourself, changing too fast, avoiding hard conversations), and early wins that build credibility.

Turn the pre-baby chaos into a staged logistics plan — leave paperwork, insurance deadlines, the hospital-bag/home-setup checklists, and the first-two-weeks operating plan with named owners. Use when asked help me prepare for a baby, what do I need to do before my due date, set up our parental leave plan, or newborn logistics checklist. Produces the countdown timeline by trimester-week, the deadline-driven paperwork list, and the week-1–2 operating plan both partners can run exhausted.

Turn a pile of newsletters and subscriptions into one skimmable brief — the items that matter to YOUR interests extracted with sources, the noise dropped with a count, on a cadence that replaces daily trickle-reading. Use when asked digest my newsletters, summarize what my subscriptions said this week, what did I miss that I actually care about, or make my reading pile useful. Produces the interest-filtered brief with per-item sources, the dropped-with-reasons ledger, and the cadence that makes trickle-reading obsolete.

Write a full creator newsletter issue — subject line, preview text, hook, body with a clear takeaway, and a CTA — in the writer's voice, for Substack, beehiiv, ConvertKit, or email. Use when asked to write a newsletter, an email issue, a Substack post, or to turn notes/a topic into a sendable newsletter. Produces a ready-to-send issue with subject-line options and a skimmable structure. Distinct from B2B drip/nurture sequences.

Set up a note-taking system that you'll actually use and that makes your notes findable and useful later — not a graveyard of notes you never reopen. Use when asked help me take better notes, set up a note system, my notes are a mess, or how should I organize my notes. Produces a system matched to your actual need (capture, study, or thinking), a simple capture-and-organize flow, a findability method (tags/links/structure), the review habit that keeps notes alive, and a warning against over-engineering the system instead of using it.

Automates NotebookLM from Claude Code using browser automation via the Claude Chrome extension — creating notebooks, adding sources, and triggering outputs without manual clicking. Use when you want to create a NotebookLM notebook, add URLs or documents as sources, or generate mindmaps, audio overviews, or briefing docs programmatically. Produces a confirmed checklist of completed actions and a direct link to the notebook.

Strips AI writing patterns from text and rewrites it to sound genuinely human — removing the statistical defaults, then adding earned voice calibrated to genre (opinion pieces get a person's voice; docs and summaries stay neutral) without ever faking humanity. Use when a draft reads as AI-generated, over-polished, or rhythmically uniform — including blog posts, emails, LinkedIn posts, or any prose that needs to sound like a real person wrote it. Produces a pattern audit, side-by-side comparison, itemised change log, and clean rewritten output ready to paste.

Work through who and what has to be notified after someone dies — the people, agencies, banks, and accounts — in a sane order, so nothing critical is missed while grieving. Use when asked who do I need to notify when someone dies, what to do after a death checklist, or how do I handle my parent's accounts after they died. Produces an ordered notification checklist (immediate people, then government/SSA, then financial, then subscriptions/digital), what each notification needs (death certificates, account numbers), how many death certificates to order, what to stop vs. transfer vs. close, and the scams that target the newly bereaved — so the administrative avalanche becomes a calm sequence. Not legal or financial advice; points to probate/estate resources.

Clean the user's REAL Notion database — read it, find stale/incomplete/duplicate entries, and fix them via the connector — not advice on keeping Notion tidy. Use when asked to clean up my Notion database, my tracker is a mess, find the stale and duplicate entries, or tidy my projects DB in Cowork. Reads the database via the Notion connector, audits for staleness / missing required fields / duplicates / status drift, and produces a hygiene-report artifact plus the applied fixes (with a preview-and-confirm step before any change).

Translate both directions across the neurodivergent↔neurotypical gap at work — decode what an indirect message actually meant ('let's circle back' = no), and rewrite your direct message so it lands without you having to sand off the point. Use when someone says 'what did my manager actually mean', 'my message came across wrong again', 'why do people think I'm blunt', or is ND navigating an NT workplace. Produces a decode of the received message and/or a rewrite of yours, with the reasoning shown so you learn the pattern.

Compare two or more job offers as total-comp curves over four years — vesting cliffs, bonuses, 401(k) match, and the crossover year computed, not vibed. Use when asked to compare job offers, which offer pays more over time, model my equity vesting, or is the startup offer actually worth it. Produces a year-by-year and cumulative comp table per offer, the crossover analysis, and negotiation levers ranked by dollar impact.

Draft a job offer — the written offer letter and a verbal-offer script. Use when asked to write an offer letter, a job offer, an employment offer, or to prepare to extend/verbal an offer to a candidate. Produces a clear, warm offer letter (role, comp, start, key terms, contingencies, acceptance) plus a verbal-offer call script — flagging that employment terms need HR/legal review. Not legal advice.

Replace ad-hoc interruptions with office hours that actually get used — the slot design (cadence, length, format), the routing rules that tell people what goes there vs. what shouldn't wait, and the empty-hours and overflow failure modes handled in advance. Use when asked set up office hours, I'm interrupted constantly but want to stay accessible, my office hours sit empty, or design expert time for the team. Produces the slot design, the routing card, the facilitation format, and the tuning rules.

Run an office move or reconfiguration without losing a week of work — the dependency-ordered plan (internet lead times rule everything), the workstream owners, the comms that keep the team functional through the chaos, and the day-one-that-works checklist. Use when asked plan our office move, we're moving floors/buildings in six weeks, who owns what in the move, or make day one at the new office not a disaster. Produces the workstream map with owners, the dependency timeline, the team comms plan, and the day-one readiness gate.

Plan a team offsite that earns its cost — the purpose split (connection vs. decisions vs. planning, weighted on purpose), the agenda that alternates work and air, the logistics runbook, and the follow-through that makes Monday different from before. Use when asked plan our team offsite, design two days for the team, make this offsite not a waste, or what do we actually do at the offsite. Produces the purpose weighting, the day designs, the logistics checklist, and the commitments-capture that survives re-entry.

Create well-structured OKRs (Objectives and Key Results) for product teams, startups, and individuals. Use when asked to write OKRs, set quarterly goals, define key results, or review existing OKRs. Produces a complete OKR set with objectives, measurable key results, baselines, and a scoring guide.

Design the buddy system that makes new-hire onboarding human — the buddy's actual job (context and safety, not training), the 30-day touchpoint plan, the ask-me-anything contract, and the buddy selection that avoids the two classic miscasts. Use when asked set up an onboarding buddy program, I'm buddying the new hire what do I do, our onboarding is docs with no humans, or the new person is drowning quietly. Produces the buddy role definition, the touchpoint schedule, the first-week script, and the escalation line.

Write in-product onboarding copy that gets users to value fast. Use when asked to write onboarding copy, a welcome flow, product tour/tooltips, setup steps, or activation messaging. Produces the copy for an onboarding flow — welcome, the guided steps/tooltips toward the first win, progress and empty-to-active nudges, and a success moment — focused on the activation outcome, not a feature tour.

Create a structured 30/60/90-day onboarding plan for any new hire. Use when asked to write an onboarding plan, new hire plan, 30-60-90 day plan, or first 90 days roadmap. Produces a week-by-week plan with milestones, meetings, learning goals, and success criteria.

Write a structured end-of-shift on-call handoff so the incoming engineer inherits state, not surprises. Use when asked to write an on-call handoff, oncall handover, shift handoff, pager handoff, or end-of-week SRE summary. Produces a handoff note with open incidents, watchlist alerts, in-flight investigations, recent changes, and one-line asks.

Write an on-call runbook for a service — covering alert definitions, escalation paths, common incident responses, and on-call handoff procedures. Use when asked to write an on-call guide, create alert runbooks, document escalation procedures, or prepare an on-call handoff document. Produces a structured on-call runbook with per-alert response procedures, escalation matrix, diagnostic commands, and handoff template.

Get the single honest thing you're avoiding about a situation — said kindly but not softened away. Use when asked tell me the hard truth, what am I avoiding here, be honest with me about this, or what do I not want to hear. Produces the one thing you already half-know but keep sidestepping, said plainly and with care (not cruelty), why it's hard to face, and what facing it would actually make possible — because the truth you're avoiding is usually the one that would change things, and a kind voice can say what your own keeps ducking.

Prepare for a 1:1 so it drives outcomes instead of becoming a status update. Use when asked to prep for a one-on-one, build a 1:1 agenda, prepare to talk to your manager (or a report), or raise something hard in a 1:1. Produces a focused 1:1 agenda — your top topics with the outcome you want for each, the asks, updates kept brief, and growth/feedback threads, tuned to direction (with your manager vs. with a report).

Distil anything — a startup, product, project, or idea — into a single persuasive page. Use when asked to make a one-pager, a one-page summary, a leave-behind, a startup/product one-sheet, or a tl;dr brief. Produces a structured single page — headline + tagline, the problem, the solution, why-now/proof, and a clear ask/CTA — designed to be skimmed and remembered, ready to export as a typeset PDF.

Plan and promote an open house that draws buyers and generates leads. Use when asked to plan an open house, market an open house, or create an open-house checklist. Produces a plan — timing and promotion across channels, prep and staging checklist, a day-of run sheet, lead capture, and follow-up — so the event drives real interest and the agent leaves with leads, not just foot traffic.

Read a contract the way the counterparty's lawyer will — hunting for leverage, not fairness. Use when someone says 'read this like opposing counsel', 'how would the other side attack this agreement', 'find the weaknesses before they do', or before sending or signing any contract. Produces the demand/position letter opposing counsel would actually send, plus an out-of-character debrief with the clause fixes that defang each attack.

Turn a team or reporting structure into a clean org chart. Use when asked to draw an org chart, show reporting lines, visualize team structure, or map who reports to whom. Produces a ready-to-render Mermaid org chart (renders live, exportable as PNG/SVG) plus headcount notes and any structural observations.

Design an out-of-office that actually protects the time off — the auto-reply that routes instead of apologizes, the coverage map behind it, and the pre-departure handoff that prevents the beach laptop. Use when asked write my out of office message, going on vacation what do I set up, cover my work while I'm out, or I always come back to chaos. Produces the OOO message with routing, the coverage assignments confirmed, the pre-departure checklist, and the re-entry buffer plan.

Record the testable predictions inside a decision, then score them against reality later — so frameworks earn trust from outcomes, not vibes. Use when committing to a prioritisation, forecast, or plan (to log what it predicts), when asked to review what actually happened, or to compute how well-calibrated past RICE scores, forecasts, or bets have been. Produces a prediction record at decision time, and a calibration report with per-framework hit rates at review time.

Outline documents before drafting them — the argument skeleton that gets alignment cheaply, the one-line-per-section discipline, and the review-the-outline step that saves rewriting the prose. Use when asked help me start this document, outline before I write, why do my docs get rewritten from scratch in review, or get sign-off before drafting. Produces the outline with each section's claim (not topic), the reader-and-decision header, the outline review step, and the expansion rules.

Write cold outreach and networking messages that actually get replies. Use when asked to write a cold message to a recruiter/hiring manager, a LinkedIn connection note, a referral request, or a networking/coffee-chat ask during a job search. Produces short, specific, reply-worthy messages — tuned to the recipient and the ask — with a clear subject and a low-friction call to action.

Audit what your public online presence quietly reveals — and tighten it — before a stranger, employer, or scammer uses it. Use when asked what does my online presence reveal, audit my privacy, what can people find out about me, or clean up my social media. Produces a review of what's exposed across profiles and posts (location, routines, identifiers, security-question answers), the specific risks each creates, prioritized fixes (settings + what to remove/stop posting), and habits to prevent future leaks — without demanding you delete everything.

When everything feels urgent and equally impossible, sort it fast into do-now / schedule / drop / delegate — so the panic becomes a short, calm list. Use when asked everything is urgent, I'm drowning in tasks, help me triage, or I can't tell what actually matters right now. Produces your overwhelming pile sorted into four clear buckets, the honest 'actually drop this' calls most people won't make themselves, the one thing to do right now, and relief from the false belief that everything must be done immediately.

Check a package's health before you depend on it — npm and PyPI registry APIs via keyless curl: downloads, release recency, maintenance signals, and the dependency-decision read. Use when asked is this npm package maintained, check this PyPI library before we adopt it, compare these two packages, or is this dependency abandoned. Produces the health read with the signals interpreted (not just listed), the numbers with their commands, and the adopt/avoid/vendor recommendation framing.

Plan a paid acquisition / performance marketing program with unit economics that work. Use when asked to plan paid media, allocate an ad budget across channels, set CAC/LTV targets, or structure a creative-testing program. Produces a paid acquisition plan — economic guardrails (CAC/LTV/payback), channel allocation, account & campaign structure, a creative testing plan, the measurement approach, and scale/kill rules.

Get the take of the specific experts a situation actually needs — a lawyer, a therapist, an accountant, a doctor-minded thinker, whoever fits — each in their own voice. Use when asked what would a [profession] say, get expert perspectives on this, who should I be thinking like here, or what am I missing that a pro would catch. Produces a panel of the right domain experts for your situation, each flagging what a layperson would miss, where they'd disagree, and what to verify with a real professional — never a substitute for licensed advice on serious matters.

Draft clear, warm, professional messages to parents or guardians — progress notes, concerns, positive news, behaviour issues, or meeting requests. Use when asked to email a parent, write home about a student, raise a concern with a guardian, or share an update. Produces a ready-to-send message that is specific, partnership-oriented, and constructive — never accusatory — with the tone matched to the situation.

Prepare for a K-12 parent-teacher conference — including the hard ones. Use when asked to prep for a parent conference, plan what to say to a parent, or handle a difficult conversation about a student's behavior or grades. Produces a structured agenda, strengths-first talking points backed by specific evidence, a plan for the tough message, anticipated parent reactions with responses, and agreed next steps.

Get real information out of a 15-minute parent-teacher conference — the questions that beat 'how's she doing', the data to bring from home, and the follow-up that makes the meeting matter. Use when asked prepare me for the parent teacher conference, what should I ask my kid's teacher, the conference is 15 minutes what do I prioritize, or how do I raise a concern without making it adversarial. Produces the prioritized question list, the home-observations brief, the concern-raising scripts, and the follow-up plan with owners.

Write a B2B partnership proposal or business case. Use when asked to write a partnership proposal, draft a partnership brief, structure a co-marketing proposal, or create a business case for a strategic partnership. Produces a structured proposal with value proposition, partnership model, commercial terms, and mutual commitments.

Cut through passive-income hype to what's actually realistic for you — the real effort, capital, and risk behind each option, and which (if any) fit your situation. Use when asked how do I make passive income, is passive income real, best passive income ideas, or help me build income streams. Produces an honest teardown of the popular passive-income options (what they really require, how 'passive' they actually are, typical returns and risks), a match to your capital/skills/time, the scams and get-rich-quick traps to avoid, and a grounded next step — replacing the fantasy with a realistic path. Not financial advice.

Set up a sane password and two-factor-authentication baseline that's genuinely secure and actually sustainable — a password manager, unique passwords where it counts, and 2FA on what matters. Use when asked to improve my password security, set up a password manager, how do I use 2FA, or make my accounts more secure. Produces a prioritized rollout (secure the crown-jewel accounts first), a password-manager setup, a 2FA plan by method strength, backup-code and recovery safeguards, and a realistic order so it gets done, not abandoned.

Write clear, plain-English patient communications for any healthcare context. Use when asked to write a patient letter, patient information leaflet, appointment letter, test-results letter, discharge summary for patients, or health education content. Produces an accessible patient communication at an appropriate reading level with clear next steps.

Decode a pay stub line by line — every deduction explained, the gross-to-net story, and the errors worth catching. Use when asked to explain my pay stub, why is my paycheck smaller than expected, what are all these deductions, or check my paycheck for mistakes. Produces a line-by-line decode, the gross-to-net waterfall, the error checklist (withholding, benefits, overtime), and the fixes to raise with payroll.

Design or optimize a paywall / upgrade screen to convert free users to paid without killing trust. Use when asked to improve a paywall, upgrade prompt, or free-to-paid conversion, or to decide what to gate. Produces the gating strategy (what's free vs. paid and why), the paywall placement and moment, the screen's copy and plan layout, and the metrics to watch — conversion that respects the user.

Write a clear penetration-test report from findings of an authorized engagement. Use when documenting a pentest, security assessment, or authorized red-team engagement — turning findings into a report clients act on. Produces an executive summary, scope & methodology, findings with severity/evidence/reproduction/remediation, and a risk-ranked remediation plan. For authorized testing only.

Define and document performance budgets for a web service or application. Use when asked to set performance targets, define SLOs for latency or throughput, establish Core Web Vitals targets, create a performance baseline, or document performance regression policy. Produces a structured performance budget covering key user journeys, Core Web Vitals, backend latency SLOs, measurement tooling, CI enforcement, and breach response process.

Write structured, balanced performance reviews from bullet-point inputs. Use when asked to write a performance review, self-assessment, peer review, 360 feedback, or manager evaluation. Produces a complete, fair, professionally written review covering achievements, areas for growth, and development goals.

Make sense of perimenopause symptoms nobody warned you about and prepare the GP conversation that actually helps — a symptom tracker mapped to what's likely hormonal, the prioritized list to raise, the HRT and treatment questions to ask, and how to push back on dismissal. Use when someone says 'is this perimenopause?', 'my doctor won't take my symptoms seriously', 'help me prepare for a menopause appointment', or is 40-55 and blindsided by symptoms. Produces a symptom map, a GP-visit brief, and a treatment-questions list. Not medical advice — it organizes your experience for the clinician who prescribes.

Work out which permits a project actually needs and the order to get them — building/renovation, business licensing, events, signage, home businesses — so you don't build first and discover the permit later. Use when someone says 'do I need a permit for this', 'what permits for my renovation/business/event', 'help me apply for a permit', or 'the council flagged my project'. Produces a permit checklist with the likely permits, their sequence and dependencies, and the official offices to confirm each. Not legal/code advice — it orients and routes to the authority.

Write a professional bio in the three lengths you actually need. Use when asked to write a bio, an 'about me', a speaker/author bio, or a short profile blurb. Produces three ready-to-use versions — a one-liner, a short (~50-word) bio, and a long (~150-word) bio — in a consistent third-person voice, plus a first-person variant.

Five standing advisors — the Operator, the Skeptic, the CFO, the Coach, the Customer — debate your decision on paper and vote. Use when asked to help me decide, pressure-test this decision, what would smart advisors say, or convene my board. Produces five distinct advisor memos, a disagreement map, a vote with a stated decision rule, and the one question to resolve before deciding.

Write the manual for how you work best — your energy, triggers, communication style, and non-negotiables — to share with a manager, team, or partner (or to know yourself). Use when asked to write my user manual, how I work best, a working-with-me guide, or help my team understand me. Produces a clear one-pager covering how you communicate, when you're at your best, what drains you, how you like feedback, and your non-negotiables — turning invisible friction into stated expectations, so people can work with you instead of around you.

Write a personal statement for a university, grad-school, or job application that's specific, coherent, and unmistakably you — showing fit and motivation, not a résumé in prose. Use when asked to write my personal statement, help with my university/grad application essay, statement of purpose, or make my personal statement stronger. Produces a read of what this program/role wants, a clear through-line (your motivation and fit), a structure that shows rather than lists, evidence from your real experience, and an authentic voice — drawing it out of you, not inventing a story.

Cap your work-in-progress so things finish — the personal WIP limit (3 active outcomes, defended), the finish-before-start rule with its exceptions named, the parking lot for the overflow, and the throughput evidence that converts the skeptic. Use when asked I have twelve things half-done, why does nothing ever finish, set a WIP limit for my work, or I start everything and complete nothing. Produces the active-list cap, the parking protocol, the start-gate, and the two-week throughput experiment.

Build the case to win someone over to a decision, idea, or change. Use when asked to persuade someone, build a case for an idea, get buy-in, win over a skeptic, or prepare to pitch a proposal internally. Produces a persuasion brief — the audience's current view and what moves them, the core argument, the proof, objection handling, the emotional and logical appeals, and the ask.

Decide fast whether a suspicious message is a phishing scam — and what to do next — without clicking anything. Use when asked is this email/text a scam, is this message legit, I got a suspicious message, or did I just get phished. Produces a quick verdict with the specific red (and green) flags in the message, a safe way to verify through official channels, exactly what to do next (delete/report, or act if genuine), and recovery steps if you already clicked or entered details.

Rescue a photo library drowning in duplicates, screenshots, and 40,000 unsorted items — the triage order that shrinks first (screenshots, bursts, dupes), the album-vs-search philosophy that ends over-organizing, and the backup rule that comes before any deleting. Use when asked organize my photo library, 40k photos help, delete duplicate photos safely, or set up a photo system that lasts. Produces the backup-first step, the shrink passes in order, the light organizing layer, and the monthly habit.

Respond to a performance improvement plan strategically — decode what the PIP really is, decide fight-vs-land-softly with clear eyes, build the evidence file, and run the parallel job search the situation demands. Use when asked I was just put on a PIP what do I do, help me respond to a performance improvement plan, is my PIP survivable, or write my PIP check-in updates. Produces the honest read of the PIP, the two-track plan (perform + search), the documentation system, and templates for check-ins and the written response.

Write a Performance Improvement Plan a manager can defend and an employee can actually act on — specific concerns, measurable goals, real support, and an honest timeline. Use when asked to write a PIP, put someone on a performance plan, document underperformance, or build a formal improvement plan. Produces the concern statement, the measurable goals with success criteria, the support plan, the check-in cadence, and the consequences — HR/legal-ready. Complements pip-responder (the employee's side).

Know which talk you're giving — the pitch (drive one decision) vs. the teach (build understanding) — because mixing their structures fails both, and most bad presentations are one wearing the other's clothes. Use when asked is this a pitch or a training, my informative deck didn't land the ask, my pitch felt like a lecture, or structure this talk for the right job. Produces the mode diagnosis, the structural implications, the mixed-mandate split, and the mode-check on an existing deck.

Plan pivot-table analysis that answers the actual question — the question-to-layout mapping (rows, values, filters chosen on purpose), the data-shape check that pivots require, and the drill-down path from summary to so-what. Use when asked analyze this data with a pivot, what's driving the total, break this down by category and month, or my pivot shows nonsense. Produces the question decomposition, the pivot layout(s) with reasons, the data-shape fixes needed first, and the reading guide.

Generate retro pixel-text animated GIFs for Slack, Teams, or a PR comment — scrolling marquees, heartbeat pulses, confetti parties, twinkling sparkles — from a bundled pure-stdlib Python script (no PIL, no dependencies, byte-exact deterministic). Use when someone wants a celebration GIF, a 'ship it' GIF, a custom Slack GIF, a launch-day animation, or to make a team win feel like one. Produces a ready-to-drag .gif file.

Rewrite jargon-dense text into plain language without losing precision — the translation pass that keeps every fact and qualifier, the jargon triage (terms to replace, terms to keep-and-define), and the reading-level honesty for the actual audience. Use when asked make this readable, translate this for non-experts, de-jargon this announcement, or rewrite this so my parents/customers/new hires understand it. Produces the rewrite with a fidelity check, the jargon ledger, and the kept-terms glossary line.

Turn a messy to-do brain-dump into a realistic, time-blocked day — top priorities first, everything slotted with buffer, and an honest 'this won't all fit, cut these.' Use when asked to plan my day, time-block my schedule, help me organize today, or I have too much to do. Produces the top 3 priorities, a time-blocked schedule around your fixed commitments, a realistic cut list when it's overloaded, and an if-things-slip fallback — planning for the day you'll actually have.

Structure a PM's weekly review and planning session. Use when doing a weekly PM review, writing a weekly update, preparing for Monday planning, or reviewing sprint health. Produces a shareable weekly update covering metrics movement, shipping progress, blockers, insights, and next week's top 3 priorities.

Get only the weaknesses in something you made — no praise, no encouragement padding, just the holes and how to fix them. Use when asked to poke holes in this, tell me what's wrong with this, critique this honestly, or don't be nice about it. Produces a focused list of the real problems in your draft, plan, argument, or code — ranked by severity, each with why it's a problem and a concrete fix — deliberately stripping the 'this is great!' padding that AI and polite humans add and you don't need.

Draft an internal policy people can actually follow — the rule stated plainly with its reason, the bright lines separated from the judgment zones, the edge cases resolved by principle, and the enforcement reality stated honestly. Use when asked write our expense/remote-work/AI-use/security policy, turn this incident into a policy, our policy doc is unreadable, or people keep asking what's allowed. Produces the policy with rules-plus-reasons, the bright-line/judgment split, the worked edge cases, and the honest enforcement section.

Write a decision-ready policy memo that frames an issue and recommends an option. Use when asked to write a policy memo, options paper, decision memo for a principal/minister/executive, or brief a decision-maker on a policy choice. Produces a tight memo: the issue, background, options with trade-offs, a clear recommendation, and implementation/risks — written for a busy decision-maker who reads the first paragraph.

Run a pre-renewal review of an insurance programme: scan coverage gaps against current operations, test limit adequacy against inflation and exposure growth, read the claims experience into pricing expectations, frame market alternatives, and arm the broker negotiation. Use when asked to prepare for a policy renewal, review cover before renewal, check if limits are still adequate, or build renewal negotiation points. Produces a structured renewal review with gap findings, limit assessment, pricing outlook, and negotiation points.

Structure a portfolio or case-study page that shows your work, not just lists it. Use when asked to write a portfolio page, a project case study, a work showcase, or an 'is this person good?' proof page. Produces a portfolio structure — a positioning header, and per-project case studies (context → your role → what you did → outcome) that demonstrate impact, ready to export as a designed page/PDF.

Fix the screen-hunch with a realistic plan — the desk fixes, the two or three exercises that counter it, and movement habits that beat any single stretch. Use when asked how to fix my posture, I have bad posture from sitting, tech neck, or rounded shoulders help. Produces a quick posture-cause read, immediate desk/setup fixes, a few high-value strengthening and mobility moves, movement-break habits, and honest expectations — plus a 'see a professional for pain/numbness' flag.

Understand power of attorney — which type you need, what it covers, and how to set one up properly — so the right person can act for you or a loved one when needed. Use when asked what is power of attorney, do I need a POA, help me set up power of attorney for a parent, or which type of POA. Produces a plain-English explainer of the main POA types (financial vs health, durable, springing), a which-do-you-need read for the situation, the setup steps and safeguards against abuse, and a strong flag to use proper legal forms/advice for your jurisdiction. Not legal advice.

Plan for an extended power outage — keeping medically-essential devices running, food safe, the home warm or cool enough, and communication alive — before the lights go out, with the special focus on power-dependent medical needs. Use when someone says 'prepare for a power outage', 'what if the power goes out for days', 'blackout plan', or 'I rely on a medical device that needs electricity'. Produces an outage plan tiered by duration, a medical-power priority plan, food/heat/cool/comms guidance, and safety warnings. Not medical advice; medical-device continuity routes to clinicians/utilities.

Audit a PowerPoint presentation for layout issues, text overflow, visual hierarchy problems, and consistency gaps. Use when asked to review a slide deck, check a presentation before a meeting, audit slides for layout problems, or QA a deck before sharing. Produces a slide-by-slide report with issues ranked by severity and specific fixes. Best used with Claude Opus 4.7 or newer for reliable slide-level vision analysis.

Build a crisis communications plan to respond fast and credibly when something goes wrong. Use when asked to handle a PR crisis, draft a crisis comms plan, respond to a public backlash/scandal/incident, or prepare holding statements. Produces a crisis comms plan — situation assessment, stakeholder map, a message house, channel-by-channel statements, a holding statement, an internal brief, and a follow-up timeline.

Write a clear pull-request description that gets reviewed fast and merged with confidence. Use when opening a PR, summarizing a change for review, or asked to write a PR/merge-request description. Produces a structured PR: what changed and why, how it was tested, risk and rollout, and a focused reviewer guide — so the reviewer understands intent before reading a single diff line.

Write a PR description grounded in the REAL diff — read the branch's actual changes via the GitHub connector, not a template the user fills in. Use when asked to write my PR description, describe this pull request, draft the PR body from my branch, or document these changes in Cowork. Reads the commits and diff via the GitHub connector, derives what changed and why from the code itself, and produces a PR-description artifact (summary, changes, testing, risk) ready to paste — matching the repo's PR template if one exists.

Write a clear, structured pull request description from a git diff, branch summary, or commit list. Use when asked to write a PR description, draft a pull request, or document code changes. Produces a description with summary, motivation, changes made, testing steps, and reviewer guidance.

Create a Product Requirements Document following proven PM template structure. Use when asked to write a PRD, product spec, feature specification, or requirements document for a new feature or product. Produces a complete PRD with problem statement, user stories, functional requirements, technical considerations, and success metrics.

Imagine your plan already failed, then get five independent 'here's why it died' stories — before you commit. Use when asked to pre-mortem this, why might this fail, what are the risks before I start, or imagine this went wrong. Produces five distinct failure narratives (each from a different cause — execution, timing, people, external, wrong-assumption), the most likely and most lethal among them, the early warning signs of each, and the specific mitigations worth doing now — catching failures while they're still cheap to prevent.

Kill the plan on paper before reality does it for money. Use when a plan, launch, migration, or strategy is about to be committed to and nobody has tried hard to murder it yet — the assassin attacks through twelve named failure vectors and writes the post-mortem of the failure that hasn't happened. Produces a premortem: the death narrative, the twelve-vector attack with survival verdicts, the three kill-shots most likely to land, and the cheap tripwires that would give early warning.

Work down the cost of a prescription systematically — the generic and therapeutic-alternative conversation, discount programs vs insurance math, pharmacy price variance, and manufacturer/assistance programs, in the order that saves the most first. Use when asked my prescription is too expensive, how do I save on my meds, is there a cheaper version of this drug, or I can't afford my medication. Produces the cost-reduction ladder for the specific prescription, the scripts for pharmacist and prescriber conversations, and the never-do list (skipping doses is not a savings plan).

Write presenter notes that actually help mid-talk — cue-grain phrases instead of scripts, the transitions and numbers that deserve verbatim capture, the timing marks that keep the talk on schedule, and the Q&A crib built in. Use when asked write my speaker notes, I either script everything or wing it, what goes in the notes pane, or I keep running over time. Produces the notes at cue grain, the verbatim-worthy lines, the timing marks, and the Q&A crib.

Build an electronic press kit that bookers and blogs actually read — the three-sentence bio that isn't 'genre-defying', a one-page layout with streaming numbers presented honestly, the photo and live-video requirements, and pitch emails tuned per target (venue, blog, radio, festival). Use when a musician says 'I need an EPK', 'venues keep ignoring my emails', 'write my band bio', or 'what do I send festivals'. Produces the EPK content, the one-page layout spec, and four pitch email templates.

Write a professional press release for any announcement. Use when asked to write a press release, media announcement, news release, or press statement. Produces a structured press release with headline, dateline, body, boilerplate, and media contact — ready to send to journalists.

Announce a price increase without triggering a churn spike — the rationale, grandfathering, effective dates, the FAQ, and the internal brief so support isn't blindsided. Use when asked to announce a price increase, write pricing change comms, raise prices to customers, or communicate new pricing. Produces the customer email, the FAQ with objection handling, the grandfathering/transition terms, and the internal enablement brief. A pricing-comms craft, not a discount.

Get a retailer to match a lower price you found — or refund the difference when the price drops right after you bought — with the request written and the exact proof to show. Use when asked for a price match, I found it cheaper somewhere else, the price dropped after I bought it, or can I get a price adjustment. Produces the policy-aware request, the evidence that qualifies, the eligibility read (what usually counts vs excludes), and a fallback if they won't match.

Model pricing scenarios — tiers, margins, break-even, and the revenue impact of a price change. Use when asked to calculate pricing, model a price increase, find break-even volume, set tier prices to a margin target, or estimate the revenue effect of a pricing change. Produces a computed pricing model (per-tier margin, break-even units, price-change revenue impact with an elasticity assumption) and a recommendation.

Write pricing page copy that helps buyers self-select the right plan and convert. Use when asked to write or improve a pricing page, name and describe pricing tiers, write plan feature lists, pricing CTAs, or a pricing FAQ. Produces complete pricing page copy — a header, tier cards with names, prices, audiences, feature lists, CTAs, an add-on/enterprise section, and an objection-handling FAQ.

Van Westendorp price sensitivity, computed from real survey answers — crossings found by interpolation, not read off a chart by eye. Use when someone has (or plans) the four-question pricing survey (too cheap / cheap / expensive / too expensive) and needs the optimal price point, the acceptable range, and a defensible readout. Produces OPP/IPP and the PMC–PME range, the four cumulative curves as data, and a real .xlsx with a live revenue what-if — via the bundled zero-dependency script.

Structure pricing strategy decisions, packaging options, and tier design for SaaS and digital products. Use when reviewing or setting pricing, designing pricing tiers, evaluating freemium vs paid, or preparing a pricing change. Produces a pricing strategy recommendation with model rationale, tier structure, competitive positioning, and rollout plan.

Design a freelance/consulting pricing structure — hourly vs day-rate vs project vs retainer chosen per engagement type, anchored packages, and the rules for saying the number out loud without flinching. Use when asked how should I price my freelance services, hourly or fixed price, build my pricing packages, or a client asked my rate what do I say. Produces the pricing-model decision per engagement type, a three-tier package structure, the rate-conversation script, and the discount policy with its floor.

Write a persuasive prior-authorization / medical-necessity letter to an insurer. Use when asked to write a prior authorization letter, a letter of medical necessity, or to appeal a denied treatment/medication/procedure. Produces a structured letter — patient and request, clinical justification tied to guidelines, treatments tried, and the specific approval asked for — ready for clinician review and signature.

Draft a clear, plain-language privacy policy tailored to what a product actually collects and does with data. Use when asked to write a privacy policy, draft a data-protection notice, or create a GDPR/CCPA-aware privacy statement. Produces a structured policy covering data collected, purposes, legal bases, sharing, retention, user rights, and contact — written to be readable, not boilerplate. Not legal advice; have counsel review before publishing.

Document any business process in a clear, structured format. Use when asked to document a process, write a process guide, create a workflow document, or map out how something works. Produces a complete process document with steps, roles, inputs, outputs, and edge cases.

Write a product description / listing that sells and ranks. Use when asked to write a product description, e-commerce listing copy, a product page, or to rewrite a flat product blurb. Produces benefit-led listing copy — a hook, scannable feature→benefit bullets, specs, an SEO-aware title and keywords, and trust/again-objection elements — tuned to the buyer and channel.

Interpret product metrics against goals and surface actionable signals. Use when asked to analyse product health, review key metrics, investigate a performance issue, produce a health report, or assess product-market fit signals. Produces a structured health report with RAG status, trend analysis, root cause hypotheses, and prioritised actions.

Generate a comprehensive pre-launch, launch day, and post-launch checklist for any product release. Use when preparing for a product launch, feature release, or major update. Produces a role-assigned, tiered checklist covering engineering readiness, marketing and comms, support, and post-launch monitoring.

Generate and evaluate names for a product, feature, or release. Use when asked to name a product/feature/company, brainstorm naming options, or choose between name candidates. Produces a shortlist of names across naming strategies, each with rationale, plus an evaluation against clear criteria (clarity, fit, memorability, availability checks to run) and a recommendation — not just a random list.

Write a product positioning document and messaging framework. Use when asked to define product positioning, write a positioning statement, build a messaging framework, or create a messaging hierarchy. Produces a complete positioning doc with category definition, target customer, differentiation, proof points, messaging pillars, and persona-specific messaging.

Find out whether something you own — a car, appliance, car seat, food item, or gadget — is under a safety recall, and what to do about it. Use when asked to check for a recall, is my [product] recalled, I heard about a recall on, or how do I find out if my car/appliance is affected. Produces a structured way to check by make/model/batch against the official sources, how to read whether your specific unit is affected, the free remedy you're owed, urgency triage for safety risks, and how to register for future recall alerts — flagging that you must confirm against the current official database.

Maintain a durable, local markdown memory ('brain') of your product context, decisions, hypotheses, and stakeholders that other skills read from and write back to. Use when asked to set up a brain, ingest notes/artifacts into memory, recall what's known about a topic, log a decision with provenance, or run a weekly brain review. Produces a structured brain/ folder (knowledge, decisions, hypotheses, stakeholders, entities, source) with provenance-tagged facts, plus ingest/recall/record/review operations with approval-gated, append-only write-back.

Translate text professionally — preserving tone, register, and meaning, not word-for-word. Use when asked to translate a document, email, or content between languages, or to improve a literal/machine translation. Produces a natural, register-appropriate translation plus translator's notes on choices, untranslatable terms, and anything that needs localization rather than translation.

Plan a programmatic SEO strategy — generate many ranking pages from a data set and a template. Use when asked about pSEO, scaling content with templates/data, building [X] for [Y] pages, or capturing long-tail search at scale. Produces the head-term + modifier model, the page template and data schema, a quality/thin-content guardrail, and an indexation plan — pages worth ranking, not doorway spam.

Write a structured project status report for any project. Use when asked to write a project update, status report, RAG report, project dashboard narrative, or weekly project communication. Produces a clear status report with RAG ratings, milestone progress, risks, and decisions needed.

Build a promotion case that proves you're already operating at the next level. Use when asked to write a promo packet/case, prepare for a promotion committee, or make the case for a level-up or title change. Produces a promotion packet — the level-up thesis, evidence mapped to each next-level competency, scope/impact highlights, peer-quote slots, and the gaps to close before submitting.

Plan a sale or promotion that drives revenue without wrecking margin. Use when asked to plan a promotion, a discount/sale campaign, a BFCM/holiday promo, or a product launch offer. Produces a promo plan — objective, the offer mechanic, margin math, audience & channels, timing, messaging, and how you'll measure it — so the discount is a strategy, not a reflex.

Figure out why a prompt isn't working and fix it — diagnose the actual failure (ambiguity, missing context, wrong format, conflicting instructions) instead of randomly rewording. Use when asked why isn't my prompt working, the AI keeps ignoring my instructions, my prompt gives inconsistent results, or how do I fix this prompt. Produces a diagnosis of the specific failure mode, the targeted fix for it (not a vibes rewrite), a corrected prompt, a check that it generalizes rather than fixing one case, and the principle behind the fix so you stop hitting it — turning prompt frustration into a debuggable, repeatable process.

Build a personal library of reusable prompts for the things you ask AI again and again — so you stop rewriting the same request from scratch. Use when asked help me build a prompt library, save my best prompts, I keep writing the same prompts, or organize my AI prompts. Produces a captured set of your recurring AI tasks turned into reusable, parameterized prompt templates, an organization scheme so you can find them, guidance on what makes a prompt reusable (clear role, inputs, output format), and how to store and improve them — turning ad-hoc prompting into a personal toolkit that compounds.

Diagnose and rewrite an underperforming LLM prompt so it produces reliable, well-structured output. Use when asked to improve a prompt, fix a prompt that gives inconsistent or wrong results, reduce hallucination/refusals, or make output follow a format. Produces a rewritten prompt with a diagnosis of what was failing, the specific changes and why, and a small test set to verify the fix.

Design a regression test suite that catches an LLM feature getting worse when the prompt, model, or context changes. Use when asked to stop prompt changes breaking production, set up golden tests or CI gates for an LLM feature, or test a model/prompt upgrade before shipping it. Produces a golden case set, per-case pass criteria, CI gate thresholds, and a triage protocol for failures. For designing first-time evaluation of a new feature use ai-eval-plan instead.

Analyze a rental / investment property's returns — cash flow, cap rate, cash-on-cash, ROI. Use when asked to analyze a rental property, evaluate a real-estate investment, run the numbers on an investment property, or compute cap rate / cash-on-cash. Produces an investment analysis — income and expenses, NOI, cap rate, monthly cash flow, cash-on-cash return, and a verdict against the investor's criteria — with formulas and a worked example. Not financial advice.

Write a compelling, accurate real-estate listing description. Use when asked to write a property listing, an MLS/Zillow description, a real-estate listing, or to make a property description more appealing. Produces a listing — a hook headline, a flowing description that sells the lifestyle and key features, a highlights list, and neighbourhood notes — accurate and Fair-Housing-compliant. Not legal advice.

Write a buyer's offer cover letter to a seller to strengthen a real-estate bid. Use when asked to write a real-estate offer letter, a buyer's 'love letter' to a seller, an offer cover note, or to make a home offer stand out. Produces a warm, genuine letter — who the buyers are, why they love the home, the strength of their offer, and a respectful close — while avoiding fair-housing risk. Not the legal offer/contract; not legal advice.

Challenge an over-assessed property tax bill — check whether your assessment is too high, build the evidence, and file the appeal before the deadline. Use when asked to appeal my property taxes, my property assessment is too high, lower my property tax, or is my home over-assessed. Produces an over-assessment check (comparables vs your valuation), the evidence pack to build, the appeal steps and the strict deadline to watch, a realistic savings estimate, and what to expect at a hearing — flagging that process and rules are local. Not legal or tax advice.

Structure an internal proposal that gets a decision — the problem-cost-options-recommendation-ask spine, the objection pre-handling that shortens the meeting, and the reversibility framing that makes yes easier. Use when asked write a proposal for the new tool or process or hire, how do I pitch this internally, structure my case for the change, or my proposals keep dying in review. Produces the proposal skeleton filled from the actual case, the objections table, the decision-sized ask, and the one-page discipline.

Write a structured sales proposal or commercial proposal for any deal. Use when asked to write a proposal, sales proposal, commercial proposal, statement of work, or quote document. Produces a complete proposal with problem statement, solution, investment, and next steps.

Draft a persuasive public comment on a proposed rule, regulation, or plan. Use when asked to comment on a rulemaking, respond to a consultation, submit feedback on a proposed regulation, or write a comment to an agency. Produces a structured comment: your position, specific evidence-based arguments tied to the proposal's text, suggested edits, and the impact — the kind agencies must consider on the record.

Look up public holidays for any country and year with zero API keys — the Nager.Date API via curl, with long-weekend detection and cross-country planning. Use when asked what are the holidays in a country, is date X a holiday somewhere, find long weekends this year, or which days is the team in Japan and Germany both off. Produces the holiday list with local names, the specific-date answer, long-weekend candidates, and the rerunnable command.

Prepare for a specific talk, presentation, or speech — a clear structure, a strong open and close, delivery and nerves handling, and a rehearsal plan — so you land it. Use when asked to help me prepare a talk/presentation/speech, prep for public speaking, I have to give a presentation, or calm my speaking nerves. Produces a message-first structure built on your core point and audience, a memorable opening and closing, delivery guidance (pace, pauses, notes vs script), a nerves-management plan, a rehearsal approach, and Q&A prep — tuned to the occasion and your experience.

Turn walkthrough notes, photos, or voice-memo transcripts into a proper construction punch list with location, trade, and spec reference per item. Use when asked to build a punch list, clean up walkthrough notes, organise a deficiency list, prep for substantial completion, or track punch items to closeout. Produces a numbered punch list grouped by location with severity tiers, responsible subcontractor, back-charge candidates, and closeout/retainage linkage.

Write the purchase request that gets approved — the cost-of-not-buying framing, the ROI math at the approver's altitude, the alternatives-considered section that preempts the obvious pushback, and the right-sized ask for the approval tier. Use when asked justify this tool/hire/equipment purchase, write the budget request, my requests keep getting deferred, or make the business case for this spend. Produces the justification memo: the problem priced, the ROI shown, alternatives dispatched, and the ask sized to its approval path.

Turn a story and its change into a clean 'ready for QA' package — test scenarios, edge cases, the data and environment setup, and what's explicitly out of scope. Use when asked to prep a QA handoff, what should QA test here, write test scenarios for this story, or make this ready for QA. Produces the scenarios mapped to acceptance criteria, the edge/negative cases devs forget, the exact data and environment setup to reproduce, the risk areas to probe, and the out-of-scope list so QA doesn't chase the wrong things.

Produce a QA release sign-off / go-no-go readiness report. Use when asked for a release sign-off, a go/no-go QA report, release readiness, or a test summary before shipping. Produces a sign-off — what was tested and the results, open defects by severity, coverage and residual risk, the go/no-go recommendation with conditions, and a rollback note — so the release decision is evidence-based, not a vibe.

Build a Quarterly Business Review (QBR) deck structure and narrative for a customer account. Use when asked to prepare a QBR, business review meeting, executive review, or quarterly check-in with a customer. Produces a slide-by-slide QBR structure with talking points, metrics review, value narrative, and mutual next steps.

Build the tax habit self-employment requires — the setaside percentage from day one, the quarterly calendar, the records that make filing boring, and the no-withholding mindset shift nobody explains. Use when asked how do taxes work for my side income, how much should I set aside, what are estimated quarterly payments, or set up my freelance tax system. Produces the setaside rule with its honest range, the quarterly rhythm calendar (jurisdiction-flagged), the five-minute-a-week records system, and the deduction-tracking habit — framing routed to a local professional for the numbers.

Generate a quiz or test on any topic with a balanced mix of question types and difficulty, plus a complete answer key with explanations. Use when asked to create a quiz, write a test, make practice questions, or build an assessment. Produces well-formed questions aligned to learning objectives, tagged by difficulty and cognitive level, with an answer key and (for MCQs) plausible distractors and rationale.

Pull the single most shareable quote out of a testimonial, review, interview, or long text and format it as a clean quote card. Use when asked to make a pull-quote, testimonial graphic, or 'quote card' for social/marketing. Produces a tightly-edited quote with attribution and 2-3 alternates, structured to look great exported as a PNG from the playground.

Talk to a family member or friend who's gone down a conspiracy, misinformation, or extremism rabbit hole — without blowing up the relationship or entrenching them further — using connection-first techniques that actually work instead of the facts-and-arguments that don't. Use when someone says 'my dad believes X now', 'my friend's gone down a conspiracy hole', 'how do I talk to them without a fight', or is losing someone to a belief spiral. Produces a conversation approach, what-not-to-do list, and a realistic goal. Connection over winning — and it names when to step back for your own wellbeing.

Define a RACI matrix for a cross-functional project or process. Use when asked to build a RACI, create a responsibility matrix, clarify ownership across teams, or document decision rights. Produces a complete RACI matrix with role definitions, decision mapping, and a process for resolving conflicts.

Review an existing Retrieval-Augmented Generation system and find why it underperforms. Use when asked to review or audit a RAG pipeline, diagnose wrong/ungrounded answers from a 'chat with your docs' feature, or improve an already-built knowledge assistant. Produces a staged review — ingestion, chunking, retrieval, reranking, generation, evaluation — with prioritised findings, root causes, and concrete fixes.

Design a Retrieval-Augmented Generation system end to end. Use when asked to design a RAG pipeline, a 'chat with your docs' feature, a knowledge assistant, or to debug why a RAG system gives wrong/ungrounded answers. Produces a RAG design doc — ingestion & chunking, embeddings & index, retrieval & reranking, the generation prompt, grounding/citations, evaluation, and failure modes with mitigations.

Model staying for annual raises vs job-hopping for bigger bumps — cumulative earnings trajectories, the crossover year, and the costs the salary math hides (vesting resets, promotion paths, search risk). Use when asked should I switch jobs for more money, is job hopping worth it, model my salary if I stay vs leave, or raise versus new offer. Produces the year-by-year salary and cumulative-earnings table, the crossover year, and the not-in-the-model checklist that usually decides it.

Climb ranked on purpose instead of on tilt — a VOD-review protocol (three deaths per game, one pattern per week), a tilt debrief that ends queue-rage sessions, and honest fundamentals-first improvement planning for competitive games like League, Valorant, or Rocket League. Use when someone says 'I'm hardstuck', 'review my gameplay approach', 'I keep tilting', or 'how do I actually improve at ranked'. Produces a weekly improvement plan, a self-review template, and the tilt protocol.

Handle the first hour of a suspected ransomware or malware infection calmly and correctly — contain it, preserve options, and avoid the moves that make it worse. Use when asked what to do about ransomware, my files are encrypted with a ransom note, I think I have malware, or my computer's been hacked. Produces an immediate containment checklist, a preserve-evidence-and-options step, a recovery path (backups, known decryptors, professional help), guidance on the ransom-payment decision, and reporting steps — for personal/small-setup use, not a substitute for professional incident response.

Build a consulting/freelance rate card and pricing structure — and the floor rate to not go broke. Use when asked to set freelance/consulting rates, build a rate card, decide what to charge, package services, or move off hourly billing. Produces a rate card — your minimum viable rate (from real targets), tiered packages, pricing models (hourly/day/project/retainer/value), and how to present and defend it.

Figure out the real social dynamics of a situation — the unspoken mood, who holds influence, what's actually going on beneath the surface — so you respond to what's real, not just what's said. Use when asked help me read this situation, what's really going on here, how should I play this socially, or I can't tell the vibe. Produces an interpretation of the likely dynamics from your description (the mood, the power/influence, the unspoken tensions, what people actually want), how to check your read, and how to adjust your approach — with a caution against over-reading and a nudge to verify rather than assume.

Actually remember and use what you read — an active-reading system that beats the highlight-and-forget cycle. Use when asked how do I remember what I read, I forget books right after finishing, help me retain what I study, or take better reading notes. Produces an active-reading method (questions before, engagement during, retrieval after), a lightweight note format that captures the few ideas worth keeping, a spaced review touch, and how to actually apply what you read — turning passive consumption into knowledge you keep.

Write a clear, well-structured README for a software project or open-source repo. Use when asked to write or improve a README, document a project, or make a repo approachable. Produces a complete README — one-line pitch, badges, quickstart, usage, install, contributing, license — that gets someone from landing to running fast.

Audit any document against its own sources — every factual claim extracted and graded as evidenced, partially evidenced, unsupported, or contradicted, with the exact source line that supports or fails it. Use when asked to fact-check a document against its sources, check whether a report's claims are backed up, verify a deck against the data, or ask 'does this doc have receipts?'. Produces a claim ledger, unsupported claims ranked by load-bearingness, a fix-or-drop call per claim, and an honesty score with stated method.

Rebuild relationships with family, kids, and friends after incarceration or a long absence — how to reach out, repair trust at the other person's pace, and handle the hard first conversations. Use when asked how do I reconnect with my kids after prison, rebuild trust with family after being away, or the first conversation after a long absence. Produces a paced reconnection plan (who to reach first and how), opening messages that don't demand forgiveness, a way to rebuild trust through consistency rather than words, scripts for the hard conversations, and realistic expectations about time and rejection — so reconnection is steady and genuine, not a pressured single grand gesture. Centers the other person's pace; points to family therapy and reentry family services.

Reach back out to a friend or person you've lost touch with — past the awkwardness of the gap — with a message that reopens the door warmly. Use when asked how do I reconnect with an old friend, it's been too long and it's awkward, reach out to someone I drifted from, or message someone I lost touch with. Produces a read on why the awkwardness is smaller than it feels, a warm reach-out message that acknowledges the gap without over-apologizing, a specific hook (a memory, a reason, a simple 'you crossed my mind'), and how to move from message to actually reconnecting — because most drifted friendships just needed one person to text first.

Plan a real rest day — active recovery, genuine downtime, and a reset — instead of either grinding through or collapsing into a guilt-scroll. Use when asked how to spend a rest day, plan a recovery day, I'm burnt out and need to recharge, or what should I do on my day off. Produces a recovery plan matched to what you're recovering from (physical, mental, or both), gentle active-recovery options, restorative downtime that actually restores, light admin to reduce next-week stress, and permission to do less.

Write personalized candidate outreach that gets replies. Use when asked to write a recruiter InMail, a candidate outreach email, a sourcing message, or a follow-up sequence. Produces a short, personalized first message (hook tied to the candidate, the role's appeal, a low-friction ask) plus a 2–3 step follow-up sequence — honest and candidate-respectful, not spammy.

Prune your own recurring-meeting load — the personal calendar audit (your role in each, honestly), the four exit moves (leave, delegate, downgrade to notes, halve), and the graceful exit scripts that don't burn standing. Use when asked get me out of some of these meetings, my calendar is 80% recurring, which meetings can I stop attending, or leave a meeting politely. Produces the personal audit with role verdicts, the exit move per meeting, the scripts, and the calendar-shape after.

Attack your own plan the way a smart adversary would — find the weakest point, the thing you're hoping nobody notices, and where it breaks under pressure. Use when asked to red-team this, attack my plan, find the holes, or where does this break. Produces an adversarial breakdown of the plan's weakest points, the single move an opponent (or reality) would make to break it, the part you're quietly hoping holds, and the fixes that close the biggest gaps — a hostile stress-test done by your own side, before someone else does it for real.

Stress-test a plan, strategy, PRD, or launch by simulating hostile expert personas who attack it from every angle. Use when asked to red-team, stress-test, pre-mortem, pressure-test, play devil's advocate, or find the blind spots in a plan before committing. Produces a per-persona critique, a ranked list of the most dangerous risks, a pre-mortem, and the specific changes that would most strengthen the plan.

Structure a redundancy consultation process and draft key communications (UK employment law focus). Use when asked to plan a redundancy process, write a redundancy letter, structure a consultation, or manage a reduction in force. Produces a structured consultation plan and draft letters; always recommends qualified HR/legal advice before proceeding.

Plan a safe, incremental refactor of messy code without changing behavior. Use when code needs restructuring, is hard to change, has grown tangled, or you want to clean it up before adding a feature. Produces a sequenced plan of small behavior-preserving steps, the safety net (tests/characterization) to add first, and the target structure — refactoring as a series of green commits, not a risky big-bang rewrite.

Run a rigorous candidate reference check that surfaces real signal. Use when asked to prepare or conduct reference calls for a job candidate, design reference questions, or build a reference-check rubric. Produces a structured question set, probing follow-ups, a red/yellow/green scoring rubric, and the legal guardrails — designed to get past 'they were great' without leading the referee.

Write a credible, specific letter of recommendation or reference. Use when asked to write a reference letter, a letter of recommendation, a character reference, or to recommend someone for a job, school, or tenancy. Produces a structured reference — your relationship, specific evidence of their strengths, a comparative endorsement, and a clear recommendation — tailored to what the reader is deciding.

Secure strong references after a departure — who to ask, the ask messages, the briefing sheet that makes their reference specific, and the LinkedIn recommendation swap. Use when asked to help me get references, write a reference request, prep my referee, or ask my old manager for a recommendation. Produces the referee shortlist with rationale, tailored ask messages, a one-page referee briefing sheet, and the follow-up etiquette.