Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

tenant-admin-crud

Étoiles0

Forks0

Mis à jour24 mars 2026 à 21:21

Use when building tenant-admin CRUD flows for branches, staff, services, clients, schedules, and other salon-owned operational resources.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

MateoGs013

MateoGs013/SaaS-Peluqueria

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	tenant-admin-crud
description	Use when building tenant-admin CRUD flows for branches, staff, services, clients, schedules, and other salon-owned operational resources.

Tenant Admin CRUD

Use this skill for the internal panel of each salon.

Read first

docs/memory/active-context.md
docs/blueprints/development-roadmap.md
docs/decisions/ADR-0002-multi-tenancy-and-panels.md
docs/engineering/development-best-practices.md

Workflow

Decide whether the record is tenant-owned or branch-owned.
Scope the resource query to the authenticated tenant.
Keep tenant_id off the form unless there is a compelling internal reason.
Set tenant ownership server-side.
Add branch filters and status filters where they help operation.
Add positive and negative tests for panel access and data isolation.

Rules

no unscoped Model::query() for tenant-owned resources
no trusting route parameters alone for ownership
no resource callback with hidden business logic if an action class is clearer
every destructive action should be authorization-aware

Plus depuis ce dépôt

même dépôt

ai-assisted-laravel-workflow

MateoGs013/SaaS-Peluqueria

AI-first Laravel repository workflow for planning, implementing, and documenting work in this project. Use when bootstrapping the repo, setting up agent guidance, or performing changes that should update memory, ADRs, or AI instructions.

2026-03-240

api-v1-contracts

MateoGs013/SaaS-Peluqueria

Use when implementing or reviewing versioned API endpoints, request/response contracts, resources, and integration-facing payloads for this repository.

2026-03-240

booking-domain

MateoGs013/SaaS-Peluqueria

Implement or plan booking, availability, rescheduling, cancellation, and reminder flows in this salon SaaS. Use when touching calendars, time slots, deposits, booking states, or customer appointment journeys.

2026-03-240

commit-discipline

MateoGs013/SaaS-Peluqueria

Use when preparing commits, splitting work into commit boundaries, writing commit messages, or reviewing whether a branch is ready for GitHub PRs in this repository.

2026-03-240

filament-panel-work

MateoGs013/SaaS-Peluqueria

Build or change Filament-based internal panels in this Laravel salon SaaS. Use when working on superadmin dashboards, tenant admin pages, tables, forms, widgets, resources, or internal workflows.

2026-03-240

public-booking-experience

MateoGs013/SaaS-Peluqueria

Use when building the public salon pages, stylist profiles, booking journey, conversion-focused UI, or client-facing scheduling flows.

2026-03-240

name	tenant-admin-crud
description	Use when building tenant-admin CRUD flows for branches, staff, services, clients, schedules, and other salon-owned operational resources.

Tenant Admin CRUD

Use this skill for the internal panel of each salon.

Read first

docs/memory/active-context.md
docs/blueprints/development-roadmap.md
docs/decisions/ADR-0002-multi-tenancy-and-panels.md
docs/engineering/development-best-practices.md

Workflow

Decide whether the record is tenant-owned or branch-owned.
Scope the resource query to the authenticated tenant.
Keep tenant_id off the form unless there is a compelling internal reason.
Set tenant ownership server-side.
Add branch filters and status filters where they help operation.
Add positive and negative tests for panel access and data isolation.

Rules

no unscoped Model::query() for tenant-owned resources
no trusting route parameters alone for ownership
no resource callback with hidden business logic if an action class is clearer
every destructive action should be authorization-aware