agentleFS
gloomyweathergloomyweather/opencode-setup/skills/linguistics/SKILL.md

linguistics

Skill0 starsChanged 55 days agoUnlicenseView on GitHub

Use when working with academic linguistics: phonetics/phonology and IPA transcription (Russian, English, French), morphosyntax with interlinear glossing, corpus analysis (RNC, COCA/BNC, French corpora), historical linguistics and reconstruction, language comparison, parsing sentences or word forms. Also suitable for planning French learning from scratch and preparing teaching materials in linguistics.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

Linguistics (Academic Linguistics)

Reference skill for academic linguistics with a focus on Russian, English, and French. Methodology + working tools; detailed material is in references/.

When to Use

  • Phonetic/phonological analysis, IPA transcription of words and sentences (RU/EN/FR)
  • Morphological and syntactic analysis, glosses, inflectional analysis
  • Corpus analysis: queries, frequency, collocations, quantitative methods
  • Historical linguistics: language comparison, reconstruction, sound laws
  • Planning French learning from scratch (or preparing teaching materials)

Not for: plain text translation (without linguistic analysis), generative AI/NLP engineering, language learning without an academic framework.

Routing

Load the reference for the task:

TaskReference
IPA, transcription, phonetic analysisreferences/phonetics-phonology.md
Morphology, syntax, glosses, typologyreferences/morphosyntax.md
Corpora, frequency, collocations, statisticsreferences/corpus.md
Comparative-historical method, reconstructionreferences/historical.md
Learning French from scratch, plan, French phoneticsreferences/french.md

Combine references for mixed tasks (for example, historical phonology → historical.md + phonetics-phonology.md).

Methodology

  1. Determine the language and level: linguistic analysis requires specifying the language and (for corpora) register/period. Default: Russian, English, French — as specified by the user.
  2. Load the needed reference and follow its conventions.
  3. Format the result according to academic conventions:
    • IPA — in square brackets [ ] for allophones, in slashes / / for phonemes.
    • Glosses — interlinearly according to Leipzig rules (see morphosyntax.md).
    • Corpus data — always with indication of corpus, sample size, and period.
  4. Separate analysis and interpretation: describe what is observed (form) separately from explanations (function/hypothesis), mark hypotheses as hypotheses.
  5. Verify data against primary sources (corpora, dictionaries, reference works), not from model memory. Mark anything doubtful explicitly.

Quick Reference

  • Phonemes RU/EN/FR: see phonetics-phonology.md → vowel/consonant tables.
  • Glossing: see morphosyntax.md → Leipzig rules + list of abbreviations.
  • Corpora: RNC ruscorpora.ru, COCA/BNC english-corpora.org, French — FrTenTen (SketchEngine), Est Républicain/Leipzig. More details in corpus.md.
  • Sound laws Proto-Slavic → Russian: second palatalization, loss of reduced vowels, akanye. More details in historical.md.

Common Mistakes

MistakeCorrect approach
Transcription based on spelling rather than pronunciationTranscribe according to actual pronunciation (for RU — taking vowel reduction into account)
Confusing a phoneme and an allophoneCheck minimal pairs; mark allophones with square brackets
Glosses without abbreviations or without word orderFollow Leipzig rules: form on the line under the word, abbreviations in capitals
Frequency without normalizationNormalize per million word forms (ipm), indicate corpus size
Etymological claims without verificationVerify against etymological dictionaries; cognate ≠ borrowing
Learning a language "from a textbook at random"Use french.md: a CEFR-level plan + phonetics before grammar

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.