Nah Mean

Nah Mean

Use this skill in four gears:

• Nah-Mean: lightweight intent read before execution. This is not a full plan.
• Aljalttak: choose the smallest fitting executor route after confirmation or fast-mode trigger.
• Gamdadwi: post-work correction recovery when the user disliked the result and wants the agent to realign intent before rework.
• Gamdasal: positive alignment feedback when the user confirms the agent captured intent accurately and wants that signal reflected in memory.

Core Behavior

When triggered, do not execute target work immediately unless the user asks for fast execution with phrases like "바로 해", "확인 생략", "질문하지 말고 진행", Korean initial aliases like "ㅂㄹㅎ", "ㅎㅇㅅㄹ", "ㅈㅁㅎㅈㅁㄱㅈㅎ", or English phrases like "just do it", "skip confirmation", or "proceed without asking".

Default mode:

1. Give a compact Nah-Mean read: intent, risk, execution standard.
2. Ask at most 1 to 3 narrowing questions only when the default would be risky.
3. Wait for confirmation.
4. Use Aljalttak dispatch to choose the executor route and then execute.

Fast mode:

1. Give one short Nah-Mean read.
2. Pick an Aljalttak executor route.
3. Execute immediately.

Post-work correction mode:

When the user says "감다뒤" or "ㄱㄷㄷ" after seeing a result, treat it as a correction trigger, not as a new pre-execution alignment trigger.

1. Do not defend the previous result or patch immediately.
2. Restate the intent you thought you were optimizing for.
3. Name where the result likely missed the user's intended sight.
4. Propose the corrected execution standard and Aljalttak route.
5. Rework only after the user confirms, unless they explicitly tell you to proceed.

Positive alignment feedback mode:

When the user says "감다살" or "ㄱㄷㅅ" after an alignment or result, treat it as a positive feedback trigger that the user's intent was accurately expressed.

1. Briefly acknowledge the matched intent without praise or celebration.
2. Restate the exact interpretation, standard, or preference that should be reinforced.
3. Update runtime preference memory from that feedback.
4. Write durable memory only when the user explicitly asks, the preference repeats, or project rules require it.
5. Apply the reinforced preference to the next relevant work unless current instructions conflict.

Aljalttak Dispatch

After alignment, pick one route. Keep it implicit unless naming it helps the user.

| Route | Use when | | --- | --- | | Direct | answer or rewrite can be done without tools | | Edit | files need small scoped changes | | Build | multi-file implementation or structured artifact creation | | Research | current facts, sources, or external comparison matter | | Design | UI/visual/product taste is central | | QA | user asks whether it works, or proof is needed | | Safety Gate | destructive, security, legal, financial, or deployment risk needs explicit confirmation |

Response Shape

Use Korean when the user writes Korean. Use English when the user writes English. For mixed input, match the user's dominant language.

Short Korean shape:

뭔말알.
의도: ...
주의: ...
기준: ...
알잘딱 route: ...

이 기준으로 진행하면 된다.

Short Korean correction shape:

감다뒤 인식.
내가 잡았던 의도: ...
어긋난 지점: ...
다시 맞출 sight: ...
재작업 기준: ...
알잘딱 route: ...

이 기준으로 다시 잡으면 된다.

Short Korean positive feedback shape:

감다살 인식.
맞게 잡은 의도: ...
강화할 기준: ...
메모리 반영: runtime preference에 반영. durable 저장은 조건 충족 시만.
다음 적용: ...

Short English shape:

Got it.
Intent: ...
Watchout: ...
Standard: ...
Route: ...

If this is right, I will proceed on this basis.

Memory Boundary

Maintain preference memory inside the current conversation when possible. Treat it as runtime personalization, not guaranteed durable storage.

Use durable memory or wiki tools only when available and appropriate:

• Query long-term project or user context when project instructions call for it.
• Do not write durable memory for one-off taste, uncertain inference, or rejected assumptions.
• Write durable memory only when the user explicitly asks, a preference repeats, or project-level rules require persistence.
• Current user instructions override older memory.

Reference Files

Read only what is needed:

• references/core.ko.md: full Korean contract and examples.
• references/core.en.md: full English contract and examples.
• references/adapters.md: portable guidance for Codex, Claude Code, Hermes-like, and generic agent frameworks.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: handlecusion
• Source: handlecusion/nah-mean
• License: MIT
• Homepage: https://handlecusion.github.io/nah-mean/

Install and usage instructions live in the source repository linked above.