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
I’m taking a few quick React / Next.js bug-fix projects this week.
If your frontend project is broken, not deploying, or behaving weirdly, I can help with:
• React / Next.js bugs
• Tailwind / CSS layout issues
• Mobile responsiveness fixes
• Vercel / Netlify deployment errors
• Broken forms, buttons, routes, or components
• TypeScript / package / build errors
• AI-generated app fixes from tools like Bolt, Lovable, Cursor, Replit, or v0
Best fit: small, fixed-scope issues where you need a clear fix fast.
Send me your live link, GitHub repo, error screenshot, and what should happen instead. I’ll review it and give you a fixed price before starting.
Fast delivery. Clean code. Clear communication.
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
Related posts
Title:
I built a design system generator inside Figma Make. Here's the workflow.
The problem I kept running into: every new client project meant re-explaining the brand to every AI tool from scratch. Figma Make didn't know the colors. Cursor didn't know the tokens. Claude didn't know the rules. I was the shared memory — and I kept losing things.
So I built Design System Gen. Entirely inside Figma Make. Powered by Claude API.
The workflow:
Upload brand references → Claude API analyzes them across 8 dimensions (palette, mood, typography, composition, lighting, texture, motion, UI DNA) → structured data, not vibes → generates 11 files, each formatted for a specific tool in your stack.
figma-make.md → paste once, Figma Make knows your entire design system
design-system.css → all tokens as CSS custom properties
tokens.json → W3C format, imports directly into Figma Variables
starter.tsx → React starter with tokens already bound
.cursorrules → Cursor knows your system from root
Claude.md → Claude reads it automatically every session
+ 5 more for docs, LLMs, prompts, components
Every tool gets its own context file. All consistent with each other.
The part I'm most proud of: I'm a designer. I don't write code. The entire tool — UI, API integration, file generation logic — was built and shipped inside Figma Make. No external hosting. No separate codebase.
Live at: vibecodingdsgen.figma.site
Add your Claude API key and try it with your own moodboard.
#FigmaMake #DesignSystem #VibeCoding #AI #Claude #UXUI #DesignSystems #ConfigMakeathon
As someone who constantly jumps between Figma, Claude, ChatGPT, Cursor, Lovable, and other AI tools, this problem feels very familiar 😅
The tools are getting smarter, but keeping context consistent is still surprisingly manual. Love seeing people tackle that gap.
VELOCE: Redefining Digital Luxury — Bespoke E-Commerce Architecture
Hey everyone,
This is my first post here 👋
I just finished a video introduction showcasing my work as a Frontend Developer converting Figma designs into pixel-perfect, responsive websites using Next.js, React.js, Tailwind CSS, and clean HTML/CSS.
I also customize WordPress themes professionally for clients who need a polished, branded online presence.
I'm new to this community, and I'd genuinely welcome any cooperation, feedback, or advice. It would mean a lot to me. 🙏
Trending
Claude
Claude has entered the design space. How are you using Claude Design?
Contra University
Learn from expert creatives how to earn more using next-gen AI tools.
MagicPath
The canvas is infinite, and exploration is becoming the workflow. How are you using MagicPath?
creativeaiflow
Creative AI workflows are evolving. What tools do you use, and what are their strengths and weaknesses?
freelancerlife
Freelancer life is wins, pivots, and everything in between. What’s yours right now?