# Nebula Component Validation

> Validate components after creating or modifying components, and after page work that changes rendered output, before considering work complete. Runs `npm run code:fix` for static validation.

- Skill: `acquia/nebula-component-validation` (Agent Skill)
- Install (CLI): `npx skillmds@latest add acquia/nebula-component-validation`
- Raw SKILL.md: https://api.skillmd.com/api/skills/acquia/nebula-component-validation/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- Author: acquia (https://skillmd.com/u/acquia)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/acquia/nebula-component-validation

---


# Validate

Before running validation, confirm the Workbench preview coverage matches the
change:

- Every new or modified component is reviewable through `component.yml`
  examples, and through `mocks.json` when additional named states are needed
- Any page work is represented as a valid Workbench page JSON file in the
  configured pages directory for this repo (`pages/`)

After creating or modifying components, always validate your code by running the
`code:fix` script. Make sure to use the right package manager. For example, if
using npm, run the following command:

```bash
npm run code:fix
```

This runs Prettier and ESLint with auto-fix, ensuring:

- Consistent formatting
- Common issue detection
- Drupal Canvas Code Component requirements

If errors remain after auto-fix, address them manually and re-run until passing.

When the task changes rendered output, this skill ends at static validation.