Files
Clément SAILLANT d7ffbf14cf feat: Add workflows and templates for design reviews, release processes, and compliance checks
- Introduced new documentation for design reviews (DR0/DR1) and release rituals.
- Created templates for Architecture Decision Records (ADR), Design Reviews, Playtest Reports, and Validation Plans.
- Established workflows for consulting, creative processes, systems engineering, R&D spikes, and compliance/QA.
- Implemented GitHub Actions workflows for firmware and hardware CI with required checks strategy.
- Added setup script for repository configuration, including label creation and branch protection.
- Developed installation script for Kill_LIFE with system updates and environment setup.
2026-02-19 01:35:10 +01:00

43 lines
1.2 KiB
Markdown
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Workflow — Design produit / UX
## But
Définir l’expérience utilisateur, les états UI, les contraintes physiques (écran/boutons), et produire un handoff exploitable.
## Phases
### 1) Brief & contraintes
- Personas, contexte d’usage, objectifs UX
- Contraintes hardware (écran, boutons, feedback)
- Livrable : spec UX (règles + mapping inputs)
- Label : `ai:spec`
### 2) Exploration
- 3–5 directions (pas plus)
- Critères : lisibilité, erreurs, temps d’apprentissage, robustesse
- Livrable : “direction choisie” + rationale
- Label : `ai:plan` (docs)
### 3) Prototypage
- Wireframes → prototype (low → mid → hi)
- États : nominal, loading, erreur, offline
- Livrable : matrice états + mapping boutons/gestes
- Label : `ai:docs` (ou `ai:impl` si tu ajoutes un prototype UI)
### 4) Design system & handoff
- Composants + états
- Guidelines + naming assets
- Handoff vers firmware/hardware
- Label : `ai:docs`
## Gates
- Mapping inputs complet (boutons/écran)
- États d’erreur spécifiés
- Handoff : assets + conventions
## Evidence pack
- Captures/export (ou liens internes)
- Checklist de validation UX
## Tips
- Si l’UI doit toucher le firmware : sépare UI logique (testable `native`) et rendu HW (drivers).