User
Write something
Hello, I am a front end designer.
I design front end websites using framer, webflow, and wordpress. And, their prorotypes in figma for apps and websites. Here is my portfolio: https://thecreativedesign.framer.website/ Currently looking for any role or opportunity. I have more portfolio to share for any interested person.
0
0
As I'm a senior full stack developer, looking for collaborate
I'm a professional developer who has been developing projects for several years. I'm currently looking for people living in the US, Canada, or the UK who are interested in this type of business and would like to collaborate and generate revenue together. If you know of anyone who is interested, please contact me.
Hiya! Let's talk about a live workshop.
It's been a while since I prepared the last tutorials, and stuff changed a bit. Take a look at the video below - Antigravity is doing QA for me in a Chrome Browser. Sounds like a thing from "Future is here old man" meme, but it's true. Let me know if you'd like to learn more about how I build websites with Antigravity.
1
0
Hiya! Let's talk about a live workshop.
You're Using Claude Code Wrong (And Losing Hours Because of It)
Look, I've been using Claude Code for a few months now and I just realized most people are doing it backwards. Everyone's just throwing vague prompts at it like "build me a login system" and then spending forever going back and forth fixing stuff. There's a better way. Write the damn spec first. I'm serious. Before you even open Claude Code, spend 20 minutes writing out what you actually need. Requirements, edge cases, how the API should work, what errors to handle. Just a markdown file. Nothing fancy. Then (and this is the part nobody talks about) you point Claude Code directly at that spec file. "Implement the auth service in auth-spec.md." That's it. What happens next is honestly kind of wild. It reads the whole thing, sometimes asks you questions if something's unclear, then just builds it. Multiple files, proper error handling, tests that actually make sense. Because it knows exactly what you want. No more asking - actually can you change this fifteen times. No more - I forgot to mention we need to handle OAuth too. The spec is right there. And here's the thing that sold me: your specs don't disappear into some Google Doc graveyard. They live with your code. When you need to refactor three months later, the spec is still there telling you what the hell you were thinking. Try it once. Write a proper spec, save it as a .md file in your project, and tell Claude Code to build from it. You'll get why everyone who does this won't shut up about it.
0
0
1-8 of 8
powered by
Vibe coding websites
skool.com/vibe-coding-websites-9200
Vibe coding websites for webflow and nocode devs.
Build your own community
Bring people together around your passion and get paid.
Powered by