rule-laravel-shared-domain-resolution-testing-model-decision

Enforce web host/domain and mobile X-App-Domain tenant resolution in tests.

Updated Nov 7, 2025
One-click install
npx skills add https://github.com/belluga/delphi-ai --skill rule-laravel-shared-domain-resolution-testing-model-decision
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rule-laravel-shared-domain-resolution-testing-model-decision
Source: https://github.com/belluga/delphi-ai/tree/main/skills/rule-laravel-shared-domain-resolution-testing-model-decision
Command: npx skills add https://github.com/belluga/delphi-ai --skill rule-laravel-shared-domain-resolution-testing-model-decision

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Separate tenant resolution contexts to prevent cross-context leakage between web host/domain resolution and mobile app-domain routing.

Core Features & Use Cases

  • Enforces web context resolution to use host/domains only.
  • Enforces mobile context resolution to use X-App-Domain and app_domains for tenant resolution.
  • Useful in integration and API tests to validate multi-context tenancy behavior.

Quick Start

Create or update tests to verify that web tenants resolve via host/domains while mobile tenants resolve via X-App-Domain.

Frequently Asked Questions about rule-laravel-shared-domain-resolution-testing-model-decision

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

FAQPage Schema
How do I test Laravel tenant resolution separately for web and mobile domains?

To test Laravel tenant resolution separately, enforce that web tests resolve tenants via host/domains only, while mobile tests set X-App-Domain and app_domains to prevent cross-context leakage between web and mobile contexts.

What is cross-context leakage in multi-tenant Laravel testing?

Cross-context leakage in multi-tenant Laravel testing occurs when web host/domain resolution and mobile app-domain routing interfere. Enforcing distinct tenant resolution contexts prevents web host/domains from affecting mobile X-App-Domain routing.

Do I need X-App-Domain headers for web tenant resolution in Laravel?

No, web tenant resolution in Laravel relies strictly on host/domains only. The X-App-Domain header and app_domains configuration are exclusively required for mobile context tenant routing to ensure proper separation.

How do I write integration tests for multi-context Laravel tenancy behavior?

Writing integration tests for multi-context Laravel tenancy involves validating that API controllers correctly resolve web tenants via host/domains and mobile tenants via X-App-Domain, ensuring strict separation across test suites.

Why does my mobile tenant resolve using the web host domain in Laravel tests?

Mobile tenant resolution incorrectly using web host domains indicates cross-context leakage. Tests must enforce that mobile contexts use X-App-Domain and app_domains for routing, while restricting web contexts to host/domains only to prevent this.