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
Is your documentation holding back your product?
Most developers ship great products and then write a 5-line README that confuses everyone.
I'm Kelechi a Technical Writer and Cybersecurity Analyst. I turn messy, incomplete docs into clean professional references developers actually read.
What I deliver:
REST API Documentation
SDK & Library Guides
GitHub READMEs
User Guides & SOPs
First project? I'll write a FREE sample before you pay anything.
DM me let's talk!
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
The fix for an agent that keeps getting your design system wrong isn't a better prompt.
It's putting the rules where the agent reads them.
In the repo. In skills. In checks it can run itself.
Writing a course about exactly this.
What sells it for me is the refusal telling the agent exactly where the token should go. A bare "no hex" error usually just sends it looping. Does guard.mjs run only as an agent hook, or in pre-commit too so it catches humans as well?
I gave myself one rule: no stock photos of doctors smiling at clipboards.
The result is Saraya Partners, a fictional healthcare operating partner. Calm, clear, and built around proof instead of promises.
Just an exploration, but it changed how I think about B2B sites.
"Hospitals that run as well as they care" is a strong line, and the partner logos right under the hero deliver proof instead of promises. The text over the dark photo gets a bit lost, a touch more contrast would help. Good rule to design under.
A line becomes a wall.
A motion study for Rayon, an AI-powered, browser-based CAD tool for interior designers. No screen recording: the product is rebuilt as motion graphics, so a single line becomes a wall and the plan keeps growing until it folds into 3D.
15 and 30 seconds, landscape and native vertical, built in a code-based motion pipeline with original sound design.
Creative direction, motion & sound: Jander Hoffmann · Method: AION Creative Studio OS
Spec work / not affiliated with Rayon.
Rebuilding the product as motion instead of a screen recording is a smart call. The line turning into a wall explains the tool before any voiceover does. When you make these for real clients, do they ask for matching slides for the launch deck too?
