taewanu

@taewanu source repo

12 skills
0 followers
6 hours ago last updated

▌
Statusline · taewanu bundle
Install, update, or customize the zoned-gauge Claude Code statusline, one line showing the model name and context tokens plus 5-hour, weekly, and per-model usage limits as instrument-style bars with reset countdowns. Use when the user wants usage limits or token info in the Claude Code statusline, asks to tweak its bars, colors, zones, or divider, or wants per-model weekly usage that the /usage panel shows but statusline stdin does not provide. Triggers: "statusline 설정", "상태줄에 사용량", "게이지 바꿔줘", "Fable 사용량 보여줘", "set up my statusline", "usage bars in statusline", "show weekly limit in status bar", "/statusline".

0
installs
▌
Time Tracking · taewanu bundle
Track per-session work time on freelance/personal projects with automatic timestamps, timezone, and category breakdowns. Supports multiple open sessions via switch / pause+resume / concurrent. Use whenever the user wants to start, end, pause, resume, switch, analyze, or invoice a work session, including phrases like "시작", "끝", "일시정지", "재개", "전환", "갈아타", "타임 트래킹 시작", "세션 종료", "이번 주 분석", "분석해줘", "<client> 청구서", "start tracking", "end session", "pause session", "resume", "switch to <project>", "analyze hours", "invoice for X", or simply invoking the skill via /time-tracking. Triggers on any work-session timing intent, even if the user doesn't say "track" or "skill" explicitly.

0
installs
▌
Break The Frame · taewanu
Generate unexpected, frame-breaking angles on a strategy, product, business model, or career situation by force-applying a library of inversion operators to the user's CONCRETE assets, not by free-associating. Sibling of step-back-as-user and step-back-as-maintainer, but the lens is strategy / identity / business-model, not UX or code. Each angle names a real stake (who has what on the line) and why it was invisible. Use when the user asks for a fresh or unexpected perspective, a different angle, a breakthrough, a way out of a rut, says 'be creative', 'think outside the box', 'what am I not seeing', '색다른 관점', '생각 못한 각도', '돌파구', '프레임 깨줘', or when a discussion has converged too early and needs shaking.

0
installs
▌
Visual Explainer · taewanu bundle
Turn a tangled technical thing (a gnarly bug and the decision it forces, a non-obvious system behavior, an architectural "why") into ONE self-contained, conclusion-first HTML page that explains it, can be handed off, and copies itself back out as Markdown. Use when the user wants something *explained and handed off*: "이거 왜 이런지 설명자료로 만들어줘", "남들도 이해하게 정리해줘", "이슈 설명 페이지", "결정 배경 정리", "explain this so the team gets it", "write up why this happens", "make a shareable explainer", "document this decision/tradeoff". Sibling of `visual-code-lecture` / `visual-code-review`, which annotate *real code*; reach for THIS when the subject is a situation, a decision, or a phenomenon. Not `visual-ui-compare` (pick by eye), not `/code-review` (audit).

0
installs
▌
Step Back As User · taewanu
Step out of the current solution frame and re-enter from the user's side. Two modes, (1) **friction**: become the end user and walk a specific moment, noticing where they stall; (2) **reference**: anchored to a specific moment, surface how 2–3 well-known products solve it and the tradeoff each took. Use when the user asks to "think from the user's perspective", wants a fresh angle on a flow or screen, is reviewing for friction, is stuck on how to handle a UX moment ("how do others do this"), or whenever the current line of thinking has gotten too internal and risks losing sight of who it's for.

0
installs
▌
Sketch To Diagram · taewanu bundle
Turn a photo of a hand-drawn concept diagram (architecture flow, boxes/arrows, coverage brackets, annotations) into a clean, self-contained HTML diagram in a fixed hand-drawn house style. Runs a multi-stage workflow whose critic actually SEES the rendered output (Chrome-headless screenshot) and refines it, so the diagram reads clearly instead of faithfully reproducing a messy sketch. Use when the user photographs a whiteboard/notebook sketch and wants it digitized: "이 손그림 다이어그램 깔끔하게", "스케치 사진 html로", "화이트보드 정리해줘", "그린 거 디지털로", "digitize this sketch", "turn my whiteboard photo into a diagram", "clean up this hand-drawn diagram", "render this sketch as html". For CONCEPT diagrams, not UI wireframes (those go to v0/Figma) and not a correctness audit.

0
installs
▌
Create Obsidian Note · taewanu bundle
Capture notes into the user's personal Obsidian vault the way its conventions require, and work with its Bases and Categories. Use this WHENEVER the user wants to save, capture, or jot down a note, insight, concept, or learning into their Obsidian vault, or create or edit a Base or Category there, even if they never say "Obsidian", as long as the intent is clearly to persist something into their personal notes. Use it too when they ask where a note should go or how the vault is organized.

0
installs
▌
Visual Code Review · taewanu bundle
Render a diff, PR, or slice of code as a single self-contained HTML page: the real diff with inline margin annotations, a flow diagram, key snippets, risks, open questions. Click-to-copy notes round-trip decisions to chat. Two modes: **review** (a change/diff/PR) and **explain** (existing code or a subsystem). Use whenever the user wants a change or codebase made legible visually ("이 diff 설명해줘", "PR 리뷰 보기 좋게 만들어줘", "이 코드 흐름 그림으로", "아키텍처 html로 설명", "walk me through this PR", "explain this diff/PR as html", "visualize this change", "help me understand this module") or is about to dump a long diff as plain markdown. NOT a graded correctness audit: that's `/code-review`; this can lay those findings over the diff.

0
installs
▌
Visual UI Compare · taewanu bundle
Generate a single self-contained HTML page for making a visual decision by eye, open it in the browser, and let the user pick: a grid of variants side-by-side (color, size, spacing, shadow, radius, border, badge or card styles), or a live preview with sliders when the choice is motion or a continuous range (animation, easing, duration, transitions). Use whenever the user wants to compare or tune a visual choice ("비교해서 보여줘", "어떤 게 나아?", "A/B 보고 싶어", "html로 만들어 봐", "직접 보고 결정할게", "easing 비교", "이 애니메이션 느낌 좀 보자", "transition 속도 조절", "compare visually", "show me side by side", "which one looks better?", "tune this animation", "slider for this") or any time you're about to use AskUserQuestion with 2+ options for a visual property.

0
installs
▌
Visual Code Lecture · taewanu bundle
Walk through code one line at a time as a guided, hand-drawn lecture: one self-contained HTML page you SCROLL, code pinned left and notes scrolling right, one note and its line(s) lit at a time, like a 족집게 강의. Use whenever the user wants code *taught* sequentially rather than scanned ("코드 한 줄씩 설명해줘", "족집게 강의처럼", "이 함수 따라가면서 설명", "이 로직 흐름 짚어줘", "라인별로 설명", "walk me through this line by line", "teach me this code", "explain this step by step", "guided tour of this function/file", "narrate this logic"). Sibling of `visual-code-review`, the static all-annotations-at-once page; reach for THIS when the goal is a paced, one-thing-at-a-time walkthrough. NOT a correctness audit (`/code-review`).

0
installs
▌
Edge Case Challenger · taewanu
Challenge a working assumption or a settled decision that nobody re-questions, by running a fixed set of probes against the ONE decision, not by free-associating about what could break. Use when something has worked long enough to feel settled and the user wants it pressure-tested: '여태 이렇게 해왔는데', '이 가정 맞나', '전제를 다시 보자', '엣지 케이스', '스케일업하면?', '이거 언젠가 터지지 않나', 'pressure-test this assumption', 'what breaks at scale', 'challenge this decision', 'is this premise still true', 'stress this at 10x', or when a decision passed review on one axis and no one checked the others.

0
installs
▌
Step Back As Maintainer · taewanu
Step out of the current frame and re-enter cold. Two modes, (1) **code**: drop the authoring frame and walk the diff/file as someone touching it months later; (2) **session**: drop the chain of reasoning in this chat and walk back into the problem as someone who just joined. Surfaces understanding cost, hidden coupling, and unstated assumptions without rewriting anything. Use when reviewing your own diff before sending it out, when finishing a feature, when something feels "clever" and you want to check it'll still be legible later, when a discussion has run long enough that you're anchored on assumptions you stopped questioning, or whenever current thinking is too tied to "I know what I just wrote/said."

0
installs

12 published skills