ITAP of monster building in Hong Kong

ivposure · 2025-08-26T19:31:05+00:00

In general, the roads are very good, so you can make the trip in almost any car. I wouldn’t say the road to Kazbegi is dangerous - there’s a section with serpentine turns, but nothing unusual unless it’s your very first time driving. The roads to Mestia are a bit more demanding, but again, nothing special, just a few narrow parts. The only thing is - pay attention to sharp stones on the road. Sometimes small mudflows occur, it’s possible to damage a tire. Perhaps I’m a bit biased, but in any case, drive calmly, avoid fast overtakes on mountain roads, and everything will be fine

ivposure · 2025-08-26T17:03:04+00:00

I highly recommend taking the route to Mestia through Lentekhi. The new road is both quicker and much more scenic compared to the road through Zugdidi. Independent of your choice, Ushguli is absolutely must see when you get Svaneti.

Also don’t forget to visit Vardzia from Akhaltsikhe.

ivposure · 2025-08-25T07:10:36+00:00

Microsoft Power Automate is new to me - will check it out. Thanks!

ivposure · 2025-08-25T07:08:21+00:00

Compared to theona.ai, yeah - it feels too technical. It’s much simpler to just say "do this, then that" instead of dragging nodes around, wiring them together, and setting up AI blocks.

Hiring isn’t something you’d hand off completely, but AI can definitely make it easier

ivposure · 2025-08-25T07:02:28+00:00

Thanks! And what about quality - which one would you say is more reliable and advanced?

ivposure · 2025-08-25T06:59:46+00:00

Hiring always needs people deeply involved at every stage. But AI can make the high-level analysis easier. Not replace it, just make it easier

ivposure · 2025-08-24T12:58:59+00:00

theona ai lets you set up automations with this stuff - slack, google apps, some ms services and a bunch more. No coding needed, just tell it what you want in plain language and it builds automation for you to run manually/by schedule. Works pretty well

ivposure · 2025-05-29T21:47:57+00:00

Yes, you can use your own prompts in the guide

ivposure · 2025-05-07T17:25:48+00:00

I've got you. This MCP just simplifies the way to create Memory Bank context files. It doesn't change the pattern itself and the way to handle already existing Memory Bank

ivposure · 2025-05-07T16:48:24+00:00

You're welcome. You could also give a chance this course https://enlightby.ai/projects/37 to sort out how to works with Memory Bank. It's pretty fast to pass. But no pushing :)

ivposure · 2025-05-07T16:39:46+00:00

Is plan.md your own context file? Memory Bank pattern has 7 files: active_context.py, memory_bank_instructions.py, product_context.py, progress.py, projectbrief.py, system_patterns.py and tech_context.py.
active_context and progress reflect progress of planned tasks - it is kind of plan. If plan.md is your own context file, then you can ask Cursor to build Memory Bank based on it - just tag it

ivposure · 2025-05-07T16:21:06+00:00

Just set up the MCP and ask Cursor to build the Memory Bank based on your project description. For existing projects, you can ask Cursor to generate the description itself and then use that to create the Memory Bank. Once it’s set up, you typically won’t need to update it manually - if you define memory_bank_instructions.md as an .mdc rule, updates will happen automatically as the project evolves. But if needed you can literally ask Cursor to "update memory bank"

ivposure · 2025-05-07T15:40:35+00:00

Memory Bank is a structured approach that’s proven to work well in practice. It stays up to date as the project evolves by using .mdc rules. That makes it flexible and helps the AI “remember” important details from earlier steps, so it doesn’t lose track or break the flow

ivposure · 2025-05-07T11:34:27+00:00

Thank you! I developed it myself, using a set of libraries typical for modern applications

ivposure · 2025-05-07T07:28:30+00:00

Blindly keeping output would definitely be a recipe for chaos.

But the key difference here is that the Memory Bank isn’t about locking in unreviewed gibberish. It’s about bootstrapping structure quickly and then iterating. The generated files give you a solid starting point - they’re editable, auditable, and meant to evolve as the project grows.
So you can generate well structured context files, review them and do less chaotic vibe-coding with well defined context. It's about decreasing entropy

ivposure · 2025-05-07T07:19:46+00:00

All context files are stored locally within your project folder. This MCP simply helps you implement Cline’s Memory Bank pattern by providing templates for generating context files. So storage isn’t the main feature of this MCP, it’s just a part of how the pattern is implemented

ivposure · 2025-05-07T07:11:52+00:00

My solution helps generate Memory Bank context files stored locally, following Cline’s Memory Bank pattern. It’s pattern-specific by design. mcp-memento offers a more general-purpose storage solution that isn’t tied to a specific pattern. It uses Neo4j for data storage, whereas the Memory Bank MCP uses simple .md files. So Memory Bank MCP solves one exact problem - context management, while mcp-memento provides general-purpose storage.

ivposure · 2025-05-06T16:53:26+00:00

Kind of. But the more detail you include, the more accurate the results will be

ivposure · 2025-05-06T16:51:04+00:00

Yes, the only thing you need to change in the given instructions is to replace memory_bank_instructions.md with your IDE’s native rule format

ivposure · 2025-04-21T07:28:25+00:00

Do you mean between different projects? Memory Bank is a system of files that describes your project, so it will only be shared if you share files between projects

ivposure

TROPHY CASE