Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

backend-json

Sterne0

Forks0

Aktualisiert16. Juli 2026 um 17:01

Use when editing PHP controllers, services, JSON persistence, auth, support assistant context, wallet, orders, reviews, media, or audit behavior.

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

getwinharris

getwinharris/auraedu

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

Datei-Explorer

2 Dateien

SKILL.md

readonly

type	skill
name	backend-json
description	Use when editing PHP controllers, services, JSON persistence, auth, support assistant context, wallet, orders, reviews, media, or audit behavior.

Backend JSON

Follow the root AGENTS.md repository contract.
Keep route -> controller -> service -> MySQL-store boundaries via DatabaseService.
MySQL is the primary runtime store. bapXaura db CLI manages the DB (init, sync, query).
JSON files in storage/data/ are used only for one-time seeding via bapXaura db sync. Do not use JsonStoreService in runtime code.
JSON files in storage/data/ are used only for one-time seeding via bapXaura db sync. Do not use JsonStoreService in runtime code.
Blog posts use YAML frontmatter in content/blog/posts/. Media metadata uses storage/media.yaml.
Use DatabaseService, ResourceService, and existing services instead of ad hoc storage writes.
Keep assistant/customer context filtered through AgentContextService or equivalent user-specific filtering.
Implement consultation messaging and WebRTC signaling through authenticated PHP JSON APIs and ConsultationService; do not introduce a persistent WebSocket or CLI service.
When direct MySQL is unavailable, remote writes must use the authenticated, collection-allowlisted DatabaseService mutation protocol. The /remoteDB endpoint is protected by remote_db_password (set via Admin → Integrations or REMOTE_DB_PASSWORD in .env). DatabaseService sends the password automatically in every remote payload. Never expose arbitrary write SQL or secret records through the remote endpoint.
For shared-hosting payment integrations, keep gateway clients as small integrations/ wrappers, source secrets through SecretService (MySQL-backed) or system env vars, and verify signatures server-side before mutating orders or wallet balances.
Validate changed PHP with php -l, then run bapXaura test.
Use bapXaura read blog <slug> / bapXaura write blog [slug] for all blog operations.
Use bapXaura read product <slug> / bapXaura write product [slug] for all product operations.

Mehr aus diesem Repository

gleiches Repository

agent-evals

getwinharris/auraedu

Skill evaluation framework, self-evolving agent loop, multi-agent SDLC orchestration, and tool-use optimization for automated quality gates.

2026-07-170

git

getwinharris/auraedu

Use plain Git for local history, branches, pushes, and Hostinger deployment checkouts.

2026-07-160

admin-ui

getwinharris/auraedu

Use when editing owner/admin pages, CRUD forms, media library, environment editor, permissions, audit log, integrations, or admin navigation.

2026-07-160

bapxaura-cli

getwinharris/auraedu

Use bapXaura CLI for ALL file/content/db operations. Never use raw shell/edit/write/find/grep tools directly.

2026-07-160

deployment

getwinharris/auraedu

Use when editing Hostinger deployment, Git auto-deploy, environment, permissions, cron, or production setup documentation.

2026-07-160

docs

getwinharris/auraedu

Use when editing README, docs, project-map docs, or agent-facing instructions.

2026-07-160

Backend JSON

Follow the root AGENTS.md repository contract.

Keep route -> controller -> service -> MySQL-store boundaries via DatabaseService.

MySQL is the primary runtime store. bapXaura db CLI manages the DB (init, sync, query).

JSON files in storage/data/ are used only for one-time seeding via bapXaura db sync. Do not use JsonStoreService in runtime code.

Blog posts use YAML frontmatter in content/blog/posts/. Media metadata uses storage/media.yaml.

Use DatabaseService, ResourceService, and existing services instead of ad hoc storage writes.

Keep assistant/customer context filtered through AgentContextService or equivalent user-specific filtering.

Implement consultation messaging and WebRTC signaling through authenticated PHP JSON APIs and ConsultationService; do not introduce a persistent WebSocket or CLI service.

When direct MySQL is unavailable, remote writes must use the authenticated, collection-allowlisted DatabaseService mutation protocol. The /remoteDB endpoint is protected by remote_db_password (set via Admin → Integrations or REMOTE_DB_PASSWORD in .env). DatabaseService sends the password automatically in every remote payload. Never expose arbitrary write SQL or secret records through the remote endpoint.

For shared-hosting payment integrations, keep gateway clients as small integrations/ wrappers, source secrets through SecretService (MySQL-backed) or system env vars, and verify signatures server-side before mutating orders or wallet balances.

Validate changed PHP with php -l, then run bapXaura test.

Use bapXaura read blog <slug> / bapXaura write blog [slug] for all blog operations.

Use bapXaura read product <slug> / bapXaura write product [slug] for all product operations.