been playing around with ai coding assistants lately to handle the boring stuff like scaffolding components and writing tests. i just stumbled onto
skill. md which seems designed to give these tools more context about ur specific project setup. instead of just asking an ai to fix a bug, u can use this file to help it understand ur exact css architecture or component patterns. it basically acts as a roadmap so the assistant doesn't hallucinate random styles that don't match your existing codebase.
it might actually save us from that endless loop of fixing broken imports having a structured way to communicate project rules to an agent feels like the next logical step in
modern development . it is pretty wild how much faster things move when u stop manually explaining every single dependency to the chat window. does anyone else use custom markdown files to prime their llms, or am i just overcomplicating my workflow?
>the goal is to make ai act like a senior dev who already knows your repomore here:
https://1stwebdesigner.com/what-is-skill-md-and-why-should-web-designers-care/