Not my name, not a CV, not a list of my sites. Six words containing a GitHub handle, typed into an empty account. It came back with seven live subdomains, more than thirty repositories, two certification badges, a Docker Hub namespace and a tutorial on somebody else's platform, every claim graded against an independent source. Twice, a day apart, for $21.02.
This document defines the exact rules for writing project cards in data/projects.yaml for projects.ibtisam-iq.com. Every rule was extracted from real mistakes caught and corrected during the authoring sessions. If an LLM is reading this, follow every rule exactly.
The YAML file is the single source of truth. A push to data/projects.yaml triggers node scripts/generate-projects.js, which auto-generates src/data/projects.ts. The generated TypeScript file must never be edited directly.
Writing clear, professional content is just as critical as writing immutable infrastructure code. Whether I am drafting a runbook, an architectural design document, or a professional summary, I have defined a strict LLM persona to ensure consistency.
Whenever I use AI to assist with writing, I provide it with a link to this exact reference page. This ensures the output reflects my actual engineering philosophy, experience level, and writing style. It avoids the arrogance of a "10-year Principal Architect," completely bans "robotic AI speak," and maintains strict production-grade standards.