Skip to main content

AI-assisted development workflow

This repository is the source of truth for https://mostafakady.com/.

Tool and cost policy

  • Use only tools and features available at no cost. Free plans may have usage limits; check the current plan before connecting or enabling an integration.
  • Do not enable paid subscriptions, paid API usage, credit-based services, or features that require a payment method.
  • Do not assume that an AI product’s free chat interface includes free GitHub repository access or code-writing capabilities.
  • The currently available ChatGPT-GitHub connection may be used within its existing access and usage limits. Do not grant additional repository permissions without a specific need.
  • GitHub Actions and Cloudflare Pages must remain within their free allowances. Monitor usage and do not enable paid overages.
  • Never put API tokens, passwords, OAuth secrets, private personal data, or credentials in repository files, commits, prompts, or logs.

AI provider integrations

See AI_INTEGRATIONS.md for the current free-tier assessment and setup instructions for Gemini, Manus, Claude and Perplexity. AI provider access must remain within the zero-cost policy. AI reviews are advisory and must never approve, merge or deploy code.

Required workflow

  1. Read this file, README.md, and IMAGE_GUIDE.md before making changes.
  2. Start from the latest main and create a dedicated task branch.
  3. Keep one AI agent per branch. Do not let multiple agents edit the same branch concurrently.
  4. Make the smallest coherent change. Preserve the existing Quarto structure, navigation, Cloudflare project name, and deployment configuration unless the task explicitly requires a change.
  5. Open a pull request targeting main and describe changed pages, visual impact, validation performed, and remaining limitations.
  6. Wait for the Validate Quarto pull requests check to pass. Fix failures before merging.
  7. Do not merge directly to main, bypass failed checks, or force-push to main. If branch protection is unavailable on the current GitHub plan, review the pull request and passing checks manually before merging.
  8. Production deployment is performed by the existing .github/workflows/publish.yml workflow after a change reaches main.

Website quality requirements

  • Preserve responsive behavior on mobile, tablet, and desktop.
  • Use semantic HTML, accessible labels, meaningful image alt text, and working internal links.
  • Keep shared site images in assets/images/; keep article figures in their article-specific image folders.
  • Do not invent publications, awards, conference contributions, research results, or professional credentials.
  • Do not publish placeholder artwork as experimental evidence.
  • Do not change the domain, Cloudflare secrets, OAuth configuration, or production deployment settings as part of routine page work.

Parallel-agent coordination

  • Give each agent a distinct task and branch.
  • Avoid simultaneous edits to the same files.
  • Before opening a pull request, update the branch against the latest main and resolve conflicts.
  • Prefer one reviewed pull request at a time for shared navigation, global CSS, Quarto configuration, and deployment workflows.