Writing Style

• NEVER use em dashes (—) in any content, code, copy, meta descriptions, or structured data. Use periods, commas, or pipes instead.
• All copy and language must sound as if written by a senior technical founder. Direct, confident, no fluff. No marketing speak.

Git

• Only consider staged changes when generating commit messages.