Inspect before downloading
See what is inside
These previews come from the published bundle files, so you can judge the method and writing before using it.
Example task
A user asks: "We have a Figma screen for a new checkout step. Tell the developer exactly what to build and share the file with the engineering team." Assume the user has not yet provided file, frame, component, variable, prototype, Dev Mode, codebase, permission, export, accessibility, or approval evidence.
Without the bundle
Build the checkout screen exactly as shown in Figma. Use the same spacing, colors, typography, and components, then share the Figma file with engineering so they can inspect it.
Using the bundle
I can plan the handoff, but I cannot tell engineering exactly what to build or share the file until the Figma and implementation evidence is provided. Source note: Figma guidance should be checked against official Figma source categories for design files, components, libraries, variables, prototypes, Dev Mode, sharing, and permissions. Local evidence used: none yet. Missing before action or conclusion: file link or screenshots, target frame/page, component and variable/source-library details, prototype flow, responsive states, accessibility notes, Dev Mode evidence, codebase component mapping, export needs, file owner, target engineering audience, sharing permissions, sensitive-content.
Why this is better: The bundle-assisted output is better because it: - avoids inventing Figma file, component, variable, prototype, Dev Mode, codebase, or permission facts; - includes a visible source note; - separates handoff planning from sharing approval; - asks for design-system, implementation, accessibility, export, and permission evidence; - requires explicit confirmation before risky file, sharing, export, comment, integration.
Inspect this example in the repositoryTool guide
Figma
Defines safe, source-backed use of Figma in OpenKnowledgeBank bundles.
Read the fileWorkflow
Review Figma Design Handoff
Plan Figma design-to-development handoff with verified source, file, design-system, Dev Mode, and codebase evidence.
Read the fileWorkflow
Review Figma Sharing and Permissions
Review Figma sharing, permission, export, comment, and integration risk before changing live access or design content.
Read the fileTemplate
Figma Handoff Readiness Plan
A source-scoped plan for Figma design handoff, design-system, prototype, Dev Mode, sharing, and permission work.
Read the fileIs this bundle right for your task?
Who it is for
- People who configure, operate, integrate, govern, or review work performed in Figma
- Teams working in software, digital-products, design
When to use it
- A proposed Figma configuration or workflow change needs current IDs, permissions, dependencies, tests, and rollback evidence.
- A report, export, integration, or automation result needs to be reconciled against actual workspace state and current product documentation.
What you need to provide
- The product version or workspace scope, relevant configuration or export, desired outcome, permissions, and accountable owner.
- Current IDs, settings, records, logs, screenshots, integration details, and test evidence needed to verify the requested change.
Tasks and expected outputs
Questions it helps answer
- Plan Figma design handoff without inventing file, frame, component, variable, or permission details.
- Separate official Figma product behavior from user-provided file, library, Dev Mode, prototype, and team evidence.
- Review design-system, prototype, export, sharing, and permissions risk before action.
- Produce handoff readiness plans with source notes, validation checks, and confirmation boundaries.
What it helps produce
- Figma handoff readiness plan
Practical example
Use it with an agent
Load the bundle as context, provide the evidence named above, then adapt this example to your situation.
Provide the product version or workspace scope, relevant configuration or export, desired outcome, permissions, and accountable owner. Ask the agent to review Figma and produce Figma handoff readiness plan that maps configuration evidence, dependencies, permissions, tests, rollback, and actions that still require approval. Begin with figma.com, then confirm that the reference is current and applicable. Inspect Figma before drafting.
Context path: bundles/tools/figma
What the bundle includes
Tools
- Figma
- Figma Design
- FigJam
- Dev Mode
- Figma libraries
- Figma variables
Frameworks
- verify-first design handoff
- design-system source-of-truth review
- prototype readiness review
- sharing and permission confirmation boundary
Commands
/plan-figma-handoff
Evaluations
- Figma handoff plan quality check
Sources used to build this bundle
These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.
Limitations and safe use
Do not use this for
- Changing live configuration, records, permissions, automations, integrations, or shared data without verified scope, testing, rollback, and approval.
Known limitations
- Not a complete Figma Design, FigJam, Dev Mode, API, plugin, pricing, plan, connector, beta-feature, or release reference.
- Requires user-provided Figma file, page, frame, component, variable, style, prototype, comment, Dev Mode, library, permission, and policy evidence before final conclusions.
- Does not replace product design, design-system, accessibility, security, privacy, legal, procurement, or administrator review.
Safety notes
- Require explicit confirmation before editing, deleting, publishing, exporting, moving, commenting, changing permissions, updating libraries/components/variables/styles, running plugins/integrations, or sharing Figma links.
- Do not claim access to Figma files, teams, projects, organizations, libraries, components, variables, comments, prototypes, permissions, or Dev Mode output unless the user provides evidence or authorized tool access.