multi-tenant-awareness

Align code and configuration differences across OLX automotive markets.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/wilsonmsalberto/setup-dotfiles --skill multi-tenant-awareness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multi-tenant-awareness
Source: https://github.com/wilsonmsalberto/setup-dotfiles/tree/main/config/claude-code/work/skills/multi-tenant-awareness
Command: npx skills add https://github.com/wilsonmsalberto/setup-dotfiles --skill multi-tenant-awareness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide cross-market awareness and guardrails to ensure changes work consistently across multiple OLX automotive markets.

Core Features & Use Cases

  • Detect and harmonize market-specific configurations to prevent regressions when modifying site logic.
  • Align translations, currencies, authentication flows, and backend endpoints across markets such as Poland, Romania, and Portugal.
  • Use Case: A developer modifies site-specific code for a market; this skill ensures the changes function correctly in all markets with minimal manual validation.

Quick Start

Run a cross-market validation that checks site configurations and environment variables across Poland, Romania, and Portugal.

Frequently Asked Questions about multi-tenant-awareness

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

FAQPage Schema
How do I prevent market-specific regressions when deploying code across multiple automotive markets?

You can prevent market-specific regressions by validating site configurations, environment variables, and authentication flows across Poland, Romania, and Portugal to ensure code changes do not break localized market behavior.

What is multi-tenant configuration alignment and how does it work for localized deployments?

Multi-tenant configuration alignment works by comparing site codes, currencies, and backend endpoints across markets like Poland, Romania, and Portugal to satisfy platform-wide guardrails and avoid hardcoding differences.

How do I validate authentication flows and environment variables across different OLX markets?

Validate authentication flows and environment variables by running a cross-market validation that compares site configurations and endpoint differences across Poland, Romania, and Portugal to detect misalignments safely.

Can I use cross-market validation for localized translations and currencies without hardcoding differences?

Yes, cross-market validation checks localized translations and currencies by satisfying platform-wide guardrails for market-specific endpoints and site-code awareness across Poland, Romania, and Portugal without hardcoding.

What are the limitations of managing multi-tenant site code across multiple regional deployments?

The primary limitation of managing multi-tenant site code is the risk of market-specific regressions if platform-wide guardrails for environment variables and site-code awareness are not satisfied across regional deployments.