sergekostenchuk/ui-ux-agent-skill-system

pencil-design-bridge

Bridge approved UI/UX direction briefs into Pencil design workflows without treating .pen files as plain text.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/sergekostenchuk/ui-ux-agent-skill-system --skill pencil-design-bridge

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Pencil Design Bridge

This skill is the Pencil layer in the UI/UX Agent Skill System. Pencil is a design-tool bridge and editable design workspace, not the central architect and not a plain-file parser.

Operating Modes

  • brief: turn an approved direction brief into a Pencil-ready design brief.
  • canvas-handoff: prepare instructions for Pencil MCP/tools or a Pencil-capable agent.
  • review-output: review Pencil output against UX, SEO/LLM, accessibility, brand, and implementation constraints.
  • figma-code-handoff: prepare Pencil results for Figma or code implementation.
  • config-check: check whether Pencil tools are available in the current runtime without reading .pen files directly.

Required Workflow

  1. Read references/pencil-bridge-contract.md.
  2. Confirm the source brief was approved by senior-ui-ux-orchestrator or came from an explicit user decision.
  3. Confirm inputs:
  • product/UX journey;
  • SEO/LLM constraints for public pages;
  • ui-ux-pro-max design intelligence;
  • optional Stitch output or Figma constraints;
  • required assets and forbidden claims.
  1. Use assets/pencil-handoff.template.md for handoff packets.
  2. Access .pen documents only through Pencil MCP/tools. Do not use shell reads, grep, cat, or ad hoc JSON parsing on .pen files.
  3. Treat Pencil output as a candidate design artifact. It still needs review before Figma, code, or production use.

Safety Rules

  • Do not store API keys, tokens, cookies, private URLs, private screenshots, or .env values in Pencil handoffs.
  • Do not claim a Pencil tool ran unless a callable Pencil tool was used and an artifact path or tool response exists.
  • If Pencil tooling is unavailable, produce a manual handoff and mark execution as Skipped or Planned.
  • If Pencil output conflicts with accessibility, visible facts, SEO/LLM structure, or implementation feasibility, route to council.

Handoff Shape

text
Mode:
Approved direction:
Pencil tool availability:
Input artifacts:
Data excluded:
Prompt or canvas instructions:
Design-system constraints:
Review criteria:
Next owner:
Checks:

Validation

When editing this skill, run:

bash
python3 $CODEX_HOME/skills/.system/skill-creator/scripts/quick_validate.py $CODEX_HOME/skills/pencil-design-bridge
python3 $CODEX_HOME/skills/senior-skill-architect/scripts/lint_production_skill.py $CODEX_HOME/skills/pencil-design-bridge
python3 -m json.tool $CODEX_HOME/skills/pencil-design-bridge/evals/evals.json >/dev/null

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
sergekostenchuk
コミュニティ

admin-ui-builder

Use when admin/CMS/back-office screens need to be built or specified after admin-ui-orchestrator defines roles, permissions, workflows, and safety gates. Covers tables, forms, editors, moderation queues, dashboards, CRUD surfaces, and state coverage without production destructive actions.

1時間の導入数
1
GitHub Stars
35
更新日
9月13日
sergekostenchuk
コミュニティ

admin-ui-orchestrator

Use when a project needs admin/CMS/back-office UI architecture: roles, permissions, content workflows, AI assistant boundaries, audit logs, destructive-action confirmations, and builder handoff. Planning only; do not perform production admin actions or expose secrets.

1時間の導入数
1
GitHub Stars
35
更新日
9月13日
sergekostenchuk
コミュニティ

analytics-setup-architect

Use when a website or web app needs privacy-aware analytics architecture: GA4, Yandex Metrica, self-hosted analytics, consent, UTM, event taxonomy, funnels, dashboards, and launch verification. Do not mutate real analytics accounts or store credentials without explicit approval.

1時間の導入数
1
GitHub Stars
35
更新日
9月13日
sergekostenchuk
コミュニティ

editorial-quality-gate

Review public site content for editorial quality, source support, prompt residue, duplicate blocks, translation drift, hidden filler, and human usefulness before SEO or LLM-friendly publication. Use this skill when the user asks to quality-gate news briefs, longform explainers, blog posts, topic pages, project pages, translated content, or generated article drafts without changing the live publishing pipeline.

1時間の導入数
1
GitHub Stars
35
更新日
9月13日