メニュー
Build or modify LGS1920 server-side functionality with Bun and Elysia, including routes, proxies, configuration, file handling, errors, security, and deployment behavior.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/lgs1920/studio --skill lgs-1920-studio-bun-elysia-backendコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Safely prepare, verify, and send emails without requesting, displaying, or transmitting passwords, API keys, tokens, recovery codes, private keys, or other secrets. Use this skill to draft an email, reply to a message, send an attachment, or automate delivery through an authorized mail connector.
CesiumJS camera control - Camera, flyTo, lookAt, setView, ScreenSpaceCameraController, CameraEventAggregator, flight animation. Use when positioning the camera, creating flyTo animations, constraining user navigation, tracking entities, or converting between screen and world coordinates.
Prepare LGS1920 release changelogs, commit history entries, README updates, version validation, and release-ready documentation from implemented changes and repository issues.
| name | lgs-1920-studio-bun-elysia-backend |
| description | Build or modify LGS1920 server-side functionality with Bun and Elysia, including routes, proxies, configuration, file handling, errors, security, and deployment behavior. |
Use for server routes, proxy endpoints, provider access, configuration, or deployment. Inspect servers.json, server entry points, deploy.js, environment handling, and existing request consumers first. The Studio repository owns the deployment orchestrator; the runtime contact-mail implementation lives in the sibling ../backend repository.
Workflow:
Do not add a second backend framework or trust user-provided URLs without validation.
When a change concerns the public contact form, read the backend
docs/CONTACT-API.md and docs/SMTP-DEPLOYMENT.md before editing Studio. Keep the
browser and Studio release free of SMTP credentials, CSRF secrets, and recipient
addresses. The site may contain only the public API URL and an opaque target key.
For backend deployment, the local source of truth is ../backend/.env. The Studio
deployment command uploads that file over the active SSH/SFTP connection to the
configured remote backend shared path, normally shared/backend.env, after
creating the directory with mode 700; it then enforces file mode 600. PM2
sources the remote file and starts or restarts the backend with --update-env.
Never copy the file into dist, a release archive, a Studio .env, or a Git
tracked file, and never log its contents.
Inspect deployment/deploy.yml, deployment/Deployment.js, and
deployment/DeploymentCommands.js when changing this boundary. Test path
calculation, shell quoting, environment upload ordering, and the PM2 command
without performing a real deployment. A real deployment still requires explicit
user authorization.