Design prompts that work

I don't love this screen but can't name why. Give me 4 dials I can react to — like warmer/cooler, airier/denser, quieter/louder type, softer/sharper shapes — and show me what pushing each one would do.

Look across all my screens. Find any visual element that repeats — cards, buttons, list rows, headers, badges. For each, tell me if it's built the same way everywhere or if there are subtle differences. Then propose turning the repeated ones into a single shared component that every screen uses.

I want to add a [new screen / new element]. Build it from the existing components and tokens so it matches the rest of the app. Only if nothing existing fits, add the new piece to the design system rather than to just this screen.

Run an accessibility contrast check on this screen. Check every text element against its background, in both light and dark mode, and tell me whether each one passes WCAG AA. Flag anything that fails and suggest the smallest fix.

Also check non-text elements that carry meaning — status dots, icons, selection outlines, dividers. Flag any that don't have enough contrast against their background, and suggest a fix.

Check every interactive element — buttons, chevrons, icons, toggles, list rows, close buttons. Measure each one's tap target. Flag anything smaller than 44×44pt and fix it by adding padding around the element (grow the touchable area, don't necessarily grow the visible icon). Confirm the fix doesn't push neighboring elements out of alignment.

Do a consistency pass across all my screens. For each recurring element, and for spacing rhythm, corner radii, font sizes and weights for equivalent roles, button styles, how headers are built, icon style and weight, and color usage by role — check whether every screen does it the same way. Give me a table of every inconsistency, ranked by how noticeable it is, and recommend which version should become the standard.

For the inconsistencies we agreed on, make the fixes by updating tokens or shared components — not by editing screens one by one. Show me the list of tokens/components you changed.

Scan all my SwiftUI screens for hardcoded values — any color, font size, spacing number, or corner radius written literally instead of read from DesignTokens.swift — and fix them. Where there's a clear matching token, just swap it in. Where a value is close to an existing token, snap it to that token. Only pause for me on the genuine judgment calls: a value that doesn't map to anything and might need a new token. When you're done, give me a short summary of what you changed and the few decisions (if any) you want me to confirm.

When a new event is added to the calendar, I want it to feel like it gently settles into place — not a hard pop. Use a spring that's soft, not bouncy, quick enough to not feel sluggish. Show me the values you chose and let me react.

This animation feels off. Give me dials to react to: faster/slower, bouncier/calmer, bigger/subtler movement, and where it starts from. Show me what each extreme looks like so I can pick.

Make sure every animation respects Reduce Motion — when it's on, replace movement with a simple fade or no animation. Check this is wired up everywhere, not just on the main screen.

Verify every screen has proper dark-mode tokens. Flag anything that's just inverted or looks washed out rather than deliberately designed.

For each screen, do I handle the empty state (no data yet), the loading state, and the error state? Show me which are missing and propose designs consistent with the system.

Verify all my icons come from one family (SF Symbols), share a weight that matches adjacent text, and none are a stray web/emoji icon.

Do a full design-system audit of my iOS app. Use design-system.md and DesignTokens.swift as the source of truth. Cover, and give me a ranked findings table for each:
1. Hardcoded values — anything not read from the token file
2. Text contrast — WCAG AA, light and dark
3. Non-text contrast — dots, icons, dividers at 3:1
4. Tap targets — everything interactive ≥ 44×44pt
5. Cross-screen consistency — recurring elements that drift
6. Dark mode — deliberate, not just inverted
7. Reused components — repeated elements that should be shared

For each finding: the screen/file, what's wrong, severity, and the smallest fix (preferring a token or shared-component change over per-screen edits). Don't fix anything yet — show me the table first, and I'll tell you what to apply.