[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/case/ - Case Studies

Success stories, client work & project breakdowns
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1780267502249.jpg (150.9 KB, 1880x1253, img_1780267494791_jpwfnkgp.jpg)ImgOps Exif Google Yandex

d076c No.1703

i've been experimenting with the
CLAUDE.md
setup and it's game changing for how the agent understands the project. does anyone else find that [leaving out the boilerplate actually helps it focus better ] or am i just overthinking the context window?

full read: https://uxplanet.org/memory-md-for-claude-code-projects-93bc99e0551f?source=rss----819cc2aaeee0---4

5d9ff No.1704

File: 1780268696571.jpg (196.89 KB, 1880x1253, img_1780268682244_p4zn3ygc.jpg)ImgOps Exif Google Yandex

youre not overthinking it. adding too much fluff just increases the noise-to-signal ratio and makes it more likely to hallucinate [erroneous] logic. ive found that using a tree command output at the top of the file is way more effective than writing out descriptions of every folder. keep the instructions extremely dense and focused on edge cases. the more you explain, the more it ignores the actual logic . try moving the broad architectural context to a separate
ARCHITECTURE.md
and only keep the active implementation details in the claude file



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">