Point Archeo at any website. Hit capture. In 30 seconds you get: - every color token on the page - the full type scale - spacing values - all of it as JSON, Markdown, or Tailwind config No inspecting elements. No guessing hex codes. No copy-pasting. I built this because I was doing a brand audit for a client and spent two hours manually pulling colors and font sizes from a site I didn't have Figma access to. Now it takes 30 seconds. But the design export is just one side of it. The other thing Archeo does: it saves any web page as a fully working offline copy. Three formats: - ZIP with the full file structure - Single HTML with everything inlined - MHTML browser snapshot It scrolls the page before capturing so lazy-loaded content doesn't get missed. It pulls from Shadow DOM. It rewrites links so navigation still works offline. It strips trackers before saving. The result is a complete, portable, interrogatable copy of any page. Useful for: - saving competitor landing pages to reference later (they will change) - building reference libraries without bookmarks that die - feeding a full page to an AI tool without losing structure - auditing client sites before a redesign kickoff No cloud. No login. No analytics. Everything runs locally in your browser. v1.1 is live at archeo.dev $9 minimum, pay what you want. 14-day refund if it doesn't click for you. Community code AIDC20 takes 20% off. First 100 uses only! If you're doing any client work, competitive research, or design auditing, try it this week.

Hi everyone 👋 I am an AI and full-stack engineer working on LLM systems, AI agents, automation, and multimodal AI (text, voice, and vision). Most of my work focuses on building AI systems that run in real production environments, not just demos. I usually connect LLMs with APIs, databases, tools, and business logic so they can operate reliably inside real workflows. *AI / ML Systems* • LLM orchestration pipelines • tool use (ReAct-style) and reasoning loops • safety guardrails and grounded generation • evaluation and reliability pipelines • multi-agent workflows and memory systems • RAG systems (vector databases, hybrid search, custom retrievers) • document intelligence (PDF extraction, OCR, structured data pipelines) • multimodal AI (text, voice, vision, audio pipelines) *Full-Stack & Infrastructure* • React / Next.js frontends • FastAPI / NestJS backend systems • secure APIs and RBAC design • automation pipelines (n8n, Zapier, Make, webhooks) • API integrations and workflow orchestration • cloud deployment and scalable backend systems • monitoring, observability, and production reliability Recently I have also been exploring AI systems in the music industry, including music understanding, audio analysis, recommendation systems, and AI-assisted production workflows. I have worked on systems in areas like healthcare AI, document intelligence, and automation platforms. For this good community, Let's build perfect a lot ! 💪

Been using this on client projects for months. Time to ship it. It's called Archeo. It downloads any web page as a working offline copy. Three formats: ZIP with full file structure, Single HTML with everything inlined, or MHTML as a browser snapshot. The scanner scrolls the page before capture to catch lazy-loaded content, pulls from Shadow DOM, rewrites links so offline navigation works, and blocks trackers before archiving. There's also a design system export. Point it at any site and it outputs color tokens, type scale, and spacing as JSON, Markdown, or Tailwind config. I use it for audits and reading codebases. No cloud, no login, no analytics. Fully local. v1.1 is live at archeo.dev. $9 minimum, pay what you want, 14-day refund if it doesn't work for you. For the community: use code AIDC20 for 20% off. First 100 uses only. If you try it, let me know what breaks. That feedback is more useful than anything right now. archeo.dev

I know I have been AFK for a few weeks now. Trust me, I have been spending hours tinkering with AI. So many new tools, improved old ones, I wanted to come back to AI Design Club and improve certain aspects based on everything I learned. I am happy to introduce a new place for you to browse all classrooms easily The AI Design Club website is live. Go here: https://www.aidesignclub.io And the classroom is now its own standalone thing: https://www.aidesignclub.io/classroom Drop your email, get a magic link, and you're in. Free. (you can access the website from the Classrooms page anytime also) What's inside right now: - Claude Code guide (+ 7 deep-dives: CLAUDE.md, MCP servers, multi-agent workflows, etc.) - Lovable - v0 - bolt.new - Orchids - Cursor - Stitch Seven complete guides. None of it is documentation rewrites. All written from actual sessions, real builds, places where things break. That's basically what separates this from everything else out there. The community runs on a freemium model. Free gets you the full tool guides. More is coming for the paid side, specifically Studio OS, which is the structured curriculum built around the Drewskii Method. I'll share more on that as it gets closer. For now, start with the classroom. Go through whichever guide covers the tool you're working with right now. And if something is broken, looks off, or a link does nothing, tell me in the comments. Still shipping and fixing as I go. What would you want to see added? Prompt library, design system templates, something else? Drop it below.

Quick question for you: What’s the #1 thing holding you back from using AI in your design work? 🔹 Figma-to-code handoffs (too slow, miscommunication) 🔹 Debugging AI-generated code (errors, broken deployments) 🔹 Client buy-in (they think AI work looks "cheap") 🔹 Learning curve ("I don’t know how to code") 🔹 Other (reply with your struggle!) Why? I’m building a free guide to solve the top 3 pain points—and I want to hear from you. Drop your answer below! ⬇️ (P.S. The most-upvoted struggle gets a dedicated tutorial next week!)