← Browse

@gethugothemes/hugo-template-guidance

A

Use whenever you need to understand how this theme works — adding pages, managing content, configuring the site, using partials/components/modules, project architecture, scripts, or styling/theming (Tailwind v4, Bootstrap 5, or a hybrid — verify which). Use for ANY question about the structure, usage, or customization of the template or theme.

skillclaude

Install

agr install @gethugothemes/hugo-template-guidance --target claude

Writes 1 file into .claude/skills/, pinned to git-97696899.

  • .claude/skills/hugo-template-guidance/SKILL.md

Document


name: hugo-template-guidance description: Use whenever you need to understand how this theme works — adding pages, managing content, configuring the site, using partials/components/modules, project architecture, scripts, or styling/theming (Tailwind v4, Bootstrap 5, or a hybrid — verify which). Use for ANY question about the structure, usage, or customization of the template or theme.

Template Guidance

Handbook for this theme (Hugo Extended + Hugo Modules; styling is Tailwind v4, Bootstrap 5, or a hybrid — verify before assuming), assuming the standard project-setup layout (site at root, theme vendored in themes/<theme>/ — the single folder under themes/; see references/detect-mode.md to find its name). Progressive disclosure: read the matching references/ file before acting.

If exampleSite/hugo.toml exists, the repo is still in theme-setup — run <pm> project-setup first (see references/detect-mode.md) before using anything below.

Package manager: <pm> is a placeholder for this project's package manager. Detect it from a lock file (pnpm-lock.yaml, package-lock.json, yarn.lock, bun.lock/bun.lockb) or package.json's packageManager field before running any command below — don't assume pnpm. Details: references/script-usage.md.

Routing Guide

RequestRead
Detect or convert setup mode (theme-setup vs project-setup)references/detect-mode.md
pre-flight checks (Node, Hugo version, package manager)references/preflight-checks.md
Architecture, folder layout, data flowreferences/project-architecture.md
Add a page, route, or homepage sectionreferences/adding-new-pages.md
Partials, components, shortcodes, Hugo Modulesreferences/component-usage.md
Add, remove, or enable a Hugo Module (module.toml)references/hugo-modules.md
Markdown content, frontmatter, taxonomiesreferences/content-management.md
Add/configure a new language, multilingual, i18n, translatereferences/i18n-guidance.md
Site config, menus, social, feature toggles, SEOreferences/page-configuration.md
Package manager detection, scripts, generators, module updatesreferences/script-usage.md
Styling/theming (Tailwind v4, Bootstrap 5, or hybrid — verify first), dark mode, design tokensreferences/styling-and-theming.md

Steps

  1. Read the matching reference.
  2. Follow it.

Trustgrade A

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • passLicense

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-97696899957c2026-07-31