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
Related posts
Post
Luxury Sound — Premium Headphones Landing Page 🎧✨
A premium landing page concept for a luxury audio brand, built around a bold headphone design and a refined visual experience
The design combines warm neutral tones, glowing details, oversized product visuals, and minimal typography to create a futuristic yet elegant feel
Special attention was given to:
• Product-first composition
• Premium visual direction
• Feature highlights
• Lifestyle imagery
• Clear CTA placement
• Responsive mobile experience
The result is a clean, immersive product experience that makes the headphones feel like more than tech — they become part of the lifestyle 🔥
The amber glow on the headphones against that warm beige is lovely. How does the mobile menu handle the product image?
I’ve spent years designing for other brands. Now I’m building mine. TACT.
HELLO GEN Z 👋🏻
I’ve spent years designing for other brands.
Now I’m building mine. TACT.
🫱🏻🫲🏽 Wish me luck on my first business!
Really excited to finally build something of my own.
More coming soon. 🖤
Top notch
Designed this interactive 3d dashboard with Opus 5.5 for an industrial company's vehicle and material tracking dashboard
A full 3D simulation of the plant, every truck tracked from gate to dock
Both modes are pixel precise. Which one you like?
4 voted
40%
6 voted
60%
10 votes
Closed
Voted Dark. On a dashboard watching trucks move from gate to dock all day, dark is easier on the eyes, and the 3D bars and route lines glow against it. Light is clean, but dark makes the live movement the focus.