tams-plugin-developer

Name: tams-plugin-developer
Availability: InStock
Author: tammer

Explain TammerStore plugin development workflows for SaaS and Tenant contexts.

Updated Aug 27, 2026

Search Tags:#php #plugin #laravel #loading #tammerstore #plugin-json

Ready to run

npx skills add https://github.com/tammerofficial/tams --skill tams-plugin-developer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tams-plugin-developer
Source: https://github.com/tammerofficial/tams/tree/main/.cursor/skills/tams-plugin-developer
Command: npx skills add https://github.com/tammerofficial/tams --skill tams-plugin-developer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide provides a structured, repeatable approach for developing TammerStore plugins, detailing the required file layout, loading process, and context considerations for SaaS vs Tenant environments.

Core Features & Use Cases

Plugin structure: defines the standard layout (plugin.json, config, helpers, src, views, routes) to ensure consistency across plugins.
Loading and registration: describes the loading flow via PluginServiceProvider, merging configs, loading helpers, and registering views and autoloading.
Verification and tooling: outlines helper functions to verify active plugins and available plugins per context, with basic validation.

Quick Start

Create a new plugin under plugins/your-plugin with a plugin.json and begin loading it through the PluginServiceProvider.

Frequently Asked Questions about tams-plugin-developer

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

FAQPage Schema

How do I structure a TammerStore plugin with Laravel?▼

A TammerStore plugin structure requires a standard layout including plugin.json, config, helpers, src, views, and routes directories to ensure consistency across plugins. This layout supports proper loading and registration via the PluginServiceProvider.

How does plugin loading and registration work in a Laravel SaaS application?▼

Plugin loading flows through the PluginServiceProvider by merging configurations, loading helpers, registering views, and enabling autoloading. This mechanism ensures plugins are properly integrated and activated within the application's lifecycle.

How do I verify active plugins for different SaaS and Tenant contexts?▼

You verify active and available plugins per context using specific helper functions that provide basic validation. These tools confirm which plugins are loaded and accessible across different SaaS or Tenant environments.

What is the purpose of plugin.json in a PHP plugin workflow?▼

The plugin.json file defines the core metadata and configuration for a TammerStore plugin, serving as the entry point for the loading process. It is required to properly identify and register the plugin within the system.

Can I develop plugins for both SaaS and Tenant environments using this workflow?▼

Yes, this workflow specifically targets developers building plugins for both SaaS and Tenant contexts. It provides end-to-end guidance covering access controls, context considerations, and verification for each environment.