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의 Skill(지시 묶음) 1개, 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가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
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가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
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만 쓸 수 있습니다
이 Skill을 ChatGPT에서 쓰려면 위 방법대로 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가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
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가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
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/formkitSkill을 읽을 수 있는 다른 앱용입니다. 이 문장에는 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
Gemini CLI, GitHub Copilot 같은 다른 Agent Skills 지원 앱은 폴더가 달라요. 그 앱 안내를 보고 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
질문하고, 팁을 나누고, 안 되는 점을 알려 주세요. "도움이 됨"이 많은 순서예요.