hugo-repo

Add a new content section to the Hugo site from a directory

Set up or trigger Hugo site deployment

Scan content directories and create missing _index.md files

Scaffold a Hugo site for the current repository

Start the Hugo development server

Hugo build diagnostic and troubleshooting specialist. Use when Hugo build fails, hugo server shows errors or warnings, the deployed site renders incorrectly, content is missing from the built site, GitHub Actions deployment workflow fails, the user needs help interpreting cryptic Hugo error messages, builds are unexpectedly slow, or assets (CSS, images, JS) are not loading or processing correctly.

Hugo site architecture and scaffolding specialist for repositories. Use when the user asks to set up a Hugo site for a repository, plan documentation structure, scaffold Hugo configuration with module mounts, design site architecture for a monorepo or multi-project repo, migrate from another static site generator (Jekyll, MkDocs, Docusaurus), or integrate multiple Hugo features (mounts, themes, data, shortcodes) for a specific project.

This skill should be used when the user asks about Hugo shortcodes, creating custom shortcodes, Hugo render hooks, custom rendering for links or images or headings or code blocks, Hugo taxonomies (tags, categories, custom), page bundles and page resources, content formatting beyond basic markdown, creating callout boxes or tabs or admonitions in Hugo, or customizing how Hugo processes markdown elements. Also applies when the user wants to add reusable content components to their Hugo site.

This skill should be used when the user asks about Hugo's data directory, loading YAML or JSON or TOML data files in Hugo templates, using .Site.Data to access structured data, data-driven navigation or menus, rendering datasets or bibliographies or registries from data files, generating content from data, using range to iterate over data collections, Hugo resources.GetRemote for external data, or organizing data files for large projects. Also applies when the user wants to drive site content or navigation from structured data rather than hardcoding it in templates.

This skill should be used when the user asks to create a Hugo site, set up Hugo, start a new Hugo project, understand Hugo directory structure, configure hugo.toml or hugo.yaml, work with Hugo front matter, create content types or archetypes, run hugo server for local development, or understand Hugo content organization including section pages and page bundles. Also applies when the user is new to Hugo and needs guidance on basic concepts, URL structure, or the relationship between content directories and rendered pages.

This skill should be used when the user asks about deploying Hugo to GitHub Pages, setting up a GitHub Actions workflow for Hugo, Hugo CI/CD pipeline, content-aware path filtering for Hugo builds, caching Hugo modules in CI, Hugo PR preview deployments, Hugo build workflow, or configuring GitHub Pages deployment for a Hugo site. Also applies when troubleshooting GitHub Actions workflow failures related to Hugo builds.

This skill should be used when the user asks about Hugo module mounts, mounting multiple directories into Hugo's content tree, aggregating docs from scattered directories, using hugo mod init, configuring module.mounts in hugo.toml, building a unified documentation site from a monorepo, mapping subdirectory docs/ folders into a single Hugo site, or understanding Hugo's union file system. Also applies when the user has a repository with multiple docs/ directories that need to be presented as a single site. This is the core skill for multi-directory content aggregation.

This skill should be used when the user asks about deploying Hugo to AWS S3, S3 static site hosting, Hugo with CloudFront, the hugo deploy command, configuring Hugo's deployment section, GitHub Actions with AWS OIDC for Hugo, S3 bucket static website configuration, CloudFront cache invalidation after Hugo deploy, or choosing between GitHub Pages and S3 for Hugo hosting. Also applies when GitHub Pages limitations (auth, custom headers, size) require an alternative deployment target.

This skill should be used when the user asks about Hugo themes, installing a theme, customizing a theme, overriding theme layouts or partials, Hugo template lookup order, creating a Hugo theme from scratch, Hugo asset pipeline (SCSS, PostCSS), Hugo baseof.html, or theme configuration parameters. Also applies when evaluating which theme to use, switching themes, or troubleshooting theme-related rendering issues.