components

Define TinyWasm component structure, embedding, CSS tokens, SSR, and PLAN.md workflow.

1|Updated Dec 2, 2023
One-click install
npx skills add https://github.com/tinywasm/devflow --skill components-tinywasm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: components
Source: https://github.com/tinywasm/devflow/tree/main/skills/components
Command: npx skills add https://github.com/tinywasm/devflow --skill components-tinywasm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TinyWasm component creation standards for tinywasm/components define a consistent, shareable blueprint for UI component development, embedding rules, CSS tokens, SSR behavior, and PLAN.md workflow to streamline reviews.

Core Features & Use Cases

  • Standardized component structure under tinywasm/components with per-component folders (go files, CSS, tests, and SSR code) to promote uniformity.
  • Clear embedding and rendering guidance, including how to embed dom.Element by value for performance and safety.
  • CSS conventions and tokens that enforce theme consistency and avoid hard-coded colors, enabling CSS-driven customization.
  • SSR separation patterns and icon registration guidelines to support pre-rendering and runtime rendering across environments.
  • PLAN.md workflow requirements to ensure documentation and review steps are followed before dispatching changes.

Quick Start

Create a new component under tinywasm/components, follow the file structure, and consult PLAN.md for review steps.

Frequently Asked Questions about components

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

FAQPage Schema
How do I standardize TinyWasm UI component file structure for consistency?

Standardizing TinyWasm UI components requires per-component folders containing Go files, CSS, tests, and SSR code. This enforces uniformity across the tinywasm/components directory and streamlines the development and review workflow.

What are the CSS token conventions for TinyWasm components?

TinyWasm CSS token conventions enforce theme consistency by avoiding hard-coded colors, enabling CSS-driven customization across components to ensure visual uniformity throughout the tinywasm/components library.

How should I handle SSR separation patterns in frontend components?

SSR separation patterns in frontend components support pre-rendering and runtime rendering across environments. Following these guidelines ensures TinyWasm components render correctly during server-side pre-rendering and client-side runtime execution.

Does embedding dom.Element by value improve component performance?

Embedding dom.Element by value improves component performance and safety. The TinyWasm component standard provides clear embedding and rendering guidance to ensure efficient DOM manipulation without pointer overhead.

What is the PLAN.md workflow requirement for TinyWasm component reviews?

The PLAN.md workflow requirement ensures documentation and review steps are followed before dispatching changes. Consulting PLAN.md during TinyWasm component development guarantees all code review standards are met prior to integration.

How do I register icons in a TinyWasm UI component?

To register icons in a TinyWasm UI component, follow the icon registration guidelines defined in the development standard. This ensures icons are properly managed and support pre-rendering and runtime rendering environments.