KS
Killer-Skills

drupal-standards — how to use drupal-standards how to use drupal-standards, drupal-standards setup guide, drupal coding standards best practices, drupal-standards vs drupal coding standards, drupal-standards install, what is drupal-standards, drupal-standards alternative, drupal development with drupal-standards, drupal-standards for PHP development

v1.0.0
GitHub

About this Skill

Perfect for PHP Development Agents needing to enforce Drupal coding standards and best practices. drupal-standards is a set of guidelines for Drupal development that ensures all code follows version-independent coding standards, US English spelling, and best practices.

Features

Applies Drupal coding standards based on development context
Enforces US English spelling in comments and names
Follows the Boy Scout Rule for code improvement
Supports PHP development for files, modules, services, and plugins
Ensures standards are always-current for new code
Detects context and loads standards for efficient development

# Core Topics

nonzod nonzod
[0]
[0]
Updated: 3/7/2026

Quality Score

Top 5%
54
Excellent
Based on code quality & docs
Installation
SYS Universal Install (Auto-Detect)
Cursor IDE Windsurf IDE VS Code IDE
> npx killer-skills add nonzod/drupaldev-claude-skill/drupal-standards

Agent Capability Analysis

The drupal-standards MCP Server by nonzod is an open-source Categories.community integration for Claude and other AI agents, enabling seamless task automation and capability expansion. Optimized for how to use drupal-standards, drupal-standards setup guide, drupal coding standards best practices.

Ideal Agent Persona

Perfect for PHP Development Agents needing to enforce Drupal coding standards and best practices.

Core Value

Empowers agents to apply version-independent Drupal coding standards, ensuring US English spelling consistency and adherence to the Boy Scout Rule, resulting in efficient development and better code quality through PHP files, modules, services, and plugins.

Capabilities Granted for drupal-standards MCP Server

Enforcing Drupal coding standards for PHP development
Validating US English spelling in code comments and names
Applying the Boy Scout Rule for improved code maintainability

! Prerequisites & Limits

  • Requires PHP development context
  • Limited to Drupal-specific coding standards
Project
SKILL.md
5.7 KB
.cursorrules
1.2 KB
package.json
240 B
Ready
UTF-8

# Tags

[No tags]
SKILL.md
Readonly

Drupal Coding Standards

Apply Drupal coding standards based on the development context.

Core Principles

From coding_standards/index.md:

  • All code must follow Drupal coding standards (version-independent)
  • Use US English spelling in all comments and names
  • Standards are "always-current" and apply to all new code
  • Follow Boy Scout Rule: leave code better than you found it

Context Detection & Standard Loading

PHP Development (.php files, modules, services, plugins)

When working with PHP code, ALWAYS read these standards FIRST:

  1. Core Standards: Read coding_standards/php/coding.md
  2. Documentation: Read coding_standards/php/documentation.md
  3. Namespaces: Read coding_standards/php/namespaces.md
  4. PSR-4: Read coding_standards/php/psr4.md

Additionally, based on specific needs:

  • Creating services → Read coding_standards/php/naming-services.md
  • Exception handling → Read coding_standards/php/exceptions.md
  • Using placeholders → Read coding_standards/php/placeholders-delimiters.md
  • Error handling → Read coding_standards/php/e_all.md
  • Documentation examples → Read coding_standards/php/documentation-examples.md

JavaScript Development (.js files)

ALWAYS read these standards FIRST:

  1. Core Standards: Read coding_standards/javascript/coding.md
  2. Documentation: Read coding_standards/javascript/documentation.md
  3. Best Practices: Read coding_standards/javascript/best-practice.md
  4. ESLint Config: Read coding_standards/javascript/eslint.md

If using jQuery:

  • Read coding_standards/javascript/jquery.md

CSS Development (.css, .scss files, styling)

ALWAYS read these standards FIRST:

  1. Core Standards: Read coding_standards/css/coding.md
  2. Formatting: Read coding_standards/css/format.md
  3. File Organization: Read coding_standards/css/file-organization.md
  4. Architecture: Read coding_standards/css/architecture.md

For tool configuration:

  • Read coding_standards/css/csscomb.md
  • Read coding_standards/css/review.md

SQL Queries (database operations)

ALWAYS read these standards FIRST:

  1. Conventions: Read coding_standards/sql/conventions.md
  2. Keywords: Read coding_standards/sql/keywords.md
  3. SELECT Queries: Read coding_standards/sql/select-from.md

Twig Templates (.twig files)

ALWAYS read these standards:

  1. Twig Standards: Read coding_standards/twig/coding.md
  2. Markup Standards: Read coding_standards/markup/style.md

YAML Configuration (.yml, .yaml files)

ALWAYS read:

  • Read coding_standards/yaml/configuration-files.md

Composer Packages (composer.json)

ALWAYS read:

  • Read coding_standards/composer/package-name.md

Accessibility (forms, UI components, interactive elements)

ALWAYS read:

  • Read coding_standards/accessibility/accessibility.md

Spelling & General

ALWAYS apply:

  • Read coding_standards/spelling/spelling.md (US English required)

Workflow

1. User requests development task
   ↓
2. Identify file types/context (PHP, JS, CSS, SQL, etc.)
   ↓
3. Read ALL relevant standard files from coding_standards/
   ↓
4. Apply standards while writing code
   ↓
5. Validate code against standards
   ↓
6. Complete task with compliant code

Multi-Context Tasks

For tasks involving multiple file types, load ALL relevant standards:

Example: Creating a custom module

  • PHP standards (module code)
  • JavaScript standards (if includes JS)
  • CSS standards (if includes styling)
  • Twig standards (if includes templates)
  • YAML standards (for .info.yml and config files)
  • Accessibility standards (if includes UI)

Application Rules

  1. Read First, Write Second: Always read relevant standards before generating code
  2. No Assumptions: Never assume standards—always verify from files
  3. Exact Compliance: Follow standards exactly as written
  4. US English Only: All comments, variable names, and documentation
  5. Complete Coverage: If working with multiple file types, apply all relevant standards
  6. Validation: Before completing, verify code against loaded standards

Examples

Example 1: Creating a PHP Service

User: "Create a service to handle user notifications"

Actions:
1. Identify: PHP service development
2. Read standards:
   - coding_standards/php/coding.md
   - coding_standards/php/documentation.md
   - coding_standards/php/namespaces.md
   - coding_standards/php/naming-services.md
3. Generate code following all standards
4. Include proper docblocks, namespaces, service naming

Example 2: Writing Database Query

User: "Write a query to get active users with roles"

Actions:
1. Identify: SQL query
2. Read standards:
   - coding_standards/sql/conventions.md
   - coding_standards/sql/keywords.md
   - coding_standards/sql/select-from.md
3. Write query with proper keyword capitalization and formatting

Example 3: Building an Accessible Form

User: "Create a contact form with validation"

Actions:
1. Identify: Multi-context (PHP form API, JavaScript validation, accessibility)
2. Read standards:
   - coding_standards/php/coding.md
   - coding_standards/php/documentation.md
   - coding_standards/javascript/coding.md
   - coding_standards/markup/style.md
   - coding_standards/accessibility/accessibility.md
3. Build form with all standards applied
4. Ensure full accessibility compliance

Critical Reminders

  • Never skip reading standards - always load them before coding
  • Standards override preferences - follow Drupal standards exactly
  • When uncertain - read additional related standard files
  • Multi-file tasks - load standards for ALL file types involved
  • US English spelling - non-negotiable requirement

Related Skills

Looking for an alternative to drupal-standards or building a Categories.community AI Agent? Explore these related open-source MCP Servers.

View All

widget-generator

Logo of f
f

widget-generator is an open-source AI agent skill for creating widget plugins that are injected into prompt feeds on prompts.chat. It supports two rendering modes: standard prompt widgets using default PromptCard styling and custom render widgets built as full React components.

149.6k
0
Design

chat-sdk

Logo of lobehub
lobehub

chat-sdk is a unified TypeScript SDK for building chat bots across multiple platforms, providing a single interface for deploying bot logic.

73.0k
0
Communication

zustand

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

72.8k
0
Communication

data-fetching

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

72.8k
0
Communication