## 中文 补齐已有 owner 与已锁定上游内容可证明的许可证、技能类型和收录版本。保留 Anthropic Source Available 和其他附加条件,不把所有内容统一标为 MIT,不提升 listing-only 的安装准入。 README 保留最新的双语结构及以 manifest 为准的数量口径,增加静态目录不存访问量、下载量、评分或 Stars 的边界。 发布兼容性:**本 PR 不包含**两支团队新增的本地化字段,也不包含微信支付 `latestVersion: 1.0`;旧客户端会拒绝这些新字段,另以待发布 PR 保留,等匹配客户端发布后再合并。 验证:47 项目录校验测试、19 项 i18n 测试、5 项合集生成测试通过;完整目录/i18n/翻译新鲜度检查通过,6 个固定来源合集的生成检查通过,2 个浮动来源按既有规则明确跳过。发现并修复了生成器在 Windows 使用反斜杠造成的误报:输出改为 POSIX 路径,比较规则不放宽、不重写合集数据。 ## English Fill only license, type and listed-release facts supported by existing owners or pinned upstream content. Preserve custom license restrictions and acquisition eligibility. Keep the current bilingual README and manifest-derived inventory; do not author usage analytics. This PR deliberately excludes localized team fields and the two-part WeChat Pay version that older clients reject. Those changes remain pending a compatible client release. Validation passes: 47 catalog-validator tests, 19 i18n tests, five collection-generator tests, complete catalog and translation checks, and generated inventory checks for six pinned collections. Two mutable sources remain explicitly skipped. Fix Windows-generated path separators without weakening comparison or changing declared children.
7.1 KiB
license, name, description, version, type, risk_level, status, disable-model-invocation, tags, provides, metadata, market
| license | name | description | version | type | risk_level | status | disable-model-invocation | tags | provides | metadata | market | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| MIT | code-intelligence | Use this skill when the user needs semantic code navigation backed by a Language Server: jump to definitions or implementations, find references, inspect hover/type information, list document or workspace symbols, or trace incoming and outgoing calls. For such requests you MUST load this skill first to unlock the hidden `Lsp` tool; do NOT answer them from `Grep`/`Glob` text matching without trying `Lsp`. Activate it for requests such as "where is this symbol defined", "find usages", "who calls this function", "show the file outline", or "search symbols in the workspace". A compatible Language Server must already be installed; this skill never installs one automatically. Use when 用户提到 跳转定义、查找引用、查找实现、类型信息、悬停信息、符号大纲、 工作区符号、调用关系、谁调用了这个函数、这个函数调用了谁、语义代码导航。 | 1.1.0 | procedural | low | enabled | true |
|
|
|
|
code-intelligence Skill
L0: One-line Summary
Use DesireCore's hidden Lsp tool for semantic code navigation through an already-installed Language Server.
L1: When to Use
Activate this skill when the task depends on symbol meaning rather than text matching:
- Jump to a symbol's definition or implementation.
- Find all semantic references to a symbol.
- Inspect type information or documentation at a source position.
- List the symbols in one file or search symbols across the workspace.
- Find callers and callees through the LSP call hierarchy.
Hard rules
- Semantic-navigation requests (definitions, references, implementations, call relations, symbols) MUST try
Lspfirst; never answer them fromGrep/Globtext matching without tryingLsp. - Falling back to text search is allowed only when: the
Lspcall errors, the target language is not in the supported mappings, or the Language Server is missing and the user has not asked to install it. - Every answer that falls back to text search MUST explicitly tell the user that the result comes from text matching, not semantic analysis, and why (for example "typescript-language-server is not installed"). In large repositories, or with same-named symbols, overloads, or inheritance, text matching can be wrong — never let the user mistake it for semantic navigation.
- Purely textual searches (string literals, log copy) are out of scope for this skill; use
Grep/Globdirectly.
L2: Operating Procedure
1. Check the workspace boundary
Lsp starts an external indexing process that can read the authorized workspace. The target file therefore needs directory-level read access. If the tool reports that an exact-file grant is insufficient, ask the user to authorize the project directory through ManageWorkDirs; never widen the scope silently.
2. Choose one operation
| Operation | Purpose | Required input |
|---|---|---|
goToDefinition |
Find where a symbol is defined | file, line, character |
findReferences |
Find semantic references, including the declaration | file, line, character |
hover |
Read type information or documentation | file, line, character |
documentSymbol |
Outline symbols in one file | file |
workspaceSymbol |
Search named symbols in the current workspace | file, non-empty query |
goToImplementation |
Find concrete implementations | file, line, character |
prepareCallHierarchy |
Resolve a callable item at a position | file, line, character |
incomingCalls |
Find functions or methods that call the target | file, line, character |
outgoingCalls |
Find functions or methods called by the target | file, line, character |
line and character are 1-based, matching editor coordinates. Character offsets use UTF-16 semantics.
3. Treat results as bounded navigation evidence
- Results are filtered by the active read scope and workspace
.gitignorerules. - Use
maxResultsto keep broad reference or symbol searches focused; the maximum is 200. - A first request may take longer while the server indexes the workspace.
- Re-run the request after source files change; DesireCore synchronizes the latest saved UTF-8 content.
4. Handle missing servers without modifying the system
DesireCore only discovers installed binaries and returns an installation hint when one is missing. Do not run that installation command unless the user explicitly asks you to install the dependency.
Supported built-in mappings:
- TypeScript/JavaScript:
typescript-language-server - Python:
pyright-langserver - Go:
gopls - Rust:
rust-analyzer
5. Fallbacks
- Unsupported file type or missing server: use
Grep,Glob, andReadfor text-level investigation, and explicitly tell the user — per the hard rules — that the result comes from text matching, not semantic analysis, and why. - Server does not advertise an operation: report that capability mismatch instead of guessing.
- Empty semantic result: explain that the symbol may be unresolved, excluded, or filtered by access rules; do not claim the symbol has no usages without qualification.