---
title: Kiro Favicon Install Guide
description: Add favicons in Kiro: generate the real files, wire them through a spec task, and use steering plus an agent hook so the icons never silently regress on rebuild.
canonical: https://favicontools.com/kiro/favicon-install
---

# Kiro Favicon Install Guide

Kiro leans on specs, steering files, and agent hooks rather than one-off prompts, which is a gift for something as easy to regress as a favicon. Encode the icon setup once (as a step in the spec and a rule in steering) and a hook can re-check coverage every time the build runs. The catch is the same as every other agent: Kiro can wire the icons but can't draw them.

## Why it matters

- **Put the rule in steering** — A steering file saying icons are generated binaries the agent must not recreate is what keeps a later spec run from helpfully re-adding a placeholder favicon.
- **Let a hook do the verifying** — Kiro's agent hooks fire on events like save or build. Point one at the favicon paths so a missing or 404ing icon surfaces automatically instead of at launch.

## Playbook

1. **Generate the files into the workspace** — Export the full kit into the static directory before the spec runs, so Kiro's tasks operate on files that already exist.
2. **Make the wiring a spec task** — Write "reference the icons in the head and manifest following the existing convention" as an explicit task, so it's tracked and repeatable rather than a loose chat instruction.
3. **Wire a hook to verify coverage** — Add an agent hook that requests each icon path against the running app, so a rebuild that breaks an icon fails loudly rather than quietly.

## Checklist

- Add a steering rule marking icon files as generated assets that must not be recreated.
- Capture the icon wiring as a task in the spec so it survives a regenerate.
- Confirm the verification hook actually fetches the paths rather than assuming success.

## FAQ

### Can Kiro generate favicon images?

No. Kiro's agent edits files and runs commands but cannot produce image bytes. Generate the PNG and ICO with a real tool, then let Kiro wire them through a spec task and guard them with steering and a hook.

### How do I stop the favicon regressing on the next spec run?

Two moves: a steering file that marks the icons as generated assets the agent must not touch, and an agent hook that re-checks the icon paths on build. Together they turn a one-time fix into something the workflow enforces.

### Where should the icon files live?

In whatever directory your framework serves static files from, with favicon.ico at the site root. Kiro can read the project to confirm the convention before its wiring task references the files.