A Shariah-compliance pre-screen for app developers, packaged as a Claude Code skill.
There is no halal certification body for software. Islamic finance has mature standards (AAOIFI, IFSB) because regulators require them — but if you're building a game, a social app, a Quran app, or a marketplace for Muslim users, there is no checklist to hand you. Developers rediscover the same pitfalls one fatwa search at a time: the ad network serving gambling ads inside a prayer app, the loot box that is structurally maysir, the analytics SDK quietly shipping mosque locations to a data broker.
This skill encodes those pitfalls — with real fatwa citations, documented cases, and named standards — as a repeatable six-layer audit your AI coding agent runs against your actual codebase.
- ✅ An engineering-side pre-screen: it finds known issues early and turns gray areas into precise questions for a qualified scholar
- ✅ Sourced: claims cite AAOIFI standards, named fatwa bodies (IIFA, AMJA, national dar al-ifta), and specific published fatwas; inferences are labeled as inferences
- ❌ Not a fatwa — it never issues rulings; contested topics go to a divergence register that presents positions without adjudicating
- ❌ Not a certification — no such thing exists for software; the only defensible public claim is a named scholar's review of a named version of your app
| Layer | Question | Typical findings |
|---|---|---|
| L1 Purpose | Does the core product depend on riba / maysir / gharar / prohibited content? | Interest-spread lending, betting mechanics |
| L2 Monetization | How does the money actually flow? | Unblocked ad categories, paid loot boxes, late fees, dark patterns |
| L3 Experience | What behavior does the design cultivate? | Compulsion loops, awrah in creatives, ghibah-shaped feeds |
| L4 Data | Is user data treated as amanah? | Religious-practice data reaching third parties (see: Muslim Pro / X-Mode) |
| L5 Company finances | AAOIFI screening applied to the operator | Interest on float/accounts, purification obligations |
| L6 Supply chain | What do your SDKs and models do? | Ad/analytics SDK behavior, AI issuing religious answers |
Each layer resolves to PASS / FIX / ASK-A-SCHOLAR — and every gray case falls to ASK-A-SCHOLAR, never silently to PASS.
Deep-dive references load on demand for: fintech/investing/crypto · games (loot boxes, tournaments/prize pools, imagery) · social & matrimony apps · e-commerce, food delivery & travel (incl. Hajj-booking fraud) · Quran/prayer/education & AI religious Q&A · health, period trackers & kids apps · data privacy · plus a divergence register for genuinely contested topics (music, tasweer, crypto, matrimony model, jurisdictional differences).
Claude Code — plugin marketplace (recommended):
claudethen inside the session:
/plugin marketplace add kyota8ai/halal-app-check
/plugin install halal-app-check@halal-app-check
Claude Code — manual copy (personal, all projects):
git clone https://github.com/kyota8ai/halal-app-check.git ~/.claude/skills/halal-app-checkOr project-local: clone into .claude/skills/halal-app-check inside your repo.
claude.ai / Claude API: upload or attach this folder as a skill.
Just ask, in a session with your app's code available:
Is this app halal? Run halal-app-check.
Review my monetization plan (rewarded ads + gacha) for Shariah issues.
You get a per-layer report naming actual files/SDKs/screens, plus a list of precise questions to take to a scholar. Sample finding:
L2 Monetization — FIX
Where: app/build.gradle → play-services-ads 23.x; RewardedAdManager.kt
Issue: AdMob sensitive-category blocking not configured — gambling/alcohol/dating
ads can serve. Rewarded video pulls from broader inventory than banners.
Fix: AdMob console → Blocking controls → block Gambling & betting, Alcohol,
Dating; enable Ad review center. (Google states blocking is best-effort.)
ASK-A-SCHOLAR
1. Our free daily spin has no purchase path — no wealth is staked. Named rulings
cover *paid* loot boxes only; is the free variant objectionable?
→ Full worked example: a six-layer audit of a (fictional) prayer app — 6 findings across ads, gacha, dark patterns, analytics SDKs, and an AI "scholar" chat.
This project is a screening aid written by a software developer, not a mufti. It cites scholarly sources but is not itself a religious authority; errors are possible and rulings differ across schools. For anything contested or consequential, consult a qualified scholar — your local institution, or a body that answers individual questions such as AMJA (North America) or ECFR (Europe); the International Islamic Fiqh Academy (OIC) publishes the session resolutions this project cites. Passing this check does not make an app "halal certified."
- halal_audit_scanner — Shariah audit for Web3 smart contracts (complementary; use it for .sol/.rs/.move)
- Awesome-Muslims — curated open-source resources for Muslim developers
- Zoya / Musaffa — Shariah-board-supervised stock screening apps (the bar for finance apps)
Corrections with primary sources (a fatwa link, an AAOIFI clause, a documented case) are especially welcome. Claims without sources — including mine — should be challenged. See CONTRIBUTING.md for the evidence rules; a monthly CI job files link-rot issues that make good first PRs.
MIT