Light planning mode. Use when the user requests a small, clearly-scoped change (roughly ≤3 files, no new interfaces, no ambiguity) that still deserves a written plan before code. For ambiguous or multi-component work, use the forge skill instead. Produces an…
tmdgusya/glm-hammer
SkillsMP has collected 5 skills from tmdgusya/glm-hammer. Open a skill to review its source and details.
- Latest recorded source activity
- SkillsMP catalog refreshed
- skills collected
- 5
- GitHub stars
- 17
- GitHub forks
- 4
Skills in this repository
Showing 5 of 5 collected skills.
Strong planning mode. Use when the user requests a non-trivial feature, refactor, or system change — especially when the request is ambiguous, spans multiple files, or says "제대로", "강하게", "빡세게", "thoroughly", "strong plan". Runs deep codebase recon BEFORE…
Implementation loop. Use when a plan document exists (from forge or blueprint) and implementation should run — including when the user says "implement", "execute the plan", "구현해", "실행해", or approves a plan. Executes tasks through a worker → validator →…
Presentation deck mode. Use when the user wants a presentation, slide deck, or PPTX built from a topic or script — especially when they say "발표", "슬라이드", "프레젠테이션", "발표 자료 만들어줘", "슬라이드 뽑아줘", "presentation", "slide deck", "pptx", "deck". Secures a script,…
Storyline-driven design mode. Use when the user makes a storyline- or reference-driven design request — design tokens, mood/visual identity, a style guide — especially when they say "디자인", "무드", "스토리", "레퍼런스", "design tokens", "style guide". Prospects real…