design(board): make the add-task composer clearly read as create - #208
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
1 participant
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.
Design-polish pass — a consistency follow-up to #207 (the new-project composer), addressing the same LLM-panel gap on the board's inline "Add task" composer.
When a column's "Add task" button expands, it became a bare "Task title" input with no create-cue and no submit button — arguably worse than the project composer: it read like a search field, and the only way to submit was pressing Enter (undiscoverable).
Fix (CSS + small markup, tokens only)
Mirrored the #207 treatment so the two composers are consistent:
Before → after
Both create composers (project + task) now read unmistakably as create rather than search. Full quality gate green; presentational-only. Verified against the sandbox (
AWS_PROFILE=personal).