
Rules and pitfalls for running Plugin API scripts in Figma files through use_figma
- Free
- 28.8K GitHub stars
- Design and media

Rules and pitfalls for running Plugin API scripts in Figma files through use_figma

Reads, creates and visually checks PDFs by rendering pages and inspecting them

Deploys apps to Render with a render.yaml Blueprint or direct service creation over MCP

Applies Python, JavaScript/TypeScript and Go security guidance to new code or reviews

Maps who owns sensitive code from git history, with bus factor and co-change clusters

Writes an evidence-based Markdown threat model of a repository or path

Bootstrap and build WinUI 3 desktop apps in C# with checks that the app really launches

Stage, commit, push and open a draft GitHub pull request in one flow with gh

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mocku

Use when the user asks how to build with OpenAI products or APIs, asks about Codex itself or choosing Codex surfaces, needs up-to-date offic


Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path

Run a pre-mortem on a launch plan, sorting risks into tigers, paper tigers and elephants

Compare RICE, ICE, Opportunity Score, Kano and five other prioritisation methods

Turn tickets, PRDs or git logs into user-facing release notes grouped by change type

Facilitate a sprint retro with Start/Stop/Continue, 4Ls or Sailboat and owned action items

Plan a sprint from backlog and velocity: capacity, story selection, dependencies and risks

Map stakeholders on a power and interest grid and build a communication plan

Red-team a plan: steelman key assumptions, rank failure modes and name cheap tests

Turn a meeting transcript into notes with decisions, action items and open questions

Write user stories using the 3 C's and INVEST criteria with testable acceptance criteria

Write backlog items in the Why-What-Acceptance format with strategic context

Pick a first launch segment by scoring pain, budget, winnable share and referral reach

Build a one-page sales battlecard against a named competitor, with objection replies

Evaluate five growth loop types for a product and plan the strongest one

Score seven go-to-market motions for your product and build a 2 to 4 motion stack

Draft a go-to-market plan: channels, messaging, launch metrics and a 90-day timeline

Define an ideal customer profile from survey and usage data with disqualification rules

Research five direct competitors and recommend how to position against them

Map a customer journey from awareness to advocacy with emotions, pain points and fixes