@etus/bhono-app 0.1.1

package/templates/base/.claude/skills/wrangler/resources/commands/delete.md

@@ -0,0 +1,27 @@
+# `delete`
+
+Delete your Worker and all associated Cloudflare developer platform resources.
+
+```txt
+wrangler delete [<SCRIPT>] [OPTIONS]
+```
+
+- `SCRIPT` string
+  - The path to an entry point for your Worker. Only required if your [Wrangler configuration file](https://developers.cloudflare.com/workers/wrangler/configuration/) does not include a `main` key (for example, `main = "index.js"`).
+- `--name` string optional
+  - Name of the Worker.
+- `--env` string optional
+  - Perform on a specific environment.
+- `--dry-run` boolean (default: false) optional
+  - Do not actually delete the Worker. This is useful for testing the output of `wrangler delete`.
+
+The following global flags work on every command:
+
+- `--help` boolean
+  - Show help.
+- `--config` string (not supported by Pages)
+  - Path to your [Wrangler configuration file](https://developers.cloudflare.com/workers/wrangler/configuration/).
+- `--cwd` string
+  - Run as if Wrangler was started in the specified directory instead of the current working directory.
+
+

package/templates/base/.claude/skills/wrangler/resources/commands/deploy.md

@@ -0,0 +1,139 @@
+# `deploy`
+
+Deploy your Worker to Cloudflare.
+
+```txt
+wrangler deploy [<PATH>] [OPTIONS]
+```
+
+> **Note:** None of the options for this command are required. Also, many can be set in your Wrangler file. Refer to the [Wrangler configuration](https://developers.cloudflare.com/workers/wrangler/configuration/) documentation for more information.
+
+- `PATH` string
+
+  - A path specific what needs to be deployed, this can either be:
+
+    - The path to an entry point for your Worker.
+
+      - Only required if your [Wrangler configuration file](https://developers.cloudflare.com/workers/wrangler/configuration/) does not include a `main` key (for example, `main = "index.js"`).
+
+    - Or the path to an assets directory for the deployment of a static site.
+
+      - Visit [assets](https://developers.cloudflare.com/workers/static-assets/) for more information.
+      - This overrides the eventual `assets` configuration in your [Wrangler configuration file](https://developers.cloudflare.com/workers/wrangler/configuration/).
+      - This is equivalent to the `--assets` option listed below.
+      - Note: this option currently only works only in interactive mode (so not in CI systems).
+
+- `--name` string optional
+
+  - Name of the Worker.
+
+- `--no-bundle` boolean (default: false) optional
+
+  - Skip Wrangler's build steps. Particularly useful when using custom builds. Refer to [Bundling](https://developers.cloudflare.com/workers/wrangler/bundling/) for more information.
+
+- `--env` string optional
+
+  - Perform on a specific environment.
+
+  > **Note:** If you're using the [Cloudflare Vite plugin](https://developers.cloudflare.com/workers/vite-plugin/), you select the environment at dev or build time via the `CLOUDFLARE_ENV` environment variable rather than the `--env` flag. Otherwise, environments are defined in your Worker config file as usual. For more detail on using environments with the Cloudflare Vite plugin, refer to the [plugin documentation](https://developers.cloudflare.com/workers/vite-plugin/reference/cloudflare-environments/).
+
+- `--outdir` string optional
+
+  - Path to directory where Wrangler will write the bundled Worker files.
+
+- `--compatibility-date` string optional
+
+  - A date in the form yyyy-mm-dd, which will be used to determine which version of the Workers runtime is used.
+
+- `--compatibility-flags`, `--compatibility-flag` string[] optional
+
+  - Flags to use for compatibility checks.
+
+- `--latest` boolean (default: true) optional
+
+  - Use the latest version of the Workers runtime.
+
+- `--assets` string optional (beta)
+
+  - Folder of static assets to be served. Replaces [Workers Sites](https://developers.cloudflare.com/workers/configuration/sites/). Visit [assets](https://developers.cloudflare.com/workers/static-assets/) for more information.
+
+- `--site` string optional (deprecated, use `--assets`)
+
+  - Folder of static assets for Workers Sites.
+
+  > **Warning:** Workers Sites is deprecated. Please use [Workers Assets](https://developers.cloudflare.com/workers/static-assets/) or [Pages](https://developers.cloudflare.com/pages/).
+
+- `--site-include` string[] optional (deprecated)
+
+  - Array of `.gitignore`-style patterns that match file or directory names from the sites directory. Only matched items will be uploaded.
+
+- `--site-exclude` string[] optional (deprecated)
+
+  - Array of `.gitignore`-style patterns that match file or directory names from the sites directory. Matched items will not be uploaded.
+
+- `--var` key:value[] optional
+
+  - Array of `key:value` pairs to inject as variables into your code. The value will always be passed as a string to your Worker.
+  - For example, `--var git_hash:$(git rev-parse HEAD) test:123` makes the `git_hash` and `test` variables available in your Worker's `env`.
+  - This flag is an alternative to defining [`vars`](https://developers.cloudflare.com/workers/wrangler/configuration/#non-inheritable-keys) in your [Wrangler configuration file](https://developers.cloudflare.com/workers/wrangler/configuration/). If defined in both places, this flag's values will be used.
+
+- `--define` key:value[] optional
+
+  - Array of `key:value` pairs to replace global identifiers in your code.
+  - For example, `--define GIT_HASH:$(git rev-parse HEAD)` will replace all uses of `GIT_HASH` with the actual value at build time.
+  - This flag is an alternative to defining [`define`](https://developers.cloudflare.com/workers/wrangler/configuration/#non-inheritable-keys) in your [Wrangler configuration file](https://developers.cloudflare.com/workers/wrangler/configuration/). If defined in both places, this flag's values will be used.
+
+- `--triggers`, `--schedule`, `--schedules` string[] optional
+
+  - Cron schedules to attach to the deployed Worker. Refer to [Cron Trigger Examples](https://developers.cloudflare.com/workers/configuration/cron-triggers/#examples).
+
+- `--routes`, `--route` string[] optional
+
+  - Routes where this Worker will be deployed.
+  - For example: `--route example.com/*`.
+
+- `--tsconfig` string optional
+
+  - Path to a custom `tsconfig.json` file.
+
+- `--minify` boolean optional
+
+  - Minify the bundled Worker before deploying.
+
+- `--dry-run` boolean (default: false) optional
+
+  - Compile a project without actually deploying to live servers. Combined with `--outdir`, this is also useful for testing the output of `npx wrangler deploy`. It also gives developers a chance to upload our generated sourcemap to a service like Sentry, so that errors from the Worker can be mapped against source code, but before the service goes live.
+
+- `--keep-vars` boolean (default: false) optional
+
+  - It is recommended best practice to treat your Wrangler developer environment as a source of truth for your Worker configuration, and avoid making changes via the Cloudflare dashboard.
+  - If you change your environment variables in the Cloudflare dashboard, Wrangler will override them the next time you deploy. If you want to disable this behaviour set `keep-vars` to `true`.
+  - Secrets are never deleted by a deployment whether this flag is true or false.
+
+- `--dispatch-namespace` string optional
+
+  - Specify the [Workers for Platforms dispatch namespace](https://developers.cloudflare.com/cloudflare-for-platforms/workers-for-platforms/get-started/configuration/#2-create-a-dispatch-namespace) to upload this Worker to.
+
+- `--metafile` string optional
+
+  - Specify a file to write the build metadata from esbuild to. If flag is used without a path string, this defaults to `bundle-meta.json` inside the directory specified by `--outdir`. This can be useful for understanding the bundle size.
+
+- `--containers-rollout` immediate | gradual optional
+
+  - Specify the [rollout strategy](https://developers.cloudflare.com/containers/faq#how-do-container-updates-and-rollouts-work) for [Containers](https://developers.cloudflare.com/containers) associated with the Worker. If set to `immediate`, 100% of container instances will be updated in one rollout step, overriding any configuration in `rollout_step_percentage`. Note that `rollout_active_grace_period`, if configured, still applies.
+  - Defaults to `gradual`, where the default rollout is 10% then 100% of instances.
+
+- `--strict` boolean (default: false) optional
+
+  - Turns on strict mode for the deployment command, meaning that the command will be more defensive and prevent deployments which could introduce potential issues. In particular, this mode prevents deployments if the deployment would potentially override remote settings in non-interactive environments.
+
+The following global flags work on every command:
+
+- `--help` boolean
+  - Show help.
+- `--config` string (not supported by Pages)
+  - Path to your [Wrangler configuration file](https://developers.cloudflare.com/workers/wrangler/configuration/).
+- `--cwd` string
+  - Run as if Wrangler was started in the specified directory instead of the current working directory.
+
+

package/templates/base/.claude/skills/wrangler/resources/commands/deployments.md

@@ -0,0 +1,56 @@
+# `deployments`
+
+Manage [Deployments](https://developers.cloudflare.com/workers/configuration/versions-and-deployments/) for your Worker.
+
+## `deployments list`
+
+List the 10 most recent Deployments of your Worker
+
+```sh
+npx wrangler deployments list
+```
+
+* `--name` string - Name of the Worker
+* `--json` boolean default: false - Display output as clean JSON
+
+## `deployments view`
+
+View the details of a specific Deployment of your Worker
+
+```sh
+npx wrangler deployments view [DEPLOYMENT-ID]
+```
+
+* `[DEPLOYMENT-ID]` string - The ID of the Deployment to view (defaults to latest)
+* `--name` string - Name of the Worker
+* `--json` boolean default: false - Display output as clean JSON
+
+## `deployments status`
+
+Check the current Deployment status of your Worker
+
+```sh
+npx wrangler deployments status
+```
+
+* `--name` string - Name of the Worker
+* `--json` boolean default: false - Display output as clean JSON
+
+## Gradual Deployments
+
+Use deployments to gradually roll out new versions of your Worker. Combined with the `versions` commands, you can:
+
+1. Upload a new version: `wrangler versions upload`
+2. View current deployment: `wrangler deployments view`
+3. Create a new deployment with traffic split: `wrangler versions deploy`
+4. Monitor and adjust: `wrangler deployments status`
+
+## Global flags
+
+- `--v` boolean alias: --version - Show version number
+- `--cwd` string - Run as if Wrangler was started in the specified directory
+- `--config` string alias: --c - Path to Wrangler configuration file
+- `--env` string alias: --e - Environment to use for operations
+- `--env-file` string - Path to an .env file to load
+
+

package/templates/base/.claude/skills/wrangler/resources/commands/dev.md

@@ -0,0 +1,157 @@
+# `dev`
+
+Start a local server for developing your Worker.
+
+```txt
+wrangler dev [<SCRIPT>] [OPTIONS]
+```
+
+> **Note:** None of the options for this command are required. Many of these options can be set in your Wrangler file. Refer to the [Wrangler configuration](https://developers.cloudflare.com/workers/wrangler/configuration) documentation for more information.
+
+- `SCRIPT` string
+
+  - The path to an entry point for your Worker. Only required if your [Wrangler configuration file](https://developers.cloudflare.com/workers/wrangler/configuration/) does not include a `main` key (for example, `main = "index.js"`).
+
+- `--name` string optional
+
+  - Name of the Worker.
+
+- `--config`, `-c` string[] optional
+
+  - Path(s) to [Wrangler configuration file](https://developers.cloudflare.com/workers/wrangler/configuration/). If not provided, Wrangler will use the nearest config file based on your current working directory.
+  - You can provide multiple configuration files to run multiple Workers in one dev session like this: `wrangler dev -c ./wrangler.toml -c ../other-worker/wrangler.toml`. The first config will be treated as the _primary_ Worker, which will be exposed over HTTP. The remaining config files will only be accessible via a service binding from the primary Worker.
+
+- `--no-bundle` boolean (default: false) optional
+
+  - Skip Wrangler's build steps. Particularly useful when using custom builds. Refer to [Bundling](https://developers.cloudflare.com/workers/wrangler/bundling/) for more information.
+
+- `--env` string optional
+
+  - Perform on a specific environment.
+
+- `--compatibility-date` string optional
+
+  - A date in the form yyyy-mm-dd, which will be used to determine which version of the Workers runtime is used.
+
+- `--compatibility-flags`, `--compatibility-flag` string[] optional
+
+  - Flags to use for compatibility checks.
+
+- `--latest` boolean (default: true) optional
+
+  - Use the latest version of the Workers runtime.
+
+- `--ip` string optional
+
+  - IP address to listen on, defaults to `localhost`.
+
+- `--port` number optional
+
+  - Port to listen on.
+
+- `--inspector-port` number optional
+
+  - Port for devtools to connect to.
+
+- `--routes`, `--route` string[] optional
+
+  - Routes to upload.
+  - For example: `--route example.com/*`.
+
+- `--host` string optional
+
+  - Host to forward requests to, defaults to the zone of project.
+
+- `--local-protocol` 'http'|'https' (default: http) optional
+
+  - Protocol to listen to requests on.
+
+- `--https-key-path` string optional
+
+  - Path to a custom certificate key.
+
+- `--https-cert-path` string optional
+
+  - Path to a custom certificate.
+
+- `--local-upstream` string optional
+
+  - Host to act as origin in local mode, defaults to `dev.host` or route.
+
+- `--assets` string optional (beta)
+
+  - Folder of static assets to be served. Replaces [Workers Sites](https://developers.cloudflare.com/workers/configuration/sites/). Visit [assets](https://developers.cloudflare.com/workers/static-assets/) for more information.
+
+- `--site` string optional (deprecated, use `--assets`)
+
+  - Folder of static assets for Workers Sites.
+
+  > **Warning:** Workers Sites is deprecated. Please use [Workers Assets](https://developers.cloudflare.com/workers/static-assets/) or [Pages](https://developers.cloudflare.com/pages/).
+
+- `--site-include` string[] optional (deprecated)
+
+  - Array of `.gitignore`-style patterns that match file or directory names from the sites directory. Only matched items will be uploaded.
+
+- `--site-exclude` string[] optional (deprecated)
+
+  - Array of `.gitignore`-style patterns that match file or directory names from the sites directory. Matched items will not be uploaded.
+
+- `--upstream-protocol` 'http'|'https' (default: https) optional
+
+  - Protocol to forward requests to host on.
+
+- `--var` key:value[] optional
+
+  - Array of `key:value` pairs to inject as variables into your code. The value will always be passed as a string to your Worker.
+  - For example, `--var "git_hash:'$(git rev-parse HEAD)'" "test:123"` makes the `git_hash` and `test` variables available in your Worker's `env`.
+  - This flag is an alternative to defining [`vars`](https://developers.cloudflare.com/workers/wrangler/configuration/#non-inheritable-keys) in your [Wrangler configuration file](https://developers.cloudflare.com/workers/wrangler/configuration/). If defined in both places, this flag's values will be used.
+
+- `--define` key:value[] optional
+
+  - Array of `key:value` pairs to replace global identifiers in your code.
+  - For example, `--define "GIT_HASH:'$(git rev-parse HEAD)'"` will replace all uses of `GIT_HASH` with the actual value at build time.
+  - This flag is an alternative to defining [`define`](https://developers.cloudflare.com/workers/wrangler/configuration/#non-inheritable-keys) in your [Wrangler configuration file](https://developers.cloudflare.com/workers/wrangler/configuration/). If defined in both places, this flag's values will be used.
+
+- `--tsconfig` string optional
+
+  - Path to a custom `tsconfig.json` file.
+
+- `--minify` boolean optional
+
+  - Minify the Worker.
+
+- `--persist-to` string optional
+
+  - Specify directory to use for local persistence.
+
+- `--remote` boolean (default: false) optional
+
+  - Develop against remote resources and data stored on Cloudflare's network.
+
+- `--test-scheduled` boolean (default: false) optional
+
+  - Exposes a `/__scheduled` fetch route which will trigger a scheduled event (Cron Trigger) for testing during development. To simulate different cron patterns, a `cron` query parameter can be passed in: `/__scheduled?cron=*+*+*+*+*` or `/cdn-cgi/handler/scheduled?cron=*+*+*+*+*`.
+
+- `--log-level` 'debug'|'info'|'log'|'warn'|'error|'none' (default: log) optional
+
+  - Specify Wrangler's logging level.
+
+- `--show-interactive-dev-session` boolean (default: true if the terminal supports interactivity) optional
+
+  - Show the interactive dev session.
+
+- `--alias` Array<string>
+  - Specify modules to alias using [module aliasing](https://developers.cloudflare.com/workers/wrangler/configuration/#module-aliasing).
+
+The following global flags work on every command:
+
+- `--help` boolean
+  - Show help.
+- `--config` string (not supported by Pages)
+  - Path to your [Wrangler configuration file](https://developers.cloudflare.com/workers/wrangler/configuration/).
+- `--cwd` string
+  - Run as if Wrangler was started in the specified directory instead of the current working directory.
+
+`wrangler dev` is a way to [locally test](https://developers.cloudflare.com/workers/development-testing/) your Worker while developing. With `wrangler dev` running, send HTTP requests to `localhost:8787` and your Worker should execute as expected. You will also see `console.log` messages and exceptions appearing in your terminal.
+
+

package/templates/base/.claude/skills/wrangler/resources/commands/dispatch-namespace.md

@@ -0,0 +1,69 @@
+# `dispatch-namespace`
+
+Manage [dispatch namespaces](https://developers.cloudflare.com/cloudflare-for-platforms/workers-for-platforms/reference/how-workers-for-platforms-works/#dispatch-namespace) for Workers for Platforms.
+
+## `dispatch-namespace list`
+
+List dispatch namespaces
+
+```sh
+npx wrangler dispatch-namespace list
+```
+
+## `dispatch-namespace get`
+
+Get a dispatch namespace
+
+```sh
+npx wrangler dispatch-namespace get [NAME]
+```
+
+* `[NAME]` string required - Name of the dispatch namespace
+
+## `dispatch-namespace create`
+
+Create a dispatch namespace
+
+```sh
+npx wrangler dispatch-namespace create [NAME]
+```
+
+* `[NAME]` string required - Name of the dispatch namespace
+
+## `dispatch-namespace delete`
+
+Delete a dispatch namespace
+
+```sh
+npx wrangler dispatch-namespace delete [NAME]
+```
+
+* `[NAME]` string required - Name of the dispatch namespace
+
+## `dispatch-namespace rename`
+
+Rename a dispatch namespace
+
+```sh
+npx wrangler dispatch-namespace rename [OLD-NAME] [NEW-NAME]
+```
+
+* `[OLD-NAME]` string required - Old name of the dispatch namespace
+* `[NEW-NAME]` string required - New name of the dispatch namespace
+
+## Workers for Platforms
+
+Dispatch namespaces are part of Cloudflare's Workers for Platforms, enabling you to:
+- Deploy customer Workers in isolated environments
+- Route requests to customer Workers dynamically
+- Manage multi-tenant Worker deployments
+
+## Global flags
+
+- `--v` boolean alias: --version - Show version number
+- `--cwd` string - Run as if Wrangler was started in the specified directory
+- `--config` string alias: --c - Path to Wrangler configuration file
+- `--env` string alias: --e - Environment to use for operations
+- `--env-file` string - Path to an .env file to load
+
+

package/templates/base/.claude/skills/wrangler/resources/commands/docs.md

@@ -0,0 +1,61 @@
+# `docs`
+
+Open the Cloudflare developer documentation in your default browser.
+
+- npm
+
+  ```sh
+  npx wrangler docs [SEARCH]
+  ```
+
+- pnpm
+
+  ```sh
+  pnpm wrangler docs [SEARCH]
+  ```
+
+- yarn
+
+  ```sh
+  yarn wrangler docs [SEARCH]
+  ```
+
+* `[SEARCH]` string
+
+  Enter search terms (e.g. the wrangler command) you want to know more about
+
+* `--yes` boolean alias: --y
+
+  Takes you to the docs, even if search fails
+
+Global flags
+
+- `--v` boolean alias: --version
+
+  Show version number
+
+- `--cwd` string
+
+  Run as if Wrangler was started in the specified directory instead of the current working directory
+
+- `--config` string alias: --c
+
+  Path to Wrangler configuration file
+
+- `--env` string alias: --e
+
+  Environment to use for operations, and for selecting .env and .dev.vars files
+
+- `--env-file` string
+
+  Path to an .env file to load - can be specified multiple times - values from earlier files are overridden by values in later files
+
+- `--experimental-provision` boolean aliases: --x-provision default: true
+
+  Experimental: Enable automatic resource provisioning
+
+- `--experimental-auto-create` boolean alias: --x-auto-create default: true
+
+  Automatically provision draft bindings with new resources
+
+

package/templates/base/.claude/skills/wrangler/resources/commands/how-to-run.md

@@ -0,0 +1,62 @@
+# How to run Wrangler commands
+
+This page provides a reference for Wrangler commands.
+
+```txt
+wrangler <COMMAND> <SUBCOMMAND> [PARAMETERS] [OPTIONS]
+```
+
+Since Cloudflare recommends [installing Wrangler locally](https://developers.cloudflare.com/workers/wrangler/install-and-update/) in your project(rather than globally), the way to run Wrangler will depend on your specific setup and package manager.
+
+- npm
+
+  ```sh
+  npx wrangler <COMMAND> <SUBCOMMAND> [PARAMETERS] [OPTIONS]
+  ```
+
+- yarn
+
+  ```sh
+  yarn wrangler <COMMAND> <SUBCOMMAND> [PARAMETERS] [OPTIONS]
+  ```
+
+- pnpm
+
+  ```sh
+  pnpm wrangler <COMMAND> <SUBCOMMAND> [PARAMETERS] [OPTIONS]
+  ```
+
+You can add Wrangler commands that you use often as scripts in your project's `package.json` file:
+
+```json
+{
+  ...
+  "scripts": {
+    "deploy": "wrangler deploy",
+    "dev": "wrangler dev"
+  }
+  ...
+}
+```
+
+You can then run them using your package manager of choice:
+
+- npm
+
+  ```sh
+  npm run deploy
+  ```
+
+- yarn
+
+  ```sh
+  yarn run deploy
+  ```
+
+- pnpm
+
+  ```sh
+  pnpm run deploy
+  ```
+
+