skills/l-ccresdoc-build/SKILL.md
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.
npx skillsauth add takazudo/claude-resources l-ccresdoc-buildInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Cache-clean build of the CCResDoc Tauri app at $HOME/.claude/doc/src-tauri/, plus safe install to /Applications/CCResDoc.app.
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.
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.
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.dmgUse 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.
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.
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.
open /Applications/CCResDoc.app
Report the installed binary's timestamp so the user can confirm it's the fresh build.
ccresdoc (lowercase, from Cargo.toml), app name is CCResDoc.app (from tauri.conf.json productName).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.src-tauri/src/, the loading page in src-tauri/frontend/, or Tauri config changes.development
Link Claude Code skill names mentioned in a CodeGrid article (data/{series}/{n}.md) to the author's public claude-resources repo, pinned to the latest commit hash so links don't rot. Use when: (1) user says 'linkify cc resources', 'link the skills', 'link skill names', or invokes /dev-linkify-cc-resources; (2) editing a CodeGrid article that mentions `/commits`, `/pr-complete`, `/skill-creator` or other Claude Code skills and they should point to claude-resources. Only links skills that actually exist in the public repo; skips hypothetical examples and code blocks.
development
Second opinion from Claude Opus on a plan or approach. Use when: (1) Planning phase of /big-plan needs a higher-quality review than /codex-2nd / /gco-2nd / /gcoc-2nd, (2) User says 'opus 2nd' or 'opus opinion', (3) Wanting Anthropic's larger model to critique a plan. Spawns a general-purpose Agent with model: opus that reads the plan file and returns structured feedback. Anthropic quota — not free.
tools
AI-based testing via subagent + a per-task test-flow skill. Use when the user wants to verify something that mechanical assertions can't fully capture — image recognition, visual size/position comparison, animation smoothness, multi-step manual flows that need AI judgment. Triggers: 'AI-based test', 'AI test', 'visual verify', 'image recognition test', 'manual operation test', 'human-eye check', 'verify visually', 'compare screenshots', 'looks the same', 'looks correct'. The skill's job is to (1) author a focused test-flow skill that captures the exact procedure + verdict criteria, then (2) dispatch a verification subagent via the Agent tool that loads BOTH the test-flow skill AND a browser-driving skill (/verify-ui primary, /headless-browser fallback) so the subagent has clear context and consistent verdicts. NEVER uses `claude -p` — subagent dispatch goes through the Agent tool exclusively.
development
End-of-workflow audit of touched GitHub issues, PRs, and branches via a Sonnet subagent. Use when: (1) /big-plan, /x-as-pr, or /x-wt-teams finishes its main work and needs to verify every touched resource is in the right state (closed when done, kept when ongoing, deleted when dead), (2) User says 'cleanup resources', 'audit cleanup', or 'check what should be closed', (3) A long workflow ends and the manager wants a structured paper trail of what it closed/kept/deleted. Auto-execute by default — the Sonnet agent proposes, the manager (you) executes safe actions and prints a final report.