project-layout
有助于保持仓库整洁、便于协作与自动化处理。
规范计算科学仓库的目录布局并定义每个目录职责。
帮你把计算科学项目的仓库目录摆清楚：哪类文件放哪儿，每个目录要负责什么都写在一份权威布局文档里。适合新建仓库、重构或判断某个 notebook 是一次性还是该做成可复用的 script。特点是每个产物只有一个“家”、大体量数据不进版本库、AI 会话规划文件也不会混进交付物，便于长期维护。
▸ 展开 SKILL.md 英文原文
Use when starting a new computational-science project, restructuring an existing one, or deciding where a new module, script, notebook, dataset, or document belongs — including whether a piece of work is a notebook one-off or a reusable script, and maintaining the notebook series. Also use when reviewing whether a repository's layout still matches its documented map. Trigger phrases: "where should this file go", "set up the project structure", "scaffold the repo", "folder layout", "project organization", "does this belong in scripts or notebooks", "notebook or script", "should this be a notebook or a script", "make this rerunnable", "the notebook is stale", "promote this to a script".
帮我安装这个 skill：https://raw.githubusercontent.com/huguryildiz/ALETHEIA/main/skills/core/project-layout/SKILL.mdcurl -fsSL "https://raw.githubusercontent.com/huguryildiz/ALETHEIA/main/skills/core/project-layout/SKILL.md"# project-layout Propose and hold a canonical folder layout for a computational-science repository, and keep a single layout document that says what every directory is *for*. The layout is a contract: every artifact has exactly one home, bulk artifacts never enter version control, and AI-session planning files never mix with project deliverables. ## When to use - Scaffolding a new research repository. - Answering "where does this go?" for any new file. - Auditing an existing repo whose layout document has drifted from reality. ## When NOT to use - Mid-project wholesale reorganization without an explicit decision-log entry — moving directories breaks links, history, and muscle memory;