Uses x64dbg to dynamically debug Windows malware: setting strategic breakpoints on APIs, stepping through unpacking and decryption, dumping memory at the right moment, and manipulating execution to reach hidden code. Activates for requests to debug malware with x64dbg, set API breakpoints, or step through unpacking in a debugger.
The English summary is being prepared. Showing the original description.
meltedinhex/analyst-ai-pack☆ 22Updated Jul 7, 2026
Adapts existing designs for phones, tablets, desktops, print, and email. Adjusts layouts, navigation, content priorities, and touch controls to suit each context, with guidance for responsive sizing and verification across devices and input methods.
- Adapting a desktop interface for mobile use
- Adjusting tablet layouts for portrait and landscape
- Expanding a mobile design for desktop screens
fengshao1227/ccg-workflow☆ 5.9KUpdated Oct 19, 2026
Test website responsiveness across viewport widths using browser automation. Resizes a single session through breakpoints, screenshots each width, and detects layout transitions (column changes, nav switches, overflow). Produces comparison reports showing exactly where layouts break. Trigger with 'responsiveness check', 'check responsive', 'breakpoint test', 'viewport test', 'responsive sweep', 'check breakpoints', or 'test at mobile'.
The English summary is being prepared. Showing the original description.
jezweb/claude-skills☆ 1.1KUpdated Oct 9, 2026
Audit or redesign responsive behavior of a layout — breakpoints, reflow, and content priority. Use when asked to "fix responsive behavior", "define breakpoints", or "how should this reflow on mobile".
The English summary is being prepared. Showing the original description.
tonone-ai/tonone☆ 76Updated Oct 15, 2026
Use when designing, implementing, or reviewing responsive frontend layouts, mobile-first breakpoints, container queries, fluid grids, data-dense tables, touch targets, safe areas, orientation changes, viewport overflow, or cross-device UI behavior; Chinese triggers include responsive layouts, mobile-side adaptation, breakpoints, container queries, horizontal and vertical screens, touch targets.
The English summary is being prepared. Showing the original description.
bovinphang/frontend-craft☆ 22Updated Sep 26, 2026
Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility.
The English summary is being prepared. Showing the original description.
youranreus/note☆ 12Updated Aug 6, 2026
Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility.
The English summary is being prepared. Showing the original description.
waynesutton/agent-ready-component☆ 9Updated Aug 28, 2026
Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility.
The English summary is being prepared. Showing the original description.
convex/components-submissions-directory☆ 9Updated Oct 16, 2026
Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility.
The English summary is being prepared. Showing the original description.
waynesutton/teleprompter☆ 5Updated Jun 28, 2026
Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility.
The English summary is being prepared. Showing the original description.
waynesutton/finder9☆ 3Updated May 24, 2026
Layout structure for web interfaces, from grouping and alignment to reading order, progressive disclosure, and adaptive breakpoints. Use when structuring a page or component, spacing or aligning controls, deciding what collapses at small sizes, handling RTL layout direction, or reviewing frontend code for layout. Triggers on layout, spacing, alignment, grouping, negative space, whitespace, visual hierarchy, reading order, progressive disclosure, breakpoints, responsive layout, container queries, safe area, full-bleed, edge-to-edge, layout margins, RTL layout, logical properties.
The English summary is being prepared. Showing the original description.
waynesutton/waynesutton-ai☆ 2Updated Sep 8, 2026
Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility.
The English summary is being prepared. Showing the original description.
waynesutton/waynesutton-ai☆ 2Updated Sep 8, 2026
Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility.
The English summary is being prepared. Showing the original description.
MMEHDI0606/ai-agent-foundation-template☆ 2Updated May 21, 2026
Implements responsive design systems with mobile-first breakpoints, container queries, fluid typography, and adaptive layouts using Tailwind CSS. Use when users request "responsive design", "mobile-first", "breakpoints", "fluid typography", or "adaptive layout".
The English summary is being prepared. Showing the original description.
sathishssj3/Stereix-Engine☆ 2Updated Oct 4, 2026
Investigate Node.js bugs by pausing execution, examining variables, and stepping through code. Diagnose stalled asynchronous work and unreliable tests, or collect memory snapshots and CPU profiles to investigate growing memory use and slow execution.
- Investigate stalled asynchronous work
- Debug tests that fail inconsistently
- Examine startup timing and child processes
openclaw/openclaw☆ 392.9KUpdated Oct 19, 2026
Test deployed web pages through browser automation. Check forms, login flows, loading and responsiveness metrics, visual changes at three screen widths, and accessibility issues, then receive a report with fixes and a release verdict.
- Testing a feature deployed to staging or preview
- Checking forms and login flows before release
- Comparing layouts at three screen widths
affaan-m/ECC☆ 284.3KUpdated Oct 20, 2026
Review images displayed at different screen sizes and help browsers select appropriately sized files. Check srcset image options, sizes display-width hints, and CSS layout together to identify oversized mobile downloads or mismatched image variants.
- Reviewing responsive images in articles
- Reducing oversized image downloads on phones
- Checking image sizes in cards and galleries
thedaviddias/Front-End-Checklist☆ 74.5KUpdated Oct 6, 2026
Review stylesheets for a CSS reset or normalization layer that reduces differences in browser defaults. Check import order, framework provisions, and rendered layouts across screen sizes and interaction states, then suggest changes for a consistent styling foundation.
- Investigating layout differences between browsers
- Choosing a reset for a new site's styles
- Checking reset coverage in a CSS framework
thedaviddias/Front-End-Checklist☆ 74.5KUpdated Oct 6, 2026
Review fixed pixel values in fonts, widths, and spacing, then suggest relative units that adapt to available space and browser font preferences. Check rendered layouts at different screen widths and during interactions before proposing changes.
- Adapting text to browser font size preferences
- Replacing fixed widths with flexible layouts
- Reviewing spacing units within components
thedaviddias/Front-End-Checklist☆ 74.5KUpdated Oct 6, 2026
Audit CSS class names for inconsistency and ambiguity, then organize them using BEM, a convention that names components, their elements, and variations. Check the rendered interface across screen sizes and interaction states when reviewing changes.
- Auditing inconsistent CSS class names
- Renaming component classes using BEM
- Separating utility classes and JavaScript hooks
thedaviddias/Front-End-Checklist☆ 74.5KUpdated Oct 6, 2026
Review CSS spacing, borders, and positioning for conversion to logical properties, which follow writing direction. Check rendered layouts across screen sizes and interaction states to support right-to-left languages and vertical text.
- Adapting layouts for Arabic or Hebrew
- Replacing fixed left and right spacing in CSS
- Reviewing layouts for vertical writing
thedaviddias/Front-End-Checklist☆ 74.5KUpdated Oct 6, 2026
Review and implement dark mode using CSS variables and the user's operating system preference. Check fixed colors, contrast, responsive layouts, and interaction states, with guidance for adding a manual theme switch that remembers the user's choice.
- Match site colors to the operating system's dark mode
- Find fixed colors that break the dark theme
- Add a manual theme switch that remembers the user's choice
thedaviddias/Front-End-Checklist☆ 74.5KUpdated Oct 6, 2026
Review CSS focus indicators, the visible outlines that show which element receives keyboard input. Identify missing, clipped, or misplaced indicators, check contrast and responsive states, and guide changes that make keyboard navigation easier to follow.
- Check keyboard focus visibility
- Review CSS that removes outlines
- Fix clipped or misplaced focus rings
thedaviddias/Front-End-Checklist☆ 74.5KUpdated Oct 6, 2026
Review and fix Flexbox layouts with overflowing text, uneven item widths, or inconsistent spacing. Check rendered results across screen sizes and interaction states, then adjust sizing rules, spacing, and text overflow settings.
- Fixing overflowing text in a horizontal layout
- Making items share available width equally
- Replacing margins between items with gap
thedaviddias/Front-End-Checklist☆ 74.5KUpdated Oct 6, 2026