SnS coding standards favor readable, explicit, maintainable changes that preserve established architecture and comments. The goal is to make code easy to inspect and safe to evolve.

• Keep changes focused on the requested task.
• Preserve comments and intentional layout.
• Use existing state, service, editor, and layout patterns.
• Prefer simple properties, methods, and markup over clever abstractions.
• Keep Razor files readable with injects first, markup next, and code blocks last.

Avoid broad refactors, unrelated cleanup, hidden side effects, new competing state systems, unapproved folder moves, or moving domain behavior across project boundaries without explicit direction.