inakaegg
UserCodexとClaude Codeで共用するAIコーディングエージェント運用キット：作業規約（AGENTS.md）、Skill、テンプレート、検査スクリプト、Git hooks（秘密情報走査・日本語文書lint）
Categories
Indexed Skills (12)
architecture-diagram
Use when a README / SPEC / design doc needs an architecture or flow diagram: system / service / cloud architecture with official icons (AWS / GCP / Azure / k8s / on-prem / SaaS / languages / generic), deploy paths, request flows, or when an existing diagram is unreadable (icons too big, text too small, labels overlapping, too small on GitHub). Japanese cues: 「構成図」「アーキテクチャ図」「図を入れて」「図が読みづらい」 「アイコンが大きい」「文字が小さい」「図がかぶる」「Mermaidで」「diagramsで」.
debug-loop
Use when a bug's cause is not obvious or a first fix did not stick: regressions, flaky failures, async・state・distributed issues, same-shape defect clusters. Japanese cues: 「原因不明のbug」「デグレ」「リグレッション」「flaky」「分散」「1回で直らない」.
evaluation-loop
Use when adoption is decided by measurement: heuristics / ranking / OCR・ASR・translation・generation quality / rival implementations compared on the same data. Japanese cues: 「同一データで比較」「実測で採否」「品質を評価」.
independent-review
Use for fresh-context review of non-trivial changes before a PR. Targets: user-visible behavior / public API / persistence / concurrency・async / security / billing / deployment / migration. Japanese cues: 「独立レビュー」「別contextでレビュー」「仕様レビュー」「実装計画レビュー」「実装レビュー」（旧称: gateレビュー・計画レビュー）.
pr-review-loop
Use on an explicitly approved PR to drive convergence on the latest head: reviewer and bot findings / CI / fixes / re-verification / re-review. Japanese cues: 「PRレビュー対応」「botの指摘を処理」「CIを通して再review」.
ui-verification
Use when changing or auditing visible UI in web・native apps: layout / components / style / interaction / navigation / loading・error・empty states. Japanese cues: 「UI確認」「実画面で検証」「画面崩れ」.
ci-fix
Use when a GitHub Actions run or PR check is failing — the user pastes a failing Actions run / PR URL, or says "CI失敗", "CIがこけてる", "CI直して", "デプロイ失敗", "why did CI fail".
dep-upgrade-safe
Use when upgrading specific npm packages — the user names a package to bump, pastes upgrade-interactive / npm outdated rows, or asks "breaking changeある？", "安全にupdateできる？", "changelog確認して". Especially for major-version bumps.
docs-maintenance
Use when README / SPEC / ROADMAP / ADR / public docs / internal _ai docs need creating or updating. Also for splitting / merging / renaming / deleting them, and for syncing docs with the implementation. Japanese cues: 「README更新」「docs整理」「仕様と実装の同期」.
large-work
Use for work that needs a staged pilot and stop conditions. Signals: over 30 minutes / over 100 items / heavy token・external-fee・GPU・storage use / large migrations・annotation・exhaustive surveys. Japanese cues: 「大量」「網羅的に」「全件処理」.
semantic-generation
Use before design docs / design from requirements / survey reports / cause isolation / countermeasures / naming decisions / reasoning-order summaries. Naming includes state・condition・type・method names. First build a correspondence table as an independent deliverable; fix referents and roles before words. Not for: quoting the user's text / mechanical edits / reusing existing names / boilerplate / chit-chat / short texts of established terms. Japanese cues: 「対応表を先に」「命名の前に」「設計資料の下準備」.
ui-quality
End-to-end visible-UI work for web and native apps: design → implementation → real-screen verification → audit → re-fix. Use for new screens・components / responsive・window layouts / themes / forms / dialogs / navigation, and for fixing UI looks・usability・consistency. Japanese cues: 「UIを作って」「画面を改善」「見た目を直して」.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.