feat(aidd-ui): give the UI contract a brand section and agnostic accessibility and adaptation baselines

オープン
#1,120 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
55/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
markdown, typescript

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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-ui through the contract, or project memory through aidd-context. aidd-ui treats 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-accessibility states the standard and level it measures, and a finding cites it.
  • 05-adapt states 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 --strict and node scripts/check-markdown-links.js pass.
Prior art in this repo
  • PR #708 (draft): 01-system/assets/system-contract.md has no brand section; 04-accessibility/references/fragments.md and 05-adapt/references/fragments.md define 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.
主要言語
TypeScript
スター
481
フォーク
45
平均マージ
1日 13時間
マージ済み PR(30日)
91

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

ai-driven-dev/framework のほかの issue

ai-driven-dev/framework の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。