Activity
Mon
Wed
Fri
Sun
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
What is this?
Less
More

Memberships

AI Automation Society

341.8k members • Free

24 contributions to AI Automation Society
Random Beginner Recommendations
I’ve been watching a lot of content on working with AI and wanted to share what I’ve learned from my own experience. My background includes jet engine maintenance in the military, IT and information security, and hands-on trades like carpentry and welding. I’ve used AI across both digital and physical projects, and after a couple of years of experimenting, I’ve settled into two main approaches: 1) I start with a clear idea and use AI to refine it and move faster than I could on my own. 2) I start with a rough concept and use AI to help develop it into something more complete. Both approaches work, but I’ve found I strongly prefer the first. I enjoy taking time to think through ideas on my own. I’ll bring a notebook into my workshop or outside, sit in the sun, and sketch or loosely wire frame concepts. That process—just thinking and creating internally—feels like play. Sometimes I go a step further and mentally simulate the idea as if it already exists. I ā€œuseā€ it in my head, test how it functions, and push on its weak points. Doing that has helped me catch design flaws and structural issues early. I treat those like small stress tests, iterate on them, and once the idea feels solid, I bring it to AI to accelerate the build-out. For anyone new to working with AI, a few things stand out: 1) Expect friction. You will make mistakes, lose work, break things, and backtrack. That’s part of learning any new tool. 2) This technology isn’t perfect. It will fail or give bad output at times. Step away when needed and rely on your own problem-solving skills. 3) Treat it as a creative process. There’s real enjoyment in building something, not just finishing it. 4) Focus on quality. Some ideas aren’t worth rushing. Focus on what’s meaningful or interesting, even if it takes longer. 5) Keep it light. Experiment, build things with friends, and don’t take it too seriously. It’s a tool meant to support you, not replace you. 6) Work in a collaborative manner. Some times asking for feedback, suggestions, or thoughts from a model can bring back useful information.
Random Beginner Recommendations
0 likes • 3h
@Nigel Vargas exactly. I think the people who can understand the basic flow of info to and from AI systems plus the ability to orchestrate. Will do really well in this field.
Micro Tip
I hit a usage cap recently and added funds to continue. When I returned to Claude Code, I was still seeing the limit notification, which was confusing at first. After a few minutes, I realized the issue: I had previously set a monthly usage limit. Even though I added funds, I still needed to increase that monthly limit to actually use them. Just goes to show that sometimes an issue isn't actually an issue. Its just a configuration change that needs to be applied.
2
0
Micro Tip
Tom.AI.gotchi
Project for this morning 1) Wipe my spare laptop 2) Install a headless linux server 3) Install ollama3 Done! This works without internet, but it is verrrry slow to respond. My main plan is to leverage this as an overnight agent. Something I can give 1 simple task to and let it do its thing.
Tom.AI.gotchi
1 like • 1d
@Lana Frei yeah its been fun. now I have access to a free $ agent that I can have execute tasks overnight for me. since it has 8ish hours to work I can be patient. The results accuracy/quality is more important. bout to post an update later this week.
šŸ˜” Please Help!!! I don't know how to organize my projects.
Last week I was adding things to a project in CC - VS Code. My /context is 80k from the start. I thought it would be a good idea to have all the skills, all the repositories, everything together, and when I wanted to do a project I could just say "Claude, I want to do X, Y, and Z." What's the best way to do this with everything we have? But I think it's better to have everything separate. How do you guys do it? Thank you in advanced.
1 like • 3d
I've found that it depends on your folder structure and if your agent "all" the tools is not a good idea. The very first thing I did when getting my claude code setup was define my folder stucture/code base. My agent has a clear structure and reference/instructions on where and when to find files, images, tools, etc. Once that's done I was ready to start the real projects. Id recommend isolating the end result you want. I want to build a pipeline, a website, etc. Once you know your primary goal tell your agent that goal and ask if there is anything you missed or for thoughts/suggestions. Once you do a few rounds of nailing down exactly what you want you can then as your agent to break it down into major tasks. Put all of this into a file ( I use markdown files). Once the file is made you can specify which task to work on. Inevitably when working on a task it will require a tool/resource. That's when I give access or integrate the needed tools. Once that task is complete have your agent write a snap shot, summary, or description on what was done, the tools used, and the end result for that task. Then you can either compact or clear the conversation and move onto the next task. Rinse and repeat. As you work through more projects you will start to refine how you do things and how you structure your data.
1 like • 2d
@Chicho Quesada once you learn how the ai 'thinks/processes' info it makes working with it a whole lot easier. just keep building small stuff and it'll click.
AI Operation systems
I have quite a few questions. Everyone is talking about AIOS as their own product and the possibility of a monthly retainer, but since you mainly focus on the power of Claude Code, I’m not really seeing how this is actually deployed to clients. Since Claude Code runs locally, you can do a one-time setup—folders, skills, config, context, etc.—and hand it over, but that’s where it ends. You don't have ongoing access to their local machine. On the other hand, if Claude Code is only meant for developing these systems, and the actual client solution is built from scratch using the Claude API, then it kind of loses me. The raw API doesn't have "skills," plugins, or commands out of the box—it honestly doesn't even come close to a polished tool like Claude Code. So, my main question is: What is your actual approach? How do you realistically build and deploy these AI systems in the way everyone describes? Thanks a lot! šŸ™
0 likes • 3d
Ive seen a lot of people tie these AIOS in with cloud hosting. That way the system is 24/7. Triggers or crons initiate certain aspects of the system and since the agent lives in the cloud it can be called whenever. I've read about local set ups that run open source models on dedicated hardware, which as long as they have power and an internet connection they are pretty much free.
1-10 of 24
@bagu-hanto-1997
Been working casually with AI for 2ish years. Starting to really dive into building a custom EA, vibe coding, and leveraging AI as an instructor.

Online now
Joined Dec 8, 2025
Errff
Powered by