lacolaco

エージェントの文脈に影響する永続層 (メモリ・CLAUDE.md・規約文書・指針文書・スキル文書等の日本語文章) の日本語品質を、`textlint-ja` と独自規則で再現可能に点検する。英単語混入等の文章規律違反を検出。ユーザーが「日本語品質チェック」「textlint かけて」「英語混入チェック」「メモリ点検」「`memory sanitize`」等を指示したら起動する。

Write or update your handover document so the next holder of this job seat can take over your responsibilities. The seat you hold is identified by (project, role) in the document's frontmatter; the document is a handoff report, not a personal diary. Use this skill whenever the user mentions 'handover', 'hand over', 'pass it on', or '/handover'. NEVER invoke this skill proactively, autonomously, or as part of completing a task — finishing work, wrapping up, ending a session, or saving progress are NOT triggers for this skill unless the user explicitly asks for a handover.

Take over a job seat left by a previous holder — adopt responsibility for the work going forward, audit the predecessor's claims before relying on them, and continue under your own name. Every referenced artifact becomes a mandatory read task, drained before any work starts. The predecessor's report is yours to audit, not yours to inherit unexamined. Use this skill whenever the user mentions 'takeover', 'take over', 'pick up where we left off', or '/takeover'. NEVER invoke this skill proactively or autonomously — resuming or continuing work is NOT a trigger for this skill unless the user explicitly asks for a takeover.

Retrospective grounded in the garbage-in-garbage-out principle: traces problems from Output back to their upstream origin across six stages, then fixes at the stage where the cause lives — knowledge deficiencies get knowledge fixes, not downstream rule patches. Implements fixes in the current session. Use after finishing a task, before creating a PR, or whenever the user says 'retrospective', 'wrap up learnings', or similar.

Edited a project's manifest, lockfile, or config? Added or deleted a whole project? Then its `.knowledge/` wiki page is now stale — use this skill to ingest (regenerate the page) or deingest (remove it). Assume the user won't mention the wiki or KB; trigger from the file touched or the action alone. Fire when: - a project's stack/dependency/build/deploy/structure-defining file changes — package.json, any lockfile (pnpm-lock, uv.lock, gleam.lock), pyproject.toml, gleam.toml, tsup.config, angular.json, wrangler.toml, Dockerfile/Cloud Run, pnpm-workspace.yaml, new workspace packages — or its CLAUDE.md; - a project is cloned, forked, or placed under a KB anchor (`~/works/`, `~/.claude/`), or a project directory is removed from one; - **AI-generated intermediate-artifact files appear, change, or are discovered** anywhere under a KB-covered repo — design docs (`docs/designs/*.md`), review records (`docs/reviews/*.md`), plans (`docs/plans/*.md`), acceptance-test records, retrospectives, conversation logs — **regard

Lint the knowledge base at `~/.knowledge/` (LLM Wiki). Deterministic checks are delegated to a script; contradictions, broken links, and staleness are reported as proposals only (no auto-fix). Use for KB health checks, contradiction detection, right after a batch ingest, or before relying on the KB as evidence.

Use this skill whenever the user is trying to recall, verify, enumerate, or reconcile facts about their own collection of projects — especially "which of my projects do X" questions. X can be a library, package, framework, version, service, cloud platform, deploy target, architectural pattern, or "what even is this project." Trigger on memory-checking and inventory intent: enumerating consumers/users of something, confirming a remembered list ("…だっけ", "…で正しい？", "…以外もあったよな", "…の気がする"), mapping relationships or dependency chains between projects, or sorting projects by which tech/version they use. Trigger even when phrased casually, even when one specific project or package is named, and even though the user never mentions a KB, wiki, or `.knowledge/`. The skill answers from the knowledge base at `~/.knowledge/` with citations. Do NOT trigger for: writing/debugging code inside a single named project, learning a technology in general, or adding/removing/maintaining KB pages.

Sync stale pages in the knowledge base at `~/.knowledge/` (LLM Wiki). Re-ingests wiki pages that drifted from their sources to resolve drift. Use for "refresh the KB", "update a stale page", or "sync".

WHEN: the user wants a critical review by the `code-critic` agent. The skill gathers the agent's required Invocation Contract inputs (review target, intent, layer), dispatches the agent via the Agent tool, and drives the **address-then-resubmit** loop until the agent returns an `Approved` verdict or the user explicitly defers what is left.

WHEN: PROACTIVELY when the change introduces or modifies design (new abstraction, new boundary, new module, contract change, security-sensitive interaction, refactor that reshapes responsibility). INPUT: File paths/directory + intent of the change. OUTPUT: Design-level critical issues — contract gaps, architectural misalignment, over-/under-engineered abstractions, security-designed-in failures, systemic problems hidden behind local fixes — with root causes and structural fixes. Implementation defects (logic bugs, races, resource leaks) are out of scope; route those to critic-implementation-review.

WHEN: PROACTIVELY when reviewing code that implements an already-settled design (bug fixes, feature implementation against an agreed shape, optimizations inside an existing module). INPUT: File paths/directory + the design contract being implemented. OUTPUT: Implementation-level critical defects — logic errors, race conditions, resource leaks, concrete security bugs, error-handling gaps, performance problems on real-sized inputs, contract drift between signature and behavior — with concrete fixes. Design-level concerns (abstraction quality, contract shape, architectural fit) are out of scope; route those to critic-design-review.

PRのライフサイクル全体をゲート付きで管理する。PR作成、レビュー対応、マージ、ポストマージまでの一連のワークフローを強制する。PRを作りたい、レビュー対応したい、マージしたい、といった場面で使用する。

OrbStack がホストの Docker runtime として常に利用可能である前提で、Docker Compose 開発環境にアクセスする方法。OrbStack 特有の自動 DNS・自動 port forwarding を活用し、dnsmasq や ports: 公開の手間を省く。Docker Compose 上の Rails/Node 等のサーバーにローカルからアクセスする場面、マルチテナントアプリのサブドメインルーティングを検証する場面で使用する。

Five Whys分析で問題の根本原因を特定し、本質的な解決策を導出する。問題の原因分析、根本原因の特定、なぜなぜ分析、トラブルシューティング、障害分析、インシデント振り返り、ポストモーテムなど、「なぜこの問題が起きたのか」を深掘りして解決策を考えたい場面で使用する。ユーザーが問題の原因について悩んでいたり、表面的な対処ではなく根本的な解決を求めている場合にも発動する。

WHEN: PROACTIVELY after completing a substantial task (PR merge, feature implementation, bug fix, investigation)—invoke WITHOUT waiting for user request. SKIP for trivial/instant tasks (typo fix, single-line change, quick question answer, config tweak). Also invokable manually via /slack-notify. Sends a completion notification to Slack via Incoming Webhook. Does nothing if CLAUDE_SLACK_NOTIFY_WEBHOOK_URL is not set.

Use when addressing PR review comments - checking pending reviews, fetching unresolved threads, evaluating each comment, and deciding to fix or explain non-problematic

ダメージ計算。攻撃側・防御側・技名を指定し、特性・持ち物・天候込みのダメージ乱数表を出力する。ダメージ計算・ダメ計・何発で落ちる等の質問時に使用。

ナッシュ均衡ソルバー。零和対戦 (ポケモン選出、構築マッチアップ、じゃんけん型メタ) の最適混合戦略、選出最適化 (pkdx select)、メタ乖離分析 (pkdx meta-divergence) を提供。「最適選出」「選出分布」「構築メタ」「対面ジャンケン」「使用率 vs 最適」等の質問時に使用。

ポケモン育成シミュレーション。性格・特性・持ち物・技・努力値を対話的に設定し、Lv50実数値を算出する。育成したい・実数値計算・努力値配分等の質問時に使用。

対戦用ポケモン構築支援（シングル/ダブル対応）。軸ポケモンからタイプ補完・メタ分析・選出パターンまでガイドする。構築したい・パーティを組みたい・チーム作成時に使用。

対戦中の高速応答モード。calc skillを事前ロードし、ダメ計とメモのラベル付き入力のみを最短で処理する。対戦中・バトル中・実戦中・対戦が始まる等の発話時に使用。

Use when editing existing slides in deck.md — rewriting body text, swapping layout, toggling freeze/skip/ignore, fixing citations, reordering. The slide's `key` is preserved through every edit. Anything that creates new content (a new deck from a template, or a new slide that needs a fresh key) goes through `deck-new`.

Use when creating anything new for deck.md — either a brand-new deck from a Google Slides template (0→1) or a new slide added to an existing deck (n→n+1, with a freshly minted 4-hex `key`). Trigger when the user provides a Google Slides URL and asks to make a deck, or says "add a slide after X", "insert a quote slide here", "new section header before Appendix". Edits to existing slides (body rewrite, layout swap, freeze/skip toggle) go through `deck-edit`.

@lacolaco/notion-syncのメジャーバージョンアップを実行する。notion-syncのアップグレード、マイグレーション、バージョンアップと言われた時に使用する。新バージョンが未公開の場合はポーリングで待機する。

GitHub Actionsのデプロイ実行履歴を分析し、デプロイ時間のトレンド把握と異常検知を行う。「デプロイ分析」「デプロイパフォーマンス」と言われた時に使用。

@lacolaco/notion-syncのメジャーバージョンアップを実行する。notion-syncのアップグレード、マイグレーション、バージョンアップと言われた時に使用する。新バージョンが未公開の場合はポーリングで待機する。

Reference data for Angular major-version updates: the breaking changes and migration items for every major-to-major step from v6 to v22, generated from the official Angular Update Guide. Use when raising an Angular major version, when `ng update` crosses a major boundary, or when investigating what breaks between two Angular majors. This is data, not a procedure. It supplies *what* changes between two Angular majors, not *how* to carry out the update — pair it with whatever update procedure you already follow. A question that is only about the procedure does not need this skill. Do NOT use for non-Angular dependency updates, for minor/patch bumps, or for source edits that don't change the Angular version. Unofficial. Not affiliated with or endorsed by Google or the Angular team.

yakkun-map.json内のnullエントリにyakkun URLを補完する。generate-pokemon-data.tsがyakkun未対応を警告した時、yakkun-mapのnull補完を依頼された時、新ポケモンデータ追加後のURL補完時に使用する。「yakkun」「URL補完」「マッピング更新」といったキーワードでも発動する。