masonry
Masonry layouts stack items of varying heights in columns without distinct rows, filling gaps like a brick wall. Use this skill when designing or optimizing Pinterest-style galleries, portfolios, and discovery-focused platforms with image-heavy content. It covers when to choose masonry over grid or bento layouts, implementation approaches using CSS columns or JavaScript libraries, accessibility considerations, and SEO challenges with infinite scroll.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/masonry && cp -r /tmp/masonry/skills/components/layout/masonry ~/.claude/skills/masonrySKILL.md
# Components: Masonry Layout Guides masonry layout design for content with varying heights. Masonry stacks items in columns without distinct rows; items fill gaps like a brick wall. Best for image galleries, portfolios, and discovery-focused platforms. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## When to Use Masonry | Use masonry when | Use grid when | |------------------|---------------| | **Varying heights** | Equal-height items | | Image-heavy; varied aspect ratios | Products, templates (consistent) | | Gallery, portfolio, showcase | Card grid | | Discovery, browsing; visual-first | Structured browsing | See **grid** for equal-height grid; **card** for card structure. ## Masonry vs Grid vs Bento vs Carousel | Layout | Structure | Best for | |--------|-----------|----------| | **Grid** | Equal rows and columns; uniform items | Products, templates, features | | **Masonry** | Columns; items stack without rows; gaps filled | Pinterest, Behance; varied content | | **Bento** | Intentional sections; predefined sizes | Homepage, dashboard; Apple-style | | **Carousel** | Slides; one/few visible; swipe/click | Testimonials, logos, featured items; see **carousel** | ## Masonry Structure | Element | Purpose | |---------|---------| | **Columns** | 2–4 columns; fluid or fixed | | **Items** | Varying heights; natural aspect ratio | | **Gap** | Consistent horizontal and vertical spacing | | **Order** | Top-to-bottom fill within columns | ## Implementation - **CSS columns**: `column-count`; simple, no JS; but items flow top-to-bottom then next column - **Masonry.js / libraries**: True masonry (left-to-right fill); may need JS - **CSS Grid + `grid-auto-flow: dense`**: Approximate; no JS; see **grid** for dense grid **Note**: Pure masonry can create accessibility challenges (screen reader order); ensure logical DOM order. ## SEO Considerations **Masonry + infinite scroll = content not crawlable.** Masonry galleries often use infinite scroll or lazy load; crawlers cannot emulate scroll or "Load more" clicks, so content beyond the initial view is not discoverable. | If you use | Then | |------------|------| | **Infinite scroll** | Provide paginated component pages with full URLs; implement pushState; see **site-crawlability** for search-friendly infinite scroll | | **Lazy load** | Ensure content exists in HTML or is reachable via crawlable links | | **Pagination** | Prefer for SEO-critical content; crawlers can follow next/prev links | **Reference**: [Google – Infinite scroll search-friendly recommendations](https://developers.google.com/search/blog/2014/02/infinite-scroll-search-friendly) ## Best Practices | Principle | Practice | |-----------|----------| | **Visual-first** | Thumbnails; minimal text | | **Aspect ratio** | Preserve original; avoid forced cropping | | **Lazy load** | Many images; load on scroll | | **Performance** | Masonry can be heavy; consider grid for simpler cases | ## Use Cases | Use case | Format | Page Skill | |----------|--------|------------| | **Showcase / Gallery** | User work; varied sizes | **showcase-page-generator** | | **Portfolio** | Projects; mixed media | — | | **Pinterest-style** | Pins; discovery | — | | **Image-heavy blog** | Blog with varied images | **blog-page-generator** | ## Related Skills - **site-crawlability**: Infinite scroll SEO; paginated component pages; search-friendly implementation - **grid**: Equal-height grid; when masonry is overkill - **carousel**: Carousel for slides/rotation; when masonry is overkill - **card**: Card structure; masonry often uses cards - **showcase-page-generator**: Gallery masonry - **image-optimization**: Lazy load, aspect ratio, LCP
When the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries," "search performance report," "URL inspection," "impressions," "CTR," "average position," "index coverage," "GSC data analysis," "Search Console API," or "searchanalytics.query." When the user wants to rewrite title tags (not only report on them), use title-tag. For meta description rewrites, use meta-description.
When the user wants to build an SEO data analysis system, monitor indexing/traffic/keywords/backlinks, or set up benchmarks. Also use when the user mentions "SEO data analysis," "SEO monitoring," "article database," "traffic benchmark," "penalty recovery," "SEO work document," "SEO dashboard," "keyword tracking," "ranking monitoring," "indexing report," or "backlink monitoring." For GSC API, use google-search-console.
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
When the user wants to analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions "traffic sources," "dark traffic," "direct traffic," "UTM parameters," "traffic attribution," "channel attribution," "attribution optimization," "channel analysis," "traffic analysis," "traffic diversification," "natural traffic benchmark," or "organic vs paid traffic." For GA4 setup, use analytics-tracking.
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.
When the user wants to promote via forums, communities, or invite users to join a community. Also use when the user mentions "forum promotion," "Indie Hacker," "Hacker News," "community growth," "Discord promotion," "vertical community," "brand encyclopedia," "Wikipedia," "Quora," "Reddit community," "community building," "forum marketing," or "community invite." For Reddit copy, use reddit-posts. For strategy, use integrated-marketing.
When the user wants to submit a product or app to directories, curated lists, launch platforms, or app stores—and needs ready-to-paste copy per platform. Reads project-context.md when present. Also use when the user mentions "directory submission," "get listed," "app store listing," "submit to directories," "curated list," "best tools list," "Taaft," "Product Hunt," "directory ads," "newsletter feature," "directory campaign," "tailor description per platform," "Shopify App Store," "Chrome Web Store," "navigation site," or "product directory." For Product Hunt launch day tactics (hunter, first comment, timing), use product-hunt-launch. For full 0→1 channel planning, use cold-start-strategy.
When the user wants to launch on Product Hunt, prepare a PH submission, or plan launch day (hunter, first comment, timing, upvotes). Also use when the user mentions "Product Hunt," "launch on Product Hunt," "PH launch," "Product Hunt submission," "hunter," "Product of the Day," "upvotes," or "Product Hunt first comment." For multi-platform directory listings and paste-ready copy beyond PH, use directory-submission.