claude/ai-resources-plugin/skills/local-init/SKILL.md
This skill should be used when the user wants to initialize a new local private repository in the current directory. This sets up the .local directory for versioning private AI configuration files separately from the main repository.
npx skillsauth add amhuppert/my-ai-resources local-initInstall 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.
Description of private versioning pattern: !echo $HOME/.claude/agent-docs/local-files-pattern.md
mkdir .local && git -C .local init --bare:
!mkdir .local && git -C .local init --bare
Configure team repo: Make sure that .git/info/exclude is ignoring these private files:
# Example .git/info/exclude
# Ignore private repo
.local
# Ignore private files
.claude
CLAUDE.md
dev-local
memory-bank
Configure private repo:
.local/info/exclude is ignoring all files from the team repo (/*) and is whitelisting the private files (!.claude, etc)Configure post-checkout hook that makes the private repo branch auto-follow the team repo branch:
# .git/hooks/post-checkout
current_branch=$(git symbolic-ref --quiet --short HEAD 2>/dev/null)
echo "post-checkout hook, current branch is $current_branch"
if [ -n "$current_branch" ] && [ -d ".local" ] && command -v lgit >/dev/null 2>&1; then
echo "lgit - Switching to or creating branch $current_branch in .local repo"
lgit switch "$current_branch" 2>/dev/null \
|| lgit switch -c "$current_branch"
fi
tools
Use when picking or vetting a keyboard shortcut on macOS. Triggers include "what hotkey should I use for X", "is `<combo>` available", "does this shortcut conflict", "recommend a keybinding for…", "check `<combo>` against my setup", "pick a hotkey for…", or any mention of choosing/binding/changing a shortcut in WezTerm, tmux, Zed, Chrome, Claude Code, or macOS. Determines whether a proposed combo collides with OS-reserved bindings, app defaults, or the user's customizations, and recommends ergonomic alternatives when needed.
development
Detect and remove dead code with knip. Use when the user asks to "run knip", "find unused files", "find unused exports", "find unused dependencies", "clean up dead code", "remove dead code", "set up knip", "configure knip", "knip.json", "knip false positive", "knip CI", or mentions a `knip` config, dependency bloat, bundle bloat from unused imports, or tree-shaking unused exports. Covers the configuration-first workflow, confidence-gated deletion, framework-specific gotchas (Next.js 15+, Tailwind, Storybook, Jest, Bun's test runner and `bun build --compile`), monorepos, CI integration, and performance tuning.
tools
This skill should be used when the user asks to "set up react-scan", "install react-scan", "diagnose React re-renders", "find unnecessary renders", "find unstable props", "automate React render checks with Playwright", "react-scan + playwright", "measure component renders programmatically", "check why a React component is slow", or mentions React rendering issues, slow React interactions, render counts, or component-level perf attribution. Covers install across Next.js/Vite/Remix/script-tag/browser-extension, the lite headless API for CI, and the canonical render-attribution → fix → validate loop driven through Playwright.
documentation
This skill should be used when integrating source material into a knowledge base, including when the user asks to "integrate this document into the knowledge base", "add this transcript to the memory bank", "ingest this document", "update the knowledge base", "analyze a new source document", or "sync current-state docs with this source".