figma-desc-spec

Writes and reviews Figma spec Description sections following the Okestro CONTRABASS documentation standard.

Updated May 10, 2026
One-click install
npx skills add https://github.com/dadafinger/dadafinger-skills --skill figma-desc-spec-dadafinger
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: figma-desc-spec
Source: https://github.com/dadafinger/dadafinger-skills/tree/main/proprium/cursor/skills/figma-desc-spec
Command: npx skills add https://github.com/dadafinger/dadafinger-skills --skill figma-desc-spec-dadafinger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing detailed specification Descriptions for Figma planning documents is inconsistent across authors, leading to missing sections, incomplete screen coverage, and non-standard formatting. This Skill defines the single source of truth for the Description column format so every spec page follows the same structure. ## Core Features & Use Cases - Standardized Description Format: Enforces the numbered-section + Appendix + Changelog structure based on the 3.0.6 full PDF and Figma example nodes, updated for the 4.0.0 baseline. - Exhaustive Screen Coverage Rules: Mandates full enumeration of the four screen types (list, create, edit, detail) with three-layer body content (policy, items, constraints) and four coverage areas (branching, exceptions, behavior, guidance). - Change Tracking Conventions: Defines change markers and Changelog rules so revisions to spec pages are traceable. - Use Case: When a planner asks to "write the detailed spec Description for this screen" or "review this Description against the checklist", the Skill loads the SoT guidelines and produces or validates content in the standard format. ## Quick Start Write the detailed spec Description for this Figma screen following the standard numbered-section format with full coverage of list, create, edit, and detail screens.

Frequently Asked Questions about figma-desc-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a Figma spec Description in a standard format?▼

Follow the numbered-section structure with Appendix and Changelog defined by this standard. Each section corresponds to a major layout element from the wireframe, and the body uses three layers: policy, items, and constraints.

What screens must a detailed spec Description cover?▼

The standard requires exhaustive description of four screen types: list, create, edit, and detail. Each screen must address branching, exceptions, behavior, and guidance areas.

Does this skill render content into Figma nodes?▼

No, it only defines the Description writing standard and review rules. Actual rendering into Figma nodes, including font and list API techniques, is handled by the figma-change-flow skill.

How are spec changes tracked in the Description?▼

Changes are recorded using defined change markers plus a Changelog section at the end of the Description. This keeps revisions traceable against the 4.0.0 baseline format.

When should I not use this Description standard?▼

It is specific to Okestro CONTRABASS planning documents based on the 3.0.6 full PDF and Figma example nodes. For unrelated products or free-form documentation, a different specification template is more appropriate.