2.1K skills · sorted by relevance
Recover readable text from PDFs when read_file or Python extraction fails. Use pdftotext, a command-line text extractor, with options to preserve layout, specify character encoding, or save extracted content to a file.
Choose charts and diagrams that fit the data and the question readers need to answer. Plan layouts and interactions for large screens and mobile devices, or critique existing visuals for misleading comparisons, unclear labels, and hidden information.
Create, edit, and analyze PowerPoint presentations, including slide content, layouts, comments, and speaker notes. Reuse existing templates or build slides from HTML, then inspect thumbnail previews to identify layout and readability issues.
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.
Inspect a running website at different screen sizes to find layout problems, inconsistent styling, and accessibility issues such as poor contrast. Fix the relevant source code, recheck the results, and report changes with before-and-after screenshots.
Generate a new image with different content while preserving a reference image’s style and layout. The skill describes the reference, rewrites that description, and can review generated layouts and retry within a set attempt limit.
Adjust .NET MAUI layouts to avoid system bars, screen cutouts, and keyboards, or extend content to screen edges. It covers .NET 10 safe area APIs, migration from older settings, and CSS coordination for Blazor Hybrid.
Use when the user mentions SwiftUI layout review, adaptive layout issues, GeometryReader problems, or multi-device layout checking.
The English summary is being prepared. Showing the original description.
Compose pages and sites that read as their vertical: ecommerce-catalog storefronts that look like storefronts, hospitality-food sites that look like restaurants, b2b-manufacturer sites that look industrial. Use this skill whenever the user wants to build a site that looks like the vertical it serves, fix a build that reads as generic or off-vertical, build to an experience bar produced by competitor-experience-audit, or compose pages with the merchandising, density, and layout conventions a credible site in the category is expected to carry. Triggers on vertical conventions, storefront layout, ecommerce layout, retail conventions, merchandising layout, category page composition, site composition, build to the experience bar, make it look like the vertical, off-vertical, looks generic, build conventions for a vertical, site grammar. Also triggers when a build that is technically clean reads wrong for its category, and the cause is composition, not visual taste.
The English summary is being prepared. Showing the original description.
Designs layout systems and responsive interfaces including grid systems, flexbox patterns, sidebar layouts, and responsive breakpoints. Use when structuring app layouts, building responsive designs, or creating complex page structures.
The English summary is being prepared. Showing the original description.
Build responsive layouts with CSS Grid, Flexbox, and container queries. Use when creating responsive designs, fixing layout issues, or building mobile-first layouts.
The English summary is being prepared. Showing the original description.
Restore legibility to an auto-generated graph diagram that has outgrown its canvas - rendering at single-digit percent scale with sub-pixel labels. Covers the levers that measurably reduce layout units (source-level label wrapping, invisible chain links so unconnected nodes stop spreading into one row, per-cluster splitting, layout direction picked by rendering both and measuring) and the rejected ones (raising the render font is a no-op because layout engines measure in text units; a topology heuristic for direction regressed 13 of 38 diagrams). Use when a generated Mermaid/Graphviz/DOT diagram is too small to read; not for hand-authoring a small diagram.
The English summary is being prepared. Showing the original description.
Fix scattered/torn regions in hex-grid simulated annealing layouts that use "competitive flood-fill" (one tile per region per outer iteration). Use when: (1) regions of >20 tiles end up dispersed instead of forming compact blobs, (2) maxDist/sqrt(N) dispersion ratio is 10×+ worse than the ideal compact blob, (3) tiles assigned to one region show up in multiple disconnected fragments across the layout, (4) the visualization has a "trypophobia ring" pattern at the perimeter where some regions spill into a perimeter spiral, (5) an overflow spiral fallback exists in the layout code and frequently kicks in for large regions, (6) bigger regions look worse than smaller ones (small regions stay compact, big ones shred). Root cause: interleaved competitive flood-fill (round-robin one tile at a time across all regions) lets large regions get boxed in by neighbors before they finish growing — the unfilled remainder is dumped into the overflow spiral at the perimeter, far from the seed. Fix: replace with sequential region-by-region BFS — process regions in size-descending order, fully claim each region's N contiguous tiles before moving to the next.
The English summary is being prepared. Showing the original description.
Configure Dynamic Forms (field and section visibility on Lightning record pages) and Dynamic Actions (button and action visibility rules) in Lightning App Builder — enabling Dynamic Forms, converting page layout fields with the Upgrade Now wizard, writing field visibility rules (field value, profile, permission, record type, device), and controlling action bar visibility. NOT for page layout design or record type assignment — use admin/record-types-and-page-layouts. NOT for a full layout-to-Dynamic-Forms migration across record types or profiles — use admin/dynamic-forms-migration. Keywords: flexipage, fieldInstance, fieldItem, uiBehavior, visibilityRule, booleanFilter, UiFormulaCriterion, actionOverrides, profileActionOverrides, page activation, org default page, App Builder Upgrade Now.
The English summary is being prepared. Showing the original description.
Layout changes: production-level FLIP layout, additive composition, measurement. Use when implementing, reviewing or testing layout changes for React, Vite, Next.js or Perfect_AI projects.
The English summary is being prepared. Showing the original description.
Responsive GNOME layouts: AdwBreakpoint conditions, BreakpointBin, MultiLayoutView, BottomSheet, narrow/wide layout swaps. Use when making an app work on phones or narrow windows.
The English summary is being prepared. Showing the original description.
Agents workbench layout — covers the fixed layout structure, grid configuration, part visibility, editor modal, titlebar, sidebar footer, and implementation requirements. Use when implementing features or fixing issues in the Agents workbench layout.
The English summary is being prepared. Showing the original description.
Generates complete page layouts and shells for common patterns (dashboard, authentication, settings, CRUD pages) with consistent navigation, layout components, routing structure, and state management placeholders. Use when building "new page", "dashboard layout", "auth pages", or "admin panel structure".
The English summary is being prepared. Showing the original description.
Design new interfaces or reshape existing ones with colors, typography, and layouts grounded in the subject and audience. It guides planning, implementation, and critique, including interface wording, purposeful motion, mobile layouts, and accessibility.
Design new interfaces or reshape existing ones with colors, typography, and layouts grounded in the subject and audience. It guides planning, implementation, and critique, including interface wording, purposeful motion, mobile layouts, and accessibility.
Build accessible interfaces with shadcn/ui components and Tailwind CSS styling. Create forms, tables, and layouts that adapt to screen size, then coordinate colors, spacing, and dark mode across the application.
Search local design guidance to plan, build, review, or improve web, mobile, and desktop interfaces. Find suitable colors, font pairings, layouts, charts, and interaction patterns, with implementation advice matched to the project's technology.
Draft simple black-and-white screen layouts as standalone SVG files, with numbered explanations of each area. For multiple screens, create a flow overview and an optional static viewer page for browsing and zooming during review.
Create a hand-drawn HTML wireframe for exploring screen layouts before detailed design. Graph paper, sticky notes, sketch tabs, and rough chart placeholders present an early concept with annotations for discussion and review.