Add repository-wide DevDocs quality rules and local reference ignore.

Introduce always-on systematic documentation quality gates with hook-specific safeguards, and ignore local .reference mirrors to keep repository history clean.

Co-authored-by: Cursor <cursoragent@cursor.com>

Author: MAX-IT-Tech

.cursor/rules/devdocs-hook-reference-quality.mdc

@@ -0,0 +1,34 @@
+---
+description: Hook reference metadata and call example quality rules
+globs: modules/concepts/hooks/list-of-hooks/*.md
+alwaysApply: false
+---
+
+# Hook Reference Quality
+
+Use this when editing generated or manually corrected hook reference pages.
+
+## Metadata Rules
+
+- `files[].url` must point to an existing source file in the correct repository.
+- Core links use `PrestaShop/PrestaShop` target branch.
+- Theme links use `classic-theme` or `hummingbird`, not `PrestaShop/PrestaShop/themes/...`.
+- Module links use native module repositories, not `PrestaShop/PrestaShop/modules/...`.
+- Do not use `files: {}` when a reviewer or source code identifies a real origin.
+- Delete pages for hooks that no longer dispatch in the target branch.
+
+## Call Example Rules
+
+- The call block must show the actual hook invocation, not adjacent code.
+- Include the full current parameter array, including `id_shop`, `chain`, by-reference values, and return flags when present.
+- Do not keep truncated fragments like only the hook name or first array keys.
+- Use `twig` fences for `renderhook(...)` and `php` fences for `Hook::exec(...)`.
+- Remove copied constants, comments, copyright headers, `include(...)`, layout markup, and unrelated code.
+- Smarty `{hook ...}` snippets must not end with `;`.
+
+## Systemic Checks
+
+- Search all changed hook pages for the same pattern after fixing one comment.
+- Verify deleted/empty-source candidates with source search, not only `hook.xml`.
+- Treat allow-list constants as references, not proof that a hook is dispatched.
+- Re-run hook validation, source-link checks, and Hugo build before push.

.cursor/rules/devdocs-hugo-markdown.mdc

@@ -0,0 +1,36 @@
+---
+description: Hugo Markdown formatting guardrails for DevDocs pages
+globs: "**/*.md"
+alwaysApply: false
+---
+
+# PrestaShop DevDocs - Hugo Markdown
+
+Use this companion rule for markdown formatting only. Repository-wide quality gates are defined in `devdocs-systematic-quality-gates.mdc` (always on).
+
+This repository is Hugo content using [Goldmark](https://github.com/yuin/goldmark). Follow existing file patterns and avoid generic markdown reformatting.
+
+## Front matter
+
+- Keep YAML front matter between `---` markers.
+- Do not add or remove fields unless explicitly requested.
+- Do not rewrite YAML indentation/order for style only.
+
+## Hugo shortcodes
+
+- Keep shortcode syntax unchanged: `{{< ... >}}`, `{{% ... %}}`, `relref`/`ref`.
+- Do not rename shortcodes or alter bracket style without task requirements.
+- Keep internal links in repository style; use plain markdown for external URLs.
+
+## Do Not Auto-Refactor
+
+- Do not insert extra spaces in links.
+- Do not remove intentional trailing spaces used for markdown line breaks.
+- Do not switch list markers (`*` vs `-`) for style only.
+- Do not add/remove blank lines without semantic reason.
+- Do not change fenced code block language tags or delimiters unless requested.
+
+## Repository References
+
+- [Writing Markdown](contribute/documentation/how/writing-markdown.md)
+- [Shortcodes index](contribute/documentation/shortcodes/_index.md)

.cursor/rules/devdocs-systematic-quality-gates.mdc

@@ -0,0 +1,43 @@
+---
+description: Repository-wide quality gates for PrestaShop DevDocs changes
+alwaysApply: true
+---
+
+# PrestaShop DevDocs: Systematic Quality
+
+Apply this to every docs area: hooks, Admin API, modules, themes, webservice, basics, contribution guides, and all version branches.
+
+## Work Systemically
+
+- Treat review comments and maintainer follow-up commits as examples of a class of issue.
+- Audit the full changed scope for similar issues before editing.
+- For version migrations, verify behavior against the target branch, not previous docs.
+- Prefer deleting obsolete pages over preserving stale documentation.
+
+## Source of Truth
+
+- Core behavior: target `PrestaShop/PrestaShop` branch.
+- Theme behavior: `classic-theme` and `hummingbird`.
+- Module behavior: official native module repositories.
+- Existing docs are not authoritative when source code disagrees.
+
+## Content Accuracy
+
+- Examples must be current, minimal, and copied from real source behavior.
+- Do not include unrelated surrounding code, constants, comments, or half-copied arrays.
+- Code fence language must match the snippet syntax.
+- Parameter arrays must be complete for the current call, including references and flags.
+- Never leave placeholders, partial links, or known-broken URLs.
+
+## Verification Before Push
+
+- Run area-specific validators and a CI-equivalent Hugo build.
+- Check changed links and examples against source.
+- Do not push until validation passes.
+
+## Continuous Improvement
+
+When a new failure pattern is discovered:
+- Add it to the relevant rule.
+- Add or improve a deterministic local check when possible.
+- Re-run the full-scope audit to prove no similar cases remain.

.gitignore

@@ -1,2 +1,3 @@
 .idea/
 .claude/
+.reference/