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

Memberships

Claude Code Pirates

324 members • Free

Leon van Zyl

961 members • Free

1 contribution to Claude Code Pirates
Is this AI workflow philosophy worth pursuing?
Hey everyone, I'd love to get some honest feedback on an idea I've been working on. Over the past few months, I've been developing a framework called AKRS. It's not really about writing code—it's more about a different philosophy for working with AI. The core idea is to split AI usage into three different paths: 1. Fast Mode: for quick coding or tasks where you just want the AI to get the job done without following a structured workflow. 2. Leader Mode: for planning, reasoning, and complex changes. This is where the "brain work" happens. 3. Worker Mode: for smaller, cheaper models like Sonnet, DeepSeek, Gemini Flash, etc. Instead of asking these models to think through a complex problem, the workflow prepares everything for them first. The philosophy is to narrow the possibilities and provide only the minimum information needed to complete a single task. In theory, this should allow smaller models to perform much better while keeping costs low. I'm not trying to prove that this workflow is perfect. What I'm really trying to validate is the philosophy behind it. Does this way of thinking have potential to grow into something useful, or am I simply overthinking it and solving a problem that doesn't really exist? If you're interested, here's the repository: https://github.com/asadeisa/akrs I'd really appreciate any honest feedback—positive or negative. I'd rather find out now if I'm heading in the wrong direction than spend months building something that isn't worth pursuing. Thanks!
1
0
1-1 of 1
Asad Eisa
1
4 points to level up
@asad-eisa-4742
laravel &Vue.js & Nuxt developer from Syria. Passionate about AI, SaaS, and building modern web applications.

Active 8h ago
Joined Jul 29, 2026