[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DNFQ06MTGD1QYBH2TJ27VA":3,"skill-same:01M7DNFQ06MTGD1QYBH2TJ27VA":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7DNFQ06MTGD1QYBH2TJ27VA","svelte-code-navigation",null,"Use when locating Svelte symbol definitions or references, tracing callers, checking types or diagnostics, or assessing a Svelte rename or deletion.","nerymurillohnd\u002Fcodex-essentials","nerymurillohnd","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F248408027?v=4","01M7DNEZJ15FJPKZRPMDTAG09H","Nery Samuel Murillo","01M7DNEZJWE6SSDEC1G81HRMWJ",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fnerymurillohnd\u002Fcodex-essentials\u002Fblob\u002Fmain\u002Fplugins\u002Fsvelte-development\u002Fskills\u002Fsvelte-code-navigation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: svelte-code-navigation\ndescription: Use when locating Svelte symbol definitions or references, tracing callers, checking types or diagnostics, or assessing a Svelte rename or deletion.\n---\n\n# Svelte code navigation\n\nWhen LSP Intelligence's `lsp_` MCP tools are available, prefer them for supported semantic queries. Pass the current task's absolute `workspace_root` and source path; check diagnostic availability and freshness before interpreting an empty result. Retain this plugin's documentation, autofixer and project-check workflows. The helper below remains the fallback when the MCP is unavailable; its empty diagnostics alone do not establish a clean file.\n\nUse the packaged [local LSP client](..\u002F..\u002Fscripts\u002Fsvelte-lsp.mjs) for semantic questions when `svelteserver` is available on `PATH`. It starts the server for one query, opens a `.svelte` document, prints JSON, and exits. It defaults the Svelte server's file watcher to polling to avoid `EMFILE` in constrained Codex subprocesses; an existing `CHOKIDAR_USEPOLLING` value takes precedence. Node.js and `svelte-language-server` are user-installed requirements; this plugin does not install them.\n\n## Query\n\nResolve the installed plugin root from this skill's location, then run:\n\n```sh\nnode \u003Cplugin-root>\u002Fscripts\u002Fsvelte-lsp.mjs --root \u003Capp-root> --file src\u002Flib\u002FWidget.svelte --operation references --line 12 --character 8\n```\n\nThe position is **one-based** (first line and first character are 1) and characters count UTF-16 code units, as in LSP. A character after an emoji can therefore have a higher column than its visual code-point count. The JSON result uses the same one-based convention. Operations are `definition`, `references`, `hover`, `document-symbols`, `workspace-symbols` (add `--query NAME`), `incoming-calls`, `outgoing-calls`, and `diagnostics`. For symbol operations, put the position on the symbol's name. Start from a `.svelte` file even when references lead into TypeScript. The helper does not modify files.\n\nBefore a rename or delete: find the symbol, query references, and search text for route filenames, dynamic import strings, `import.meta.glob` patterns, CSS classes, and route paths. Those are not guaranteed to appear as semantic references. Check the project's own check script after an edit.\n\n## Full-project verification\n\nUse the project's `check` script when present (`npm run check`, `pnpm check`, or the project's package manager). If absent, run the already-installed `svelte-check` binary with the project's TypeScript configuration; SvelteKit may first need its existing sync command to regenerate `.svelte-kit` types. State that generated files may change. Do not install dependencies merely to make a check command available.\n\n`diagnostics` waits for a notification about the opened file; it is narrower than a full project check. Empty or failed LSP results require checking the file and position, then trying `document-symbols`. If `svelteserver` is absent or unresponsive, say so and use `rg` for text matches plus project checks for errors. Describe text matches as text matches, not as complete symbol references.\n","# Svelte code navigation\n\nWhen LSP Intelligence's `lsp_` MCP tools are available, prefer them for supported semantic queries. Pass the current task's absolute `workspace_root` and source path; check diagnostic availability and freshness before interpreting an empty result. Retain this plugin's documentation, autofixer and project-check workflows. The helper below remains the fallback when the MCP is unavailable; its empty diagnostics alone do not establish a clean file.\n\nUse the packaged [local LSP client](..\u002F..\u002Fscripts\u002Fsvelte-lsp.mjs) for semantic questions when `svelteserver` is available on `PATH`. It starts the server for one query, opens a `.svelte` document, prints JSON, and exits. It defaults the Svelte server's file watcher to polling to avoid `EMFILE` in constrained Codex subprocesses; an existing `CHOKIDAR_USEPOLLING` value takes precedence. Node.js and `svelte-language-server` are user-installed requirements; this plugin does not install them.\n\n## Query\n\nResolve the installed plugin root from this skill's location, then run:\n\n```sh\nnode \u003Cplugin-root>\u002Fscripts\u002Fsvelte-lsp.mjs --root \u003Capp-root> --file src\u002Flib\u002FWidget.svelte --operation references --line 12 --character 8\n```\n\nThe position is **one-based** (first line and first character are 1) and characters count UTF-16 code units, as in LSP. A character after an emoji can therefore have a higher column than its visual code-point count. The JSON result uses the same one-based convention. Operations are `definition`, `references`, `hover`, `document-symbols`, `workspace-symbols` (add `--query NAME`), `incoming-calls`, `outgoing-calls`, and `diagnostics`. For symbol operations, put the position on the symbol's name. Start from a `.svelte` file even when references lead into TypeScript. The helper does not modify files.\n\nBefore a rename or delete: find the symbol, query references, and search text for route filenames, dynamic import strings, `import.meta.glob` patterns, CSS classes, and route paths. Those are not guaranteed to appear as semantic references. Check the project's own check script after an edit.\n\n## Full-project verification\n\nUse the project's `check` script when present (`npm run check`, `pnpm check`, or the project's package manager). If absent, run the already-installed `svelte-check` binary with the project's TypeScript configuration; SvelteKit may first need its existing sync command to regenerate `.svelte-kit` types. State that generated files may change. Do not install dependencies merely to make a check command available.\n\n`diagnostics` waits for a notification about the opened file; it is narrower than a full project check. Empty or failed LSP results require checking the file and position, then trying `document-symbols`. If `svelteserver` is absent or unresponsive, say so and use `rg` for text matches plus project checks for errors. Describe text matches as text matches, not as complete symbol references.\n",{"name":5,"description":7},"main","5a594c6e779b4a440ca0ed4bfaa2f9983747ddaf","plugins\u002Fsvelte-development\u002Fskills\u002Fsvelte-code-navigation","https:\u002F\u002Fgithub.com\u002Fnerymurillohnd\u002Fcodex-essentials","https:\u002F\u002Fgithub.com\u002Fnerymurillohnd","https:\u002F\u002Fforestal-mt.com","Manager | Forestal MT","2026-11-01 17:23:43",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add nerymurillohnd\u002Fcodex-essentials --skill svelte-code-navigation",{"tool":38,"command":39},"bunx","bunx skills add nerymurillohnd\u002Fcodex-essentials --skill svelte-code-navigation",{"tool":41,"command":42},"pnpm","pnpm dlx skills add nerymurillohnd\u002Fcodex-essentials --skill svelte-code-navigation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnerymurillohnd\u002Fcodex-essentials\u002Fblob\u002Fmain\u002Fplugins\u002Fsvelte-development\u002Fskills\u002Fsvelte-code-navigation\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7DNG2RXK8GXCETABGYZT0DZ","example-workflow","Use when the user needs the specific workflow supplied by this plugin.","https:\u002F\u002Fgithub.com\u002Fnerymurillohnd\u002Fcodex-essentials\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills-only\u002Fskills\u002Fexample-workflow\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7DNFXX8B0X5R5VJ74QBSCEK","svelte-docs-and-autofixer","Use when a Svelte or SvelteKit task needs current official API documentation, a Svelte compiler check, autofixer feedback, or a Svelte playground link.","https:\u002F\u002Fgithub.com\u002Fnerymurillohnd\u002Fcodex-essentials\u002Fblob\u002Fmain\u002Fplugins\u002Fsvelte-development\u002Fskills\u002Fsvelte-docs-and-autofixer\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7DNFSKTVQQP0X73APMPPCAY","svelte-component-editor","Use when creating, editing, fixing, or migrating Svelte components, Svelte modules, SvelteKit routes, forms, loads, hooks, or related integration code.","https:\u002F\u002Fgithub.com\u002Fnerymurillohnd\u002Fcodex-essentials\u002Fblob\u002Fmain\u002Fplugins\u002Fsvelte-development\u002Fskills\u002Fsvelte-component-editor\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7DNFJQX9RE7RA17XJVH8D9H","svelte-code-auditor","Use when reviewing or auditing Svelte or SvelteKit code, a pull request, a migration, or framework-related security and accessibility concerns without editing source files.","https:\u002F\u002Fgithub.com\u002Fnerymurillohnd\u002Fcodex-essentials\u002Fblob\u002Fmain\u002Fplugins\u002Fsvelte-development\u002Fskills\u002Fsvelte-code-auditor\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7DNFF7YR51BNZ1PV4QCNHV4","svelte-best-practices","Use when implementing, reviewing, or migrating Svelte components, SvelteKit routes, Svelte CLI setup, Astro Svelte islands, or Tailwind styling in a Svelte project.","https:\u002F\u002Fgithub.com\u002Fnerymurillohnd\u002Fcodex-essentials\u002Fblob\u002Fmain\u002Fplugins\u002Fsvelte-development\u002Fskills\u002Fsvelte-best-practices\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7DNFBM5ZM4HYMQ6VD7ZN3V2","lsp-setup","Use when installing, verifying, updating, or troubleshooting the LSP Intelligence plugin and its local mcpls language-server runtime.","https:\u002F\u002Fgithub.com\u002Fnerymurillohnd\u002Fcodex-essentials\u002Fblob\u002Fmain\u002Fplugins\u002Flsp-intelligence\u002Fskills\u002Flsp-setup\u002FSKILL.md",[],[]]