Sync the local LikeC4 syntax guide with the upstream LikeC4 skills repository (github.com/likec4/likec4/tree/main/skills/likec4-dsl). Use when the user asks to update, sync, or check the LikeC4 syntax guide, when upstream LikeC4 DSL changes are suspected, or when mentioning likec4 syntax sync, DSL drift, or syntax guide update.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Keep packages/core/src/adapters/likec4/prompts/likec4-syntax-guide.md in sync
with the canonical upstream LikeC4 DSL skill at likec4/likec4.
Our guide is injected into every model-patch prompt via {{syntaxGuide}}, so it
must stay both accurate and concise (under 40 lines).
Fetch the relevant upstream files using gh api:
gh api repos/likec4/likec4/contents/skills/likec4-dsl/SKILL.md --jq '.content' | base64 -d
gh api repos/likec4/likec4/contents/skills/likec4-dsl/references/model.md --jq '.content' | base64 -d
gh api repos/likec4/likec4/contents/skills/likec4-dsl/references/identifier-validity.md --jq '.content' | base64 -d
gh api repos/likec4/likec4/contents/skills/likec4-dsl/references/specification.md --jq '.content' | base64 -d
Only these files contain model-patching-relevant syntax. Skip all others.
Read the local file at packages/core/src/adapters/likec4/prompts/likec4-syntax-guide.md
and compare against upstream for changes in these areas:
ID = KIND and KIND ID), nesting, property order-[KIND]->, .REL_KIND), this/ittitle, summary, description, notes, technology, #tag, link, metadataextend FQN { } for elements, extend SOURCE -> TARGET for relationshipsExplicitly skip (not relevant to model-patching): views, deployment, CLI commands, styling/shapes/colors/icons, dynamic views, predicates, wildcards, project configuration, response discipline, eval guidance.
Apply changes to the local file following these rules:
## LikeC4 DSL SYNTAX REFERENCE headingnpm run test
Confirm:
## LikeC4 DSL SYNTAX REFERENCEまだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Create and manage Architecture Decision Records (ADRs). Use when making architectural changes (refactoring, API versioning, new domain layers, schema changes), when reviewing recent commits for documentation needs, or when the user mentions ADR, architecture decisions, or documenting technical decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Detect documentation and architecture-model drift by comparing source-of-truth code (CLI commands, flags, env vars, GH Action inputs/outputs, package structure, pipeline stages, providers, adapters, platforms) against web docs, README, and LikeC4 architecture model (.c4 files). Use when files that define the user-facing interface or internal structure change, when the user asks to check docs, or when mentioning doc drift, architecture drift, stale docs, or documentation sync.
日本語の概要は準備中です。原文の説明を表示しています。
Enforce the project's documentation voice when writing or reviewing public-facing content. Triggers on edits to doc files (packages/web/src/content/docs/**/*.md) and README.md. Catches LLM prose patterns, marketing language, and messaging drift.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill whenever code changes introduce new imports, API calls, database connections, message queues, or service-to-service communication. Also use before any commit or push. Catches undeclared dependencies and architecture violations using Erode.
日本語の概要は準備中です。原文の説明を表示しています。
Generate product pitch videos for the Erode project from screenshots. Use this skill whenever the user wants to create, update, or regenerate the product demo video, landing page animation, or pitch clip for erode.dev or the GitHub repo. Also trigger when the user mentions "product video", "demo video", "pitch video", "update the video", "regenerate video", or "landing page animation" in the context of Erode.
日本語の概要は準備中です。原文の説明を表示しています。
Conventional commits with project conventions. Use when the user asks to commit, make a commit, or wants to follow the project's git commit standard.
日本語の概要は準備中です。原文の説明を表示しています。