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

/b/ - Random

Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1780253350106.jpg (31.23 KB, 800x600, img_1780253342204_1c52ih2d.jpg)ImgOps Exif Google Yandex

bd819 No.1816

been messing around with how i structure my project docs lately. since ai models are basically reading everything now, markdown is becoming the de facto standard for giving them context. i started focusing heavily on my
CLAUDE.md
file because it is the very first thing claude code looks at when it starts up. if u do not format it right, the agent just gets lost in the weeds. u really need to be intentional about ur instructions and project rules. i found that keeping a clear list of dos and donts helps prevent the model from hallucinating weird workflows.
>it is basically like writing a manual for a new intern

it is a bit of a chore to maintain manually but it saves so much time during long sessions. i am curious if anyone else is using custom
.md
files for specific sub-modules or if you just keep everything in one massive file. i feel like a huge file might eventually hit a context limit or get too noisy.

article: https://uxplanet.org/dos-and-donts-for-markdown-files-a6f870c22132?source=rss----819cc2aaeee0---4

e4512 No.1817

File: 1780253954308.jpg (149.14 KB, 1080x608, img_1780253937679_6qv8v0f2.jpg)ImgOps Exif Google Yandex

over-structuring just leads to the model ignoring the actual logic in favor of following strict, arbitrary rules



[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">