deokjinlog

@deokjinlog source repo

25 skills
0 followers
6 hours ago last updated

▌
Design Style Explorer · deokjinlog bundle
사용자가 도메인(제품·서비스 주제)을 지정하면 그 도메인의 대표 화면을 30가지 디자인 스타일(SF HUD, 공공포털, 트렌디 SaaS, 고밀도 터미널, 브루탈리즘, 글래스모피즘, 미니멀 모노크롬, 럭셔리 다크, 레트로 픽셀, 에디토리얼, 네이처 오가닉, 뉴모피즘, 오로라 그라디언트, 벤토 그리드, 클레이모피즘, 머티리얼, Y2K 베이퍼웨이브, 스위스, 맥시멀리즘, 다크 대시보드, AI 프로덕트, 핀테크 소프트, 엔터프라이즈 B2B, 헬스케어 웰니스, 커머스 리테일, 다크 프로 미니멀, 웜 프로페셔널, 하이컨트라스트 접근성, 컬러풀 모던, 데이터 리치 라이트)의 HTML 시안으로 만들어 비교하게 해주는 스킬. 사용자가 "디자인 시안 뽑아줘", "스타일 비교", "30개 디자인", "○○ 도메인으로 디자인 보여줘", "디자인 탐색", "어떤 스타일이 어울릴지" 등을 말하거나, 새 제품/화면의 비주얼 방향을 고민할 때 반드시 이 스킬을 사용할 것. 특정 스타일 이름(브루탈리즘, 글래스모피즘 등)을 언급하며 화면을 요청할 때도 사용.

0
installs
▌
Code Pretty · deokjinlog bundle
Use AFTER verifying-spec passes and BEFORE generating-html during the initial-creation iteration loop of <slug>-implementation-plan.md ONLY. Dispatches a Sonnet subagent that performs a strict format + 자명한 정리 pass on every "수정 후" code block in the plan. NEVER touches "원본" blocks, prose, or tables. Stops firing once the first change-history entry is logged. Idempotent on already-clean blocks (no-op rule).

0
installs
▌
Tech Design · deokjinlog
Use after brainstorming has produced <slug>-requirements.md, before writing-plans. Conducts a technical-design dialogue (architecture → impacted components → data model → external interfaces → key decisions w/ alternatives → preliminary risks → testing strategy) and writes <slug>-tech-design.md. Ends with the main agent's spec verification gate (verifying-spec) before handing off to /writing-plans.

0
installs
▌
Brainstorming · deokjinlog bundle
You MUST use this before creating any feature, component, or behavior change. Offers two modes — PRD (structured, default) for productisation work, or Socratic (free-form, upstream-superpowers style) for exploratory/internal work. Both modes write <slug>-requirements.md to docs/features/YYYY-MM-DD-<slug>/. Does NOT cover technical design — that belongs to tech-design.

0
installs
▌
Writing Plans · deokjinlog
Use when <slug>-requirements.md and <slug>-tech-design.md exist for a feature, before touching code. Reads both, produces <slug>-implementation-plan.md (단계별 plan with bite-sized TDD tasks). Ends with the main agent's spec verification gate (verifying-spec) — covers 요구사항 + 개발방향 ↔ 구현계획서 consistency + code impact.

0
installs
▌
Change History · deokjinlog
Use when ANY MD or code is added/modified/deleted in a feature folder under docs/features/<date>-<slug>/, before commits — appends a structured change-log entry to the relevant MD's "변경이력" footer with auto-generated CH-id, reason, scope, before/after code (for code edits), and impact links.

0
installs
▌
Verifying Spec · deokjinlog
Use immediately after writing <slug>-tech-design.md (via tech-design) or <slug>-implementation-plan.md (via writing-plans), before final user handoff. Performs main-agent self-verification — A) consistency cross-check between target MD and all upstream MDs, plus C) code impact analysis (file existence, callers, side-effect candidates) — and produces a structured 4-axis report for user decision.

0
installs
▌
Executing Plans · deokjinlog
Executing Plans

0
installs
▌
Generating HTML · deokjinlog bundle
Use during the initial-creation iteration loop of <slug>-requirements.md / <slug>-tech-design.md / <slug>-implementation-plan.md. Fires before user review on every draft (v1.1.15+ unified timing — pre-review per-draft). Re-fires on each user-fix iteration. STOPS firing once the first change-history entry is logged — that boundary marks "live doc". Dispatches a single Sonnet subagent (B) in fire-and-forget mode (v2.2.1+) — generates a sibling `.html` companion (사람 전용 시각화 사본) with semantic 1:1 preservation. Main does NOT wait for the result. RAW `.md` is shown to user as-is (v2.2.1 removed the v2.2.0 A format-only pass — B alone now handles human readability). NEVER invoked on change-history appends, change-propagation cascades (use `/sync-html` instead), or partial revisions.

0
installs
▌
Risk Annotation · deokjinlog
Risk Annotation (Auto-Attach RISK Comments)

0
installs
▌
Subagent Driven · deokjinlog bundle
서브에이전트 실행 경로 (1인 개발 + 사전 검증 게이트 가정). v1.1.14+ wave-parallel — 메인이 plan 분석으로 DAG 추론 → wave 단위 pair-parallel dispatch (implementer + spec reviewer). 메인이 wave 끝에서 직렬 commit + post-hoc 충돌 검출. quality reviewer는 사전 verifying-spec + TDD + RISK + 변경이력으로 분산 흡수.

0
installs
▌
API Auto Testing · deokjinlog
Use when /api-test is invoked after /executing-plans has implemented APIs. Drives the 6-step pipeline — API inventory from <slug>-implementation-plan.md and code → SQL guides for test data acquisition (user pastes results) → pytest scenario code generation (with conftest.py auth fixture auto-selected via detect_auth.py) → execution → result recording in <slug>-implementation-plan.md change-history → fail-handling proposal.

0
installs
▌
Auto Tech Design · deokjinlog
auto-flow 2단계 — requirements.md 읽기 + adaptive 7-topic 자동 판정 + design decision 자동 alternatives 비교 → recommendation 자동 선택 + verifying-spec 4축 보고서 transition 직전 노출 + auto-writing-plans 자동 invoke. AskUserQuestion 호출 X — clarifying Q 는 prose 질의다 (본문 Anti-Patterns 와 CLAUDE.md 정본). generating-html 은 Step 4.5 fire-and-forget dispatch (v2.3.2+ — v1.1.17 '호출 부재' 룰이 반전됨).

0
installs
▌
Og Brainstorming · deokjinlog
Upstream-original (superpowers 5.0.7) brainstorming, exposed under intent-locked-workflow. Use when invoked via /og-brainstorm — free-form Socratic dialogue producing docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md, terminal state is og-writing-plans. Identical behavior to upstream brainstorming except for the og- naming and downstream pointer. Use this when the intent-locked-workflow extended workflow (PRD + 변경이력 + 위험 주석) feels heavy and you want the original superpowers experience.

0
installs
▌
Og Writing Plans · deokjinlog
Upstream-original (superpowers 5.0.7) writing-plans, exposed under intent-locked-workflow. Use when invoked via /og-write-plan after /og-brainstorm. Identical behavior to upstream writing-plans except for the og- naming and downstream pointer (handoff goes to og-executing-plans / subagent-driven-development). Use this when the intent-locked-workflow extended workflow (변경이력 / 위험주석 / verifying-spec / generating-html) feels heavy and you want the original superpowers experience.

0
installs
▌
Using Superpowers · deokjinlog bundle
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

0
installs
▌
Auto Brainstorming · deokjinlog
auto-flow 진입점 — Socratic clarifying Q (1~5개 적응) + AI 자동 approach 선택 + 자동 section 작성 + change-history 자동 + auto-tech-design 자동 invoke. 사용자 입력은 clarifying Q 답변에만. Visual Companion 호출 X. AskUserQuestion 호출 X — clarifying Q 는 prose 질의다 (본문 Anti-Patterns 와 CLAUDE.md 정본). generating-html 은 Step 4.5 fire-and-forget dispatch (v2.3.2+ — v1.1.17 '호출 부재' 룰이 반전됨).

0
installs
▌
Auto Writing Plans · deokjinlog
auto-flow 3단계 — requirements + tech-design 읽기 + AI 자동 task 분해 (TDD bite-sized + Model hint 자동) + RISK 코드 지점 §2 자동 + verifying-spec 자동 + code-pretty 호출 X (D-T12 와 일관) + change-history 자동 + auto-executing-plans 자동 invoke. AskUserQuestion 호출 X — clarifying Q 는 prose 질의다 (본문 Anti-Patterns 와 CLAUDE.md 정본). generating-html 은 Step 4.5 fire-and-forget dispatch (v2.3.2+ — v1.1.17 '호출 부재' 룰이 반전됨).

0
installs
▌
Change Propagation · deokjinlog
Use whenever the user expresses a change to existing 요구사항/개발방향/구현계획서/code in a feature folder (natural language like "X 바꿔/추가해/빼" or explicit edit-skill invocation). Identifies the change level, applies the impact matrix to surface affected downstream artifacts, gates user approval, then performs cascading updates and writes change-history entries with cross-linked CH-ids.

0
installs
▌
Og Executing Plans · deokjinlog
Upstream-original (superpowers 5.0.7) executing-plans, exposed under intent-locked-workflow. Use when invoked via /og-execute-plan after /og-write-plan. Identical behavior to upstream executing-plans — load plan, review critically, execute task-by-task, follow steps exactly. No 변경이력 / 위험주석 / git-fast mode / batched logging — those are intent-locked-workflow extensions, intentionally absent here.

0
installs
▌
Auto Executing Plans · deokjinlog
auto-flow 4단계 (마지막) — implementation-plan.md 읽기 + Entry Guard (preflight.subagent_task_entry_check) + DAG 자동 build + 무조건 wave-parallel subagent 강제 (Gate #14 override) + failure isolation 그대로 + End-of-run consolidator 자동 + finishing-a-development-branch 자동 호출. AskUserQuestion 호출 X — clarifying Q 는 prose 질의다 (본문 Anti-Patterns 와 CLAUDE.md 정본). generating-html 은 Step 4.5 fire-and-forget dispatch (v2.3.2+ — v1.1.17 '호출 부재' 룰이 반전됨).

0
installs
▌
Systematic Debugging · deokjinlog bundle
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

0
installs
▌
Requesting Code Review · deokjinlog bundle
Use when completing tasks, implementing major features, or before merging to verify work meets requirements

0
installs
▌
Subagent Driven Development · deokjinlog bundle
Use when executing implementation plans with independent tasks in the current session

0
installs
▌
Finishing A Development Branch · deokjinlog
Use when implementation is complete and tests pass. Runs the test gate one final time and emits a single termination message; user manually decides merge / PR / keep / discard. (v1.1.14 슬림화 — AskUserQuestion 게이트 + boilerplate 제거)

0
installs

25 published skills