ワンクリックでManusで任意のスキルを実行

cf-guardrails

スター0

フォーク0

更新日2026年7月16日 14:53

Check Cloudflare Workers Free plan guardrails for scare-the-spire. Use when adding or changing features, Workers, OpenNext runtime behavior, patch Worker behavior, routing, build output, static assets, server data loading, API routes, SEO, sitemaps, canonical URLs, internal links, or any implementation that could affect Cloudflare CPU time, memory, bundle size, subrequests, crawl volume, request volume, or static-first delivery.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

flavono123

flavono123/scare-the-spire

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

cf-guardrails

Keep scare-the-spire viable on Cloudflare Workers Free. Apply this skill before and after feature/runtime work, then use the focused project skill for the domain being changed.

Required Checks

Prefer static generation, precomputed JSON, static assets, and cacheable responses. Keep Workers thin.
Avoid request-time SSR, markdown rendering, large JSON parsing, full-data joins, search index construction, image processing, or route fan-out fetches.
Treat these Workers Free constraints as design limits unless the user explicitly accepts a paid-plan target:
- 10 ms CPU time per HTTP request
- 128 MB memory per isolate
- 3 MiB gzip Worker bundle size
- 50 subrequests per invocation
- 100,000 requests per day
Treat exceededResources, Error 1102, exceeded CPU/memory, and likely 503 behavior as functional failures, not ops-only concerns.
Treat sitemap, canonical URL, generateStaticParams, internal-link, prefetch, and crawl-surface changes as runtime changes. A route becoming discoverable can expose cold OpenNext work even when no Worker file changed.
For crawlable SSG routes, verify that the production request resolves to a static asset path. Do not infer static delivery only from successful Next.js generation or a 200 response.
Check current Cloudflare docs before relying on numeric quotas, billing assumptions, or paid-only products.

Project Shape

Main Worker: @opennextjs/cloudflare, with static asset dispatch before OpenNext fallback.
Prefixless Korean and /en service-locale Compendium detail HTML/RSC must be copied to _cf_static_pages and served before OpenNext. Game-only locale detail copies are excluded to stay below the Workers Free asset-count limit.
Patch Worker: separate static Worker. Patch HTML, CSS, fonts, images, and provisional /_patches/* assets must be generated ahead of time.
Do not move /patches* back into the main OpenNext runtime as the primary Cloudflare production path.
Future custom-domain route dispatch is documented in docs/CLOUDFLARE_CUSTOM_DOMAIN_ROUTING.md.

Verification Hooks

For runtime/config changes, run the Cloudflare checks from $qa, including pnpm cf:assets, pnpm cf:preview, and Wrangler dry-run bundle/binding inspection.
Smoke both HTML and RSC requests for representative Korean and English Compendium details. Require x-cf-static-page: compendium; a plain 200 is insufficient because OpenNext fallback can also return one.
For patch Worker changes, run pnpm patch:build, pnpm patch:test, and preview/deploy checks from $slseoun-patch or $qa.
For feature work, record the expected request-time cost and why it remains static, cached, or bounded to a small constant.

このリポジトリの他の Skills

同じリポジトリ

supabase-migrations

flavono123/scare-the-spire

Plan and apply production-safe scare-the-spire Supabase schema changes with the Supabase CLI, including cross-deployment compatibility and expand/contract rollouts. Use when creating, reviewing, applying, auditing, or repairing database migrations, Supabase SQL files, RLS policies, RPCs, tables, columns, indexes, or any feature that changes the remote Supabase schema or database response contract.

2026-07-260

create-toybox-service

flavono123/scare-the-spire

Choose and implement game-backed identities for new scare-the-spire Toy Box services. Use when the user asks to create, build, or add a Toy Box service, or asks for recommendations for any combination of its title, gameLocale page subtitle, token asset, and background art. Accept complete, partial, or absent identity inputs; verify provided values and resolve missing ones from the codebase, extracted game data and assets, PCK, or DLL without guessing.

2026-07-260

feature-implementation

flavono123/scare-the-spire

Implement or change scare-the-spire service features with Cloudflare Free/static-first constraints and Slay the Spire 2 game-first product design. Use for new features, existing feature changes, new service surfaces, UI/workflow additions, data-backed interactions, or service concepts that must feel native to STS2.

2026-07-240

flavono123/scare-the-spire

Integrated repository QA coordinator for scare-the-spire. Use when the user invokes $qa or asks for implementation-scoped QA, final verification, regression checks, or "QA this change"; always verifies docs/I18N.md policy and delegates to project QA skills such as mobile-viewport-qa, animation-playback-qa, and history-course-qa when the touched implementation scope requires them.

2026-07-160

byrdispatch-writer

flavono123/scare-the-spire

Format, create, or update byrdispatch / 섀소식 service-update posts and notices for scare-the-spire from rough user notes. Use when the user asks to write, draft, publish, add, or normalize byrdispatch / 섀소식 entries, especially markdown files under data/byrdispatch/YYYY-MM-DD.md, service notices, service update changelogs, deployment-date updates, service-link sections, rich game-resource references, token status badges, or optional screenshots/videos for service announcements.

2026-07-160

monster-intent-graph

flavono123/scare-the-spire

Extract, verify, mock up, implement, or revise Slay the Spire 2 monster intent FSM graphs and phase layouts. Use when changing monster move-pattern extraction, intent graph routing, start nodes, random or conditional transitions, reversible phases, progressive boss phases, Graphviz mockups, or representative intent-graph QA in scare-the-spire.

2026-07-160

name

cf-guardrails

description

cf-guardrails

Keep scare-the-spire viable on Cloudflare Workers Free. Apply this skill before and after feature/runtime work, then use the focused project skill for the domain being changed.

Required Checks

Prefer static generation, precomputed JSON, static assets, and cacheable responses. Keep Workers thin.
Avoid request-time SSR, markdown rendering, large JSON parsing, full-data joins, search index construction, image processing, or route fan-out fetches.
Treat these Workers Free constraints as design limits unless the user explicitly accepts a paid-plan target:
- 10 ms CPU time per HTTP request
- 128 MB memory per isolate
- 3 MiB gzip Worker bundle size
- 50 subrequests per invocation
- 100,000 requests per day
Treat exceededResources, Error 1102, exceeded CPU/memory, and likely 503 behavior as functional failures, not ops-only concerns.
Treat sitemap, canonical URL, generateStaticParams, internal-link, prefetch, and crawl-surface changes as runtime changes. A route becoming discoverable can expose cold OpenNext work even when no Worker file changed.
For crawlable SSG routes, verify that the production request resolves to a static asset path. Do not infer static delivery only from successful Next.js generation or a 200 response.
Check current Cloudflare docs before relying on numeric quotas, billing assumptions, or paid-only products.

Project Shape

Main Worker: @opennextjs/cloudflare, with static asset dispatch before OpenNext fallback.
Prefixless Korean and /en service-locale Compendium detail HTML/RSC must be copied to _cf_static_pages and served before OpenNext. Game-only locale detail copies are excluded to stay below the Workers Free asset-count limit.
Patch Worker: separate static Worker. Patch HTML, CSS, fonts, images, and provisional /_patches/* assets must be generated ahead of time.
Do not move /patches* back into the main OpenNext runtime as the primary Cloudflare production path.
Future custom-domain route dispatch is documented in docs/CLOUDFLARE_CUSTOM_DOMAIN_ROUTING.md.

Verification Hooks

For runtime/config changes, run the Cloudflare checks from $qa, including pnpm cf:assets, pnpm cf:preview, and Wrangler dry-run bundle/binding inspection.
Smoke both HTML and RSC requests for representative Korean and English Compendium details. Require x-cf-static-page: compendium; a plain 200 is insufficient because OpenNext fallback can also return one.
For patch Worker changes, run pnpm patch:build, pnpm patch:test, and preview/deploy checks from $slseoun-patch or $qa.
For feature work, record the expected request-time cost and why it remains static, cached, or bounded to a small constant.