optional-usage

Estrellas6

Forks0

Actualizado13 de julio de 2026 a las 13:20

Denigma std::optional usage conventions. Use when adding, reviewing, or modifying std::optional fields or return values, especially for enum or bool state.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

rpatters1

rpatters1/denigma

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

name	optional-usage
description	Denigma std::optional usage conventions. Use when adding, reviewing, or modifying std::optional fields or return values, especially for enum or bool state.

Optional Usage

Prefer explicit domain states over std::optional when the missing state is part of the model.

Rules:

When Denigma controls an enum type, avoid std::optional<Enum> when possible.
Add a first enum value such as Unspecified, Float, NotApplicable, or the best domain-specific unengaged value.
Use that first enum value to represent the otherwise not-engaged state.
If Denigma does not control the enum, std::optional<Enum> may be appropriate when the enum has no value that corresponds to not engaged.
Apply the same rule to std::optional<bool>.
Prefer a new or existing three-state enum over std::optional<bool> when the state is really yes / no / unengaged.
Keep the unengaged enum value first so default construction is meaningful.

Más de este repositorio

mismo repositorio

classifier-design

rpatters1/denigma

Denigma classifier design conventions. Use when creating, editing, reviewing, or refactoring classifiers in src/classify or shared classification helpers used by exporters.

2026-07-146

nested-namespaces

rpatters1/denigma

Denigma C++ namespace style. Use when adding, editing, reviewing, or refactoring C++ namespace declarations in this repository.

2026-07-146

windows-minmax

rpatters1/denigma

Denigma Windows compatibility convention for standard min/max calls. Use when adding, reviewing, or modifying any C++ code that calls std::min, std::max, std::clamp, numeric_limits<T>::min/max, or related standard-library min/max functions or members.

2026-07-146

denigma-test-harness

rpatters1/denigma

Denigma repository test harness conventions. Use when building Denigma, running Denigma tests, interpreting Denigma test failures, or choosing the correct working directory for the test executable.

2026-07-136

enum-mappings

rpatters1/denigma

Denigma exporter enum mapping conventions. Use when adding, moving, reviewing, or modifying enum conversions for exporters such as MusicXML, MNX, MSS, SVG, or other format-specific code.

2026-07-136

name	optional-usage
description	Denigma std::optional usage conventions. Use when adding, reviewing, or modifying std::optional fields or return values, especially for enum or bool state.

Optional Usage

Prefer explicit domain states over std::optional when the missing state is part of the model.

Rules:

When Denigma controls an enum type, avoid std::optional<Enum> when possible.
Add a first enum value such as Unspecified, Float, NotApplicable, or the best domain-specific unengaged value.
Use that first enum value to represent the otherwise not-engaged state.
If Denigma does not control the enum, std::optional<Enum> may be appropriate when the enum has no value that corresponds to not engaged.
Apply the same rule to std::optional<bool>.
Prefer a new or existing three-state enum over std::optional<bool> when the state is really yes / no / unengaged.
Keep the unengaged enum value first so default construction is meaningful.