elevarus-admin

elevarus-admin/agent-example

Command Claude Code

One item, one PR, then stop. You never merge. Read knowledge/engine.md for the engine map and the exact verify commands.

elevarus-admin/agent-example

Agent Claude Code

Verifies a factual claim (incentive, tax, rebate, net-metering, electricity-rate, installer) against live sources via Perplexity, returning a verdict + the REAL source URL. The truth backstop for SolarFY pages — especially the 25D federal-credit trap.

elevarus-admin/agent-example

Agent Claude Code

READ-ONLY. Gathers the cited, locally-specific data bundle for one SolarFY target (city or utility) by running the solar-data scripts (EIA rate, PVWatts production, DataForSEO SERP+keywords, Perplexity/Tavily incentives/net-metering/news/installers). Returns a structured JSON bundle with sources. Never writes pages.

elevarus-admin/agent-example

Command Claude Code

The proven procedure (built docs/solarfy/samples/boston-solar.md this way). One target, then stop. Draft only. solar-wordpress-developer publishes after a human approves.

elevarus-admin/agent-example

Command Claude Code

A bounded procedure for changing a funnel. Read the relevant knowledge/ files first.

elevarus-admin/agent-example

Command Claude Code

Reference: knowledge/deploy.md. Never deploy without a passing QA pass (commands/qa.md). Targeted to ONE funnel folder — never the WP base.

elevarus-admin/agent-example

Command Claude Code

Full reference (dimensions, severity bar, Playwright setup) is in knowledge/qa.md. This is the run procedure.

elevarus-admin/agent-example

Command Claude Code

Plan + queue only. One cycle, then stop.

elevarus-admin/agent-example

Agent Claude Code

The SolarFY fleet's single image engine. Produces ONE on-brand SolarFY image (isometric scene illustration OR flat data infographic, Clean Daylight palette) from a brief, end to end: craft the nano-banana prompt, generate, run the QA/QC checklist by VIEWING it, upload to WP media with alt text, and return the media id…

elevarus-admin/agent-example

Agent Claude Code

Executes ONE SAFE-AUTO WordPress fix — snapshot -> wp-cli apply -> verify-live -> auto-rollback on failure. Surgical, claim-preserving technical fixes only (heading tag, Rank Math meta length/typo, alt text, canonical-fix). Never a content/visual/claim change, never a slug, never WP core.

elevarus-admin/agent-example

Agent Claude Code

Runs a RICH, human-gated WordPress page edit — restyle to brand, copy rewrite, new images, layout/shortcode changes, new pages. Researches, composes, shows a before->after preview, WAITS for human approval, then saves + verifies-live. Never bypasses the approval gate, never changes a slug or compliance copy.

elevarus-admin/agent-example

Agent Claude Code

READ-ONLY. Reads a MySolarFY WordPress page's postcontent (Flatsome UX Builder shortcodes) + Rank Math meta, maps its sections, and locates the EXACT shortcode/section/field a directive targets, quoting the current value as evidence. Never edits.

elevarus-admin/agent-example

Command Claude Code

The first-task procedure: bring one page to the Clean Daylight brand AND sharpen its copy + Rank Math SEO. This is a HUMAN-GATED change — compose and preview, get approval, then save + verify. Run it one page at a time.

elevarus-admin/agent-example

Agent Claude Code

Files exactly ONE evidence-backed directive into solardirectives for one fleet agent, idempotent on its ref. Turns a synthesized finding into concrete, guardrail-respecting guidance. Never files more than one row, never instructs an agent toward a guardrail breach.

elevarus-admin/agent-example

Agent Claude Code

READ-ONLY. Reads the whole SolarFY fleet's recent activity from Supabase (per-agent cursor + content log, backlog counts by targettype, recent gate verdicts with the top recurring block cause, and the board) and returns a structured cross-agent synthesis as strict JSON. Never writes anything.

elevarus-admin/agent-example

Agent Claude Code

Evaluates ONE open solar-content-engine PR against the director's GUARDRAIL-9 auto-merge gate and merges it to main with gh pr merge --squash ONLY if every condition holds. Otherwise leaves it open and reports why. Never merges human WIP, never bypasses the gate, never pushes main directly.

elevarus-admin/agent-example

Command Claude Code

No writes, no directives, no merges. Just answer "what is the fleet doing right now" in plain language. This is the default the launcher boots to (supervised-first).

elevarus-admin/agent-example

Command Claude Code

Run ONE cycle, then stop. Kill-safe, resumable, idempotent. You read, synthesize, and file a few directives; you never write a page or push main (except the gated PR merge in PHASE 5). Read knowledge/fleet.md first for the exact db.mjs calls.