OpenParable
Skip to content
← Back to skills

Place And Route

Development
place-and-route

Place And Route is an Agent Skill for development published in the a5c-ai/babysitter repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Expert skill for FPGA place and route optimization and physical implementation

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/a5c-ai/babysitter/blob/HEAD/library/specializations/fpga-programming/skills/place-and-route/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/place-and-route, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Place and Route Skill

Overview

Expert skill for FPGA place and route optimization, achieving timing closure and optimal resource utilization through physical implementation strategies.

Capabilities

  • Create floorplans for large designs
  • Define Pblocks and placement constraints
  • Analyze and resolve routing congestion
  • Apply physical optimization directives
  • Use incremental implementation flows
  • Optimize for timing closure
  • Analyze and fix timing violations
  • Generate utilization and timing reports

Target Processes

  • place-and-route.js
  • timing-closure.js
  • clock-network-design.js

Usage Guidelines

Floorplanning Strategy

  • Identify major functional blocks
  • Allocate resources by region
  • Consider data flow and connectivity
  • Plan for clock distribution
  • Reserve space for debug logic

Pblock Constraints

  • Define rectangular regions
  • Assign hierarchical modules
  • Set resource limits per Pblock
  • Consider I/O proximity
  • Allow flexibility for routing

Congestion Resolution

  • Identify congested regions in reports
  • Apply SpreadLogic directives
  • Adjust Pblock boundaries
  • Consider logic restructuring
  • Use alternate routing architectures

Physical Optimization

  • Enable post-place optimization
  • Apply post-route physical optimization
  • Use retiming when beneficial
  • Consider register replication
  • Balance pipeline stages

Incremental Flows

  • Lock placed/routed cells
  • Use reference checkpoints
  • Minimize ECO iterations
  • Preserve timing-critical paths
  • Update only changed logic

Dependencies

  • P&R tool awareness (Vivado, Quartus)
  • FPGA architecture knowledge
  • Physical constraint syntax