language-idioms-refiner

Codify language-specific idioms into a reference document for pseudocode adaptation.

176|13|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/techygarg/lattice --skill language-idioms-refiner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: language-idioms-refiner
Source: https://github.com/techygarg/lattice/tree/main/plugins/lattice/skills/language-idioms-refiner
Command: npx skills add https://github.com/techygarg/lattice --skill language-idioms-refiner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clarifies language-specific idioms to standardize how code is written and reviewed across a project. Captures patterns for error handling, type usage, naming, tests, configuration, and dependency wiring as language-aware guidelines. Prevents drift when teams switch languages or onboard new contributors by providing a single reference document. Generates a reusable artifact that atoms can reference to align generated pseudocode with the project's language norms.

Core Features & Use Cases

  • Output: The document is produced at .lattice/standards/language-idioms.md (or a configured path from .lattice/config.yaml -> paths.language_idioms).
  • Mode: Standalone — no embedded language defaults exist in atoms to overlay; revisions load and update the existing document in place.
  • Config keys: language (top-level) and paths.language_idioms; supports the template from assets/template.md.
  • Template: Reads assets/template.md for structure, examples, and interview guidance notes.
  • Consumed by: Multiple atoms reference six stable sections: Error Handling, Type System & Object Model, Naming Conventions, Testing Patterns, Parameter & Function Design, Dependency Management.

Quick Start

Start the language-idioms refinement flow to generate the document at the configured path for your project language.

Frequently Asked Questions about language-idioms-refiner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize coding standards and language idioms across a new software project?

To standardize language idioms, this Skill identifies and codifies patterns for error handling, type usage, naming, tests, and dependency management into a single reference document for projectwide consistency.

What is the best way to document programming language idioms for pseudocode adaptations?

Documenting language idioms involves codifying rules for type systems and parameter design into an embeddable markdown file, ensuring pseudocode adaptations align with project language norms.

Can I configure the output path for language idioms and coding standards documents?

Yes, the output path is configurable via the paths.language_idioms key in your .lattice/config.yaml file, defaulting to .lattice/standards/language-idioms.md if no custom path is specified.

How do you prevent coding standards drift when onboarding new contributors to a different programming language?

You prevent drift by providing a single language-aware reference document that captures patterns for testing, configuration, and dependency wiring to guide code generation and reviews.

Does the language idioms document require existing coding standards to function?

No existing coding standards are required; it operates in standalone mode, loading and updating the existing document in place without relying on embedded language defaults.

What sections are included when defining language idioms for project consistency?

The generated document includes six stable sections: Error Handling, Type System & Object Model, Naming Conventions, Testing Patterns, Parameter & Function Design, and Dependency Management.