本文へ移動
cccskills

「building」の検索結果

4,907 件 ・ 関連度順

概要と使いどころ

Use when building figures and tables for an Agricultural Systems (AgSy) manuscript so exhibits communicate interactions, dynamics, trade-offs, and model performance clearly. AgSy is a systems journal, so the best exhibits show trade-off frontiers, observed-vs-simulated fit, resource flows, and conceptual system diagrams — not just a bar chart of one treatment. Designs exhibits; it does not run the analysis.

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

brycewang-stanford/Awesome-Journal-Skills1,2692026年9月27日 更新

Use when building or revising exhibits for an AEJ: Economic Policy manuscript so they meet AEA house style and carry the policy message — no significance asterisks, a self-contained headline exhibit, and figures that show the policy effect with uncertainty. Designs exhibits; it does not run the estimation or write the surrounding prose.

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

brycewang-stanford/Awesome-Journal-Skills1,2692026年9月27日 更新

Use when building the theoretical engine for an Administrative Science Quarterly (ASQ) manuscript — mechanisms, process vs. variance logic, constructs, and boundary conditions. Builds the argument; it does not select methods or run analysis.

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

brycewang-stanford/Awesome-Journal-Skills1,2692026年9月27日 更新

Use when building and refining exhibits for an Administrative Science Quarterly (ASQ) manuscript — qualitative data structures and data-to-theory tables, process models, and quantitative tables. Designs exhibits; it does not run the analysis behind them.

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

brycewang-stanford/Awesome-Journal-Skills1,2692026年9月27日 更新

Use when building or revising the exhibits of an American Economic Journal: Applied Economics (AEJ: Applied) manuscript so the main causal result is legible in one table or figure and respects AEA house presentation norms. Formats exhibits; it does not establish the result (aeja-identification / aeja-robustness) or write the surrounding prose.

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

brycewang-stanford/Awesome-Journal-Skills1,2692026年9月27日 更新

Use when packaging code, models, datasets, or media as ACM MM (ACM Multimedia) artifacts — building the anonymous review package versus the public release, and choosing between the Open Source Software Competition, the Dataset track, the Reproducibility track, and main-track supplementary evidence, each with its own blinding and expectations.

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

brycewang-stanford/Awesome-Journal-Skills1,2692026年9月27日 更新

Use when building or auditing the related-work section of an ACM MM (ACM Multimedia) paper — covering the multimedia literature spread across vision, audio/speech, language, HCI/QoE, and systems, handling arXiv-speed concurrency, keeping citations double-blind, and verifying that cited "ACM MM papers" are ACM MM and not ICMR, MMSys, CVPR, or TOMM.

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

brycewang-stanford/Awesome-Journal-Skills1,2692026年9月27日 更新

Use when building the exhibits of an Accounting, Organizations and Society (AOS) manuscript — data-inventory and evidence tables for qualitative work, cell-means and process-test tables for experiments, and figures that carry theoretical weight — in Elsevier-compatible format. Builds exhibits; it does not run the analysis (aos-data-analysis).

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

brycewang-stanford/Awesome-Journal-Skills1,2692026年9月27日 更新

Use when building the actual theory for an Academy of Management Review (AMR) manuscript — turning a positioned puzzle into defined constructs, explicit relationships, propositions, and boundary conditions. Constructs the theory; it does NOT stress-test the argument's logic (that is amr-data-analysis) or design any data collection (AMR has none).

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

brycewang-stanford/Awesome-Journal-Skills1,2692026年9月27日 更新

Use when building the robustness section for a 《会计研究》 (Accounting Research) manuscript — replacing accounting measures with alternatives, adding governance / institutional controls, placebo tests, and endogeneity follow-ups — so the main result survives an accounting referee's scrutiny. Use after mechanism is settled.

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

brycewang-stanford/Awesome-Journal-Skills1,2692026年9月27日 更新

Use when choosing and applying a theory-construction method for an Academy of Management Review (AMR) manuscript — building constructs, defining their domain, specifying relationships, articulating the underlying logic/mechanisms, and setting boundary conditions. This is the THEORY-CONSTRUCTION craft, NOT empirical method; AMR publishes no datasets, no measures, and no statistical tests.

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

brycewang-stanford/Awesome-Journal-Skills1,2692026年9月27日 更新

Use when building or repairing the literature review for 《会计研究》 (Accounting Research) — entering the accounting research lineage (earnings quality, conservatism, audit quality, disclosure, value relevance) rather than piling recent Chinese empirical citations, and positioning the gap as an accounting contribution.

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

brycewang-stanford/Awesome-Journal-Skills1,2692026年9月27日 更新

Use when building the conceptual exhibits of an Academy of Management Review (AMR) manuscript — process models, 2x2 typologies, multi-level frameworks, and propositions tables that carry theoretical work. These are CONCEPTUAL figures, NOT data plots; AMR has no charts of results because it has no data.

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

brycewang-stanford/Awesome-Journal-Skills1,2692026年9月27日 更新

Use when building the theoretical engine of an Accounting, Organizations and Society (AOS) manuscript — choosing a social/organizational theory tradition (institutional theory, governmentality, Bourdieu, actor-network theory, practice theory, psychological process theory) and making it generate the analysis rather than decorate it. Builds the lens; it does not collect data (aos-methods) or frame the contribution (aos-contribution-framing).

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

brycewang-stanford/Awesome-Journal-Skills1,2692026年9月27日 更新

Use when deciding which amr-* sub-skill to invoke next, or when sequencing a theory-building manuscript from theoretical-puzzle framing through developmental-review revision for an Academy of Management Review (AMR) submission. Routes — does not replace — the specialized skills.

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

brycewang-stanford/Awesome-Journal-Skills1,2692026年9月27日 更新

Use when the theoretical argument and hypotheses are the bottleneck for an Academy of Management Journal (AMJ) manuscript — building a mechanism and deriving testable hypotheses a priori. Constructs the theory; it does not run the analysis (amj-data-analysis) or write the final contribution paragraph (amj-contribution-framing).

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

brycewang-stanford/Awesome-Journal-Skills1,2692026年9月27日 更新

Use when building or cleaning the tables and figures for an Academy of Management Journal (AMJ) manuscript — correlation tables, regression/SEM/HLM result tables, the theoretical-model figure, and interaction plots in AOM house style. Finalizes exhibits; it does not run the analysis (amj-data-analysis) or frame the contribution (amj-contribution-framing).

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

brycewang-stanford/Awesome-Journal-Skills1,2692026年9月27日 更新

Use when building the novel integrative framework that an Academy of Management Annals (Annals) review must deliver — the theory-advancing "new way of seeing the field" that is the acceptance bar, not a catalog of papers. Designs the spine; it does not gather the literature (amann-literature-synthesis) or appraise evidence balance (amann-evidence-standards).

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

brycewang-stanford/Awesome-Journal-Skills1,2692026年9月27日 更新

Use when building exhibits for an Academy of Management Annals (Annals) review — the signature framework figure, who-studied-what synthesis tables, and search/coverage exhibits that summarize across a literature. Designs review exhibits; it does not produce original-estimate regression tables (an Annals review reports no new data of its own).

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

brycewang-stanford/Awesome-Journal-Skills1,2692026年9月27日 更新

Identify programmatic SEO page patterns worth building for your product — vs/ pages, integrations/, for-{industry}/, alternatives-to/, use-cases/ — and design the template structure, data model, and priority order. Outputs a complete pSEO blueprint with URL patterns, title templates, content frameworks, and data sources per variable.

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

gooseworks-ai/goose-skills1,2562026年10月18日 更新

Discover newsletters in a target niche relevant to your ICP, evaluate audience fit, estimate reach and CPM, and output a ranked shortlist of sponsorship opportunities. Uses web search to find newsletters, then scores each against ICP alignment criteria. Use when a marketing team wants to reach an existing engaged audience for less than the cost of building their own, or when testing a new channel before committing.

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

gooseworks-ai/goose-skills1,2562026年10月18日 更新

Render an 'Instagram-Live social-proof gallery' video from a config — ~5 real brand product stills each framed as an Instagram-LIVE card (IG gradient-ring avatar, username, verified check, red LIVE badge, viewer count, close X, a short claim-free live-comment feed, an empty 'Add a comment…' bar, and reaction hearts floating up the right edge), with a brand-approved benefit sentence building one phrase per slide and a clean logo endcard, rendered deterministically with PIL frames plus FFmpeg — FREE (the music bed comes from create-music-elevenlabs), products and wordmark stay crisp. Use for the ig-live-gallery format.

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

gooseworks-ai/goose-skills1,2562026年10月18日 更新

Test-driven development for behaviour a unit test cannot reach, by writing the expectation against the running app before writing the code. Declare the consequence first, watch it fail, implement, watch it pass. Use when building a user-facing feature, when the user asks for TDD on UI or full-stack work, when a unit test cannot express the outcome that matters, or when you want a red-green loop that runs against the real app instead of mocks.

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

reticlehq/reticle1,2542026年10月18日 更新

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.

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

reticlehq/reticle1,2542026年10月18日 更新