language-evolution
Design evolving language systems for fictional worlds. Use when creating language families, dialects, linguistic history, or when language should reflect cultural and historical development.
What this skill does
# Language Evolution: Linguistic Development Skill You help writers create realistic language systems that evolve over time and reflect cultural history. This goes beyond conlang phonology to address how languages change, branch, and interact across generations and geographies. ## Core Principles 1. **Historical Continuity**: Languages evolve from previous forms rather than appearing fully formed 2. **Contact Modification**: Languages change through interaction with other languages 3. **Functional Adaptation**: Language structures evolve to serve communication needs 4. **Cultural Reflection**: Languages encode values, environment, and practices of speakers 5. **Cognitive Constraints**: Development is shaped by human cognitive limitations 6. **Register Variation**: Languages develop specialized forms for different contexts 7. **Innovation-Conservation Balance**: Languages contain both innovative and conservative elements 8. **Geographic Divergence**: Physical separation leads to linguistic divergence over time 9. **Sociolinguistic Stratification**: Language varies across social groups 10. **Writing System Independence**: Spoken and written forms evolve semi-independently ## Parameter Categories ### 1. Environmental Parameters | Parameter | What It Affects | |-----------|-----------------| | **Geographic Distribution** | Mountain ranges, rivers affecting spread | | **Climate Influence** | Weather and seasonal vocabulary | | **Resource Availability** | Local materials in terminology | | **Fauna and Flora** | Taxonomic complexity for important species | | **Topographical Marking** | Landscape feature naming patterns | ### 2. Cultural-Historical Parameters | Parameter | What It Affects | |-----------|-----------------| | **Migration Patterns** | Population movements creating contact | | **Conquest History** | Dominant-subordinate language relationships | | **Trade Networks** | Commercial contact creating exchange | | **Technological Development** | New terminology requirements | | **Religious Traditions** | Abstract concepts and sacred language | ### 3. Sociolinguistic Parameters | Parameter | What It Affects | |-----------|-----------------| | **Social Stratification** | Class-based language variation | | **Occupational Specialization** | Professional jargons | | **Gender Differentiation** | Gender-based language patterns | | **Age Grading** | Generational change markers | | **Group Identity Marking** | In-group terminology and pronunciation | ### 4. Communication Context Parameters | Parameter | What It Affects | |-----------|-----------------| | **Formality Levels** | Situational appropriateness markers | | **Medium Adaptation** | Spoken vs. written vs. digital | | **Specialist Discourse** | Technical, legal, scientific evolution | | **Artistic Expression** | Poetic, narrative, performance forms | | **Privacy/Secrecy** | Coded communication and euphemisms | ## Language Typologies ### Morphological Types | Type | Characteristics | Real Examples | |------|-----------------|---------------| | **Isolating** | Minimal word modification | Mandarin Chinese | | **Agglutinative** | Clear morpheme boundaries | Turkish, Japanese | | **Fusional** | Multiple meanings in single morphemes | Latin, Russian | | **Polysynthetic** | Many morphemes per word | Inuktitut, Mohawk | ### Word Order Types | Type | Pattern | Examples | |------|---------|----------| | **SVO** | Subject-Verb-Object | English, Mandarin | | **SOV** | Subject-Object-Verb | Japanese, Turkish | | **VSO** | Verb-Subject-Object | Irish, Classical Arabic | | **VOS** | Verb-Object-Subject | Malagasy | | **OVS** | Object-Verb-Subject | Hixkaryana | | **OSV** | Object-Subject-Verb | Rare | ### Writing System Types | Type | How It Works | Examples | |------|--------------|----------| | **Logographic** | Character per word/morpheme | Chinese | | **Syllabic** | Character per syllable | Japanese kana | | **Alphabetic** | Character per phoneme | Latin, Cyrillic | | **Abjad** | Consonants primarily | Arabic, Hebrew | | **Abugida** | Consonant-vowel units | Devanagari | | **Featural** | Characters represent features | Korean Hangul | ## Language Evolution Mechanisms ### Sound Change Types | Type | Description | |------|-------------| | **Lenition** | Weakening of consonants | | **Fortition** | Strengthening of consonants | | **Vowel Shift** | Systematic vowel changes | | **Palatalization** | Consonants shift toward palate | | **Assimilation** | Sounds become more similar | | **Metathesis** | Sound order swaps | ### Grammatical Evolution | Type | Description | |------|-------------| | **Grammaticalization** | Lexical words become grammatical | | **Analogical Leveling** | Irregular forms become regular | | **Case System Simplification** | Loss of case distinctions | | **Tense/Aspect Development** | New temporal distinctions | | **Evidentiality Emergence** | Source marking becomes grammatical | ### Contact Effects | Type | Description | |------|-------------| | **Lexical Borrowing** | Vocabulary adoption (most common) | | **Phonological Influence** | Sound system adjustments | | **Syntactic Convergence** | Sentence structure alignment | | **Morphological Simplification** | Complexity reduction in contact | | **Calquing** | Loan translation with native words | | **Code-Switching** | Alternation between languages | ## Language Family Construction ### Step 1: Proto-Language Design - Create core vocabulary (200-500 words) - Establish basic phoneme inventory - Define grammatical skeleton - Set morphological type ### Step 2: Sound Change Rules - Define systematic sound shifts - Apply changes to create daughter languages - Track which changes apply where - Create regular correspondences ### Step 3: Grammatical Divergence - Develop distinct innovations per branch - Create unique grammatical features - Track loss and gain of categories - Design independent evolution paths ### Step 4: Vocabulary Divergence - Track cognate relationships - Add unique vocabulary per branch - Create borrowings from contact - Develop semantic shifts ### Step 5: Contact Zone Development - Map where languages meet - Create contact effects - Develop pidgins/creoles if appropriate - Design bilingual phenomena ## Common Evolution Sequences ### Tonal Development - Consonant distinctions lost → Pitch compensates → Tones stabilize ### Case System Simplification - Full case → Reduced case → Prepositions → Fixed word order ### Creolization - Pidgin → Expanded pidgin → Creole with native speakers ### Dialect to Language - Single language → Regional varieties → Political division → "Separate languages" ## Setting-Specific Adaptations ### Fantasy Settings - **Elven Language Family**: Ancient, conservative, prestige - **Dwarven Isolation**: Mountain-separated dialects - **Human Diversity**: Rapid change and adaptation - **Magical Terminology**: Specialized arcane vocabulary - **Dead Language Remnants**: Ritual preservation ### Science Fiction Settings - **Post-Earth Divergence**: Colony isolation effects - **Alien-Human Pidgins**: Contact language development - **Universal Translator Implications**: Technology effects - **Digital-Augmented Communication**: Tech-language interface - **Xenolinguistic Principles**: Non-human cognition ### Post-Apocalyptic Settings - **Linguistic Fragmentation**: Isolation creating new dialects - **Technological Vocabulary Loss**: Terms for lost tech - **Specialized Jargon**: New environmental challenges - **Writing System Degradation**: Literacy decline effects - **Pre-Collapse Remnants**: Preserved texts, misunderstandings ## Sociolinguistic Variation ### Register Levels | Register | Context | Features | |----------|---------|----------| | **Frozen** | Ceremonies, oaths | Fixed phrases, archaic forms | | **Formal** | Official, professional | Complete sentences, technical | | **Consultative** | Teacher-student, expert-client | Standard grammar | | **Casual** | Friends, family | Slang, e
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.