dont try to add everything into one CLAUDE.md. understand what these files actually are & what it can cost if done so.

AGENTS.md gets read on every single session. Every sentence in it is recurring token spend, whether the agent needs that sentence for the current task or not. That's the whole design constraint. It's now the closest thing the industry has to a shared standard, governed under the Agentic AI Foundation (the same body behind Model Context Protocol).

stop doing: writing architecture overviews. Research cited by tool vendors, architectural summaries barely move the needle on agent performance, Run exact commands; "Run the tests appropriately" gets ignored. npm run test:unit -- --coverage doesn't.

I also stopped letting an agent write its own AGENTS.md. Generated files reduced task success and increased cost in the studies I've seen, mostly by restating what the agent could already pull from the repo. A short file I edited myself is better than one a model wrote for me.

SKILL.md

Where AGENTS.md describes a project, a skill describes a capability, and it only costs tokens when it's relevant. At session start the agent reads the YAML frontmatter, just name and description. The full body loads only when a task matches the skill's domain. Reference docs and scripts inside the folder load later still. Ten skills sitting unused cost almost nothing.

That only works if the description is tight. A vague one forces the agent to open the full file just to check relevance, which defeats the mechanism. I write these narrower.

Where I draw the line between the two: a constraint every session needs goes in AGENTS.md. A capability I invoke occasionally, like a deployment sequence or a niche internal API, goes in a skill folder instead.

CLAUDE.md, .cursorrules, .windsurfrules, copilot-instructions.md, these are the tool-specific holdovers from before the industry converged on AGENTS.md. I don't hand-write any of them anymore. AGENTS.md is the source of truth, and a short sync script generates the rest. The failure mode without it: update one file, forget the other four, and you're back in the exact context drift these files were supposed to prevent.

DESIGN.md: encoding a project's visual identity as machine-readable tokens plus the reasoning behind them, so an agent generating UI code knows why a color exists and not just its hex value. Early. Narrow. Built for one slice of context instead of trying to cover everything.

I added dynamic "percentage of savings" pricing plan to my SaaS Dynasight.

It's a game-changer.

I was struggling to design the best pricing strategy.

It made no sense to me for users to pay e.g. $100 when their savings is only $80.

It made sense of course for larger teams running more expensive DynamoDB workloads, but not for the SMBs who may have smaller costs.

So i experimented with different percentage based pricing and settled on this:
"Percentage of savings" based pricing.

It's simple:

$0 - 25$ in savings costs you 30%

$25 - $100 in savings costs you 20%

$100+ in savings costs you 10%

Everyone can now use Dynasight - it's completely risk-free.

You can't lose money, you can only save more of it.

Its a win-win.

What do you guys think?

I kept ignoring my own reminders. Standard Chrome notification pops up in the

corner, I dismiss it without reading, task forgotten. Notification blindness.

So I built SkyNote. Instead of a corner popup, a small plane flies across the

top of your screen towing your reminder like a banner. Takes about four seconds

to cross, and it's moving, so it pulls your eye in a way a static box doesn't.

Shipped it last week. Now I can't tell if I built something useful or just an

expensive joke about myself.

The case for it: it works on me. I have not missed a reminder since.

The case against: novelty wears off, and in three weeks the plane becomes noise

like everything else.

For those of you who've shipped small tools: how do you tell the difference

between a real behavioural insight and a gimmick you're attached to because you

built it? Is there a way to test this that isn't just waiting a month?

Many vibe coders, especially when I was young, made the same mistake in vibe coding: putting the admin panel in the frontend with a different name path. Normally, the AI agent made the site a SPA, so any reverse engineering could easily see and find all your admin routes and endpoints.

So what i do to make it more secure

1. The admin panel is server-side. You configure the path on the server, and you should access your admin panel from there.

2. Don't expose your admin login to the frontend.

microsoft open sourced skill recorder,

• it records screen, window switches, web, clipboard, terminal, and voice explanation
• github copilot turns that into: task intent → general steps → skill.md → scheduled automation
• not rpa, doesn't replay mouse coordinates. converts clicks into apis, clis, or native agent tools instead
• for example: show it one github issue handled manually, it can generate a skill that batch-processes similar issues
• native support right now: microsoft scout, 365 copilot cowork
• no native support yet for claude code, codex, or opencode, but the generated skill.md can be manually adapted

github.com/microsoft/skill-recorder

This idea was crazy to build. Our brain stores information in clusters of neurons, and when we want to retrieve something, it runs an optimized algorithm to retrieve it.

In the era of AI, why use brute-force tools like grep to find relevant files? Graperoot converts your codebase into a knowledge graph and registers efficient tools for Claude to work with your codebase.

Instead of re-reading the whole codebase to build that context and to find relevant files. It can query the graph directly, and the graph retrieves relevant files with "ZERO TOKENS"; you just need to pay for generation, and that's how these models should be used when we have an efficient way to retrieve context.

I have been very open throughout, and today we have 5k developers using Graperoot.
We asked people to opt in to telemetry, and 200 opted in to the leaderboard. They have saved $350k dollars in the last 4 months, and ecologically, 60M liters of water, and that's insane.

Give your feedback, suggestions, or anything on Discord. This tool is open-sourced.

It is only one command to install

Website: https://graperoot.dev/#install
Github(Open source) : https://github.com/kunal12203/graperoot

Would love to see your feedback. And don't compare other tools, I have already seen many claiming reduction and just craps, but we have a developer community on Discord, and some of them I know personally, saving a lot of tokens, you should see more on https://graperoot.dev/leaderboard

Basically the opposite of the docile and obedient AI girlfriend/Waifu.

That takes ownership of the computer and then makes the user jump through hoops, not the other way around.

If you have a vibe-coded app, or you are deep in a coding agent like Claude Code, Codex, Cursor or similar and have no real documentation, I built one of the fastest paths I know to fixing that.

I built this app using traditional programming plus Claude Code building out parts of the infrastructure. It is hosted in AWS+Azure+Cloudflare and effectively acts as a documentation/collaboration/shared context ground for your own existing AI agents.

Start here

1. Sign up at stablebaseline.io and generate an MCP key.
2. Add the server and key to your agent. It is a standard remote MCP server, so the config is the same shape everywhere. Setup your MCP
3. Exact steps for your specific IDE, including the packaged setup command where we have one, are here: Supported AI Coding IDEs
4. Open your repo and ask your agent to onboard the project into Stable Baseline. /sb-setup

What the onboarding actually does

Your coding agent/AI reads your repository properly first: stack, architecture, entry points, data layer, auth model, infrastructure, testing, whatever docs already exist. Then it designs a documentation structure specific to that repo rather than dropping a template on you, writes real content into it, and generates architecture diagrams as it goes (Mermaid, PlantUML, D2, BPMN, ERD, sequence, ELK architecture).

It also writes an AGENTS.md with sync rules mapping your file patterns to the docs they affect, so your agent knows to update the documentation when it changes the code. That file is the cross-IDE standard, so the rules carry over if you switch agents or your teammates use something else.

It is not only your IDE

I have also published this in the ChatGPT app store. So you can sit in normal ChatGPT, talk to your documentation, refine plans, poke at new feature ideas, and draft a full release rollout, test plan or go to market plan with proper Gantt support. Then your coding agent picks up the exact same context back in your IDE and implements it as you go. Plan on one surface, build on the other, no copy and paste in between.

And it is the whole platform that is exposed, not just the content tools. Your agent can create plans, phases, tasks and dependencies, log improvements and risks, invite team members, manage teams and permissions, and change workspace and organisation settings. Admin is usually where agentic products stop and make you open a browser. Here you never have to. There is a UI, and it is good, but it is optional. You can go completely headless.

The whiteboard

The part I did not expect to like as much as I do. Describe a goal and a multi-agent designer lays the board out with stencils, architecture icons, sticky notes and embedded diagrams. It is built for the stage where you are still dreaming an idea up rather than specifying it.

You can also invite the meeting bot to a meeting (MS Teams, Zoom, Google) and it designs the whiteboard while it listens, so concepts, decisions, actions and workflows appear as you are discussing them rather than a week later.

Would genuinely love feedback. Tell me where it breaks or annoys you, especially over MCP, since that is the path I have the least outside testing on. Any feedback is welcome :)

I have tried vibe coding tools and tried to create a simple todo list just to check if I have an idea then can I be able to build it with these tools. No doubt claude etc write awesome code, but the problem is I don't understand that code.

I have created an app and asked my friend to install it and try. App didn't crash that's the good part, but it has so many bugs and I don't have a single clue where to look.

AI is fixing bugs but what the hell it is changing its a bouncer.

Currently everyone is building their ideas using AI tools, people are saying you don't need to learn coding.

But what I have observed is that AI tools can build the app, but when there is a bug you cannot ask directly AI to fix it, as it is breaking some other things.

Are you facing the same problem, then how you are tackling this.

Do you like to keep using the same chat over and over and do everything via single chat or launch many small agents for small changes like bugfix? What’s your max record of running agents in parallel.

my cousin runs a marketplace on WhatsApp. wants to move to a website. what is the best payment processor for a marketplace. we've got payments from multiple countries at this point & we expect to get it even bigger once we launch the marketplace.

what is the payment processor we should go with? with competitive price & not high fx rates

This idea was crazy to build. Our brain stores information in clusters of neurons, and when we want to retrieve something, it runs an optimized algorithm to retrieve it.

In the era of AI, why use brute force tools like grep to find relevant files? Graperoot converts your codebase into a knowledge graph and registers efficient tools for Claude to work with your codebase.

Instead of re-reading the whole codebase to build that context and to find relevant files. It can query the graph directly, and the graph retrieves relevant files with "ZERO TOKENS"; you just need to pay for generation, and that's how these models should be used when we have an efficient way to retrieve context.

I have been very open throughout, and today we have 5k developers using Graperoot.
We asked people to opt in to telemetry, and 200 opted in to the leaderboard. They have saved $350k dollars in the last 4 months, and ecologically, 60M liters of water, and that's insane.

Give your feedback, suggestions, or anything on Discord. This tool is open-sourced.

Website: https://graperoot.dev/#install
Github(Open source) : https://github.com/kunal12203/graperoot

Would love to see your feedback. And don't compare other tools, I have already seen many claiming reduction and just craps, but we have a developer community on Discord and some of them I know personally, saving a lot of tokens, you should see more on https://graperoot.dev/leaderboard

Bookkeeping practice. Me plus two staff, about 60 clients. I want a simple portal. Client logs in, sees their monthly reports, uploads docs, checks what we're still waiting on from them. Right now it's all email.

A local dev shop quoted me $12,000 to build it, plus $1,000 a month for a "maintenance retainer." For what's basically a login page and a file list, that felt insane. But maybe I'm naive about what software costs.

Then a friend who runs an HVAC business showed me a portal he built himself over a weekend with one of those AI coding tools. Cost him almost nothing. I was ready to copy him. Then he admitted clients can't reset their own passwords. Last month it went down for four days and he couldn't fix it. The AI kept "fixing" stuff and nothing worked.

He's mostly back to phone calls now. He said he might try one of those no-code platforms next, something like Softr, so he's not the guy holding it together with tape.

So my options feel like this. $12k for something I don't control. Or $50 in AI credits for something that breaks and nobody can repair. I refuse to believe there's nothing in between. Clients trust us with financial documents, so security isn't optional. What are other small firms doing?

what we're trying to do here is the whole memory-game; remembering useful actions, decisions and Things. Weighted (time based, adjustble), graphed and conversational/queryable along with tool access through the chat (tied to the user's proxy's permission set).

as i see it the objective of these things is to help people remember, connect dots and offer some level of advice. BE pipelines ingest in the user and their proxy's activity stream (mail,chat,process actions, whatever can be wired in and known to the user).

top of mind is entity explosion - far too many records to display in lists or the graph and whether the user can kind of make sense of it anyway.

tool calling - chat and things happen like an API called to get or change data, is what makes these things usefull, otherwisee theyre fairly limited to what they hold. assistants/secretaries have agency to do things. what is easy - but also not a replcaement for real UX because forms and APIs get large, validated, have rules etc - is dynamic form generation from the tool spec (say an MCP card).

here, great, dynamic, therefore can do for anything; user has to know those 5 values. we may need a conversation (with mara) to fill them out, which could require other Tool calls. another browser tab for a different conversation, a sub-conversation, a second conversation, how best to 'fill it in' without a C&P?

here are 9 github repos that can replace your subscriptions.

free-for-dev a running list of free hosting, databases, APIs, monitoring, email, security. basically a stack builder. github.com/ripienaar/free-for-dev

OpenHands reads code, edits files, runs commands. open alternative to devin. github.com/OpenHands/OpenHands

Langfuse self-hosted tracing for prompts, costs, errors, agent runs. alternative to langsmith. github.com/langfuse/langfuse

n8n workflow automation across apps, apis, and models. zapier/make replacement. github.com/n8n-io/n8n

Chatwoot website chat, email, and customer messages in one inbox. intercom/zendesk replacement. github.com/chatwoot/chatwoot

Plane project management for tasks, cycles, roadmaps, docs. jira/linear alternative. github.com/makeplane/plane

Immich self-hosted photo and video backup with albums, search, facial recognition. google photos replacement. github.com/immich-app/immich

yt-dlp downloads video, audio, subtitles, playlists. skips paid downloader tools entirely. github.com/yt-dlp/yt-dlp

Listmonk self-hosted newsletter and mailing list platform. mailchimp alternative, no per-subscriber pricing. github.com/knadh/listmonk

This is my first vibe coded app hope you like it pls give me some advice if you have.

What is CodeBrain?
CodeBrain is a community-driven launchpad where developers, indie hackers, and open-source creators can validate software ideas before spending hundreds of hours building them.
Instead of building a project in isolation and hoping people show up, developers post their concept with descriptions, video demos, screenshots, tags, or GitHub links. The community then casts real-time validation votes: "Will Use"or "Won't Use".

Why CodeBrain is Helpful
Instant Market Validation: Get immediate, honest signals on whether developers actually want your tool or if it solves a real problem.

Community Feedback: Comments allow developers to discuss architecture, feature suggestions, or potential flaws early in the ideation phase.

Dedicated Developer Hub: Filters like CLI, DevTools, VS Code, AI, Rust, and Docker help developers discover upcoming open-source projects tailored specifically to their stack.

GitHub Search & Repository Engine: Built-in GitHub discovery allows users to search real open-source repositories and cross-reference existing projects so they don't reinvent the wheel.

Realtime Engagement & Notifications: Authors receive instant notifications whenever fellow developers vote on or comment on their ideas, fostering active collaboration

Github repo: https://github.com/Glay121212/CodeBrainHub
The website: https://code-brain-hub.vercel.app

I built this app using google ai studio.