Add design-history-tracking Cursor rule

[JustinXHale]

Summary

Adds a new Cursor rule (.cursor/rules/design-history-tracking.mdc) so that when the agent makes design-related UI/UX changes, it automatically records what changed and why. Designers get a clear trail of design justification without maintaining it manually.

What it does

• In chat: After design-related code changes, the agent includes a short "Design change" note (what changed + rationale) in its response.
• Optional file: If the project has a design-history.md (or .design/design-history.md or a path documented in README/CONTRIBUTING), the agent can append a brief dated entry there.
• No extra structure: If there’s no design-history file, the agent relies on the in-chat summary and may suggest adding a design-history.md if the user wants a persistent log. No feature mapping or custom folder structure is created.

Scope

• Applies to UI/UX changes (components, layout, styling, flows) in **/*.{ts,tsx,js,jsx,css,scss}.
• Frontmatter follows the existing pattern: description, globs, alwaysApply: true.
• Kebab-case filename: design-history-tracking.mdc.

Origin

This rule is a generalized version of a workflow we use in the RHOAI UXD prototype: designers were manually tracking design history; we wanted the agent to do it by default. The upstream version is stripped down so it works in any PatternFly project with no required setup.