open-index/open-npm huggingface dataset:
npm package: @nova-flow/lint
Description: ```json   "editor.codeActionsOnSave": {     "source.fixAll.biome": "explicit"   } ```
Latest version: 0.0.1

# @nova-flow/lint

## vscode 设置
### .vscode/settings.json 
```json
  "editor.codeActionsOnSave": {
    "source.fixAll.biome": "explicit"
  }
```

## 默认配置 
+ [biome.jsonc](./biome.jsonc)

## monorepo 配置 
> 根目录 biome.jsonc
```json
{
  "root": true,
  "extends": ["@nova-flow/lint"]
}

```
npm package: @nova-infra/d2c-cli
Description: Agent-friendly Figma design extraction CLI
Latest version: 1.0.4

# @nova-infra/d2c-cli (nova-d2c)

Agent-Friendly Figma 设计提取 CLI。

从 Figma 提取平台无关的设计数据（节点、组件、变量、样式、布局树）以及图片资源，供 AI Agent 驱动的 D2C 工作流使用。

官网与文档：

- 官网：https://nova-d2c.pages.dev
- 文档：https://nova-d2c.pages.dev/docs
- npmjs：https://www.npmjs.com/package/@nova-infra/d2c-cli

## 安装

```bash
npm install -g @nova-infra/d2c-cli
```

## 配置 Figma Token

从 https://figma.com/developers 获取 Personal Access Token。

推荐设置为全局环境变量（zsh）：

```bash
echo 'export FIGMA_TOKEN=figd_your_token_here' >> ~/.zshrc && source ~/.zshrc
```

也可以在命令行里用 `--token` 显式传入。

## 快速开始

```bash
# 1) 检查环境
nova-d2c doctor

# 2) 发现结构（推荐入口）
nova-d2c explore "https://www.figma.com/design/xxx"

# 3) 提取设计数据
nova-d2c get "https://www.figma.com/design/xxx" --node-id 1:2

# 4) 导出图片资源
nova-d2c images "https://www.figma.com/design/xxx" --node-id 1:2 --output ./assets
```

## 命令

### doctor

检查 Token、API 连通性与缓存状态。

```bash
nova-d2c doctor
```

### explore <figma-url>

分析文件结构并输出推荐节点与后续建议命令。

```bash
nova-d2c explore "https://www.figma.com/design/xxx"
```

### get <figma-url>

提取设计数据。

常用示例：

```bash
# 提取指定节点
nova-d2c get "https://www.figma.com/design/xxx" --node-id 1:2

# 过滤输出
nova-d2c get "https://www.figma.com/design/xxx" --node-id 1:2 --only components
nova-d2c get "https://www.figma.com/design/xxx" --node-id 1:2 --only variables
nova-d2c get "https://www.figma.com/design/xxx" --node-id 1:2 --only styles
nova-d2c get "https://www.figma.com/design/xxx" --node-id 1:2 --only tree

# 内联解析后的样式（减少下游 join 成本）
nova-d2c get "https://www.figma.com/design/xxx" --node-id 1:2 --resolved
```

### images <figma-url>

从指定节点导出 PNG/SVG 图片资源。

```bash
nova-d2c images "https://www.figma.com/design/xxx" \
  --node-id 1:2,3:4 \
  --output assets/ \
  --image-format png \
  --scale 2
```

## 选项速查

| 选项 | 说明 |
|------|------|
| `--node-id` | 节点 ID，逗号分隔 |
| `--only` | `pages` `components` `variables` `styles` `tree` `resolved` |
| `--format` | `yaml` `json` `md` `compact` |
| `--depth` | 节点遍历深度 |
| `--resolved` | `--only resolved` 的快捷方式 |
| `--output` | 写入文件路径 |
| `--no-cache` | 跳过缓存，强制重新获取 |
| `--token` | 显式传 Figma Token |
| `--image-format` | `png` 或 `svg` |
| `--scale` | PNG 缩放倍率 |

## 缓存

`get` 会将首次提取结果缓存约 5 分钟，后续使用 `--only` 切不同视图时不会重复请求 Figma API。

## License

MIT
npm package: @nova-infra/template-react-ts
Description: *Desktop shell meets fast front-end iteration — Electrobun + React 19 + Vite 8*
Latest version: 0.1.6

# Electrobun + React + Vite Starter

*Desktop shell meets fast front-end iteration — Electrobun + React 19 + Vite 8*

This template is a minimal desktop starter focused on two things:

- letting `Electrobun` stay the thin native shell
- letting `Vite 8` handle the fast front-end feedback loop
- giving the renderer a modern `React 19` default

The project is intentionally small so it is easy to extend with AI-assisted "vibe coding" sessions.

This template is published independently as `@nova-infra/template-react-ts` through npm Trusted Publishing.

## Why this shape

- Development mode loads the Vite dev server directly in an `Electrobun` window.
- Production mode builds the web app with Vite and copies the output into `views://app/...`.
- A small typed RPC example is included so the React UI can immediately talk to the Bun process.
- A local skill file is bundled in [skills/electrobun-best-practices/SKILL.md](skills/electrobun-best-practices/SKILL.md) and referenced from [AGENTS.md](AGENTS.md).
- The template keeps all top-level runtime configuration inside [electrobun.vite.config.ts](electrobun.vite.config.ts).

## Version constraints

This starter is pinned to:

- `electrobun@1.16.0`
- `react@19.2.4`
- `react-dom@19.2.4`
- `vite@8.0.0`

## Commands

```bash
bun install
bun run dev
bun run build
bun run preview
bun run update
bun run typecheck
```

The `package.json` scripts call `electrobun-vite` directly, so no local wrapper script is needed.
`bun run dev` will generate the initial `dist` output once, then keep Electrobun in watch mode with the Vite dev server.
`bun run update` refreshes the template-managed dependency versions and then runs `bun install`.

## Scaffold into the current directory

If you want to generate the starter directly in an empty folder, use either of these equivalent commands:

```bash
bunx -p @nova-infra/electrobun-vite create-electrobun .
bunx -p @nova-infra/electrobun-vite create-electrobun
```

Both forms only work when the current directory is empty, so the starter files can be written safely without overwriting anything.

## Structure

- [src/bun/index.ts](src/bun/index.ts): native app entry
- [src/shared/rpc.ts](src/shared/rpc.ts): shared RPC schema
- [src/ui/index.html](src/ui/index.html): Vite HTML entry
- [src/ui/main.tsx](src/ui/main.tsx): React bootstrap
- [src/ui/App.tsx](src/ui/App.tsx): starter UI
- [electrobun.vite.config.ts](electrobun.vite.config.ts): the only top-level config file
- `package.json` scripts: direct `electrobun-vite` entry points for dev/build/preview/update

## Extending the starter

- Replace the UI in `src/ui`.
- Add new RPC requests/messages in `src/shared/rpc.ts`.
- Keep external content sandboxed and isolated if you introduce embedded web content.