KKenny0

@kkenny0 source repo

27 skills
0 followers
13 hours ago last updated

▌
Card Skill · kkenny0 bundle
Render text and evidence into polished, shareable PNG visuals with one consistent Kenny Style visual grammar. Use this skill whenever the user asks to turn words, notes, articles, quotes, arguments, stories, open-source repository or tool material, technical commands/workflows, explicit WeChat Reading highlights/thoughts, or WeChat Reading personal statistics into an 信息图/infographic, 海报/poster, 卡片/card, 大字报, whiteboard, visual summary, comic, sketchnote, social card grid, 开源工具介绍配图, 工具推荐卡片, GitHub 项目介绍插画, 小红书式竖版技术内容, 公众号头图, 博客封面, 正文配图, 正文解释图, 关系图, 流程图, 边界图, reading report, or non-summary editorial image for an essay. Trigger on phrases like 做成图, 渲染成图, 做张卡片, 卡片组, 处理这个开源工具, 技术工作流卡片, 做成漫画, 视觉笔记, 给文章配图, 微信读书划线做卡, article cover, blog hero, article diagram, process flow, and editorial image. Supports 9 output modes. Tone and explicit legacy design names affect color only; they never replace the house typography, geometry, spacing, material, or composition grammar. Do not use for websites, UI components, Figma protot

0
installs
▌
Social Content Kit · kkenny0 bundle
仅在用户明确要求社交媒体内容套件、多图轮播、公众号图文套件、文章与配图、配图规格，或显式调用 $social-content-kit 时使用，将 URL、文件或知识点转化为平台发布文案、按需文章与逐图自包含的 figure-spec；默认交付 publish-info 和 figure-spec，显式只请求文章时交付 article-draft，文章与配图或完整套件才交付三产物。用户用自然语言提到旧名 Folio 时也使用，但显式调用名已改为 $social-content-kit。仅需摘要、单篇文章或学习笔记时不隐式使用；显式调用除外。项目或工具内容直接生成面向采用决策的版本。

0
installs
▌
Weave Editorial · kkenny0 bundle
将已经完成研究、事实与引用核验的中文 Markdown 长文，按 faithful 保真模式或 publication 公共发布模式改写为一篇可同时发布到微信公众号和 X 长文的完整成稿。只要用户提到公众号发布、X 长文、跨平台成稿、提高传播力、重写标题或开头、调整叙事层级，尤其强调不删内容、保留次要材料时，都应使用本 skill。它不负责新增研究、事实核验、摘要、翻译、X thread、短帖、卡片、平台多版本或自动发布。

0
installs
▌
Weave · kkenny0 bundle
Multi-source research pipeline that produces evidence-grounded Chinese longform from a source bundle, technical project, or open domain. Deep Read handles prose sources, Source Dive reconstructs technical systems, and Survey uses a Learn-based six-phase research-to-writing workflow with an explicit Spine Direction Gate and sparse Visual Pass. Auto-scouts when the user provides only a topic. Use whenever the user asks in any language to 深入研究, 研究一下, 深度阅读, source dive, survey, 测绘领域, 从零讲懂, 让非专业背景也能读懂, 写一篇深度解析, 整理成研究文章, research, deep dive, study, or wants to understand material deeply enough to write about it.

0
installs
▌
Git Daily Note Updater · kkenny0 bundle
Generate or update Markdown daily notes from Git activity and Agent sessions, including research, design, review, diagnosis, writing, and uncommitted work. Use for daily notes, work logs, catch-up reports, or requests such as 更新日报, 写日报, 补日报, daily note, and work log.

0
installs
▌
Forge · kkenny0 bundle
概念锻造 — 跨域发现新概念连接，不是总结。输入 2+ 个 Source Brief、Topic Note、URL 或文本，输出锻造图（原子分解 → 跨域映射 → 碰撞 → 锻造产物）。当用户想要连不同领域想法、找结构性相似、创造新隐喻或框架、跨域知识迁移、或"把这些东西碰撞一下"时使用。

0
installs
▌
Debate · kkenny0 bundle
辩证推理 — 通过扬弃达到更高层次理解，不是罗列正反方。输入主张、争议、Source Brief Disputes 或 Synthesis Pack Conflicts，输出结构化辩证记录（钢铁侠建构 → 反题 → 扬弃）。当用户想要辩证分析争议、钢铁侠论证、压力测试主张、"把问题辩一辩"、或理解对立观点各抓住了什么时使用。

0
installs
▌
Survey · kkenny0 bundle
领域地貌测绘 — 从一个领域名或研究方向出发，产出结构化的领域地图（研究纲领 → 核心争议 → 演化脉络 → 开放问题 → 入门推荐）。三阶段流水线：侦察 → 测绘 → 撰述。当用户想要了解某个领域的全貌、快速进入一个新研究方向、找一篇综述式的领域地图、或者问"X 领域现在是什么状态"时使用。

0
installs
▌
Excavate · kkenny0 bundle
假设考古 — 挖掘主张下的隐藏假设和未审视前提。输入 Source Brief、Topic Note、URL 或主张，输出结构化挖掘报告（表层主张 → 推理结构 → 隐藏假设 → 根基评级）。当用户想要挖掘假设、找隐藏前提、质疑"常识"、理解"这个论点默认了什么"、或分析观点站不站得住时使用。

0
installs
▌
Deep Read · kkenny0 bundle
深度阅读非技术素材，输出完整研究文章。四阶段流水线：捕获→精读→综合→撰写。素材类型：论文（arxiv、期刊）、书籍章节、新闻报道、长文、访谈记录、行业报告、政策文件。一个 skill 从头到尾完成，不依赖外部 skill。当用户想要：深度阅读论文、研究非技术主题、把多份素材综合成文章、对论文做深度解析、把报告整理成研究文章、综合分析多份素材、理解一篇论文的核心思想并写成文章、深度研究某个话题（社会现象、商业模式、理论框架等非代码主题）时，都应该触发。即使用户只说"分析这篇论文"或"帮我读一下这个"——只要素材不是代码或技术项目，就应该用 deep-read 而不是其他 skill。用户分享论文 PDF/URL、arxiv 链接、报告文件并要求分析时，一律触发。不触发：GitHub URL / 源码分析 / 技术框架深度解析 → source-dive；纯 URL 抓取不分析 → read skill；vault 维护 → loom-maintain。

0
installs
▌
Source Dive · kkenny0 bundle
全自动流水线：从技术主题的官方文档 + GitHub 源码出发，经过发现、并行分析、结构化撰写，输出一篇完整的中文技术深度解析长文。零外部 skill 依赖，所有核心规则已内联。当用户想要深入研究某个技术项目、框架、工具、库的内部实现时，都应该使用这个 skill，即使用户没有明确说"写文章"。比如用户说"帮我看看 X 的架构"、"研究一下 X 的实现原理"、 "X 的源码是怎么工作的"、"深入分析 X 的设计"、"分析 X 的技术原理"、 "写一篇关于 X 的技术文章"、"深度研究 X"、"source dive X"，或者给了一个 GitHub URL 并要求理解其内部机制，都应该触发。

0
installs
▌
Loom Maintain · kkenny0 bundle
Validate, migrate, discover connections, generate evolution summaries, create Topic Notes, and rebuild indexes for a Loom vault. Use when the user asks to check vault health, migrate a legacy vault, find cross-topic connections, generate evolution reports, create or update Topic Notes, or rebuild indexes.

0
installs
▌
Taku Plan · kkenny0 bundle
Turn an approved design into an executable implementation plan. Three-step pipeline: scope + architecture review → design review (UI only) → plan writing. Auto-detects which step to start from based on project state. Invoke when DESIGN.md exists and is approved. Triggers on "write the plan", "create implementation plan", "plan this", "review this plan", "scope check", "architecture review", "design review", "is this plan buildable", "what could go wrong", "写计划", "制定方案", "规划实施", "架构评审", "这个方案可行吗", "有什么风险", or after /taku-think completes.

0
installs
▌
Taku Debug · kkenny0 bundle
When the user reports a bug, crash, error, or anything that is broken or behaving unexpectedly, invoke this skill FIRST — before writing any code or proposing any fix. This skill is the mandatory entry point for ALL bug-fix tasks. The user expects you to investigate root cause systematically before fixing. Without this skill, you will likely fix the symptom instead of the cause, which is the #1 debugging failure mode. Use this skill whenever the user says anything like: "fix this bug", "crashes", "returns null", "500 error", "not working", "wrong result", "throws exception", "timeout", "silent failure", "was working yesterday", "broke after deploy", "sometimes fails", "only in production", "works locally but not in CI/staging", "CLI crashes", "config missing", "test fails", or describes any error/stack trace. Also: "调试", "找bug", "报错", "排查问题", "不工作了", "挂了", "崩了", "数据不对". Do NOT use for: lint fixes, dependency updates, adding features, refactoring, or any task that is NOT about fixing broken behavior.

0
installs
▌
Taku Guard · kkenny0 bundle
Execution reliability expert. ALWAYS invoke this skill after any coding skill completes its work. Do not accept completed work without running this guard first. Use this skill to audit step execution and catch silent omissions.

0
installs
▌
Taku Think · kkenny0 bundle
Clarify ambiguous development requests, new feature ideas, product/design choices, and idea-stage work before planning. Three adaptive modes: Quick (small clear changes -> fast alignment), Design (feature requests -> architecture + DESIGN.md), Explore (new ideas -> forcing questions before committing). Triggers on "add a feature", "I have an idea", "should we build", "let's design", "设计一下", "需求分析", "我有个想法", or when the user describes a desired end state but implementation choices or success criteria are not yet settled. Also handles design system creation. Bug fixes and refactors use `/taku-debug` or `/taku-review` directly unless they need fresh design decisions.

0
installs
▌
Taku Review · kkenny0 bundle
Use after implementation is complete. Triggers after /taku-build. Analyzes diffs for security issues, bugs, and code quality. Run when asked to "review this", "check my diff", "code review", "审查代码", "看看有什么问题", "检查一下", "准备合并", "代码质量", or before shipping. Proactively invoke when the user is about to merge or land code changes.

0
installs
▌
Taku Compact · kkenny0 bundle
Create a recoverable active-work brief for context-heavy coding, design, debugging, review, research, or handoff sessions. Multi-mode context-control habit with resume, handoff, debug, review, design, and research policies.

0
installs
▌
Taku Reflect · kkenny0 bundle
User-invoked reflection. Three modes: Learn (script-backed recording, searching, pruning, exporting, and optional bootstrap for user-approved patterns, pitfalls, preferences, discoveries), Retro (weekly engineering retrospective with git commit analysis, metrics, team breakdowns, trends), and Write Skill (codify recurring learnings into reusable skills). Triggers on "what have we learned", "add learning", "show learnings", "weekly retro", "what did we ship", "engineering retrospective", "write a skill", "create a skill", "codify this pattern", "总结一下", "学到了什么", "记录一下", "回顾这周", "做个retro", "写个技能", "把这个模式固化". Also invoke when the user expresses satisfaction or frustration after completing work — these are natural reflection moments.

0
installs
▌
Daily · kkenny0 bundle
Generate or update workplace-facing daily reports from Tracework raw entries, using git only as limited fallback coverage. Supports work, personal, and private all-project scopes without mixing audiences. Use for "/tracework:daily", "更新日报", "写日报", "日报", "工作日志", "补日报", "daily note", or a dated daily work report. Do not use for agent handoff, meeting notes, generic prose reports, or git operations.

0
installs
▌
Query · kkenny0 bundle
Query Tracework's decision replay index for why a project chose a path, what alternatives were rejected, what should be revisited, what impact a decision had, or any natural-language question about project history. Use this skill for "/tracework:query", "why did we choose this?", "为什么当时这么选", "有没有被拒绝过的方案", "revisit this decision", "auth 迁移做到哪了", "我们讨论过 rate limiting 吗", or when a coding agent needs cited decision evidence before changing architecture, contracts, prompts, schemas, or product direction.

0
installs
▌
Recall · kkenny0 bundle
Recall recent project memory at the start of an agentic coding session. Use this skill for "/tracework:recall", when the user says "开工", "session start", "start session", "recall context", "继续上次", "接着做", or asks what to remember before implementing in the current repo. Intra-project only; does not do cross-project retrieval.

0
installs
▌
Weekly · kkenny0 bundle
Generate a workplace-facing weekly report from Tracework raw entries, using git only as limited fallback coverage. Supports work, personal, and private all-project scopes. Three modes: quick conversation review ("这周做了啥", "周报简版", "quick weekly", "本周概要"), default Markdown brief ("写周报", "周报", "/tracework:weekly", "weekly brief", "本周总结", "weekly report"), and PPT-ready Markdown Deck only when weekly PPT is explicit ("weekly PPT", "周报 PPT", "weekly slides", "演示大纲"). Do not use for daily notes, generic slide decks, or single-commit analysis.

0
installs
▌
Capture · kkenny0 bundle
Adaptive-depth session recap and low-friction checkpoint capture for report-ready Tracework memory. Use this skill for "/tracework:capture" or when the user signals end of a work session, such as "收工", "今天到这", "done", "wrap up", "that's it for today", "好了", or "先这样". Also trigger on explicit checkpoint or logging requests like "记录变更", "log changes", "记一下今天做了什么", "记一下当前进展", or "checkpoint". The skill dynamically routes the session to lite, standard, or deep capture depth; explicit "/tracework:capture lite|standard|deep" wording overrides that route. Use day mode for "/tracework:capture day", "扫描今天的会话", "补录今天", or "capture today". Do NOT trigger when the user is simply saying goodbye or switching topics.

0
installs
▌
Monthly · kkenny0 bundle
Generate a raw-first monthly management review, using Daily and Weekly reports as prior human judgments rather than semantic truth. Supports work, personal, and private all-project scopes. Use for "/tracework:monthly", "月报", "月度总结", "月度回顾", "monthly review", or monthly Daily Note archiving. Do not use for performance packaging or unsupported value claims.

0
installs
▌
Roadmap · kkenny0 bundle
Generate a narrative decision roadmap from accumulated raw entries in the Tracework knowledge vault. Use this skill for "/tracework:roadmap", when the user says "决策路线图", "decision roadmap", "项目决策历史", "decision history", "看看项目做了哪些关键决策", or when they want to understand how project decisions evolved over time. Also use this skill when the user wants to revisit abandoned alternatives, reassess past decisions, or find forgotten viable approaches.

0
installs
▌
Cold Start Interview · kkenny0 bundle
Configure Tracework's knowledge vault, project identity, and reporting group for first use. Use for "/tracework:cold-start-interview", "configure Tracework", "set up Tracework", "初始化 Tracework", or "配置 Tracework".

0
installs

27 published skills