Skip to content
Omar Abdalla
All work

Case study · 2026

Company Profile Plugin

After shipping the Scientific platform, I distilled the repeatable parts into an open-source Claude Code plugin, so the next bilingual, compliance-heavy build starts at speed.

10
skills
2
review agents
3
commands
MIT
license

The idea.

A one-off production build is worth more if the hard-won patterns survive it. I open-sourced mine (MIT) as a self-hosted Claude Code plugin marketplace.

  • 10 skills
  • 2 review agents
  • 3 commands
  • 1 guardrail hook

Guardrails as code.

The plugin enforces a two-tier invariant system. A non-blocking PreToolUse hook (Python, with a graceful grep fallback and zero dependencies) catches issues as they happen, and an /invariant-check scan sweeps the whole tree.

It flags banned terms, hardcoded hex, physical CSS, and in-memory rate limiting, the mistakes that quietly break a regulated, bilingual build.

Review agents.

Two agents do the reviewing. A compliance-auditor runs KSA/SFDA checks and reports with file:line evidence; an adversarial-reviewer spans correctness, invariants, SEO/accessibility, and security.

Their rules live in a tunable config, so the whole system re-points to a new client without touching code.

Stack.

Claude CodePythonAgentic AIMulti-Agent Workflows

FAQ.

What is the Company Profile Plugin?
The Company Profile Plugin is an open-source (MIT) Claude Code plugin that distills Omar Abdalla's production KSA pharma build into reusable parts: 10 skills, 2 review agents, 3 commands, and 1 guardrail hook, shipped as a self-hosted plugin marketplace.
How does the Company Profile Plugin enforce quality?
It runs a two-tier invariant system: a non-blocking PreToolUse hook (Python, zero dependencies, with a graceful grep fallback) catches issues as they happen, and an /invariant-check command sweeps the whole tree. It flags banned terms, hardcoded hex, physical CSS, and in-memory rate limiting, the mistakes that quietly break a regulated, bilingual build.
What do the plugin's review agents do?
Two agents handle review: a compliance-auditor runs KSA/SFDA checks and reports with file:line evidence, and an adversarial-reviewer spans correctness, invariants, SEO/accessibility, and security. Their rules live in a tunable config, so the system re-points to a new client without touching code.

Let's talk.

Happy to walk through the architecture and the decisions behind it.