bydeepklarity· 18 skills
Consults existing breadcrumb analysis docs before exploring the codebase. Use this skill whenever the user asks about how a flow works, where something happens in the code, how to debug or test a specific area, what files are involved in a feature, or needs to understand the path data takes through the system. Also trigger when the user mentions 'where does X happen', 'how does Y work', 'trace this', 'what files handle Z', 'how to test this flow', 'debug this area', or when you're about to spawn multiple exploration subagents to understand a cross-cutting flow. Even if the user doesn't explicitly ask — if the task requires understanding how multiple layers connect (frontend → backend → worker → CLI), check breadcrumbs first. This is cheaper and more accurate than re-discovering the same information through code search.
$npx -y skills add deepklarity/harness-kit --skill hk-follow-breadcrumbInstalls into the current project.
Run `npx skills use "https://github.com/deepklarity/harness-kit" --skill "deepklarity/harness-kit/hk-follow-breadcrumb"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/deepklarity/harness-kit" that are relevant to the current task. Run `npx skills add "https://github.com/deepklarity/harness-kit"` and select the relevant skills, then follow their instructions.