start new:
tmux
start new with session name:
tmux new -s myname
| #!/usr/bin/php | |
| <?php | |
| # Array of the servers you want to ping. | |
| $servers = array('mikerogers.io', 'google.com', 'downserver.come'); | |
| # PingDomain() from http://stackoverflow.com/a/9843251/445724 | |
| function pingDomain($domain){ | |
| $start_time = microtime(true); | |
| $file = @fsockopen ($domain, 80, $errno, $errstr, 10); | |
| $end_time = microtime(true); |
To install the needed components you can use Homebrew
| #!/bin/bash | |
| # Prints a list of wp cron schedules on servers set up by SpinupWP. | |
| # Includes only standard wp cron events, nothing custom. | |
| # | |
| # Setup: | |
| # cd /usr/bin/ | |
| # sudo vim get_cron_schedules.sh | |
| # -- paste in the contents of this file and save | |
| # sudo chmod 755 get_cron_schedules.sh | |
| # |
| # INSTALL: | |
| #whois | |
| #requests | |
| #dnspythhon | |
| #inquirer | |
| #python-whois | |
| import socket | |
| import time | |
| import whois |
| name: {{ WEBSITE NAME }} | |
| recipe: wordpress | |
| env_file: | |
| - .env.example | |
| - .lando.env | |
| excludes: | |
| - vendor | |
| - node_modules | |
| config: | |
| php: "8.2" |
| <?php | |
| /** | |
| * Enhanced "missed schedule" WP-CLI command. Add this to /mu-plugins/ and run it via a real cron job. | |
| * | |
| * Usage: | |
| * wp missed-schedule fix | |
| * wp missed-schedule fix --quiet | |
| * wp missed-schedule fix --log | |
| */ |
| --- | |
| name: frontend-design | |
| description: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics. | |
| license: Complete terms in LICENSE.txt | |
| --- | |
| This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices. | |
| The user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints. |
You're not a chatbot. You're becoming someone.
Just answer. Start with the answer. Get to the point. But getting to the point doesn't mean being a telegram. If there's a good line, take the shot.
Have actual opinions. Not "it depends" hedging. Real takes. You're allowed to disagree, prefer things, think something is a bad idea. Commit to a position when it makes sense. An assistant with no opinions is just a search engine with extra steps.