CSF: Fix incorrect CSF constructs

[jonniebigodes]

Closes #

What I did

With this pull request, some of the CSF stories constructs were updated to align with the rest of the documentation and prevent misconceptions

What was done:

• Fixed some of the examples to align with the rest of the documentation on their CSF story constructs

Checklist for Contributors

Testing

The changes in this PR are covered in the following automated tests:

• stories
• unit tests
• integration tests
• end-to-end tests

Manual testing

This section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!

Documentation

• Add or update documentation reflecting your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

Checklist for Maintainers

• When this PR is ready for testing, make sure to add ci:normal, ci:merged or ci:daily GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found in code/lib/cli-storybook/src/sandbox-templates.ts

• Make sure this PR contains one of the labels below:

  Available labels

  • bug: Internal changes that fixes incorrect behavior.
  • maintenance: User-facing maintenance tasks.
  • dependencies: Upgrading (sometimes downgrading) dependencies.
  • build: Internal-facing build tooling & test updates. Will not show up in release changelog.
  • cleanup: Minor cleanup style change. Will not show up in release changelog.
  • documentation: Documentation only changes. Will not show up in release changelog.
  • feature request: Introducing a new feature.
  • BREAKING CHANGE: Changes that break compatibility in some way with current major version.
  • other: Changes that don't fit in the above categories.

🦋 Canary release

This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the @storybookjs/core team here.

core team members can create a canary release here or locally with gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=<PR_NUMBER>

Greptile Summary

This PR standardizes CSF (Component Story Format) constructs across Storybook documentation snippets to align with modern TypeScript best practices and ensure consistency throughout the codebase. The changes focus on four documentation files that contain code examples used throughout the Storybook documentation.

The key improvements include:

1. Modern TypeScript patterns: Updated examples to use the satisfies operator instead of explicit type annotations on meta objects, providing better type inference while maintaining type safety
2. Consistent type derivation: Changed Story type definitions from StoryObj<typeof Component> to StoryObj<typeof meta> for better type consistency across story definitions
3. Framework-specific examples: Added Angular-specific examples with proper component imports and type annotations to complement existing examples
4. Standardized formatting: Unified comment formatting using arrow notation (👇) and consistent placement of export default meta declarations

These documentation snippets are used as reference examples throughout Storybook's documentation system. The updated patterns demonstrate current best practices that provide better TypeScript support and align with how modern Storybook applications should be structured. The changes ensure that developers copying these examples will use the most effective patterns available, preventing the propagation of outdated or suboptimal CSF constructs.

The affected files (play-function.md, my-component-skip-tags.md, my-component-include-tags.md, and my-component-exclude-tags.md) serve as template snippets that are likely referenced across multiple documentation pages, making this standardization effort particularly valuable for maintaining consistency across the entire documentation ecosystem.

Confidence score: 5/5

• This PR is extremely safe to merge with virtually no risk of breaking changes
• Score reflects documentation-only changes that improve consistency and modernize examples without affecting functionality
• No files require special attention as these are purely documentation improvements

Context used:

Context - When documenting code snippets, ensure to include Svelte CSF and CSF examples, and also include JS and TypeScript variants. (link)

[greptile-apps]

_{4 files reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}

[nx-cloud]

View your CI Pipeline Execution ↗ for commit b1d992e

Command	Status	Duration	Result
nx run-many -t build --parallel=3	✅ Succeeded	1m 9s	View ↗

---

☁️ Nx Cloud last updated this comment at 2025-08-11 18:28:25 UTC

[kylegach]

LGTM