code style

SKILL.md

NEVER use if/else, switch/case, or ternary operators. These imperative constructs must be replaced with pattern matching in ALL cases:

When you encounter imperative control flow in existing code, refactor it immediately. This is not optional - imperative conditionals are code smells that must be eliminated.

Define ALL data structures as Effect Schemas. This is the foundation of type-safe Effect code.

This skill should be used when the user asks about "Effect best practices", "Effect code style", "idiomatic Effect", "Schema-first", "Match-first", "when to use Schema", "when to use Match", "branded types", "dual APIs", "Effect guidelines", "do notation", "Effect.gen", "pipe vs method chaining", "Effect naming conventions", "Effect project structure", "data modeling in Effect", or needs to understand idiomatic Effect-TS patterns and conventions. Source: andrueandersoncs/claude-skill-effect-ts.

View raw