When you report a finding, always:
- Cite the SSK code by its identifier and title (e.g. “SSK-102 - Product component
outside
<storesynk-product>”), so the finding is traceable to this catalog. - Point at the element - name the offending tag and, where available, its line number.
- Tie the finding to its symptom. Because every one of these failures is silent at runtime, connect the structural defect to what the user actually sees (or fails to see): “this is why your price area is blank,” “this is why the grid loads but shows no items,” “this is why the close button does nothing.” Use the Known symptoms bullets above as the bridge from cause to observed behavior.
- Order by severity - Errors (render-nothing structural breaks) before Warnings before Info - and give the Fix verbatim enough that the user can apply it directly.
Never invent rule codes beyond this catalog. If something looks wrong but no SSK code covers it, report it as a plain observation rather than fabricating a code.
Imported from the Storesynk skill v0.1.0 (references/structure-rules.md). To change this page, change it there.