🎯

gatsby

🎯Skill
g1joshi/agent-skills1 Installs9Last Updated Feb 10, 2026

Installation

$npx skills add g1joshi/agent-skills --skill gatsby

Run it in a terminal; it asks which AI coding tools to install it for (Claude Code, Codex, Cursor and more).

Uses skills.sh Β· Node.js 22.20+

After installing

Ask for related work and the agent uses it on its own, or call it yourself.

Run it (Claude Code)/gatsby
Install by hand

Copy the whole skill folder from GitHub to the place below. Copying only SKILL.md can leave out files the skill uses.

Open the skill folder β†’
  • This project .claude/skills/gatsby/
  • All projects ~/.claude/skills/gatsby/

These paths are for Claude Code. For other tools, the command above puts it in the right place.

Expert Gatsby assistance covering static site generation, GraphQL data layer, Head API, and Gatsby Cloud. Use when building performant marketing sites and content blogs with React.

Gatsby

Gatsby v5 focuses on Valhalla Content Hub and improved build speeds (Slice API). While Next.js has overtaken it, Gatsby remains strong for complex CMS-driven sites.

When to Use

  • Static Marketing Websites & Blogs: Pre-rendering React pages with maximum SEO and instantaneous page loads.
  • Headless CMS Frontends: Sourcing content from Contentful, Sanity, Strapi, or WordPress via unified GraphQL.
  • High-Performance Image Optimization: Delivering responsive WebP/AVIF images with blur-up placeholders.
  • Documentation Sites: Generating static documentation with MDX and Algolia search integrations.

Quick Start

// src/pages/index.js
import * as React from "react";
import { Link } from "gatsby";

export default function IndexPage() {
  return (
    <main>
      <h1>Welcome to Gatsby</h1>
      <Link to="/about">About Us</Link>
    </main>
  );
}

export function Head() {
  return <title>Home Page</title>;
}

Core Concepts

GraphQL Data Layer & Static Query

Querying build-time metadata and CMS content:

import React from "react";
import { graphql, useStaticQuery, PageProps, Link } from "gatsby";

interface SiteMetaQuery {
  site: {
    siteMetadata: {
      title: string;
      description: string;
    };
  };
}

export default function IndexPage({ data }: PageProps) {
  const meta = useStaticQuery<SiteMetaQuery>(graphql`
    query SiteTitleQuery {
      site {
        siteMetadata {
          title
          description
        }
      }
    }
  `);

  return (
    <main>
      <h1>{meta.site.siteMetadata.title}</h1>
      <p>{meta.site.siteMetadata.description}</p>
      <Link to="/about">About Us</Link>
    </main>
  );
}

Dynamic Page Creation with gatsby-node.ts

Programmatically generating pages from GraphQL queries at build time:

import path from "path";
import { GatsbyNode } from "gatsby";

export const createPages: GatsbyNode["createPages"] = async ({
  graphql,
  actions,
}) => {
  const { createPage } = actions;
  const postTemplate = path.resolve("./src/templates/post.tsx");

  const result: any = await graphql(`
    query AllArticles {
      allMarkdownRemark {
        nodes {
          frontmatter {
            slug
          }
        }
      }
    }
  `);

  result.data.allMarkdownRemark.nodes.forEach((node: any) => {
    createPage({
      path: `/blog/${node.frontmatter.slug}`,
      component: postTemplate,
      context: {
        slug: node.frontmatter.slug,
      },
    });
  });
};

High-Performance Images with Gatsby Image Plugin

Automated responsive image optimization:

import React from "react";
import { StaticImage } from "gatsby-plugin-image";

export function HeroImage() {
  return (
    <StaticImage
      src="../images/hero-banner.png"
      alt="Modern Developer Platform"
      placeholder="blurred"
      layout="constrained"
      width={1200}
      height={600}
      quality={90}
    />
  );
}

Common Patterns

Static Page Query with GraphQL

Problem: Injecting build-time metadata or markdown content into React page components.

Solution: Use Gatsby page queries:

import * as React from "react";
import { graphql } from "gatsby";

export default function BlogList({ data }) {
  return (
    <div>
      <h2>Latest Posts ({data.site.siteMetadata.title})</h2>
      {data.allMarkdownRemark.nodes.map((node) => (
        <article key={node.id}>
          <h3>{node.frontmatter.title}</h3>
        </article>
      ))}
    </div>
  );
}

export const query = graphql`
  query {
    site {
      siteMetadata {
        title
      }
    }
    allMarkdownRemark(limit: 5) {
      nodes {
        id
        frontmatter {
          title
        }
      }
    }
  }
`;

Best Practices

Do:

  • Use TypeScript (gatsby-config.ts, gatsby-node.ts) for compile-time configuration validation.
  • Use StaticImage and GatsbyImage to eliminate layout shifts (CLS) and automate responsive sizes.
  • Leverage Deferred Static Generation (DSG) for infrequently accessed archive pages to speed up builds.
  • Configure gatsby-plugin-manifest and gatsby-plugin-offline for PWA capabilities.

Don't:

  • Use standard <img> tags for local assets; always use the Gatsby image pipeline.
  • Execute client-side API requests for data that can be queried at build time via GraphQL.
  • Query full body content inside list queries; query only excerpt and frontmatter fields.

Troubleshooting

ErrorCauseSolution
WebpackError: ReferenceError: window is not definedAccessing window or document during build-time SSR.Guard window access: if (typeof window !== "undefined").
GraphQL query failed: Field ... does not existField missing in data source or schema not yet inferred.Verify schema in GraphiQL explorer (http://localhost:8000/___graphql).
Gatsby clean requiredCache corruption in .cache/ or public/ directory.Run gatsby clean and rebuild.

References

More from this repository10