@etus/bhono-app 0.1.1

package/templates/base/.claude/skills/wrangler/resources/commands/secrets-store-secret.md

@@ -0,0 +1,100 @@
+# `secrets-store secret`
+
+With the release of [Secrets Store](https://developers.cloudflare.com/secrets-store/) in open beta, you can use the following commands to manage your account secrets.
+
+> **Note:** In order to interact with Secrets Store in production, you should append `--remote` to your command. Without it, your command will default to [local development mode](https://developers.cloudflare.com/workers/development-testing/).
+
+## `secrets-store secret create`
+
+Create a secret within a store
+
+```sh
+npx wrangler secrets-store secret create [STORE-ID]
+```
+
+* `[STORE-ID]` string required - ID of the store in which the secret resides
+* `--name` string required - Name of the secret
+* `--value` string - Value of the secret (Note: Only for testing. Not secure as this will leave secret value in plain-text in terminal history)
+* `--scopes` string required - Scopes for the secret (comma-separated list e.g. "workers")
+* `--comment` string - Comment for the secret
+* `--remote` boolean default: false - Execute command against remote Secrets Store
+* `--persist-to` string - Directory for local persistence
+
+## `secrets-store secret update`
+
+Update a secret within a store
+
+```sh
+npx wrangler secrets-store secret update [STORE-ID]
+```
+
+* `[STORE-ID]` string required - ID of the store in which the secret resides
+* `--secret-id` string required - ID of the secret to update
+* `--value` string - Updated value of the secret
+* `--scopes` string - Updated scopes for the secret
+* `--comment` string - Updated comment for the secret
+* `--remote` boolean default: false - Execute command against remote Secrets Store
+* `--persist-to` string - Directory for local persistence
+
+## `secrets-store secret duplicate`
+
+Duplicate a secret within a store
+
+```sh
+npx wrangler secrets-store secret duplicate [STORE-ID]
+```
+
+* `[STORE-ID]` string required - ID of the store in which the secret resides
+* `--secret-id` string required - ID of the secret to duplicate the secret value of
+* `--name` string required - Name of the new secret
+* `--scopes` string required - Scopes for the new secret
+* `--comment` string - Comment for the new secret
+* `--remote` boolean default: false - Execute command against remote Secrets Store
+
+## `secrets-store secret get`
+
+Get a secret within a store
+
+```sh
+npx wrangler secrets-store secret get [STORE-ID]
+```
+
+* `[STORE-ID]` string required - ID of the store in which the secret resides
+* `--secret-id` string required - ID of the secret to retrieve
+* `--remote` boolean default: false - Execute command against remote Secrets Store
+* `--persist-to` string - Directory for local persistence
+
+## `secrets-store secret delete`
+
+Delete a secret within a store
+
+```sh
+npx wrangler secrets-store secret delete [STORE-ID]
+```
+
+* `[STORE-ID]` string required - ID of the store in which the secret resides
+* `--secret-id` string required - ID of the secret to delete
+* `--remote` boolean default: false - Execute command against remote Secrets Store
+
+## `secrets-store secret list`
+
+List secrets within a store
+
+```sh
+npx wrangler secrets-store secret list [STORE-ID]
+```
+
+* `[STORE-ID]` string required - ID of the store in which to list secrets
+* `--page` number default: 1 - Page number of secrets listing results
+* `--per-page` number default: 10 - Number of secrets to show per page
+* `--remote` boolean default: false - Execute command against remote Secrets Store
+
+## 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/secrets-store-store.md

@@ -0,0 +1,60 @@
+# `secrets-store store`
+
+Use the following commands to manage your store.
+
+> **Note:** [Secrets Store](https://developers.cloudflare.com/secrets-store/) is in open beta. Currently, you can only have one store per Cloudflare account.
+
+## `secrets-store store create`
+
+Create a store within an account
+
+```sh
+npx wrangler secrets-store store create [NAME]
+```
+
+* `[NAME]` string required - Name of the store
+* `--remote` boolean default: false - Execute command against remote Secrets Store
+
+Example:
+
+```sh
+npx wrangler secrets-store store create default --remote
+```
+
+```sh
+🔐 Creating store... (Name: default)
+✅ Created store! (Name: default, ID: 2e2a82d317134506b58defbe16982d54)
+```
+
+## `secrets-store store delete`
+
+Delete a store within an account
+
+```sh
+npx wrangler secrets-store store delete [STORE-ID]
+```
+
+* `[STORE-ID]` string required - ID of the store
+* `--remote` boolean default: false - Execute command against remote Secrets Store
+
+## `secrets-store store list`
+
+List stores within an account
+
+```sh
+npx wrangler secrets-store store list
+```
+
+* `--page` number default: 1 - Page number of stores listing results
+* `--per-page` number default: 10 - Number of stores to show per page
+* `--remote` boolean default: false - Execute command against remote Secrets Store
+
+## 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/setup.md

@@ -0,0 +1,67 @@
+# `setup`
+
+> **Experimental**
+
+Setup a project to work on Cloudflare
+
+- npm
+
+  ```sh
+  npx wrangler setup
+  ```
+
+- pnpm
+
+  ```sh
+  pnpm wrangler setup
+  ```
+
+- yarn
+
+  ```sh
+  yarn wrangler setup
+  ```
+
+* `--yes` boolean alias: --y default: false
+
+  Answer "yes" to any prompts for configuring your project
+
+* `--build` boolean default: false
+
+  Run your project's build command once it has been configured
+
+* `--dry-run` boolean
+
+  Runs the command without applying any filesystem modifications
+
+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/tail.md

@@ -0,0 +1,37 @@
+# `tail`
+
+Start a log tailing session for a Worker
+
+```sh
+npx wrangler tail [WORKER]
+```
+
+* `[WORKER]` string - Name or route of the worker to tail
+* `--format` "json" | "pretty" - The format of log entries
+* `--status` "ok" | "error" | "canceled" - Filter by invocation status
+* `--header` string - Filter by HTTP header
+* `--method` string - Filter by HTTP method
+* `--sampling-rate` number - Adds a percentage of requests to log sampling rate
+* `--search` string - Filter by a text match in console.log messages
+* `--ip` string - Filter by the IP address the request originates from. Use "self" for your own IP
+* `--version-id` string - Filter by Worker version
+
+## 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
+
+## Usage
+
+After starting `wrangler tail`, you will receive a live feed of console and exception logs for each request your Worker receives.
+
+If your Worker has a high volume of traffic, the tail might enter sampling mode. This will cause some of your messages to be dropped and a warning to appear in your tail logs. To prevent messages from being dropped, add the options listed above to filter the volume of tail messages.
+
+> **Note:** It may take up to 1 minute (60 seconds) for a tail to exit sampling mode after adding an option to filter tail messages.
+
+If sampling persists after using options to filter messages, consider using [instant logs](https://developers.cloudflare.com/logs/instant-logs/).
+
+

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

@@ -0,0 +1,64 @@
+# `telemetry`
+
+Manage Wrangler telemetry settings.
+
+Wrangler collects anonymous usage data to improve the CLI experience. You can control this behavior using these commands.
+
+## `telemetry status`
+
+Check the current telemetry status
+
+```sh
+npx wrangler telemetry status
+```
+
+## `telemetry disable`
+
+Disable telemetry collection
+
+```sh
+npx wrangler telemetry disable
+```
+
+## `telemetry enable`
+
+Enable telemetry collection
+
+```sh
+npx wrangler telemetry enable
+```
+
+## What Data is Collected
+
+When enabled, Wrangler collects:
+- Command usage statistics
+- Error rates and types
+- Feature usage patterns
+- Performance metrics
+
+Data collected is:
+- Fully anonymized
+- Not linked to any personal information
+- Used only to improve Wrangler
+
+## Alternative Methods
+
+You can also control telemetry via environment variables:
+
+```sh
+# Disable telemetry
+export WRANGLER_SEND_METRICS=false
+
+# Or in your shell profile
+echo 'export WRANGLER_SEND_METRICS=false' >> ~/.zshrc
+```
+
+## 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/triggers.md

@@ -0,0 +1,39 @@
+# `triggers`
+
+Update the triggers of your current deployment.
+
+## `triggers deploy`
+
+Update the triggers of an existing Worker
+
+```sh
+npx wrangler triggers deploy
+```
+
+* `--name` string - Name of the Worker
+* `--triggers` array - Cron schedules to attach
+* `--routes` array - Routes to attach
+* `--dry-run` boolean default: false - Don't actually deploy
+* `--json` boolean default: false - Display output as clean JSON
+
+This command updates the triggers for your currently deployed Worker. Use this when you need to modify cron schedules or routes without redeploying your Worker code.
+
+Example:
+
+```sh
+# Add cron triggers
+npx wrangler triggers deploy --triggers "*/5 * * * *" --triggers "0 12 * * MON"
+
+# Update routes
+npx wrangler triggers deploy --routes "example.com/*" --routes "api.example.com/*"
+```
+
+## 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/types.md

@@ -0,0 +1,73 @@
+# `types`
+
+Generate TypeScript types from bindings and module rules in your Wrangler configuration file.
+
+```sh
+npx wrangler types [PATH]
+```
+
+* `[PATH]` string - Path to the output file (defaults to `worker-configuration.d.ts`)
+* `--experimental-include-runtime` boolean alias: --x-include-runtime - Experimental: Include types for the Workers runtime
+
+## Usage
+
+When you run `wrangler types`, it reads your `wrangler.toml` configuration and generates TypeScript type definitions for all your bindings.
+
+Example:
+
+```sh
+# Generate types to default location
+npx wrangler types
+
+# Generate types to custom location
+npx wrangler types ./src/types/env.d.ts
+```
+
+## Generated Types
+
+The command generates type definitions for:
+- KV namespaces
+- R2 buckets
+- D1 databases
+- Durable Objects
+- Queues
+- Service bindings
+- Secret variables
+- Environment variables
+- AI bindings
+- Vectorize indexes
+- Hyperdrive configurations
+
+## Example Output
+
+```typescript
+interface Env {
+  // KV Namespace
+  MY_KV: KVNamespace;
+  
+  // R2 Bucket
+  MY_BUCKET: R2Bucket;
+  
+  // D1 Database
+  DB: D1Database;
+  
+  // Durable Object
+  MY_DO: DurableObjectNamespace;
+  
+  // Queue
+  MY_QUEUE: Queue;
+  
+  // Secret
+  API_KEY: string;
+}
+```
+
+## 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
+
+