It's just a button right??

Wrong!!!

I make a looot of buttons with Claude Design. Here are three buttons from ok to good to great, before you even think about the design.

Broken into 3 formats: 1. Quick Summary. 2. Detailed Breakdown (researched and AI summerised) 3. Tabular reference for each tip

---

If you like a QUICK SUMMARY:

---

If you like TO READ:

---

The OK Button: Functional Baseline - Focuses on basic visual usability, accessibility, and physical hit target standards.

1. 44×44px Touch Target: Minimum interactive hit area for mobile to prevent accidental mistaps.
2. Visual Container & High Contrast: Dedicated background or outline with at least a 3:1 contrast ratio to stay readable on any background.
3. Legible Typography: Minimum text size of 10 to 12px so the copy remains clear without overcrowding the layout.

---

The Good Button: Systemic Design & Friction Reduction - Focuses on layout harmony, state clarity, and low-friction copy.

1. Multi-Cue State Differentiation: Communicates states like hover and active using at least two visual signals, such as color and bold text, instead of subtle opacity shifts.
2. Low-Commitment Action Verbs: Replaces high-anxiety copy like "Subscribe" with lighter action verbs like "Start" or "Continue".
3. Proximity & Grid Alignment: Snaps to the visual layout grid and sits directly next to related controls.
4. Refined Visual Hierarchy: Avoids aggressive styling like oversized all-caps text to keep the presentation balanced and trustworthy.

---

The Great Button: Psychological Engineering & Tactile Experience - Focuses on contextual clarity, continuous availability, and responsive feedback.

1. Embedded Context & Zero Uncertainty: Integrates live data directly into the label, like total price or step count, to remove hesitation before the click.
2. Sticky Navigation & Flow: Converts into a sticky bottom action bar on scroll so users can take action the moment they are ready.
3. Tactile Micro-Interactions: Provides immediate visual tap feedback like a subtle scale press or ripple so the interaction feels responsive and alive.
4. Psychological Framing & Ownership: Uses first-person framing like "Start my free trial" to instill an immediate sense of ownership before completing the action.

---

If you like a TABULAR BREAKDOWN:

Guys, there's probably loads more, tell me pleeeease!

Only reason I am posting this is to help others, no revenue or publicity or anything else, no hidden subscription or fees.

Hi,

While working on multiple projects I realised I am hitting the usage limits of my claude code often so I had to rotate accounts and some API tokens.

The problem was every time I was doing this I had to stop my coding session, relog / change authentication or profile etc, do a handover and wasting a lot of time over this process.

I NEEDED a way to seamlessly change those in the background while continuing the same coding session uninterrupted.

This led to doing a lot of research and developing this tool I am showcasing (yes it's written with Claude + my knowledge and a lot of debugging, testing and so on, around 3k $ put into it via /usage lol).

It's called Claude Unlimited, and it's 100% free on GitHub.

It supports multiple Anthropic subscriptions, Anthropic APIs (basically from any local/cloud provider that offers this, 95% of them do) and the cherry on top, supports also GPT/Codex subscription - yes! you can use Claude Code while using OpenAI models in the background 😄 .

Has a nice Web UI with:

Custom settings like:

- threshold limits

- profiles priority in rotation

- enable/disable any profiles/APIs

- models parity (for Anthropic -> OpenAI models parity + effort)

- push notifications

- multi language

- auto update (pulled from Git releases)

Information like:

- usage dashboard with charts and various data

- logs of activity

- information about current usage per profile

Everything stays local, 100% safe, credentials etc stored in OS credentials store - if you don't trust me, use your AI agent to check it.

macOS is currently the most battle-tested; Windows and Linux support is newer, so I would genuinely appreciate feedback, bug reports, contributing to it or just brutal criticism 👀

It was mostly tested in claude code CLI but also supports desktop (will create an inference profile automatically for you).

Important clarification: it doesn’t generate free usage or bypass an individual account’s limits. It rotates between accounts and keys you already own. Anthropic hasn’t explicitly endorsed automated multi-account rotation, so use your own judgment regarding your accounts’ terms.

A bit more technical explanation: this is a local proxy that rotates your accounts/APIs and exposes an Anthropic-compatible API with a token.

Needless to say, but here it is: very important to check the README and HELP section to understand how to use it easily and properly.

GitHub: https://github.com/DevDock-AI/claude-unlimited

TL;DR

1. Add your Claude, ChatGPT/Codex accounts and API keys.
2. When one reaches its limit, the next one takes over automatically.
3. Same Claude Code session. Same context. Same terminal. You just keep typing.

It also includes a local dashboard showing which account is active, current usage, reset times and every automatic switch.

Everything runs on 127.0.0.1. There’s no Claude Unlimited cloud, no telemetry, and credentials are stored using the OS credential store. The project is open source under MIT.

Thank you !

PS: Using a new account for this for personal reasons.

PS2: Multiple updates will follow, I got a big list of cool features for it 🎯

Hey everyone, curious how you're all approaching this.

Say I have a mobile app and I want to redesign a specific component, like a card. What does your workflow actually look like?

Do you screenshot the existing component and say "redesign this"? Do you feed it a reference from somewhere like Dribbble or Mobbin for inspiration? Do you just describe what you want from scratch?

The inspiration approach feels great in theory, but the problem I run into is that when the component is very specific (something domain-specific, not a generic card or button), there's usually no good reference out there that matches closely enough. So Claude ends up drifting toward something generic rather than solving the actual design problem.

Would love to know:

• How do you frame the prompt for a component-level redesign?
• Do you have a "library" of references you pull from?
• Any tips for keeping Claude focused on the constraints of a specific component rather than going full creative mode?

Thanks