一键在 Manus 中运行任何 Skill

backend-json

星标2

分支0

更新时间2026年7月16日 02:18

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

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

getwinharris

getwinharris/bapXphp

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Backend JSON

Follow the root AGENTS.md repository contract.
Keep route -> controller -> service -> MySQL-store boundaries via DatabaseService.
MySQL is the primary runtime store. bapXphp db CLI manages the DB (init, sync, query).
JSON files in storage/data/ are used only for one-time seeding via bapXphp db sync. Do not use JsonStoreService in runtime code.
JSON files in storage/data/ are used only for one-time seeding via bapXphp 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 bapXphp test.
Use bapXphp read blog <slug> / bapXphp write blog [slug] for all blog operations.
Use bapXphp read product <slug> / bapXphp write product [slug] for all product operations.

同仓库更多 Skills

同仓库

frontend-php

getwinharris/bapXphp

Use when editing public, account, shop, astrologer, temple, cart, checkout, contact, or support templates.

2026-07-162

admin-ui

getwinharris/bapXphp

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

2026-07-162

bapxphp-cli

getwinharris/bapXphp

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

2026-07-162

deployment

getwinharris/bapXphp

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

2026-07-162

git

getwinharris/bapXphp

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

2026-07-162

subagent-orchestration

getwinharris/bapXphp

Use when designing, implementing, or debugging sub-agent handoff workflows, model routing, telemetry, or admin-panel agent wiring.

2026-07-162

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. bapXphp db CLI manages the DB (init, sync, query).
JSON files in storage/data/ are used only for one-time seeding via bapXphp db sync. Do not use JsonStoreService in runtime code.
JSON files in storage/data/ are used only for one-time seeding via bapXphp 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 bapXphp test.
Use bapXphp read blog <slug> / bapXphp write blog [slug] for all blog operations.
Use bapXphp read product <slug> / bapXphp write product [slug] for all product operations.