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 No key found in README or SKILL.md
- Category Otros
Para autores: añade una insignia a tu README
Si lo creaste tú, pega este código en tu README. La insignia enlaza a esta página.
[](https://mcp.popnx.com/en/skills/fjz13-unrealspecifiers)Skills parecidas
Mismo tipo de trabajo, ordenadas como la lista de Skills
| Este UnrealSpecifiers | llmfit | claude-video | VideoCaptioner | claude-cookbooks | |
|---|---|---|---|---|---|
| Autor | fjz13 | AlexsJones | bradautomates | WEIFENG2333 | anthropics |
| Skills | 1 | 1 | 1 | 1 | 4 |
| Estrellas de GitHub | 1065 | 39.036 | 21.085 | 16.557 | 54.799 |
| Último cambio de código | 7 jun 2026 | 16 nov 2026 | 25 sept 2026 | 12 sept 2026 | 5 nov 2026 |
| Licencia | – | MIT | MIT | GPL-3.0 | MIT |
1 skills (conjuntos de instrucciones) de fjz13 que la IA lee y sigue · no es un MCP server
En qué se diferencia un Skill de MCP
MCP = las manos
Conecta la IA a un servicio o dato externo, como leer Notion o crear una factura. Necesita un programa o servidor en marcha.
Skill = el manual
Un archivo de texto que enseña a la IA cómo hacer una tarea. No se conecta a nada.
A veces se parecen: algunas Skills ejecutan scripts que llaman herramientas y algunos MCP solo envían conocimiento. Empieza por la tarea que quieres hacer.
Funciona con
Claude CodeCodex
Según el README del autor y las carpetas del repo
Instalar
Is it safe?
- Who made it
GitHub account fjz13 (person), 15 years old
- Use and upkeep
★ 1065 stars · code last changed 7 jun 2026
- 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
Primero: ¿qué IA usas?
Elige tu app y esta página mostrará solo cómo instalarlo en ella
Option 1Upload to claude.ai (web and app)
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
Open Skills on claude.ai and upload
+Create skillUpload a skillpick ue-specifiers.zip
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 12 nov 2026 · Source: support.claude.com, support.claude.com, code.claude.com
Option 1Deja que Claude Code lo instale
Copia esta frase y pégala en un chat de 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
Vuelve a abrir Claude Code y escribe /ue-specifiers, o pide una tarea relacionada y Claude lo usará
Checked against official docs 12 nov 2026 · Source: code.claude.com
For Terminal users
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Abre la Terminal
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Copia la carpeta del skill a ~/.claude/skills
Descarga el repo a una carpeta temporal y copia solo las carpetas con 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-specifiersVuelve a abrir Claude Code y escribe /ue-specifiers, o pide una tarea relacionada y Claude lo usará
App de escritorio de ChatGPT
La app de escritorio de ChatGPT incluye Codex, y Codex lee las skills de la carpeta ~/.agents/skills
Option 1Deja que ChatGPT lo instale
Abre Codex en la app de escritorio de ChatGPT y pega esta frase en el chat
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 2Coloca la carpeta tú mismo
Coloca la carpeta ue-specifiers en ~/.agents/skills/ue-specifiers
~ es tu carpeta de inicio ($HOME)
For Terminal users
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Abre la Terminal
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Copia la carpeta del skill a ~/.agents/skills
Descarga el repo a una carpeta temporal y copia solo las carpetas con 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
Después de instalar
- App de escritorio de ChatGPT: abre Skills en la barra lateral para ver que la skill está
- Para usarla: en ChatGPT escribe @ y elige la skill · en Codex CLI o la extensión del IDE ejecuta /skills o escribe $ y el nombre de la skill
- Codex detecta solo las skills recién instaladas; si una no aparece, reinicia Codex
Checked against official docs 15 nov 2026 · Source: learn.chatgpt.com
ChatGPT en la web y el móvil
Las skills que instalas tú no funcionan aquí; solo las que vienen con un plugin del directorio
Para usar esta skill con ChatGPT, usa la app de escritorio de ChatGPT como se indica arriba
Checked against official docs 15 nov 2026 · Source: learn.chatgpt.com
Option 1Deja que Codex lo instale
Copia esta frase y pégala en un chat de Codex · Sirve en Codex dentro de la app de escritorio de ChatGPT, en Codex CLI y en la extensión del 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 detecta solo las skills recién instaladas; si una no aparece, reinicia Codex · Para usarla: en ChatGPT escribe @ y elige la skill · en Codex CLI o la extensión del IDE ejecuta /skills o escribe $ y el nombre de la skill
Checked against official docs 15 nov 2026 · Source: learn.chatgpt.com
For Terminal users
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Abre la Terminal
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Copia la carpeta del skill a ~/.agents/skills
Descarga el repo a una carpeta temporal y copia solo las carpetas con 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-specifiersVuelve a abrir Codex y pide una tarea relacionada; Codex mostrará el skill
Option 1Deja que Cursor lo instale
Copia esta frase y pégala en un chat de 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
En el chat Agent de Cursor escribe / y elige ue-specifiers
Checked against official docs 12 nov 2026 · Source: cursor.com
For Terminal users
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Abre la Terminal
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Copia la carpeta del skill a ~/.cursor/skills
Descarga el repo a una carpeta temporal y copia solo las carpetas con 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-specifiersEn el chat Agent de Cursor escribe / y elige ue-specifiers
Option 1Let the AI install it
Para otras apps que leen skills. La frase incluye las rutas de Claude Code, Codex y Cursor para que la IA elija la de tu app · 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 12 nov 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com
For Terminal users
Otras apps con Agent Skills (como Gemini CLI o GitHub Copilot) usan otras carpetas. Mira la guía de esa app y copia allí la carpeta con el SKILL.md.
Carpetas de skills comprobadas con las guías oficiales de Claude Code, Codex y Cursor el 11 nov 2026
✓ Comandos revisados el 18 nov 2026
Ver el SKILL.md original
El texto siguiente viene del repo del autor, no de PopNx MCP
5748 caracteres · Abrir el archivo completo en 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.
Conversación
Pregunta, comparte un consejo o avisa de que no funciona. Ordenado por lo que la gente marcó como útil.
Aún no hay publicaciones. Sé la primera persona en preguntar o compartir.
Lo publicado aquí lo escriben usuarios, no el equipo de PopNx.
Desde GitHub
- Estrellas en GitHub
- 1065
- Autor
- fjz13
- Licencia
- Sin licencia indicada Este repo no indica licencia: por defecto el autor conserva todos los derechos. Pregunta antes de compartirlo o usarlo comercialmente.
- Último cambio de código
- 7 jun 2026
- Archivos SKILL.md del repo (con traducciones y plantillas)
- 1
- Temas
- metadata, specifiers, ue5