Jordan Bowman

28 Followers
69 Following
66 Posts
8) Ask Claude to double-check its work, look for edge cases, suggest improvements, and ensure nothing broke.
9) Remember that Claude can research and browse the web for additional context or documentation.
6) Use the `/compact` command when you hit milestones to compress down your context. If you don't, it'll force you to do it anyway.
7) Ask it to break down large tasks and run subagents simultaneously for faster completion.
4) Since there's no restore function, push to your repo often at key checkpoints so you always have a backup.
5) If you're using VS Code or JetBrains, use the accompanying extension for better functionality.
3) Run `/init` to automatically create the CLAUDE markdown file. Ask Claude to "remember" something and it will add it to this file. Put all your rules (think Cursor rules) here.
1) Press Shift-Tab to get into "Plan" mode. Use that generously to figure out what you're going to have the AI do before it does it.
2) Drag reference images directly into the terminal.
I've been blown away by the quality of work that Claude Code produces compared to Cursor, and I want to give you 9 practical tips to get the most out of it:
The design file is still useful, but it's no longer *the thing*. It's more like a shared map, a conversation starter, and a snapshot of what we're trying to accomplish.

Our real value goes beyond what's on the screen:

→ Framing things from the user's perspective
→ Asking the right questions
→ Bringing research into the room
→ Deep expertise in experience
→ Strategic thinking about what to build and why

Designers are in a unique position to lead here. We can shape direction, create clarity, and help teams align around the right problem and the best solution.

It's about direction.

Where are we headed?
Why are we building this?
How do we make sure everyone's aligned?

That's becoming more important than almost anything else.