HuolalaTech

6 mods across 1 repository, 85 stars between them.

Kotlin-convert

01

HuolalaTech/huolala-figma-mcp

Skill Claude CodeCodex

Instructions for converting a design or HTML page into native Android views written in Kotlin. They cover layout, components, events, images, fonts, naming, and style checks.

not rated 85 4mo ago A 48 tokens original Apache-2.0

ObjectiveC-convert

02

HuolalaTech/huolala-figma-mcp

Skill Claude CodeCodex

A rulebook and checklist for converting a design or HTML page into native iOS code written in Objective-C. It covers project files, images, layout, interface controls, interactions, and style checks.

not rated 85 4mo ago A 50 tokens original Apache-2.0

HuolalaTech/huolala-figma-mcp

Skill Claude CodeCodex

A conversion guide for turning HTML or Figma designs into React Native code for mobile apps. It covers the code files, styles, names, interactive states, and repeated content.

not rated 85 4mo ago A 63 tokens original Apache-2.0

adjust-list-layout

04

HuolalaTech/huolala-figma-mcp

Skill Claude CodeCodex

A layout-refactoring guide that uses a JSON description of a page to recognize horizontal lists, vertical lists, and grids in HTML. It then reorganizes the HTML into clearer list or layout structures.

not rated 85 4mo ago A 38 tokens original Apache-2.0

HuolalaTech/huolala-figma-mcp

Skill Claude CodeCodex

A tagging step that adds a control type to matching elements in index.html based on types found in vlm_result.json. Control types include buttons, checkboxes, switches, inputs, images, and calendar controls.

not rated 85 4mo ago A 29 tokens original Apache-2.0

HuolalaTech/huolala-figma-mcp

Skill Claude CodeCodex

A conversion guide for turning an HTML design export into H5 mobile web code, React code, or Vue code. H5 means a web page designed for mobile browsers; React and Vue are tools for building user interfaces.

not rated 85 4mo ago A 51 tokens original Apache-2.0

At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: