Document the MyTypes global namespace pattern

[narutamaaurum]

Closes #97

Summary

• add a dedicated README section for the MyTypes global namespace pattern
• explain how modules.d.ts, store/types.d.ts, and services/types.d.ts work together
• include example imports that show how shared app types are consumed

Validation

• npm run ci-check
• cd playground && npm run tsc

[gemini-code-assist]

Code Review

This pull request introduces a new "Types global namespace" section to the documentation, detailing the use of the MyTypes module for shared ambient type declarations. Feedback suggests avoiding shorthand module declarations to prevent type safety issues, consolidating this new section with existing documentation to avoid redundancy, and refining type aliases to remove redundant wrappers and improve naming clarity.

[gemini-code-assist]

The use of a shorthand module declaration (e.g., declare module 'MyTypes';) in modules.d.ts is discouraged for internal type namespaces. Shorthand declarations make all imports from that module any, which bypasses type checking for missing or misspelled types. It is better to use an explicit (even if empty) module declaration: declare module 'MyTypes' {}.

[gemini-code-assist]

As noted in the generated README, using a shorthand module declaration for MyTypes is unsafe as it defaults all imports to any. It is recommended to update the referenced playground/typings/modules.d.ts to use declare module 'MyTypes' {} instead.

[gemini-code-assist]

This new section "Types global namespace" significantly overlaps with the existing "Create Global Store Types" section (around line 1288). To improve maintainability and avoid documentation drift, consider consolidating these sections or having one reference the other.

[gemini-code-assist]

The naming of the Store type alias is confusing because StateType<typeof store> returns the State type, not the Store instance type. Since RootState is already defined below, this alias might be redundant or should be renamed to reflect that it represents the state tree.

[gemini-code-assist]

The use of ReturnType inside StateType is redundant. StateType from typesafe-actions automatically extracts the return type when a function (like a reducer) is passed.

Suggested change

	export type RootState = StateType<ReturnType<typeof import('./root-reducer').default>>;
	export type RootState = StateType<typeof import('./root-reducer').default>;

[gemini-code-assist]

This new section overlaps with the existing "Create Global Store Types" section at line 508. Consider merging them to maintain a single source of truth for the MyTypes pattern.

[narutamaaurum]

Addressed the highest-priority namespace feedback in this branch update. The example now uses an explicit empty declare module 'MyTypes' {} declaration, and the new section points back to the earlier store-types setup to reduce duplication.