메뉴
Search and fetch official Drupal documentation from drupal.org and api.drupal.org. Matches natural language queries against a curated URL catalog and retrieves relevant documentation pages. Use when you need authoritative Drupal documentation.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when reviewing Drupal code for standards compliance across PHP, JavaScript, CSS, Twig, YAML, SQL, and markup — dynamically loads relevant standards per file type using Drupal's official community guidelines.
How to write, modify, and style React components for Drupal Canvas and Drupal CMS. Covers the technology stack (React 19, Tailwind CSS 4, CVA variants, cn utility), component.yml prop and slot definitions, enum naming, image and video prop types, formatted text fields, color scheme variants, theme tokens from global.css, required folder structure (index.jsx + component.yml), and matching source site visual styles including extracting design tokens, dark backgrounds, gradient text, glass/blur effects, and updating global.css theme. Use when building, editing, or fixing any component in src/components/.
Managing content in Drupal CMS via JSON:API. Covers listing, fetching, creating, updating, and deleting pages and content entities using npm run content commands. Includes page component structure (uuid, component_id, inputs, parent_uuid, slot), image uploading and media target_id handling, formatted HTML text fields, UUID generation, input format reference mapping component.yml prop types to JSON formats, menu item listing (menu_items--main, menu_items--footer, menu_items--social-media are read-only via API — must use admin UI for create/update/delete), page path alias management, and common pitfalls like wrong media IDs, link props as objects instead of strings, plain strings for HTML fields, target_id as integer instead of string, langcode errors, and JSON:API read-only mode. Use when composing pages, adding components to pages, uploading images, or interacting with the Drupal CMS content API.
Search and fetch Canvas and Drupal CMS documentation pages. Takes a query describing what you need to know (e.g., "code components", "page regions", "known issues", "data fetching") and returns the full content of matching documentation pages. Invoke with /canvas-docs-explorer <query>. Use this whenever you need to understand how Canvas or Drupal CMS works, verify platform behavior, check for limitations, or find configuration options.
Use when setting up a new Drupal CMS project with Canvas for component development. Covers DDEV, JSON:API write mode, Canvas OAuth client, permissions, page regions, menus, project scaffolding, .env, CSS layer fix, and Storybook validation. Every step is idempotent — safe to re-run.
Step-by-step guide for scaffolding a new React component from scratch. Covers copying an existing component as a base, creating the required index.jsx and component.yml files, naming conventions (snake_case machineName, no project prefixes), creating the matching Storybook story file, reusing existing components via imports, composability patterns, and internal component setup (status false). Use when a needed component does not yet exist in src/components/ and must be created.
| name | drupal-docs-explorer |
| description | Search and fetch official Drupal documentation from drupal.org and api.drupal.org. Matches natural language queries against a curated URL catalog and retrieves relevant documentation pages. Use when you need authoritative Drupal documentation. |
Fetch and return official Drupal documentation relevant to a query. This skill searches a curated catalog of essential drupal.org and api.drupal.org URLs, identifies the most relevant pages, fetches their full content, and returns it for the calling agent to use.
$1 — Query (required). A natural language description of what you need to know. Examples:
"entity API field definitions""how to create a custom module""form API validation and submission""routing and controllers""services and dependency injection""configuration management export import""caching strategies and cache tags""Twig theming and templates""hook system event subscribers""automated testing PHPUnit"You are a fast research agent. Your job is to find and fetch documentation, not to analyze or act on it. Return the raw content so the calling agent can use it.
Read the URL catalog file at references/drupal-docs-urls.md (in this skill's directory). This contains all curated Drupal documentation URLs organized by category, each with a brief description of its content.
From the catalog, identify all pages relevant to the query. Match by:
/entity-api, /entity, /content-entities)/creating-modules, /module-file, /info-yml, /hooks, /routing-system)Be generous with matching — it is better to fetch an extra page than to miss a relevant one. But stay focused: do not fetch unrelated categories unless the query is broad.
Matching guidelines:
For each matched URL, fetch the URL content to retrieve the page. Fetch pages in parallel where possible for speed.
When fetching, extract the complete content of each page. Return all text, code examples, tables, steps, warnings, and notes. Do not summarize — return everything.
If a URL redirects, follow the redirect and note the final URL in the output.
Return all fetched content organized by page, with clear headers:
## <Page Title> — <URL>
<full page content>
---
## <Next Page Title> — <URL>
<full page content>
If a page fails to load (404, 503, timeout), note the failure and continue with remaining pages. Suggest the user check whether the URL has moved by searching drupal.org directly.
The URL catalog at references/drupal-docs-urls.md is a manually curated list. To maintain it: