Menu
Use when picking up or completing work in league-of-web — how to claim a GitHub issue, branch, PR, and update the kanban labels.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when building any new UI component for league-of-web — scaffolds folder, component, showcase entry, and registry line following the component contract.
Use when adding component tasks to the league-of-web kanban — how to write a GitHub issue complete enough that an agent with zero conversation context can build the component from it alone.
Use when styling any league-of-web component — the Hextech design language reference (palette usage, typography, borders, states).
| name | task-workflow |
| description | Use when picking up or completing work in league-of-web — how to claim a GitHub issue, branch, PR, and update the kanban labels. |
gh issue list --label "status:ready" --label "type:component"
Pick by priority (priority:1 first). Read the full issue:
gh issue view <N>
gh issue edit <N> --add-label "status:in-progress" --remove-label "status:ready"
git checkout main && git pull
git checkout -b feat/<component-slug>
Follow the new-component skill. Commit frequently (conventional commits).
git push -u origin feat/<component-slug>
gh pr create --title "feat(<area>): <component name>" --body "Closes #<N>
<what was built, variants included, any deviations from reference>"
gh issue edit <N> --add-label "status:review" --remove-label "status:in-progress"
PR merge closes the issue automatically (via Closes #N).
After the merge, remove the stale kanban label:
gh issue edit <N> --remove-label "status:review"
Vercel builds a preview deploy per PR — link it in the PR if reviewing visuals.
main