{"owner":"ykdojo","repo":"claude-code-tips","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["CLAUDE.md"],"skills":{"CLAUDE.md":"# Project Instructions\n- Writing: keep user's voice, conversational, stick closely to what user said without making things up, but fix small grammar mistakes\n- After adding or renaming tips, run `node scripts/generate-toc.js` to update the table of contents\n- `~/.claude/CLAUDE.md` is symlinked to `GLOBAL-CLAUDE.md` in this repo\n- When committing changes to the plugin (skills, plugin.json, etc.), bump the patch version in both `.claude-plugin/plugin.json` and `.claude-plugin/marketplace.json`. Don't bump for non-plugin changes.\n- Git tags/releases (e.g. `v0.25.1`) and plugin versions (e.g. `0.14.9`) are separate. The git tag follows the repo release progression and is bumped for any change. The plugin version is only in `plugin.json` and `marketplace.json`.\n- After pushing a plugin change, update the local install non-interactively (no `/plugin` menu needed): `claude plugin marketplace update ykdojo` then `claude plugin update dx@ykdojo`. The CLI repopulates the versioned cache; a session restart is required to apply.\n\n# Filing Claude Code GitHub issues\n\nFor issues against `anthropics/claude-code`. When I ask you to file one:\n- Draft it to a temp file and open it in VS Code (`code <file>`) for me to review before filing - never file without showing me first.\n- File from host `gh` (`gh issue create`), not a container.\n\nStyle (based on my past issues):\n- Title: specific, states the symptom; flag regressions. No `[BUG]`/`[FEATURE]` prefix needed.\n- Lead with a one-sentence problem statement (no \"Description\" header). Keep it short and factual, no fluff.\n- Note the version where it broke / regression info when relevant.\n- Bug sections: `## Steps to reproduce`, `## Expected behavior` (+ `## Actual behavior` if useful), `## Environment` (OS, Claude Code version, terminal).\n- Feature requests: `## Problem`, then `## Suggestion` / `## Demonstration`.\n- Show concrete fenced code blocks for actual vs expected. Link relevant scripts/files inline rather than pasting them.\n"},"files":{"CLAUDE.md":"# Project Instructions\n- Writing: keep user's voice, conversational, stick closely to what user said without making things up, but fix small grammar mistakes\n- After adding or renaming tips, run `node scripts/generate-toc.js` to update the table of contents\n- `~/.claude/CLAUDE.md` is symlinked to `GLOBAL-CLAUDE.md` in this repo\n- When committing changes to the plugin (skills, plugin.json, etc.), bump the patch version in both `.claude-plugin/plugin.json` and `.claude-plugin/marketplace.json`. Don't bump for non-plugin changes.\n- Git tags/releases (e.g. `v0.25.1`) and plugin versions (e.g. `0.14.9`) are separate. The git tag follows the repo release progression and is bumped for any change. The plugin version is only in `plugin.json` and `marketplace.json`.\n- After pushing a plugin change, update the local install non-interactively (no `/plugin` menu needed): `claude plugin marketplace update ykdojo` then `claude plugin update dx@ykdojo`. The CLI repopulates the versioned cache; a session restart is required to apply.\n\n# Filing Claude Code GitHub issues\n\nFor issues against `anthropics/claude-code`. When I ask you to file one:\n- Draft it to a temp file and open it in VS Code (`code <file>`) for me to review before filing - never file without showing me first.\n- File from host `gh` (`gh issue create`), not a container.\n\nStyle (based on my past issues):\n- Title: specific, states the symptom; flag regressions. No `[BUG]`/`[FEATURE]` prefix needed.\n- Lead with a one-sentence problem statement (no \"Description\" header). Keep it short and factual, no fluff.\n- Note the version where it broke / regression info when relevant.\n- Bug sections: `## Steps to reproduce`, `## Expected behavior` (+ `## Actual behavior` if useful), `## Environment` (OS, Claude Code version, terminal).\n- Feature requests: `## Problem`, then `## Suggestion` / `## Demonstration`.\n- Show concrete fenced code blocks for actual vs expected. Link relevant scripts/files inline rather than pasting them.\n"},"items":[{"name":"CLAUDE.md","path":"CLAUDE.md","title":"CLAUDE.md","content":"# Project Instructions\n- Writing: keep user's voice, conversational, stick closely to what user said without making things up, but fix small grammar mistakes\n- After adding or renaming tips, run `node scripts/generate-toc.js` to update the table of contents\n- `~/.claude/CLAUDE.md` is symlinked to `GLOBAL-CLAUDE.md` in this repo\n- When committing changes to the plugin (skills, plugin.json, etc.), bump the patch version in both `.claude-plugin/plugin.json` and `.claude-plugin/marketplace.json`. Don't bump for non-plugin changes.\n- Git tags/releases (e.g. `v0.25.1`) and plugin versions (e.g. `0.14.9`) are separate. The git tag follows the repo release progression and is bumped for any change. The plugin version is only in `plugin.json` and `marketplace.json`.\n- After pushing a plugin change, update the local install non-interactively (no `/plugin` menu needed): `claude plugin marketplace update ykdojo` then `claude plugin update dx@ykdojo`. The CLI repopulates the versioned cache; a session restart is required to apply.\n\n# Filing Claude Code GitHub issues\n\nFor issues against `anthropics/claude-code`. When I ask you to file one:\n- Draft it to a temp file and open it in VS Code (`code <file>`) for me to review before filing - never file without showing me first.\n- File from host `gh` (`gh issue create`), not a container.\n\nStyle (based on my past issues):\n- Title: specific, states the symptom; flag regressions. No `[BUG]`/`[FEATURE]` prefix needed.\n- Lead with a one-sentence problem statement (no \"Description\" header). Keep it short and factual, no fluff.\n- Note the version where it broke / regression info when relevant.\n- Bug sections: `## Steps to reproduce`, `## Expected behavior` (+ `## Actual behavior` if useful), `## Environment` (OS, Claude Code version, terminal).\n- Feature requests: `## Problem`, then `## Suggestion` / `## Demonstration`.\n- Show concrete fenced code blocks for actual vs expected. Link relevant scripts/files inline rather than pasting them.\n","category":"root","tokens":499}]}