본문으로 건너뛰기
cccskills
무료GitHub에 공개

home-assistant-card

Use when creating, reviewing, debugging, or maintaining Home Assistant custom Lovelace cards or card editors, including custom elements, Web Components, hass data, setConfig, getCardSize/getGridOptions, getConfigElement/getConfigForm, window.customCards, resource registration, HACS card packages, entity display, service calls, translations, or frontend build validation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

denysdovhan/agents
설치 방법 보기

포함된 파일(8)

  • SKILL.md3.8 KB
  • agents/openai.yaml326 B
  • assets/home-assistant.png11.2 KB
  • README.md248 B
  • references/card-examples.md4.3 KB
  • references/card-patterns.md3.1 KB
  • references/card-workflow.md2.2 KB
  • references/frontend-docs.md1.9 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Home Assistant Card Skill

Use this skill for Home Assistant custom card development. Custom cards are Web Components; any framework that defines custom elements can work. Lit and helper libraries are optional unless the repo already uses them.

This is separate from Python integrations, automations, scripts, helpers, and ordinary dashboard YAML. Use those skills unless the work changes a custom card package, registration, editor, or card usage contract.

Start With Current Docs

Fetch current markdown from the Home Assistant developers docs repository before changing card APIs. All doc paths in this skill's references are relative to this base URL — prepend it when fetching:

https://raw.githubusercontent.com/home-assistant/developers.home-assistant/master/docs/

Use rendered pages on developers.home-assistant.io only as secondary reading. Fetch only relevant files, and do not copy Home Assistant docs into generated skill or repo files.

Use references/frontend-docs.md as the docs routing index. The most important source is frontend/custom-ui/custom-card.md.

Local Workflow

  1. Inspect local instructions first: AGENTS.md, package scripts, README, HACS metadata, build config, source entrypoints, card/editor files, translations, and release notes.
  2. Preserve the existing architecture and framework. Do not convert frameworks, add helper libraries, or add build tooling unless required.
  3. Read the relevant reference: references/card-workflow.md for repo structure and validation, references/card-patterns.md for card API patterns, references/card-examples.md for card/editor examples, and references/frontend-docs.md for current docs.
  4. Keep diffs surgical. Work with dirty worktrees; never revert unrelated edits.
  5. Prefer explicit config validation/defaulting in setConfig or a local helper. A buildConfig helper is a useful pattern, not a requirement.
  6. Use Home Assistant frontend data and APIs deliberately: hass.states, hass.localize, hass.callService, custom events, card sizing, editor APIs, and resource registration.
  7. Handle unavailable or missing entities without crashing the whole dashboard.
  8. For card editors, dispatch config-changed with the full updated config and preserve existing editor UX.
  9. Run repo-local validation, usually npm test, npm run lint, npm run build, or equivalent scripts. For dependency changes in public repos, keep lockfiles and package-manager config free of private or machine-local registry URLs.

Scaffolding Guidance

When scaffolding a new card, copy the repo's preferred structure if one exists. Minimum shape is a JavaScript module that defines a custom element and is registered as a dashboard resource with type module. Add TypeScript, bundling, visual editors, translations, HACS metadata, screenshots, or release automation only when requested or already expected.

Review Checklist

Before finishing:

  1. Re-fetch the relevant current docs.
  2. Confirm the custom element name, dashboard custom: type, and resource URL still match.
  3. Check setConfig, defaults, missing-entity handling, unavailable state, card sizing, editor updates, and card picker metadata.
  4. Verify service calls use the intended domain, service, data, and target shape.
  5. Check translations, HACS metadata, generated bundle expectations, and public-registry hygiene if dependencies changed.
  6. Run local validation scripts and report any commands that could not be run.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

agent-log

무료

Use this skill to maintain an agent log in .agents/log, a decision journal shared by the developer and agents. Trigger when the user explicitly asks to use agent-log or record/update an agent log entry; when planning, implementing, or finalizing a significant feature in a repo with an existing .agents/log; or before non-trivial changes or questions in areas covered by existing entries. Never initialize .agents/log unless the user explicitly asks for an agent log.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

denysdovhan/agents182026년 7월 29일 업데이트

commit

무료

Use this skill when an agent needs to prepare a focused commit, follow repository commit-message conventions, write a clear commit message, and create the git commit cleanly.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

denysdovhan/agents182026년 7월 29일 업데이트

home-assistant-integration

무료

Use this skill when creating, scaffolding, reviewing, or maintaining Python Home Assistant custom integrations, including work on custom_components, manifests, config flows, options flows, config entries, platforms/entities, DataUpdateCoordinator, integration automation triggers, diagnostics, repairs, discovery/networking, authentication, HACS-ready repositories, or Home Assistant integration quality scale compliance.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

denysdovhan/agents182026년 7월 29일 업데이트

interactive-debugging

무료

Use this skill when debugging runtime behavior requires live data from the running app, temporary instrumentation, or hypothesis verification through logs. Trigger for async timeouts, stale or incorrect state updates, race conditions, event ordering bugs, intermittent failures, browser/client behavior that static inspection cannot explain, or any issue where the agent should create a local debug HTTP server, insert temporary probes, ask the user to reproduce, inspect .debug/debug.log, then remove all debug instrumentation and assets.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

denysdovhan/agents182026년 7월 29일 업데이트

denysdovhan의 스킬 모두 보기

이 스킬의 문제 신고