documentation-organization
Organize research project documentation - structure working files, prepare sharing packages, maintain clean project layout
What this skill does
# Documentation Organization for Research Projects
> **Supporting files in this directory:**
> - [migration-guide.md](migration-guide.md) - Migration from flat to directory-based organization, pattern reference, format debugging
> - [manifest-updates.md](manifest-updates.md) - MANIFEST update best practices, patterns, and checklists
> - [version-control-and-examples.md](version-control-and-examples.md) - Version control for document iterations, VGP project example
## Overview
Organize project documentation in a structured way that separates internal working files from shareable content. This makes it easy to:
- Find documents during development
- Prepare sharing packages
- Maintain clean professional documentation
- Collaborate effectively
## Recommended Structure
```
documentation/
├── README.md # Documentation index
│
├── data_descriptions/ # SHARE: Data understanding
│ ├── dataset_name_README.md
│ ├── column_definitions.md
│ └── data_sources.md
│
├── methods/ # SHARE: Methodology
│ ├── workflow.md
│ ├── analysis_plan.md
│ └── protocol.md
│
├── results/ # SHARE: Key findings
│ ├── analysis_summary.md
│ └── key_findings.md
│
├── reference/ # SHARE: External references (optional)
│ ├── citations.md
│ └── useful_resources.md
│
├── progress/ # INTERNAL: Development tracking
│ ├── PROGRESS.md
│ ├── session_YYYY-MM-DD.md
│ └── RESUME_HERE.md
│
├── action_reports/ # INTERNAL: What was done
│ ├── corrections_YYYY-MM-DD.md
│ ├── figure_regeneration.md
│ ├── data_verification.md
│ └── updates_summary.md
│
├── todos/ # INTERNAL: Planning
│ ├── priorities.md
│ ├── search_lists.md
│ └── task_tracking.md
│
├── internal/ # INTERNAL: Project management
│ ├── minimal_essential_files.md
│ ├── documentation_organization.md
│ └── notebook_issues.md
│
└── deprecated/ # INTERNAL: Old versions
├── old_analysis_v1.md
└── deprecated_workflow.md
```
## Categorization Guide
### data_descriptions/ (SHARE)
**Purpose**: Help recipients understand the data
**Include:**
- Dataset descriptions and README files
- Column/variable definitions
- Data sources and provenance
- Data quality notes
- Expected formats
**Examples:**
- `vgp_assemblies_README.md`
- `column_definitions.md`
- `data_sources.md`
- `karyotype_data_README.md`
### methods/ (SHARE)
**Purpose**: Explain how analysis was done
**Include:**
- Methodology documentation
- Analysis workflows
- Protocols and procedures
- Step-by-step guides
**Examples:**
- `karyotype_workflow.md`
- `analysis_plan.md`
- `data_fetching_protocol.md`
- `quality_control_methods.md`
### results/ (SHARE)
**Purpose**: Present findings and conclusions
**Include:**
- Analysis summaries
- Key findings
- Interpretation notes
- Publication-ready summaries
**Examples:**
- `analysis_summary.md`
- `complete_results.md`
- `haplotype_analysis_summary.md`
### reference/ (SHARE - optional)
**Purpose**: Provide additional context
**Include:**
- Citations and references
- Useful external resources
- Related work
- Background reading
### progress/ (INTERNAL)
**Purpose**: Track development and resume work
**Include:**
- Progress tracking files
- Session notes
- Resume-here files
- Status updates
**Examples:**
- `PROGRESS.md`
- `session_2026-02-05.md`
- `RESUME_HERE.md`
- `tier1_search_progress.md`
**Pattern matching:** `*progress*`, `*session*`, `*resume*`
### action_reports/ (INTERNAL)
**Purpose**: Document what actions were taken
**Include:**
- Corrections and fixes
- Update summaries
- Figure regeneration notes
- Data verification reports
- Migration documentation
**Examples:**
- `corrections_complete.md`
- `figure_regeneration_summary.md`
- `data_verification.md`
- `updates_summary.md`
- `migration_changes.md`
**Pattern matching:** `*correction*`, `*update*`, `*regeneration*`, `*restoration*`, `*verification*`, `*migration*`
### todos/ (INTERNAL)
**Purpose**: Planning and task management
**Include:**
- Priority lists
- Search task lists
- Task tracking
- To-do items
**Examples:**
- `karyotype_search_priorities.md`
- `analysis_todos.md`
**Pattern matching:** `*todo*`, `*priority*`, `*task*`
### internal/ (INTERNAL)
**Purpose**: Project meta-documentation
**Include:**
- Essential files documentation
- Organization notes
- Issue tracking
- Project management notes
**Examples:**
- `minimal_essential_files.md`
- `documentation_organization.md`
- `notebook_coherence_issues.md`
- `text_fixes_needed.md`
**Pattern matching:** `*essential*`, `*organization*`, `*issue*`, `*fixes*`, `*coherence*`
### deprecated/ (INTERNAL)
**Purpose**: Old versions kept for reference
**Include:**
- Deprecated files
- Old versions
- Superseded documentation
**Pattern matching:** `*deprecated*`, `*old*`, `*backup*`
## Sharing Package Selection
When creating sharing packages, include only these directories:
```python
SHARE_INCLUDE = [
'data_descriptions', # Essential for understanding data
'methods', # Essential for understanding methodology
'results', # Essential for understanding findings
'reference' # Optional: external references
]
INTERNAL_EXCLUDE = [
'progress', # Internal tracking
'action_reports', # Internal updates
'todos', # Internal planning
'internal', # Project management
'deprecated', # Old versions
'logs', # Runtime logs
'working_files' # Temporary files
]
```
## Implementation
### For New Projects
```bash
mkdir -p documentation/{data_descriptions,methods,results,reference,progress,action_reports,todos,internal,deprecated}
# Create documentation README
# For general project README templates, see the folder-organization skill
cat > documentation/README.md << 'EOF'
# Project Documentation
## For Recipients (Shareable)
- **data_descriptions/** - Understanding the data
- **methods/** - How the analysis was done
- **results/** - Key findings and summaries
## Internal (Development)
- **progress/** - Progress tracking and session notes
- **action_reports/** - Updates, corrections, verifications
- **todos/** - Task lists and priorities
- **internal/** - Project management
EOF
```
### For Existing Projects
Reorganize documentation gradually:
1. Create new structure
2. Move files to appropriate folders
3. Update any references
4. Test that notebooks still work
> **See [migration-guide.md](migration-guide.md)** for detailed migration commands, pattern reference table, and format debugging templates.
### In share-project Command
Update filtering to use directory-based exclusion:
```python
# Exclude entire directories
EXCLUDE_DIRS = ['progress', 'action_reports', 'todos', 'internal',
'deprecated', 'logs', 'working_files']
# Or include only specific directories
INCLUDE_DIRS = ['data_descriptions', 'methods', 'results', 'reference']
```
## Sharing Package Integration
### Directory-Based Filtering (Recommended)
When creating sharing packages from projects with organized documentation:
**Advantages**:
- Simple and maintainable (no complex pattern matching)
- Clear intent (directory name = purpose)
- Easy to audit (just look at directory list)
- Scalable (add new categories without updating filters)
**Implementation in share-project command**:
```python
def ignore_internal_dirs(dir, files):
"""Exclude internal documentation directories."""
ignore_list = []
for item in files:
# Exclude internal directories
if item in ['progress', 'action_reports', 'todos', 'internal',
'deprecated', 'logs', 'working_files', 'temp', 'tmp']:
ignore_list.append(item)
# Exclude hidden files except .gitkeep
elif item.startswith('.') and item !=Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.