Results for “microsoft-clarity”

Technical documentation specialist and knowledge curator. Use when the user asks to talk to Paige or requests the tech writer.

Technical documentation specialist and knowledge curator. Use when the user asks to talk to Paige or requests the tech writer.

Enriches vague, low-detail prompts into structured, agent-optimized XML before execution. INVOKE IMMEDIATELY — before any tool use or file reads — when you detect any of these signals: prompt under 10 words with no file path or error message; vague action verbs with no object ("fix the bug", "make it better", "clean this up", "refactor this", "optimize performance", "improve the UI", "add authentication", "add payments", "add notifications", "build the feature"); CLARIFIER_ADVISORY in your context window; user says "clarify", "help me describe this", "enrich this prompt", "structure my request". Also triggers on: "make this work", "it's broken", "it looks bad", "add X" with no further detail, "implement Y" with no constraints. Do NOT trigger on: prompts ending with ?, prompts containing error messages or stack traces, prompts with specific file paths, prompts already containing acceptance criteria or success metrics.

Queries Microsoft 365 Copilot data (emails, meetings, documents, Teams, people) using the WorkIQ CLI/MCP server for live context, summaries, and recommendations.

Search the web with LLM-optimized results via the Tavily CLI, returning relevant snippets, relevance scores, and metadata. Supports domain filtering, time ranges, and multiple search depths.

Decision guide for when to proactively use Claude Code slash commands — /think, /model, /compact, /clear. Use when choosing whether to invoke a command before or during a task, or when a complexity-classifier hook has flagged a task as high or critical. Pairs with the complexity-classifier UserPromptSubmit hook.