Skill ディレクトリ
すべての推奨は、リポジトリ、監査、インストール経路に明確につながっています。
ATLAS: a senior-engineer layer for Claude Code. Explore with wireframes & prototypes, clarify the essentials, capture it in HTML spec doc then let Claude Code's native plan/goal/workflow loop build. Fewer tokens, less ceremony, faster to what people pictured. KISS/YAGNI/DRY, context decides. No overengineering. Clean architecture that works.
AI agents now operate with authority. Authority without discipline is how complex systems fail. Nuclear’s control loop, ported to AI-assisted software engineering.
A zero ceremony ORM for Java
Think and deliver like a management consultant from McKinsey, BCG, or Bain. Use when the user wants to: (1) Structure a business problem with hypothesis-driven decomposition, (2) Run strategy analysis with professional frameworks: market sizing, competitive landscape, financial modeling, SWOT, Porter's, (3) Build MBB-quality deliverables: executive summaries, strategy deck outlines, decision memos, (4) Apply firm-specific methodology: McKinsey verdict-first, BCG framework-first, or Bain decision-first, (5) Package analysis for non-consulting audiences: investor pitches, board presentations, conference talks. Produces structured analysis and deliverable CONTENT. For visual production, hand off to a delivery skill for slides, documents, or spreadsheets.
Shared clean-code / DRY / KISS / YAGNI standards and stack-specific smells for the React 19 + TypeScript + Rust (Tauri 2) monorepo. Library consumed by the code-quality-reviewer and code-quality-author agents.
Everyday Writer master dispatcher for an AI writing companion. Use when the user invokes $ew, /ew, or asks for help writing anything for publication: newsletters, LinkedIn posts, tweets, Substack Notes, landing pages, sales copy, fiction scenes, screenplays, outlines, or a rewrite of existing text. Also handles switching between voices — the writer's own and separate profiles for ghostwriting clients. Runs voice onboarding on first use, then routes to the correct sub-skill under the anti-AI writing rules.
Graduate a project's in-repo backlog (roadmap phases, sprint deliverables, ADRs) onto a forge issue tracker at a thin-hybrid default, once the backlog outgrows a single contributor. Use when a team needs to see and claim work that currently lives only in docs/roadmap and docs/sprints, when a repo has a mature in-repo roadmap but an empty tracker, when open-sourcing a project, or when deciding what work should stay in-repo versus live on a GitHub, GitLab, Codeberg/Forgejo, or self-hosted internal tracker.
Systematically find root causes and fix bugs. Use when debugging errors, investigating test failures, reproducing bugs from issue trackers (GitHub, Linear, Jira), or when stuck on a problem after failed fix attempts. Also use when the user says ''debug this'', ''why is this failing'', ''fix this bug'', ''trace this error'', or pastes stack traces, error messages, or issue references.
Skill ディレクトリ
すべての推奨は、リポジトリ、監査、インストール経路に明確につながっています。
ATLAS: a senior-engineer layer for Claude Code. Explore with wireframes & prototypes, clarify the essentials, capture it in HTML spec doc then let Claude Code's native plan/goal/workflow loop build. Fewer tokens, less ceremony, faster to what people pictured. KISS/YAGNI/DRY, context decides. No overengineering. Clean architecture that works.
AI agents now operate with authority. Authority without discipline is how complex systems fail. Nuclear’s control loop, ported to AI-assisted software engineering.
A zero ceremony ORM for Java
Think and deliver like a management consultant from McKinsey, BCG, or Bain. Use when the user wants to: (1) Structure a business problem with hypothesis-driven decomposition, (2) Run strategy analysis with professional frameworks: market sizing, competitive landscape, financial modeling, SWOT, Porter's, (3) Build MBB-quality deliverables: executive summaries, strategy deck outlines, decision memos, (4) Apply firm-specific methodology: McKinsey verdict-first, BCG framework-first, or Bain decision-first, (5) Package analysis for non-consulting audiences: investor pitches, board presentations, conference talks. Produces structured analysis and deliverable CONTENT. For visual production, hand off to a delivery skill for slides, documents, or spreadsheets.
Shared clean-code / DRY / KISS / YAGNI standards and stack-specific smells for the React 19 + TypeScript + Rust (Tauri 2) monorepo. Library consumed by the code-quality-reviewer and code-quality-author agents.
Everyday Writer master dispatcher for an AI writing companion. Use when the user invokes $ew, /ew, or asks for help writing anything for publication: newsletters, LinkedIn posts, tweets, Substack Notes, landing pages, sales copy, fiction scenes, screenplays, outlines, or a rewrite of existing text. Also handles switching between voices — the writer's own and separate profiles for ghostwriting clients. Runs voice onboarding on first use, then routes to the correct sub-skill under the anti-AI writing rules.
Graduate a project's in-repo backlog (roadmap phases, sprint deliverables, ADRs) onto a forge issue tracker at a thin-hybrid default, once the backlog outgrows a single contributor. Use when a team needs to see and claim work that currently lives only in docs/roadmap and docs/sprints, when a repo has a mature in-repo roadmap but an empty tracker, when open-sourcing a project, or when deciding what work should stay in-repo versus live on a GitHub, GitLab, Codeberg/Forgejo, or self-hosted internal tracker.
Systematically find root causes and fix bugs. Use when debugging errors, investigating test failures, reproducing bugs from issue trackers (GitHub, Linear, Jira), or when stuck on a problem after failed fix attempts. Also use when the user says ''debug this'', ''why is this failing'', ''fix this bug'', ''trace this error'', or pastes stack traces, error messages, or issue references.
Skill ディレクトリ
すべての推奨は、リポジトリ、監査、インストール経路に明確につながっています。
ATLAS: a senior-engineer layer for Claude Code. Explore with wireframes & prototypes, clarify the essentials, capture it in HTML spec doc then let Claude Code's native plan/goal/workflow loop build. Fewer tokens, less ceremony, faster to what people pictured. KISS/YAGNI/DRY, context decides. No overengineering. Clean architecture that works.
AI agents now operate with authority. Authority without discipline is how complex systems fail. Nuclear’s control loop, ported to AI-assisted software engineering.
A zero ceremony ORM for Java
Think and deliver like a management consultant from McKinsey, BCG, or Bain. Use when the user wants to: (1) Structure a business problem with hypothesis-driven decomposition, (2) Run strategy analysis with professional frameworks: market sizing, competitive landscape, financial modeling, SWOT, Porter's, (3) Build MBB-quality deliverables: executive summaries, strategy deck outlines, decision memos, (4) Apply firm-specific methodology: McKinsey verdict-first, BCG framework-first, or Bain decision-first, (5) Package analysis for non-consulting audiences: investor pitches, board presentations, conference talks. Produces structured analysis and deliverable CONTENT. For visual production, hand off to a delivery skill for slides, documents, or spreadsheets.
Shared clean-code / DRY / KISS / YAGNI standards and stack-specific smells for the React 19 + TypeScript + Rust (Tauri 2) monorepo. Library consumed by the code-quality-reviewer and code-quality-author agents.
Everyday Writer master dispatcher for an AI writing companion. Use when the user invokes $ew, /ew, or asks for help writing anything for publication: newsletters, LinkedIn posts, tweets, Substack Notes, landing pages, sales copy, fiction scenes, screenplays, outlines, or a rewrite of existing text. Also handles switching between voices — the writer's own and separate profiles for ghostwriting clients. Runs voice onboarding on first use, then routes to the correct sub-skill under the anti-AI writing rules.
Graduate a project's in-repo backlog (roadmap phases, sprint deliverables, ADRs) onto a forge issue tracker at a thin-hybrid default, once the backlog outgrows a single contributor. Use when a team needs to see and claim work that currently lives only in docs/roadmap and docs/sprints, when a repo has a mature in-repo roadmap but an empty tracker, when open-sourcing a project, or when deciding what work should stay in-repo versus live on a GitHub, GitLab, Codeberg/Forgejo, or self-hosted internal tracker.
Systematically find root causes and fix bugs. Use when debugging errors, investigating test failures, reproducing bugs from issue trackers (GitHub, Linear, Jira), or when stuck on a problem after failed fix attempts. Also use when the user says ''debug this'', ''why is this failing'', ''fix this bug'', ''trace this error'', or pastes stack traces, error messages, or issue references.
Skill ディレクトリ
すべての推奨は、リポジトリ、監査、インストール経路に明確につながっています。
ATLAS: a senior-engineer layer for Claude Code. Explore with wireframes & prototypes, clarify the essentials, capture it in HTML spec doc then let Claude Code's native plan/goal/workflow loop build. Fewer tokens, less ceremony, faster to what people pictured. KISS/YAGNI/DRY, context decides. No overengineering. Clean architecture that works.
AI agents now operate with authority. Authority without discipline is how complex systems fail. Nuclear’s control loop, ported to AI-assisted software engineering.
A zero ceremony ORM for Java
Think and deliver like a management consultant from McKinsey, BCG, or Bain. Use when the user wants to: (1) Structure a business problem with hypothesis-driven decomposition, (2) Run strategy analysis with professional frameworks: market sizing, competitive landscape, financial modeling, SWOT, Porter's, (3) Build MBB-quality deliverables: executive summaries, strategy deck outlines, decision memos, (4) Apply firm-specific methodology: McKinsey verdict-first, BCG framework-first, or Bain decision-first, (5) Package analysis for non-consulting audiences: investor pitches, board presentations, conference talks. Produces structured analysis and deliverable CONTENT. For visual production, hand off to a delivery skill for slides, documents, or spreadsheets.
Shared clean-code / DRY / KISS / YAGNI standards and stack-specific smells for the React 19 + TypeScript + Rust (Tauri 2) monorepo. Library consumed by the code-quality-reviewer and code-quality-author agents.
Everyday Writer master dispatcher for an AI writing companion. Use when the user invokes $ew, /ew, or asks for help writing anything for publication: newsletters, LinkedIn posts, tweets, Substack Notes, landing pages, sales copy, fiction scenes, screenplays, outlines, or a rewrite of existing text. Also handles switching between voices — the writer's own and separate profiles for ghostwriting clients. Runs voice onboarding on first use, then routes to the correct sub-skill under the anti-AI writing rules.
Graduate a project's in-repo backlog (roadmap phases, sprint deliverables, ADRs) onto a forge issue tracker at a thin-hybrid default, once the backlog outgrows a single contributor. Use when a team needs to see and claim work that currently lives only in docs/roadmap and docs/sprints, when a repo has a mature in-repo roadmap but an empty tracker, when open-sourcing a project, or when deciding what work should stay in-repo versus live on a GitHub, GitLab, Codeberg/Forgejo, or self-hosted internal tracker.
Systematically find root causes and fix bugs. Use when debugging errors, investigating test failures, reproducing bugs from issue trackers (GitHub, Linear, Jira), or when stuck on a problem after failed fix attempts. Also use when the user says ''debug this'', ''why is this failing'', ''fix this bug'', ''trace this error'', or pastes stack traces, error messages, or issue references.