Janet Style Guide This skill guides the generation of idiomatic Janet code covering functional patterns, performance tradeoffs, common gotchas, and Janet-specific idioms. Core Principles Functional Style by Default - Always prefer functional style unless there is a clear performance penalty or tradeoff - Use imperative/mutable approaches only when performance demands it (large collections, hot paths, string building) - When mutation is used for performance, document why and keep scope limited Prefer Over Sequential Use to group related bindings instead of sequential statements: Reserve for to…