at-language-expert

Enforce explicit procedural constraints when writing and debugging at code.

2|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/aryaminus/at --skill at-language-expert
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: at-language-expert
Source: https://github.com/aryaminus/at/tree/main
Command: npx skills add https://github.com/aryaminus/at --skill at-language-expert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides essential procedural knowledge and constraints for writing and debugging at code, ensuring consistency and safety in AI-assisted development.

Core Features & Use Cases

  • Enforces explicit return types, alias imports, and explicit effects declarations to improve readability and mockability.
  • Provides a comprehensive guide to syntax, control flow, error handling, and tooling conventions for at programs.
  • Serves as a reference for building reliable agent-focused code with deterministic tests and safe sandboxing.

Quick Start

Create a minimal at program that demonstrates explicit return types, aliased imports, and a Result-based error path, then run at check to verify type- and lint-diagnostics.

Frequently Asked Questions about at-language-expert

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

FAQPage Schema
How do I enforce explicit return types and alias imports in at programming?

To enforce explicit return types and alias imports in at programming, apply mandatory frontmatter and procedural constraints. This approach improves code readability, ensures safe sandboxing, and enhances mockability for deterministic AI-assisted generation.

What is the best way to handle errors in at code?

The best way to handle errors in at code is using a Result-based error path. This procedural knowledge ensures deterministic, testable code generation by avoiding macros and enforcing explicit effects declarations for safe execution.

How do I run deterministic tests for at programs?

Run deterministic tests for at programs by executing 'at check' to verify type and lint diagnostics. This enforces syntax rules like semicolons and trailing commas while validating explicit capability declarations.

Why does my at code fail without explicit effects declarations?

At code fails without explicit effects declarations because the constraints mandate explicit capability declarations. This design philosophy prioritizes deterministic, testable code generation and safe sandboxing by avoiding macros and hidden side effects.

Can I use macros when writing at code?

No, you cannot use macros when writing at code. The procedural constraints explicitly avoid macros to ensure deterministic testing, enforce semicolons and trailing commas, and prioritize safe, testable code generation.