.dotfiles

Group code by business domain, never by technical kind. Use when refactoring or restructuring a codebase, creating new folders/modules, deciding where a new file goes, or reviewing a structure proposal. Triggers on module layout, folder structure, "where should this live", or plans that add folders like components/, store/, hooks/, services/.

Write a deep-explanation document (concept) — the reader wants "help me understand why/how it works". Invoked from the docs-write pipeline; also usable directly when the task is unambiguously conceptual explanation.

Write a problem-solving document (how-to / guide) — the reader has a specific task and wants to be unblocked. Invoked from the docs-write pipeline; also usable directly when the task is unambiguously a how-to.

Write a reference document — the reader wants to look up an exact fact (API surface, config options, CLI flags). Invoked from the docs-write pipeline; also usable directly when the task is unambiguously reference material.

Entry point for writing any outside-facing document — READMEs, guides, tutorials, API references, design/status docs, issue bodies, PR bodies, release notes. Use BEFORE drafting anything a reader other than the author will see. Classifies the document's purpose, routes to the matching docs-write-* purpose skill, and mandates a prose-editor review pass on every draft. Also holds the shared core rules: information architecture, sentence craft, Korean prose, labels & jargon.

Write a status/design document — living issue bodies, ADRs, design docs, PR bodies. The reader wants "what's the state, what was decided, and why". Invoked from the docs-write pipeline; also usable directly for issue/ADR/PR-body writing.

Write a learning document (tutorial) — the reader wants "teach me to do this, step by step". Invoked from the docs-write pipeline; also usable directly when the task is unambiguously a tutorial.

Disciplined GitHub workflow via the gh CLI. Lean router — per-command guides in guides/ (pr.md — PR template detection and filling, Korean 개조식 body, issue-closing keywords; issue.md — issue scoping and writing) are force-injected per session by the gh-guard PreToolUse hook on mutating gh pr / gh issue commands. Use when creating or updating pull requests, searching or triaging issues, or working with gh.

Disciplined git workflow — inspect before acting, Conventional-Commits messages, atomic commits, deliberate staging, commit and push as separate steps, always fetch and check remote branches before integrating/pushing, and fail-closed guardrails on destructive ops. Use when staging, committing, branching, pushing, pulling, rebasing, or rewriting history.

Use Slopless to review English Markdown for deterministic AI and human slop signals, including vague phrasing, formulaic prose, weak rhythm, filler, cliches, and readability issues.