Copilot instructions for ambroise-leclerc/WebFront: Read and follow the repository-wide guidance in ../AGENTS.md. It is the canonical source for project architecture, commands, conventions, test requirements, and workspace safety.
AGENTS.md instructions for ambroise-leclerc/WebFront, covering webfront contributor and agent guide, project goal and current maturity, repository map, build and test commands and fast, portable c++ baseline (no cef download).
Use when adding or modifying a baked asset (font, shader, image, .medui screen, ML model) or anything under generated/ — the recipe-to-baker-to-committed-artifact doctrine, the canonical JSON rules that make byte-identity possible, and why generated/ is never hand-edited.
Use when configuring, compiling, testing, or running examples for MduX, or when diagnosing a local build failure (CMake configure errors, module compilation errors, missing Vulkan SDK, toolchain version failures).
Use when changing MduX C++23 module interfaces or implementations, Vulkan or Vulkan SC integration code, rendering resources, example programs, or public API surface.
Use whenever a change can affect safety behavior, risk controls, compliance metadata, traceability, auditability, lifecycle documents, or claims about medical-device standards (IEC 62304, IEC 62366, ISO 14971, ISO 13485) in MduX.
Use when authoring or reviewing a .medui screen, or discussing MduX's planned UI-description language — the grammar, component dictionary, theme tokens, text budgets, and when @safetycritical / requirement: are mandatory.
Use when writing or reviewing any document under docs/ /, softwaredevelopmentfile/, or an ADR that claims alignment with IEC 62304, ISO 13485, ISO 14971, IEC 62366-1, or IEC 81001-5-1 — the citation-key format, the Justification object, and the prohibition on reproducing normative standard text.
Use when filling in or reviewing a document under softwaredevelopmentfile/ (SAD, SDD, SOUP, Risk Management File, Usability Engineering File, Cybersecurity SAD) — the summarize-don't-duplicate rule and how to cite into the regulatory corpus.
Use this agent when you want to improve code quality using clang-tidy static analysis. Examples: Context: User has written a new C++ function and wants to ensure it follows best practices. user: 'I just wrote this function for parsing configuration files. Can you help me improve it with clang-tidy?' assistant: 'I'll…
AGENTS.md instructions for ambroise-leclerc/MduX, covering agents.md, 1. project purpose and maturity, 2. instruction scope and sources of truth, the trustsc parity programme and 3. verified architecture summary.