2.5천건 · 관련도순
Agent Ready project design context for navigation, docs links, and interface tone. Use when building or reviewing UI in this repo so patterns match the documented product feel.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Personalized academic writing assistant for university assignments in Chinese and English. Use when users need help writing/revising academic reports, project docs, technical analyses, research reviews, or case studies. Produces natural prose avoiding AI markers. Triggers: academic writing, assignment, report, technical analysis, research review, case study. | 个性化学术写作助手，适用于中英文大学作业。触发词：学术写作、作业、报告、技术分析、研究综述、案例研究、项目文档。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when writing recommendation letters, reference letters, or award nominations for students, postdocs, or colleagues. Invoke when user mentions recommendation letter, reference, nomination, letter of support, endorsement, or needs help with strong advocacy, comparative statements, or evidence-based character assessment.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create documentation with gaming-specific examples, retro styling, and 8-bit terminology. Apply when documenting gaming blocks, RPG components, or retro-styled UI elements.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[22] UNDERSTAND. Deep research from all sources — internal (code, git, logs) AND external (web, docs, best practices). Use when choosing libraries, investigating solutions, understanding legal/technical questions, comparing approaches, or anytime you need comprehensive knowledge from both project context and world knowledge. Triggers on "research", "investigate", "find best approach", "what do others do", "compare options", or complex questions requiring multiple sources.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
パフォーマンス改善作業の開発ドキュメントを自動生成します。YYYYMMDD_要件名の形式でディレクトリを作成し、requirements.md、design.md、tasklist.md、testing.mdを生成します。「パフォーマンス改善のドキュメント作って」「最適化作業のドキュメント」「高速化のドキュメント生成」などで呼び出されます。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
開発作業ドキュメントを自動生成します。YYYYMMDD_要件名の形式でディレクトリを作成し、requirements.md、design.md、tasklist.md、testing.mdを生成します。「開発作業ドキュメント作成」「新規開発のドキュメント作って」「ドキュメント生成」などで呼び出されます。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Master API documentation with OpenAPI 3.1, AI-powered tools, and modern developer experience practices. Create interactive docs, generate SDKs, and build comprehensive developer portals.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user asks to "create AGENTS.md", "update AGENTS.md", "maintain agent docs", "set up CLAUDE.md", or needs to keep agent instructions concise. Enforces research-backed best practices for minimal, high-signal agent documentation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Запускает lightweight baseline verification для docs, OpenSpec, skills и live context этого репозитория.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write strategy-oriented Product Requirements Documents (PRDs) for AI product managers. Use when: (1) drafting a new PRD or strategy doc, (2) structuring a feature proposal with strategy rationale, (3) writing requirement docs that emphasize "why" over "how", (4) turning raw product ideas into structured requirement documents. NOT for: purely technical specs, engineering tickets, or UI copy.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps.' Use this for any document or asset that helps a sales team close deals. For competitor comparison pages and battle cards, see competitor-alternatives. For marketing website copy, see copywriting. For cold outreach emails, see cold-email.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Detect silent drift between what the docs claim and what the repo actually contains — drift check, health check, audit, watch, sync check, /mxm-watch. Runs 13 drift classes and reports gaps before they ship.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Structure AI work artifacts under .aiwork/{YYYY-MM-DD}_{slug}/ folders using the project's protocol (intent, triage, research, spec, prd, areas, plan, review, notes, docs/). Use when the user asks to plan, capture an intent, make a spec, triage, research a task, write a report, code review, summarize findings, save the work, document decisions, record this, write that down, persist findings, or references any path under .aiwork/. Also use when starting a non-trivial task that needs a plan or spec before implementation, or when finishing one and capturing notes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (GLOSSARY.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Triage requirements, specs, or tickets. Detect input (pasted text, markdown path, tracker ticket id/URL, or empty prompt). Explore codebase + docs, score completeness, ask clarifying questions, write a markdown report. Trigger when user says "triage", "review this spec", "is this requirement complete", or provides a ticket/spec to assess.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use for writing any English text like docs, notes, summaries, explanations, answers, README sections.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Skills for accessing official documentation
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create or update standardized object-oriented component documentation using a shared template plus mode-specific guidance for new and existing docs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Ensure that Java types are documented with Javadoc comments and follow best practices for documentation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Query official Microsoft documentation to find concepts, tutorials, and code examples across Azure, .NET, Agent Framework, Aspire, VS Code, GitHub, and more. Uses Microsoft Learn MCP as the default, with Context7 and Aspire MCP for content that lives outside learn.microsoft.com.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Look up Microsoft API references, find working code samples, and verify SDK code is correct. Use when working with Azure SDKs, .NET libraries, or Microsoft APIs—to find the right method, check parameters, get working examples, or troubleshoot errors. Catches hallucinated methods, wrong signatures, and deprecated patterns by querying official docs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.