ui-guidancelisted

# UI/Frontend Guidance This is a composable overlay, not a standalone workflow. Use alongside the matching principle skill (for example, `coding-guidance-cpp`) when the change touches UI or frontend code. Add `project-core-dev` only when repository-specific completion checks still need to be discovered or reported. Choose the activity before applying the rules below: - for implementation, make only the requested UI changes and validate them - for review, inspect and report prioritized findings with evidence; do not edit files or require findings to be fixed unless the user also asks for remediation Use this as the thin default overlay for ordinary UI work. If the task is redesign-heavy, frontend-polish heavy, or needs a stronger UX review checklist, prefer `ui-design-guidance`. Routing examples: - add a small control that matches nearby components -> use this skill - fix spacing, labels, or responsive behavior within the existing visual language -> use this skill - redesign a page, introduce a new visual direction, or perform a UX-heavy release review -> use `ui-design-guidance` - product-security or permission-sensitive UI flows -> use `security` first when the main risk is trust, identity, or authorization rather than presentation; add `security-identity-access` when the security scope centers on identity, sessions, recovery, or tenant authorization ## When to use The repo includes graphical UI or web frontend code — web views, desktop UI, embedded pan