Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

api-v1-contracts

Sterne0

Forks0

Aktualisiert24. März 2026 um 21:21

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

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

MateoGs013

MateoGs013/SaaS-Peluqueria

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

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

API v1 Contracts

Use this skill when the output must be consumed by something other than the current panel page.

Read first

docs/blueprints/development-roadmap.md
docs/engineering/development-best-practices.md
docs/decisions/ADR-0001-laravel-architecture.md
docs/decisions/ADR-0002-multi-tenancy-and-panels.md

Workflow

Put routes under api/v1.
Define validation in Form Requests.
Define output contracts in API Resources when the shape matters.
Resolve tenant context server-side.
Add tests for:
- expected payload shape
- auth or public access behavior
- cross-tenant denial when applicable

Rules

prefer additive changes to response payloads
keep naming stable and explicit
avoid shipping panel-only assumptions into integration contracts
document breaking behavior with an ADR or explicit note if it cannot be avoided

Mehr aus diesem Repository

gleiches Repository

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

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

superadmin-tenant-onboarding

MateoGs013/SaaS-Peluqueria

Use when implementing or changing superadmin flows for tenant creation, owner assignment, tenant lifecycle, status changes, and initial customer onboarding.

2026-03-240

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

API v1 Contracts

Use this skill when the output must be consumed by something other than the current panel page.

Read first

docs/blueprints/development-roadmap.md
docs/engineering/development-best-practices.md
docs/decisions/ADR-0001-laravel-architecture.md
docs/decisions/ADR-0002-multi-tenancy-and-panels.md

Workflow

Put routes under api/v1.
Define validation in Form Requests.
Define output contracts in API Resources when the shape matters.
Resolve tenant context server-side.
Add tests for:
- expected payload shape
- auth or public access behavior
- cross-tenant denial when applicable

Rules

prefer additive changes to response payloads
keep naming stable and explicit
avoid shipping panel-only assumptions into integration contracts
document breaking behavior with an ADR or explicit note if it cannot be avoided