- name
SKILL.md
ไฟล์สกิลยังคงอยู่ในรีโพซิทอรีของผู้เผยแพร่
วางคำสั่งที่คัดลอกไว้ในเทอร์มินัล คำสั่งจะติดตั้ง SKILL.md นี้ลงในเอเจนต์ตัวนั้น
npx skills add BlackBeltTechnology/pi-agent-dashboard --skill frontend-mockup-loop-dashboard -a cursor -yวางคำสั่งที่คัดลอกไว้ในเทอร์มินัล คำสั่งจะติดตั้ง SKILL.md นี้ลงในเอเจนต์ตัวนั้น
npx skills add BlackBeltTechnology/pi-agent-dashboard --skill frontend-mockup-loop-dashboard -a claude-code -yวางคำสั่งที่คัดลอกไว้ในเทอร์มินัล คำสั่งจะติดตั้ง SKILL.md นี้ลงในเอเจนต์ตัวนั้น
npx skills add BlackBeltTechnology/pi-agent-dashboard --skill frontend-mockup-loop-dashboard -a codex -yวางคำสั่งที่คัดลอกไว้ในเทอร์มินัล คำสั่งจะติดตั้ง SKILL.md นี้ลงในเอเจนต์ตัวนั้น
npx skills add BlackBeltTechnology/pi-agent-dashboard --skill frontend-mockup-loop-dashboard -a grok -yส่งข้อความที่คัดลอกไว้ในแชต Grok Bot แล้ว Bot จะดึง SKILL.md นี้จาก GitHub และเพิ่มลงในสกิลที่ Bot ทุกตัวของคุณใช้ร่วมกัน
Install this skill: https://github.com/BlackBeltTechnology/pi-agent-dashboard/tree/HEAD/.pi/skills/frontend-mockup-loop-dashboardจากผู้เผยแพร่
Use when designing or refining any surface in packages/client (or src/client) of pi-agent-dashboard, and for every mock / mockup / UI-option / variant request here. This is a THIN ADAPTER: the generic loop, tools, and rubric live in the frontend-mockup-loop skill (source of truth: the workspace copy in packages/mockup-loop). Load that first for the full procedure; this skill only supplies the dashboard-specific bindings. Skip for trivial one-class tweaks.
packages/mockup-loop/.pi/skills/frontend-mockup-loop/SKILL.md (not an installed npm copy: unreleased skill changes apply here before the next release). Follow its 7 steps (GROUND, CONTRACT, MOCKUP, TEST, FIX, PROMOTE, LEARN) and use its tools (serve_mockup, score_mockup, init_ui_contract). The bindings below override only the dashboard-specific details.
ANTI-SLOP binding (packages/anti-slop suite): Design Read profile is always product-ui; redesign mode preserve (anti-slop-redesign: audit first, protected list incl. data-testid + keyboard shortcuts); image direction is off for every dashboard surface (never run anti-slop-image-direction or anti-slop-brandkit here). Part B and layout discipline do not apply.rounded-xl border border-[var(--border-secondary)] bg-[var(--bg-secondary)]) and cite colours by TOKEN NAME (--bg-secondary, --bg-tertiary, --severity-*-{bg,fg,border}), never by a measured hex: values differ per palette. Delegate harvest per the debug-dashboard skill's references/isolated-verification.md.serve_mock_site, #ref URLs in every question, decisions via mock-decide). One page per <root>/<yyyy-mm-dd-slug>/mock.tsx using REAL @app/* client components, kit via mock-site/kit, rings Issue/Fix on the divs that change (guide: packages/mockup-loop/references/live-mock-site.md; example: packages/mockup-loop/examples/2026-11-03-session-pills/). Environment: inherited from packages/client/vite.config.ts via root package.json mockSite (launcher packages/client/scripts/vite-build.mjs) — never copy client aliases or plugins; mockups/mock-site.config.ts holds options only (title, themes, app, mock-only aliases @app/@flows), plus mock-site.app.tsx + mock-site.css. Host APIs (/api/*, /ws) come from fixtures (capture real shapes with mock-capture); "Missing fixtures" on the page lists what is still unanswered. Serve serve_mock_site{} (port 5299, never 8000) or npm run mocks. Static boards only for geometry repros (chat-selection-anchor style), and only as a directory holding STATIC.md that names the exception — never a loose .html (npm run check:mockups reports it). Location: change exists -> mockups go to openspec/changes//mockups/ (no marker row). No change yet (explore mode) -> write a dated live mock mockups/<yyyy-mm-dd-slug>/mock.tsx (static: mockups/<slug>/ + STATIC.md) and add a mockups/AGENTS.md row whose Purpose cell ends exactly Pending change: <intent> right before the closing | — spelling and casing exact, intent a short human hint with no | and no backticks. The marker makes it adoptable: openspec/config.yaml rules.proposal and plan-proposal Step 1b move it into the change when its proposal is created. Mockups not meant for a change get no marker. Verify dark AND light.
PLUGIN SURFACE binding (a plugin page, dialog, overlay route or slot widget): compose from the runtime kit (dashboard-plugin-runtime: SettingsStatusPill, SettingsNotice, SettingsActionError, the field family) and the ui:* primitives (ui:dialog, ui:status-pill, ...), never hand-built equivalents. Check the slot and its footprint in packages/dashboard-plugin-skill/.pi/skills/dashboard-plugin-scaffold/references/slot-taxonomy.md, and the plugin-author rules in references/host-design.md. A plugin overlay route or slot widget is mocked inside its host: give the frame surroundings that render the real host shell part (the overlay chrome / slot container) around the slot, identical in both panes (R1). Rows without a reference implementation in ui-contract.md say Adoption: pending.--port/--pi-port to pi-dashboard stop (it honors them and kills only listeners that HOME owns; never use --force, never copy server.pid/server.lock*/instances/ from the real HOME). Or kill by pgrep -f 'cli.ts.*--port '.node scripts/theme-token-guard.mjs reports no new violation; screenshots exist for Base dark, Base light and one non-base palette from themes.ts. Visual judgment of them is a non-gating note.Pending change: <intent> row; npm run check:mockups -- --base origin/develop reports nothing new.Dashboard-specific adapter on the generic frontend-mockup-loop skill: binds the 7-step design loop to pi-agent-dashboard component sources, theme-system tokens, and isolated verification. Use when des
---name: frontend-mockup-loop-dashboarddescription: Dashboard-specific adapter on the generic frontend-mockup-loop skill: binds the 7-step design loop to…---# .pi/skills/frontend-mockup-loop-dashboard/SKILL.mdภาพรวม
Dashboard-specific adapter on the generic frontend-mockup-loop skill: binds the 7-step design loop to pi-agent-dashboard component sources, theme-system tokens, and isolated verification. Use when designing/redesigning any pi-agent-dashboard client surface. Triggers: "design a dashboard screen", "mockup a dashboard surface", "redesign SessionCard", "make dashboard UI consistent".
FAQ
ดาวน์โหลด .pi/skills/frontend-mockup-loop-dashboard/SKILL.md จากผู้เผยแพร่ หรือคัดลอกพาธแล้วเปิดรีโพซิทอรี PlugMCP แสดงรายการสกิลเท่านั้น ไม่ได้โฮสต์ไฟล์
ผู้เผยแพร่เก็บไว้ที่ https://github.com/BlackBeltTechnology/pi-agent-dashboard
Claude, Cursor, Codex และ Grok Build อ่าน SKILL.md ที่คุณเพิ่มจากรีโพซิทอรีของผู้เผยแพร่ได้ ส่วน Grok Bot จะติดตั้งให้เมื่อคุณส่งลิงก์โฟลเดอร์ GitHub ของสกิลในแชต