REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
The form framework for coding agents
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/skills/formkit-formkit)在同一工作中把 AI 连到服务的 MCP
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.
MCP server for terminal commands, file operations, and process management
同类工作,排序与 Skill 列表相同
| 本项 formkit | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| 作者 | formkit | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skill 数 | 1 | 1 | 1 | 1 | 1 |
| GitHub 星标 | 4,787 | 463,670 | 233,682 | 148,887 | 143,987 |
| 最近代码更新 | 2026年11月8日 | 2026年11月17日 | 2026年4月20日 | 2026年11月17日 | 2026年11月16日 |
| 许可证 | MIT | MIT | – | Apache-2.0 | MIT |
formkit 提供的 1 个 Skill(指令集),AI 读取后照做 · 不是 MCP server
MCP = 手
把 AI 连到外部服务或数据,例如读取 Notion 或开发票。需要有程序或服务器在运行。
Skill = 手册
教 AI 怎么做某项工作的文本文件,不连接任何服务。
有些会重叠:少数 Skill 带有调用工具的脚本,少数 MCP 只提供知识。请从你想完成的工作出发。
Claude CodeCodexCursorOpenCode
依据开发者 README 和 repo 中的文件夹
GitHub account formkit (organization), 5 years old
★ 4,787 stars · code last changed 2026年11月8日
No, plain text files the AI reads and follows
No scripts, so it does not go online by itself
No hooks or writes to machine settings found
Checked automatically from the repo files at commit 990590a (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
第一步:你用哪个 AI?
选择你用的应用,本页只显示该应用的安装方法
Files are byte-for-byte the same as on GitHub at commit 990590a · View on GitHub ↗
Plain text files, no programs
Once uploaded it runs on Claude’s systems, not on your computer. No need to unzip
All 4 files · 19 KB
SKILL.md7 KBagents/openai.yaml1 KBreferences/docs-index.md11 KBLICENSE1 KB+Create skillUpload a skillpick formkit.zip
SettingsCapabilitiesCode execution and file creation
Turn on Code execution and file creation first (newer menus: Create and edit files) · personal plans: Settings → Capabilities · Team/Enterprise: an admin turns it on under Organization settings → Plugins & skills · every plan, including Free
Upload once; it works in claude.ai and Claude Desktop, and in recent Claude Code signed in with a Claude account (not with an API key)
Cowork and cloud sessions use the skills turned on in your claude.ai account, not ~/.claude/skills on your computer (Claude Desktop scheduled tasks run locally and still load it)
Checked against official docs 2026年11月12日 · Source: support.claude.com, support.claude.com, code.claude.com
复制这句话,粘贴到 Claude Code 的对话中
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
重新打开 Claude Code,输入 /formkit,或直接提出相关任务,Claude 会自动选用
Checked against official docs 2026年11月12日 · Source: code.claude.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/formkit/formkit.git /tmp/popnx-skill-formkit-formkit-990590a && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-formkit-formkit-990590a/packages/cli/assets/skills/formkit' ~/.claude/skills/formkitChatGPT 桌面应用内置 Codex,Codex 从 ~/.agents/skills 文件夹读取 Skill
在 ChatGPT 桌面应用中打开 Codex,把这句话粘贴到对话中
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
把 formkit 文件夹放到 ~/.agents/skills/formkit
~ 是你的主文件夹($HOME)
不用终端:下载 ZIP,解压后把 formkit 文件夹移到 ~/.agents/skills
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/formkit/formkit.git /tmp/popnx-skill-formkit-formkit-990590a && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-formkit-formkit-990590a/packages/cli/assets/skills/formkit' ~/.agents/skills/formkitChecked against official docs 2026年11月15日 · Source: learn.chatgpt.com
不能使用你自己安装的 Skill,只能使用目录中插件自带的 Skill
想在 ChatGPT 中使用这个 Skill,请按上面的方法使用 ChatGPT 桌面应用
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
复制这句话,粘贴到 Codex 的对话中 · 适用于 ChatGPT 桌面应用中的 Codex、Codex CLI 和 IDE 扩展
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex 会自动发现新安装的 Skill;如果没有出现,请重启 Codex · 使用方法:在 ChatGPT 中输入 @ 并选择 Skill · 在 Codex CLI 或 IDE 扩展中运行 /skills,或输入 $ 加 Skill 名称
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/formkit/formkit.git /tmp/popnx-skill-formkit-formkit-990590a && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-formkit-formkit-990590a/packages/cli/assets/skills/formkit' ~/.agents/skills/formkit复制这句话,粘贴到 Cursor 的对话中
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
在 Cursor 的 Agent 聊天中输入 / 并选择 formkit
Checked against official docs 2026年11月12日 · Source: cursor.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/formkit/formkit.git /tmp/popnx-skill-formkit-formkit-990590a && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-formkit-formkit-990590a/packages/cli/assets/skills/formkit' ~/.cursor/skills/formkit适用于其他能读取 Skill 的应用。这句话列出了 Claude Code、Codex 和 Cursor 的路径,AI 会按你的应用选择 · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs 2026年11月12日 · Source: code.claude.com, learn.chatgpt.com, cursor.com
其他支持 Agent Skills 的应用(如 Gemini CLI、GitHub Copilot)使用不同文件夹,请查看该应用的指南,再把含 SKILL.md 的文件夹复制过去。
已于 2026年11月11日 对照 Claude Code、Codex 和 Cursor 官方指南核实 skill 文件夹
✓ 命令已检查 2026年11月17日
以下文字来自开发者的 repo,不是 PopNx MCP 的指令
6,931 个字符 · 在 GitHub 打开完整文件
---
name: formkit
description: Use when working with FormKit forms, validation, schema, or custom inputs in React, Vue, or Nuxt projects.
---
# FormKit
Use this skill when you are building, debugging, or refactoring FormKit forms, inputs, schema, validation, plugins, or node-tree behavior.
## Install and setup
- Install or refresh this skill with `npx formkit skill`.
- The installer copies the skill to `~/.codex/skills/formkit`.
- The installer can also wire project instructions for Codex (`AGENTS.md`) and Claude Code (`CLAUDE.md`).
- For OpenCode, Cline, Gemini, Qwen, Amp, pi, Cursor, Copilot, and Crush, the installer prints a ready-to-paste project instructions block.
## Runtime selection
- FormKit has both React and Vue/Nuxt runtimes.
- Match the docs flavor to the project:
- React or Astro-with-React: `https://formkit.com/<page>.react.md`
- Vue or Nuxt: `https://formkit.com/<page>.vue.md`
- The full route index for both runtimes is in `references/docs-index.md`.
## FormKit Pro
- Distinguish core inputs from Pro inputs before recommending or implementing one.
- Current Pro input docs routes are:
- `/inputs/autocomplete`
- `/inputs/colorpicker`
- `/inputs/currency`
- `/inputs/datepicker`
- `/inputs/dropdown`
- `/inputs/mask`
- `/inputs/rating`
- `/inputs/repeater`
- `/inputs/slider`
- `/inputs/taglist`
- `/inputs/toggle`
- `/inputs/togglebuttons`
- `/inputs/transfer-list`
- `/inputs/unit`
- Core inputs do not require FormKit Pro. Pro inputs require `@formkit/pro` plus a FormKit Pro project key.
- To add Pro to a project:
- create a free project key at `https://pro.formkit.com`
- install `@formkit/pro`
- add `createProPlugin(...)` to the FormKit config and register the needed Pro inputs
- React projects wire Pro through the FormKit React config. Vue and Nuxt projects wire Pro through the FormKit Vue config. The Pro plugin and inputs come from `@formkit/pro`.
- FormKit Pro keys are not public values for docs or examples, but they are also not private keys in the server-secret sense. They are client-side project keys and should usually be hard-coded in the codebase or another intentionally client-exposed config surface.
- Whenever you use or recommend a Pro input, say so in the user-facing summary and explicitly mention that `@formkit/pro` and a FormKit Pro key are required.
## Mental model
- FormKit is a node tree. Inputs, forms, groups, and lists are all nodes with value, props, state, validation, messages, and plugins.
- Prefer declarative configuration through props, validation rules, schema, classes, sections, plugins, and node state.
- In general, listening to events in FormKit is an antipattern. FormKit already collects and reconciles state for you, so prefer reacting to value, validation state, form state, and node structure instead of manually wiring event chains.
- Reach for imperative event handlers only when there is no clear node- or state-driven alternative.
## Styling and themes
- Prefer Tailwind CSS 4 as the primary styling mechanism when the project can support it.
- Avoid the legacy Genesis theme by default. Prefer Regenesis or another Tailwind theme from the FormKit theme workflow.
- To generate a project-root Tailwind theme, prefer the FormKit CLI.
- For non-interactive Regenesis setup, pass the theme explicitly instead of using the prompt:
- `formkit theme --theme=regenesis`
- or `npx formkit@latest theme --theme=regenesis`
- That command generates `formkit.theme.(mjs|ts)` in the project root. Then:
- import `rootClasses` from `./formkit.theme` into the FormKit config
- add `@source "./formkit.theme.ts";` and `@source "./formkit.config.ts";` to the main Tailwind 4 CSS entry
- For theme creation or deeper customization, start with:
- `/essentials/styling`
- `/guides/create-a-tailwind-theme`
## Core nodes
- `form`: submission boundary and top-level collector. A form aggregates descendant values, manages submit lifecycle, validation visibility, settled state, loading/submitting, and errors.
- `group`: object collector. A group combines named child nodes into an object and is the correct abstraction for nested records.
- `list`: array collector. A list manages ordered children, insertion/removal/reordering, and array-shaped values and validation.
- `input`: the leaf or higher-order field node. Inputs still participate in the same node tree and inherit the same state and validation model.
## Best practices
- Keep validation co-located with the inputs that own it.
- Prefer `form`, `group`, and `list` composition over manual object or array assembly.
- Prefer node APIs, props, and derived FormKit state over DOM queries or duplicate framework state.
- For cross-field behavior, model the relationship in the FormKit tree before introducing custom event plumbing.
- For backend validation or submission failures, prefer a small adapter/helper that maps the backend error payload into FormKit form errors plus keyed input errors.
- Normalize backend field paths into FormKit addresses such as `email`, `group.name`, or `group.list.2.name`, then pass them to `node.setErrors()` or framework `setErrors()`.
- For nested groups and lists, prefer dot-notation addresses over one-off manual field wiring in submit handlers.
- Prefer Tailwind 4 theme generation over ad hoc styling when the project needs a cohesive FormKit design system.
- When a project needs first-party FormKit styling, generate Regenesis before considering Genesis.
- When customizing markup or behavior, preserve the existing schema and section structure unless the task really requires replacing it.
- In React, avoid mirroring FormKit form state in separate React state unless there is a clear boundary reason.
- In Vue or Nuxt, avoid watchers that duplicate FormKit state when node context or collected values already express the behavior.
## Workflow
1. Inspect the existing runtime, form tree, config, and validation rules.
2. Pick the runtime-specific markdown page from `references/docs-index.md`.
3. Prefer the smallest declarative change that keeps behavior inside FormKit.
4. If multiple fields interact, model that through `form`, `group`, `list`, validation, schema, or node state before adding listeners.
5. If backend errors are involved, add or reuse one adapter that converts the server response into FormKit form errors and dot-notation input-error keys.
## Pulling specific docs
- Open the exact runtime page directly from `references/docs-index.md`.
- If you only know the route, use:
- React: `https://formkit.com/<page>.react.md`
- Vue: `https://formkit.com/<page>.vue.md`
- Start with:
- `/getting-started/installation`
- `/essentials/architecture`
- `/essentials/forms`
- `/essentials/validation`
- `/essentials/styling`
- `/guides/create-a-tailwind-theme`
- `/inputs/form`
- `/inputs/repeater`
- the specific `/inputs/<type>` page involved in the task
提问、分享技巧或报告无法使用。按“有帮助”数量排序。