Before running validation, confirm every new component has a matching `src/stories/<component-name>.stories.jsx` file (see `nebula-storybook-stories`). 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 Canva...
Scanned 9/4/2026
Install to Claude Code
Skills Directorynpx -y skills add NeverSight/skills_feed --skill nebula-component-validation --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Nebula Component Validation?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/neversight-nebula-component-validation)More formats (shields.io, HTML) on the badges page.
---
name: nebula-component-validation
description:
Validate components before uploading to Canvas. Use after creating or
modifying components, before considering work complete. Runs `npm run
code:fix` for Prettier, ESLint, and Canvas requirements.
---
# Validate
Before running validation, confirm every new component has a matching
`src/stories/<component-name>.stories.jsx` file (see
`nebula-storybook-stories`).
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.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Playbook for creating and editing uCoz landing pages via MCP tools (`templates_tool`, `ftp_tool`, `modules_tool`). Use for tasks such as: "build a landing page", "update the homepage as a landing page", "create a promo page on the homepage", "add a lead form / menu / SEO to the homepage". Homepage: `page_list`, `page_get`; first publish — `page_update` with full `page_tmpl`; HTML edits after generation — `patch_template` (module_id=2, template_id=1), not `update_template`. Activate the mail f...
Interact with the Paperclip control plane API to manage tasks, coordinate with other agents, and follow company governance. Use when you need to check assignments, update task status, delegate work, post comments, set up or manage routines (recurring scheduled tasks), or call any Paperclip API endpoint. Do NOT use for the actual domain work itself (writing code, research, etc.) — only for Paperclip coordination.
Digital Audio Workstation usage, music composition, interactive music systems, and game audio implementation for immersive soundscapes.
Instantly.ai cold email outreach API - manage campaigns, leads, accounts, and analytics. Use for cold email automation, lead management, campaign creation/monitoring, and email account warmup.
Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging, GitHub releases, and changelog generation. NPM publishing is the final human-required handoff because the maintainer raised npm security.
