hearth-documentation

Locate and verify Hearth library documentation across versions.

68|7|Updated Nov 24, 2025
One-click install
npx skills add https://github.com/kubuszok/kindlings --skill hearth-documentation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hearth-documentation
Source: https://github.com/kubuszok/kindlings/tree/main/docs/contributing/hearth-documentation
Command: npx skills add https://github.com/kubuszok/kindlings --skill hearth-documentation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Finding and using Hearth documentation across versions can be confusing; this skill provides a clear, version-aware workflow to locate ReadTheDocs pages, verify APIs with MCP, and cross-reference Hearth sources.

Core Features & Use Cases

  • Version-aware documentation lookup: determine the correct documentation URL based on Hearth version in build.sbt and environment.
  • MCP-backed API verification: validate method signatures before usage.
  • Source cross-reference: consult Hearth source references for key files when uncertain.

Quick Start

Use this skill to locate the Hearth API docs for a specific version, verify the API signatures with MCP, and cross-check against Hearth source files.

Frequently Asked Questions about hearth-documentation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find Hearth documentation for a specific version?

To find Hearth documentation for a specific version, you need a version-aware lookup workflow that reads the version from your build.sbt and locates the corresponding ReadTheDocs URL to ensure you are referencing the correct API.

What is the best way to verify Hearth API method signatures before usage?

The best way to verify Hearth API method signatures is by using MCP-backed API verification, which validates the exact signatures against the targeted library version before you implement them.

How do I cross-reference Hearth sources when API documentation is unclear?

You can cross-reference Hearth sources by consulting key source files directly, which provides accurate guidance when the ReadTheDocs pages leave you uncertain about specific implementation details.

Does locating Hearth docs across versions require checking build.sbt?

Yes, locating the correct Hearth docs requires checking the version specified in your build.sbt and environment to determine the exact ReadTheDocs URL for accurate, version-aware documentation.

Why does Hearth API behavior differ across library versions?

Hearth API behavior differs across versions because the library evolves, making it crucial to cross-reference source files and verify APIs with MCP to prevent using outdated or incorrect method signatures.