菜单
Fix TS1261 when TypeScript reports two paths that differ only in casing (import vs include vs git index). Use when compile shows error 1261 or "Already included file name ... differs from file name ... only in casing".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Enforces Effect-TS patterns for services, errors, layers, and atoms. Use when writing code with Effect.Service, Schema.TaggedError, Layer composition, or effect-atom React components.
Consume the salesforcedx-vscode-services extension API. Use when an extension depends on salesforcedx-vscode-services and you are registering commands, calling its services (Workspace, Connection, Project, Settings, FS, Channel, Media, prompts), watching files/config/target-org, or wiring the AllServicesLayer/runtime in extensionProvider.ts.
package.json conventions for this repo. Use when editing/reviewing a package.json — name, types, browser, files, dependencies, devDependencies, packaging, scripts, or vscode contributes.
Prefer vscode-uri over node:path. Use when .ts files in /src import node:path or use path.join/basename/dirname/resolve, URI.file, or memfs paths.
Add custom SVG icons to salesforcedx-vscode-services for font generation. Use when adding new icons to media/icons-src, creating SVG icons for VS Code extension, or defining font-based icons.
TypeScript coding standards — apply when writing, reviewing, or refactoring .ts/.tsx, or naming/renaming .ts files (camelCase casing).
| name | ts1261-filename-casing |
| description | Fix TS1261 when TypeScript reports two paths that differ only in casing (import vs include vs git index). Use when compile shows error 1261 or "Already included file name ... differs from file name ... only in casing". |
Diagnostic 1261 in typescript (Already_included_file_name_0_differs_from_file_name_1_only_in_casing): one path comes from an import, another from include / program — same file on a case-insensitive disk, different casing in the string.
Typical cause: git tracks fooBar.ts but imports ./FooBar; or a case-only rename left the index with old casing.
Canonical name = what imports use (and consistent Pascal/camel across repo).
Case-insensitive FS (macOS default, Windows): case-only renames need a temporary middle name so git and the filesystem both update.
cd path/to/dir
git mv WrongCaseName.ts _tmp_rename.ts
git mv _tmp_rename.ts RightCaseName.ts
Then npm run compile.
git mv?git mv a.ts A.ts often no-ops or fails when a and A resolve to the same path — the two-step move is the reliable fix.
git rm / indexGoal is an index entry whose path string matches imports. git rm --cached <wrong-cased-path> removes that index entry; you still must put content on disk under the right cased name (again: use intermediate mv on case-insensitive FS). Two-step git mv updates index + working tree in one workflow without a detached delete step.
npm run compilegit ls-files path/to/dir | grep -i <basename> shows one line, casing matches importsgit mv if case-only change on case-insensitive FS