Applies a deliberate visual direction to an interface — minimalist editorial, industrial utilitarian, or high-polish commercial — each with its own type scale, palette behavior, surface treatment, and motion. Use this when a product needs a point of view rather than defaults, when choosing between visual directions, when an interface reads as generic, or when restyling something without changing its structure.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Three directions, each internally consistent. Pick one deliberately and apply it completely — half-applied styles read as mistakes, not hybrids.
| Direction | Reads as | Fits when |
|---|---|---|
| Minimalist editorial | Calm, content-first, confident | The content is the product: docs, writing tools, reading surfaces, analytics where data should dominate |
| Industrial utilitarian | Precise, dense, tool-like | The user is an operator, not a visitor: developer tooling, dashboards, internal systems |
| High-polish commercial | Expensive, considered, reassuring | Perceived quality drives the decision: marketing surfaces, onboarding, anything asking for trust or money |
If the brief does not imply one, ask. Defaulting is how products end up looking like their framework's starter template.
Near-monochrome with a single accent used sparingly. Hierarchy carried almost entirely by type size and generous whitespace. Flat surfaces — no shadows, no gradients; separation by space and hairline rules. Wide margins. Motion is almost absent: fades, no movement.
Fails when: applied to dense data, where the whitespace it needs is not available.
Rigid grid, visible structure. Extreme type contrast — small dense body against large stark headings. Monospace for anything numeric or identifying. Functional color only: state, not decoration. Square or near-square corners, borders rather than shadows. Motion is instant or absent.
Fails when: applied to consumer surfaces, where it reads as unfinished rather than deliberate.
Layered depth — considered shadows at two or three elevations, never more. Generous but not empty spacing. A type pairing with real personality in headings against a neutral body. Restrained gradients on key surfaces only. Motion is present and eased: things enter and settle rather than appear.
Fails when: applied to high-frequency tools, where the motion and padding become friction.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。