php-json-backend

星标0

分支0

更新时间2026年7月16日 17:01

Use this skill set when contributing to this PHP/JSON agent-ready monorepo.

安装

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

来源

getwinharris

getwinharris/auraedu

下载

PHP JSON Backend

Read the root AGENTS.md repository contract first.
Reproduce or inspect the behavior and pinpoint its owning map/source path before selecting or creating the implementation issue.
Keep route -> controller -> service -> MySQL-store boundaries via DatabaseService.
Remote MySQL is the only runtime store. JSON files in storage/data/ are import fixtures only and never a runtime fallback.
Use storage/schema/collections.php before changing collection shape, admin fields, media fields, seed data, or agent-visible context.
Use docs/systematic-map.mmd as the single wiring map. Regenerate it with php cli/generate-project-map.php and validate with php cli/validate-project-map.php.
For documentation or root instruction changes, also consult docs/map.mmd and map.mmd (root); regenerate with bapXaura update.
Traverse the affected map path into primary sources and verify its route, controller, service, schema, storage, page, and navigation contracts. Do not create a parallel file from a map gap without first searching the repo and classifying the gap.
Extend existing controllers, services, views, storage files, and tools when they already cover the use case.
Do not add React, CDN React, a SPA fallback, or parallel project-map artifacts unless the user explicitly requests a separate migration.

同仓库更多 Skills

同仓库

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

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

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

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

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

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

type	skill
name	php-json-backend
description	Use this skill set when contributing to this PHP/JSON agent-ready monorepo.

Read the root AGENTS.md repository contract first.
Reproduce or inspect the behavior and pinpoint its owning map/source path before selecting or creating the implementation issue.
Keep route -> controller -> service -> MySQL-store boundaries via DatabaseService.
Remote MySQL is the only runtime store. JSON files in storage/data/ are import fixtures only and never a runtime fallback.
Use storage/schema/collections.php before changing collection shape, admin fields, media fields, seed data, or agent-visible context.
Use docs/systematic-map.mmd as the single wiring map. Regenerate it with php cli/generate-project-map.php and validate with php cli/validate-project-map.php.
For documentation or root instruction changes, also consult docs/map.mmd and map.mmd (root); regenerate with bapXaura update.
Traverse the affected map path into primary sources and verify its route, controller, service, schema, storage, page, and navigation contracts. Do not create a parallel file from a map gap without first searching the repo and classifying the gap.
Extend existing controllers, services, views, storage files, and tools when they already cover the use case.
Do not add React, CDN React, a SPA fallback, or parallel project-map artifacts unless the user explicitly requests a separate migration.