i-vsd

Reviews provider-mediated software decisions against Islamic value-sensitive design principles and writes structured Markdown reports.

7|3|Updated Sep 23, 2025
One-click install
npx skills add https://github.com/islamu-ngo/Event --skill i-vsd-islamu-ngo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: i-vsd
Source: https://github.com/islamu-ngo/Event/tree/main/.agents/skills/i-vsd
Command: npx skills add https://github.com/islamu-ngo/Event --skill i-vsd-islamu-ngo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams building Islamic or values-driven software lack a structured way to evaluate provider responsibilities—privacy, monetization, moderation, AI behavior, lock-in, governance—without conflating design reasoning with religious rulings. This Skill provides a disciplined review workflow with clear authority boundaries and auditable, persisted reports. ## Core Features & Use Cases - Action-routed reviews: 22 review actions (compliance-check, business-model-review, ai-data-review, moral-diff-review, guided-discovery, and more) mapped to canonical report templates and domain heuristics. - Evidence discipline: Context discovery gates, evidence levels, missing-evidence tracking, and stable finding IDs (IVSD-Fnnn/IVSD-Mnnn) prevent overclaiming and keep reports auditable. - Authority boundaries: Escalates halal/haram, riba, and contested religious-legal questions to qualified scholars instead of issuing fatwa-like conclusions. - Use Case: Before pushing a PR that adds paid subscriptions to a community app, run a moral-diff-review to assess pricing clarity, cancellation fairness, and riba exposure, producing a persisted report under islamic-value-sensitive-design/workstreams/. ## Quick Start Ask the assistant to run an I-VSD compliance-check on this repository's pricing, privacy, and moderation practices and write the report to the default output folder.

Frequently Asked Questions about i-vsd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run an Islamic value-sensitive design review on my software project?▼

Invoke the i-vsd skill with your product context and choose an action such as compliance-check, detailed-audit, or business-model-review. The skill inventories available evidence, asks one material decision question at a time, then writes a structured Markdown report under islamic-value-sensitive-design/.

What review actions does the i-vsd skill support?▼

It supports 22 actions including short-advisory, compliance-check, detailed-audit, business-model-review, architecture-review, ai-data-review, moderation-review, governance-review, incident-postmortem, guided-discovery, and moral-diff-review for pre-PR changeset analysis.

Does i-vsd issue halal or haram rulings on software features?▼

No. The skill explicitly refuses fatwa, Sharia certification, and religious-legal conclusions such as halal/haram or riba determinations. It performs provider-responsibility design reasoning and escalates religious-legal questions to qualified Sunni scholarly authority.

Can I use i-vsd to review code changes before a pull request?▼

Yes. The moral-diff-review action collects the complete outgoing changeset, including unpushed commits, staged and unstaged changes, docs, and configs, then reviews them through I-VSD traceability before push, PR, or CI handoff.

Where does i-vsd store its review reports?▼

Substantive findings are persisted as Markdown files under islamic-value-sensitive-design/, partitioned into governance/, consultations/, and workstreams/ folders using the i-vsd-*.md naming pattern. Menus, refusals, and clarification questions remain conversational and create no files.

What are the limitations of an i-vsd compliance check?▼

Compliance checks use pass/concern/fail/not-reviewed levels and are explicitly not certification. The skill cannot prove a product is ethical, Islamically compliant, or secure; it provides design reasoning and implementation traceability bounded by the evidence actually reviewed.