create-element

Create LikeC4 elements with PascalCase kinds, camelCase names, and required metadata.

5|1|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/a-scolan/c4-template --skill create-element
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-element
Source: https://github.com/a-scolan/c4-template/tree/main/.github/skills/create-element
Command: npx skills add https://github.com/a-scolan/c4-template --skill create-element

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that LikeC4 elements are created with proper naming (PascalCase kinds, camelCase instance names) and include mandatory metadata (technology, description) while enforcing correct hierarchy.

Core Features & Use Cases

  • Enforces naming conventions for element kinds (PascalCase) and instance names (camelCase).
  • Validates that each element includes required metadata (technology, description).
  • Guides users to consult the shared spec first (read-project-summary) and to place elements in the correct C4 hierarchy (C1 Context, C2 Container, C3 Component).
  • Encourages reuse of existing kinds from the shared spec to maintain consistency across models.

Quick Start

Create a new LikeC4 element skeleton by running the skill to generate a properly named element with the required metadata and correct hierarchy.

Frequently Asked Questions about create-element

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

FAQPage Schema
How do I enforce naming conventions for LikeC4 elements?

Mandatory metadata for LikeC4 elements includes specific technology and description fields, ensuring proper documentation and correct parent placement within the C1, C2, or C3 hierarchy contexts.

What is the correct way to structure a C4 model hierarchy in LikeC4?

The correct way to structure a C4 model hierarchy in LikeC4 involves placing elements accurately within C1 Context, C2 Container, or C3 Component levels while adhering to established parent placement rules.

Do I need to reuse existing element kinds when creating LikeC4 elements?

You need to reuse existing element kinds from the shared spec to maintain consistency across C4 models, which involves consulting the project summary before creating or updating elements.

Can I create a LikeC4 element without a technology or description field?

You cannot create a proper LikeC4 element without technology and description fields, as these are mandatory metadata requirements enforced to ensure complete and valid architecture documentation.