feat(aidd-ui): give the UI contract a brand section and agnostic accessibility and adaptation baselines
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 55/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- markdown, typescript
- Ambito
- design, documentation
Direzione di ricerca
Start with plugins/aidd-ui/skills/01-system/assets/system-contract.md, 04-accessibility/references/fragments.md, and 05-adapt/references/fragments.md; read 01-system/references/authority.md for existing ownership guidance. Define the brand ownership decision and technology-agnostic accessibility and adaptation baselines, then update the template and skills so their outputs reflect those requirements. Done means all acceptance criteria pass, including the strict plugin validation and Markdown link check.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Problem
The UI system contract template in PR #708 (plugins/aidd-ui/skills/01-system/assets/system-contract.md) covers foundations (color, type, spacing, shape, depth, motion), surfaces, adaptation, accessibility, assets and deprecations. It has no place for brand identity: logo usage, voice and tone, and the rules that tell a model what the product must sound and look like beyond its tokens. A model generating a screen from the contract can follow every token and still ship an off-brand result.
The two provider skills have the same gap. 04-accessibility and 05-adapt define the shape of their outputs (references/fragments.md: provider, target, scope, evidence, acceptance), but state no baseline to evaluate against. The skill never says which accessibility standard it measures, nor which adaptation conventions it assumes (mobile-first, relative units, breakpoint rules, touch input without hover). Each project would have to reinvent them, and two projects will not get the same verdict on the same screen.
This was raised during a community lab on the plugin: brand is missing from the design contract, and the accessibility and adaptation skills should carry technology-agnostic good practice.
Scope
- Add a brand section to the UI system contract template: logo usage, voice and tone, and where the canonical brand sources live. Optional, removed when empty like the other sections.
- Decide and document who owns brand:
aidd-uithrough the contract, or project memory throughaidd-context.aidd-uitreats memory as read-only, so the default is the contract; state the reason if memory wins. - In
04-accessibility, name the reference standard the skill evaluates against (a recognised one, for example WCAG 2.2 level AA) and the minimum requirement families it checks. - In
05-adapt, state the technology-agnostic baseline: mobile-first, relative units over fixed pixels, breakpoint and layout-primitive conventions, input modality (no hover on touch), content pressure. - Keep both skills free of technology-specific rules (no framework, CSS or toolkit names).
Acceptance criteria
- The contract template has a brand section, and the skill that fills it is named.
- The ownership decision for brand (contract vs project memory) is written in the plugin, with its reason.
-
04-accessibilitystates the standard and level it measures, and a finding cites it. -
05-adaptstates its baseline conventions, and a requirement that follows the baseline reports no system impact. - Neither skill mentions a specific framework, library or design tool.
-
claude plugin validate plugins/aidd-ui --strictandnode scripts/check-markdown-links.jspass.
Prior art in this repo
- PR #708 (draft):
01-system/assets/system-contract.mdhas no brand section;04-accessibility/references/fragments.mdand05-adapt/references/fragments.mddefine output fields only. 01-system/references/authority.md(PR #708): evidence priority between contract, code, memory and external documents.- #192 and #218 to #222 (closed): original plugin scoping and placeholders, no brand or baseline decision.
Out of scope
- Generating logos or other binary brand assets: the plugin contracts asset roles and does not produce binaries (PR #708, "Known limitations").
- Visual identity work for the AI-Driven Dev trainers: a separate task, not a framework change.
- UX methodology (interviews, flows, heuristics): a later increment.
- Lingua principale
- TypeScript
- Stelle
- 481
- Fork
- 45
- Merge medio
- 1g 13h
- PR unite (30g)
- 91
Preparare l'ambiente
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di ai-driven-dev/framework
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 86/100
ai-driven-dev/framework#1311 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 79/100
ai-driven-dev/framework#1244 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
ai-driven-dev/framework#1197 ·
I maintainer di solito rispondono entro 1 giorno
-
refactor(aidd-context): apply the new skill template to learnForse già presa @blafourcade l’ha presa 3 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
ai-driven-dev/framework#1186 · 1 assegnatario ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 83/100
ai-driven-dev/framework#1163 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di ai-driven-dev/framework
Issue simili
-
bug impact:low Team: SecuritySolution Team:Defend Workflows v9.6.0
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
elastic/kibana#306401 · 3 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
agentes-chat/agentes-chat#927 ·
I maintainer di solito rispondono entro 1 giorno
-
[Bug]: Webapp workspace fails to render in Safari — "Can't find variable: requestIdleCallback"Apertacomp/desktop P2 type/bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
NousResearch/hermes-agent#157702 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
I maintainer di solito rispondono entro 1 giorno
-
e2e-failure ready-to-code
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 72/100
redhat-developer/rhdh-plugin-export-overlays#4794 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno