pg-responsive-ui
/pg-responsive-ui
Use when designing, implementing, or reviewing responsive client layouts, text truncation, title wrapping, icon-only controls, mobile hover, tooltips and keyboard behavior, and focus during width changes.
- Author
- JusticeSc ↗
- Repository
- project-governance ↗
- Licence
- MIT
- Last repository change
- 09.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 09.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when designing, implementing, or reviewing responsive client layouts, text truncation, title wrapping, icon-only controls, mobile hover, tooltips and keyboard behavior, and focus during width changes.
Original author description
Use when designing, implementing, or reviewing responsive client layouts, text truncation, title wrapping, icon-only controls, mobile hover, tooltips and keyboard behavior, and focus during width changes.
How it works
- 1. Minimum viewport
- 2. Decision order
- 3. Text truncation
- 4. Titles
- 5. Icon-only controls
- 6. Mobile hover behavior
- 7. Mobile tooltips
- 8. Mobile keyboard
SKILL.md preview
--- name: pg-responsive-ui description: Use when designing, implementing, or reviewing responsive client layouts, text truncation, title wrapping, icon-only controls, mobile hover, tooltips and keyboard behavior, and focus during width changes. --- # Responsive client UI ## 1. Minimum viewport Use a viewport width of 390 CSS px as the primary acceptance minimum. There must be no unintended overlap, clipping, page-wide horizontal scrolling, or inaccessible primary actions. Below 390px, layout requirements may be relaxed. ## 2. Decision order 1. First adjust space allocation or wrap elements onto another line; then consider text truncation, icon-only controls, or moving icons into the More menu. 2. Primary actions and primary states must not be omitted. 3. Do not hide conflicts through global clipping, reducing all font sizes, or shrinking click targets. 4. Reduce font sizes only when specifically required by product design. ## 3. Text truncation 1. Truncated content must be fully available on a secondary page or by opening a menu. 2. Truncation must not lose errors or other key information. 3. Prefer single-line truncation for tab navigation, visible selectors, buttons, tags, and similar components. 4. Important information that is not available on another page must be displayed in full without truncation. ## 4. Titles 1. Prefer displaying page titles in full. Move the action area onto another line when necessary. 2. Prefer natural wrapping for card titles. If the number of lines is limited, the full title must remain available to view. ## 5. Icon-only controls 1. Reducing a control to an icon requires both: - The icon clearly conveys its meaning, or the operation is familiar to users. - A tooltip appears on hover; add one if needed. 2. Judge familiarity from the actual product and its users; navigation to a separate page is not automatically a familiar icon action. ## 6. Mobile hover behavior 1. Enable mouse-hover effects only on devices that support hovering. Use `@media (hover: hover)`, not viewport width, to determine this. 2. Tapping on a phone must not leave behind backgrounds, highlights, or action-button visibility intended only for hover. 3. Preserve normal selected, enabled, and pressed states, as well as focus indicators for keyboard interaction. 4. Try to preserve focus when the width changes, unless the focused element disappears from the page as a result. ## 7. Mobile tooltips 1. Do not show tooltips that only provide auxiliary information such as action names or keyboard shortcuts on mobile. For example, omit the “Copy” tooltip on a copy button; tapping still performs the original action directly. 2. Tooltips that provide supplementary explanations must support tap-to-show on mobile. ## 8. Mobile keyboard On mobile, do not raise the input keyboard automatically unless it is explicitly intended.
Versions
The database has no other skills named pg-responsive-ui.
Database snapshot: 13.11.2026 · package version 4f51cd2d4d9f (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100dsh-responsive-ui
Use when designing, implementing, or reviewing responsive client layouts, text truncation, title wrapping, icon-only controls, mobile hover, tooltips and keyboard behavior, and focus during width changes in DeepSeek Harness. - 100dsh-responsive-ui
Use when designing, implementing, or reviewing responsive client layouts, mobile and touch detection, text truncation, title wrapping, icon-only controls, mobile hover, tooltips and keyboard behavior, and focus during width changes in DeepSeek Harness. - 100responsive-design-advisor
Design responsive layouts with breakpoints, mobile-first approach, and flexible grids. Use when creating responsive designs, implementing breakpoints, or optimizing for multiple screen sizes. - 90saas-responsive
This skill should be used when the user is building or reviewing responsive layouts, mobile design, breakpoints, table-to-card patterns, touch targets, collapsible sidebars, or mobile/bottom navigation for a SaaS application. Covers the \"sacrifice principle\" for mobile SaaS,… - 90responsive-accessibility
Design responsive layouts that maintain accessibility across screen sizes, zoom levels, and orientations. Use when designing responsive interfaces, testing zoom behaviour, or reviewing layouts across devices. Triggers on: responsive, zoom, reflow, breakpoint, mobile… - 95responsive-design
Implement modern responsive layouts using container queries, fluid typography, CSS Grid, and mobile-first breakpoint strategies. Use when building adaptive interfaces, implementing fluid layouts, or creating component-level responsive behavior.