dunnlab-defaults

Enforce Dunn Lab coding conventions across Python, R, and Rust projects.

2|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/caseywdunn/dunnlab_code --skill dunnlab-defaults
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dunnlab-defaults
Source: https://github.com/caseywdunn/dunnlab_code/tree/main/skills/dunnlab-defaults
Command: npx skills add https://github.com/caseywdunn/dunnlab_code --skill dunnlab-defaults

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes and enforces Dunn Lab coding conventions and defaults across projects, reducing onboarding time and drift.

Core Features & Use Cases

  • Establishes language guidelines (Python, R, Rust), environment management, and dependency handling.
  • Provides naming conventions, documentation standards, and performance considerations to ensure reproducibility.
  • Use Case: Start a new Dunn Lab project with a consistent structure, environment file, and linting rules.

Quick Start

Apply Dunn Lab defaults when starting a new project to initialize structure and tooling.

Frequently Asked Questions about dunnlab-defaults

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a new Python or R project structure for reproducibility?

Establish project reproducibility by applying standardized coding conventions that prescribe repository layout, environment management, and dependency handling across Python, R, and Rust workflows.

What are coding conventions for maintaining consistent linting and documentation?

Coding conventions for linting and documentation enforce specific naming conventions and docstring styles across your codebase to ensure maintainability and reduce project drift.

Can I use these project defaults across Python, R, and Rust environments?

Yes, these defaults support environment management and dependency handling across Python, R, and Rust workflows, providing consistent naming and documentation standards for each language.

What's the best way to standardize repository layout and environment files for a new lab project?

The best way to standardize a lab project is to apply coding defaults upon initialization, which establishes the standard repository layout, environment files, and linting rules.

Why do I need performance guidance and coding defaults when starting analysis scripts?

You need performance guidance and coding defaults when starting analysis scripts to ensure reproducibility and maintainability, reducing onboarding time and preventing convention drift across projects.