creating-kiro-packages

Steering files are Markdown documents with frontmatter-based inclusion modes (always, fileMatch, or manual) that define context for Kiro automation. Use the creating-kiro-packages skill to generate these files with appropriate inclusion logic, then populate foundational files like product.md, tech.md, and structure.md to establish project standards and trigger event-driven hooks.

Kiro hooks are JSON-based automation triggers that respond to file events and lifecycle events. Configure them by defining event types, file matchers, and actions within your Kiro package. This skill helps you set up hook definitions that automatically execute tasks—like creating test files or updating asset indexes—when specified conditions occur in your codebase.

Yes. Kiro packages enable event-driven automation through hooks that trigger on file changes. Set up hooks to automatically generate corresponding files (such as test files for new components) and update indexes or metadata. This eliminates manual repetition and ensures consistent project structure across always/fileMatch/manual inclusion modes.

Use fileMatch inclusion mode to apply steering content conditionally to files matching specific patterns (like .tsx files for React components). Use always mode for steering content that applies globally to all files. Manual mode requires explicit inclusion. Choose based on whether your automation should apply universally or only to specific file types.

Yes. Pattern validation is part of creating a Kiro package. The skill implements validation checks for fileMatch patterns to ensure your hooks and steering files trigger on the correct files. Invalid patterns can cause automation to fail silently, so validation prevents misconfigurations before deployment.

Steering files are Markdown documents providing context and inclusion rules for your project; hooks are JSON configurations defining automated actions triggered by events. Together they form a complete Kiro package: steering files establish when and where automation applies, while hooks specify what automation does when triggered.