project-organization
Expert guidance for setting up and organizing research software projects following established patterns for R packages, Julia packages, and research projects
What this skill does
# Project Organization Use this skill when creating new projects, scaffolding packages, or reviewing project structure to ensure consistency with established patterns. ## Quick Reference **R packages**: See [R project patterns](references/r-projects.md) **Julia packages**: See [Julia project patterns](references/julia-projects.md) ## Core Principles ### Project Root Structure Every project should have: ``` project/ ├── .claude/ # Claude Code project config (optional) │ └── CLAUDE.md # Or in project root ├── .github/ # GitHub Actions and templates │ └── workflows/ ├── .pre-commit-config.yaml ├── .gitignore ├── CLAUDE.md # Project-specific instructions ├── LICENSE.md ├── NEWS.md # Changelog ├── README.md # Or README.Rmd for R └── CITATION.cff # Citation metadata ``` ### CLAUDE.md Structure Every project CLAUDE.md should include: 1. **Package/Project Overview** - What it does, core purpose 2. **Development Commands** - How to test, build, document 3. **Architecture** - Key components and their relationships 4. **Testing Patterns** - Framework, conventions, special considerations 5. **Code Style** - Language-specific guidelines beyond global rules Template: ```markdown # CLAUDE.md This file provides guidance to Claude Code when working with this repository. ## Package Overview [Brief description of purpose and core functionality] ## Development Commands ```bash # Key commands with comments ``` ## Architecture ### Core Components - **Component**: Description - **Component**: Description ### Testing Patterns [Framework, conventions, file naming] ## Code Style [Project-specific rules beyond global CLAUDE.md] ``` ### Pre-commit Hooks All projects use pre-commit for automated quality checks: ```bash # Install pip install pre-commit pre-commit install # Run manually pre-commit run --all-files ``` Common hooks: - Trailing whitespace removal - End of file fixing - Large file checks - YAML validation - Language-specific linting and formatting ## When to Use This Skill Activate when: - Creating a new R or Julia package - Setting up a research project repository - Reviewing project structure for consistency - Adding configuration files to existing projects - Scaffolding CI/CD workflows For language-specific patterns, see the reference files.
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.