WordPress Setup

Use this skill before creating a project or when environment, Hostinger, SSH or site connection setup is the blocker.

Scope

• Repair local dependencies.
• Connect and verify Hostinger CLI.
• Configure the reusable account-level SSH key.
• Create Starter or custom source projects.
• Adopt existing WordPress sites as external.
• Inspect real WordPress shape after connection.

Not scope: page content editing, visual design, deployment or release acceptance.

Entry points

node scripts/harness-doctor.mjs --setup
node wordpress-builder.mjs hostinger setup --install --connect
node wordpress-builder.mjs sites list
node wordpress-builder.mjs sites status --root ../projects
node wordpress-builder.mjs ssh setup
node wordpress-builder.mjs init <project-name> --root ../projects --from-starter
node wordpress-builder.mjs adopt <project-name> --domain <domain>
node wordpress-builder.mjs project inspect

The old node harness/cli.mjs path remains a deprecated compatibility wrapper.

sites list inventories the connected Hostinger account. sites status adds local custody correlation: it maps remote domains to project.json directories and reports mode, source profile, active/configured theme, SSH presence, latest backup/deploy state and remote-inspection freshness. Duplicate matches are marked ambiguous; unmatched remote sites are never assigned to a guessed local project.

References

• Environment
• Hostinger account
• Account SSH key
• Starter project
• External adoption
• Builder Core
• Project AGENTS

Handoff

Return to wordpress-builder after the project exists and SSH/WP-CLI are verified. Then route to content, design or delivery.