菜单
Use when any test fails, any bug surfaces, or any behavior is unexpected. Enforces root-cause analysis before code changes.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Creates distinctive editorial art direction for kernel.chat issues before implementation. Use when choosing an issue's visual concept, typography, composition, cover system, media grammar, responsive transformation, or motion intent; when a page feels generic or lacks character; or when original image and video assets need one coherent visual language.
Audits kernel.chat pages for responsive visual craft, accessibility, motion safety, interaction truth, runtime health, and production rendering. Use when reviewing an issue or artifact, checking whether a design is finished, comparing desktop and mobile, validating reduced motion or print, finding overflow and broken media, or proving that a published route matches the build.
Guides the design, layout, styling, and interactivity of kernel.chat editorial spreads and standalone artifact editions. Use this skill when editing or creating pages, React components, CSS files, or single-file HTML artifacts in the kernel.chat project to enforce the POPEYE-inspired bilingual design grammar and the interaction-language/artifact-language laws.
Use this skill to generate well-branded editorial interfaces and assets for kernel.chat ("Magazine for City Coders" — an independent magazine that is an unnamed homage to POPEYE), either for production or throwaway prototypes/mocks/etc. Contains essential design guidelines, colors, type, fonts, assets, and editorial UI components for prototyping.
Hand off a model from Blender (via BlenderMCP) into Unity (via MCP for Unity) — export the current Blender model, import it through import_model_file, and place it in the open scene. Use when the user has BlenderMCP and MCP for Unity both connected and wants to bring a Blender model into Unity. Does NOT drive Blender's own generators; BlenderMCP owns how the model got into Blender.
Generate images/videos/3D assets/audio via Higgsfield AI. Defaults: GPT Image 2 for image/design/text, Seedance 2.0 for video, Nano Banana 2/Lite/Pro for character/reference images, Marketing Studio for ads, Seed Audio 1.0 for audio. Use when: "generate an image", "make a video", "animate this photo", "image-to-video", "edit/stylize/remix this image", "reframe this video", "edit this video from a sketch", "create a 3D model/GLB", "create a sound effect", "make music", "text-to-audio", "create an ad", "make a UGC video", "unboxing", "presenter video", "import product from URL", or "analyze video virality". Supports image-to-3D (`multi_image_to_3d`), text-to-audio/music (`seed_audio`), workflow generation (`draw_to_video`, `reframe`), Marketing Studio, and Virality Predictor (`brain_activity`). Chain with higgsfield-soul-id for face/identity consistency. NOT for: Soul Character training (use higgsfield-soul-id), product photoshoots, marketplace listing cards, text/chat/TTS tasks.
| name | systematic-debugging |
| description | Use when any test fails, any bug surfaces, or any behavior is unexpected. Enforces root-cause analysis before code changes. |
| version | 1.0.0 |
| author | kbot |
| license | MIT |
| metadata | {"kbot":{"tags":["debugging","root-cause","investigation","tdd"],"related_skills":["test-driven-development","ship-pipeline","specialist-routing"]}} |
Random fixes waste time and create new bugs. Before writing a single line of fix, you must understand why it broke.
NO FIX WITHOUT A NAMED ROOT CAUSE.
If you can't finish the sentence "It broke because ___", you are not ready to edit.
Especially use this under time pressure — "quick fix" almost always means "new bug tomorrow."
Tools: bash to run the command, kbot_read to open the file at the stack trace line, git_diff to see what changed recently.
git log --oneline -20 and check the last commit that touched the area.Tools: grep for the bad value, git_log for history, subagent with Explore to map the call graph.
Do not write code yet. Share the hypothesis first if the user is watching.
test-driven-development).If your third fix attempt failed, stop. Don't try a fourth. The bug is not where you think it is, or the architecture is wrong. Escalate — use kbot_plan or hand off to a specialist agent.
kbot --thinking shows reasoning — use it when debugging complex issues.kbot --agent coder routes to the specialist with strongest code-patching track record.kbot --plan forces read-only investigation mode for Phase 1 & 2.forge_tool builds a throwaway diagnostic script when stdlib tools aren't enough.