chore: add scoped AI guardrails for docs maintenance

Keeps documentation guidance concise, publishable, and aligned with helper/app behavior.

Author: phaupt

.claude/CLAUDE.md

@@ -0,0 +1,9 @@
+# mobileid-docs - Claude Notes
+
+- Keep diffs small and publishable.
+- Prefer accuracy over fluency; do not invent behavior or guarantees.
+- Keep terminology, frontmatter, and navigation conventions consistent.
+- Avoid marketing phrasing and unnecessary URL query parameters.
+- Use realistic but safe example data (no secrets/tokens/PII).
+- If behavior is unclear, document uncertainty explicitly.
+- Verify flow/UI wording against `mobileid-helper` and `mybank-demo-app`.

.cursor/rules/00-core.mdc

@@ -0,0 +1,13 @@
+---
+description: Core guardrails for mobileid-docs documentation changes
+globs:
+  - "**/*"
+alwaysApply: true
+---
+
+- Keep edits narrow; avoid broad rewrites unless requested.
+- Prefer factual accuracy over stylistic polish.
+- Do not invent parameters, guarantees, or flow behavior.
+- Keep terminology consistent with existing pages/navigation.
+- Use safe placeholder data only; never include real secrets or PII.
+- If implementation evidence is unclear, state assumptions explicitly.

.cursor/rules/10-docs-guardrails.mdc

@@ -0,0 +1,14 @@
+---
+description: Docs guardrails for publishable, implementation-aligned content
+globs:
+  - "docs/**"
+  - "README.md"
+alwaysApply: true
+---
+
+- Keep text aligned with `mobileid-helper` and `mybank-demo-app`.
+- Distinguish normative Mobile-ID behavior from demo/helper behavior.
+- Avoid marketing phrasing; use concrete behavior and constraints.
+- Preserve existing structure, frontmatter, and navigation conventions.
+- Keep links clean; avoid unnecessary query parameters in references/sources.
+- Keep snippets realistic, safe, and copy-paste plausible.