no-paint-drying

Settle open questions with the human at small scale and fast turnaround (seconds to minutes: synthetic design, checkpoint, single stage, unit test) before any long run, then declare the long run and how many hours it needs no input, and run it unattended with monitor, timeout, memory cap and incremental results. Use whenever a task involves a build, sweep or flow stage longer than a few minutes, or a decision that depends on a measurement.

설치로 이동 파일 검토

저장소: The-OpenROAD-Project/bazel-orfs
최근 소스 활동: 2026년 9월 18일 06:42
감지된 SKILL.md 언어: 영어
스타: 27
포크: 24

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

AI 어시스턴트로 설치

이 프롬프트를 복사해 사용 중인 AI 어시스턴트에 입력하세요.

Follow https://skillsmp.com/skill-install/prompt.md to install only the Agent Skill at https://github.com/The-OpenROAD-Project/bazel-orfs/tree/main/.claude/skills/no-paint-drying.

직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.

npx skills add https://github.com/The-OpenROAD-Project/bazel-orfs --skill no-paint-drying

명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.

로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

SKILL.md

소스 지침 · 읽기 전용 미리보기

name: no-paint-drying
description: Settle open questions with the human at small scale and fast turnaround (seconds to minutes: synthetic design, checkpoint, single stage, unit test) before any long run, then declare the long run and how many hours it needs no input, and run it unattended with monitor, timeout, memory cap and incremental results. Use whenever a task involves a build, sweep or flow stage longer than a few minutes, or a decision that depends on a measurement.

# no-paint-drying The instructions for this skill are maintained in the shared Claude slash command. Please read and follow the single source of truth: [../../../.claude/commands/no-paint-drying.md](../../../.claude/commands/no-paint-drying.md)

GitHub에서 보기

검색으로 돌아가기 설치로 돌아가기

repair-timing-grt

Investigate OpenROAD global-route repair_timing correctly — the grt "grind"/timeout, hold- and setup-buffer insertion. Covers why a skip-repair (fast) grt measures nothing about repair, why repair_timing must run inside global_route.tcl on the pre-GR ODB, how to split the grind into setup vs hold before blaming either, why the win is measured as clk_period-WNS in picoseconds rather than as a percentage of WNS, and why a design that closes measures nothing about a repair knob. Use when a grt stage times out or runs for hours, when a change is meant to affect repair_timing, or when reasoning about hold vs setup buffer insertion at global route.

2026-09-27

cache-miss

Ask whether a target is a remote cache hit on this machine without building it (a capture kills every miss as it appears and lists the actions behind it as not reached, minutes on a laptop), and find out why it is not when another machine built it: a few kilobytes of key evidence per machine (Bazel version, commit and tree, redacted options, tool digests, the source files read, one line per action with its cache key and which of arguments, environment, tools, sources or design inputs moved), committed next to the design and diffed, naming the first action that differs and the source file behind it. Says what committed evidence promises and when to recapture. Use before building any long flow target, when XSTile_grt or any stage rebuilds unexpectedly, or before blaming Scala, a toolchain or the cache.

2026-09-26

dogfooding

The standing rules learned building XiangShan with bazel-orfs, for any large design: fix the tools and never the design (no multicycle or false-path exceptions, no added RTL registers); hard stops where a problem is made; finish the macros before the parent; a design README says what is; public PR tests check intended behaviour, not golden .ok output; a PR on an unmerged upstream PR is a draft; choices in the flow script, facts in the .odb; relative paths; unattended means continue; Chesterton's fence, check what our flow skipped before blaming a tool; watch a run that grinds past its expected time. Use before proposing a fix for a timing or flow problem found on a big design, before writing a design README or status, before opening a PR that depends on another, and before writing a test for a public PR.

2026-09-25

이 저장소의 모든 Skills 보기

no-paint-drying

소스 정보

설치 방법

AI 어시스턴트로 설치

소스 파일 검토

이 저장소의 다른 Skills

AI 어시스턴트로 설치

이 저장소의 다른 Skills