Menu
Use when the user wants to start work on a specific GitHub issue — phrases like "let's work on issue
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when adding a CodeMirror 6 extension to the editor — phrases like "add Tab/Shift+Tab support", "add a keymap", "support Ctrl+B for bold", "add a dark theme toggle", "swap the CodeMirror theme", "add a CodeMirror extension". Several roadmap items (Tab support, key shortcuts, dark mode for the editor) all flow through this skill. Enforces the lifecycle invariants documented in `src/components/Editor/CLAUDE.md`.
Use when the user asks to commit changes, create a commit, or stage and commit. Drafts a commit message following Lumark's `<type>(<issue#>): <subject>` convention, deriving the issue number from the current branch name (e.g. branch `47-add-delete-buttons-to-files` → `(47)`). Selects `feat` / `fix` / `chore` / `doc` based on what's changed.
Use whenever the user asks about a library, framework, SDK, API, CLI tool, or cloud service — even well-known ones (React, Tauri, CodeMirror, Tailwind, Vite, ESLint, lucide-react, react-markdown, remark, rehype, Rust crates, etc.). Includes API syntax, configuration, version migration, library-specific debugging, setup, CLI usage. ALWAYS consults Context7 (`mcp__context7__*`, configured in `.mcp.json`) — never relies on training data for library docs. Skip for: refactoring, writing scripts from scratch, debugging business logic, general programming concepts.
Use when `yarn lint` reports errors or warnings, or when the user asks to fix lint issues, format code, or clean up style. Triggers on phrases like "fix lint errors", "the linter is failing", "run lint:fix", "clean up style". Reads `eslint.config.mjs` to understand which rules apply and respects existing repo conventions.
Use when the user wants to add a new Tauri IPC command — anything reachable via `invoke('name', ...)` from React. Triggers on phrases like "add a Tauri command", "expose X to the frontend", "create a new `#[tauri::command]`", "add IPC for Y". Enforces the three-step contract (Rust fn + invoke_handler! registration + frontend wiring) and the file-extension contract.
Use when the user wants to **call an existing Tauri command** from a new place in the frontend — adding a button that loads a file, a UI action that triggers an existing IPC, etc. Distinct from creating a new command. Triggers on phrases like "call `load_files` from this component", "wire up the existing IPC", "invoke X from the frontend". For creating NEW commands, use `ipc-command-creator` instead.
| name | issue-starter |
| description | Use when the user wants to start work on a specific GitHub issue — phrases like "let's work on issue |
You're starting work on a GitHub issue. Set up the branch and orient the user (or yourself) on what's needed.
From the user's message — #51, issue 51, 51-, etc. If ambiguous or missing, ask.
gh issue view <n>
If the user doesn't have gh authenticated or the command fails, ask them to authenticate (gh auth login — they need to run this themselves with ! gh auth login) or paste the issue text manually.
Capture from the output:
good first issue / bug / enhancement, mention to the user.closed, stop and surface that to the user before doing anything else.In parallel:
git status
git branch --show-current
Then:
main, ask before checking out main.git fetch origin main to see if local main is behind. Don't pull without asking.Format: <issue#>-<kebab-case-summary>. Examples seen in this repo:
47-add-delete-buttons-to-files51-prepare-a-framework-for-claude-codeDerive the kebab-case summary from the issue title:
--)If the GitHub "Create a branch" button has already generated a name on the issue page, prefer that exact string (the user can paste it). Otherwise generate one and show it to the user before creating.
git checkout -b <issue#>-<kebab-summary>
After branch is created, give the user a short orientation:
src-tauri/src/lib.rs + src/contexts/AppProvider.tsxsrc/components/Editor/Editor.tsxsrc/components/UI/src/components/Layouts/MainLayout/FilesPanel/Don't start making code changes yet. The user may want to plan, ask questions, or split the work across multiple sessions.
committer will, on first commit, if you set upstream then.