lang-research-design
Use when defending the empirical design of a Language (LSA) manuscript on the terms of its subfield — elicitation and fieldwork, corpus construction, phonetic measurement, experiment, or the diachronic/typological sample. Language judges each kind of evidence by its own standards, and the design must support the theoretical claim. Defends the design; it does not run the analysis.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill lang-research-design --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Research Design (lang-research-design) *Language* is method-pluralist: it publishes elicited fieldwork, corpus studies, phonetic and experimental work, computational modeling, and diachronic/typological comparison, and it judges each by the standards of *its own subfield*. The job here is to make the design defensible to a general, possibly cross-subfield, double-anonymous reviewer — and to show the evidence actually supports the theoretical claim from `lang-theory-building`. ## When to trigger - Choosing or justifying the design before data collection or analysis - A reader questioned the elicitation, the consultant sample, corpus coverage, measurement, or the typological sample - Aligning the evidence with the analysis's predictions - Mixed-evidence work (e.g., corpus + experiment) that must defend each component ## Defend the design (by subfield) ### Elicited / fieldwork data - Describe **consultant number and background, elicitation method, and the recording/annotation workflow**; distinguish elicited judgments from spontaneous/textual data. - Give data in **numbered examples with Leipzig interlinear glossing** and a source for each token; a reader must be able to see the pat
- When to trigger
- Defend the design (by subfield)
- Elicited / fieldwork data
- Corpus / quantitative usage
- Phonetic / experimental
- Diachronic / typological
- Computational / modeling
- Match design to claim
- Referee-pushback patterns by subfield (the modal Language objection)
- Calibration with a quick example (hedged)
- Design pass for Language
- Anti-patterns
- Output format
- Supplementary resources
What does the lang-research-design skill do?
Use when defending the empirical design of a Language (LSA) manuscript on the terms of its subfield — elicitation and fieldwork, corpus construction, phonetic measurement, experiment, or the diachronic/typological sample. Language judges each kind of evidence by its own standards, and the design must support the theoretical claim. Defends the design; it does not run the analysis.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill lang-research-design --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.