Skip to content
Skills Library
Programming · Building & coding

ui

/ui

Use this skill when contributing to InsForge's reusable UI package. This is for maintainers editing design-system primitives, exports, styles, and package-level component behavior in the InsForge monorepo.

Repository
InsForge ↗
Licence
Apache-2.0
Last repository change
24.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 24.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Use this skill when contributing to InsForge's reusable UI package. This is for maintainers editing design-system primitives, exports, styles, and package-level component behavior in the InsForge monorepo.

Original author description

Use this skill when contributing to InsForge's reusable UI package. This is for maintainers editing design-system primitives, exports, styles, and package-level component behavior in the InsForge monorepo.

How it works

  1. Scope
  2. Working Rules
  3. Validation
Original SKILL.md headings · 39 lines, 227 words
SKILL.md preview
---
name: ui
description: Use this skill when contributing to InsForge's reusable UI package. This is for maintainers editing design-system primitives, exports, styles, and package-level component behavior in the InsForge monorepo.
---

# InsForge Dev UI

Use this skill for `packages/ui/` work in the InsForge repository.

## Scope

- `packages/ui/src/components/**`
- `packages/ui/src/lib/**`
- `packages/ui/src/index.ts`
- `packages/ui/src/styles.css`

## Working Rules

1. Put only reusable primitives here.
   - If the component is generic across dashboard features or other InsForge apps, it belongs in `packages/ui/`.
   - If it is tightly coupled to one dashboard workflow but should ship to both OSS and cloud hosts, keep it in `packages/dashboard/`.
   - If it is only for the self-hosting host app, keep it in `frontend/`.

2. Preserve the package's implementation style.
   - Use `class-variance-authority` for variants when appropriate.
   - Use the shared `cn()` helper for class merging.
   - Follow the existing Radix-wrapper and typed-export patterns.

3. Keep the public surface in sync.
   - Export new public components from `packages/ui/src/index.ts`.
   - Avoid adding internal-only abstractions to the package surface unless they are meant to be consumed.
   - Never use the TypeScript `any` type. Keep component props and exported helpers strictly typed.

4. Validate downstream impact.
   - The shared dashboard package consumes this package directly, so UI changes can break `packages/dashboard/` even if `packages/ui/` itself builds cleanly.

## Validation

- `cd packages/ui && npm run build`
- `cd packages/ui && npm run typecheck`

Also validate `packages/dashboard/` when the changed component is used in the dashboard, and validate `frontend/` if the host app integration or CSS entrypoints changed.

Versions

RepositoryScoreLicence
This page · InsForge/InsForge90Apache-2.0
wellwelwel/lagune100Apache-2.0
maquina-app/rails-claude-code100MIT
tim-hub/powerball-harness100MIT
tw93/Waza90MIT
lilly-logic-labs/lll-skills90MIT
svngoku/coding-agents-skills90MIT
LeMarkk/agent-skills90MIT
melodic-software/claude-code-plugins84MIT

Identical content appears in 2 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 11b670698e0d (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90insforge-dev
    Use this skill set when contributing to the InsForge monorepo itself. This is for InsForge maintainers and contributors editing the platform, the shared dashboard package, the self-hosting shell, the UI library, shared schemas, tests, or docs.
  • 100backend
    Use this skill when contributing to InsForge's backend package. This is for maintainers editing backend routes, services, providers, auth, database logic (including RLS-enforced surfaces like storage and realtime), schedules, or backend tests in the InsForge monorepo.
  • 100insforge-debug
    Rigor Debug / Rigor Audit 技能,面向 Insforge(即时后端/数据库服务)的调试。当用户想排查 Insforge 数据模型、CLI、本地开发或部署问题时使用。
  • 100insforge-cli
    当用户需要后端,或任务通过 InsForge CLI 触及 InsForge 后端或云基础设施时使用:项目、SQL、迁移、RLS 策略、函数、存储、备份、部署、计算、密钥、配置、调度、日志、诊断、顾问扫描与抑制、导入/导出、AI/OpenRouter 设置、Stripe/Razorpay 支付、Apify 爬取、PostHog 分析、后端分支、组织成员、智能体记忆、反馈上报或 CLI 文档。应用代码集成见 insforge app-integration 技能。
  • 100insforge-cli
    Use this skill whenever someone needs a backend, or a task touches InsForge backend or cloud infrastructure through the InsForge CLI: projects, SQL, migrations, RLS policies, functions, storage, backups, deployments, compute, secrets, config, schedules, logs, diagnostics,…
  • 100insforge-integrations
    Use when wiring an external auth provider (Clerk, Auth0, WorkOS, Kinde, Stytch, Better Auth) into InsForge for JWT-based RLS, or when adding the OKX x402 payment facilitator for onchain pay-per-use billing.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.