Add foundational documentation templates to support product design and architecture planning, including ADR, archetypes, LLM systems, dev setup, and shared modules.
This commit is contained in:
@@ -11,6 +11,8 @@
|
||||
- `/docs/backend/payment-flow.md`
|
||||
---
|
||||
|
||||
> This guide reflects a **pipeline / human‑review** archetype. For chat‑first or generation tools, keep the same principles (clarity, accessibility, safe actions) but replace the concrete flows and terminology per `/docs/archetypes.md`.
|
||||
|
||||
## 1. Tone & Clarity
|
||||
- Professional and concise. Emphasize trust (audit log, reasoning traces, secure billing and webhooks).
|
||||
- Avoid jargon without tooltips; show why a decision was made (rule hit, similarity, LLM reasoning).
|
||||
|
||||
Reference in New Issue
Block a user