automation

Applies Sun Lab API documentation conventions when creating or modifying Sphinx documentation files. Covers conf.py configuration, RST file structure, Doxygen/Breathe integration for C++ projects, tox build environments, and Makefile wrappers. Use when creating documentation for a new project, modifying existing docs/ files, adding new modules to API documentation, or when the user asks about documentation conventions.

Drafts Sun Lab style-compliant git commit messages by analyzing all local changes relative to the active branch. Use when the user asks to commit, when completing a coding task that should be committed, or when the user invokes /commit. Proactively offer to draft a commit message after completing substantial code changes.

Applies Sun Lab C++ coding conventions when writing, reviewing, or refactoring code. Covers .h, .hpp, and .cpp files, Doxygen documentation, naming, formatting, error handling, include directives, file ordering, template patterns, embedded (Arduino/PlatformIO) conventions, and Python C++ extension (nanobind/scikit-build-core) conventions. Use when writing new C++ code, modifying existing code, reviewing pull requests, or when the user asks about C++ coding standards.

Applies Sun Lab C# coding conventions when writing, reviewing, or refactoring code. Covers .cs files, XML documentation, naming, formatting, error handling, using directives, file ordering, and Unity-specific patterns. Use when writing new C# code, modifying existing code, reviewing pull requests, or when the user asks about C# coding standards.

Performs in-depth codebase exploration at the start of a coding session. Builds comprehensive understanding of project structure, architecture, key components, and patterns. Use when starting a new session, when asked to understand or explore the codebase, when asked "what does this project do", when exploring unfamiliar code, or when the user asks about project structure or architecture.

Explores installed ataraxis and Sun Lab dependency source code to build a live API snapshot. Discovers public classes, functions, and constants exported by each dependency, identifies replacement opportunities where project code reimplements existing library functionality, and produces a structured dependency API snapshot. Use when starting a session on a project with ataraxis dependencies, before writing code that uses ataraxis library features, or when the user asks about available library APIs.

Applies Sun Lab project directory structure conventions when creating new projects, adding directories, or verifying project layout. Covers the five project archetypes (Python-only, Python+C++ extension, C++ PlatformIO library, C++ PlatformIO firmware, C# Unity), common root files, environment directories, test directories, and documentation directory placement. Use when creating a new project, adding top-level directories, restructuring a project, or when the user asks about project directory conventions.

Applies Sun Lab pyproject.toml conventions when creating or modifying pyproject.toml files. Covers section ordering, metadata fields, dependency specifications, tool configurations (ruff, mypy, coverage, hatch), and classifier templates. Use when creating a new project, modifying an existing pyproject.toml, adding dependencies, or when the user asks about pyproject.toml conventions.

Applies Sun Lab Python coding conventions when writing, reviewing, or refactoring code. Covers .py files, docstrings, type annotations, naming, formatting, error handling, imports, file ordering, and ataraxis library preferences. Use when writing new Python code, modifying existing code, reviewing pull requests, or when the user asks about Python coding standards.

Applies Sun Lab README conventions when creating or updating README.md files. Covers section ordering, writing style, standard section templates, badges, MCP server documentation, CLI documentation, and codebase cross-referencing. Use when writing a new README, updating an existing README, or when the user asks about README conventions.

Generates, updates, and verifies Claude Code skill files and CLAUDE.md project instructions. Covers SKILL.md structure, YAML frontmatter, formatting conventions, inter-skill relationships, scope declarations, and verification checklists. Use when creating new skills, modifying existing skills, updating CLAUDE.md files, or when the user asks about skill conventions.

Applies Sun Lab tox.ini conventions when creating or modifying tox configuration files. Covers the mamba + uv + tox toolchain architecture, envlist patterns, environment definitions, dependency installation strategies, environment naming, and project archetype variations (full Python, reduced Python, C++ extension, C++ docs-only). Use when creating a new tox.ini, modifying an existing tox.ini, adding or changing tox environments, or when the user asks about tox configuration, development automation, or the mamba/uv/tox toolchain.