Isn't it scary how many features Claude has shipped in the last two months. In the

Isn't it scary how many features Claude has shipped in the last two months. In theIsn't it scary how many features Claude has shipped in the last two months. In the

The network for creativity

Join 1.25M professional creatives like you

Connect with clients, get discovered, and run your business 100% commission-free

Creatives on Contra have earned over $150M and we are just getting started

Back to feedPost

Jerry Rodriguez

pro

• Mar 13

Isn't it scary how many features Claude has shipped in the last two months. In the last 60 days, Claude shipped:

→ Memory across all accounts → 1M token context window → Opus 4.6 → Sonnet 4.6 → Haiku 4.5 → Plugin marketplace → Task scheduling in Cowork → Excel + PowerPoint add-in upgrades → Claude Code Security → Enterprise Analytics API → Skills support in desktop add-ins → Interactive charts & inline visualizations

That's just in two months. Not a year..

Claude

Denys Dod

pro

• Mar 16

Your Design System has a "Delivery Gap" — and it’s a black hole for your time. 🕳️ Most teams treat Figma and Code as two separate worlds. The result? Manual handovers, "close enough" styling, and endless Slack threads. Here is my Claude Code Workflow to bridge this gap and automate implementation: Token Sync (Figma to JSON): Use Tokens Studio or Figma Variables to export your design decisions as a JSON file. No more hardcoded hexes. The Transformer (Style Dictionary): Run the JSON through Style Dictionary. Claude Code Component Base: Use your React base knowledge to define Props and States. Git Automation (The Pipeline): . A push in Figma = a Pull Request in the repo. Live Documentation: Connect everything to Storybook or Chromatic. Your documentation is always synced with the latest production code.

Claude Figma crypto

Alex Ginsberg

• Mar 16

People have been talking about this Dario Amodei quote from Davos that AI could do most of what software engineers do within 6-12 months.

What’s interesting to me is that he wasn’t just talking about better coding tools - he was arguing that software engineering may be one of the first domains to get close to full task automation (which could then accelerate AI progress itself)

Curious how this is showing up for freelancers here... What parts of software work feel closest to full automation right now, and what still feels very far away?