tams-architecture-expert

Configure landlord and tenant contexts with subdomain routing for multi-tenant TammerStore deployments.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/tammerofficial/tams --skill tams-architecture-expert
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tams-architecture-expert
Source: https://github.com/tammerofficial/tams/tree/main/.cursor/skills/tams-architecture-expert
Command: npx skills add https://github.com/tammerofficial/tams --skill tams-architecture-expert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designing and maintaining a scalable multi-tenant TammerStore architecture with centralized landlord control and tenant isolation, including database separation and domain-based routing.

Core Features & Use Cases

  • Central landlord and per-tenant databases coordinated with Stancl Tenancy.
  • Subdomain-based tenant routing, context switching (Landlord vs Tenant), and middleware-driven tenancy initialization.
  • Helper patterns like isTenant() and getAdminPrefix() to guard roles and admin paths.
  • Use Case: Deploy a new store with isolated data, shared governance, and tenant-specific admin panel routing.

Quick Start

Configure and switch between Landlord and Tenant contexts in a TammerStore deployment to validate subdomain-based routing.

Frequently Asked Questions about tams-architecture-expert

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

FAQPage Schema
How do I configure multi-tenancy architecture with landlord and tenant database separation in Laravel?

Subdomain-based tenant routing works by configuring middleware to initialize tenancy initialization and perform context switching between landlord and tenant environments. The routing mechanism identifies tenants via subdomain access, automatically switching application context to route requests to the correct isolated tenant database.

Can I use Stancl Tenancy to deploy a new store with isolated data and tenant-specific admin panel routing?

Stancl Tenancy supports deploying new stores with isolated data, shared governance, and tenant-specific admin panel routing. The deployment utilizes helper patterns like isTenant() and getAdminPrefix() to guard roles and protect admin paths within the multi-tenant architecture.

How do I switch between landlord and tenant contexts to validate subdomain routing?

Switching between landlord and tenant contexts requires configuring context parameters within the TammerStore deployment to validate subdomain-based routing. This configuration ensures correct middleware-driven tenancy initialization, allowing proper domain routing and database separation during architecture planning and debugging workflows.

What is the best way to guard roles and admin paths in a multi-tenant Laravel application?

Guarding roles and admin paths in a multi-tenant Laravel application is best achieved using helper patterns like isTenant() and getAdminPrefix(). These helpers secure tenant-specific admin panel routing, ensuring middleware correctly restricts access based on landlord versus tenant context.