菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
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.
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.
Interact with Linear.app for issue tracking. Use when working with Linear tickets (format ABC-123), creating issues, updating status, or downloading attachments. Triggers on ticket references, issue management, or when user mentions Linear.
| name | adr |
| description | 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. |
| allowed-tools | Read, Write, Edit, Bash, Glob, Grep |
Create and manage ADRs in packages/web/src/content/docs/docs/contributing/adrs/ to document significant architectural decisions. ADRs are published on the docs site under Contributing.
Suggest creating an ADR when detecting:
domain/, api/, services/, models/prisma/schema.prisma modifiedtsconfig.json, eslint.config.js significantly changedSkip ADR suggestion for:
tests/, *.test.ts, *.spec.tspackages/web/src/content/docs/docs/contributing/adrs/~/.claude/plans/ for contextgit log --since="7 days ago" --onelinepackages/web/src/content/docs/docs/contributing/adrs/packages/web/src/content/docs/docs/contributing/adrs/index.mdList existing ADRs: ls -1 packages/web/src/content/docs/docs/contributing/adrs/*.md | grep -v index
Use Michael Nygard format in packages/web/src/content/docs/docs/contributing/adrs/NNN-kebab-case-title.md:
---
title: 'ADR-XXX: Title'
description: One-sentence summary of the decision.
---
**Status:** Accepted
**Date:** YYYY-MM-DD
**Authors:** [Names]
## Context
[What is the issue we're solving? What forces are at play?]
## Decision
[What is the change we're making?]
## Rationale
[Why is this the right choice?]
## Consequences
### Positive
- [Benefit 1]
### Negative
- [Tradeoff 1]
## Related Commits
- `hash` - commit message
User asks: "Document the recent API versioning changes" Action: Create ADR covering the v1 prefix, Zod validation, and thin client decisions
After refactoring: When Claude completes a significant refactor, proactively suggest documenting the decision
Reviewing work: When asked to review recent architectural changes, check if ADRs exist and suggest creating them if missing