style-figma-clean
Skill142 starsChanged 3 months agoMITView on GitHub
Figma Clean style tokens and row template for the list-styling skill. Polished professional cards with a colored top stripe that matches the status, clean data layout below, subtle self-colored borders. Layout features a thin status-colored bar across the top of each card. Use when the user says "figma," "clean," "polished," "professional," "design tool," or similar.
In this repository61 other files it gives its agents.
- analyze-document-librarySkill
- broken-link-auditorSkill
- build-sharepoint-business-solutionSkill
- campaign-storySkill
- convert-cowork-skill-to-sharepointSkill
- copilot-toolboxSkill
- custom-image-taggerSkill
- decision-register-builderSkill
- document-browserSkill
- dossierSkill
- exec-reportSkill
- file-classifierSkill
- find-relevant-skillSkill
- flashcards-dashboardSkill
- generate-site-onboarding-guideSkill
- generate-test-contentSkill
- guest-access-reviewerSkill
- intranet-page-lifecycle-reviewSkill
- invoice-po-reconciliationSkill
- kb-ai-review-liteSkill
- knowledge-readiness-advisorSkill
- learning-designerSkill
- library-cleanupSkill
- list-stylingSkill
- metadata-completeness-auditorSkill
- narrated-story-animationSkill
- news-governance-reviewSkill
- organize-librarySkill
- permission-reportSkill
- project-health-checkSkill
- project-intelligence-change-event-extractionSkill
- project-intelligence-root-cause-analysisSkill
- project-intelligence-timeline-dashboardSkill
- rename-files-date-prefixSkill
- resume-screening-summarizerSkill
- review-councilSkill
- rfp-response-compliance-reviewSkill
- rfp-response-content-finderSkill
- rfp-response-content-generationSkill
- rfp-response-extractionSkill
- rfp-response-proposal-reviewSkill
- rfp-response-quality-tone-reviewSkill
- rfp-response-strategy-synthesisSkill
- roadmap-timelineSkill
- scorecard-matrixSkill
- sharepoint-safe-htmlSkill
- site-pages-content-calendarSkill
- site-storage-heatmapSkill
- style-bentoSkill
- style-blueprintSkill
- style-glassmorphismSkill
- style-high-contrastSkill
- style-monochromeSkill
- style-neobrutalismSkill
- style-pastelSkill
- style-retroSkill
- style-terminalSkill
- sync-blocker-auditorSkill
- team-newsletter-publisherSkill
- topic-explainerSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 212
Min-width hygiene: every text child needs min-width: 0 so long document names ellipsis-truncate without pushing siblings off-screen.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Figma Clean — Style Tokens + Row Template
Precise, polished, information-dense. Each card has a thin colored stripe across the top that matches the status. Below it, a clean horizontal layout with all metadata. Feels like a Figma component.
Layout philosophy: Top-stripe card. A thin 4px colored bar spans the top of each card, color-coded to the status. Below it, a single horizontal row of data: name, badge, progress, deadline. Dense but never cluttered. Every element is precisely placed.
Badge Tokens
- padding:
4px 12px - border-radius:
4px - font-size:
12px - font-weight:
600 - text-transform:
none
status_colors
| Value | bg | text | border | stripe_color |
| Draft | #6b7280 | #ffffff | 1px solid #6b7280 | #6b7280 |
| In Review | #3b82f6 | #ffffff | 1px solid #3b82f6 | #3b82f6 |
| Revising | #f97316 | #ffffff | 1px solid #f97316 | #f97316 |
| Approved | #22c55e | #ffffff | 1px solid #22c55e | #22c55e |
| Published | #16a34a | #ffffff | 1px solid #16a34a | #16a34a |
| _fallback | #9ca3af | #ffffff | 1px solid #9ca3af | #9ca3af |
Row Card Tokens
- card_border:
1px solid #e5e7eb - card_border_radius:
8px - card_background:
#ffffff - card_margin_bottom:
8px - card_shadow:
0px 1px 4px #0000000a - stripe_height:
4px(colored bar at top) - overdue_stripe_color:
#ef4444 - overdue_card_border:
1px solid #fecaca
Row Template Layout
Top-stripe card with a horizontal metadata row.
┌──────────────────────────────────────────────────────────┐
│████████████████████████████████████████████████████████████│ ← 4px status-colored stripe
│ │
│ API Guide.docx [In Review] ███████░░░ 72% │
│ 5/15/2026 │
╰──────────────────────────────────────────────────────────╯rowFormatter JSON
Adapt before applying. The column names below ([$Status], [$Progress], [$Deadline]) are example placeholders — replace them with the actual internal column names from the user's list. Also update every status value string ('Draft', 'In Review', 'Revising', etc.) to match the user's actual Choice values. Follow list-styling Step 3.
{
"$schema": "https://developer.microsoft.com/json-schemas/sp/v2/view-formatting.schema.json",
"hideSelection": false,
"hideColumnHeaders": true,
"rowFormatter": {
"elmType": "div",
"style": {
"display": "flex",
"flex-direction": "column",
"border": "=if([$Deadline] < @now, '1px solid #fecaca', '1px solid #e5e7eb')",
"border-radius": "8px",
"background-color": "#ffffff",
"margin-bottom": "8px",
"box-shadow": "0px 1px 4px #0000000a",
"overflow": "hidden"
},
"children": [
{
"elmType": "div",
"style": {
"height": "4px",
"width": "100%",
"background-color": "=if([$Deadline] < @now, '#ef4444', if([$Status] == 'Draft', '#6b7280', if([$Status] == 'In Review', '#3b82f6', if([$Status] == 'Revising', '#f97316', if([$Status] == 'Approved', '#22c55e', if([$Status] == 'Published', '#16a34a', '#9ca3af'))))))"
}
},
{
"elmType": "div",
"style": {
"display": "flex",
"align-items": "center",
"padding": "16px 20px",
"gap": "20px"
},
"children": [
{
"elmType": "div",
"style": {
"flex": "2",
"display": "flex",
"flex-direction": "column",
"gap": "2px"
},
"children": [
{
"elmType": "div",
"style": {
"font-size": "14px",
"font-weight": "600",
"color": "#1f2937"
},
"txtContent": "=if([$FileLeafRef] == '', [$Title], [$FileLeafRef])"
},
{
"elmType": "span",
"txtContent": "=if([$Deadline] < @now, '⚠ Overdue — ' + toLocaleDateString([$Deadline]), toLocaleDateString([$Deadline]))",
"style": {
"font-size": "12px",
"color": "=if([$Deadline] < @now, '#ef4444', '#9ca3af')",
"font-weight": "=if([$Deadline] < @now, '600', '400')"
}
}
]
},
{
"elmType": "span",
"txtContent": "[$Status]",
"style": {
"display": "inline-block",
"padding": "4px 12px",
"border-radius": "4px",
"font-size": "12px",
"font-weight": "600",
"white-space": "nowrap",
"color": "#ffffff",
"background-color": "=if([$Status] == 'Draft', '#6b7280', if([$Status] == 'In Review', '#3b82f6', if([$Status] == 'Revising', '#f97316', if([$Status] == 'Approved', '#22c55e', if([$Status] == 'Published', '#16a34a', '#9ca3af')))))",
"border": "=if([$Status] == 'Draft', '1px solid #6b7280', if([$Status] == 'In Review', '1px solid #3b82f6', if([$Status] == 'Revising', '1px solid #f97316', if([$Status] == 'Approved', '1px solid #22c55e', if([$Status] == 'Published', '1px solid #16a34a', '1px solid #9ca3af')))))"
}
},
{
"elmType": "div",
"style": {
"flex": "1.5",
"display": "flex",
"align-items": "center",
"gap": "8px"
},
"children": [
{
"elmType": "div",
"style": {
"flex": "1",
"height": "6px",
"background-color": "#e5e7eb",
"border-radius": "3px",
"overflow": "hidden"
},
"children": [
{
"elmType": "div",
"style": {
"width": "=toString([$Progress]) + '%'",
"height": "100%",
"border-radius": "3px",
"background-color": "=if([$Progress] < 30, '#ef4444', if([$Progress] < 66, '#3b82f6', '#22c55e'))"
}
}
]
},
{
"elmType": "span",
"txtContent": "=toString([$Progress]) + '%'",
"style": {
"font-size": "13px",
"font-weight": "600",
"color": "#374151",
"min-width": "36px",
"text-align": "right"
}
}
]
}
]
}
]
}
}Checklist — "I Can't Believe That's SharePoint"
- ✅ Full rowFormatter — NOT default column grid
- ✅ 4px colored STATUS STRIPE across the top of each card — this IS the style
- ✅ Stripe color changes per status AND turns red for overdue
- ✅ Compact single-row horizontal layout below the stripe
- ✅ Self-colored badge borders (border matches background)
- ✅ Title Case on badges — not uppercase
- ✅ Blue mid-range progress fill (#3b82f6)
- ✅ Date is secondary text below the document name — not a separate compartment
- ✅ Overdue shows inline with the date ("⚠ Overdue — 4/25/2026")
- ✅ Very subtle shadow and border — precision, not drama
- ✅ Most compact layout of all styles — highest information density
- ✅ Completely different from: Neobrutalism (stripe vs sidebar), Glassmorphism (horizontal vs stacked), Bento (single-row vs compartments), Retro (subtle vs loud)
Responsive / mobile
- ≤ 480 px: stack the inline metadata (status pill, progress, deadline) under the title rather than beside it. The top status-colored stripe stays its full width.
- Min-width hygiene: every text child needs
min-width: 0so long document names ellipsis-truncate without pushing siblings off-screen. - Touch targets: the row card is the click target — keep its height ≥ 56 px on mobile.
- Hero text: 14 px on desktop is already the floor; do not step down further or the precision tone collapses.
Implementation notes
Two independent color channels — don't collapse them
This is the single most common adaptation mistake. The style uses two color encodings simultaneously and they are driven by different fields:
| Element | Driven by | Example |
| Top stripe color | Status (Choice value → palette swatch) | In Review → amber stripe |
| Progress fill color | Progress percentage (red < 30% · amber 30–70% · blue ≥ 70%) | 82% → blue fill |
A card can therefore have an amber stripe and a blue progress fill simultaneously — that is correct, not a bug. When adapting the rowFormatter, keep these two if() expressions completely separate. Never derive one from the other.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

