Repository navigation
Figma component pages: one doc card with a real description - #35
Merged
Merged
Conversation
…description, a divider, then the Propstar tables (doc-card.js, pnpm figma:doc-cards, audit check)
…n table (hard-stop gradient when only some variants need it); every Figma change goes into both files (figmaCommunityFileKey)
…ells the agent to run it on the martacondedieguez file too
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The owner's layout for every Figma component page (2026-10-22): one white rounded card with the component's name, its description, a divider edge to edge, and below it the Propstar table(s) with their labels.
Description. It's the component's
purposefrom its{Name}.doc.ts, the same sentence its Storybook docs page opens with (owner's choice). Before, the page showed conversion notes or loose fragments; Button's even said "5 sizes (xs → xl)".Tokens (owner's choice): fill/page, radius/2xl, padding spacing/layout/l, gaps spacing/layout/m, divider border/neutral. Title is Heading / 3xl / Bold, description Body / l / Regular, and a child set's name Heading / m / Bold.
What's in this PR
scripts/figma/doc-card.jsdraws the card on one or more pages. It's safe to re-run: it keeps every table and component and rewrites the texts. A child set (ChartTooltip, MenuItem, SegmentedControlItem, TableRow…) gets its name above its table.pnpm figma:doc-cards [Name…]prints that script with the descriptions filled in from the.doc.tsfiles, so they can't drift from Storybook.propstar.jsno longer overwrites the page description with the set's conversion note. When it regenerates a table, the card stays auto-layout and hugs it.docCardcheck: header, divider, body, vertical auto-layout, fill bound to fill/page, and a description that isn't a conversion note.components-to-figma.mddescribe the card. The skill's new Phase 7b says to run it on every new or changed component, in both Figma files.Figma. All 29 core pages of the working file are redone. The new check passes on all 36 sets and components, and no leftover nodes remain. The Figma Community copy lives in another account, so the owner updates it (Phase 8).
🤖 Generated with Claude Code