strmt7
strmt7/project_air_defense
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/strmt7/project_air_defense --skill caveman命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Use when changing UE5 smartphone rendering, graphics settings, anti-aliasing, ambient occlusion, reflections, post-process, device profiles, or mobile performance tiers. Applies when exposing graphics options to players or claiming that a visual feature works on-device.
Use when changing a major UE5 front-end menu, options flow, modal stack, routed input surface, or layered smartphone-first menu architecture. Applies to CommonUI adoption decisions, activatable-widget stacks, menu settings flows, and player-facing mobile front-end structure.
Use when changing UE5 mobile gameplay flow, menu-to-battle state, touch input routing, hidden debug bindings, deterministic simulation ownership, or verification for a smartphone-first game. Applies to controller state, battle bootstrap, Enhanced Input, and automation-backed gameplay checks.
基于 SOC 职业分类
正在显示 SKILL.md
| name | caveman |
| description | Mandatory concise-output mode for Project Air Defense agents. |
Upstream reference: JuliusBrussee/caveman v1.5.0
This repo uses mandatory concise mode by default.
v1.5.0 factsCAVEMAN_DEFAULT_MODE -> ~/.config/caveman/config.json -> full.off disables session-start activation and writes no flag file./caveman-help is one-shot and non-persistent.wenyan-* modes.Repo policy overrides upstream configurability: default here is mandatory, instruction-only, and closest to upstream lite.
If the user explicitly asks for harder compression, escalate wording toward upstream full or ultra.
No hooks, no slash commands, no env/config readers, no flag files, and no session-persistence writes are installed here.
This repo does not expose wenyan-* modes in the default workflow.
Use the local caveman-help skill for the one-shot reference card.
Apply this only to live AI prompting or conversational output, never to repo docs, README prose, or function descriptions.
Keep progress updates and summaries short.
Prefer evidence, commands, and outcomes over commentary.
Compression changes wording only.
Do not compress away uncertainty, risk, exact dates, commands, or verification details.
Drop heavy compression when security, destructive actions, or ambiguous licenses are involved.