Designs system structure and makes architectural decisions defensible — boundaries, coupling, trade-offs, and recording why. Use this to design a new system or major component, choose between architectural options, review an existing design, decide where a boundary belongs, or document an architectural decision so it survives the people who made it.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Architecture is the set of decisions that are expensive to reverse. Everything cheap to change later is design, and does not need this level of ceremony.
Architecture is driven by quality attributes, not by features. Establish the ones that actually bind before drawing anything: expected load and its shape, latency the user notices, availability the business will fund, data residency and retention obligations, the rate of change the team needs to sustain, and the size and skills of the team who will operate it.
Vague attributes produce vague architecture. "Scalable" is not a requirement; "20,000 concurrent sessions with p99 under 300ms" is a constraint that eliminates options.
Draw boundaries where change is independent and where data has a single owner. A boundary in the right place absorbs change; a boundary in the wrong place turns every feature into a negotiation across three teams.
The reliable test: if a routine change requires coordinated deployment across two components, the boundary is wrong regardless of how clean the diagram looks.
Prefer coarse boundaries until you have evidence for finer ones. Distributed systems convert simple in-process failures into network, partial-failure and consistency problems — a cost worth paying for independent scaling or independent deployment, and not worth paying for tidiness.
Every architecture sacrifices something. The failure is not choosing badly; it is choosing without naming what was given up, so nobody later understands why the constraint exists.
Present options with their costs: what each makes easy, what each makes hard, what it costs to operate, and what it would take to reverse. Two credible options and an honest comparison beat one recommendation.
Write down the decision, the context at the time, the options considered, and the consequences accepted. Architecture rots because the reasoning evaporates while the structure remains, and the next team reads a constraint as an accident.
Keep records short and immutable — supersede rather than edit, so the history of thinking survives.
references/sources.md in this skill lists the outside authorities that settle the questions
here — what each one is authoritative for, and what you may do with it. Check them before
answering on anything they cover, and cite what you used. Most are free to read and not free
to reproduce; the use note on each is binding.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.
日本語の概要は準備中です。原文の説明を表示しています。
Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.
日本語の概要は準備中です。原文の説明を表示しています。
Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account. Use this to design or fix signup and onboarding, diagnose why signups do not convert to active use, reduce time-to-value, or decide what a new user must accomplish first.
日本語の概要は準備中です。原文の説明を表示しています。
Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.
日本語の概要は準備中です。原文の説明を表示しています。
Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.
日本語の概要は準備中です。原文の説明を表示しています。
Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.
日本語の概要は準備中です。原文の説明を表示しています。