👤 Who I am: Joshua Everett, based in Charleston, South Carolina. 🛠️ What I actually do: Independent strategy and operations consultant. Most of my day-to-day is business strategy and process workflows—helping teams streamline how their work actually moves and gets done. 🤖 What I'm building with AI right now: Using AI agents to bridge my consulting work into the creative projects I'm genuinely passionate about. I'm laying the groundwork to build out several applications across different areas—from legal frameworks to book writing and personality assessments—with plans to create content around some of my creative disciplines (painting, writing, design, boxing). 🎯 What I'm looking for connection-wise: 1. Collaborators interested in teaming up on creative or alternative app concepts. 2. Anyone who already has their workspace architecture and file structure dialed in and is open to sharing some pointers to speed up my setup so I can start cruising. 📫 Best way to reach me: Drop a comment below or send me a DM here on Skool.

I built a simple receipt logging system that reads incoming files, renames them consistently, moves them into organized archive folders, and logs each purchase into a clean CSV ledger. Existing options fall short because off-the-shelf expense apps lock your data behind monthly subscriptions, force everything into proprietary cloud dashboards, and don't organize the actual files on your own computer the way you want them. To match my actual workflow, I made two simple design choices: 1. Keep everything in local files and folders: Receipts get automatically renamed with the date, vendor, and amount, then filed into year and month folders next to a single CSV ledger. Everything stays on my drive, fully searchable and independent of any third-party app. 2. Flag missing details instead of guessing: When a receipt is blurry or cut off, the system routes it to a review folder and asks for the confirmed total before touching the ledger. That keeps the expense log completely accurate without risking bad data.

I’m building a system that turns Human Design blueprints into tabletop RPG character cards and evaluates synergy across an adventuring party. Right now, running this in basic web chats gets messy fast—I'm constantly re-pasting archetype tables, gate rules, and class mechanics, and the model tends to guess at channel completions or party balance instead of checking the actual mechanics. Looking at the Tool Ladder, Level 3 (working in an editor with local files) is the sweet spot. It lets me keep reference guides and generated player cards organized in plain text, while running quick Python scripts to handle the math—calculating defined centers, completed channels, and team balance deterministically. It’s tempting to jump straight to building a full custom web app (Level 4), but an editor workspace solves the actual friction without the headache of building a UI from scratch. Web chat was fine for drafting a one-off character card, but it fell apart the moment I needed to compare three or four character profiles side by side to see how their mechanics click together. A disciplined folder structure gives me persistent files, a clear home for reference data, and zero front-end overhead. The real trigger for moving to a custom app would be handing it to other people. As long as I’m the one generating cards and running party synergy audits, a local workspace gives me complete control. If I ever want other players to plug in their birth data directly and explore their character cards through a clean visual interface, that’s when building a standalone tool makes sense.

Hey everyone! I'm Joshua and I'm very happy to have found this group. 🙋 A little about me: Artist at heart, habitual DIY remodeler, and newly fantasy fiction reader (fresh off The Name of the Wind). While I’ve spent years building physical things with my hands, I’m diving headfirst into building and shipping my own digital ideas. 🎯 My current goal: Getting an efficient creative stack dialed in so I have the structure to focus entirely on personal creative output. 💪 What I'm currently building/working on: Drafting my first novel, while concurrently building an app that maps Human Design profiles and archetypes into D&D-style character frameworks. 🤔 My biggest struggle or question right now: Moving past piecemeal chat-window prompting into a sustainable, multi-file developer baseline. I love the leverage AI gives to someone with frontend experience, but I need the right toolchain and scaffolding so I’m not constantly stitching copied snippets together. Let's get it! 🚀

I primarily use AI as a conversational sounding board—talking through ideas back and forth to figure out the best way to bring them to life—and I'm currently using it to build out a website. In the past, I've leaned on AI to build quite a few advanced Microsoft tools and scripts, but it has all been done through the manual copy-paste loop. Right now, I’d say I’m right at the beginning of the structured systems stage, though still very much in the setup phase. One thing that caught my attention from this lesson is the interpretable context methodology, because establishing transparent, structured context up front means the AI actually understands the bigger picture of what I’m building—eliminating the need to constantly feed it fragmented snippets or re-explain project constraints in every new chat. I'm excited to learn how to lock down a solid, reliable workflow and see how structured approaches to AI can help me stop messing around with the tedious, non-creative parts of the process, freeing me up to spend more time actually creating and building.