fix-build
Skill1 starsChanged 43 days agoMITView on GitHub
构建失败、改完代码界面没反应、报错看不懂时,按这个顺序排查
2 other projects use a version of this.
Adopted by
Most recently taken up by
- iabhisekbosepm/claude-god-setuptheir own version, first seen Apr 7, 2026
- WhatIfWeDigDeeper/application-trackertheir own version, first seen Feb 10, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- iabhisekbosepm/claude-god-setup★ 1same name
- WhatIfWeDigDeeper/application-tracker★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- add-toolSkill
- design/comfyui-fluxSkill
- designSkill
- dev/refactor-safeSkill
- devSkill
- ensoul-mapSkill
- find-recipeSkill
- make-componentSkill
- make-pluginSkill
- pixal3d-comfyuiSkill
- prompt-protocolSkill
- troubleshootSkill
The file
Files
改了没反应 / 构建失败,怎么查
这个软件跑的是 dist/,不是 src/。 electron . 只读 dist。
改了源码没构建,界面一定没反应,而且无显式异常提示 —— 这是最隐蔽的一种排查陷阱:
不是报错,是静默地跑旧代码。
顺序
build_project拿完整错误。报错都在输出的末尾,前面全是噪声。- 主进程报错(
src/main/**)→tsc会指出文件和行号,直接去改。 - 渲染层报错(
src/renderer/**)→ vite 通常只说哪个文件、不说行号, 去那个文件找最近动过的地方。 - 类型错误的头号来源:改了
src/shared/types.ts的字段,忘了同步另外两处。 加一个字段通常要动三个文件:shared/types.ts、renderer/core/api.ts、preload/index.ts。少一个就是编译不过。 - 构建过了但界面还是旧的 → 只是没重启。
restart_project。
Windows 上"删不掉的小写文件"(TS1261)
报 TS1261: Already included file name 'D:/ensoul/src/renderer/panel/PanelSurface.tsx' differs from
file name 'D:/ensoul/src/renderer/panel/panelsurface.tsx' only in casing 时:
NTFS 不区分大小写,但目录里确实有两个只差大小写的条目。 Node 的 readdirSync /
fs.existsSync 看不见幽灵项,只有 cmd 看得见 —— 先 cmd /c "dir /a /b src\renderer\panel" 确认。
最要命的一点:del 小写名 删掉的是真身。 区分大小写不成立,del chatdock.tsx 就是删 ChatDock.tsx。
动手前一定先 git status,看到 D 说明源码已经被删了,git checkout -- <路径> 恢复。
把内容搬回正确文件名时不要 del + ren(两步都会动真身),用 node 一次做完:
node -e "const fs=require('fs');const b=fs.readFileSync('src/renderer/panel/chatdock.tsx');fs.unlinkSync('src/renderer/panel/chatdock.tsx');fs.writeFileSync('src/renderer/panel/ChatDock.tsx',b)"先 unlink 幽灵项,再 writeFile 正确名 —— 读和写都指向磁盘上真实存在的那一个。
几种"看起来像错误、其实不是"的情况
spawn EPERM/Access is denied:沙箱或杀软挡住了子进程。换一条命令,别硬顶。- 端口占用 / 新旧实例打架:旧实例没死干净。先
stop_project,再restart_project。 npm报Could not determine Node.js install directory:这是 npm 的 PowerShell 包装脚本(npm.ps1)找不到安装目录,不是项目的问题。用cmd /c "npm run build"或直接调node node_modules/typescript/bin/tsc。启动.cmd每次都会构建,所以双击启动拿到的永远是最新产物; 但restart_project走needsBuild()判断 —— 源码比产物新才构建。
构建通过 ≠ 改动生效
还要过一次 restart_project。而且如果改的是主进程(src/main/**),
重启是必须的;改渲染层同样需要重启,因为窗口加载的是构建产物,不做热更新。
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

