m1nga
UserCross-agent SKILL.md workflows for product architecture, UX audits, prompt clarity, work synthesis, and hands-on practice.
Categories
Indexed Skills (13)
coffee-brewing
Mingtao 的私人咖啡冲煮助手。看咖啡照片（豆袋 / 豆子本身 / 磨好的粉 / 萃出的浓缩液）→ 判断烘焙度与处理法 → 给出精确的研磨/水温/比例/时间参数和饮品配方（意式 espresso、冰美式、热美式、拿铁奶卡、V60 手冲），并通过「时间+口感」反馈帮你一步步调豆（dial-in），诊断萃取过度/不足，把调定的豆子存进豆子记忆，越用越准。硬件写死：Mazzer Philos 磨豆机、Hario V60、La Marzocco Linea Micra。 Use this skill whenever Mingtao shares a photo of coffee beans/bags/grounds/espresso, asks how to brew / grind / dial in any coffee, wants a recipe for espresso/americano/latte/pour-over, reports a shot tasting sour/bitter/under- or over-extracted, or mentions 冰美式/热美式/浓缩/手冲/磨豆/研磨度/养豆/萃取/拉花/奶卡/V60. Trigger even if they don't say the word "skill" — any coffee brewing or dial-in question counts.
explain-ai-reply
Turn a confusing Claude, Codex, ChatGPT, or other AI response into a plain-language version anchored to the user's original instruction. Use when the user pastes their request plus an AI reply and says they do not understand it, asks “他说了什么”, “什么意思”, “说人话”, “帮我解释这个回复”, or wants to know what was actually completed, merely proposed, left unverified, missed, or requires their decision.
iteration-close
Close a product iteration the safe-but-ruthless way, in ANY repo — not tied to one product. Distill this iteration's decisions into the repo's own record, DELETE superseded baggage (git history is the archive — no _archive dirs, no .bak, no legacy- renames), verify two SEPARATE readiness channels (a confirmed cloud upload AND a tested zero-context takeover probe), rehearse the one-command new-machine bootstrap, then tag and seed the next iteration. Adapts to each repo's conventions and creates the minimum where one is missing. Run when an iteration or slice is done/approved and the user says any of — 收口 / 迭代收口 / 迭代收尾 / 收尾 / 收工 / 封版 / 发版 / 甩包袱 / 清旧账 / 蜕壳 / 这个迭代做完了 / 收尾上云 / close the iteration / wrap up this iteration / ship this iteration / finalize this iteration / done with this iteration. Also handles a STRUCTURAL overhaul as an in-repo iteration, never a new-repo restart. Product-agnostic; works in Claude Code and Codex.
loop-system-architect
Design, audit, repair, and operationalize reliable agent loops with explicit goals, triggers, persistent state, orchestration, independent verification, failure recovery, open skill discovery or creation, experience distillation, controlled self-improvement, and retirement conditions. Use when the user asks to build a loop, autonomous or recurring agent workflow, multi-agent operating system, self-improving process, knowledge/experience distillation pipeline, zero-context recovery flow, permanent update/replacement loop, or to turn a prose plan or repeated prompt into a genuinely executable loop.
map-product-system
Turn rough product ideas, conversations, documents, or an existing codebase into an end-to-end product system map covering user journeys, capability boundaries, platform and customer mandates, data lifecycles, agent/service/human responsibilities, architecture, failure paths, governance, and delivery slices. Use when the user asks to understand the whole product, find missing functions or branches, establish product foundations, decide what belongs in code versus mandates or configuration, design multi-agent responsibilities, audit product completeness, or convert a product concept into an executable architecture. Trigger on phrases such as “看一下产品结构”, “梳理产品架构”, “检查用户旅程和功能分支”, “review the product structure”, or “map the whole product”.
morning-brief
晨报 — overnight digest generated after Ming has been idle 3+ hours past midnight, waiting on his Desktop when he wakes. Summarizes yesterday's work across ALL Claude sessions and projects (tasks, conclusions, progress, open loops), then proposes up to five evidence-based ways to simplify and work more efficiently with Claude Code. Use when invoked by the scheduled task ("generate the morning brief"), or whenever Ming says 晨报 / 早报 / morning brief / 昨天干了什么 / 总结一下昨天 / daily digest / 睡前总结 / asks what happened across his sessions yesterday, or wants efficiency suggestions based on his recent Claude usage.
product-experience-officer
资深产品体验官 — experience a product-in-development as a zero-experience first-time user, then report to the PM with prioritized findings, fix recommendations, and follow-ups. Covers product experience, design, visual, interaction, copy, emotion — everything a cold stranger would feel. Two modes — analyze screenshots the user provides, or run/drive the product live (web via browser tools, CLI/TUI via terminal, native via computer-use). Use whenever Ming shares screenshots of a product he's building and wants reactions, or says anything like 体验一下 / 用户视角 / 从0经验的角度 / 体验官 / 帮我试试这个产品 / walkthrough / first-time user experience / UX audit / 看看新用户会怎么想 / 这个流程顺不顺 — even if he doesn't say the skill name. Trigger for any "experience my product and give feedback" request, screenshots included or not.
prompt-craft
Turn casual ideas into AI-ready prompts. Combines brand context, marketing knowledge, and Mingtao-specific communication patterns to produce prompts better than you'd write yourself. Fast by default, deep-audit on request or auto-escalated for high-stakes.
prompt4ming
Clarify Mingtao's intended outcome from rough, voice-dictated, mixed Chinese-English, or self-correcting input while preserving his meaning and direct style. Use when Ming explicitly asks to optimize, clean up, clarify, or turn his words into a reusable prompt, or when ambiguity in dictated input prevents reliable execution. Do not invoke merely because his request is conversational or long.
think4ming
Ming's thinking-partner protocol. Run whenever Ming says 帮我想想 / 你先理解一下我的需求 / 帮我想一下 / 我在想一个事 / 这个你怎么看 / 你觉得呢 / think this through with me — or describes an idea, need, or problem and wants understanding and design thinking rather than immediate building. Restores the real need behind voice-dictated words, inventories current reality from the live system (not memory), opens the option space, gives ONE recommendation with trade-offs, and hands back only the decisions Ming himself must make. Thinking is the deliverable — do not implement while this skill is active. Works identically in Claude Code and Codex.
conclude-rounds
Conclude the last N rounds of the CURRENT conversation, in Chinese by default, AND hand back 5 evidence-based insights for working more efficiently with Claude Code. Read back over the recent exchanges — both the user's questions AND the assistant's answers, including code written, decisions made, and progress — then give a tight conclusion (what was asked, what was actually done and verified vs merely proposed, current state, open decisions) followed by 5 concrete Claude-Code-usage insights drawn from patterns in those rounds. N defaults to 4 and is read from what the user says (前4轮 / past 3 / 前面5个来回 / 前面两个问题). This is an IN-conversation recap, read-only — it never changes files, and it is NOT a cross-session daily digest. Run whenever the user says 总结前面N轮 / 总结一下前面 / 小结一下 / 结论一下 / 回顾前面几轮 / 前4轮 / 这几轮做了啥 / conclude the last N rounds / recap the last few rounds / summarize what we just did / catch me up on this thread — even without naming the skill. Works identically in Claude Code and Codex.
diagnose-project-rebuild
Diagnose a confused, inherited, partially lost, repeatedly rebuilt, or direction-changing project and establish the safest evidence-based foundation for what comes next. Use when the user says a project is chaotic, polluted by old decisions, only an older version survives, the original purpose must be rediscovered, they are unsure whether to recover/repair/rebuild/continue, or they want to restart without importing the prior project's strategy. Adapt the route to the project's actual failure mode rather than forcing a universal sequence.
experience-pack
Two-layer experience system for any project: keep a per-project EXPERIENCE.md ledger (dated entries: what happened, what we did, what it cost), then distill it through an experience-vs-decision boundary test into portable, noun-free lessons that other projects can safely reuse — experience inherits, decisions die. Ships a reference pack distilled from a real 5-rebuild contamination saga (source-lock bundles, planner/executor/ verifier role isolation, zero-context probes, quarantined banned-noun lists, bounded repair loops, multi-AI reference-not-instruction triage) plus five prevention advices. Use when the user says 经验包 / 记录经验 / 复盘 / 经验文件 / 沉淀经验 / experience pack / lessons learned / post-mortem / record this experience / distill experience / "what did we learn" / wants a project to learn from another project's history, or after any expensive incident worth recording. NOT for closing an iteration (use iteration-close) and NOT a decision register — decisions stay in the project's own truth files.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.