ds-ai-coding-skills
CLAUDE.md86 starsChanged 49 days agoMITView on GitHub
AGENTS.md carries the same content for GitHub Copilot and Codex. Everything from ## Hard Rules onward must match between the two files; scripts/sync_agent_docs.py --check enforces this. The ## Skills section at the end is Claude-specific. This is a Python 3.11 data science / analysis project. Detailed task-specific procedures are in .claude/skills/*/SKILL.md. Project-specific context is in docs/agent/*.
In this repository24 other files it gives its agents.
- AGENTS.mdAGENTS.md
- analysis-reportingSkill
- causal-inference-diagnosticsSkill
- dataframe-polarsSkill
- notebook-workflowSkill
- path-and-ioSkill
- plan-analysisSkill
- predictive-modeling-diagnosticsSkill
- prepare-prSkill
- python-project-opsSkill
- python-styleSkill
- review-sqlSkill
- run-edaSkill
- run-modelingSkill
- safe-data-handlingSkill
- simulation-optimization-diagnosticsSkill
- sql-analysisSkill
- statistical-inference-diagnosticsSkill
- statistical-ml-reviewSkill
- summarize-analysisSkill
- sync-agent-docsSkill
- unsupervised-eda-diagnosticsSkill
- update-agent-docsSkill
- visualizationSkill
The file
Show its rules and text
We split this CLAUDE.md into the rules it gives an agent
23 rules. About 0 are common, 12 are distinctive, and 11 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈12
Distinctive · estimate
This author's own choices. Worth a look.
11
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 14
Never commit raw data, credentials, API keys, tokens, or customer-level records.
- Distinctive: line 15
Never modify, overwrite, delete, or regenerate raw data directly.
- Distinctive: line 16
Prefer small, reviewable changes.
- Distinctive: line 18
Ask for clarification when data semantics are unclear.
- Very specific: line 19
Use uv exclusively for Python dependency management.
- Very specific: line 20
When applying a statistical, ML, causal, simulation, or optimization method, always apply the matching *-diagnostics skill (図と値をセットで出す).
- Distinctive: line 24
Use uv exclusively for all dependency management.
- Very specific: line 25
Never use pip, pip3, python -m pip, poetry, conda, pipenv, or easy_install.
- Distinctive: line 30
Never modify or delete raw data directly.
- Very specific: line 31
Treat data/raw and data/external as immutable.
- Very specific: line 59
Follow python-style skill: type hints, Google-style docstrings, Japanese comments.
- Very specific: line 60
Follow dataframe-polars skill: prefer polars over pandas.
- Very specific: line 61
Follow path-and-io skill: use pathlib.Path, no absolute paths.
- Very specific: line 65
Do not create, modify, or commit real data files under data/raw/ or data/external/ — these are immutable.
- Very specific: line 67
Only .gitkeep files and documentation (README, markdown) are acceptable to commit.
- Very specific: line 72
Use explicit column names.
- Distinctive: line 73
Use CTEs for readability.
- Distinctive: line 74
Add date filters for large tables.
- Very specific: line 76
Never run DROP, TRUNCATE, DELETE, or UPDATE unless explicitly requested.
- Distinctive: line 81
Keep restartable from a clean kernel.
- Distinctive: line 86
Write documentation in clear Japanese.
- Distinctive: line 87
Keep code snippets, commands, file paths, and config values in English as-is.
- Distinctive: line 88
Do not translate technical terms unnecessarily.
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
CLAUDE.md
AGENTS.md carries the same content for GitHub Copilot and Codex. Everything from
## Hard Rules onward must match between the two files; scripts/sync_agent_docs.py --check
enforces this. The ## Skills section at the end is Claude-specific.
This is a Python 3.11 data science / analysis project.
Detailed task-specific procedures are in .claude/skills/*/SKILL.md.
Project-specific context is in docs/agent/*.
Hard Rules (Always Apply)
- Never commit raw data, credentials, API keys, tokens, or customer-level records.
- Never modify, overwrite, delete, or regenerate raw data directly.
- Prefer small, reviewable changes.
- Explain assumptions before non-trivial analytical decisions.
- Ask for clarification when data semantics are unclear.
- Use
uvexclusively for Python dependency management. Never use pip, conda, poetry, or pipenv. - When applying a statistical, ML, causal, simulation, or optimization method, always apply the matching
*-diagnosticsskill (図と値をセットで出す).
Package Management
- Use uv exclusively for all dependency management.
- Never use pip, pip3,
python -m pip, poetry, conda, pipenv, or easy_install.
Data Safety
- Never commit raw data, credentials, API keys, tokens, or customer-level records.
- Never modify or delete raw data directly.
- Treat
data/rawanddata/externalas immutable.
Common Commands
uv sync
uv run pytest
uv run ruff check .
uv run ruff format . # ローカル整形
uv run ruff format --check . # CI用(差分チェックのみ)
uv run mypy src
uv run python scripts/check_no_raw_data_commit.py
uv run python scripts/check_no_sensitive_patterns.pyKey Conventions
- DataFrame operations: prefer polars over pandas.
- Visualization: use
fig, ax = plt.subplots(...), notplt.figure(...). - File paths: use
pathlib.Path, no absolute local paths. - Docstrings: Google-style.
- Inline comments: Japanese.
- Reports and documentation: Japanese.
File-Specific Guidelines
Python files (**/*.py)
- Follow
python-styleskill: type hints, Google-style docstrings, Japanese comments. - Follow
dataframe-polarsskill: prefer polars over pandas. - Follow
path-and-ioskill: use pathlib.Path, no absolute paths.
Data files (data/**)
- Do not create, modify, or commit real data files under
data/raw/ordata/external/— these are immutable. - Writing derived data to
data/interim/ordata/processed/is allowed in code, but do not commit large data files. - Only
.gitkeepfiles and documentation (README, markdown) are acceptable to commit. - See
safe-data-handlingskill.
SQL files (**/*.sql)
- Use explicit column names; avoid
SELECT *. - Use CTEs for readability.
- Add date filters for large tables.
- Validate join cardinality and row counts.
- Never run
DROP,TRUNCATE,DELETE, orUPDATEunless explicitly requested. - See
sql-analysisskill.
Notebooks (**/*.ipynb, notebooks/**/*.md)
- Keep restartable from a clean kernel; no secrets in outputs.
- See
notebook-workflowandsafe-data-handlingskills.
Documentation (README.md, docs/**/*.md)
- Write documentation in clear Japanese.
- Keep code snippets, commands, file paths, and config values in English as-is.
- Do not translate technical terms unnecessarily.
Skill Routing
| Task | Skill |
| Dependencies, tests, lint, type check, notebook execution | python-project-ops |
| Reading / writing / moving data files | safe-data-handling + path-and-io |
| Writing or reviewing SQL | sql-analysis |
| Writing or reviewing Python code | python-style |
| DataFrame operations | dataframe-polars |
| Charts and visualization | visualization |
| Notebook creation and editing | notebook-workflow |
| Running any statistical / ML / causal / simulation / optimization method | the matching *-diagnostics router (5 families, each routing to references/<method>.md): statistical-inference, predictive-modeling, causal-inference, unsupervised-eda, simulation-optimization |
| Reviewing someone else's statistics or ML work | statistical-ml-review |
| Analysis summaries and reports | analysis-reporting |
| File paths and I/O | path-and-io |
Project Context (docs/agent)
このリポジトリでしか通用しない知識だけを置く。作業手順・規約は skill 側が正本であり、
ここには重複させない(持ち運ぶ単位は .claude/skills/<name>/ ディレクトリ)。
ディレクトリ構成は README.md を参照する。
| Document | Purpose |
| project-overview.md | プロジェクトの目的とスコープ |
| data-catalog.md | データセット一覧と定義 |
| metrics-and-definitions.md | 指標定義 |
| diagnostics-reference-template.md | 診断 skill(*-diagnostics)への手法追加手順と雛形 |
Skills
@.claude/skills/python-project-ops/SKILL.md @.claude/skills/python-style/SKILL.md @.claude/skills/dataframe-polars/SKILL.md @.claude/skills/path-and-io/SKILL.md @.claude/skills/safe-data-handling/SKILL.md @.claude/skills/sql-analysis/SKILL.md @.claude/skills/notebook-workflow/SKILL.md @.claude/skills/statistical-ml-review/SKILL.md @.claude/skills/visualization/SKILL.md @.claude/skills/analysis-reporting/SKILL.md
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.

