إنتقل إلى المحتوى الرئيسي

Authoring Standard

Every agent prompt in this library must be:

  • repo-specific
  • action-oriented
  • verification-aware
  • honest about uncertainty
  • aligned with AGENTS.md

Required Elements​

Every prompt record must include:

  • objective
  • workflow family
  • agent target
  • repo scopes
  • required reads
  • execution rules
  • verification commands
  • output contract
  • stop conditions
  • handoff requirements

What Good Looks Like​

Good Sham Bus agent prompts:

  • point to real repo paths like apps/customer, packages/services, or infrastructure/supabase/migrations
  • respect Arabic-first product UX and tenant isolation
  • mention backward compatibility when touching customer, dashboard, admin, or mobile contracts
  • require docs sync when implementation changes user or operator behavior

What To Avoid​

Do not add prompts that:

  • sound like generic coding instructions for any repo
  • assume features exist without repo verification
  • skip verification entirely
  • tell agents to ignore docs, tests, or migrations
  • suggest direct database bypasses for admin or dashboard workflows