What problem does it solve? Writing SCSS in the Lucca Front monorepo requires strict adherence to flat BEM-style naming, CSS layers, design tokens, and a canonical per-component file structure. This Skill encodes those rules so generated or modified styles pass Stylelint and stay consistent with the design system. ## Core Features & Use Cases - Naming conventions: Flat BEM-like classes (camelCase blocks, - descendants, _ adjacency), .mod-* modifiers, .is-* states, and .palette-* color variants always attached to a component. - Architecture rules: CSS @layer ordering, canonical component file layout (index.scss, component.scss, vars.scss, mods.scss, states.scss, exports.scss), and mandatory design token usage with logical properties only. - Angular integration: Wiring styleUrl to a .component.scss containing the right @use '@lucca-front/scss/src/components/<name>' imports, plus registering new components in highlight-prisme.scss. - Use Case: When adding a new numericBadge component or modifying styles in packages/scss, packages/ng, or stories, apply these rules so npm run lint:style passes and the component ships with its styles. ## Quick Start Write the SCSS for a new Lucca Front component following the lucca-front-scss conventions and wire it to its Angular component.