원클릭으로 Manus에서 모든 스킬 실행

dialtone-lookup

스타15

포크7

업데이트2026년 6월 4일 13:28

Look up Dialtone documentation, components, tokens, utilities, and icons before making design-system decisions. Use when the user asks about Dialtone APIs, docs guidance, component usage, tokens, utilities, icons, or implementation patterns.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

dialpad

dialpad/dialtone

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Dialtone Lookup

Goal

Ground Dialtone decisions in installed-version lookup data before editing or recommending API usage.

Trigger

Questions about Dialtone components, props, events, slots, examples, tokens, utility classes, icons, or docs guidance.
Work that introduces or changes component usage, token usage, utility classes, icons, or public documentation patterns.
Before implementing a UI or docs change where Dialtone conventions are uncertain.

Required Context

User question or target component/token/utility/icon/docs topic.
.agents/resources/dialtone-lookup.md
Changed source files when the lookup is part of implementation or review.

Constraints

Prefer the local ./node_modules/.bin/dialtone CLI for version-sensitive docs, component, token, utility, and icon lookup.
Use the configured Dialtone MCP server as a supplement when CLI output is insufficient or unavailable.
Do not guess component APIs, token names, or utility classes when lookup tools can answer.
Do not treat lookup results as authoritative over changed local source.
Do not add private Dialpad context to lookup queries, commits, or PRs.

Workflow

Identify whether the question is documentation guidance, component API, token, utility, icon, or mixed.
Load .agents/resources/dialtone-lookup.md.
Use the local Dialtone CLI first for installed-version evidence.
Use the Dialtone MCP server only when CLI output is insufficient, unavailable, or when a protocol tool is already the better fit.
Read changed source files before editing.
Summarize the lookup evidence and any source verification used.

Done When

The answer or implementation cites the lookup source used, such as MCP tool name or CLI command.
Any source edits are verified against local files.
Missing or failing lookup tools are reported with the fallback used.

Verification

./node_modules/.bin/dialtone --help
node .agents/evals/run-skill-contract-evals.mjs

References

.agents/resources/dialtone-lookup.md

이 저장소의 다른 Skills

같은 저장소

commit

dialpad/dialtone

Safely stage and commit Dialtone changes. Use when the user asks to stage, commit, or prepare committed work.

2026-06-0415

component-work

dialpad/dialtone

Create or update Dialtone Vue components and keep package/docs artifacts synchronized. Use when the user asks for component creation, component API changes, stories, docs, or related tests.

2026-06-0415

doc-sync-check

dialpad/dialtone

Check whether source changes need Dialtone AI docs updates. Use before PR prep/create or when source package behavior changes.

2026-06-0415

pr-comments

dialpad/dialtone

Triage and address Dialtone GitHub PR review comments. Use when the user invokes $pr-comments, $address-review, or asks to handle review feedback.

2026-06-0415

pr-complete

dialpad/dialtone

Complete merged Dialtone PR follow-up safely. Use after a PR has merged or when closing out a local PR branch.

2026-06-0415

pr-create

dialpad/dialtone

Prepare, create, or update a Dialtone pull request. Use when the user invokes $pr-create, asks to open a PR, or asks to fill a PR description.

2026-06-0415

name	dialtone-lookup
description	Look up Dialtone documentation, components, tokens, utilities, and icons before making design-system decisions. Use when the user asks about Dialtone APIs, docs guidance, component usage, tokens, utilities, icons, or implementation patterns.

Dialtone Lookup

Goal

Ground Dialtone decisions in installed-version lookup data before editing or recommending API usage.

Trigger

Questions about Dialtone components, props, events, slots, examples, tokens, utility classes, icons, or docs guidance.
Work that introduces or changes component usage, token usage, utility classes, icons, or public documentation patterns.
Before implementing a UI or docs change where Dialtone conventions are uncertain.

Required Context

User question or target component/token/utility/icon/docs topic.
.agents/resources/dialtone-lookup.md
Changed source files when the lookup is part of implementation or review.

Constraints

Prefer the local ./node_modules/.bin/dialtone CLI for version-sensitive docs, component, token, utility, and icon lookup.
Use the configured Dialtone MCP server as a supplement when CLI output is insufficient or unavailable.
Do not guess component APIs, token names, or utility classes when lookup tools can answer.
Do not treat lookup results as authoritative over changed local source.
Do not add private Dialpad context to lookup queries, commits, or PRs.

Workflow

Identify whether the question is documentation guidance, component API, token, utility, icon, or mixed.
Load .agents/resources/dialtone-lookup.md.
Use the local Dialtone CLI first for installed-version evidence.
Use the Dialtone MCP server only when CLI output is insufficient, unavailable, or when a protocol tool is already the better fit.
Read changed source files before editing.
Summarize the lookup evidence and any source verification used.

Done When

The answer or implementation cites the lookup source used, such as MCP tool name or CLI command.
Any source edits are verified against local files.
Missing or failing lookup tools are reported with the fallback used.

Verification

./node_modules/.bin/dialtone --help
node .agents/evals/run-skill-contract-evals.mjs

References

.agents/resources/dialtone-lookup.md