@pikaa-ai/pikaa 0.3.23 → 0.3.24

package/skills/matlab/SKILL.md

@@ -1,274 +0,0 @@
----
-name: matlab
-description: Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
-license: MIT
-compatibility: >-
-  Documentation is pinned where noted to proprietary MATLAB R2026a and free
-  GNU Octave 11.3.0. Bundled Python CLIs require Python 3.11+ and run locally
-  without MATLAB or Octave; optional MAT inventory uses scipy and/or h5py.
-allowed-tools: Read Write Bash Glob Python
-metadata:
-  version: "1.1"
-  skill-author: "K-Dense Inc."
-  last-reviewed: "2026-07-23"
----
-
-# MATLAB and GNU Octave
-
-Use this skill to design or review numerical code, migrate MATLAB releases,
-prepare reproducible projects, and plan trusted execution. MATLAB and GNU
-Octave are distinct products: compatibility is partial, not a license or
-behavior guarantee.
-
-## Product and license gate
-
-- **MATLAB R2026a is proprietary.** Do not assume MATLAB, MATLAB Online, a
-  named toolbox, MATLAB Test, MATLAB Compiler, MATLAB Coder, Parallel Computing
-  Toolbox, or an add-on is installed, licensed, or available to the user.
-- **MATLAB Runtime is not MATLAB.** It runs compatible applications produced
-  with MATLAB Compiler; it cannot run arbitrary source or host MATLAB Engine
-  for Python. Building artifacts needs the applicable licensed compiler and
-  every product used by the source.
-- **GNU Octave 11.3.0 is free software under GPLv3+.** Octave packages are not
-  MATLAB toolboxes. Similar names do not imply API, numerical, graphics, or
-  licensing equivalence.
-- Ask which runtime, release, platform, installed products, and license context
-  the user actually has. Treat availability as `unknown` until confirmed.
-
-See [Octave compatibility](references/octave-compatibility.md) and
-[execution/product boundaries](references/executing-scripts.md).
-
-## Nonnegotiable safety boundary
-
-Never run an untrusted `.m`, `.mlx`, MEX binary, MAT file, project startup or
-shutdown action, package installer, or generated artifact. Static review does
-not prove safety.
-
-Treat these as execution or code-loading surfaces:
-
-- `eval`, `evalin`, `assignin`, text-derived `feval`, `str2func`, callbacks,
-  timers, app callbacks, and dynamically modified paths;
-- `system`, `unix`, `dos`, shell escape `!`, Java, .NET, Python (`py.*`,
-  `pyrun`, `pyrunfile`), MEX, and native libraries;
-- `mex`, `codegen`, MATLAB Compiler, build tasks, package/project startup, and
-  generated code;
-- `load`, object deserialization (`loadobj`, custom serialization), function
-  handles, Java/System objects, and class code reachable from MAT files.
-
-`.mlx` is an opaque archive for this toolkit and MEX is native executable code.
-Do not use Python pickle for exchange. Inspect first, isolate when appropriate,
-obtain explicit approval, then invoke a user-confirmed executable and license.
-Bundled scripts are static or dry-run tools: none launches MATLAB, Octave,
-Python Engine, a compiler, or a subprocess.
-
-## Default workflow
-
-1. **Clarify target.** Record MATLAB release or Octave version, OS/architecture,
-   base product versus required toolboxes/packages, expected inputs/outputs,
-   numerical tolerances, and whether execution is authorized.
-2. **Inventory statically.** Scan `.m` files, opaque artifacts, project paths,
-   required products, and MAT headers before any runtime loads them.
-3. **Choose code form.** Prefer functions with an `arguments` block for
-   automation. Use scripts only for controlled orchestration and live scripts
-   for reviewed interactive narratives.
-4. **Make semantics explicit.** Record shapes, classes, units, missing-value
-   rules, indexing, implicit expansion, RNG algorithm/seed, tolerances, and
-   output formats.
-5. **Test without hidden state.** Keep fixtures synthetic, paths project-local,
-   graphics deterministic, and tests independent of base-workspace residue.
-6. **Plan execution.** Generate an argv plan, review startup/path effects and
-   licenses, and launch only after explicit approval outside these helpers.
-7. **Capture provenance.** Hash named inputs/code and record release, products,
-   RNG policy, tolerances, and command plan without dumping the environment.
-
-## Language and data checklist
-
-### Scripts, functions, and live scripts
-
-- Scripts share the caller/base workspace and leave variables behind.
-  Functions have local workspaces and explicit inputs/outputs.
-- Live scripts (`.mlx`) mix code and rich output but are not plain-text
-  review artifacts. Export reviewed code to `.m` for static inspection.
-- Avoid `clear all`, broad `addpath(genpath(...))`, dependence on `pwd`, global
-  variables, and silent name shadowing. Use project roots and `fullfile`.
-- Validate sizes, classes, and values in `arguments` blocks. Remember that
-  type declarations can convert inputs; validators check without converting.
-- A main function file should match the main function name. Local functions
-  are private to the file; since R2024a they can appear anywhere in a script
-  outside conditional contexts.
-
-```matlab
-function y = scaleSignal(x, options)
-arguments
-    x (:,1) double {mustBeFinite}
-    options.Scale (1,1) double {mustBeFinite, mustBeNonzero} = 1
-end
-y = x .* options.Scale;
-end
-```
-
-Read [programming](references/programming.md).
-
-### Arrays, indexing, and numerics
-
-- MATLAB uses 1-based, column-major indexing. `A(i,j)`, `A(k)`, `A(:,j)`,
-  `A{...}`, and `A.(name)` have different semantics.
-- `*`, `/`, `\`, and `^` are matrix operations; dotted forms are
-  element-wise. Use `A\b`, not `inv(A)*b`.
-- Since R2016b, compatible dimensions expand implicitly. Assert intended shape
-  before operations that could accidentally form an outer result.
-- Preallocate when output size is known, but do not vectorize at the cost of
-  huge temporaries or unreadable code. Measure with `timeit` or the profiler.
-- Compare floating-point results with domain-chosen absolute and relative
-  tolerances, not blanket `==` or a magic multiple of `eps`.
-- Pin both random algorithm and seed. Use named `RandStream` substreams for
-  independent parallel work; do not use time-based `rng("shuffle")` for a
-  reproducibility claim.
-
-Read [arrays](references/matrices-arrays.md) and
-[mathematics](references/mathematics.md).
-
-### Tables, timetables, and missing values
-
-- A `table` has named, equal-height variables that may have different types.
-  `T(rows,vars)` returns a table; `T{rows,vars}` extracts contents; `T.Var`
-  selects one variable.
-- A `timetable` additionally has row times. Sort, validate time zones and
-  uniqueness, then use `retime`/`synchronize` intentionally.
-- Missing sentinels are type-specific: `NaN`, `NaT`, `<missing>`,
-  `<undefined>`, and empty character vectors. Integer and logical arrays have
-  no standard missing sentinel.
-- Define import options rather than relying on inference for production data.
-  Preserve units, time zones, variable names, encodings, and missing rules.
-
-Read [data import/export](references/data-import-export.md).
-
-## Graphics and export
-
-Use explicit figure/axes handles and `tiledlayout`; label units; set limits,
-color scales, font sizes, and colormaps deliberately. Prefer `exportgraphics`
-over `saveas` for publication output. In R2026a it exports raster, PDF/EPS/EMF,
-SVG, GIF, and interactive HTML; format capabilities differ. Specify
-`ContentType="vector"` for suitable PDF/SVG-style output and `Resolution` for
-raster output. Review accessibility and embedded-raster behavior.
-
-Read [graphics and export](references/graphics-visualization.md).
-
-## MAT files and exchange
-
-- Version 7 is the normal `save` default; `matfile` creates 7.3 by default.
-  Versions 4/6/7/7.3 differ in types, compression, and per-variable limits.
-- Version 7.3 is HDF5-based, not an arbitrary HDF5 interchange contract.
-  Partial access and chunking can help large arrays.
-- Never load an untrusted MAT file. Inventory headers/datasets first. Objects
-  can invoke class deserialization behavior; opaque/function/native content
-  requires escalation.
-- Prefer CSV/JSON/Parquet/HDF5 with a documented schema for simple exchange.
-  Do not rename pickle payloads as MAT files and do not deserialize pickle.
-
-Read [data import/export](references/data-import-export.md).
-
-## Projects, analysis, and tests
-
-- Use MATLAB Projects for controlled paths, startup/shutdown tasks,
-  dependencies, source control, and reproducible entry points. Review project
-  actions before opening an untrusted project.
-- `matlab.codetools.requiredFilesAndProducts` and Dependency Analyzer are
-  static approximations; dynamic dispatch can cause misses or false positives.
-  A required-product report does not prove a license is available.
-- Use Code Analyzer (`codeIssues`; legacy text workflows can use `checkcode`)
-  and `codeCompatibilityReport` before migration.
-- Base MATLAB includes script-, function-, and class-based
-  `matlab.unittest` workflows. Parallel runs require Parallel Computing
-  Toolbox. Dependency-based selection, richer quality dashboards, generated
-  tests, and advanced coverage/equivalence features can require MATLAB Test or
-  other products.
-- R2026a `runtests` automatically opens and later closes a project when target
-  tests belong to a project that is not already open. Account for startup and
-  shutdown actions before using this behavior.
-
-Read [programming](references/programming.md) and
-[execution/testing](references/executing-scripts.md).
-
-## Python integration, pinned to R2026a
-
-- R2026a supports 64-bit CPython 3.9-3.13 for MATLAB Interface to Python,
-  MATLAB Engine for Python, and MATLAB Compiler SDK for Python.
-- The current R2026a PyPI package reviewed here is
-  `matlabengine==26.1.12` (released 2026-05-08). It requires an installed
-  R2026a; MATLAB Runtime alone is insufficient. R2026a also ships a
-  preinstalled Engine distribution under one named `matlabroot` path.
-- Package installation does not grant MATLAB or toolbox licenses. Configure
-  one named interpreter/executable; do not print the full environment,
-  `PATH`, `PYTHONPATH`, or credentials.
-- `pyenv` controls MATLAB-to-Python interpreter selection. In-process Python
-  generally requires restarting MATLAB to switch; out-of-process Python can
-  be terminated and reconfigured.
-- Starting Engine is an explicit execution action:
-  `matlab.engine.start_matlab()` starts a MATLAB process and can check out a
-  license. Never call it merely to probe availability.
-- Verify conversion semantics for NumPy arrays, pandas DataFrames,
-  tables/timetables, strings/missing values, datetime/duration, dictionaries,
-  shape/order, and unsupported sparse/object/categorical cases.
-
-Read [Python integration](references/python-integration.md).
-
-## Local helper CLIs
-
-Every helper is network-free, bounded, symlink-rejecting, and nonexecuting.
-Run from this skill directory with Python 3.11+. Bash is allowed only to invoke
-these Python CLIs and validation commands; never use it to execute a generated
-MATLAB/Octave argv plan or untrusted artifact.
-
-| Helper | Purpose |
-|---|---|
-| `scripts/plan_batch_command.py` | Produce reviewed MATLAB/Octave argv; never execute |
-| `scripts/scan_m_code.py` | Scan `.m` text and flag opaque `.mlx`/MEX risks |
-| `scripts/validate_project_manifest.py` | Validate paths and declared product/license status |
-| `scripts/inventory_mat_file.py` | Header/metadata inventory; never call `loadmat` |
-| `scripts/plan_python_compatibility.py` | Check R2026a CPython/Engine compatibility |
-| `scripts/reproducibility_report.py` | Hash named local artifacts and emit a bounded report |
-| `scripts/generate_function_scaffold.py` | Dry-run or create function and unit-test scaffolds |
-
-```bash
-python scripts/scan_m_code.py path/to/source --root path/to/project
-python scripts/plan_batch_command.py matlab script path/to/main.m --root path/to/project
-python scripts/validate_project_manifest.py project-manifest.json --root path/to/project
-python scripts/inventory_mat_file.py data.mat --root path/to/project
-python scripts/plan_python_compatibility.py --python-version 3.13
-python scripts/reproducibility_report.py --root path/to/project --file src/analyze.m
-python scripts/generate_function_scaffold.py analyzeSignal --root path/to/project
-```
-
-The scaffold generator defaults to dry-run; writing requires `--write` and
-refuses collisions. SciPy and h5py are optional inventory backends; if
-authorized, add exact reviewed versions to the caller's project lockfile.
-They are not required for `--help` or header-only inventory, and this skill
-does not perform package installation.
-
-## References
-
-- [Programming, workspaces, projects, analysis, tests](references/programming.md)
-- [Matrices, indexing, types, missingness, performance](references/matrices-arrays.md)
-- [Numerical methods, tolerances, RNG, toolbox boundaries](references/mathematics.md)
-- [Graphics and `exportgraphics`](references/graphics-visualization.md)
-- [Import/export, tables/timetables, MAT semantics and safety](references/data-import-export.md)
-- [MATLAB/Octave command-line execution and migration](references/executing-scripts.md)
-- [MATLAB and Python interoperability](references/python-integration.md)
-- [GNU Octave 11.3.0 compatibility differences](references/octave-compatibility.md)
-
-Bundled JSON assets are the [project manifest](assets/project_manifest_template.json),
-[reproducibility manifest](assets/reproducibility_manifest_template.json), and
-[R2026a Python table](assets/python_compatibility_r2026a.json). There is no
-`templates/` directory and no Markdown file is loaded from `assets/`;
-local-link tests enforce this package contract.
-
-## Primary sources (verified 2026-07-23)
-
-- [MATLAB R2026a documentation](https://www.mathworks.com/help/matlab/)
-- [MATLAB R2026a release notes](https://www.mathworks.com/help/matlab/release-notes.html)
-- [R2026a system requirements](https://www.mathworks.com/support/requirements/matlab-system-requirements.html)
-- [Python compatibility by release](https://www.mathworks.com/support/requirements/python-compatibility.html)
-- [MATLAB Engine installation](https://www.mathworks.com/help/matlab/matlab_external/install-the-matlab-engine-for-python.html)
-- [GNU Octave 11.3.0 release](https://octave.org/)
-- [GNU Octave current manual](https://docs.octave.org/latest/)

package/skills/matplotlib/SKILL.md

@@ -1,378 +0,0 @@
----
-name: matplotlib
-description: Low-level plotting library for full customization. Use when you need fine-grained control over every plot element, creating novel plot types, or integrating with specific scientific workflows. Export to PNG/PDF/SVG for publication. For quick statistical plots use seaborn; for interactive plots use plotly; for publication-ready multi-panel figures with journal styling, use scientific-visualization.
-allowed-tools: Read Write Bash
-license: https://github.com/matplotlib/matplotlib/tree/main/LICENSE
-compatibility: Requires Python 3.10+ and Matplotlib 3.10.x. Use `uv add matplotlib` in projects; interactive Jupyter widgets require `ipympl`.
-metadata:
-  version: "1.1"
-  skill-author: K-Dense Inc.
----
-
-# Matplotlib
-
-## Overview
-
-Matplotlib is Python's foundational visualization library for creating static, animated, and interactive plots. This skill provides guidance on using matplotlib effectively, covering both the pyplot interface (MATLAB-style) and the object-oriented API (Figure/Axes), along with best practices for creating publication-quality visualizations.
-
-## When to Use This Skill
-
-This skill should be used when:
-- Creating any type of plot or chart (line, scatter, bar, histogram, heatmap, contour, etc.)
-- Generating scientific or statistical visualizations
-- Customizing plot appearance (colors, styles, labels, legends)
-- Creating multi-panel figures with subplots
-- Exporting visualizations to various formats (PNG, PDF, SVG, etc.)
-- Building interactive plots or animations
-- Working with 3D visualizations
-- Integrating plots into Jupyter notebooks or GUI applications
-
-## Setup
-
-For project work, install Matplotlib with uv:
-
-```bash
-uv add matplotlib
-```
-
-For notebook interactivity:
-
-```bash
-uv add matplotlib ipympl
-```
-
-Then enable the widget backend in Jupyter with `%matplotlib widget` or `%matplotlib ipympl`.
-
-Matplotlib 3.10 requires Python 3.10+ and NumPy 1.23+. Non-interactive file output works through backends such as Agg, PDF, and SVG. For GUI windows, Matplotlib auto-selects an available backend; if `TkAgg` fails in a uv-managed Python, update uv and Python builds with `uv self update` and `uv python upgrade --reinstall`, or install a Qt backend with `uv add pyside6`.
-
-## Core Concepts
-
-### The Matplotlib Hierarchy
-
-Matplotlib uses a hierarchical structure of objects:
-
-1. **Figure** - The top-level container for all plot elements
-2. **Axes** - The actual plotting area where data is displayed (one Figure can contain multiple Axes)
-3. **Artist** - Everything visible on the figure (lines, text, ticks, etc.)
-4. **Axis** - The number line objects (x-axis, y-axis) that handle ticks and labels
-
-### Two Interfaces
-
-**1. pyplot Interface (Implicit, MATLAB-style)**
-```python
-import matplotlib.pyplot as plt
-
-plt.plot([1, 2, 3, 4])
-plt.ylabel('some numbers')
-plt.show()
-```
-- Convenient for quick, simple plots
-- Maintains state automatically
-- Good for interactive work and simple scripts
-
-**2. Object-Oriented Interface (Explicit)**
-```python
-import matplotlib.pyplot as plt
-
-fig, ax = plt.subplots()
-ax.plot([1, 2, 3, 4])
-ax.set_ylabel('some numbers')
-plt.show()
-```
-- **Recommended for most use cases**
-- More explicit control over figure and axes
-- Better for complex figures with multiple subplots
-- Easier to maintain and debug
-
-## Common Workflows
-
-### 1. Basic Plot Creation
-
-**Single plot workflow:**
-```python
-import matplotlib.pyplot as plt
-import numpy as np
-
-# Create figure and axes (OO interface - RECOMMENDED)
-fig, ax = plt.subplots(figsize=(10, 6))
-
-# Generate and plot data
-x = np.linspace(0, 2*np.pi, 100)
-ax.plot(x, np.sin(x), label='sin(x)')
-ax.plot(x, np.cos(x), label='cos(x)')
-
-# Customize
-ax.set_xlabel('x')
-ax.set_ylabel('y')
-ax.set_title('Trigonometric Functions')
-ax.legend()
-ax.grid(True, alpha=0.3)
-
-# Save and/or display
-fig.savefig('plot.png', dpi=300, bbox_inches='tight')
-plt.show()
-```
-
-### 2. Multiple Subplots
-
-**Creating subplot layouts:**
-```python
-# Method 1: Regular grid
-fig, axes = plt.subplots(2, 2, figsize=(12, 10))
-axes[0, 0].plot(x, y1)
-axes[0, 1].scatter(x, y2)
-axes[1, 0].bar(categories, values)
-axes[1, 1].hist(data, bins=30)
-
-# Method 2: Mosaic layout (more flexible)
-fig, axes = plt.subplot_mosaic([['left', 'right_top'],
-                                 ['left', 'right_bottom']],
-                                figsize=(10, 8))
-axes['left'].plot(x, y)
-axes['right_top'].scatter(x, y)
-axes['right_bottom'].hist(data)
-
-# Method 3: GridSpec (maximum control)
-from matplotlib.gridspec import GridSpec
-fig = plt.figure(figsize=(12, 8))
-gs = GridSpec(3, 3, figure=fig)
-ax1 = fig.add_subplot(gs[0, :])  # Top row, all columns
-ax2 = fig.add_subplot(gs[1:, 0])  # Bottom two rows, first column
-ax3 = fig.add_subplot(gs[1:, 1:])  # Bottom two rows, last two columns
-```
-
-### 3. Plot Types and Use Cases
-
-**Line plots** - Time series, continuous data, trends
-```python
-ax.plot(x, y, linewidth=2, linestyle='--', marker='o', color='blue')
-```
-
-**Scatter plots** - Relationships between variables, correlations
-```python
-ax.scatter(x, y, s=sizes, c=colors, alpha=0.6, cmap='viridis')
-```
-
-**Bar charts** - Categorical comparisons
-```python
-ax.bar(categories, values, color='steelblue', edgecolor='black')
-# For horizontal bars:
-ax.barh(categories, values)
-```
-
-**Histograms** - Distributions
-```python
-ax.hist(data, bins=30, edgecolor='black', alpha=0.7)
-```
-
-**Heatmaps** - Matrix data, correlations
-```python
-im = ax.imshow(matrix, cmap='coolwarm', aspect='auto')
-plt.colorbar(im, ax=ax)
-```
-
-**Contour plots** - 3D data on 2D plane
-```python
-contour = ax.contour(X, Y, Z, levels=10)
-ax.clabel(contour, inline=True, fontsize=8)
-```
-
-**Box plots** - Statistical distributions
-```python
-ax.boxplot([data1, data2, data3], tick_labels=['A', 'B', 'C'])
-```
-
-**Violin plots** - Distribution densities
-```python
-ax.violinplot([data1, data2, data3], positions=[1, 2, 3])
-```
-
-For comprehensive plot type examples and variations, refer to `references/plot_types.md`.
-
-### 4. Styling and Customization
-
-**Color specification methods:**
-- Named colors: `'red'`, `'blue'`, `'steelblue'`
-- Hex codes: `'#FF5733'`
-- RGB tuples: `(0.1, 0.2, 0.3)`
-- Colormaps: `cmap='viridis'`, `cmap='plasma'`, `cmap='coolwarm'`
-
-**Using style sheets:**
-```python
-plt.style.use('seaborn-v0_8-darkgrid')  # Apply predefined style
-# Available styles: 'ggplot', 'bmh', 'fivethirtyeight', etc.
-print(plt.style.available)  # List all available styles
-```
-
-**Customizing with rcParams:**
-```python
-plt.rcParams['font.size'] = 12
-plt.rcParams['axes.labelsize'] = 14
-plt.rcParams['axes.titlesize'] = 16
-plt.rcParams['xtick.labelsize'] = 10
-plt.rcParams['ytick.labelsize'] = 10
-plt.rcParams['legend.fontsize'] = 12
-plt.rcParams['figure.titlesize'] = 18
-```
-
-**Text and annotations:**
-```python
-ax.text(x, y, 'annotation', fontsize=12, ha='center')
-ax.annotate('important point', xy=(x, y), xytext=(x+1, y+1),
-            arrowprops=dict(arrowstyle='->', color='red'))
-```
-
-For detailed styling options and colormap guidelines, see `references/styling_guide.md`.
-
-### 5. Saving Figures
-
-**Export to various formats:**
-```python
-# High-resolution PNG for presentations/papers
-fig.savefig('figure.png', dpi=300, bbox_inches='tight', facecolor='white')
-
-# Vector format for publications (scalable)
-fig.savefig('figure.pdf', bbox_inches='tight')
-fig.savefig('figure.svg', bbox_inches='tight')
-
-# Transparent background
-fig.savefig('figure.png', dpi=300, bbox_inches='tight', transparent=True)
-```
-
-**Important parameters:**
-- `dpi`: Resolution (300 for publications, 150 for web, 72 for screen)
-- `bbox_inches='tight'`: Removes excess whitespace
-- `facecolor='white'`: Ensures white background (useful for transparent themes)
-- `transparent=True`: Transparent background
-
-### 6. Working with 3D Plots
-
-```python
-fig = plt.figure(figsize=(10, 8))
-ax = fig.add_subplot(111, projection='3d')
-
-# Surface plot
-ax.plot_surface(X, Y, Z, cmap='viridis')
-
-# 3D scatter
-ax.scatter(x, y, z, c=colors, marker='o')
-
-# 3D line plot
-ax.plot(x, y, z, linewidth=2)
-
-# Labels
-ax.set_xlabel('X Label')
-ax.set_ylabel('Y Label')
-ax.set_zlabel('Z Label')
-```
-
-## Best Practices
-
-### 1. Interface Selection
-- **Use the object-oriented interface** (fig, ax = plt.subplots()) for production code
-- Reserve pyplot interface for quick interactive exploration only
-- Always create figures explicitly rather than relying on implicit state
-
-### 2. Figure Size and DPI
-- Set figsize at creation: `fig, ax = plt.subplots(figsize=(10, 6))`
-- Use appropriate DPI for output medium:
-  - Screen/notebook: 72-100 dpi
-  - Web: 150 dpi
-  - Print/publications: 300 dpi
-
-### 3. Layout Management
-- Use `constrained_layout=True` or `tight_layout()` to prevent overlapping elements
-- `fig, ax = plt.subplots(constrained_layout=True)` is recommended for automatic spacing
-
-### 4. Colormap Selection
-- **Sequential** (viridis, plasma, inferno): Ordered data with consistent progression
-- **Diverging** (coolwarm, RdBu): Data with meaningful center point (e.g., zero)
-- **Qualitative** (tab10, Set3): Categorical/nominal data
-- Avoid rainbow colormaps (jet) - they are not perceptually uniform
-
-### 5. Accessibility
-- Use colorblind-friendly colormaps (viridis, cividis)
-- Add patterns/hatching for bar charts in addition to colors
-- Ensure sufficient contrast between elements
-- Include descriptive labels and legends
-
-### 6. Performance
-- For large datasets, use `rasterized=True` in plot calls to reduce file size
-- Use appropriate data reduction before plotting (e.g., downsample dense time series)
-- For animations, use blitting for better performance
-
-### 7. Code Organization
-```python
-# Good practice: Clear structure
-def create_analysis_plot(data, title):
-    """Create standardized analysis plot."""
-    fig, ax = plt.subplots(figsize=(10, 6), constrained_layout=True)
-
-    # Plot data
-    ax.plot(data['x'], data['y'], linewidth=2)
-
-    # Customize
-    ax.set_xlabel('X Axis Label', fontsize=12)
-    ax.set_ylabel('Y Axis Label', fontsize=12)
-    ax.set_title(title, fontsize=14, fontweight='bold')
-    ax.grid(True, alpha=0.3)
-
-    return fig, ax
-
-# Use the function
-fig, ax = create_analysis_plot(my_data, 'My Analysis')
-fig.savefig('analysis.png', dpi=300, bbox_inches='tight')
-```
-
-## Quick Reference Scripts
-
-This skill includes helper scripts in the `scripts/` directory:
-
-### `plot_template.py`
-Template script demonstrating various plot types with best practices. Use this as a starting point for creating new visualizations.
-
-**Usage:**
-```bash
-uv run python scripts/plot_template.py
-```
-
-### `style_configurator.py`
-Interactive utility to configure matplotlib style preferences and generate custom style sheets.
-
-**Usage:**
-```bash
-uv run python scripts/style_configurator.py
-```
-
-## Detailed References
-
-For comprehensive information, consult the reference documents:
-
-- **`references/plot_types.md`** - Complete catalog of plot types with code examples and use cases
-- **`references/styling_guide.md`** - Detailed styling options, colormaps, and customization
-- **`references/api_reference.md`** - Core classes and methods reference
-- **`references/common_issues.md`** - Troubleshooting guide for common problems
-
-## Integration with Other Tools
-
-Matplotlib integrates well with:
-- **NumPy/Pandas** - Direct plotting from arrays and DataFrames
-- **Seaborn** - High-level statistical visualizations built on matplotlib
-- **Jupyter** - Interactive plotting with `%matplotlib inline` or `%matplotlib widget`
-- **GUI frameworks** - Embedding in Tkinter, Qt, wxPython applications
-
-## Common Gotchas
-
-1. **Overlapping elements**: Use `constrained_layout=True` or `tight_layout()`
-2. **State confusion**: Use OO interface to avoid pyplot state machine issues
-3. **Memory issues with many figures**: Close figures explicitly with `plt.close(fig)`
-4. **Font warnings**: Install fonts or suppress warnings with `plt.rcParams['font.sans-serif']`
-5. **DPI confusion**: Remember that figsize is in inches, not pixels: `pixels = dpi * inches`
-
-## Additional Resources
-
-- Official documentation: https://matplotlib.org/
-- Gallery: https://matplotlib.org/stable/gallery/index.html
-- Cheatsheets: https://matplotlib.org/cheatsheets/
-- Tutorials: https://matplotlib.org/stable/tutorials/index.html
-