ds-developer-guide

Builds developer guide pages for Figma components in the Souz Design System.

Updated Jun 17, 2026
One-click install
npx skills add https://github.com/RickOBrian/aid --skill ds-developer-guide-rickobrian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ds-developer-guide
Source: https://github.com/RickOBrian/aid/tree/main/skills/ds-developer-guide
Command: npx skills add https://github.com/RickOBrian/aid --skill ds-developer-guide-rickobrian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually assembling a complete developer guide page for a design system component in Figma is slow and error-prone: sections must follow a fixed structure, templates must be imported from a library, annotations drawn, and text styles applied consistently. This Skill automates the entire build so every component page follows the same specification. ## Core Features & Use Cases - Structured page generation: Creates the three required top-level sections (Общее, 💻 Для разработчиков, Layout) with correct colors, padding, and positioning, skipping Layout automatically for Presets. - Template-driven content blocks: Imports Guide Intern library components (Guide Block, Guide Header Detailed, Guide List, etc.) and fills them with anatomy, corner radius, sizes, types, states, tap area, behavior, constraints, and animation blocks in a fixed order. - Crash recovery via checkpoints: Writes a hidden checkpoint node on the Figma page after each step so a retried run resumes where it stopped instead of duplicating sections. - Use Case: A designer pastes a Figma link to a Switch component and asks for a developer guide; the Skill asks about behavior and mockup scenario, then builds the full annotated guide page with sections, hyperlinks, and a banking-app mockup. ## Quick Start Paste a Figma design link to your component and ask to build the developer guide page for it.

Frequently Asked Questions about ds-developer-guide

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

FAQPage Schema
How do I generate a developer guide for a Figma component?

Paste a Figma design URL (ideally with a node-id for the selected layer) and ask for the developer guide. The Skill resolves the component identity, asks about behavior and mockup scenario, then builds the Общее, Для разработчиков, and Layout sections automatically.

What sections does a Figma design system developer guide need?

Every component page needs three top-level sections: Общее (navigation hub), 💻 Для разработчиков (the main guide with anatomy, sizes, states, behavior, and other blocks), and Layout (per-type visual spec). Presets skip the Layout section entirely.

Can this run through a read-only Figma MCP integration?

No. The guide-building steps require live Figma Plugin API calls such as createSection, importComponentByKeyAsync, and detachInstance. A read-only integration can only resolve the node and pull reference context; the Skill flags this mismatch and asks how to proceed.

Why does text editing fail in Figma plugin scripts?

Writing to .characters or .textStyleId throws or silently fails if the node's font is not loaded first. The Skill loads Inter Regular, Medium, and SemiBold up front and loads each template node's own font before editing it.

What happens if the guide build crashes mid-run?

The Skill writes a hidden checkpoint text node on the page after each major step, storing answers and completed sections. On retry it reads the checkpoint, skips answered questions, and rebuilds only the sections that are actually missing.

Should nested Guide Intern components be detached in Figma?

No. Only the five top-level [AGENT] frames are detached after import. Nested components like Guide Block, Guide List, and Guide Header Detailed must stay as instances and be edited through their SLOT, or the library styling and structure are destroyed.