デザインのスキル

Use when revising the prose, abstract, and introduction of an American Economic Journal: Applied Economics (AEJ: Applied) manuscript so the design and headline estimate land in the first paragraph in AEA house style. Polishes exposition; it does not change the result (aeja-identification / aeja-robustness) or the exhibits.

日本語の概要は準備中です。原文の説明を表示しています。

Use when an AEJ: Economic Policy manuscript's headline policy estimate needs to be shown stable and credible against specification, sample, inference, and identification threats. Organizes the robustness program by threat-to-the-policy-conclusion; it does not design the primary identification or write exhibits.

日本語の概要は準備中です。原文の説明を表示しています。

Use when an American Economic Journal: Applied Economics (AEJ: Applied) manuscript needs a model to interpret, discipline, or structure its empirical estimates — not to lead the paper. Calibrates how much theory belongs in an empirical-first journal and where it goes; it does not design the identification (aeja-identification) or build a standalone structural estimation.

日本語の概要は準備中です。原文の説明を表示しています。

Use when judging whether a research idea fits Administrative Science Quarterly (ASQ) and has the *surprising* theoretical insight ASQ demands. Sharpens the puzzle and the contribution claim; it does not design the study or write theory sections.

日本語の概要は準備中です。原文の説明を表示しています。

Use when an AEJ: Economic Policy decision letter (R&R or reject-and-resubmit) has arrived and a response-letter strategy and revision plan are needed. Structures the response to referees and editor with policy-relevance front and center; it does not run new estimation or redesign identification from scratch.

日本語の概要は準備中です。原文の説明を表示しています。

Use when deciding whether a project fits AEJ: Economic Policy rather than J. Public Economics, AEJ: Applied, or AER, and when sharpening the policy question and its welfare stake for an AEJ: Economic Policy manuscript. Frames fit and the policy-question-first contribution; it does not design the identification or run estimation.

日本語の概要は準備中です。原文の説明を表示しています。

Use when drafting or revising the prose of an AEJ: Economic Policy manuscript — especially the abstract and introduction — to translate causal estimates into a clear policy takeaway without overclaiming. Shapes the policy-first narrative and house style; it does not design identification or build the welfare model.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the theoretical puzzle is the bottleneck for an Academy of Management Review (AMR) manuscript — deciding whether an idea is theory-worthy and AMR-fit before any theorizing begins. Frames the puzzle; it does NOT build constructs (that is amr-theory-development) or design any empirical study (AMR has none).

日本語の概要は準備中です。原文の説明を表示しています。

Use when responding to an Academy of Management Annals (Annals) proposal decision or full-review referee letter — framework/attitude asks, coverage gaps, balance complaints, and accessibility. Drafts the response letter and revision plan; it does not run the portal preflight (amann-submission) or redesign the framework from scratch (amann-organizing-framework).

日本語の概要は準備中です。原文の説明を表示しています。

Use when revising an Academy of Management Annals (Annals) review for the house voice — authoritative, integrative, agenda-setting "reviews with an attitude," with a strong problem-first opening and a contribution-stating abstract. Polishes prose and structure; it does not design the framework (amann-organizing-framework) or run the submission preflight (amann-submission).

日本語の概要は準備中です。原文の説明を表示しています。

Prove a UI that updates before the server answers puts things back and says so when the request fails, and keeps the change when it succeeds. Use when a like, toggle, rename, reorder, delete or add-to-cart updates instantly, when an optimistic update was added or changed, or when a user reports a change that "saved" but was gone after a reload.

日本語の概要は準備中です。原文の説明を表示しています。

Pick up the bugs a human flagged by pointing at them in the running app, each arriving with the element, the note they typed, and the source file and line. Use when the user says they marked or flagged something, when starting a session on an app someone has been clicking through, when a designer or PM has left feedback in the UI, or when the user describes a problem as "that button there" without saying which file.

日本語の概要は準備中です。原文の説明を表示しています。

Prove sign-in lands the user where they should be, sign-out really ends the session so a protected page sends them back to sign in, and an expired session asks to sign in again instead of breaking. Use when auth, a login form, a logout button, route guards or token refresh were added or changed, or when a user reports being logged out, or not logged out, unexpectedly.

日本語の概要は準備中です。原文の説明を表示しています。

Check that a change to a web app actually works in the running app before calling it done. Drives the real page and returns a pass/fail verdict with the request that fired, the state that moved, and the file:line to fix. Use after editing a component, a form, a route, or an API call; when you have said "fixed" but have not opened the app; when the user asks "does it actually work?"; or when a change looks right on screen and you cannot prove it.

日本語の概要は準備中です。原文の説明を表示しています。

Check that the UI you actually rendered uses the design system, by reading computed styles in the running app against the project's design tokens. Catches hardcoded hex colors, off-palette backgrounds, invisible or unusable controls, and animations that never ran. Use after building or restyling a component, when a design review is wanted, when a UI looks slightly off but nobody can say why, or when a design system exists and nothing checks whether the code follows it.

日本語の概要は準備中です。原文の説明を表示しています。

Find out why something in a running web app does not work, when the console is empty and the code looks correct. Reads the click, the request, the store and the console together and returns the file:line to open. Use when a button does nothing, a form will not submit, data will not load, a page renders blank or stale, a modal will not close, or the user says "it's broken" and the code review says it is fine.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill when the user wants to curate the SATK library knowledge index for a Simulink project — mark commonly used blocks, correct auto-assigned block categories, or improve block descriptions so the model-building agent picks better blocks from custom libraries. Triggered by phrases like "mark blocks common", "improve block descriptions", "correct block category", "make the agent prefer certain blocks", and from Gate 3 of building-simulink-models.

日本語の概要は準備中です。原文の説明を表示しています。

Manages MATLAB projects for Simulink workflows: path management, file registration, labels, source control configuration, and project lifecycle. Use when creating projects, adding models/dictionaries/requirements to projects, configuring labels for automation, fixing broken model references, or setting up source control for Simulink artifacts.

日本語の概要は準備中です。原文の説明を表示しています。

Specify plant models for closed-loop simulation: system specs, architecture, build plans, validation plans. Use when creating, updating, or reviewing plant model specifications, planning plant model architecture, or planning plant model validation.

日本語の概要は準備中です。原文の説明を表示しています。

Specify algorithms for Model-Based Design: system specs, architecture specs, implementation plans, test plans. Use when creating specifications for controllers, signal processing, diagnostics, estimators, or other algorithms authored in Simulink, Stateflow, System Composer, or MATLAB Function blocks.

日本語の概要は準備中です。原文の説明を表示しています。

Register, add, or update existing custom Simulink block libraries and configure block policy and knowledge index. Use when a user wants to register, set up, configure, or add existing .slx library files for agent-assisted model building. Do NOT use when the user wants to create or author a new library from scratch — that requires building-simulink-models.

日本語の概要は準備中です。原文の説明を表示しています。

Guide users through creating and managing .satk/block-policy.json for controlling which blocks the agent can use, which are excluded, and which block parameters the agent should not modify. Use when setting up block usage policy for a project.

日本語の概要は準備中です。原文の説明を表示しています。

Configures Simulink simulations non-destructively using SimulationInput objects — parameter overrides without modifying the model, batch sweeps via parsim, custom input signals via Dataset, and simulation data retrieval via logsout. Use when running sim()/parsim() with setVariable, setBlockParameter, setExternalInput, or when performing parameter sweeps and multi-run analysis. Not needed for one-shot simulations without configuration.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill to run multiple Simulink simulations in parallel with parsim, batchsim, and DesignStudy. TRIGGER when: user asks for parameter sweep, sweeping/varying parameters across simulations, Monte Carlo study, batch simulation, running multiple simulations, parallel simulations, large-scale multiple simulations, any task involving repeated simulations with different parameter values, user mentions having an existing script/function for parameter sweeps, or user wants to migrate from parfor/set_param/for-loop patterns to recommended workflows.

日本語の概要は準備中です。原文の説明を表示しています。