メニュー
Loads and applies the project's configured style guide. Hard stops if config or any required piece is missing. All style rules come from the guidelines file set during /init style.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | content-style |
| description | Loads and applies the project's configured style guide. Hard stops if config or any required piece is missing. All style rules come from the guidelines file set during /init style. |
| user-invocable | false |
| disable-model-invocation | false |
This skill provides style rules for content creation and review. All rules come from the project's configured guidelines file — nothing is hardcoded here.
Before applying any style rules, verify the following are present in .content-ops/config.md. Stop immediately if any are missing:
| Required | Config key | If missing |
|---|---|---|
| Config file | .content-ops/config.md exists | "Run cp .claude/plugins/content-ops/config.example.md .content-ops/config.md then /init." |
| Word range | content_types.<type>.word_range | "Run /init content-types to configure content types." |
| Guidelines list | content_types.<type>.guidelines (must be a non-empty list) | "Run /init style to generate your style guides." |
| General guide exists | .content-ops/content-styles/general.md exists on disk | "Run /init style — general style guide not found." |
| Type-specific guide exists | The type-specific guide from the list exists on disk | "Run /init style — no structure guide found for [type]." |
| Reference content | reference_content | "Run /init style to configure reference content." |
Read the content_types.<type>.guidelines list from config. This is a list of file paths.
Loading order:
.content-ops/content-styles/general.md is in the list. If missing, add it — the general guide is always loaded regardless of what the config lists.general.md first. This file is the authoritative source for cross-cutting style rules: voice, tone, jargon policy, anti-patterns, and examples.content-styles/article.md). This file is the authoritative source for structural rules: sentence length, paragraph density, opening/closing conventions.Apply only the rules defined in the loaded files. Do not apply rules not present in the guidelines.
Read the files in reference_content to calibrate tone before writing or reviewing.
Frontmatter fields per content type come from content_types.<type>.frontmatter in config, set during /init content-types.
Linking review and enforcement is handled by the content-linker agent, not by this skill.
Create content of any configured type from a topic or from the content backlog. Orchestrates research, writing, style review, glossary creation, linking, and reindexing as focused sub-agents. Hooks handle tracker updates and build verification automatically.
content-seo setup wizard. Run /init to see status, or /init [round] to run a setup step. Rounds: project, credentials, strategy.
Site-level SEO intelligence. Routes to one of five workflows — status (site-wide GSC performance), opportunities (pages ranking 4–20), diagnose (deep-dive a page with GSC data + fixes), brief (keyword research before writing), or coverage (audit GSC indexing errors from a CSV export).
content-ops setup wizard. Run /init to see status, or /init [round] to run a setup step. Rounds: project, content-types, style, strategy, infra, images, link-building.
Identify content gaps and add suggestions to the backlog. Accepts an optional freeform payload to narrow scope. Without a payload, surveys the full corpus against pillars. Powered by the backlog-suggester agent.
Review content for tone, style, structure, glossary coverage, and linking completeness against the style guide.