flowkit-naming
starsforks
How to install flowkit-naming?
webflow/webflow-skills/flowkit-naming
$npx -y skills add webflow/webflow-skills --skill flowkit-namingApply Flowkit CSS naming system in Webflow. Use when creating classes, auditing existing naming, or building new components following Flowkit conventions. Flowkit is Webflow's official CSS framework with utility-first approach. Runs headlessly against a page ID — no Designer conn
SKILL.md
| 1 | # Flowkit Naming System |
| 2 | |
| 3 | Apply FlowKit CSS naming conventions in Webflow projects using Webflow Designer tools. |
| 4 | |
| 5 | ## Important Note |
| 6 | |
| 7 | **ALWAYS use Webflow MCP tools for all operations:** |
| 8 | - Use Webflow MCP's `webflow_guide_tool` to get best practices before starting |
| 9 | - Use Webflow MCP's `data_sites_tool` with action `list_sites` to identify the target site |
| 10 | - Use Webflow MCP's `data_pages_tool` with action `list_pages` to find the target page by name or slug — headless, no Designer needed |
| 11 | - Use Webflow MCP's `data_element_tool` to inspect current classes and apply new ones — headless, pass the page's ID directly |
| 12 | - Use Webflow MCP's `data_style_tool` to create and update FlowKit-compliant styles — headless |
| 13 | - Use Webflow MCP's `webflow_guide_tool` to understand supported style properties |
| 14 | - Use Webflow MCP's `designer_tool` only if the user wants to work with whatever page is currently open in Designer, or wants to interactively select an element on the canvas |
| 15 | - DO NOT use any other tools or methods for Webflow operations |
| 16 | - All tool calls must include the required `context` parameter (15-25 words, third-person perspective) |
| 17 | - **No Designer connection is required for the core workflow.** Getting the page, inspecting classes, creating styles, and applying classes all run headlessly against an explicit page ID. Designer is only needed for the optional `designer_tool` conveniences above. |
| 18 | |
| 19 | ## Instructions |
| 20 | |
| 21 | ### Phase 1: Discovery & Setup |
| 22 | 1. **Identify the task**: Determine if user is: |
| 23 | - Creating new component classes |
| 24 | - Auditing existing class names |
| 25 | - Building complete page sections |
| 26 | - Refactoring non-FlowKit classes to FlowKit |
| 27 | 2. **Get target page**: Use Webflow MCP's `data_pages_tool` with action `list_pages` to find the page by name or slug — no Designer connection needed. If the user wants to work with whatever page they currently have open in Designer, use `designer_tool` with action `get_current_page` instead. |
| 28 | 3. **Ask for scope**: Clarify which elements or sections to work with |
| 29 | |
| 30 | ### Phase 2: Analysis (if auditing existing) |
| 31 | 4. **Get all elements**: Use Webflow MCP's `data_element_tool` to retrieve elements from the target page |
| 32 | 5. **Extract classes**: Identify all class names currently applied |
| 33 | 6. **Categorize issues**: |
| 34 | - Missing `fk-` prefix |
| 35 | - Incorrect case (uppercase/mixed case) |
| 36 | - Wrong separators (underscores instead of hyphens) |
| 37 | - Non-semantic naming |
| 38 | - Inconsistent component structure |
| 39 | 7. **Generate audit report**: Show current vs suggested FlowKit-compliant names |
| 40 | |
| 41 | ### Phase 3: Suggestion Generation |
| 42 | 8. **Apply FlowKit patterns**: Generate class names following FlowKit v2 conventions |
| 43 | 9. **Structure by type**: |
| 44 | - Component wrappers: `fk-[component]` |
| 45 | - Child elements: `fk-[component]-[element]` |
| 46 | - State modifiers: combo classes with `is-[state]` |
| 47 | - Layout utilities: `fk-flex`, `fk-grid`, `fk-stack` |
| 48 | - Spacing utilities: `fk-space-[size]`, `fk-py-[size]`, `fk-px-[size]` |
| 49 | - Typography utilities: `fk-text-[style]` |
| 50 | 10. **Validate suggestions**: Ensure all suggestions follow FlowKit conventions |
| 51 | 11. **Show preview**: Display hierarchical structure with suggested classes |
| 52 | |
| 53 | ### Phase 4: Application (if user confirms) |
| 54 | 12. **Create styles**: Use Webflow MCP's `data_style_tool` to create new FlowKit-compliant class styles |
| 55 | 13. **Update elements**: Use Webflow MCP's `data_element_tool` to apply classes to elements |
| 56 | 14. **Process in batches**: If many elements, process in groups of 10-15 |
| 57 | 15. **Show progress**: Display which elements are being updated |
| 58 | |
| 59 | ### Phase 5: Verification & Reporting |
| 60 | 16. **Verify application**: Check that classes were applied correctly |
| 61 | 17. **Generate report**: Show what was created/updated |
| 62 | 18. **Provide documentation**: Explain the FlowKit structure used |
| 63 | 19. **Suggest next steps**: Recommend additional FlowKit patterns to implement |
| 64 | |
| 65 | ## FlowKit Naming Reference |
| 66 | |
| 67 | ### Core Naming Patterns |
| 68 | |
| 69 | | Pattern | Purpose | Example | |
| 70 | |---------|---------|---------| |
| 71 | | `fk-[component]` | Component wrapper (base class) | `fk-card`, `fk-nav`, `fk-hero` | |
| 72 | | `fk-[component]-[element]` | Child element within component | `fk-card-title`, `fk-nav-link` | |
| 73 | | `fk-[component].[modifier]` | Combo class modifier (state/variant) | `fk-card.is-featured` | |
| 74 | | `fk-text-[style]` | Typography utility | `fk-text-xl`, `fk-text-bold` | |
| 75 | | `fk-flex` / `fk-grid` | Layout utilities | `fk-flex-center`, `fk-grid-3` | |
| 76 | | `fk-space-[size]` | Spacing utilities | `fk-space-md`, `fk-py-lg` | |
| 77 | | `is-[state]` | State modifiers (combo) | `is-active`, `is-hidden`, `is |
People who liked this also viewed
6 picksType
- web-design-guidelinesReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".SkillsJul 2026
- lark-slides飞书幻灯片：创建和编辑幻灯片。创建演示文稿、读取幻灯片内容、管理幻灯片页面（创建、删除、读取、局部替换）。当用户需要创建或编辑幻灯片、读取或修改单个页面时使用。当用户给出 doubao.com 的 /slides/ URL/token 时，也应直接使用本 skill，不要因为域名不是飞书而回退到 WebFetch；路由依据是 URL 路径模式和 token，而不是域名。不负责：云文档内容编辑（走 SkillsJul 2026
- design-taste-frontendTaste-Skill - gives your AI good taste. stops the AI from generating boring, generic slop SkillsJul 2026
- ui-ux-pro-maxUI/UX design intelligence for web and mobile. Searchable local database with 84 styles, 192 color palettes, 74 font pairings, 192 product types, 98 UX guidelines, 104 icon entries, 16 GSAP motion presSkillsJul 2026
- caveman-helpQuick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".SkillsJul 2026
- codebase-designShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-nSkillsJul 2026
