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

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

admin-interface-backend

Étoiles7

Forks0

Mis à jour15 mai 2026 à 12:07

Implementare il backend di una pagina admin Laravel complessa con FormRequest, DTO/filter object, service di query/aggregation, controller thin e route. Trigger quando si crea o refactora un endpoint admin con filtri, KPI, tabelle paginate o export, o quando si tocca un controller in app/Http/Controllers/Api/Admin/ o un servizio in app/Services/Admin/.

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

lopadova

lopadova/AskMyDocs

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	admin-interface-backend
description	Implementare il backend di una pagina admin Laravel complessa con FormRequest, DTO/filter object, service di query/aggregation, controller thin e route. Trigger quando si crea o refactora un endpoint admin con filtri, KPI, tabelle paginate o export, o quando si tocca un controller in app/Http/Controllers/Api/Admin/ o un servizio in app/Services/Admin/.

Admin Interface Backend

Skill per implementare il backend di una pagina admin Laravel complessa.

Obiettivo

Preparare:

Request/validator
DTO o filter object
service di query o aggregation
controller thin
route
eventuale export

Sequenza

definire filtri e vincoli
progettare il contratto JSON o view data
creare service di lettura
aggiungere controller e route
scrivere test del service e feature test minimi

Regole

niente query complesse in controller
struttura di output stabile per il frontend
validazione esplicita per limiti, range date, filtri multipli

Plus depuis ce dépôt

même dépôt

ios-testflight-release

lopadova/AskMyDocs

Build, version-bump, sign and upload the AskMyDocs Desktop Tauri app (desktop/) to TestFlight / App Store Connect. Codifies the exact flow that shipped build 0.1.0 on 2026-06-23 — `tauri ios build --export-method app-store-connect`, automatic distribution signing, the transient export-error retry, and the Xcode Organizer GUI upload. Trigger when the user asks to "send/upload the app to TestFlight", "build the iOS app", "ship a new beta", bump the iOS version/build number, or distribute desktop/ to Apple.

2026-06-247

copilot-pr-review-loop

lopadova/AskMyDocs

After EVERY commit-push-PR cycle, the agent MUST loop on Copilot review + CI status until ALL Copilot comments resolved AND ALL CI checks green. NEVER stop after a single push. Trigger when opening a PR with `gh pr create`, after `gh pr push`, or when user asks to "fix PR" / "address review" / "make CI green". Applies to ALL repos lopadova/* and padosoft/*. The loop is mandatory for current and future sessions and for any developer working on this codebase.

2026-06-227

team-scope-wiring

lopadova/AskMyDocs

How to wire an admin SPA page (or the chat) to the global TEAM (= tenant) switcher in the topbar — every authenticated route lives under /app/{teamHash}/…, the X-Tenant-Id header is automatic via the shared axios client, switching team rewrites the URL hash + clears the TanStack cache + remounts the route outlet, project options must come from tenant-scoped endpoints. Trigger when wiring an admin page to the team scope, when adding a NEW admin page / route / feature folder under frontend/src/features/, when adding a `navigate(...)` call, when touching a project picker / project filter, or when a page shows stale cross-team data after a team switch.

2026-06-177

cross-tenant-isolation

lopadova/AskMyDocs

Every Eloquent query against tenant-aware tables MUST be scoped to the active tenant_id. Use `forTenant($tenantId)` scope (provided by BelongsToTenant trait) or explicit `where('tenant_id', $ctx->current())`. The TenantContext singleton holds the active tenant; never bypass it. Trigger when writing services / scopes / controllers that query tenant-aware models, when reviewing PRs that touch persistence, or when investigating R30 architecture test failures.

2026-06-157

mintlify-doc-authoring

lopadova/AskMyDocs

Author and maintain the AskMyDocs Mintlify documentation site under /docs-site/. Every page is a deep, academic, standalone explainer (motivation → theory → design+Mermaid diagram → data model → ADR rationale → worked example → gotchas) — NOT a condensed README paste. Trigger when adding or changing a capability that ships user-facing behaviour, when editing README feature tables / changelog / roadmap (R45 doc-site parity), when adding a page to /docs-site/, or when editing docs.json navigation.

2026-06-157

compile-repo-canonical

lopadova/AskMyDocs

CONSUMER-SIDE template — use in a consumer repository that posts knowledge to AskMyDocs, NOT when editing AskMyDocs itself. Triggers when the team wants to bootstrap or refresh the ENTIRE canonical knowledge base of a repository in one pass: survey the codebase, plan the typed-document inventory, and emit a full cross-wikilinked kb/ tree (project-index + modules + decisions + standards + integrations + domain-concepts + runbooks + rejected-approaches). Draft only — produces Markdown files under kb/ for human review, never commits and never POSTs. Example triggers: generate the canonical docs for this repo, compile the knowledge base, bootstrap kb/ from the codebase, document the whole project in canonical mode.

2026-06-117

name	admin-interface-backend
description	Implementare il backend di una pagina admin Laravel complessa con FormRequest, DTO/filter object, service di query/aggregation, controller thin e route. Trigger quando si crea o refactora un endpoint admin con filtri, KPI, tabelle paginate o export, o quando si tocca un controller in app/Http/Controllers/Api/Admin/ o un servizio in app/Services/Admin/.

Admin Interface Backend

Skill per implementare il backend di una pagina admin Laravel complessa.

Obiettivo

Preparare:

Request/validator
DTO o filter object
service di query o aggregation
controller thin
route
eventuale export

Sequenza

definire filtri e vincoli
progettare il contratto JSON o view data
creare service di lettura
aggiungere controller e route
scrivere test del service e feature test minimi

Regole

niente query complesse in controller
struttura di output stabile per il frontend
validazione esplicita per limiti, range date, filtri multipli