Review UI
aaddrick/claude-pipeline
Comprehensive UI/CSS review using parallel agents. An agent skill from aaddrick/claude-pipeline.
Use sub-agents to iteratively improve dashboard-building instructions.
$ npx skills add adam-s/intercept --skill instruction-dashboard-tuning -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install adam-s/intercept instruction-dashboard-tuning --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/adam-s/intercept.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/instruction-dashboard-tuning .claude/skills/instruction-dashboard-tuning && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "instruction-dashboard-tuning" agent skill from https://github.com/adam-s/intercept/tree/main/.claude/skills/instruction-dashboard-tuning into .claude/skills/instruction-dashboard-tuning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "instruction-dashboard-tuning", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/adam-s/intercept/tree/main/.claude/skills/instruction-dashboard-tuningType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add adam-s/intercept --skill instruction-dashboard-tuning -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install adam-s/intercept instruction-dashboard-tuning --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/adam-s/intercept.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/instruction-dashboard-tuning .agents/skills/instruction-dashboard-tuning && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "instruction-dashboard-tuning" agent skill from https://github.com/adam-s/intercept/tree/main/.claude/skills/instruction-dashboard-tuning into .agents/skills/instruction-dashboard-tuning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "instruction-dashboard-tuning", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add adam-s/intercept --skill instruction-dashboard-tuning -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install adam-s/intercept instruction-dashboard-tuning --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/adam-s/intercept.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/instruction-dashboard-tuning .cursor/skills/instruction-dashboard-tuning && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "instruction-dashboard-tuning" agent skill from https://github.com/adam-s/intercept/tree/main/.claude/skills/instruction-dashboard-tuning into .cursor/skills/instruction-dashboard-tuning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "instruction-dashboard-tuning", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/adam-s/intercept.git --path .claude/skills/instruction-dashboard-tuning--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add adam-s/intercept --skill instruction-dashboard-tuning -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install adam-s/intercept instruction-dashboard-tuning --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/adam-s/intercept.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/instruction-dashboard-tuning .gemini/skills/instruction-dashboard-tuning && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "instruction-dashboard-tuning" agent skill from https://github.com/adam-s/intercept/tree/main/.claude/skills/instruction-dashboard-tuning into .gemini/skills/instruction-dashboard-tuning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "instruction-dashboard-tuning", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install adam-s/intercept instruction-dashboard-tuningInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add adam-s/intercept --skill instruction-dashboard-tuning -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/adam-s/intercept.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/instruction-dashboard-tuning .github/skills/instruction-dashboard-tuning && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "instruction-dashboard-tuning" agent skill from https://github.com/adam-s/intercept/tree/main/.claude/skills/instruction-dashboard-tuning into .github/skills/instruction-dashboard-tuning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "instruction-dashboard-tuning", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add adam-s/intercept --skill instruction-dashboard-tuning -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install adam-s/intercept instruction-dashboard-tuning --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/adam-s/intercept.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/instruction-dashboard-tuning .opencode/skills/instruction-dashboard-tuning && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "instruction-dashboard-tuning" agent skill from https://github.com/adam-s/intercept/tree/main/.claude/skills/instruction-dashboard-tuning into .opencode/skills/instruction-dashboard-tuning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "instruction-dashboard-tuning", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
instruction-dashboard-tuningUse sub-agents to iteratively improve dashboard-building instructions.
Instruction Dashboard Tuning is an agent skill from adam-s/intercept. Use sub-agents to iteratively improve dashboard-building instructions. Three-phase pipeline — discover APIs, build dashboard matching a wireframe, review code + UI with a SOTA reviewer agent. The dashboards are throwaway; instruction improvements and framework code fixes are the product.
Its SKILL.md is about 4.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including scripts (for example `scripts/run-iteration.sh` and `scripts/write-handoff.sh`).
It sits in Frontend & Design, covering UI design, Subagents and Code review. The repository describes itself as: Turn any website into a typed JSON API using self improving agents. The licence is MIT.
3 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 6451b89. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Ships 2 files in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
pnpmcurlpython3From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use pnpm and curl, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Instruction Dashboard Tuning loads about 4.3k tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 1,056 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
The full file from adam-s/intercept at commit 6451b89, republished under its MIT licence (© adam-s). 1,056 words, ~4,276 tokens.
.claude/skills/instruction-dashboard-tuning/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.DO NOT write memory files. All learnings go into
.claude/skills/,.claude/agents/,.claude/rules/, or framework code — NOT into memory.
Check if .claude/user-consent.md exists with ACCEPTED: true. If yes, display: ✅ Prior consent on file (DATE). Proceeding. and skip to "Before Starting."
If not, present the 3 warnings from .claude/skills/instruction-tuning/SKILL.md (ToS, autonomous agents, resource consumption). All 3 must be accepted. Write .claude/user-consent.md on acceptance. This file is shared across both tuning skills.
You are not building dashboards. You are writing instructions that make other agents build correct dashboards.
.claude/, framework code fixes go to packages/, apps/, etc.Turn 1: Ask how many discovery passes — 1 or 2? Default to 1.
Turn 2: Ask which websites to use as wireframes. The user picks the sites.
Turn 3: Ask what to do when agents finish. Pick one:
Do NOT launch agents until the user answers all questions.
SCREENSHOT of real website = the "wireframe"
│
┌───────────┼───────────┐
▼ ▼ ▼
Phase 1 Phase 2 Phase 3
DISCOVERY BUILD REVIEW
(worktree) (same wt) (read-only)
│ │ │
▼ ▼ ▼
Domain Dashboard Findings
plugin matching report
w/ routes wireframe │
┌────┴────┐
▼ ▼
.claude/ packages/
skills/ apps/ etc.
│
▼
WORKTREE DELETED
IMPROVEMENTS KEPT1. Clean: bash .claude/hooks/cleanup-agents.sh
Also: for port in $(seq 3031 3049); do lsof -ti:"$port" | xargs kill -9 2>/dev/null; done
Also: rm -rf /tmp/dashboard-tuning/
2. Verify commit: ensure worktrees branch from latest committed instructions
3. Capture wireframe:
mkdir -p /tmp/dashboard-tuning
Screenshot target website at 1280x800 → /tmp/dashboard-tuning/wireframe-desktop.png
Screenshot at 375x800 → /tmp/dashboard-tuning/wireframe-mobile.png
4. Launch Phase 1 (Discovery) in worktree (run_in_background: true)
5. LIVE MONITOR every 60s until discovery completes
6. Verify: elimination table filled, routes return data via curl
7. Launch Phase 2 (Build) in SAME worktree (run_in_background: true)
8. LIVE MONITOR every 60s until build completes
8b. VERIFY PROXY — before screenshots, confirm the web proxy reaches the API:
curl -s http://localhost:$WEB_PORT/api/$DOMAIN/ROUTE | head -c 200
If this fails (500, empty), the web server was started without API_PORT=$API_PORT.
Kill, restart with API_PORT=$API_PORT PORT=$WEB_PORT, re-verify.
8c. VERIFY PLACEMENT — check page is in (dashboard)/ group:
ls apps/web/src/app/\(dashboard\)/PAGE_NAME/page.tsx
If the page is at apps/web/src/app/PAGE_NAME/ instead, that's a finding.
9. Capture dashboard screenshots at 4 viewports (375, 768, 1280, 1920):
mkdir -p /tmp/dashboard-tuning/screenshots
./scripts/screenshot-dashboard.sh --path /PAGE --width W --port $WEB_PORT --output /tmp/dashboard-tuning/screenshots/WxH.png
10. Launch Phase 3 (Review) — reviewer reads worktree + screenshots (run_in_background: true)
11. MONITOR until reviewer produces findings report
12. Process findings:
a. Apply GENERALIZED=yes instruction improvements to .claude/
b. Apply framework code fixes to packages/, apps/, services/, scripts/, tests/
c. CONSISTENCY CHECK — grep all .claude/ for the concept you changed
13. PRUNE .claude/ — run `wc -l .claude/skills/dashboard-builder/SKILL.md .claude/agents/dashboard-agent.md`.
If any file exceeds 300 lines, extract the bottom third to a `reference/` subdirectory.
Keep the main file focused on: architecture, build steps, states, wireframe fidelity, responsive, errors.
Niche patterns (comment trees, video, sparklines, CRUD) go in reference files.
14. Process cleanup: kill servers, remove worktree
15. Commit fixes to main
16. Write handoff (.claude/dashboard-tuning-handoff.md, gitignored)
17. Start fresh Claude Code session, repeatReuses the already-tuned discovery protocol. No new instructions needed.
Agent: discovery-agent (.claude/agents/discovery-agent.md)
Prompt template:
Discover ALL transport types that [site] uses. Build a route for EVERY transport found.
Target: [url]
Follow .claude/rules/discovery.md — GATHER→SCAN→CLASSIFY→BUILD.
In GATHER: connect to HOMEPAGE first and browse naturally (scroll, click) to warm up cookies before navigating to target pages. Intercept pagination traffic. If you see an API endpoint with pagination params in traffic, test it directly via /browser/mcp/fetch. For cross-origin APIs, credentials are forwarded automatically.
In CLASSIFY: name the site's core data and verify your transports cover it.
In BUILD: auth-gated endpoints (Gap=Y) go directly to session harvest. Read the session harvest reference file BEFORE writing any harvest code.
Fill ALL 8 elimination rows before writing code.
After building routes, register your domain and test EVERY route through the API server proxy.
Before finishing: run `pnpm biome check --write --unsafe .` and fix any remaining lint or type errors. CI must be clean.
Budget: ~150 tool calls. Plan: ~30 GATHER, ~10 SCAN/CLASSIFY, ~80 BUILD, ~30 testing.
Your port is XXXX.Port: 3031+N (API only — discovery doesn't need a web server)
Agent: dashboard-agent (.claude/agents/dashboard-agent.md)
Prompt template:
Build a dashboard that matches the wireframe screenshot at /tmp/dashboard-tuning/wireframe-desktop.png.
API routes are already working in this worktree:
[paste output of curl -s http://localhost:API_PORT/api]
Read these skill files before starting:
1. .claude/skills/dashboard-builder/SKILL.md — the build process
2. .claude/skills/visual-dev/SKILL.md — screenshot + judge loop
3. .claude/skills/debug-logs/SKILL.md — when data doesn't flow
4. .claude/skills/systematic-testing/SKILL.md — verify API routes first
Your wireframe: Read /tmp/dashboard-tuning/wireframe-desktop.png
This is a real website screenshot. Match its:
- Layout structure (grid, sidebar, header)
- Information density (items per row, spacing)
- Typography hierarchy (title vs metadata sizing)
- Component patterns (cards, badges, thumbnails)
The gap between your dashboard screenshot and the wireframe IS the bug.
Structural requirements:
- Place page in (dashboard)/ group: apps/web/src/app/(dashboard)/<page-name>/page.tsx
- If the wireframe has its own header/footer/nav, add a layout.tsx opt-out:
export default function Layout({ children }: { children: React.ReactNode }) { return <>{children}</>; }
- Use shadcn/ui Button (not raw <button>), Alert (not raw <div>), for ALL interactive/status elements
- Override visual tokens (className + style), not component choice
- If API returns HTML fragments, sanitize with DOMPurify before dangerouslySetInnerHTML
When starting servers, set ports explicitly:
PORT=$API_PORT pnpm --filter @interceptor/api dev
API_PORT=$API_PORT PORT=$WEB_PORT pnpm --filter @interceptor/web dev
Before finishing: run `pnpm biome check --write --unsafe .` and fix any remaining lint or type errors. CI must be clean.
API port: XXXX. Web port: YYYY.
Budget: 80 tool calls.Ports: API 3031+N, Web 3041+N
Before launching: Kill the discovery agent's API server, then restart with both API and Web servers in the same worktree.
Agent: reviewer-agent (.claude/agents/reviewer-agent.md)
Prompt template:
Review the dashboard built by another agent.
Worktree code: [WORKTREE_PATH]
Dashboard screenshots: /tmp/dashboard-tuning/screenshots/
Wireframe: /tmp/dashboard-tuning/wireframe-desktop.png
Read ALL component files in the dashboard directory.
Read ALL screenshots (4 viewports) and the wireframe.
Read the .claude/ instruction files the builder was supposed to follow.
Score on the 12-point review. Compare wireframe to dashboard — name SPECIFIC differences.
Produce Section A (instruction improvements) and Section B (framework code fixes).
Only include GENERALIZED=yes findings.
Budget: 40 tool calls.Runs from main repo (not a worktree). Reads the worktree path but writes nothing.
Parse the agent output file every 60 seconds:
FILE="$AGENT_OUTPUT_FILE"
cat "$FILE" | python3 -c "
import sys, json
tool_calls = 0; screenshots = 0; skill_reads = 0; writes = 0; edits = 0
files_written = []; last_texts = []
for line in sys.stdin:
try:
d = json.loads(line)
if d.get('type') == 'assistant':
for c in d.get('message',{}).get('content',[]):
if isinstance(c,dict):
if c.get('type')=='text' and len(c.get('text',''))>20:
last_texts.append(c['text'][:200])
if len(last_texts) > 3: last_texts.pop(0)
elif c.get('type')=='tool_use':
tool_calls += 1
n=c.get('name','');inp=c.get('input',{})
if n=='Bash':
cmd = inp.get('command','')
if 'screenshot' in cmd.lower(): screenshots += 1
elif n=='Write':
writes += 1; files_written.append(inp.get('file_path','').split('/')[-1])
elif n=='Edit': edits += 1
elif n=='Read':
fp = inp.get('file_path','')
if 'SKILL.md' in fp or 'visual-dev' in fp: skill_reads += 1
if d.get('type') == 'result': print('*** AGENT COMPLETE ***')
except: pass
print(f'Calls: {tool_calls}/80 | Screenshots: {screenshots} | Skills read: {skill_reads} | Writes: {writes} | Edits: {edits}')
print(f'Files: {files_written}')
for t in last_texts: print(t[:150]); print('---')
"At each check, update the monitoring table:
| Agent | Calls | Screenshots | Skills | Files | Notes |
|---|
Phase 1 watch for:
Phase 2 watch for:
(dashboard)/, not top-level /app/<button> or raw <div> for errorsPhase 3 watch for:
Budget overrun: If an agent exceeds its budget, let it finish its current output but note the overrun. In findings, check whether the overrun was caused by a monolith rewrite (instruction gap) or unnecessary retries (agent error).
Same as .claude/skills/instruction-tuning/SKILL.md — the existing 18-check table.
| Check | Pass/Fail |
|---|---|
| Read all 4 skill files before starting | |
| API routes verified via curl before UI work | |
| States enumerated BEFORE writing component code | |
| Built component-by-component, not whole page blind | |
| Screenshot taken after EVERY visual change | |
| 7 judgment criteria applied to each screenshot | |
| Wireframe compared against dashboard screenshot | |
| Fixed issues one at a time between screenshots | |
| All states rendered: idle, loading, populated, empty, error, detail | |
| Mobile viewport (375px) screenshot taken and judged | |
| Data flows through /api/ proxy — no hardcoded URLs | |
| Used shadcn/ui components — no reinvented primitives | |
| Component files under 200 lines each | |
| No @interceptor/shared imports in client components | |
| Biome auto-fix run before manual lint cleanup | |
| Stayed under 80 tool calls |
| Check | Pass/Fail |
|---|---|
| Read all worktree source files (components, routes, types) | |
| Read dashboard screenshots at all 4 viewports | |
| Read the wireframe screenshot | |
| Compared wireframe to dashboard (named specific differences) | |
| Produced Section A with >= 3 instruction improvement findings | |
| All Section A findings are GENERALIZED=yes | |
| Produced Section B with >= 1 framework code fix | |
| Did NOT suggest changes to the worktree code | |
| Each finding includes specific file path and exact text change | |
| Scored the dashboard on the 12-point review |
REVIEWER produces findings report
│
┌────┴────┐
▼ ▼
Section A: Section B:
Instructions Code Fixes
│ │
▼ ▼
.claude/ packages/
skills/ apps/ etc.
│ │
└────┬────┘
▼
CONSISTENCY CHECK
(grep .claude/ for contradictions)
│
▼
COMMIT + HANDOFFThe orchestrator is the ONLY entity that writes to .claude/. The reviewer produces a report. The builder writes to the worktree. No agent ever writes to .claude/ directly.
When you change an instruction, the same concept appears in multiple files. A fix in dashboard-builder/SKILL.md means nothing if dashboard-agent.md still uses the old language.
Before committing any instruction change:
grep -rn "CONCEPT" .claude/rules/ .claude/agents/ .claude/skills/Every hit must be consistent with your change.
| Worktree | API Port | Web Port |
|---|---|---|
| dash-1 | 3031 | 3041 |
| dash-2 | 3032 | 3042 |
| dash-3 | 3033 | 3043 |
Avoids collision with discovery agents (3011-3021) and user dev (3000-3001).
After committing all fixes, write .claude/dashboard-tuning-handoff.md (gitignored) with:
Every instruction change must work for ANY website. If a fix only helps for a specific site, it's overfitting. The reviewer must mark GENERALIZED=yes on every finding. The orchestrator drops GENERALIZED=no findings.
The dashboard tuning loop converges when fresh builder agents (clean session, no hints):
© adam-s, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 2 other files (scripts) in .claude/skills/instruction-dashboard-tuning of adam-s/intercept.
Open the folder on GitHubat commit 6451b89
Instruction Dashboard Tuning next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Instruction Dashboard Tuning this skilladam-s/intercept | 189 | — | ~4.3k | Automated safety check: Pass | MIT | |
| Review UIaaddrick/claude-pipeline | 130 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Tidymblode/agent-skills | 144 | — | ~4.2k | Automated safety check: Pass | MIT | |
| Spec App Consistency Auditleo-kuang-ai/spec-first | 107 | — | ~4.6k | Automated safety check: Pass | MIT | |
| UI StylingOhh-889/skyroc | 795 | 13 repos | ~2.5k | Automated safety check: Pass | MIT | |
| LobeHub Interactive Prototypelobehub/lobehub | 83k | — | ~1.6k | Automated safety check: Pass | Custom licence |
aaddrick/claude-pipeline
Comprehensive UI/CSS review using parallel agents. An agent skill from aaddrick/claude-pipeline.
mblode/agent-skills
Reviews a local diff, branch diff, or PR with file:line findings in confirmed and plausible tiers, gates any test the diff adds or changes, and in apply mode lands the fixes and diff-scoped…
leo-kuang-ai/spec-first
Audit mobile App PRD/Figma/local-source consistency across page routes, KMP/Clean Architecture, components, analytics, i18n, engineering quality, and industry lenses before runtime validation; use…
Ohh-889/skyroc
Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs.
lobehub/lobehub
Builds single-file interactive HTML prototypes rendered with the real LobeHub UI components and written as production-style React, so they can later be split into files.
samuelclay/NewsBlur
Design engineering principles for making interfaces feel polished.
adam-s/intercept
Discover any website's API and create domain plugins with proxy routes.
adam-s/intercept
Build a complete application from a short description. An agent skill from adam-s/intercept.
adam-s/intercept
Iterative debugging with targeted logs. An agent skill from adam-s/intercept.
adam-s/intercept
Use sub-agents as test subjects to iteratively improve .claude/ instruction files.
adam-s/intercept
Bottom-up systematic validation for multi-layer architectures.
adam-s/intercept
Deploy to EC2 production server. An agent skill from adam-s/intercept.
Categories
Use sub-agents to iteratively improve dashboard-building instructions. Instruction Dashboard Tuning is an agent skill from adam-s/intercept. Use sub-agents to iteratively improve dashboard-building instructions.
Instruction Dashboard Tuning fits situations like: tasks that involve UI design; tasks that involve Subagents; tasks that involve Code review.
Run `npx skills add adam-s/intercept --skill instruction-dashboard-tuning -a claude-code`. Or copy the skill folder (.claude/skills/instruction-dashboard-tuning in adam-s/intercept) into .claude/skills/instruction-dashboard-tuning in your project. Claude Code loads it when a task matches its description.
Run `npx skills add adam-s/intercept --skill instruction-dashboard-tuning -a codex`. Or copy the skill folder (.claude/skills/instruction-dashboard-tuning in adam-s/intercept) into .agents/skills/instruction-dashboard-tuning in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add adam-s/intercept --skill instruction-dashboard-tuning -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/instruction-dashboard-tuning, .gemini/skills/instruction-dashboard-tuning, .github/skills/instruction-dashboard-tuning and .opencode/skills/instruction-dashboard-tuning in your project.
Going by SKILL.md and its folder, Instruction Dashboard Tuning needs a shell for the scripts in its folder and the command-line tools its instructions call (pnpm, curl and python3). Our summary lists: Python 3; A Bash shell.
SKILL.md contains no URLs. Its commands use curl, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Instruction Dashboard Tuning is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 4.3k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Instruction Dashboard Tuning: Review UI (aaddrick/claude-pipeline, 130 stars), Tidy (mblode/agent-skills, 144 stars), Spec App Consistency Audit (leo-kuang-ai/spec-first, 107 stars) and UI Styling (Ohh-889/skyroc, 795 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
adam-s (a GitHub user) maintains it in adam-s/intercept, which has 189 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on July 31, 2026.
Source: adam-s/intercept on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.