wk-j

Generate a NotebookLM infographic cover image for a theme that already has a concept doc. Uploads the concept doc as a source, generates an editorial infographic, downloads it to the theme's docs/ folder, and adds it to the README.

Generate a Lexer markdown reader theme TOML file for a theme that already has a palette JSON. Covers meta, colors, syntax, typography, and effects sections.

Deploy editor and terminal themes from this repository to their local installation paths (Helix, Zed, Rio, Yazi, Lazygit, OpenCode, Lexer)

Generate a complete opencode TUI theme JSON file for a theme that already has a palette JSON. Covers all UI, markdown, syntax, and diff keys.

Generate a lazygit color theme config snippet for a theme that already has a palette JSON. Produces a ready-to-paste YAML block for the lazygit config file.

Generate complete Helix editor theme files (base + transparent variant) for a theme that already has a palette JSON. Covers every Helix scope including rainbow brackets.

Create a complete theme concept specification from a creative direction, reference image, or both. Extracts colors from images, proposes a theme name, and generates palette JSON, docs README, and concept document.

Post analysis comments on GitHub issues with AI attribution, appropriate labels, and a non-developer-friendly structure

Analyze GitHub issues and produce a structured markdown analysis document before any code changes — routes bug/improvement issues and question issues into separate document folders

Maintain GitHub repository Wiki pages safely in natural Thai as Open Knowledge Format-compatible markdown by categorizing important repository knowledge, auditing existing wiki content, drafting page changes, and publishing verified updates automatically. Use when asked to create, update, sync, reorganize, or audit a GitHub Wiki for a repository; do not use for README/docs edits in the main repo.

Import a skill from an external source (GitHub repo, URL, or local path) into this repo, rewriting project-specific details (file paths, company/team names, internal tool references, hard-coded URLs, domain examples) as generic patterns that work across any project. Use whenever the user asks to import, pull, copy, fetch, or add a skill from another repo or source.

Reference for the local external-source repos that are ground truth for Krypton's vendored deps and prior art — pi-mono (@mariozechner/pi-agent-core, pi-ai, pi-coding-agent), pretext (@chenglou/pretext text layout/measurement), Zed editor (ACP / MCP / agent-server / model-selection prior art), Obsidian Web Clipper (browser clipping, extraction, template rendering, Obsidian handoff), and Omnigent (multi-agent orchestration, native harnesses, Polly/Debby/Scribe examples). Use when working on src/agent/, debugging agent events, adding tools, or changing models/providers (pi-mono); creating text layouts/animations, measuring text without DOM, or rendering text to canvas/SVG (pretext); studying how Zed implements ACP, MCP context-server forwarding, external agent servers, or model selection for the ACP harness (zed); designing clipping/import flows, Markdown extraction, template engines, browser-extension surfaces, highlights, or Obsidian URI/CLI handoff (obsidian-clipper); or designing multi-agent orchestration,

Before writing any code for a new feature or significant improvement, perform deep research then write an implementation specification in docs/ and wait for explicit user approval. No code is written until the spec is approved.

Performance audit checklist for each window/view implementation. Run against a specific view or all views to identify rendering bottlenecks, leaked listeners, missing cleanup, and animation issues.

Convert a wiki concept page (wiki/concepts/*.md) into a Medium-style Thai blog post. Use when the user asks to "summarize concept as blog", "write blog post from concept", "Medium style Thai", or passes a concept filename and asks for a blog version.

Convert a wiki concept page (wiki/concepts/*.md) into a Medium-style Thai blog post. Use when the user asks to "summarize concept as blog", "write blog post from concept", "Medium style Thai", or passes a concept filename and asks for a blog version.

Answer any question and save it as a document in docs/question/. Use for general knowledge questions, how-things-work explanations, and non-feature topics.

Explain a specific Claude Code feature in detail. Use when the user asks any question about Claude Code features, capabilities, or how things work — even in casual conversation. Always generate documentation.

Create a new Ghost Signal audio theme from images, visual references, text descriptions, or concept prompts. Use this skill when users want to create a new sound theme from an image, photo, screenshot, or artwork. Also triggers on: "new theme", "create theme", "sound theme", "audio theme", "sound palette", "analyze this image", "theme from image", or any request to turn a visual into browser sounds.

When implementing new features in Lexer, always design as a Change Request (CR) document in docs/cr/ first before writing any code. Use this skill when asked to add a feature, implement functionality, create a new capability, or build something new.