project-safety

Featured

Install or reconcile research-project safety rules and protected folder boundaries for data, code, outputs, and paper sources. Use when a project lacks guardrails or is being migrated into the governed structure. Not for auditing the full research scaffold; use $audit-project-research.

AI & Automation 144 stars 27 forks Updated 3 days ago MIT

Install

View on GitHub

Quality Score: 90/100

Stars 20%
72
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Project Safety Skill **CRITICAL RULE: Never delete data or code files. Never.** Use legacy/ folder for originals. Copy, don't move. > Establish safety rules and structures before Claude makes changes to research projects. ## Purpose Based on Scott Cunningham's workflow: prevent accidental data loss by establishing rules and using legacy folders before Claude reorganizes or modifies project files. ## When to Use - Starting a new research project folder - Before asking Claude to reorganize files - When Claude will be running code or modifying data - Setting up a project for collaborative work --- ## Safety Rules Template Add this to any project's CLAUDE.md file: ```markdown ## Safety Rules 1. **Never delete data files** — No .csv, .dta, .xlsx, .parquet, or any data format 2. **Never delete code files** — No .py, .R, .do, .tex, .md or scripts 3. **Use legacy/ folder** — If reorganizing, move originals to legacy/ first 4. **Copy from legacy, don't move** — Always preserve the original ### If you need to reorganize: 1. Create a legacy/ folder if it doesn't exist 2. Move ALL original files into legacy/ 3. Copy (not move) needed files into new structure 4. Never modify anything in legacy/ ``` --- ## Directory Structure After safety setup: ``` project/ ├── CLAUDE.md ← Safety rules + project context ├── README.md ← Project documentation ├── legacy/ ← PROTECTED: original files │ └── [all originals] ├── code/ │ ├── R/ │ ├── python/...

Details

Author
flonat
Repository
flonat/flonat-research
Created
7 months ago
Last Updated
3 days ago
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Listed

rule-file-organization

Where generated files belong. Archives, backups, handoffs, reports, and screenshots go under .claude/, never the project root. Load before writing any generated artifact.

5 Updated today
djnsty23
AI & Automation Listed

setup-research

Record a research project's launch commands, layout and doc conventions into its CLAUDE.md. Run once per project.

1 Updated 1 months ago
CUTEPKQ
Data & Documents Listed

project-structure

Scaffold a new personal project folder under a-projects/ with a standardized skeleton (master index, business/domain glossary, external-documentation folder, a stable home for design-decision sessions), or audit an existing organically-evolved project folder against that same convention and propose a migration plan for approval. Use this whenever the user wants to start a new project folder for ongoing multi-session work (a new client, initiative, or investigation), says things like "set up a project structure," "scaffold a project," "apply the project structure to X," or is about to create a new top-level folder/file in an existing a-projects/ folder without first checking whether an established convention already covers it. Also trigger proactively when a project folder has clearly grown ad hoc — multiple sessions each inventing new top-level folders with inconsistent naming (numbered vs. not, PascalCase vs. spaces vs. underscores) — even if the user hasn't explicitly asked to fix it.

1 Updated 1 weeks ago
justinmchoi