Skip to content

Define Studio UI/UX rules using existing fonts and theme, and ignore Evidence - #208

Merged
SpectralDragon merged 2 commits into
mainfrom
codex/studio-design-rules-publish
Nov 5, 2026
Merged

SpectralDragon merged 2 commits into
mainfrom
codex/studio-design-rules-publish

Conversation

@SpectralDragon

@SpectralDragon SpectralDragon commented Nov 5, 2026 •

Copy link
Copy Markdown
Contributor

Studio contributors now have explicit rules for building and verifying editor interfaces within Studio's existing theme and font assets. Local Evidence artifacts are excluded from the repository.

Changes

  • Add Studio visual rules and contributor skill routing to AGENTS.md, Editor/AGENTS.md, and the knowledge index.
  • Retain two focused skills: adaengine-studio-design for proposals/review and ui-ux-pro-max for UI construction and rendered verification.
  • Cover layout, control semantics, interaction states, form validation, focus, keyboard/touch access, accessibility, async feedback, text wrapping/scaling, and verification evidence.
  • Use only existing Studio fonts/text roles and semantic theme tokens. The final PR contains no font binaries, font-pairing or visual-style catalogs, palette generators, branding/banner/slide skills, framework installers, or creative API helpers.
  • Preserve the adapted UI/UX source revision and MIT license in the provenance documents.
  • Ignore /Evidence/ and remove its 208 tracked files. Original local Evidence files are preserved.

Validation

  • Both maintained skills pass the skill format validator.
  • All 70 local links in the changed maintained documents resolve; no font binaries or stale references to removed skills/CLIs remain.
  • The normal pre-commit checks pass.
  • In a clean checkout of the final tree, the full PR content, whitespace, and secret checks pass.
  • The publication check remains blocked because the existing runner requests an owning Python suite for deleted Evidence Python files, while the final tree contains no changed Python implementation. No validation configuration or suppressions were added.
  • Independent review found no content/scope defects. A settings-inspector scenario verified the retained guidance covers dropdowns, immediate toggles, async field validation, Studio fonts, desktop/iOS states, and rendered QA. This instruction change does not claim an application runtime/UI test pass.

The PR remains a draft while the publication-runner limitation is unresolved. Contribution pre-push hooks were bypassed for the requested PR publication; existing Git LFS hooks were retained.

The work was prepared in an isolated worktree. Unrelated local edits and the original Git index were preserved.

@SpectralDragon SpectralDragon changed the title Document Studio design rules, vendor design skills, and ignore Evidence Define Studio UI/UX rules using existing fonts and theme, and ignore Evidence Nov 5, 2026
@SpectralDragon
SpectralDragon marked this pull request as ready for review November 5, 2026 09:21
@SpectralDragon
SpectralDragon merged commit 035d520 into main Nov 5, 2026
6 of 12 checks passed
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 5, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-05T09:23:23.673394Z d409347 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant