사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/sergekostenchuk/ui-ux-agent-skill-system --skill figma-context-reader시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Figma Context Reader
Use this skill to turn Figma context into an evidence-backed design brief. This is a read-only skill; route mutations to figma-canvas-editor or figma-design-system-sync.
Modes
frame-brief: summarize a selected frame or page.component-brief: summarize components, variants, props, and constraints.token-brief: summarize variables, styles, color roles, spacing, radius, typography, and effects.audit-input: collect enough Figma evidence forux-audit-skillordesign-critic-skill.handoff: prepare context for implementation specialists.
Workflow
- Confirm the input type: Figma URL, selected node, file key, screenshot/export, or connected MCP selection.
- Apply
../../shared/privacy-policy.md. - If a
use_figmacall is needed, first invoke the installedfigma:figma-useskill. - Read only the needed nodes, variables, components, styles, and assets. Avoid broad file scans unless the user asks for library/system work.
- Produce a structured context brief with evidence labels. Distinguish direct Figma metadata from visual inference.
- If MCP access is unavailable, ask for an export, screenshot, node metadata, or manual Figma details as fallback.
Output Shape
Use assets/context-brief-template.md.
Evidence Rules
Figma metadata: node names, type, layout fields, variables, styles, component names, asset references.Visual inference: hierarchy, attention, density, likely intent, visual polish.Missing: anything not available from the current Figma context.
Do not claim DOM, runtime behavior, accessibility scan, or implementation evidence from Figma context alone.
Validation And Eval
- Check that the final brief names the evidence source and privacy mode.
- Check that every implementation claim is traceable to Figma metadata, visual inference, or an explicit missing-context note.
- Use
evals/evals.jsonfor forward tests that distinguish connected Figma context from screenshot-only input.
Resources
- Read
$CODEX_SKILLS_DIR/senior-figma-orchestrator/references/figma-mcp-compatibility.mdwhen tool availability is unclear. - Use assets/context-brief-template.md for reports.
