Choose a recipe
Start from a heading, button, image, table, spacing, cover, media-text, columns, or global block style.
devs Tools / WordPress Rescue 1.0.0
WordPress Rescue Mode: Diagnose and package safe fixes
Choose from twelve common WordPress repair recipes, validate scope and safety, and export the same fix as Additional CSS, a block style, theme.json, a child theme, a micro-plugin, or one of eight guided outputs.
WordPress Rescue Mode is a free local-first repair workspace. Pick a symptom, narrow the selector and WordPress scope, validate the result, and export the same fix in eight installable or copy-and-paste formats.
- Processing stays in this browser
- Twelve recipes and sixty-four rules
- No automatic WordPress writes
Opening the local repair workspace…
Four-step rescue
From a symptom to an implementation package
Set scope
Use a custom class, page or post body class, or a registered Block Style before escalating specificity.
Preview and validate
Compare Front and Editor surfaces and four widths, then review scope, compatibility, accessibility, and conversion losses.
Install and verify
Copy one file or download a package that includes installation, verification, and rollback instructions.
Eight adapters
One repair project, eight outputs
| Output | Best for | Where to install |
|---|---|---|
| Additional CSS（追加CSS） | The quickest guided fix | Site Editor / Customizer |
| Block custom class（追加CSSクラス） | One selected block | Block advanced settings and CSS |
| Page/Post scoped CSS | One page or post | Additional CSS / stylesheet |
| Block Style API | A reusable editor style choice | Child theme or plugin |
| theme.json v3 fragment | Block-theme settings and styles | theme.json merge |
| Child theme（子テーマ） | Theme-bound production work | wp-content/themes |
| Micro-plugin（小さなプラグイン） | A theme-independent repair | wp-content/plugins |
| Runbook（作業手順書） | Hand-off and review | INSTALL / VERIFY / ROLLBACK |
The recommended output depends on WordPress version, theme type, target scope, and detected capabilities. The tool never pastes into WordPress automatically.
Public knowledge base
Inspect the recipes and rules before using code
Glossary
Terms used in the workspace
- Recipe（レシピ）
- A versioned repair pattern for one WordPress design problem.
- Scope（スコープ／適用範囲）
- The pages and elements a selector can affect.
- Selector（セレクター／対象指定）
- The CSS expression that selects an element.
- Specificity（詳細度）
- The CSS precedence score used when declarations compete.
- Adapter（アダプター／出力変換）
- A deterministic converter from one RescueProject to a target installation format.
- Rollback（ロールバック／元に戻す）
- A documented procedure for removing the change safely.
Safety boundary
What this version will not do
- No automatic file, database, theme, plugin, or WordPress setting writes.
- No arbitrary PHP execution, remote URL fetching, or sending project data to AI services.
- No guessing theme-private selectors and no automatic !important escalation.
- A passing report does not replace testing on the target site, devices, cache, and editor.
FAQ
Before applying a repair
Does this edit my WordPress site?
No. It only generates files and guided copy-and-paste output. You choose when and where to install them.
Which output should a beginner choose?
Start with a block custom class plus Additional CSS. It is easy to inspect and remove. Use a child theme or micro-plugin when the repair becomes reusable production code.
Why is !important not recommended?
It can hide the real cascade cause and make later maintenance harder. The tool first narrows scope and raises selector specificity in measured steps.