'solidjs' 검색 결과

Add and troubleshoot the json-render inspection panel in SolidJS applications. This skill covers panel setup for examining specifications, editing state, reviewing action and stream timelines, browsing component catalogs, and selecting page elements for inspection.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Add an inspection panel to a SolidJS app
• Inspect JSON specifications and edit application state
• Review action and stream timelines

Turn json-render specifications into SolidJS interfaces. This skill guides component registration, connects inputs to application state, handles actions and validation, and helps troubleshoot how changing values update the screen, including streamed UI generation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Build SolidJS interfaces from JSON specifications
• Connect form inputs to application state
• Troubleshoot values that fail to update the screen

Expert guide for SolidJS 2 and SolidStart — fine-grained reactivity, signals, createResource, and server-first rendering / Panduan ahli SolidJS 2 dan SolidStart — reaktivitas fine-grained, signals, createResource, dan rendering server-first.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

SolidJS expert including reactivity, components, and store patterns

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Add Storybook stories, examples of component states, for the Kilo VS Code extension UI. The existing Playwright runner turns them into screenshot comparisons to check visual changes across states and widths.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Add screenshot coverage for chat or settings screens
• Check layouts at 420px and 200px widths
• Show permission requests using mock data

SolidJS fine-grained reactivity — signals, effects, memos, stores, resources, control-flow components. Load when writing Solid components or reactive state.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Tauri 2.x + SolidJS stack for Openrind Desktop native app

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

SolidJS reactivity + UI state patterns for Openrind Desktop

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

How a downstream app consumes the shared @kolu/surface stack (@kolu/surface · surface-app · surface-nix-host · surface-mcp) — declaring a typed reactive surface, serving it, consuming it (SolidJS hooks or a CLI), and mirroring a remote surface over ssh. Grounded in the real consumers: kolu, pulam-web, drishti, odu, and the TUIs. Load when wiring a surface server/client/mirror, or reaching for getHostSession / a link / the `.use()` hooks. CHANGING the framework is gated separately — `.claude/rules/surface.md` (a paired, CI-green drishti PR pinned to final kolu HEAD).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use Pierre Computer Company's `@pierre/trees` (path-first file tree) and `@pierre/diffs` (shiki-based code/diff renderer) in Kolu. Pierre ships Preact/vanilla cores with optional React wrappers — Kolu consumes the vanilla classes and wraps them in thin SolidJS components. Trigger when: wiring up a file tree, rendering unified diffs or syntax-highlighted files, replacing `@git-diff-view`, or any mention of `@pierre/trees` / `@pierre/diffs` / "pierre library".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

How a downstream app consumes the shared @kolu/surface stack (@kolu/surface · surface-app · surface-remote · surface-mcp) — declaring a typed reactive surface, serving it, consuming it (SolidJS hooks or a CLI), and mirroring a remote surface over ssh. Grounded in the real consumers: kolu, drishti, odu, and the TUIs. Load when wiring a surface server/client/mirror, or reaching for makeSession / a link / the `.use()` hooks. CHANGING the framework is gated separately — `.claude/rules/surface.md` (a paired, CI-green drishti PR pinned to final kolu HEAD).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.