Skip to content

ricardodantas/skills / skills/hugo-expert

hugo-expert

Verified

Expert guidance for building and maintaining Hugo (gohugo.io) static sites — templating and layouts, theme creation and customization, content modeling, configuration and Hugo Modules, performance and the asset pipeline, deployment and CI, multilingual/i18n, SEO and feeds, and version upgrades. Fetches version-appropriate Hugo docs via Context7. Use inside or when starting a Hugo repo — building or customizing a theme, fixing or writing Go templates and partials, configuring hugo.toml or modules, optimizing builds, deploying, adding i18n or SEO, upgrading Hugo, or any "Hugo best practices" question. For writing blog posts in the author's voice, use hugo-write-post.

Hugo Expert

Deep help with Hugo static sites. This skill carries durable Hugo best-practices and pins live documentation lookups to the repo's actual Hugo version — Hugo ships frequently and APIs change, so verify current syntax against the docs rather than from memory.

Preflight — live docs via find-docs

Current Hugo syntax, template functions, and config keys are fetched with the find-docs skill (Context7). Confirm it's available (it appears in your available skills); if it's missing, tell the user and offer to install it — npx skills find find-docs. Without it, say so and proceed from general knowledge, flagging that version-specific details may be stale.

1. Detect the target version

Run the detector at the repo root to pin doc lookups to the right version:

"<skill-dir>/scripts/detect_hugo.py" .

It reports the config file/format, the pinned Hugo version, Hugo Modules usage, an extended-vs-standard hint, and configured themes. For a brand-new repo (is_new_repo), use the latest Hugo release — look it up (hugo version, the GitHub releases page, or Context7); never assume a hardcoded version.

2. Fetch current docs when it matters

Before asserting exact template-function signatures, config keys, or version-specific behavior, use the find-docs skill to pull the current Hugo docs (library Hugo → /gohugoio/hugo). Query one specific topic at a time, and pin the repo's version when it declares one. Rely on the references below for durable practice; reach for live docs when the detail is version-sensitive.

3. Route to the reference for the task

Read only the file(s) the task needs:

TaskReference
Go templates, partials, blocks, render hooks, lookup orderreferences/templating.md
Creating/customizing a theme, overriding, publishingreferences/themes.md
Sections, page/leaf bundles, taxonomies, front matter, archetypesreferences/content-modeling.md
hugo.toml/environments, Hugo Modules, mountsreferences/config-modules.md
Hugo Pipes, image processing, minify/fingerprint, cachingreferences/performance.md
Netlify/Vercel/Pages, CI, HUGO_VERSION, baseURLreferences/deployment.md
Version bumps, deprecations, extended vs standardreferences/upgrade-migration.md
Multilingual sites, translationsreferences/i18n.md
Sitemap, RSS/output formats, meta/OpenGraph, structured datareferences/seo-feeds.md

4. Best-practice bar (holds across versions)

  • Prefer configuration over hardcoding; keep environment-specific values in config/<env>/.
  • Build themes as Hugo Modules over copying files; override by shadowing layouts in the project.
  • Compose layouts from partials and render hooks; don't duplicate markup across templates.
  • Route CSS/JS/images through the asset pipeline (Hugo Pipes) — fingerprint and minify for production.
  • Pin HUGO_VERSION in CI/deploy so local and production builds match.
  • Verify with hugo server during work and a clean hugo --minify before shipping; treat build warnings and deprecations as work to resolve.

5. Writing blog posts → delegate

To write a blog post in the author's established voice, use the hugo-write-post skill rather than drafting prose here.

6. Validate the work

Confirm the site still builds: hugo completes without errors, hugo server renders the change, and no new deprecation warnings were introduced. Report the outcome and any warnings.

writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall