XiaomiMiMo/MiMo-Code - 2페이지

image-to-code

Implement a selected image, screenshot, mockup, generated concept, or design frame as a faithful, responsive, interactive frontend in the target codebase.

원문 언어: 영어

index

Use when Product Design is explicitly invoked, or when the user's main goal is to explore a design, research UX, audit or critique a flow, faithfully clone a visual source, check a built design, or share a prototype. Do not use Product Design for ordinary…

원문 언어: 영어

share

Share a runnable prototype using the user's preferred deployment tool.

원문 언어: 영어

url-to-code

Recreate an authorized live website or app URL as a faithful, runnable, frontend-only local implementation.

원문 언어: 영어

user-context

Load or manage Product Design's saved user context. Use when the user asks to set up Product Design, get started, onboard, save product or design sources, see what Product Design remembers, update saved context, or remember Product Design preferences.…

원문 언어: 영어

research-paper-writing

Write, rewrite, and polish academic papers (ML/CV/NLP style). Use when the user drafts or revises Abstract, Introduction, Related Work, Method, Experiments, or Conclusion; asks "does this flow / 这段通顺吗 / polish this paragraph"; turns bullet points or a Chinese…

원문 언어: 영어

sales

Use this skill whenever Sales is explicitly invoked or the task involves customer meeting preparation, call follow-up, account prioritization, account signals, deal strategy, business cases, competitive briefs, forecasts, customer evidence, rep coaching,…

원문 언어: 영어

analyze-account-signals

Use when the user wants to know what changed with one account, monitor an owner portfolio or watchlist, or rank accounts needing attention from recent evidence. Produce an evidence-backed account brief or bounded watchlist summary with recommended actions.

원문 언어: 영어

answers-ask-user-input

Use when a small amount of missing context would materially improve the answer and tappable options plus a free-text answer can gather it efficiently.

원문 언어: 영어

apollo

Use only when a focused Sales workflow has selected a present and connected Apollo connector, or the user explicitly asks for Apollo prospecting, enrichment, Company Details, records, sequences, or outbound planning. Apply Apollo v2-specific behavior only…

원문 언어: 영어

build-business-case

Review commercial proposals and build customer-led business cases, ROI or value models, pricing or investment rationales, executive summaries, and customer-ready value stories tied to a customer, workflow, initiative, or decision.

원문 언어: 영어

build-competitive-brief

Use when the user wants a competitor or vendor comparison, market-landscape analysis, battlecard, objection package, positioning brief, or account-specific competitive view. Produce an evidence-backed comparison, guidance, and brief, using supplied materials,…

원문 언어: 영어

enrich-company-and-contact-data

Use for data-first company, contact, lead, and prospect discovery or enrichment, including firmographic or technographic completion, named-company profiling, entity resolution, ICP matching, prospect-list building, segmentation, trigger or sales-signal…

원문 언어: 영어

find-customer-quotes

Use when the user wants verbatim customer or prospect quotes, voice-of-customer evidence, theme validation, objection evidence, product-friction examples, or support for a product area, use case, or sales narrative. Retrieve from transcripts, call notes,…

원문 언어: 영어

find-key-internal-sources

Use when a seller needs to find the best internal experts, owners, approvers, documents, channels, source-of-truth materials, or escalation routes for a customer question, product topic, competitive objection, implementation issue, account task, or other…

원문 언어: 영어

follow-up-after-call

Use after a completed customer, prospect, partner, or important internal sales call, discovery session, demo, or conversation, including when the user supplies or uploads a transcript, notes, recording summary, or other grounded evidence. Advise on, assess,…

원문 언어: 영어

get-rep-call-feedback

Use when the user wants evidence-backed coaching for one rep's calls, especially by comparing the rep with peer examples to identify repeatable best practices, specific upgrade moments, and practical next-call language.

원문 언어: 영어

hubspot

Use only when a focused Sales workflow has selected a connected HubSpot CRM, or the user explicitly asks for HubSpot guidance, reads, drafts, notes, or reviewed record changes. Do not use when another CRM is authoritative.

원문 언어: 영어

index

Use this Sales index first for explicit Sales mentions and clear seller workflows: prospecting, lead qualification, account research, monitoring or prioritization, meeting prep, call follow-up, outreach research, deal strategy, pipeline or forecast review,…

원문 언어: 영어

plan-deal-strategy

Use when the user wants strategy for one active deal, renewal, negotiation, buying process, or initial sales motion for an offer or product. Build a grounded deal map or practical sales plan with objections, sequencing, posture, and prioritized next actions.…

원문 언어: 영어

prepare-for-meeting

Use when the user wants to prepare for one or more upcoming meetings with customers, prospects, partners, accounts, or important stakeholders; requests daily or date-based meeting preparation; asks to organize a same-day customer call queue; asks for the most…

원문 언어: 영어

prioritize-accounts

Use when the user asks which existing accounts to work now, which leads are hottest in a grounded list or pipeline, how to rank a territory, book, pipeline, ICP list, or account list, where to focus this week, or what rep-ready next actions to take.…

원문 언어: 영어

review-forecast

Use when the user wants forecast posture, forecast accuracy, commit, upside, forecast-call preparation, or a pipeline or deal-risk review for a seller book, team, period, report, or named deal set. Produce a manager-ready forecast rollup, risk posture,…

원문 언어: 영어

review-rep-call-trends

Use when the user wants to understand how a sales or customer-facing rep's call behavior is changing over time. Produce an evidence-backed trend readout with improvements, regressions, stable patterns, coaching actions, and calls to re-listen.

원문 언어: 영어

sales-company-research

Research companies, partners, and referral channels to shape draft outreach approaches, messages, or partner motions; exclude descriptive company profiling, list enrichment, and internal source finding.

원문 언어: 영어

salesforce

Use when a focused Sales workflow needs Salesforce-backed CRM reads, links, drafts, notes, account plans, Agentforce assignments, or explicitly requested Salesforce connector/query guidance. Do not use for generic CRM app construction or when another CRM is…

원문 언어: 영어

zoominfo

Use only when a focused Sales workflow has selected a present and connected ZoomInfo connector, or the user explicitly asks for ZoomInfo company search, contact search, enrichment, intent, similarity, recommendations, or research. Do not use when another…

원문 언어: 영어

skill-creator

Interactive guide for creating, reviewing, and improving agent skills (SKILL.md folders). Use when the user wants to build a new skill ('create a skill', 'make a skill for X', 'write a SKILL.md', 'turn this workflow into a skill'), review or improve an…

원문 언어: 영어

compose-ask

Use whenever you need a decision, clarification, or approval from the user — covers how to ask with the question tool, and how to resolve the decision yourself when no user is available (question tool absent, or a [Never-Ask] response)

원문 언어: 영어

compose-brainstorm

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

원문 언어: 영어

compose-debug

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

원문 언어: 영어

compose-execute

Use when you have a written implementation plan to execute in a separate session with review checkpoints

원문 언어: 영어

compose-feedback

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

원문 언어: 영어

compose-merge

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

원문 언어: 영어

compose-parallel

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

원문 언어: 영어

compose-plan

Use when you have a spec or requirements for a multi-step task, before touching code

원문 언어: 영어

compose-report

Use after implementation is verified and before merge — consolidates multiple spec iterations into a single final-state report, marks related specs, and records key lessons

원문 언어: 영어

compose-review

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

원문 언어: 영어

compose-subagent

Use when executing implementation plans with independent tasks in the current session

원문 언어: 영어

compose-tdd

Use when implementing any feature or bugfix, before writing implementation code

원문 언어: 영어