agentleFS
OhmsSweetOhmsOhmsSweetOhms/claude-skills/fpga-timing-closure/SKILL.md

fpga-timing-closure

Skill0 starsChanged 58 days agoNo licenceView on GitHub

Close and audit Vivado timing for Zynq-7000 and Zynq UltraScale+ (ZynqMP) programmable-logic designs using a disciplined XDC → out-of-context (OOC) → full Project Implementation loop. Use this skill whenever work involves negative WNS/WHS, setup or hold closure, unconstrained paths, XDC ownership or rendering, PS/PL or generated-clock relationships, source-synchronous I/O, CDC max-delay or bus-skew constraints, OOC-versus-full timing differences, implementation directive sweeps, routed-checkpoint freshness, timing waivers, or proving that a routed Zynq build is release-ready. Trigger even when the user asks only why OOC passes but the full project fails, whether a false path/clock group/multicycle is safe, how to structure a Vivado timing matrix, or how to bank timing evidence. For the spin_dr FT600 interface, also read references/ft600-spin-dr.md.

The file

Show its rules and text

We split this skill into the rules it gives an agent

37 rules. About 0 are common, 31 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈31

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.