skills.rest
acquia
acquiaOFFICIAL
Explore all skills by this author →
WebsiteGitHub

nebula-project-structure

Detect repository layout and package manager from config and lock files.

16|6|Updated Feb 19, 2025
Search Tags:#lockfiles#project-structure#package-manager#repo-navigation#nebula#canvas-workbench
One-click install
npx skills add https://github.com/acquia/nebula --skill nebula-project-structure
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nebula-project-structure
Source: https://github.com/acquia/nebula/tree/main/.agents/skills/nebula-project-structure
Command: npx skills add https://github.com/acquia/nebula --skill nebula-project-structure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill removes uncertainty about where to find working components, pages, and global styles in the Nebula codebase and ensures you run commands with the correct package manager.

Core Features & Use Cases

  • Repository layout reference: Describes the separation between working code and example components and where component preview mocks are stored so developers know where to edit or copy from.
  • Package manager detection: Explains how to detect npm, yarn, pnpm, or bun by checking for lock files and which command forms to use for each manager.
  • Configuration awareness: Notes that canvas.config.json, when present, is the source of truth for componentDir, pagesDir, and globalCssPath.
  • Use Case: Before running scripts or launching Canvas Workbench, use this guidance to locate src/components and pages and to pick the appropriate package manager for consistent commands.

Quick Start

Locate the project's component and pages directories and determine the correct package manager by inspecting canvas.config.json and root lock files.

Frequently Asked Questions about nebula-project-structure

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect the correct package manager for a repository?▼

Package manager detection is done by inspecting root lock files such as package-lock.json, yarn.lock, pnpm-lock.yaml, and bun.lockb to identify npm, yarn, pnpm, or bun.

Where do I find working components and pages in a Nebula project?▼

Find working Nebula components and pages by inspecting canvas.config.json, which serves as the source of truth for mapping componentDir, pagesDir, and globalCssPath.

What is the best way to navigate project structure before running scripts?▼

The best way to navigate project structure is to inspect canvas.config.json and lock files to locate src/components and pages and pick the appropriate package manager for consistent commands.

Does canvas.config.json work with both Nebula and Canvas Code Component projects?▼

Yes, canvas.config.json works with both Nebula and Canvas Code Component projects to map directories like componentDir, pagesDir, and globalCssPath when navigating code or preparing development commands.

Why does package manager detection matter for launching Canvas Workbench?▼

Package manager detection matters because running Canvas Workbench requires consistent command forms; inspecting lock files ensures you use the correct npm, yarn, pnpm, or bun execution syntax.

Related Skills

Explore More Software Engineering Skills→
MadeAgentsMadeAgents
22

send-owner-clone-message

Send friend or group messages using the TopoClaw owner's digital clone identity via the customer_service API.

Official
Intermediate
balintbrewsbalintbrews
14

canvas-workbench

Start the local Canvas Workbench server and verify components via the package runner.

Community
Intermediate
MacPhobosMacPhobos

Git Worktrees

Manage multiple Git worktrees for parallel development in separate directories.

Community
Intermediate
rsmdtrsmdt
381

framework-detection

Detect framework, language, and package manager from codebase files.

Community
Advanced