Activity
Mon
Wed
Fri
Sun
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
What is this?
Less
More
4 contributions to Useful AI • AI For Business
Claude Code 👾 with structure and memory
Minimal Claudeness gives Claude Code what it's missing: memory, structure, and focus. No Python. No Node. No database. Just files. - Installs with one prompt, configures itself - Remembers what you've built (two-tier memory) - Branches per feature, asks before touching Git - Subagents: code reviewer, security auditor, QA engineer - Updates with one command Used daily. Feedback welcome. Link: https://github.com/mathiew82/minimal-claudeness
Claude Code 👾 with structure and memory
0 likes • 10d
@Glen Hutsell Good question. The memory doesn't store ideas, it stores features. Only what's been built. FEATURES.md is a historical record: date, keywords, files. No proposals, no "maybe we'll do this later". If it's in the memory, it exists in the code. If it's not, it doesn't. And it's not every change either. A small tweak (styling, a typo, a single button) isn't considered a feature and doesn't get registered. Only meaningful functionality goes in. Small changes still happen, they just don't need a memory entry. The memory is for what's worth remembering, not for everything that's done. So there's no ambiguity between an established decision and a new idea: new ideas live in the conversation, not in the memory. Only when something is actually implemented does it get registered. The goal is simple: give the agent context about what has been done, not about what has been thought or proposed.
0 likes • 10d
@Glen Hutsell Exactly. That's the part I like most about it. Because every entry is tied to real files, you can always check the memory against the code. That's why ideas don't belong there. An idea has no files and no branch to point to.
A skill to detect conflicts and contradictions in your agent's context
I've built agent-linter, a skill that audits the context your AI agent receives (AGENTS.md, CLAUDE.md, installed skills, referenced docs, MCP configs) and detects: - ⚔️ Conflicts between skills - ❓ Ambiguities - ♻️ Redundancies (with token savings) - 🔗 Broken references - 🧱 Context overload It generates an executive report with a health score, root cause, and priority actions. It doesn't modify anything until you ask it to. The problem it tries to solve: agents usually get contradictory information across documents and skills, which makes them inefficient. I tested it with 5 real frontend skills and it detected 6 conflicts, 3 ambiguities, and ~1,250 recoverable tokens. All caused by a single root cause: no skill declared its priority over the others. Attached is the report it generated. Feedback welcome 🙌 📦 Install: npx skills add https://github.com/mathiew82/skills --skill agent-linter
A skill to detect conflicts and contradictions in your agent's context
1 like • 13d
@Thomas Dvorak Thanks Thomas! Really appreciate that 🫶
Hi there
I'm Pierre, I'm turning 21 in one month and I'm ready to change my life. I challenged myself to marry my girlfirend in the next 2 years so we can start our dream life together. I think it's time to start the serious things now so be ready I won't stop untill I win. here is my setup ^^
Hi there
0 likes • 13d
Matrix setup 🤯
Hi there 👋
Just joined. Excited to learn from you all and share ideas along the way.
2
0
1-4 of 4
Berto Matt
2
14 points to level up
@berto-matt-3373
Me gusta la tecnologia y aprender cosas nuevas

Active 30m ago
Joined Oct 11, 2026
Powered by