원클릭으로 Manus에서 모든 스킬 실행

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 저장소 열기 Creator 저장소 보기

다운로드

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

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.

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.

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.

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.