The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Hey! I just shared a write-up on something I learned while rebuilding a product with AI agents:)
The main idea is pretty simple:
Don’t put all your product context in one giant agent file.
Keep the main file small, and put the real product knowledge inside structured docs that the AI can navigate when it needs them.
This has helped me a lot when working on a SaaS product with a lot of business logic!
Sharing the full breakdown here:
I'm offering consulting services to set this up! :)
The giant agent file problem is real, I hit context limits constantly before splitting docs by domain. Curious how you decide what counts as core context versus something the agent should look up on demand.
I think core context can be a small product overview, summary of technical architecture doc and repository rules/naming conventions.
Then you include a sort of table of contents where you add the different paths to other important docs that describe features !
What a nice tip! Are you into product development?
Yes! I'mcurrently a lead tech at a stratup and im migrating the old app into the new stack :)
So I'm doing the job of a product owner and also building the whole app!
The table-of-contents-in-the-main-file pattern is the key move here - it keeps the agent's default context small while still giving it a map to go fetch the architecture or naming-convention doc only when the task actually touches that domain.
Yeah! That's right!
I also really like the feature-spec skill I made for the repo. Having AI ask you further questions to get into the edge cases and fill better the documentation files.
keeping the main file small is underrated tbh
This maps to how I think about client documentation too, keep the source of truth thin and let people drill into details only when they need them. Curious if there was any part of the product where the thin main file approach broke down and you had to load more context up front.
Great to hear @Maty Sandoval ! I'm thinking to do a template repo or a sort of framework so others can use it also!
Hmm I don't think so, as the main file always gets updated if there is a new doc added to the repo. So if I add a new document, the main file will add it too, so the ai knows it...
Client documentation is always such a tricky part.. great job!! 🎉
I think the trick is to see it as the app great build from the documentation, so the docs are the start not something to do after :)
This makes a lot of sense. Keeping the main context small and letting the AI pull in the right docs when needed seems way easier to manage as the product grows.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Trending
retrofuturism
Share your favorite designs from the past exploring the distant future. Or your own take on the aesthetic 🚀
halftone
Dots. Texture. Grain. Let's see your designs using the halftone technique.
Midjourney
Creatives are showing off what they're making with Midjourney.
colorgrade
Video editors sound off: How do you enhance the mood of your video in color grading?
Related posts
NOIRA - Music Production Platform
Hardest brief in product design: make someone feel sound through a screen.
You can't play audio on a Dribbble shot. You can't hear a beat in a portfolio scroll. So the entire visual system has to carry the emotional weight of the thing you actually can't show.
The wave logo is clean but I'll say stacked horizontal lines for audio brands is becoming the new "gradient circle for AI startups." It works here because the weight and spacing match the typographic mood. But the concept alone won't differentiate much in 2026.
#WebDesign #MusicTech #ProductDesign #DarkUI #CreativeDirection
great designs..
Today I've created this x.crop hero section, The hero background is created using the Vision Engine and rest of the Layout is created in Framer! 🤍
⬇️ What would you rate this hero out of 10 ?
A solid 9 /10. Incredible work as always brother, keep it up!
😍
I wanted my next framer template's portfolio showcase to have a standout interaction, not another flat slider.
That idea is now the hero: a carousel where every image bends on a cylinder as it moves. Perspective, velocity skew, a touch of chromatic distortion on the...