{"owner":"1jehuang","repo":"jcode","hasSkills":true,"totalSkillsCount":5,"totalTokensCount":1922,"categories":["claude-rule","root-instruction","mcp-config","marketplace","plugin-manifest"],"hasMcp":true,"mcpConfig":{"mcpServers":{"jcode":{"command":"npx","args":["-y","@modelcontextprotocol/server-jcode"]}}},"found":["CLAUDE.md","AGENTS.md",".cursor/mcp.json",".claude-plugin/marketplace.json",".claude-plugin/plugin.json"],"skills":{"CLAUDE.md":"# Repository Instructions\n\n@AGENTS.md\n\nFollow `AGENTS.md` for the development workflow and `CONTRIBUTING.md` for the\ncontribution policy. Pull requests from everyone are welcome for direct review\nand merging, regardless of contributor or maintainer status. Preserve unrelated\nwork and obtain user authorization before merging.\n","AGENTS.md":"# Repository Guidelines\n\n## Repository Scope\n\n- Jcode Desktop is in a separate repository.\n\n## TUI style\n\n- UI chrome must not wrap: startup headers, account rows, status labels, and\n  other compact UI rows should fit their available terminal-cell width or\n  truncate with an ellipsis. Count Unicode display cells, not characters.\n  Preserve one logical row per visual row, including at narrow widths.\n  Chat prose and other intentionally multiline content may wrap normally.\n- Reuse the info widget's limit-bar renderer for usage indicators instead of\n  introducing a different bar glyph, color, or used/remaining convention.\n\n## Development Workflow\n\n- **Use the user's Git identity** - Create commits with the configured\n  `user.name` and `user.email`. Do not override them with `Jcode`, `Jcode agent`,\n  or a fabricated agent email. Preserve existing contributor attribution when\n  integrating work. If no identity is configured, ask rather than inventing one.\n- **Welcome pull requests from everyone** - Review contributions on their merits,\n  regardless of whether the author is a maintainer, an existing contributor, a\n  first-time contributor, or an agent. Good PRs can be merged directly after review\n  and validation. Do not require a maintainer-authored rewrite merely because of\n  who submitted the change. See `CONTRIBUTING.md` for the contribution policy.\n- **Prefer master/main** - Work directly on the repository's primary branch\n  (`master` or `main`) by default. Do not create a branch or worktree merely to\n  start a task. Only do so when the user explicitly requests it or isolation is\n  genuinely necessary, and explain the concrete reason first.\n- **Keep work scoped** - Preserve unrelated work. If already on a branch with\n  ongoing changes, finish and integrate safely rather than switching blindly.\n  When the user asks you to review or integrate a PR or branch, you may inspect,\n  test, and integrate that contribution regardless of author status. Do not pull\n  in unrelated branches or merge a PR without user authorization.\n\n## Install Notes\n- `~/.local/bin/jcode` is the launcher symlink used from `PATH`.\n- `~/.jcode/builds/current/jcode` is the active local/source-build channel; self-dev builds and `scripts/install_release.sh` point the launcher here.\n- `~/.jcode/builds/stable/jcode` is the stable release channel; `scripts/install.sh` installs this and points the launcher here.\n- `~/.jcode/builds/versions/<version>/jcode` stores immutable binaries.\n- `~/.jcode/builds/canary/jcode` still exists for canary/testing flows, but it is not the primary self-dev install path.\n- On Windows, the equivalents are `%LOCALAPPDATA%\\\\jcode\\\\bin\\\\jcode.exe` for the launcher, `%LOCALAPPDATA%\\\\jcode\\\\builds\\\\stable\\\\jcode.exe` for stable, and `%LOCALAPPDATA%\\\\jcode\\\\builds\\\\versions\\\\<version>\\\\jcode.exe` for immutable installs; `scripts/install.ps1` currently installs the stable channel.\n- Ensure `~/.local/bin` is **before** `~/.cargo/bin` in `PATH`.\n\n## Verifying a change at runtime\n\n`cargo build` alone proves nothing about behavior. `jcode run` and interactive\nsessions are served by the long-lived daemon at\n`~/.jcode/builds/shared-server/jcode`, which is a symlink into\n`~/.jcode/builds/versions/<version>/`. Until that symlink is repointed and the\ndaemon restarted (`jcode self-dev --build`), a freshly built binary is inert and\nevery runtime check silently measures the old code.\n\nTo test a change without disturbing the shared daemon or the caller's session,\nrun your build against its own socket:\n\n```bash\ncargo build --profile selfdev\n./target/selfdev/jcode run --no-update --socket /run/user/1000/jcode-mytest.sock '<prompt>'\n```\n\nTwo things that waste time otherwise:\n\n- `crate::logging::info` writes to a log file, not stderr, so instrumenting a\n  code path with it produces no visible output under `--trace`. Use `eprintln!`\n  for throwaway diagnostics and delete it before committing.\n- Confirm which binary you are actually inspecting. `strings` on\n  `builds/shared-server/jcode` reads a 70-byte symlink, not a program; resolve it\n  with `readlink -f` first.\n",".cursor/mcp.json":"# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/1jehuang/jcode/HEAD/.cursor/mcp.json)",".claude-plugin/marketplace.json":"# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/1jehuang/jcode/HEAD/.claude-plugin/marketplace.json)",".claude-plugin/plugin.json":"# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/1jehuang/jcode/HEAD/.claude-plugin/plugin.json)"},"files":{"CLAUDE.md":"# Repository Instructions\n\n@AGENTS.md\n\nFollow `AGENTS.md` for the development workflow and `CONTRIBUTING.md` for the\ncontribution policy. Pull requests from everyone are welcome for direct review\nand merging, regardless of contributor or maintainer status. Preserve unrelated\nwork and obtain user authorization before merging.\n","AGENTS.md":"# Repository Guidelines\n\n## Repository Scope\n\n- Jcode Desktop is in a separate repository.\n\n## TUI style\n\n- UI chrome must not wrap: startup headers, account rows, status labels, and\n  other compact UI rows should fit their available terminal-cell width or\n  truncate with an ellipsis. Count Unicode display cells, not characters.\n  Preserve one logical row per visual row, including at narrow widths.\n  Chat prose and other intentionally multiline content may wrap normally.\n- Reuse the info widget's limit-bar renderer for usage indicators instead of\n  introducing a different bar glyph, color, or used/remaining convention.\n\n## Development Workflow\n\n- **Use the user's Git identity** - Create commits with the configured\n  `user.name` and `user.email`. Do not override them with `Jcode`, `Jcode agent`,\n  or a fabricated agent email. Preserve existing contributor attribution when\n  integrating work. If no identity is configured, ask rather than inventing one.\n- **Welcome pull requests from everyone** - Review contributions on their merits,\n  regardless of whether the author is a maintainer, an existing contributor, a\n  first-time contributor, or an agent. Good PRs can be merged directly after review\n  and validation. Do not require a maintainer-authored rewrite merely because of\n  who submitted the change. See `CONTRIBUTING.md` for the contribution policy.\n- **Prefer master/main** - Work directly on the repository's primary branch\n  (`master` or `main`) by default. Do not create a branch or worktree merely to\n  start a task. Only do so when the user explicitly requests it or isolation is\n  genuinely necessary, and explain the concrete reason first.\n- **Keep work scoped** - Preserve unrelated work. If already on a branch with\n  ongoing changes, finish and integrate safely rather than switching blindly.\n  When the user asks you to review or integrate a PR or branch, you may inspect,\n  test, and integrate that contribution regardless of author status. Do not pull\n  in unrelated branches or merge a PR without user authorization.\n\n## Install Notes\n- `~/.local/bin/jcode` is the launcher symlink used from `PATH`.\n- `~/.jcode/builds/current/jcode` is the active local/source-build channel; self-dev builds and `scripts/install_release.sh` point the launcher here.\n- `~/.jcode/builds/stable/jcode` is the stable release channel; `scripts/install.sh` installs this and points the launcher here.\n- `~/.jcode/builds/versions/<version>/jcode` stores immutable binaries.\n- `~/.jcode/builds/canary/jcode` still exists for canary/testing flows, but it is not the primary self-dev install path.\n- On Windows, the equivalents are `%LOCALAPPDATA%\\\\jcode\\\\bin\\\\jcode.exe` for the launcher, `%LOCALAPPDATA%\\\\jcode\\\\builds\\\\stable\\\\jcode.exe` for stable, and `%LOCALAPPDATA%\\\\jcode\\\\builds\\\\versions\\\\<version>\\\\jcode.exe` for immutable installs; `scripts/install.ps1` currently installs the stable channel.\n- Ensure `~/.local/bin` is **before** `~/.cargo/bin` in `PATH`.\n\n## Verifying a change at runtime\n\n`cargo build` alone proves nothing about behavior. `jcode run` and interactive\nsessions are served by the long-lived daemon at\n`~/.jcode/builds/shared-server/jcode`, which is a symlink into\n`~/.jcode/builds/versions/<version>/`. Until that symlink is repointed and the\ndaemon restarted (`jcode self-dev --build`), a freshly built binary is inert and\nevery runtime check silently measures the old code.\n\nTo test a change without disturbing the shared daemon or the caller's session,\nrun your build against its own socket:\n\n```bash\ncargo build --profile selfdev\n./target/selfdev/jcode run --no-update --socket /run/user/1000/jcode-mytest.sock '<prompt>'\n```\n\nTwo things that waste time otherwise:\n\n- `crate::logging::info` writes to a log file, not stderr, so instrumenting a\n  code path with it produces no visible output under `--trace`. Use `eprintln!`\n  for throwaway diagnostics and delete it before committing.\n- Confirm which binary you are actually inspecting. `strings` on\n  `builds/shared-server/jcode` reads a 70-byte symlink, not a program; resolve it\n  with `readlink -f` first.\n",".cursor/mcp.json":"# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/1jehuang/jcode/HEAD/.cursor/mcp.json)",".claude-plugin/marketplace.json":"# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/1jehuang/jcode/HEAD/.claude-plugin/marketplace.json)",".claude-plugin/plugin.json":"# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/1jehuang/jcode/HEAD/.claude-plugin/plugin.json)"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","rawUrl":"https://raw.githubusercontent.com/1jehuang/jcode/HEAD/AGENTS.md","title":"AI Agent Protocol & Instructions","category":"root-instruction","format":"markdown","content":"# Repository Guidelines\n\n## Repository Scope\n\n- Jcode Desktop is in a separate repository.\n\n## TUI style\n\n- UI chrome must not wrap: startup headers, account rows, status labels, and\n  other compact UI rows should fit their available terminal-cell width or\n  truncate with an ellipsis. Count Unicode display cells, not characters.\n  Preserve one logical row per visual row, including at narrow widths.\n  Chat prose and other intentionally multiline content may wrap normally.\n- Reuse the info widget's limit-bar renderer for usage indicators instead of\n  introducing a different bar glyph, color, or used/remaining convention.\n\n## Development Workflow\n\n- **Use the user's Git identity** - Create commits with the configured\n  `user.name` and `user.email`. Do not override them with `Jcode`, `Jcode agent`,\n  or a fabricated agent email. Preserve existing contributor attribution when\n  integrating work. If no identity is configured, ask rather than inventing one.\n- **Welcome pull requests from everyone** - Review contributions on their merits,\n  regardless of whether the author is a maintainer, an existing contributor, a\n  first-time contributor, or an agent. Good PRs can be merged directly after review\n  and validation. Do not require a maintainer-authored rewrite merely because of\n  who submitted the change. See `CONTRIBUTING.md` for the contribution policy.\n- **Prefer master/main** - Work directly on the repository's primary branch\n  (`master` or `main`) by default. Do not create a branch or worktree merely to\n  start a task. Only do so when the user explicitly requests it or isolation is\n  genuinely necessary, and explain the concrete reason first.\n- **Keep work scoped** - Preserve unrelated work. If already on a branch with\n  ongoing changes, finish and integrate safely rather than switching blindly.\n  When the user asks you to review or integrate a PR or branch, you may inspect,\n  test, and integrate that contribution regardless of author status. Do not pull\n  in unrelated branches or merge a PR without user authorization.\n\n## Install Notes\n- `~/.local/bin/jcode` is the launcher symlink used from `PATH`.\n- `~/.jcode/builds/current/jcode` is the active local/source-build channel; self-dev builds and `scripts/install_release.sh` point the launcher here.\n- `~/.jcode/builds/stable/jcode` is the stable release channel; `scripts/install.sh` installs this and points the launcher here.\n- `~/.jcode/builds/versions/<version>/jcode` stores immutable binaries.\n- `~/.jcode/builds/canary/jcode` still exists for canary/testing flows, but it is not the primary self-dev install path.\n- On Windows, the equivalents are `%LOCALAPPDATA%\\\\jcode\\\\bin\\\\jcode.exe` for the launcher, `%LOCALAPPDATA%\\\\jcode\\\\builds\\\\stable\\\\jcode.exe` for stable, and `%LOCALAPPDATA%\\\\jcode\\\\builds\\\\versions\\\\<version>\\\\jcode.exe` for immutable installs; `scripts/install.ps1` currently installs the stable channel.\n- Ensure `~/.local/bin` is **before** `~/.cargo/bin` in `PATH`.\n\n## Verifying a change at runtime\n\n`cargo build` alone proves nothing about behavior. `jcode run` and interactive\nsessions are served by the long-lived daemon at\n`~/.jcode/builds/shared-server/jcode`, which is a symlink into\n`~/.jcode/builds/versions/<version>/`. Until that symlink is repointed and the\ndaemon restarted (`jcode self-dev --build`), a freshly built binary is inert and\nevery runtime check silently measures the old code.\n\nTo test a change without disturbing the shared daemon or the caller's session,\nrun your build against its own socket:\n\n```bash\ncargo build --profile selfdev\n./target/selfdev/jcode run --no-update --socket /run/user/1000/jcode-mytest.sock '<prompt>'\n```\n\nTwo things that waste time otherwise:\n\n- `crate::logging::info` writes to a log file, not stderr, so instrumenting a\n  code path with it produces no visible output under `--trace`. Use `eprintln!`\n  for throwaway diagnostics and delete it before committing.\n- Confirm which binary you are actually inspecting. `strings` on\n  `builds/shared-server/jcode` reads a 70-byte symlink, not a program; resolve it\n  with `readlink -f` first.\n","isInternal":false,"tokens":956,"sizeBytes":4104},{"name":"CLAUDE.md","path":"CLAUDE.md","rawUrl":"https://raw.githubusercontent.com/1jehuang/jcode/HEAD/CLAUDE.md","title":"Claude Agent Guidelines & System Prompt","category":"claude-rule","format":"markdown","content":"# Repository Instructions\n\n@AGENTS.md\n\nFollow `AGENTS.md` for the development workflow and `CONTRIBUTING.md` for the\ncontribution policy. Pull requests from everyone are welcome for direct review\nand merging, regardless of contributor or maintainer status. Preserve unrelated\nwork and obtain user authorization before merging.\n","isInternal":false,"tokens":66,"sizeBytes":327},{"name":"marketplace.json","path":".claude-plugin/marketplace.json","rawUrl":"https://raw.githubusercontent.com/1jehuang/jcode/HEAD/.claude-plugin/marketplace.json","title":"Claude Plugin Marketplace Catalog","category":"marketplace","format":"json","content":"# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/1jehuang/jcode/HEAD/.claude-plugin/marketplace.json)","tokens":300,"sizeBytes":193},{"name":"plugin.json","path":".claude-plugin/plugin.json","rawUrl":"https://raw.githubusercontent.com/1jehuang/jcode/HEAD/.claude-plugin/plugin.json","title":"claude-plugin Plugin Manifest","category":"plugin-manifest","format":"json","content":"# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/1jehuang/jcode/HEAD/.claude-plugin/plugin.json)","tokens":300,"sizeBytes":179},{"name":"mcp.json","path":".cursor/mcp.json","rawUrl":"https://raw.githubusercontent.com/1jehuang/jcode/HEAD/.cursor/mcp.json","title":"Model Context Protocol (MCP) Configuration","category":"mcp-config","format":"json","content":"# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/1jehuang/jcode/HEAD/.cursor/mcp.json)","tokens":300,"sizeBytes":172}],"systemPromptSnippet":"<yakaai_skills repo=\"1jehuang/jcode\">\n<!-- File: AGENTS.md (Tokens: ~956 | Category: root-instruction) -->\n# Repository Guidelines\n\n## Repository Scope\n\n- Jcode Desktop is in a separate repository.\n\n## TUI style\n\n- UI chrome must not wrap: startup headers, account rows, status labels, and\n  other compact UI rows should fit their available terminal-cell width or\n  truncate with an ellipsis. Count Unicode display cells, not characters.\n  Preserve one logical row per visual row, including at narrow widths.\n  Chat prose and other intentionally multiline content may wrap normally.\n- Reuse the info widget's limit-bar renderer for usage indicators instead of\n  introducing a different bar glyph, color, or used/remaining convention.\n\n## Development Workflow\n\n- **Use the user's Git identity** - Create commits with the configured\n  `user.name` and `user.email`. Do not override them with `Jcode`, `Jcode agent`,\n  or a fabricated agent email. Preserve existing contributor attribution when\n  integrating work. If no identity is configured, ask rather than inventing one.\n- **Welcome pull requests from everyone** - Review contributions on their merits,\n  regardless of whether the author is a maintainer, an existing contributor, a\n  first-time contributor, or an agent. Good PRs can be merged directly after review\n  and validation. Do not require a maintainer-authored rewrite merely because of\n  who submitted the change. See `CONTRIBUTING.md` for the contribution policy.\n- **Prefer master/main** - Work directly on the repository's primary branch\n  (`master` or `main`) by default. Do not create a branch or worktree merely to\n  start a task. Only do so when the user explicitly requests it or isolation is\n  genuinely necessary, and explain the concrete reason first.\n- **Keep work scoped** - Preserve unrelated work. If already on a branch with\n  ongoing changes, finish and integrate safely rather than switching blindly.\n  When the user asks you to review or integrate a PR or branch, you may inspect,\n  test, and integrate that contribution regardless of author status. Do not pull\n  in unrelated branches or merge a PR without user authorization.\n\n## Install Notes\n- `~/.local/bin/jcode` is the launcher symlink used from `PATH`.\n- `~/.jcode/builds/current/jcode` is the active local/source-build channel; self-dev builds and `scripts/install_release.sh` point the launcher here.\n- `~/.jcode/builds/stable/jcode` is the stable release channel; `scripts/install.sh` installs this and points the launcher here.\n- `~/.jcode/builds/versions/<version>/jcode` stores immutable binaries.\n- `~/.jcode/builds/canary/jcode` still exists for canary/testing flows, but it is not the primary self-dev install path.\n- On Windows, the equivalents are `%LOCALAPPDATA%\\\\jcode\\\\bin\\\\jcode.exe` for the launcher, `%LOCALAPPDATA%\\\\jcode\\\\builds\\\\stable\\\\jcode.exe` for stable, and `%LOCALAPPDATA%\\\\jcode\\\\builds\\\\versions\\\\<version>\\\\jcode.exe` for immutable installs; `scripts/install.ps1` currently installs the stable channel.\n- Ensure `~/.local/bin` is **before** `~/.cargo/bin` in `PATH`.\n\n## Verifying a change at runtime\n\n`cargo build` alone proves nothing about behavior. `jcode run` and interactive\nsessions are served by the long-lived daemon at\n`~/.jcode/builds/shared-server/jcode`, which is a symlink into\n`~/.jcode/builds/versions/<version>/`. Until that symlink is repointed and the\ndaemon restarted (`jcode self-dev --build`), a freshly built binary is inert and\nevery runtime check silently measures the old code.\n\nTo test a change without disturbing the shared daemon or the caller's session,\nrun your build against its own socket:\n\n```bash\ncargo build --profile selfdev\n./target/selfdev/jcode run --no-update --socket /run/user/1000/jcode-mytest.sock '<prompt>'\n```\n\nTwo things that waste time otherwise:\n\n- `crate::logging::info` writes to a log file, not stderr, so instrumenting a\n  code path with it produces no visible output under `--trace`. Use `eprintln!`\n  for throwaway diagnostics and delete it before committing.\n- Confirm which binary you are actually inspecting. `strings` on\n  `builds/shared-server/jcode` reads a 70-byte symlink, not a program; resolve it\n  with `readlink -f` first.\n\n<!-- File: CLAUDE.md (Tokens: ~66 | Category: claude-rule) -->\n# Repository Instructions\n\n@AGENTS.md\n\nFollow `AGENTS.md` for the development workflow and `CONTRIBUTING.md` for the\ncontribution policy. Pull requests from everyone are welcome for direct review\nand merging, regardless of contributor or maintainer status. Preserve unrelated\nwork and obtain user authorization before merging.\n\n<!-- File: .claude-plugin/marketplace.json (Tokens: ~300 | Category: marketplace) -->\n# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/1jehuang/jcode/HEAD/.claude-plugin/marketplace.json)\n\n<!-- File: .claude-plugin/plugin.json (Tokens: ~300 | Category: plugin-manifest) -->\n# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/1jehuang/jcode/HEAD/.claude-plugin/plugin.json)\n\n<!-- File: .cursor/mcp.json (Tokens: ~300 | Category: mcp-config) -->\n# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/1jehuang/jcode/HEAD/.cursor/mcp.json)\n</yakaai_skills>"}