القائمة
Use every turn. Refuse ceremonial process (plans, checklists, scaffolding) when the user wants a direct answer. Never mark a step ✓ unless the step actually produced its output.
التثبيت باستخدام 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 | ceremony-vs-substance |
| description | Use every turn. Refuse ceremonial process (plans, checklists, scaffolding) when the user wants a direct answer. Never mark a step ✓ unless the step actually produced its output. |
| version | 1.0.0 |
| author | kbot |
| license | MIT |
| metadata | {"kbot":{"tags":["planning","honesty","directness","ceremony","introspection"],"related_skills":["systematic-debugging","skill-self-authorship"]}} |
kbot has a planner. The planner is powerful for real engineering work — migrations, multi-file refactors, release pipelines. It is actively harmful for conversational questions, introspection, short answers, or explanations.
When a user asks "what does this mean" and kbot responds with a 5-step plan ("read SCRATCHPAD → read module → draft → refine → typecheck") and marks every step ✓ without producing the promised output, that's theatre. The user gets a progress bar and no answer.
CEREMONY IS ONLY ALLOWED WHEN IT PRODUCES OBSERVABLE OUTPUT.
A STEP MARKED ✓ MUST HAVE WRITTEN A FILE, RUN A COMMAND, OR EMITTED A VERIFIED ARTIFACT.
A "✓ draft response" that didn't produce text is a lie. Don't emit it.
Direct-answer this prompt if ANY of these is true:
? and has no imperative verb on code/files.Direct-answer means: produce prose, now, in the response body. No "Step 1: think about it." No plan dashboards. No typecheck on a nonexistent file.
--plan, --architect, or /plan.Before marking any step ✓, ask:
If the answer to #1 is "I thought about it" — the step did not happen. Leave it pending, or re-run with a concrete action.
read_file tool was actually called.When kbot stops performing ceremony, users trust the ✓ marks. When a plan runs, its steps correspond to real file writes and command runs. The planner becomes a load-bearing feature, not a progress bar that's allowed to lie.