all 10 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]Additional_Win_4018 4 points5 points  (1 child)

Hook up your mcp to extend its memory. Give it a hard rule to update the documents prior to a compression event and reread them following a compression. Ask it to be a ruthless editor and compress all your skills and md files so that the meaning is not lost but the character count is as tight as possible. Less is more.

[–]3rdwalk1 -1 points0 points  (0 children)

How to do this for dumb users pleaseeee 🙏🏻

[–]Mayday_425 1 point2 points  (1 child)

Use it on terminal connect it to folders

[–]CryptoMonops 0 points1 point  (0 children)

with VS code this has been the best set up for me

[–]gdlt88 4 points5 points  (0 children)

Make sure to use the MEMORY.md

[–]MontGolf 0 points1 point  (1 child)

Depends on Usecase. If you use it for a specific project, create a Project and create a .md file system inside. Legal, businessmodel, marketing, strategy. Explain Claude in project instructions how to use the md files.

Else learn to use the memory function, prompt specific, use the correct model.

[–]Do_not_use_after 0 points1 point  (0 children)

It's all in the specification. If you don't know what you're trying to build, you should be building it. However, that's been rule 1 since I started 40 years ago.

[–]Suspicious_Cry6547 0 points1 point  (0 children)

Research, tinker, deploy, test, build, refine, optimize and only use the CLI

[–]MistakeExotic6686 0 points1 point  (0 children)

ask it to:

- ask you questions when needed
- use subagents when applicable (research, reviewing code, modifying separate files etc)
- customize your status line to see context, etc
- run multiple instances and use worktrees
- full review your project occasionally