Skip to content

gpsaggese/helpers / .claude/skills/notebook.split_header_cells

notebook.split_header_cells

Verified

Split notebook header cells so each cell has a single header and comment

FileKindSize
SKILL.mdskill md1.7 KB
---
description: Split notebook header cells so each cell has a single header and comment
model: haiku
---

# Goal
- Split each markdown cell in a Jupyter notebook so it has at most one header

# Workflow

## Split Markdown Cells
- Make sure each markdown cell has at most one header and some text
  - **Bad** (there are 3 headers in the same cell: one H1, one H2, one H3)
    ```
    # %% [markdown]
    # Part 3: Composition Examples

    ## Example 1: Minimal End-to-End Workflow

    Rain -> Sprinkler -> Grass Wet
    
    ### Mental Model
    ```
  - **Good** (each header is in a different cell)
    ```
    # %% [markdown]
    # Part 3: Composition Examples

    # %% [markdown]
    ## Example 1: Minimal End-to-End Workflow

    Rain -> Sprinkler -> Grass Wet

    # %% [markdown]
    ### Mental Model
    ```

## Remove Empty Lines
- Remove empty lines at the start or end of a markdown cell
  - **Bad** (blank lines around the header)
    ```

    # %% [markdown]
    # Part 3: Composition Examples


    ```
  - **Good** (no blank lines around the header)
    ```
    # %% [markdown]
    # Part 3: Composition Examples
    ```

## Sync with Jupytext
- At the end, run `jupytext --sync` to update the paired Python notebook, per
  `# Code Architecture and Responsibility` -> `## Utilities vs. Notebook
  Responsibilities` in `.claude/skills/notebook.rules.md`

# Constraints
- Do not change or remove any Python code cell
- Do not change the content of the markdown text besides splitting cells

# Verification
- [ ] Confirm no markdown cell contains more than one header
- [ ] Confirm every Python code cell is unchanged
- [ ] Confirm the `.ipynb` and paired `.py` file are in sync via Jupytext
deprecation-and-migrationaddyosmani/agent-skillsManages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when migrating a database schema in production, such as renaming or dropping a column without downtime (expand/contract). Use when deciding whether to maintain or sunset existing code.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
performance-optimizationaddyosmani/agent-skillsOptimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
Agent Cost Reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
Agent Cost Reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json.Stars: 118kUpdated Claude CodeCodexVerifiedInstall