Claude Skills by brycewang-stanford

Use when building or repairing the conceptual framework of a Journal of International Marketing (JIM) manuscript — theorizing why effects differ across countries, choosing cultural/institutional lenses, and drafting cross-national hypotheses. It builds the mechanism; jim-literature-positioning stakes the claim against prior work.

Use when choosing or auditing a research question for a Journal of International Marketing (JIM) manuscript — testing whether the international dimension is the theoretical core and whether JIM beats sibling outlets. It vets the question; jim-theory-development builds the mechanism.

Use when starting or unblocking a Journal of International Marketing (JIM) manuscript and you need to pick the right jim-* sub-skill for the current stage, from first idea through the response letter. It routes to the specialist skills; it does not do their work.

Use when drafting or revising the prose of a Journal of International Marketing (JIM) manuscript — the 200-word abstract, introduction architecture, precise culture language, and AMA-journal conventions. It polishes expression; substance fixes belong to the upstream skills.

Use when the cross-country/time-series data construction, sample, frequency, or measurement of a Journal of International Money and Finance (JIMF) manuscript is the bottleneck. Builds the international dataset and measurement; it does not establish causality (jimf-identification) or run robustness (jimf-robustness).

Use when the identification argument is the bottleneck for a Journal of International Money and Finance (JIMF) manuscript — open-economy causal designs, high-frequency policy/FX surprises, capital-control natural experiments, or parameter identification in an open-economy model. Stress-tests the strategy to JIMF's international-finance bar.

Use when organizing the online/supplementary appendix and the data-and-code deposit for a Journal of International Money and Finance (JIMF) manuscript. Structures supplementary material and the replication package; it does not establish the main result or write the main text.

Use when staking a Journal of International Money and Finance (JIMF) manuscript's contribution against the international-finance frontier and its sibling journals. Sharpens positioning; it does not invent evidence, exemplars, or citations.

Use when a Journal of International Money and Finance (JIMF) decision letter has arrived and you need a response-letter strategy for an R&R or a reject-and-resubmit. Plans the revision and response; it does not pre-empt objections before submission (jimf-referee-strategy).

Use when anticipating and pre-empting referee objections before submitting a Journal of International Money and Finance (JIMF) manuscript. Maps the likely international-finance pushbacks to fixes you make now; it does not draft the post-decision response (jimf-rebuttal).

Use when a Journal of International Money and Finance (JIMF) result must be shown stable across samples, regimes, measures, and inference choices. Designs the robustness layer mapped to international-finance threats; it does not establish the design (jimf-identification / jimf-empirical-design).

Use when running the final pre-submission preflight for a Journal of International Money and Finance (JIMF) manuscript via Elsevier Editorial Manager — file set, abstract/Highlights/JEL, declarations (competing interest, CRediT), data statement, and house style. Final checks; it does not draft content.

Use when building or revising the exhibits of a Journal of International Money and Finance (JIMF) manuscript so the international result is legible and respects Elsevier/finance presentation norms. Formats exhibits; it does not establish the result (jimf-identification / jimf-robustness) or write the prose.

Use when deciding whether a question belongs at the Journal of International Money and Finance (JIMF) and how to frame it as international monetary/financial economics. Tests scope and the international margin; it does not invent evidence, exemplars, or citations.

Use when deciding which jimf-* sub-skill to invoke next, or when sequencing a Journal of International Money and Finance (JIMF) manuscript from topic through rebuttal. Routes — it does not replace — the specialized skills.

Use when the prose, intro, abstract, or Highlights of a Journal of International Money and Finance (JIMF) manuscript do not land for an international-finance audience. Sharpens the writing and front matter; it does not change the result or the design.

Use when the identification argument is the bottleneck for an empirical Journal of Law, Economics, and Organization (JLEO) manuscript — institutional/organizational causal designs (reforms, institutional variation, court/committee/case assignment, governance-form choice). Stress-tests the design to JLEO's institutional bar; it does not build the theory model (jleo-theory-model).

Use when staking a Journal of Law, Economics, and Organization (JLEO) manuscript's contribution against the new-institutional / positive-political-economy frontier — locating it relative to Williamson/North/Weingast and to sibling journals. Sharpens the contribution claim; it does not write the literature review prose.

Use when a Journal of Law, Economics, and Organization (JLEO) decision letter has arrived and you need a response-letter strategy — triaging an institutional-economist referee's report into a credible revision and point-by-point reply. Plans the rebuttal; it does not redo the analysis (route back to the relevant jleo-* skill).

Use when anticipating the referee read on a Journal of Law, Economics, and Organization (JLEO) manuscript before submitting — modeling the institutional/organizational economist who will review it and pre-empting the objections that sink JLEO papers. Anticipates objections; it does not write the response to an actual report (jleo-rebuttal).

Use when assembling the data and code replication package for a Journal of Law, Economics, and Organization (JLEO) manuscript — building reproducible paths from institutional/organizational/political data sources (court records, contracts, legislative data, firm-boundary data) to every exhibit. Builds the package; it does not run new analysis.

Use when organizing robustness and sensitivity checks for a Journal of Law, Economics, and Organization (JLEO) manuscript — structuring checks by the institutional/organizational threat each one defuses (selection into governance, reform endogeneity, measurement of institutional constructs, alternative mechanisms). Organizes the robustness program; it does not establish primary identification (jleo-identification).

Use when running the final pre-submission preflight for a Journal of Law, Economics, and Organization (JLEO) manuscript via the Editorial Express portal — files, anonymization, format, disclosures, and data-policy readiness for the Oxford University Press journal. Final checks; it does not draft content.

Use when designing tables and figures for a Journal of Law, Economics, and Organization (JLEO) manuscript — making exhibits carry the institutional/organizational comparison cleanly for an OUP economics audience. Improves the exhibits; it does not run the analysis (jleo-robustness) or write the prose (jleo-writing-style).

Use when building or sharpening the formal model for a Journal of Law, Economics, and Organization (JLEO) manuscript — transaction-cost, incomplete-contracts / property-rights, principal-agent, or political-agency models of institutions and organizations. Right-sizes and disciplines the model; it does not run the empirics (jleo-identification, jleo-robustness).

Use when scoping or pitching a topic for a Journal of Law, Economics, and Organization (JLEO) manuscript — testing whether the question is a genuine law-economics-organization / positive-political-economy contribution rather than a sibling-journal fit. Sharpens the question and its audience; it does not design identification or build the model.

Use when deciding which jleo-* sub-skill to invoke next, or when sequencing manuscript work from topic selection through rebuttal for a Journal of Law, Economics, and Organization (JLEO) submission. Routes — it does not replace — the specialized skills.

Use when the prose, introduction, or abstract of a Journal of Law, Economics, and Organization (JLEO) manuscript needs to land its institutional/organizational contribution for an OUP economics-of-institutions audience. Sharpens framing and exposition; it does not change the analysis or the model.

Use when the causal identification argument is the bottleneck for a The Journal of Law and Economics (JLE) manuscript — a law change (DiD/event study), a court/judge/case-assignment design, a regulatory threshold (RD), or an antitrust/enforcement event. Stress-tests the law-to-outcome mapping to the JLE credibility bar before exhibits are finalized; it does not write the prose or build the deposit.

Use when the marginal contribution of a The Journal of Law and Economics (JLE) manuscript is fuzzy or undersold and must be staked precisely against prior law-and-economics work. Positions the contribution; it does not fix the identification (jle-identification) or the prose (jle-writing-style).

Use when a The Journal of Law and Economics (JLE) decision letter arrives (R&R or conditional accept) and a response-to-referees letter plus a revision plan must be drafted. Plans and structures the response; it does not run the new analysis (jle-identification / jle-robustness) or the submission preflight (jle-submission).

Use when anticipating the objections a law-and-economics referee at The Journal of Law and Economics (JLE) will raise, so a manuscript pre-empts them before submission or addresses them in revision. Plans the defense around JLE's single-blind process; it does not draft the response letter (jle-rebuttal) or run the submission preflight (jle-submission).

Use when assembling the data and code package for a The Journal of Law and Economics (JLE) manuscript to satisfy the journal's replication policy — data, programs, and computation details available for replication before publication. Builds the deposit and README; it does not run the analysis or write the paper.

Use when a The Journal of Law and Economics (JLE) manuscript's headline estimate must be shown to survive specification, sample, jurisdiction, and inference choices before submission or in an R&R. Builds the robustness suite a law-and-economics referee expects; it does not establish the primary identification (jle-identification) or format the exhibits (jle-tables-figures).

Use when running the final pre-submission preflight for a The Journal of Law and Economics (JLE) manuscript via the Editorial Manager portal — the single-blind title page, the US$100 submission fee, Chicago author-date style, the replication-policy readiness, and disclosures. Final checks; it does not draft content.

Use when building or revising the exhibits of a The Journal of Law and Economics (JLE) manuscript so the effect of the legal rule is legible in one table or figure and respects University of Chicago Press presentation norms. Formats exhibits; it does not establish the result (jle-identification / jle-robustness) or write the surrounding prose.

Use when a The Journal of Law and Economics (JLE) manuscript needs a model of the legal rule — deterrence, liability, contracting, or regulation — to interpret estimates, generate testable predictions, or carry a theory contribution in the Chicago price-theory tradition. Calibrates how much theory belongs and where; it does not design the identification (jle-identification).

Use when deciding whether a law-and-economics project belongs at The Journal of Law and Economics (JLE) rather than the Journal of Legal Studies, JLEO, or the American Law and Economics Review, and what its central legal/regulatory question should be. Sets venue fit and question scope; it does not design the identification (see jle-identification).

Use when deciding which jle-* sub-skill to invoke next, or when sequencing manuscript work from topic selection through rebuttal for a The Journal of Law and Economics (JLE) submission. Routes — it does not replace — the specialized skills.

Use when revising the prose, abstract, and introduction of a The Journal of Law and Economics (JLE) manuscript so the legal institution and the design land early, in University of Chicago Press house style with Chicago author-date citations. Polishes exposition; it does not change the result (jle-identification / jle-robustness) or the exhibits.

Use when turning results into an explicit contribution for a Journal of Management Information Systems (JMIS) manuscript — an advance to an IS-management/economics conversation with theoretical and managerial implications. Frames the contribution and aligns intro/discussion; it does not position the literature (jmis-literature-positioning) or run the submission preflight (jmis-submission).

Use when the estimation, identification, construct validity, or modeling is the bottleneck for a Journal of Management Information Systems (JMIS) manuscript — econometrics on firm/platform data, SEM/PLS for behavioral constructs, analytical-model derivations, or ML/analytics evaluation. Executes and stress-tests the analysis the design (jmis-methods) chose; it does not redesign the study.

Use when staking a Journal of Management Information Systems (JMIS) manuscript's contribution against the IS literature and the basket siblings — showing it advances an IS-management/economics conversation rather than only a reference discipline. Positions the work; it does not build the mechanism (jmis-theory-development) or write the contribution statement (jmis-contribution-framing).

Use when choosing and defending the research design for a Journal of Management Information Systems (JMIS) manuscript — IT-value/platform econometrics, a behavioral survey or experiment, an analytical/economic model, or a design-science/data-science artifact. Matches the method to the IS claim and the ≤50-page budget; it designs the study and hands estimation/evaluation to jmis-data-analysis.

Use when planning and drafting the response to a Journal of Management Information Systems (JMIS) major/minor revision — a point-by-point reply to the EIC, Associate Editor, and double-anonymized referees that resolves identification, measurement, contribution, and robustness concerns. Plans and drafts the response; revisit earlier jmis-* skills to execute the underlying fixes.

Use when calibrating expectations for the Journal of Management Information Systems (JMIS) editorial process — the EIC-led, email-intake, double-anonymized review by Associate Editors and expert referees, likely decision types, and timing. Sets expectations and revision posture; it does not draft the response letter (jmis-rebuttal).

Use when running the final pre-submission preflight for a Journal of Management Information Systems (JMIS) manuscript — the email-to-EIC intake, full anonymization for double-blind review, the ≤50-page and 150-word-abstract limits, the numbered bracketed reference style, and the cover-letter/attachment package. Final checks; it does not draft content.

Use when the exhibits are the bottleneck for a Journal of Management Information Systems (JMIS) manuscript — regression/SEM tables, platform/value figures, measurement-model exhibits, or artifact-evaluation charts that must carry the argument inside the 50-page budget. Finalizes exhibits and labeling; it does not run the analysis (jmis-data-analysis) or polish prose (jmis-writing-style).

Use when building the theoretical engine of a Journal of Management Information Systems (JMIS) manuscript — an IT-business-value logic, a platform/network-effects mechanism, an economic model of IS, or a technology-specific behavioral theory. Adapts the form of "theory" to JMIS's management-and-economics-of-IS identity; it does not run the analysis (jmis-data-analysis) or frame the contribution (jmis-contribution-framing).

Use when deciding whether a question is the right shape for a Journal of Management Information Systems (JMIS) manuscript — an IS-management or economics-of-IS problem, not a generic tech study or a pure CS contribution. Pressure-tests fit and outlet choice before theory work begins; it does not build the mechanism (jmis-theory-development).