Safely delete a document from an agent-authored content collection (notes, inbox, sources, wiki) by first mapping every inbound reference to it across the whole repo, surfacing structural dependencies (hub↔child, category TOC), and only then removing it with git rm so the deletion is reviewable and reversible. Never auto-rewrites inbound links — it reports them and proposes edits. Handles hubs with children explicitly (delete subtree / reparent / abort), never orphaning children. Use when the user asks to delete/remove a note, wiki card, spec, or inbox capture, or to clean up an obsolete doc without leaving dangling links. 노트·위키· 스펙·inbox 문서 안전 삭제, 참조 파악 후 삭제, dangling 링크 없이 정리 요청에 사용.
2026-07-30
Take a raw idea, research BOTH how to best develop it (idea-handling methodologies) AND its subject-domain evidence (official/primary sources first), apply the chosen methodology, and persist the result as an OKF note under src/content/idea, served on the unlisted /idea route. /idea behaves like the notes route (URL-only, excluded from search index, sitemap, and robots) but is additionally NOT linked in the footer — reachable only by a direct URL. Content is committed plaintext, so it is public-if-found; do not put secrets in it. Use when the user hands over an idea to develop, expand, pressure-test, or capture. 아이디어를 방법론+도메인 근거로 조사·발전시켜 unlisted /idea 노트로 남길 때 사용. 아이디어 정리·발전·검증 요청에 사용.
2026-07-30
Lightweight idea capture. Given a raw idea (or a few), do a light cleanup, list a handful of questions worth exploring next, and run a quick scan of related references and existing services — then save it as a short note under src/content/idea/inbox, served at /idea/inbox/. This is the fast, low-ceremony sibling of the `idea` skill: no full methodology, no exhaustive primary-source verification, no business analysis — just enough structure to make the idea reviewable and promotable later. Use when the user runs /ideabox or wants to jot and lightly organize an idea to BUILD. NOT for research/analysis captures — those go to the separate top-level `src/content/inbox/` collection (`YYYY-MM-DD-{slug}.md`, no owning skill), so a bare "inbox에 추가해줘" / "조사해서 inbox에 넣어줘" is NOT this skill. 아이디어를 가볍게 정리·질문·레퍼런스 스캔해 idea 인박스에 남길 때 사용.
2026-07-30
Batch-polish agent-authored content collections (notes, inbox, wiki, idea) — NOT user-authored posts/read-and-write. Two body edits: (1) highlight the load-bearing spans with `==마커==`, sparingly; (2) align structure to each collection's own charter (hub 통합 + 하위 목차 재구성), deferring to the owning skill's model. A deterministic checker stamps a body-only `polishHash` and flags files whose body drifted since their last polish. Warning-only in pre-push. Runs as an independent pass (manual batch, or scoped to named files) — not coupled to /lint. Use before commit/push, or when the polish check flags drift.
2026-07-30
Research references for a topic — official/primary sources first — and persist them into the OKF-conformant wiki collection (src/content/wiki), categorized in a nested tree. Each doc gets a `type` frontmatter, a readable prose core, and primary/secondary reference links. Use when the user wants to gather the sources/evidence behind a topic, build up a reference category, or asks to "조사해서 위키에 정리" / "레퍼런스 카드 만들어줘". Distinct from the one-off deep-research report: /research produces a persistent, browsable, searchable library entry. 레퍼런스 조사·근거 자료 수집· 위키 카테고리 정리·공식 문서 우선 조사 요청에 사용.
2026-07-30
Write and revise CV/résumé project entries in a consistent Korean résumé voice — flowing narrative + separated impact, with an optional leading Why. Use when adding a project or experience to the CV, rewriting an entry, tightening wording, removing redundant dates, or converting segmented What/How/Impact bullets into narrative flow. CV 항목 작성·수정, 이력서 문체(개조식) 정리, 프로젝트 추가 시 사용.
2026-07-22
interpretive-generative-visuals
Interpret abstract words, compressed names, brand-like tokens, or concepts into mathematical generative visual grammars, confirm the interpretation direction with the user, then implement Three.js/WebGL or another renderer. Use when creating concept-driven visuals where the user expects semantic interpretation, recursive/metaphorical structure, formula-based shapes, 3D fields, or custom generated graph forms rather than literal text rendering or fixed chart/math-pattern presets.
2026-07-22
Creates, updates, reviews, and tests project agent skills under .agents/skills with .claude symlink compatibility. Use when the user asks to write or improve SKILL.md, create a reusable skill, validate skill structure, restructure skill-manager, or prepare workflow skills such as git-stash-pull. 스킬 생성, 수정, 리뷰, 검증, SKILL.md 작성 요청에 사용.
2026-07-22
