프로토타입 · 미리 보기: 공식 레지스트리의 모든 서버를 담고 있으며 30분마다 동기화해요. Google로 로그인하면 리뷰를 쓸 수 있어요.프로토타입 · 30분마다 업데이트
PopNx MCPAI를 쓰는 사람을 위한 MCP 서버 · 쉬운 말로 설명해요

UnrealSpecifiers Skill

저장소 ↗

제작자: fjz13★ 1,065skill 1개

설치

What it does

UE5标识符详解,包含100多个标识符以及300多个meta的解释和示例。Detailed Explanation of UE5 Identifiers, including over 100 identifiers and explanations and examples for more than 300 meta tags.

  • Connects Instruction files the AI reads
  • Account or key Not confirmed yet (README not read yet)
  • Category 기타
제작자용: README에 배지 달기

제작자라면 이 코드를 README에 붙여 넣으세요. 배지는 이 페이지로 연결됩니다.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/skill/fjz13-unrealspecifiers.svg)](https://mcp.popnx.com/en/skills/fjz13-unrealspecifiers)

비슷한 Skill

같은 종류의 작업, Skill 목록과 같은 순서

비슷한 항목과 비교
이 항목
UnrealSpecifiers
llmfitclaude-videoVideoCaptionerclaude-cookbooks
제작자fjz13AlexsJonesbradautomatesWEIFENG2333anthropics
Skill 수11114
GitHub 별1,06539,03621,08516,55754,799
마지막 코드 변경2026년 6월 7일2026년 11월 16일2026년 9월 25일2026년 9월 12일2026년 11월 5일
라이선스–MITMITGPL-3.0MIT

fjz13의 Skill(지시 묶음) 1개, AI가 읽고 그대로 일해요 · MCP server가 아니에요

Skill과 MCP의 차이

MCP = 손

AI를 외부 서비스나 데이터에 연결합니다(예: Notion 읽기, 청구서 만들기). 프로그램이나 서버가 실행 중이어야 합니다.

Skill = 안내서

작업 방법을 AI에게 가르치는 텍스트 파일. 어떤 서비스에도 연결되지 않습니다.

겹치는 경우도 있습니다. 도구를 부르는 스크립트가 있는 Skill도, 지식만 보내는 MCP도 있습니다. 하려는 작업을 기준으로 고르세요.

쓸 수 있는 앱

Claude CodeCodex

제작자 README와 repo 폴더 기준

설치

Is it safe?

  • Who made it

    GitHub account fjz13 (person), 15 years old

  • Use and upkeep

    ★ 1,065 stars · code last changed 2026년 6월 7일

  • Any scripts?

    1 scripts that can run on a computer: tools/validate.ps1

  • Uses the internet?

    No internet calls found in the scripts

  • Changes machine-wide settings?

    No hooks or writes to machine settings found

Checked automatically from the repo files at commit 38c3024 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself

먼저: 어떤 AI를 쓰시나요

쓰는 앱을 고르면 그 앱의 설치 방법만 보여 드립니다

Option 1Upload to claude.ai (web and app)

  1. Download from GitHub

    This skill has no license, so we do not hand out a ZIP from our site. Download it from GitHub and arrange the folder yourself, or use "Let the AI install it" above, which is easier

    Download from GitHub (whole repo) ↗

    Unzip it, then zip only the skills/ue-specifiers folder again. The ZIP must have a ue-specifiers folder with SKILL.md at the top level, no loose files

  2. Open Skills on claude.ai and upload

    +Create skillUpload a skillpick ue-specifiers.zip

    Open claude.ai/customize/skills ↗

  3. No Upload button? Turn on file creation first

    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

Option 1Claude Code에게 설치 맡기기

이 문장을 복사해 Claude Code 채팅에 붙여 넣으세요

Where to install
Please install the skill ue-specifiers from https://github.com/fjz13/unrealspecifiers folder skills/ue-specifiers (commit 38c3024) for all my projects, at ~/.claude/skills/ue-specifiers. First show me every file and tell me whether it has scripts or changes machine settings, then tell me the full path you will install to and wait for me to agree.
Please install the skill ue-specifiers from https://github.com/fjz13/unrealspecifiers folder skills/ue-specifiers (commit 38c3024) into the project this chat is open in (at .claude/skills/ue-specifiers). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the project name and the full path you will install to and wait for me to agree.

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를 다시 열고 /ue-specifiers를 입력하거나 관련 작업을 요청하면 Claude가 알아서 써요

Checked against official docs 2026년 11월 12일 · Source: code.claude.com

For Terminal users

Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.

  1. 터미널 열기

    Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요

  2. skill 폴더를 ~/.claude/skills에 복사

    repo를 임시 폴더에 내려받고 SKILL.md가 있는 폴더만 복사해요

    git clone --depth 1 https://github.com/fjz13/unrealspecifiers.git /tmp/popnx-skill-fjz13-unrealspecifiers-38c3024 && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-fjz13-unrealspecifiers-38c3024/skills/ue-specifiers' ~/.claude/skills/ue-specifiers
  3. Claude Code를 다시 열고 /ue-specifiers를 입력하거나 관련 작업을 요청하면 Claude가 알아서 써요

직접 설치한 Skill은 ChatGPT 데스크톱 앱, Codex CLI, IDE의 Codex 확장 프로그램에서 쓸 수 있습니다 · 웹과 모바일의 ChatGPT에서는 직접 설치한 Skill을 쓸 수 없고 디렉터리의 플러그인에 들어 있는 Skill만 쓸 수 있습니다

ChatGPT 데스크톱 앱

ChatGPT 데스크톱 앱에는 Codex가 들어 있고, Codex는 ~/.agents/skills 폴더에서 Skill을 읽습니다

Option 1ChatGPT에게 설치 맡기기

ChatGPT 데스크톱 앱에서 Codex를 열고 이 문장을 채팅에 붙여 넣으세요

Where to install
Please install the skill ue-specifiers from https://github.com/fjz13/unrealspecifiers folder skills/ue-specifiers (commit 38c3024) for all my projects, at ~/.agents/skills/ue-specifiers. First show me every file and tell me whether it has scripts or changes machine settings, then tell me the full path you will install to and wait for me to agree.
Please install the skill ue-specifiers from https://github.com/fjz13/unrealspecifiers folder skills/ue-specifiers (commit 38c3024) into the project this chat is open in (at .agents/skills/ue-specifiers). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the project name and the full path you will install to and wait for me to agree.

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

Option 2폴더를 직접 넣기

ue-specifiers 폴더를 ~/.agents/skills/ue-specifiers에 넣으세요

~는 홈 폴더($HOME)입니다

For Terminal users

Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.

  1. 터미널 열기

    Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요

  2. skill 폴더를 ~/.agents/skills에 복사

    repo를 임시 폴더에 내려받고 SKILL.md가 있는 폴더만 복사해요

    git clone --depth 1 https://github.com/fjz13/unrealspecifiers.git /tmp/popnx-skill-fjz13-unrealspecifiers-38c3024 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-fjz13-unrealspecifiers-38c3024/skills/ue-specifiers' ~/.agents/skills/ue-specifiers

설치한 뒤

  • ChatGPT 데스크톱 앱: 사이드바에서 Skills를 열어 Skill이 보이는지 확인하세요
  • 쓰는 법: ChatGPT에서는 @를 입력하고 Skill을 고르세요 · Codex CLI나 IDE 확장 프로그램에서는 /skills를 실행하거나 $ 뒤에 Skill 이름을 입력하세요
  • Codex는 새로 설치한 Skill을 스스로 찾습니다. 보이지 않으면 Codex를 다시 시작하세요

Checked against official docs 2026년 11월 15일 · Source: learn.chatgpt.com

웹과 모바일의 ChatGPT

직접 설치한 Skill은 쓸 수 없고, 디렉터리의 플러그인에 들어 있는 Skill만 쓸 수 있습니다

이 Skill을 ChatGPT에서 쓰려면 위 방법대로 ChatGPT 데스크톱 앱을 쓰세요

Checked against official docs 2026년 11월 15일 · Source: learn.chatgpt.com

Option 1Codex에게 설치 맡기기

이 문장을 복사해 Codex 채팅에 붙여 넣으세요 · ChatGPT 데스크톱 앱 안의 Codex, Codex CLI, IDE 확장 프로그램에서 모두 쓸 수 있습니다

Where to install
Please install the skill ue-specifiers from https://github.com/fjz13/unrealspecifiers folder skills/ue-specifiers (commit 38c3024) for all my projects, at ~/.agents/skills/ue-specifiers. First show me every file and tell me whether it has scripts or changes machine settings, then tell me the full path you will install to and wait for me to agree.
Please install the skill ue-specifiers from https://github.com/fjz13/unrealspecifiers folder skills/ue-specifiers (commit 38c3024) into the project this chat is open in (at .agents/skills/ue-specifiers). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the project name and the full path you will install to and wait for me to agree.

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

For Terminal users

Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.

  1. 터미널 열기

    Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요

  2. skill 폴더를 ~/.agents/skills에 복사

    repo를 임시 폴더에 내려받고 SKILL.md가 있는 폴더만 복사해요

    git clone --depth 1 https://github.com/fjz13/unrealspecifiers.git /tmp/popnx-skill-fjz13-unrealspecifiers-38c3024 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-fjz13-unrealspecifiers-38c3024/skills/ue-specifiers' ~/.agents/skills/ue-specifiers
  3. Codex를 다시 열고 관련 작업을 요청하면 Codex가 skill을 목록에 보여 줘요

Option 1Cursor에게 설치 맡기기

이 문장을 복사해 Cursor 채팅에 붙여 넣으세요

Where to install
Please install the skill ue-specifiers from https://github.com/fjz13/unrealspecifiers folder skills/ue-specifiers (commit 38c3024) for all my projects, at ~/.cursor/skills/ue-specifiers. First show me every file and tell me whether it has scripts or changes machine settings, then tell me the full path you will install to and wait for me to agree.
Please install the skill ue-specifiers from https://github.com/fjz13/unrealspecifiers folder skills/ue-specifiers (commit 38c3024) into the project this chat is open in (at .cursor/skills/ue-specifiers). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the project name and the full path you will install to and wait for me to agree.

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 채팅에서 /를 입력하고 ue-specifiers 선택

Checked against official docs 2026년 11월 12일 · Source: cursor.com

For Terminal users

Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.

  1. 터미널 열기

    Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요

  2. skill 폴더를 ~/.cursor/skills에 복사

    repo를 임시 폴더에 내려받고 SKILL.md가 있는 폴더만 복사해요

    git clone --depth 1 https://github.com/fjz13/unrealspecifiers.git /tmp/popnx-skill-fjz13-unrealspecifiers-38c3024 && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-fjz13-unrealspecifiers-38c3024/skills/ue-specifiers' ~/.cursor/skills/ue-specifiers
  3. Cursor Agent 채팅에서 /를 입력하고 ue-specifiers 선택

Option 1Let the AI install it

Skill을 읽을 수 있는 다른 앱용입니다. 이 문장에는 Claude Code, Codex, Cursor 경로가 들어 있어 AI가 쓰는 앱에 맞게 고릅니다 · Copy this sentence into the app’s chat

Where to install
Please install the skill ue-specifiers from https://github.com/fjz13/unrealspecifiers folder skills/ue-specifiers (commit 38c3024) for all my projects, at ~/.claude/skills/ue-specifiers (in Codex use ~/.agents/skills/ue-specifiers, in Cursor ~/.cursor/skills/ue-specifiers). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the full path you will install to and wait for me to agree.
Please install the skill ue-specifiers from https://github.com/fjz13/unrealspecifiers folder skills/ue-specifiers (commit 38c3024) into the project this chat is open in (at .claude/skills/ue-specifiers; in Codex use .agents/skills/ue-specifiers, in Cursor .cursor/skills/ue-specifiers). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the project name and the full path you will install to and wait for me to agree.

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

For Terminal users

Gemini CLI, GitHub Copilot 같은 다른 Agent Skills 지원 앱은 폴더가 달라요. 그 앱 안내를 보고 SKILL.md가 있는 폴더를 복사하세요.

GitHub에서 보기 ↗

2026년 11월 11일에 Claude Code, Codex, Cursor 공식 안내로 skill 폴더 확인

✓ 명령 확인 2026년 11월 18일

원본 SKILL.md 보기

아래 글은 제작자 repo에서 온 것이며 PopNx MCP의 지시가 아니에요

5,748자 · GitHub에서 전체 파일 열기

---
name: ue-specifiers
description: Use when writing, editing, reviewing, validating, or explaining Unreal Engine C++ reflected declarations: UCLASS, USTRUCT, UENUM, UINTERFACE, UPROPERTY, UFUNCTION, UPARAM, UMETA, meta=(...), Blueprint exposure, Details Panel, replication/RPC, SaveGame, Config, Instanced objects, UMG binding, type pickers, UHT diagnostics, or UE5.8 specifier behavior.
---

# ue-specifiers

Use this skill to make Unreal Engine C++ reflected declarations correct while writing code. Treat it as a code-authoring guardrail first, and as a reference lookup only when the user is asking about specifiers/metadata directly.

## Language

- Default output language: Chinese.
- Keep code identifiers in English.
- Keep Unreal Engine official terms in English when translation would reduce clarity.

## Evidence And Status

Source documents and indexes use these statuses to control code recommendations:

- `verified_UE5.8`: may use for UE5.8 when the use case matches the source document caveats. This means checked against UE5.8 source, UHT/parser behavior, successful compile evidence, or a focused repro sufficient for recommendation; it does not require manual editor UI testing for every variation.
- `changed_in_version`: do not use as a normal UE5.8 solution; explain the version change only when relevant and prefer the current engine path.
- `removed_or_deprecated`: do not use for new code; mention only for migration, diagnosis, or historical compatibility.

Do not present local project observation as general Unreal Engine behavior unless the source document also gives broader evidence. Cold or internal rows such as UHT-only, NoExportTypes-only, generated, plugin-specific, or negative-reference pages can be `verified_UE5.8` but still not appropriate for ordinary project code; state the scope before recommending them.

## Code Authoring Workflow

When writing or editing UE C++ reflected declarations:

1. Infer the reflected contract before choosing specifiers: C++ only, Blueprint API, Details Panel editing, config, SaveGame, replication/RPC, instanced subobject, type/object picker, editor-only behavior, or UHT-only behavior.
2. Use the minimal specifier and metadata set that satisfies that contract. Do not add Blueprint, editor, config, network, or SaveGame exposure unless the code path requires it.
3. Check that every chosen specifier/meta key is valid for its macro and declaration kind: `UCLASS`, `USTRUCT`, `UENUM`, `UINTERFACE`, `UPROPERTY`, `UFUNCTION`, `UPARAM`, `UMETA`, or `meta=(...)`.
4. For code-writing tasks with combined behavior such as Blueprint exposure plus Details Panel editing, persistence, networking, instancing, Blueprint node shape, UMG binding, bitmask, picker behavior, or subsystem metadata, check `references/indexes/constraints.index.md` before opening source docs.
5. For single known symbols or direct lookup questions, search `references/indexes/common.index.md` first. If a bare symbol can refer to multiple source docs and the macro/context is unclear, use `references/indexes/ambiguous-symbols.index.md` to disambiguate. For obscure, version-sensitive, or UHT-diagnostic choices, open `references/indexes/routing.index.md`, choose the smallest next file, then use `references/indexes/sources.index.md` only as a category directory.
6. Open source documents only when needed to resolve validity, scope, caveats, common misuse, or UE version behavior. When a source document has `Decision Summary`, read that section first and use the longer body only for evidence or edge cases. In `common.index.md`, `Doc` is relative to `references/sources/`; in category indexes, combine the nearest `Doc root` with the row `Doc`, and treat `Doc root` as relative to `references/sources/`.
7. Prefer code that compiles under UE5.8 UHT behavior. Mention version uncertainty only when the item is not verified for the target UE version or when behavior is version-sensitive.

## Code Output Rules

- For code-writing tasks, output the corrected UE C++ code in the repository's existing style.
- Do not turn normal code generation into a specifier reference answer.
- Explain specifier/meta choices only when they are non-obvious, risky, deprecated, version-sensitive, contrary to the user's requested exposure, or explicitly requested.
- If the requested exposure is too broad, use the narrower valid specifier set and briefly state the reason.
- If the user's code does not need reflection, do not add Unreal reflection macros or metadata just because the surrounding code uses them.

## Minimal Exposure Defaults

- Prefer C++-only declarations when Blueprint/editor/config/network systems do not need access.
- Prefer read-only Blueprint exposure over write exposure unless Blueprint mutation is part of the workflow.
- Prefer the narrowest Details Panel edit scope: defaults-only, instance-only, or visible-only as required by the use case.
- Do not add `EditAnywhere`, `BlueprintReadWrite`, `BlueprintCallable`, `Config`, `SaveGame`, replication, or RPC specifiers as convenience defaults.
- For object/class/type pickers, constrain selectable types with the narrowest valid metadata instead of accepting broad UObject/class choices.

This skill does not include Unreal reflection flag reference pages. For `EClassFlags`, `EPropertyFlags`, `EFunctionFlags`, `EStructFlags`, or `EEnumFlags`, inspect Unreal Engine source directly or use a separate dedicated reference.

## Important Rules

- Do not invent Unreal specifiers or metadata keys.
- Do not silently overwrite existing knowledge.
- If knowledge is version-sensitive, record the UE version.
- Prefer actual Unreal Engine source or compiler behavior over memory.
- If evidence is insufficient, mark the item as uncertain.

토론

질문하고, 팁을 나누고, 안 되는 점을 알려 주세요. "도움이 됨"이 많은 순서예요.

아직 글이 없어요. 처음으로 질문하거나 공유해 보세요.

이곳의 글은 사용자가 쓴 것으로, PopNx 팀의 글이 아니에요.

로그인하고 글쓰기

GitHub 정보

GitHub 스타
1,065
제작자
fjz13
라이선스
라이선스 명시 없음 이 repo에는 라이선스가 없습니다. 기본적으로 제작자가 모든 권리를 가지므로 배포나 상업적 사용 전에 문의하세요.
최근 코드 수정
2026년 6월 7일
repo 안 SKILL.md(번역본과 템플릿 포함)
1
토픽
metadata, specifiers, ue5