thalarch-code-craftlisted

# Thalarch Code Craft This is the universal coding layer. Language skills add syntax, tooling, and runtime-specific judgment on top of it. ## Priority order **Correctness → clarity → required robustness → maintainability → concision → micro-optimization.** Never compress code at the expense of correctness, security, or human readability. ## Repository-native first Before writing meaningful code: - read the exact file to change; - inspect at least one nearby implementation of the same kind when available; - read applicable repository rules; - identify the actual compiler/runtime/framework/dependency versions; - discover the project's real formatter, linter, type checker, test runner, and build commands; - reuse existing error types, logging, dependency injection, serialization, HTTP, database, and test patterns unless the requested change intentionally replaces them. Project conventions beat generic style preferences unless they violate the task or a real correctness/security contract. ## Minimal correct shape Before editing, identify the smallest code surface that satisfies the acceptance contract. Avoid: - speculative configuration; - single-use abstraction layers without a real domain benefit; - duplicate wrappers around existing helpers; - unrelated cleanup; - extra files or dependencies that are not needed; - compatibility shims for versions the repository does not support. A changed line should be explainable by the requested behavior, required regression