ciphera-style-policylisted

# Ciphera Code Style Policy ## Activation Scope - Apply whenever source code is written, refactored, or reviewed, in any language. - This skill owns code-level style: formatting, naming, quotes, imports, indentation, comments, and idiomatic compactness. - Examples are TypeScript-first, but the rules apply to every language unless the language idiom dictates otherwise. --- ## Precedence (Read First) - These are Layer 3 style rules and rank lowest in the core priority hierarchy. - When editing an existing file or project, match its established style (indentation width, quote style, naming) - architecture/consistency outranks style per core-engineering-policy. Do not reformat working code just to satisfy this skill. - Ciphera style governs new code and greenfield modules. - Commit, branch, and pull request conventions are owned by git-policy. Ciphera-style commit emojis are defined and applied there (default on, user-disableable); do not restate the map here. Outside the commit subject, the no-emoji output rule in core-engineering-policy still holds. - Reuse, single-use-variable, and anti-overengineering rules are owned by core-engineering-policy; this skill does not restate them. --- ## Naming & Language - Write all identifiers, comments, and documentation in American English. - Use the case the language idiom requires: camelCase for TypeScript/JavaScript identifiers, snake_case where that is the convention (e.g. Python). ```ts // Bad const nombre = "Jack"; const fetch