chore: attempt to avoid conflict

Author: caseyisonit

.cursor/rules/stories-format.mdc

@@ -46,10 +46,6 @@ Required structure with visual separators between sections:
 //    AUTODOCS STORY
 // ────────────────────
 
-// ────────────────────
-//    OVERVIEW STORIES
-// ────────────────────
-
 // ──────────────────────────
 //    ANATOMY STORIES
 // ──────────────────────────
@@ -122,26 +118,6 @@ export const Sizes: Story = {
 };
 ```
 
-### `template()` and slot content
-
-`getStorybookHelpers('<tag>')` returns a `template(args)` function. Use `template({ ...args, ... })` as the default so attributes/properties from the Custom Elements Manifest and Storybook controls stay wired to the component.
-
-Slot args (`default-slot`, `icon-slot`, etc.) accept strings only — they are injected via `innerHTML`. Plain text and self-contained HTML strings work fine.
-
-When slot content can't be expressed as a string — for example, an imported icon or `TemplateResult` content, a Lit binding like `size=${size}`, or a `.map()` call — write the host element directly with `html` instead:
-
-```typescript
-// slot content is a TemplateResult; use html directly
-html`
-  <swc-badge variant=${args.variant} size=${args.size}>
-    <swc-icon slot="icon">${checkmarkIconForSize(args.size)}</swc-icon>
-    ${args['default-slot']}
-  </swc-badge>
-`
-```
-
-Avoid duplicating SVG or nested components as long HTML strings just to force them through a `*-slot` arg.
-
 ### Documentation sections (auto-generated)
 
 **Component-specific `.usage.mdx` files are no longer needed.** The `DocumentTemplate.mdx` automatically renders all standard documentation sections based on story tags: