## TL;DR
RSpec only knows about shared examples that were loaded before the spec file referencing them runs; when `it_behaves_like` says the group is not found, the shared file simply was not required yet. Require shared-example files explicitly in `spec_helper.rb` (or via a `Dir` glob in your spec helper), and make sure `spec_helper` is required at the top of every spec. Alphabetical auto-loading is the usual trap: `a_spec.rb` runs before `shared/z_examples.rb` is ever loaded.

## The query
```text
rspec shared examples not found: load order fix
```

## Use this when
- `it_behaves_like` raises "could not find shared examples"
- Shared examples work in some spec files but not others
- You recently moved shared files into a new directory

## Not for
- Logic errors inside shared examples
- RSpec installation or version problems
- Shared context (`shared_context`) naming questions

## Steps
1. Find where the shared examples are defined and check whether anything requires that file before the failing spec runs. Expected output: you confirm the file is never required in the failing path.
2. Add an explicit require (or a `Dir[...]` glob over your support dir) in `spec_helper.rb`, and require `spec_helper` at the top of the spec. Expected output: the shared file loads on every run regardless of filename ordering.
3. Re-run the failing spec file alone. Expected output: `it_behaves_like` resolves and the examples execute.
4. Run the full suite to catch other specs with the same latent load-order dependency. Expected output: no other "not found" errors surface.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_SunkPxnohuatCdVY0-DZPQ
