Creates domain enums in TypeScript and Go with language-specific conventions and registries.
npx skills add https://github.com/gabriellst/codm --skill enum-gabriellst
Please help me install this Agent Skill. Skill: enum Source: https://github.com/gabriellst/codm/tree/main/.claude/skills/enum Command: npx skills add https://github.com/gabriellst/codm --skill enum-gabriellst
.ts / .go) or a --lang flag, so the right idioms apply per backend. - TypeScript enum playbook: Enforces native enum with SCREAMING_SNAKE_CASE key=value pairs, z.enum() in Zod schemas, barrel exports, central openapi.registerEnums() registration, and i18n-based UI labels under enums.<EnumName>.<VALUE>. - Go enum playbook: Enforces typed string constants, one enum per snake_case file, // Values: doc-comments, IsValid() guards for external input, and typed struct fields instead of plain strings. - Machine-checkable registries: Each language ships a registry.yaml with patterns, bad practices (e.g. z.nativeEnum(), as const arrays, lowercase wire values), and detection regexes used by review tooling. - Use Case: When adding a JobStatus state machine to the Go gateway or an OrderStatus to the TypeScript API, invoke this Skill to scaffold the enum, wire it into entities, repositories, controllers, and locale files following project rules. ## Quick Start Ask the agent to create a new domain enum such as PaymentStatus with values PENDING, PAID, and FAILED in the TypeScript or Go backend, and it will apply the matching language playbook and registry rules.High-intent search queries and answers about installing and using this skill.
Create a file in the context's enums folder using a native TypeScript enum with SCREAMING_SNAKE_CASE keys and values, export it from the enums index barrel, and reference it in Zod schemas via z.enum(OrderStatus). Register it centrally through openapi.registerEnums() in shared/index.ts.
Declare a named string type plus a const block of typed constants, one enum per snake_case file. Add a // Values: doc-comment line for tooling, and an IsValid() method when the value arrives from external input like HTTP bodies or database rows.
Always use z.enum() with the TypeScript enum reference, never z.nativeEnum() and never inline string arrays like z.enum(['PENDING']). This generates correct OpenAPI types and ensures the SDK exposes the enum values.
Enum labels resolve through i18n under the canonical enums.<EnumName>.<VALUE> namespace in both pt and en locale files. For Select components, pass the translated label as children of SelectValue, since Base UI does not auto-resolve it from SelectItem.
Avoid it for open-ended string fields with no fixed value set, bitmasks or flags where Go iota is more idiomatic, and values already defined in the contracts package, which should be imported from contracts generated bindings instead of re-declared.
The string literal stored in the database and sent over the wire must be uppercase to satisfy DB constraints, OpenAPI enum schemas, and wire compatibility between the TypeScript and Go peers. Lowercase values break cross-language consistency and are flagged as a bad practice.
vitorlopes-coderIdentify subdomains and suggest bounded contexts using Domain-Driven Design principles.
fireflyframeworkGenerate OpenAPI specifications and Java SDKs for Firefly Framework services.
weiloon1234Add a Rust forge::AppEnum with wire keys, i18n labels, and TypeScript bindings.
liwooGenerate Go enum types and corresponding TypeScript unions from Go source files.