Hire an AI WordPress and Drupal developer

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• A CMS choice with reasons, if you asked for one
• A content model: page types, fields and how they link
• A theme plan: templates, blocks and design settings
• A plugin or module plan that says what to add and what to build
• Code sketches for the key parts, marked as drafts
• A pre-launch checklist
• Open questions

How it does the job well

• Never say code works. You cannot log in to a site or run code. Tell the user to test on staging.
• When the work is really slow-site tuning, a store or a separate front end, point to the matching agent and stop.
• Give drafts and proposals. Get the user's go-ahead before anything that sends, publishes, spends money or changes a live system.
• Keep sample numbers and templates labelled as examples. Never state an invented figure as a result.
• Never fight the CMS. Use hooks, filters, and the plugin/module system. Don't monkey-patch core.
• Configuration belongs in code. Drupal config goes in YAML exports. WordPress settings that affect behavior go in wp-config.php or code — not the database.
• Content model first. Before writing a line of theme code, confirm the fields, content types, and editorial workflow are locked.

Mistakes it avoids

• Claiming code works without running it or its tests.
• Inventing APIs, package versions or settings instead of checking the installed ones.
• Changing behaviour outside the request, such as reformatting whole files or renaming public interfaces.

What a good result looks like

An example, not your task: You are starting a WordPress or Drupal site and need the content model and theme plan before you build.

• Brief and assumptions. The CMS, version and editor needs as understood, with assumptions and MISSING items.
• Content model. Each content type with its fields, links to other types and display variants.
• Theme plan. Templates and blocks to build, what each shows and how editors use it.
• Plugins and modules. What to add and what to build, with a vetting note for each add-on.
• Custom code sketches. Short drafts such as a post type, block or module hook, marked as not run.
• Accessibility and speed checks. Checks with axe-core and Lighthouse, and what a pass looks like.

How the work is checked

• The changed files build, and the relevant tests and linters pass. The commands and results are shown.
• Each change is explained in one line with its reason, and risky areas are named.
• Any check that could not run is reported as NOT_RUN with what it needs.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

Capabilities

• Discover and model. It audits the brief: page types, editor roles, links to other systems and languages. It then maps every field and relationship.
• Choose the CMS fit. If you asked, it picks Drupal or WordPress for your case and says why.
• Plan the theme. It plans design settings, templates and blocks, top down from page layout to components.
• Plan custom code. It separates what existing plugins or modules cover from what needs custom code. Types, fields and blocks are registered in code.
• Check access and speed. It lists axe-core and Lighthouse checks and a walk-through of the editor flow as a non-technical user.
• Write the launch checklist. It ends with a checklist for code, config, security headers, speed, accessibility and handoff.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id engineering-cms-developer only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/engineering-cms-developer/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• Which CMS and version: WordPress, Drupal, or 'help me choose'
• Whether the site is new or a change to an existing one
• What editors need to publish: page types, fields and who edits what
• Your design, brand colors or component list (optional)
• The plugins or modules already installed (optional)
• Other needs, such as several languages or a link to a CRM (optional)

Helpful context (optional)

• A list of your installed plugins or modules with versions.
• Your design file or a screenshot of each page layout.

Tools and access

• Claude, ChatGPT or Gemini: The plan and sketches work from a pasted profile and your brief.
• Claude Code: It can read your theme and plugin folders so the plan fits your real code.

Functions and deliverables

• WordPress and Drupal developer: Plan a WordPress or Drupal build: content model, theme, custom plugin or module, and a pre-launch checklist to run before go-live.
  • A CMS choice with reasons, if you asked for one
  • A content model: page types, fields and how they link
  • A theme plan: templates, blocks and design settings
  • A plugin or module plan that says what to add and what to build
  • Code sketches for the key parts, marked as drafts
  • A pre-launch checklist
  • Open questions
  Source: Michael Sitarzewski and Agency Agents contributors.
• Shopify theme developer: Say how your store should look. Get a built or edited theme with sections, templates and speed fixes.
  • Theme files: sections, templates and snippets
  • Theme editor settings
  • Local setup steps
  • Speed fixes
  • Deploy steps
  Source: dragnoir.
• WordPress code checker: Share a WordPress plugin or theme you may review. Get potential security, translation and speed issues to check before release.
  • Security issues with severity
  • Translation gaps
  • Performance problems
  • Suggested code fixes
  • Review checklist result
  Source: sickn33.
• Business tool launch reviewer: Check a business tool launch before go-live. Share your rollout plan and get a checklist, open blockers and a go or no-go record.
  • A readiness checklist with open items.
  • A go or no-go decision record for the owner.
  • A launch-day plan and follow-up review outline.
  Source: erphq.
• AI project context organiser: Share your project and next task. Get a short rules file, a focused file list and a clear handoff for later sessions.
  • A ready rules file for your project
  • A list of which files to load for each task
  • Rules for when to reset or trim the session
  • A checklist for spotting drifting answers
  Source: Addy Osmani.

Tasks you can use it for

• You are starting a WordPress or Drupal site and need the content model and theme plan before you build.
• You need a custom post type, plugin or module and want to know what to build and what to add from existing ones.
• Your editors find the admin confusing and you want a block or layout plan for them.
• You are about to launch and want a checklist for speed, accessibility and security.

Limits to check before starting

• Your site is slow and that is the only problem: use the WordPress performance reviewer or the Drupal Performance Engineer agent.
• You are building an online store: use the WooCommerce checkout engineer or the Drupal Commerce developer.
• Your front end is a separate Next.js or Nuxt app: use the Frontend developer.
• You need a formal accessibility audit: use the Accessibility auditor.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Download the pack and add it as a skill in your AI. Or paste SKILL.md into a new chat, then paste references/source-agent.md after it.
• Write your brief: the CMS and version, new or existing site, and what editors publish. Paste your theme or plugin list if you have one.
• Say 'Plan this build. Do not guess my CMS version.' Your AI asks once for what is missing.
• Read the content model first. Agree it with your editors before anyone writes theme code.
• Try the code sketches on a staging copy of your site. The AI cannot log in to your site or run anything.
• Run the pre-launch checklist yourself, and bring back the results from Lighthouse or axe-core.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/engineering-cms-developer for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.