normlstudio
OrganizationNorml WordPress Copilot Advanced - CLI-only theme development through GitHub, SSH, and WP-CLI.
Categories
Indexed Skills (6)
norml-wp-developer
Norml WordPress Copilot Advanced: rebuild Squarespace captures and HTML mockups as editable WordPress in Local, with local-only onboarding before hosting. The CLI-only WordPress development skill for Claude Code, Codex, and Gemini CLI. Develop themes locally and deploy through SSH + Git + GitHub Actions. WP Local is the default local environment (DDEV / Lando / Valet recognized too). Per-project onboarding connects GitHub and SSH, verifies remote WP-CLI, chooses the CI/CD pattern, scaffolds .claude/ inside the theme repo, generates capabilities.md, and records a five-file architecture snapshot. The everyday workflow is edit locally, commit, push, stage, smoke test, promote to prod. **Does NOT make backups.** Every production write gates on a backup acknowledgement. Direct-on-server work is permitted but flagged and logged. Local-first is the default. Use when the user says "build a WordPress theme," "develop a WP site," "set up a new WP project," "init this WP project," "ship to staging," "deploy to productio
norml-wp-manager
Norml WordPress Copilot: manage a single WordPress site through the WordPress REST API from Claude Desktop / Cowork, Claude Code, Codex, or Gemini CLI. For non-technical site owners — no SSH, no WP-CLI, no developer tooling. Needs WordPress 5.6+ and an admin or editor Application Password. All state for a site lives in one portable folder you name: generated `capabilities.md`, readable `project-notes.md` + `changelog.md` at the top, machinery in a hidden `.wpm/` (connection config + the auto-generated site scan; the credential only when no OS keychain is available). Detects a supported CLI runtime (Console) vs Claude Desktop / Cowork (Desktop) and acts accordingly; on Desktop it verifies your site is reachable before asking for any credential. The Application Password lives in macOS Keychain / Windows Credential Manager / Linux libsecret on Console, or a local browser-to-folder handoff on Desktop — the credential never enters the AI conversation and is immediately imported into a born-private, gitignored file
norml-wp-manager
Norml WordPress Copilot: manage a single WordPress site through the WordPress REST API from Claude Desktop / Cowork, Claude Code, Codex, or Gemini CLI. For non-technical site owners — no SSH, no WP-CLI, no developer tooling. Needs WordPress 5.6+ and an admin or editor Application Password. All state for a site lives in one portable folder you name: generated `capabilities.md`, readable `project-notes.md` + `changelog.md` at the top, machinery in a hidden `.wpm/` (connection config + the auto-generated site scan; the credential only when no OS keychain is available). Detects a supported CLI runtime (Console) vs Claude Desktop / Cowork (Desktop) and acts accordingly; on Desktop it verifies your site is reachable before asking for any credential. The Application Password lives in macOS Keychain / Windows Credential Manager / Linux libsecret on Console, or a local browser-to-folder handoff on Desktop — the credential never enters the AI conversation and is immediately imported into a born-private, gitignored file
norml-wp-developer
Norml WordPress Copilot Advanced: the CLI-only WordPress development skill for Claude Code, Codex, and Gemini CLI. Develop themes locally and deploy through SSH + Git + GitHub Actions. WP Local is the default local environment (DDEV / Lando / Valet recognized too). Per-project onboarding connects GitHub and SSH, verifies remote WP-CLI, chooses the CI/CD pattern, scaffolds .claude/ inside the theme repo, generates capabilities.md, and records a five-file architecture snapshot. The everyday workflow is edit locally, commit, push, stage, smoke test, promote to prod. **Does NOT make backups.** Every production write gates on a backup acknowledgement. Direct-on-server work is permitted but flagged and logged. Local-first is the default. Use when the user says "build a WordPress theme," "develop a WP site," "set up a new WP project," "init this WP project," "ship to staging," "deploy to production," "promote to prod," "set up CI/CD for WordPress," "what's the deploy flow," "pull production DB," "rescan architecture
moonpresschat-setup
Install or set up MoonPress Chat on a WordPress site through a safe six-stage workflow: preflight, research, owner questions, connect, configure, and verify. Defaults to the shipped MoonPress Chat setup API with a local credential helper; keeps the guided WordPress-admin path as the documented fallback. Use when a site owner asks to install, plan, configure, review, or launch MoonPress Chat without exposing WordPress passwords or AI-provider keys to the agent.
quip-setup
Install or set up Quip Bot on a WordPress site through a safe six-stage workflow: preflight, research, owner questions, connect, configure, and verify. Defaults to the shipped Quip Bot setup API with a local credential helper; keeps the guided WordPress-admin path as the documented fallback. Use when a site owner asks to install, plan, configure, review, or launch Quip Bot without exposing WordPress passwords or AI-provider keys to the agent.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.