td-ai-tools 1.0.4 → 1.0.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "td-ai-tools",
-  "version": "1.0.4",
+  "version": "1.0.5",
   "description": "Install agent skills and packs into your project",
   "scripts": {
     "smoke:install": "./scripts/smoke-install.sh"
@@ -18,6 +18,12 @@
   "engines": {
     "node": ">=16"
   },
-  "keywords": ["claude", "agents", "skills", "shopify", "theory-digital"],
+  "keywords": [
+    "claude",
+    "agents",
+    "skills",
+    "shopify",
+    "theory-digital"
+  ],
   "license": "MIT"
 }

package/skills/forge-cli/SKILL.md

@@ -0,0 +1,84 @@
+---
+name: forge-cli
+description: Manage Laravel Forge servers, sites, and provisioned resources from the terminal with the Laravel Forge CLI. Use when the user wants to inspect Forge state, switch active servers, deploy sites, update environment variables, view logs, run remote commands, use Tinker, or manage services like PHP, Nginx, daemons, and databases.
+---
+
+# Laravel Forge CLI
+
+## Core Workflow
+
+1. Start with `forge` to confirm the CLI is installed and to inspect available commands.
+2. Check the active server before making changes:
+
+```bash
+forge server:current
+forge server:list
+forge server:switch staging
+```
+
+3. If the task needs SSH access, verify connectivity first:
+
+```bash
+forge ssh:test
+forge ssh:configure --key=/path/to/public/key.pub --name=workstation-name
+```
+
+4. Run the smallest command that answers the question or performs the requested change.
+5. After environment changes, note that cached Laravel config or queue workers may require a fresh deployment before the new values take effect.
+
+## Common Tasks
+
+### Sites and Deployments
+
+```bash
+forge site:list
+forge deploy
+forge deploy example.com
+forge deploy:logs
+forge deploy:logs 12345
+```
+
+### Environment Variables
+
+Pull, edit locally, then push back:
+
+```bash
+forge env:pull
+forge env:pull example.com .env
+forge env:push
+forge env:push example.com .env
+```
+
+### Logs, Commands, and Tinker
+
+```bash
+forge site:logs
+forge site:logs example.com --follow
+forge command example.com --command="php artisan about"
+forge tinker example.com
+```
+
+### SSH and Resource Access
+
+```bash
+forge ssh
+forge ssh server-name
+forge database:status
+forge database:logs
+forge database:shell my-database-name --user=my-user
+forge php:status 8.5
+forge php:restart 8.5
+forge nginx:logs access
+forge daemon:restart
+```
+
+## Decision Guide
+
+- Need server context first: use `server:current`, `server:list`, or `server:switch`.
+- Need site-level work: use `site:list`, `deploy`, `env:*`, `site:logs`, `command`, or `tinker`.
+- Need service health or maintenance: use `{resource}:status`, `{resource}:logs`, `{resource}:restart`, or `{resource}:shell`.
+- Need a secure shell on the box: confirm `ssh:test`, then use `forge ssh`.
+
+## Reference
+
+Read [references/command-reference.md](references/command-reference.md) when you need the fuller command set, examples, or reminders about how the active server affects command behavior.

package/skills/forge-cli/references/command-reference.md

@@ -0,0 +1,176 @@
+# Forge CLI Command Reference
+
+This reference condenses the official Laravel Forge CLI documentation into the commands most likely to come up during support and operations work.
+
+## Installation and Authentication
+
+Requirements:
+
+- PHP 8.0 or newer
+- Composer available on the machine
+
+Install:
+
+```bash
+composer global require laravel/forge-cli
+```
+
+Basic checks:
+
+```bash
+forge
+```
+
+Authenticate:
+
+```bash
+forge login
+forge login --token=your-api-token
+```
+
+CI authentication:
+
+```bash
+export FORGE_API_TOKEN=your-api-token
+```
+
+## Active Server Model
+
+Most Forge CLI commands run against the current active server. Check or change it before acting:
+
+```bash
+forge server:current
+forge server:list
+forge server:switch
+forge server:switch production
+```
+
+Use this first when a task is ambiguous or when multiple Forge servers exist.
+
+## SSH Setup
+
+Validate or configure SSH access for the `forge` user:
+
+```bash
+forge ssh:test
+forge ssh:configure
+forge ssh:configure --key=/path/to/public/key.pub --name=laptop-key
+forge ssh
+forge ssh server-name
+```
+
+## Sites
+
+List sites on the active server:
+
+```bash
+forge site:list
+```
+
+Deploy a site:
+
+```bash
+forge deploy
+forge deploy example.com
+```
+
+Review deployment output:
+
+```bash
+forge deploy:logs
+forge deploy:logs 12345
+```
+
+Manage environment variables:
+
+```bash
+forge env:pull
+forge env:pull example.com
+forge env:pull example.com .env
+
+forge env:push
+forge env:push example.com
+forge env:push example.com .env
+```
+
+If the application uses Laravel config caching or queue workers, push alone is not enough. Redeploy so the new variables are actually loaded.
+
+View application logs:
+
+```bash
+forge site:logs
+forge site:logs --follow
+forge site:logs example.com
+forge site:logs example.com --follow
+```
+
+Run commands relative to the site's root:
+
+```bash
+forge command
+forge command example.com
+forge command example.com --command="php artisan migrate --force"
+```
+
+Open Tinker on a remote Laravel app:
+
+```bash
+forge tinker
+forge tinker example.com
+```
+
+## Resources
+
+Forge exposes service-oriented commands with the pattern `{resource}:status`, `{resource}:logs`, `{resource}:restart`, and sometimes `{resource}:shell`.
+
+### Status
+
+```bash
+forge daemon:status
+forge database:status
+forge nginx:status
+forge php:status
+forge php:status 8.5
+```
+
+### Logs
+
+```bash
+forge daemon:logs
+forge daemon:logs --follow
+forge database:logs
+forge nginx:logs
+forge nginx:logs access
+forge php:logs
+forge php:logs 8.5
+```
+
+### Restart
+
+```bash
+forge daemon:restart
+forge database:restart
+forge nginx:restart
+forge php:restart
+forge php:restart 8.5
+```
+
+### Local Shell Access to Resources
+
+```bash
+forge database:shell
+forge database:shell my-database-name
+forge database:shell my-database-name --user=my-user
+```
+
+## Practical Usage Notes
+
+- Prefer read-only commands first when the request is exploratory.
+- Confirm the active server before running deploys, restarts, or environment pushes.
+- Use explicit site names when there is any chance of ambiguity.
+- Use `--follow` only when the user wants a live log tail.
+- When sharing results back to the user, report the exact command run and whether it changed state.
+
+## Source
+
+Official documentation: https://forge.laravel.com/docs/cli