Use when the user wants to write or revise Japanese prose — technical docs, articles, READMEs, explanations — including the phrasings 書いて, 文章書いて, 執筆, 推敲,…
EnglishUse when the user wants help deciding how to build something, evaluating whether to keep/kill/pivot an approach, drafting an implementation plan, or…
EnglishUse when the user wants code reviewed or findings simplified — including the phrasings レビューして, コードレビュー, 整理して, simplify. Activate after implementation, when reviewing a git diff before opening a PR, or when restructuring messy findings — even when the user doesn't say 'review' explicitly.
EnglishUse when the user wants help deciding how to build something, evaluating whether to keep/kill/pivot an approach, or drafting an implementation plan —…
EnglishUse when the user wants to write or revise Japanese prose — technical docs, articles, READMEs, explanations — including the phrasings 書いて, 文章書いて, 執筆, 推敲,…
EnglishUse when the user wants to understand an unfamiliar code area, gather context before design, map impact scope, inspect related files, or clarify terminology/spec gaps before implementation — including phrasings 探索して, 全体像を掴んで, この辺り見て, 影響範囲を調べて, 関連ファイルを洗って, zoom-out, すり合わせ, 仕様を詰めたい. Activate before kouchiku when the request depends on unknown code structure, domain terminology, docs/ADR context, or ambiguous acceptance criteria.
EnglishUse when the user wants to submit a pull request or draft a PR body — including the phrasings PR出す, PR提出, PR ready, PR open する, PR文書いて, PR description, submit. Handles PR body drafting and the full submission flow: remote state check, submodule-first ordering, parent commit, cwd-aware gh pr create. Activates after implementation is complete and ready to ship, even when the user just says 提出する or 出す without explicit PR wording.
EnglishUse when the user wants to execute an already-approved plan or diagnose a failure — including phrasings 進めて, 計画実行, 着手, 実装開始, 実装して, エラー, 動かない, 落ちる, クラッシュ, 前は動いてた, 原因が分からない. Activate when the user just approved a plan and wants it built, or reports a bug/test failure whose root cause is unknown.
Japanese
AGENT SKILLS ATLASExplore the listed skills and choose the workflows that fit your task.
Claude Code
Codex
Cursor
GitHub Copilot
Gemini CLISupported by the Atlas install prompt. Skill-specific requirements vary.
Pack stats
What’s included
Kaku
Use when the user wants to write or revise Japanese prose — technical docs, articles, READMEs, explanations — including the phrasings 書いて, 文章書いて, 執筆, 推敲, リライト
Kouchiku
Use when the user wants help deciding how to build something, evaluating whether to keep/kill/pivot an approach, drafting an implementation plan, or executing
Sadoku
Use when the user wants code reviewed or findings simplified — including the phrasings レビューして, コードレビュー, 整理して, simplify. Activate after implementation, when reviewing a git diff before opening a PR, or when restructuring messy findings — even when the user doesn't say 'review' explicitly. レビュー系の語 (レビューして / コードレビュー) は通常レビュー、整理系の語 (整理して / simplify) のみ simplify findings を起動する。
Sekkei
Use when the user wants help deciding how to build something, evaluating whether to keep/kill/pivot an approach, or drafting an implementation plan — including
Shippitsu
Use when the user wants to write or revise Japanese prose — technical docs, articles, READMEs, explanations — including the phrasings 書いて, 文章書いて, 執筆, 推敲, リライト
Tansaku
Use when the user wants to understand an unfamiliar code area, gather context before design, map impact scope, inspect related files, or clarify terminology/spec gaps before implementation — including phrasings 探索して, 全体像を掴んで, この辺り見て, 影響範囲を調べて, 関連ファイルを洗って, zoom-out, すり合わせ, 仕様を詰めたい. Activate before kouchiku when the request depends on unknown code structure, domain terminology, docs/ADR context, or ambiguous acceptance criteria.
Teishutsu
Use when the user wants to submit a pull request or draft a PR body — including the phrasings PR出す, PR提出, PR ready, PR open する, PR文書いて, PR description, submit. Handles PR body drafting and the full submission flow: remote state check, submodule-first ordering, parent commit, cwd-aware gh pr create. Activates after implementation is complete and ready to ship, even when the user just says 提出する or 出す without explicit PR wording.
Jikkou
Use when the user wants to execute an already-approved plan or diagnose a failure — including phrasings 進めて, 計画実行, 着手, 実装開始, 実装して, エラー, 動かない, 落ちる, クラッシュ, 前は動いてた, 原因が分からない. Activate when the user just approved a plan and wants it built, or reports a bug/test failure whose root cause is unknown. 設計判断そのものは sekkei に戻す。
Quick start
- Choose your skills. Select individual skills above, or choose the entire pack.
- Copy the install prompt. Use Copy install prompt above the list.
- Send it to your agent. Paste into your coding agent’s chat. Your agent reviews the source and guides the setup.
Try it with your agent
After installation, start with a request like:
Use the Kaku skill to help with my task.
Ask me for the context you need before getting started.Requirements & license
- A coding agent that can access your project files and install skills.
- Your agent checks each skill’s instructions, dependencies, and permissions during setup.
- Reported license for the skills shown: MIT. The author’s terms apply.