configure-project-includes

Configure likec4.config.json includes and image aliases for multi-file LikeC4 projects.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage LikeC4.config.json includes and imageAliases to ensure relative paths are preserved and existing configuration is maintained across multi-file C4 projects.

Core Features & Use Cases

  • Multi-file organization support: Organize model, views, deployment, and operations files without conflicts.
  • Relative-path preservation: Maintains consistent include paths when updating from templates.
  • Image alias consistency: Enforces imageAliases mapping, e.g., "@" to a shared images directory.

Quick Start

Update the likec4.config.json to reference shared paths, for example including "../shared" in "include.paths" and setting "imageAliases" to {"@": "../shared/images"}.

Frequently Asked Questions about configure-project-includes

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

FAQPage Schema
How do I manage LikeC4 includes across multiple files without breaking relative paths?▼

To manage LikeC4 includes, standardize the likec4.config.json file to preserve relative paths and prevent overwriting existing configurations. This standardizes multi-file C4 projects by organizing model, views, deployment, and operations files without conflicts.

What is the best way to structure a multi-file LikeC4 project?▼

The best way to structure a multi-file LikeC4 project is to separate system-model, system-views, deployment, and operations files. Using standardized include paths in likec4.config.json ensures these components remain organized without path conflicts.

How do I configure image aliases in likec4.config.json?▼

Configure image aliases in likec4.config.json by mapping keys to shared directories, such as setting "imageAliases" to {"@": "../shared/images"}. This enforces image alias consistency and maintains the mapping across multi-file setups.

Why does updating my LikeC4 template overwrite existing configuration paths?▼

Updating templates overwrites existing configuration paths when relative path conventions are not enforced. Standardizing likec4.config.json includes preserves defaults and maintains existing configurations during multi-file project updates.

Can I maintain a shared images directory across multiple LikeC4 files?▼

Yes, you can maintain a shared images directory across multiple LikeC4 files by enforcing the imageAliases mapping in likec4.config.json. Setting an alias like "@" to "../shared/images" ensures consistent image references across the project.