Repository navigation
[autopilot] skills: correct dense-data-tool guidance in ui-design (calm/light, not dark) - #186
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Corrects stale guidance in designing-interfaces: it told agents that financial/quantitative workbenches should be dark and very dense. First-hand design review verdicts on dense data tools say the opposite on theme: information-dense but calm, with light warm surfaces and natural colors, beautiful rather than overwhelming. The rule now keeps the density and numeral/color-semantics advice, drops the dark-theme mandate, and adds a focal-figure/grouping note. Readers stop producing black terminal-style dashboards by default.