Repository navigation
feat: add ux-planner skill for UX and frontend design questions - #309
Merged
Merged
Conversation
Adapted from the SalesPower ux-planner skill. It runs codebase-researcher then ux-advisor and returns no UI work, a design conflict to resolve, or an implementation plan. Update ux-advisor so it can be invoked from the skill with only a question and research findings, and restrict DESIGN_CONFLICTS to directions the request explicitly asks for.
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.
Summary
Adds a
/ux-plannerskill for answering UX and frontend design questions before building, adapted from the SalesPower skill of the same name.The skill runs
codebase-researcheron the relevant frontend area, passes the findings toux-advisor, and returns one of three outcomes:It accepts a question or an issue reference (
/ux-planner #307).Changes
.claude/skills/ux-planner/SKILL.md(new). Adapted to TaskFlow's advisor sections (STYLE_ADDITIONS,TESTING_CRITERIA), conventions and design philosophy. Reviewed against Anthropic's skill authoring guidance:$ARGUMENTSis used in the body.allowed-tools: Bash(gh issue view *)is pre-approved..claude/agents/ux-advisor.md:/ux-plannerwith only a question and research findings.DESIGN_CONFLICTSto directions the request explicitly asks for. Notes, exceptions and resolved choices go in other sections. Before this change, the advisor sometimes filled the section with non-conflicts, which made the skill stop for user input unnecessarily.Testing
No app code changed, so there are no unit tests.
claude plugin validate .claude/skillspasses. Ran the skill in fresh headless sessions (claude -p):/ux-planner #307DESIGN_CONFLICTSfix; the first run stopped on non-conflicts)TaskItems.JournalDate)Not tested:
The #307 run also surfaced #308 (journal updates may clear unsent task fields).
🤖 Generated with Claude Code