The ancestor checks judge the rendered DOM tree, not a single source file. In framework
The ancestor checks judge the rendered DOM tree, not a single source file. In framework
projects (Next.js/React components, Astro pages, partials/templates) the provider often lives in
a parent file - <storesynk-store> in the root layout/shell, the product markup in a page or
component. Validating such a fragment alone makes every consumer look orphaned and floods
false-positive SSK-101/102/105/110 findings. Before trusting them, check the enclosing
layout/shell for the provider; if it’s there, the finding is a false positive - do not “fix”
it by adding a second provider (that trips SSK-104 nesting and breaks the page for real). To
validate properly, compose the tree: paste the fragment inside its real ancestors in a temp file
and re-run. Conversely, SSK-401 auto-fires only on full documents (doctype / <html>) - on
fragments, manually confirm the bundle loads once at the shell/layout level.
Imported from the Storesynk skill v0.1.0 (references/structure-rules.md). To change this page, change it there.