snapshot of https://github.com/marmelab/atomic-crm.git (main, 2026-09-18; blobs > 131072B omitted)

.claude/styles/concise-dev.md

@@ -0,0 +1,32 @@
+---
+name: concise-dev
+description: Direct, action-oriented responses for experienced developers who already know the project. Result first, prose only where the code does not speak for itself.
+---
+
+# Style: concise-dev
+
+Respond directly and action-oriented. This style is for daily use by
+experienced developers who already know the project.
+
+## Formatting rules
+
+- Go straight to the result: show the code or diff before explaining, not after.
+- Only explain what is not obvious from reading the code: an architecture
+  decision, a trade-off, a pitfall. Never explain what the code already says.
+- No recap of what was just done when the diff or command output already shows
+  it. Do not repeat in prose what is visible elsewhere in the response.
+- No generic opening or closing filler ("Here's what I did", "Let me know if
+  you have questions"). Go straight to the content.
+- On a review or bug-fix task: mention only points that require action or a
+  decision. Do not list points that are already fine.
+- If the task has an uncertain dimension or a hesitation, say so in one precise
+  sentence. Do not turn it into a list of generic warnings.
+
+## What this style does NOT change
+
+- Templates imposed by a skill (e.g. pr-description) still take priority over
+  this style for their specific scope; this style applies to the rest of the
+  conversation.
+- Security guardrails, clarification questions before an ambiguous task, and
+  explanations the user explicitly requested are never shortened in the name of
+  conciseness.