l-ccresdoc-build
Build and install the CCResDoc Tauri app locally. Use when: (1) User says 'build ccresdoc', 'rebuild ccresdoc', 'install ccresdoc', or 'l-ccresdoc-build', (2) User wants a fresh CCResDoc.app after changing Rust, frontend loading page, or doc site code under $HOME/.claude/doc/. Runs cargo clean -p, cargo tauri build, kills running app, replaces /Applications copy, clears quarantine.
Best use case
l-ccresdoc-build is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Build and install the CCResDoc Tauri app locally. Use when: (1) User says 'build ccresdoc', 'rebuild ccresdoc', 'install ccresdoc', or 'l-ccresdoc-build', (2) User wants a fresh CCResDoc.app after changing Rust, frontend loading page, or doc site code under $HOME/.claude/doc/. Runs cargo clean -p, cargo tauri build, kills running app, replaces /Applications copy, clears quarantine.
Teams using l-ccresdoc-build should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/l-ccresdoc-build/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How l-ccresdoc-build Compares
| Feature / Agent | l-ccresdoc-build | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Build and install the CCResDoc Tauri app locally. Use when: (1) User says 'build ccresdoc', 'rebuild ccresdoc', 'install ccresdoc', or 'l-ccresdoc-build', (2) User wants a fresh CCResDoc.app after changing Rust, frontend loading page, or doc site code under $HOME/.claude/doc/. Runs cargo clean -p, cargo tauri build, kills running app, replaces /Applications copy, clears quarantine.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Local CCResDoc Build & Install Cache-clean build of the CCResDoc Tauri app at `$HOME/.claude/doc/src-tauri/`, plus safe install to `/Applications/CCResDoc.app`. ## Why a skill `cp -rf` does NOT reliably update a macOS `.app` bundle — the old binary inside `Contents/MacOS/` can survive the copy. And Cargo sometimes reuses the cached release binary even after frontend changes in `$HOME/.claude/doc/dist/`. Run the steps below in order; do not substitute `cp -rf` or skip the clean. ## Step 1 — Clean cargo cache for the ccresdoc crate ```bash cd $HOME/.claude/doc/src-tauri && cargo clean -p ccresdoc --release ``` `-p ccresdoc` cleans only this crate's artifacts (seconds), not all Rust deps. `--release` is required because `cargo tauri build` uses the release profile. ## Step 2 — Build ```bash cd $HOME/.claude/doc/src-tauri && cargo tauri build ``` Takes ~1–2 minutes on cold cache. Outputs: - `$HOME/.claude/doc/src-tauri/target/release/bundle/macos/CCResDoc.app` - `$HOME/.claude/doc/src-tauri/target/release/bundle/dmg/CCResDoc_0.1.0_aarch64.dmg` ## Step 3 — Kill, move old bundle aside, copy fresh Use `mv` instead of `rm -rf` so the old bundle is replaced atomically (and recoverable from `/tmp` if the copy fails). Use `cp -R` (not `cp -rf`) on a path that no longer exists. ```bash killall ccresdoc 2>/dev/null killall CCResDoc 2>/dev/null sleep 1 mv /Applications/CCResDoc.app /tmp/CCResDoc-old-$$.app 2>/dev/null cp -R $HOME/.claude/doc/src-tauri/target/release/bundle/macos/CCResDoc.app /Applications/CCResDoc.app xattr -dr com.apple.quarantine /Applications/CCResDoc.app ``` `xattr -dr com.apple.quarantine` only strips the quarantine flag; it does not nuke all extended attributes. ## Step 4 — Verify the installed binary is fresh ```bash stat -f "%Sm %N" /Applications/CCResDoc.app/Contents/MacOS/ccresdoc stat -f "%Sm %N" $HOME/.claude/doc/src-tauri/target/release/bundle/macos/CCResDoc.app/Contents/MacOS/ccresdoc ``` The two timestamps should match within seconds (installed is slightly later — it was copied right after the build finished). If the installed binary is older than the source, the copy failed — go back to Step 3. ## Step 5 — Launch (optional) ```bash open /Applications/CCResDoc.app ``` Report the installed binary's timestamp so the user can confirm it's the fresh build. ## Notes - Binary name inside the bundle is `ccresdoc` (lowercase, from `Cargo.toml`), app name is `CCResDoc.app` (from `tauri.conf.json` `productName`). - The bundled frontend is only the loading spinner at `src-tauri/frontend/`. The real doc site is served at runtime by the sidecar (node `scripts/dev-stable.js`) or the axum fallback reading `$HOME/.claude/doc/dist/`. So for pure doc-content changes, no rebuild is needed — just rebuild `$HOME/.claude/doc/` (`pnpm build`) and re-open the app. - Rebuild this app only when Rust code in `src-tauri/src/`, the loading page in `src-tauri/frontend/`, or Tauri config changes.
Related Skills
zudoesa-articlify
Convert conversation context into an esa article via the zudoesa-writer subagent. ONLY invoke when the user explicitly asks — NEVER proactively propose. Triggers: 'write esa article', 'esa記事', 'esaに書いて', 'articlify for esa', or /zudoesa-articlify. Gathers context, creates a writing brief, delegates to the writer subagent.
zudoesa-apply-voice
Apply Takazudo's esa writing voice and vocabulary rules to text. Use when: (1) User wants to write/rewrite text in Takazudo's esa style, (2) User says 'apply voice', 'esa voice', 'esa文体で', 'esa風に書いて', '文体を適用', (3) User provides text to transform to esa style. Reads writing-style.md and vocabulary-rule.md from takazudo-esa-writing repo and applies the rules.
zudocg-articlify
Convert conversation context into a CodeGrid article via the zudocg-writer subagent. ONLY invoke when the user explicitly asks — NEVER proactively propose. Triggers: 'write codegrid article', 'CodeGrid記事', 'codegridに書いて', 'articlify for codegrid', or /zudocg-articlify. Gathers context, creates a writing brief, delegates to the writer subagent.
zudocg-apply-voice
Apply Takazudo's CodeGrid writing voice and vocabulary rules to text. Use when: (1) User wants to write/rewrite text in Takazudo's CodeGrid style, (2) User says 'apply voice', 'codegrid voice', 'codegrid文体で', 'codegrid風に書いて', '文体を適用', (3) User provides text to transform to CodeGrid style. Reads writing-style.md and vocabulary-rule.md from takazudo-codegrid-writing repo and applies the rules.
zpaper-articlify
Convert conversation context into a zpaper blog article via the zpaper-writer subagent. ONLY invoke when the user explicitly asks — NEVER proactively propose. Triggers: 'write zpaper article', 'zpaper記事', 'zpaperに書いて', 'articlify for zpaper', or /zpaper-articlify. Gathers context, creates a writing brief, delegates to the writer subagent.
zpaper-apply-voice
Apply Takazudo's zpaper blog writing voice and vocabulary rules to text. Use when: (1) User wants to write/rewrite text in Takazudo's zpaper style, (2) User says 'apply voice', 'zpaper voice', 'zpaper文体で', 'zpaper風に書いて', 'ブログ文体を適用', (3) User provides text to transform to zpaper style. Reads writing-style.md and vocabulary-rule.md from the zpaper repo and applies the rules.
xlsx
Spreadsheet creation, editing, and analysis. Use when working with .xlsx, .xlsm, .csv, .tsv files for: (1) Creating spreadsheets with formulas and formatting, (2) Reading or analyzing data, (3) Modifying existing spreadsheets while preserving formulas, (4) Data analysis and visualization, (5) Recalculating formulas.
x
Facade for development workflows. Routes on two axes: plan-first vs implement-now (escalates to /big-plan -a when the request needs research / decomposition / has unclear scope — the appended -a makes the plan chain into implementation in-session), then single vs multi on the ready-to-build fast paths (/x-as-pr single-topic, /x-wt-teams multi-topic parallel). Use when: (1) User says '/x' followed by dev instructions, (2) User wants to start development without choosing the workflow skill, (3) User says 'dev', 'implement', or 'build' with a task. Default option: -v (verify-ui). Review-loop (-l) is opt-in — without -l the downstream skill runs a single /deep-review pass. Forwards -a (autonomy/auto-chain) and -m (merge at the end + cleanup + CI watch) through every route; auto-fix of raised findings (-f) and issue-raising (-ri) are downstream defaults, with -nf/--no-fix and -nori/--no-raise-issues as the forwarded opt-outs. -a and -m are orthogonal — full hands-off end-to-end is -a -m.
x-wt-teams
Parallel multi-topic development using git worktrees, base branches, and Claude Code agent teams. Use when: (1) User wants to work on multiple related features in parallel, (2) User mentions 'worktree', 'base branch', 'parallel development', 'split into topics', or 'multi-topic'. FULLY AUTONOMOUS — creates worktrees, spawns teams, coordinates everything. Also supports Super-Epic child mode for [Epic] issues from /big-plan with '**Super-epic:** #N' markers (targets the super-epic base branch instead of main).
x-as-pr
Start a development workflow as a draft PR. Creates a NEW branch from the current branch, empty start commit, draft PR targeting the current branch, then implements. ALWAYS creates a new branch by default — produces a nested PR-on-PR when the current branch already has one. Use when: (1) User says 'dev as pr', (2) User wants a PR-first workflow before coding, (3) User passes -s/--stay to reuse the current branch instead of nesting, (4) User passes a GitHub issue URL to implement, (5) User passes --make-issue/--issue to create an issue first. Logs progress via issue comments when an issue is linked.
watch-ci
Watch GitHub PR CI checks in the background and notify on completion. Use when: (1) User wants to monitor CI/CD status, (2) User says 'watch CI', 'check CI', 'monitor checks', or 'wait for CI', (3) User wants to know when checks pass or fail. Runs a background gh polling shell loop (NOT a subagent — near-zero token cost), sends macOS notification on completion. Also handles merged PRs by watching the target branch CI.
w-update-wording-rule
Add or update wording rules (表記ルール) in the w repo's vocabulary-rule.md files. Use when: (1) User says 'add wording rule', 'update wording rule', '表記ルール追加', (2) User wants to add a kanji/hiragana usage rule, (3) User provides a rule like 'X should be Y' with examples.