alloy-languages

Assemble Alloy language packages for TypeScript, C#, Java, Python, and Go.

1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/hafley66/claude-research --skill alloy-languages
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: alloy-languages
Source: https://github.com/hafley66/claude-research/tree/main/skills/alloy-languages
Command: npx skills add https://github.com/hafley66/claude-research --skill alloy-languages

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Alloy language packages enable building and organizing multi-language targets (TypeScript, C#, Java, Python, Go) and guide the future Rust integration, including naming, scopes, and symbol resolution practices.

Core Features & Use Cases

  • Understand language package anatomy and internal structure for creating new targets
  • Map language constructs to Alloy components and apply naming conventions, scope rules, and symbol resolution
  • Scaffold new language packages (e.g. Rust) following the established pattern

Quick Start

Review the SKILL.md to understand how to explore language packages and start creating a new Alloy target.

Frequently Asked Questions about alloy-languages

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

FAQPage Schema
What are Alloy language packages and when do I need them for multi-language targets?

Alloy language packages organize multi-language targets like TypeScript, C#, Java, Python, and Go by mapping language constructs to Alloy primitives. You need them when designing language-specific components or planning Rust integration for consistent naming, scopes, and symbol resolution.

How do I scaffold a new Alloy language package for a target like Rust?

To scaffold a new Alloy language package, follow the established directory layout pattern by creating a SKILL.md frontmatter containing name and description, then optionally include scripts, references, and assets to map your target language constructs to Alloy primitives.

How do I map language constructs to Alloy components across TypeScript, C#, and Python?

Mapping language constructs to Alloy components involves applying consistent naming conventions, scope rules, and symbol resolution practices across TypeScript, C#, and Python. Each language package follows the same directory layout with SKILL.md frontmatter for structural consistency.

Does the Alloy language package structure support Rust integration alongside TypeScript and Go?

Yes, the Alloy language package structure plans for Rust integration alongside existing TypeScript, C#, Java, Python, and Go targets. New Rust packages follow the same established pattern with SKILL.md frontmatter, directory layout, and optional scripts, references, and assets.

What directory layout and files are required when creating an Alloy language package?

Creating an Alloy language package requires a consistent directory layout with a SKILL.md frontmatter containing name and description. You may optionally include scripts, references, and assets to support language-specific component design and naming policies.

What's the best way to define name policies and symbol resolution for multiple language targets?

The best way to define name policies and symbol resolution for multiple language targets is using Alloy language packages, which provide a consistent structure for mapping constructs across TypeScript, C#, Java, Python, and Go while applying uniform naming conventions and scope rules.