We're very excited to launch today FluencyLoop! It is an AI-assisted development workflow that ensures the code and your fluency in it are produced together. No more black-box codebases: adaptive teaching, living project principles, and reviewer-ready documentation right inside your git repository.
Let the AI care about you, it feels great!
AI agents can generate a 2,000-line feature in under 10 minutes. It feels like magic doesn't it? But the morning after "vibe coding" a massive feature, reality hits: you just inherited a massive black-box codebase that you don't actually understand.
I’ve felt that exact mix of pure excitement and hidden dread firsthand, which is why I am very proud and excited to share FluencyLoop with the community today. 🚀
We built FluencyLoop because we love the speed of agentic coding, but we refuse to sacrifice human context, control, and the architectural safety of a proper Software. It is an AI-assisted development workflow that sits right on top of Claude Code and Codex to ensure that code and your fluency in it are produced together, or not at all.
Why am I so hyped about this tool? Because it completely flips the paradigm of how we build with AI:
🧠 It teaches you at your skill level: It reads a private local profile to bypass explanations for things you already know, but dives deep into concepts where your knowledge is still forming.
📜 It protects your repo architecture: Building a living project constitution, auditing every single AI modification against local engineering principles.
📁 It saves your reviewers from git-diff hell: Instead of handing your team a massive wall of unreadable, automated file changes, it auto-generates intent-driven decision logs and Mermaid diagrams right beside your code under docs/fluencyloop/.
Seeing the system acting more careful about the developer / architect behind feels really good: try it!
We are officially live on Product Hunt today! If you are tired of dealing with untrusted codebases and want to stay fluent in the code your agent writes, I would love for you to check out our repo, try the plugin, and share your feedback.
Love the idea of a project constitution for AI changes, that part alone could save so many code review arguments. One thing I'd love to see is a quick "explain like I'm five" mode toggle in the diffs, so junior devs and non-engineers on the team can actually follow the architectural reasoning without needing years of context.
@saniye0ike Good idea, I will think about adapting the set of skills for less technical people.
One thing that would really help me is a way to flag specific code regions during review and have the AI explain only those parts instead of regenerating full rationale blocks. That way when a reviewer is stuck on a single confusing function they can get a focused explanation without rereading the whole changeset.
@kamileuyav55094 Thank you for the suggestion. At the moment the knowledge handover happens at the end of each slice design. Discussions on the review can happen on the architecture diagram or the documentation.
Tried it on a side project this week and the project constitution thing genuinely saved me from accepting a refactor that would have broken my auth flow. The adaptive explanations actually meet you where you are instead of either over-explaining or skipping basics.
@kardelenme87576 Thank you for trying it.
The "why this changed" summaries alone would change how my team reviews AI-generated PRs. Spent an afternoon wiring it up and the project constitution concept genuinely clicked once I saw it flagging a sketchy import.
Finally something that stops my codebase from becoming a black box I wrote myself. The project constitution idea alone is worth it.
@tahsin1368376 Thank you for trying it. The constitution is also present in SpecKit but SpecKit can a bit ceremony heavy for personal projects.
Pazi
Really nice work on FluencyLoop. Hope the launch goes brilliantly! 🎉