I have been a content creator in the BJJ niche for a decade and a half now. When I started playing with Ai and Machine Learning my vision was very narrow - I wanted to teach a LLM how to do jiu jitsu! Ha! Not impossible but a task tantamount to it with the depth and breadth of the nearly infinite permutations of the way the human body moves in conjunction with another human's body trying to manipulate it with nearly infinite paths of resistance and compliance. But I digress... 🤓 I saw a friend building a project to set an agent free researching content in a specific niche and then generating short YouTube clips based on its findings. The best part - it was gathering statistics and analytics to use as fuel for self-improvement! He had it set up so each iteration started in a new session and used analytical data from the last to improve upon it. I was fascinated and decided to try to reproduce it myself. bjjDigest.com was born. Today I have a near-fully autonomous Content Creation Engine that I set free on the BJJ community. Calibrated to my "voice" from a decade and a half of my own content - it generates News Articles for real-world Current Events in the BJJ space, with a snarky, sarcastic, dry tone (me). It also writes Satire Articles - I'm pretty proud of this part. As LLMs aren't known for their comedic timing or judgement. The weakest link in this chain (in my opinion) was actually its impetus - the YouTube shorts. And yes - it closes the loop I saw in my friend's project, and honestly this is the part I'd point to first. The research never really stops. Every couple hours it scans the BJJ landscape - news, forums, RSS, event results - and scores what it finds, ranking the topics worth writing about and working out the angle on each one. That scored board is what feeds the pitch generator - nothing gets written that the research didn't surface first. Then the other half of the loop runs backward. It reads its own analytics - what actually landed on YouTube and the sites - and uses that to re-weight what it goes looking for and which topics it prioritizes next. Each run starts in a fresh session and inherits the last run's data, so it's not really "generate content" so much as "generate, watch how it did, adjust, repeat." Slowly, it's learning what this audience actually responds to.

I rebuilt my site today with the focus on folders over agents. It's geared toward providing the workflows for businesses. Not sure if this is allowed here, but I'm sharing anyway. Take it down if it breaks any rules. So many great minds here, so I thought it was worth risking criticism or advice on how to improve. Perhaps it will give you ideas for your own site. Check it out: optimarketai.com

We talk about folders all day, but the folders are FOR something. I want to know what... 🎖️Bonus points: comment with the single most painful manual process in your industry. The best comp entries come from exactly those answers.

Someone shared that a person a reaction video was made about my method and at first I was nervous but immediately it was amazing praise. I have never met with this person one-on-one and I haven't paid them or done anything other than post my own videos ! I think they do a great job at breaking some of the concepts down. It does an amazing job of breaking down some of the logic especially some parts where I go ranting in my video he slows it down a bunch ! Much needed

I just can't keep this one to myself. When your conversation is getting close to being compacted. Don't let it! I created a hook that warns me I'm at 75%. Then I apply a skill that I call "loop context". /loopcontext loopcontext.md --- description: Reason only over the verbatim content already loaded in context -- no new gathering; no summarizing. argument-hint: [Optional question to answer under the lock] CONTEXT-LOCK MODE - follow these rules strictly for this turn and every turn after it, until i explicitly say to lift the lock: 1. **Do NOT gather new information.** Make no tool calls that pull in external data -- no Read, Grep, Glob, Bash, WebSearch, WebFetch, and do not spawn agents to fetch anything. Work only from what is already loaded in this context window. 2. **Do NOT summarize or compact.** Never substitute a condensed paraphrase for the loaded content in your reasoning. The verbatim text already in context is the source of truth -- reason over it directly, not over a summary of it. 3. **Traverse the full loaded context before answering.** Actually work through what is loaded - earlier messages, file contents, tool outputs -- rather than relying on your running impression. Treat a detail that appears only once, or buried mid-context, as just as important as the most recent content. 4. **If the answer genuinely requires information NOT present in the loaded context, say so explicitly,** state exactly what is missing and stop - do not guess and do not fetch it. Let me decide whether to lift the lock. Acknowledge in one line that context-lock mode is active, then proceed. If I included a request after the command, answer it under these rules: $ARGUMENTS I've ran several tests against this, where I'm testing the collapsed versions the same contexts versus just looping the context. The improvements are nuts from what I can tell. When I need more info that it needs to reach for. I'll instruct it to grab what it needs then activate the skill again.