# Create FlowGram Custom Nodes

FlowGram node setup can require repeated registry, schema, and form changes. This skill guides Claude, Codex, and Claude Code through simple and custom node creation.

## Install

```bash
npx skillstore add bytedance/create-node
```

## Metadata

- Status: approved
- Slug: bytedance-create-node
- Version: 1.0.0
- Author version: 1.0.0
- Skillstore revision: r1
- Version status: valid
- Tree hash: bd65df08be1d99102f216ecc53c29f19df814cac967b0dc96e89e1bee1b5f7ea
- Author: bytedance
- GitHub username: bytedance
- License: MIT
- Repository: https://github.com/bytedance/flowgram.ai/tree/main/.claude/skills/create-node
- Ref: 67e6747f5b57a33ea8c62a0043d8f2ef310189ab
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, filesystem
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/bytedance-create-node
- Manifest: https://skillstore.pages.dev/api/skills/bytedance-create-node/manifest

## Capabilities

- Explains the FlowGram node data model for inputsValues, inputs, and outputs.
- Helps choose simple automatic forms or complex custom UI forms.
- Guides template copying for simple and complex node structures.
- Lists required registration updates for constants, node exports, and icons.
- Shows how to define JSON Schema fields and default form values.
- Provides development checks with Rush commands for build, type check, and lint.

## Use Cases

- Create a Simple Configuration Node: Use the simple template when a node only needs schema-driven fields and default form rendering.
- Build a Custom Form Node: Use the complex template when a node needs custom layout, custom components, or specialized interaction.
- Review Node Registration Steps: Check constants, exports, icons, form metadata, and validation steps before testing the new node.

## Prompt Templates

### Create a Simple Node

```
Use this skill to create a simple FlowGram node named {name} with fields {fields} and outputs {outputs}.
```

### Add a Custom UI Node

```
Use this skill to create a complex FlowGram node named {name} with a custom form section for {configuration}.
```

### Extend an Existing Pattern

```
Use this skill to adapt an existing FlowGram node pattern for {feature}, including schema, defaults, outputs, and registration.
```

### Review a Node Implementation

```
Use this skill to review my FlowGram node files for schema consistency, template variables, read-only state, and registration gaps.
```

## Limitations

- Focused on FlowGram demo-free-layout project structure.
- Does not implement backend execution logic for the new node.
- Assumes TypeScript, FlowGram form materials, and Semi UI are available.
- Copy and Rush commands should be reviewed before execution.

## Best Practices

- Keep each node focused on one workflow responsibility.
- Keep inputsValues, input schema properties, and required fields aligned.
- Run type check, lint, and demo testing after registration changes.

## Anti Patterns

- Do not create custom UI when schema-driven form rendering is enough.
- Do not leave template placeholders in node names, types, titles, or icons.
- Do not define free-form fields without constraints when validation is needed.

## Security Audit

- Audited at: 2026-07-19T02:42:53.04\+00:00
- Summary: All 103 static findings are false positives caused by Markdown formatting, TypeScript syntax, fixed imports, generic field names, and documentation links. No prompt injection, malicious intent, data exfiltration, unsafe path handling, or concealed payload was found.

## Stats

- Views: 355
- Downloads: 9
- Favorites: 0
- Popularity score: 0