feat(aidd-ui): give the UI contract a brand section and agnostic accessibility and adaptation baselines
Mantenedores costumam responder em até 1 dia
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Facilidade para iniciantes
- 55/100
- Tipo de issue
- Funcionalidade
- Clareza
- Claramente especificada
- Status de atividade
- Ativa
- Stack de tecnologia
- markdown, typescript
- Domínio
- design, documentation
Direção de pesquisa
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.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
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.
- Linguagem predominante
- TypeScript
- Estrelas
- 481
- Forks
- 45
- Merge médio
- 1d 13h
- PRs com merge (30d)
- 91
Preparar o ambiente
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de ai-driven-dev/framework
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 86/100
ai-driven-dev/framework#1311 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 79/100
ai-driven-dev/framework#1244 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
ai-driven-dev/framework#1197 ·
Mantenedores costumam responder em até 1 dia
-
refactor(aidd-context): apply the new skill template to learnTalvez já em andamento @blafourcade assumiu há 3 dias. Aberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
ai-driven-dev/framework#1186 · 1 responsável ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 83/100
ai-driven-dev/framework#1163 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
Todas as issues de ai-driven-dev/framework
Issues semelhantes
-
type: bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
Mantenedores costumam responder em até 2 dias
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 67/100
db-ux-design-system/core-web#8856 ·
Mantenedores costumam responder em até 1 dia
-
'!' breaking change is lost when the commit also has an empty BREAKING CHANGE footerTalvez já em andamento @wittdennis assumiu hoje. Abertapriority: p3 type: bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 74/100
googleapis/release-please#2971 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 1/5 1-3 horas Facilidade para iniciantes 87/100
Mantenedores costumam responder em até 1 dia
-
🛠️ dette technique
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 61/100
betagouv/mon-entreprise#4752 · 1 comentário ·
Mantenedores costumam responder em até 5 dias