Fetch, categorize, and summarize GitHub Trending projects across daily, weekly, and monthly spans. Use when a user asks for "trending projects", "latest hot repos", or a "summary of GitHub trends" to provide a structured, categorised report with full hyperlinking. Supports Markdown, HTML (Pinterest design), or both output formats, with optional Obsidian vault storage.
Turn a local folder or GitHub repository into an interactive browser-based course that explains how the codebase works for non-expert programmers and AI-assisted builders. Use when a user asks to make a course, tutorial, walkthrough, learning guide, codebase explanation, or interactive lesson from a project.
Converts a PRD or broad technical requirement into an AI-executable agile workflow with cards, checklists, branch-diff mapping, review gates, and a final comparison report. Use when the user wants PRD review, agile card decomposition, AI execution tracking, implementation branch review, or PRD-to-code traceability.
Two complementary Bezos heuristics in one skill. (A) Two-Way Door — classify decisions by reversibility; reversible = decide fast with 70% info, irreversible = decide slow with 90% info. (B) Regret Minimization — for life-defining choices, project to age 80 and pick what minimizes regret. Use Two-Way Door triggers on Chinese 决策瘫痪 / 反复纠结小事 / 开了三次会还没定 / 大事小事一样慢; Regret Min triggers on 离职 / 创业 / 移民 / 结婚 / 生育 / 转行 / 重大决定 / 这辈子. Especially when team applies identical heavy process to all decisions (need Two-Way), or when user faces once-in-a-decade pivot where rational analysis ties (need Regret Min). Do NOT misclassify One-Way as Two-Way (most expensive mistake), use Regret Min for daily decisions (age-80 view on "what to eat" is meaningless), or run Regret Min in heated emotion (cool 24-48h first to avoid romanticizing risk).
Use BEFORE selecting any other decision framework — Cynefin (kuh-NEV-in) classifies WHICH framework fits the current situation across 5 domains (Clear / Complicated / Complex / Chaotic / Confused). Triggers when user is about to apply a method and the fit feels off, asks meta-questions like "should we follow SOP or explore?", or when same approach that worked last time seems wrong now. Also use after failure when "the method was right but the situation didn't match", or when team argues over deterministic-plan-vs-experimentation. Especially valuable at the start of major decisions to avoid using the wrong hammer for the nail. Do NOT use for trivial classified decisions (don't run Cynefin for "what to eat for lunch"), true Chaotic situations needing immediate stabilizing action (act first, classify later), or teams unfamiliar with the model (use simpler known/unknown binary).
Use when user reports overwhelm from too many tasks, asks for week/sprint/OKR planning help, or describes spending 'all day firefighting' while long-term projects stall. Triggers on Chinese phrases 太多事 / 不知道先做哪个 / 排不过来 / 周计划 / sprint planning / 救火 / 优先级 / overwhelm / 焦虑 / 做不完 / todo 列表炸了, and explicit task triage requests. Especially valuable when waiting list has 15+ pending items, or when user says "重要的事一直推不动 / 都在做紧急的事". Do NOT use for small lists (<5 items just sort by deadline), team-level responsibility assignment (use RAPID/DACI from backlog), or when importance needs quantitative weighting (use weighted decision matrix).
Use when user is stuck by industry conventions ("大家都这么做"), faces a new problem with no precedent, or finds current solutions arbitrarily expensive (intuition says "it shouldn't cost this much"). Triggers on Chinese phrases 行业惯例 / 大家都这么做 / 为什么不能 / 这么贵不合理 / 颠覆性 / 从零开始, and English signals "everyone does it this way", "why is it so expensive", "let's think from scratch". Decompose to irreducible physical/logical truths then rebuild — bypasses analogy thinking. Musk's secret. Do NOT use for problems with proven best practice (Cynefin Clear domain — use SOP), time-critical decisions (first principles takes hours-days), high-emotion contexts (cool down first), or in low-psychological-safety teams (will create conflict with authority).
Use for incident/bug root-cause analysis, postmortem, recurring-problem diagnosis, or process improvement. Triggers on Chinese phrases 复盘 / 根因 / postmortem / 又坏了 / 老是 / 重复出现 / 这不是第一次 / 为啥总是 / RCA, and English signals "this keeps happening", "RCA", "post-mortem", "incident review". Ask "why?" 3-7 times (5 is average not rule) until hit a process/system/design root that can be changed — not the symptom. Do NOT use for one-off random events (could be noise — observe first), Cynefin Complex-domain problems (5 Whys assumes linear causality, complex systems have multi-cause emergence), teams in blame-mode (Why will become 因为 X 不靠谱 chain), or truly unknowable causes (ML model outputs — use statistics not 5 Whys).