Use the moment you're forced into a workaround because the clean Spiderly-native path didn't exist — you looked for a lifecycle hook, an override, an entity attribute, or a generator option and it was structurally missing, so you had to bypass or copy generated code, or reach into framework internals. Also use when the gap is in Spiderly's own skills, plugins, or docs — a skill that should have fired but didn't, or skill/doc content that was missing, stale, or wrong for the case you hit. Turns that gap into a pre-filled GitHub issue URL against filiptrivan/spiderly that the user copies and submits. Also invoke manually to report a Spiderly limitation. NOT for hacks in the consumer's own business logic, NOT for ordinary bugs in your own code.
$npx -y skills add filiptrivan/spiderly --skill report-gapInstalls into the current project.
Run `npx skills use "https://github.com/filiptrivan/spiderly" --skill "filiptrivan/spiderly/report-gap"` 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/filiptrivan/spiderly" that are relevant to the current task. Run `npx skills add "https://github.com/filiptrivan/spiderly"` and select the relevant skills, then follow their instructions.