pldi-topic-selection
Use when deciding whether a project is PLDI-shaped — implementation insight with benchmark-grade evidence — or better routed inside the PACMPL family to POPL, OOPSLA, or ICFP, or outward to ASPLOS, CGO, CAV, ICSE/FSE, or a systems venue, based on where the claim's evidence actually lives.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pldi-topic-selection --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# PLDI Topic Selection PLDI's scope statement is broad — all aspects of programming language research: design, implementation, theory, applications, performance (PLDI 2026 CFP) — but its acceptance bar has a recognizable shape: **an idea about languages, compilers, analyses, runtimes, or verification tooling whose truth is demonstrated by a working implementation evaluated on convincing programs.** The routing question is never "is this PL?"; it is "is the decisive evidence an implementation-and-benchmarks story?" ## The fit test Answer three questions honestly: 1. **Where does the claim's proof live?** In a theorem about a calculus → POPL lens. In measurements of a built system → PLDI lens. In how developers experience the language → OOPSLA lens. 2. **Who must be convinced?** People who build compilers and analyzers → PLDI. People who prove type soundness → POPL. People who study software at scale → ICSE/FSE. 3. **Would the paper survive with the implementation deleted?** If yes, the implementation is decoration and PLDI reviewers will say so. ## Routing table | Signal in your project | Better home | Why | |---|---|---| | The theorem is the contribution; implementation is a demo |
- The fit test
- Routing table
- PLDI-shaped in practice
- Decision procedure
- Output format
What does the pldi-topic-selection skill do?
Use when deciding whether a project is PLDI-shaped — implementation insight with benchmark-grade evidence — or better routed inside the PACMPL family to POPL, OOPSLA, or ICFP, or outward to ASPLOS, CGO, CAV, ICSE/FSE, or a systems venue, based on where the claim's evidence actually lives.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pldi-topic-selection --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 984 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.