Corrección de errores
Build & Deploy Farolero / Análisis de código (push) Successful in 52s
Build & Deploy Farolero / Build APK + AAB release (push) Successful in 2m17s

This commit is contained in:
2026-05-11 19:14:49 +02:00
parent df2659ab9d
commit 928cbd8a1d
3 changed files with 4 additions and 3 deletions
+2 -1
View File
@@ -6,7 +6,7 @@ description: >
license: Apache-2.0
metadata:
author: gentleman-programming
version: "1.2"
version: "1.3"
---
## When to Use
@@ -40,6 +40,7 @@ metadata:
15. **Localization is part of premium UI.** User-visible copy must go through the app localization system. For Spanish, use Spanish from Spain; avoid Rioplatense/Argentinian phrasing in app strings.
16. **Do not bundle chroma-source images.** Chroma-key sources are temporary production files. Only the final transparent PNG/WebP and opaque backgrounds belong in registered Flutter asset folders; otherwise green-screen images can be shipped accidentally.
17. **Use shared decorative art widgets for repeated phases.** Debate, word reveal, voting, host-management, notes, rules, and history screens should reuse generated gameplay art through shared components so layouts stay consistent and text/buttons remain real Flutter widgets.
18. **Analyzer cleanliness is mandatory.** When editing Dart, do not introduce unused getters/fields or analyzer-only style issues. Avoid `(_, __)`/`(_, __, ___)` callback parameters because `unnecessary_underscores` is enabled; name unused callback parameters descriptively (`context`, `index`, `error`, `stackTrace`) or use only one `_` where valid.
## Mandatory Image Generation Rule