Agent skill

locque-authoring

Author or update Locque .lq code and tests with the canonical M-expr syntax, CBPV rules, data/match forms, modules/imports/opens, and project conventions.

Stars 3
Forks 0

Install this agent skill to your Project

npx add-skill https://github.com/jaggederest/locque/tree/main/skills/locque-authoring

SKILL.md

Locque authoring

Use this skill when writing or editing Locque source or tests.

Sources of truth

  • grammar.md defines the canonical syntax and S-expr mapping.
  • AGENTS.md lists project conventions and tooling.

Workflow

  1. Prefer .lq M-expr files; do not handwrite .lqs.
  2. Keep paths lowercase. Every lib/** file must have a matching test/** file.
  3. Use Module::name qualification; open Alias exposing ... end is explicit only.
  4. Effects are explicit: computations are values via compute ... end, run via perform.
  5. Multiline constructs must end with end (function, compute, bind, match, data, typeclass, instance, module, open, pack, unpack).
  6. Data: define ... as data ... in TypeN ... end with constructors Type::Ctor; match uses case Type::Ctor.
  7. No implicit coercions; use of-type, lift, up, down, pack, unpack as needed.
  8. Use ignored instead of _ for unused binders.
  9. List literals are canonical: [] and [a, b] (commas required). Empty lists require of-type [] (List A) when no expected list type is in scope.

Test conventions

  • Use assert::assert-eq with an explicit type argument.
  • Run smyth test after changes.

Templates

Function:

locque
# Assumes: import arithmetic as Ar
define transparent inc as
  function x Natural returns Natural value
    Ar::add x 1
  end

Data:

locque
define transparent Option as data A Type0 in Type0
  case Option::none of-type Option A
  case Option::some of-type for-all x as A to Option A
end

Expand your agent's capabilities with these related and highly-rated skills.

jaggederest/locque

locque

Orient to the Locque repo, understand how to run and test programs, and follow key project conventions. Use this when starting work in the locque repo.

3 0
Explore
petekp/claude-code-setup

ubiquitous-language

Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".

20 6
Explore
petekp/claude-code-setup

every-style-editor

This skill should be used when reviewing or editing copy to ensure adherence to Every's style guide. It provides a systematic line-by-line review process for grammar, punctuation, mechanics, and style guide compliance.

20 6
Explore
petekp/claude-code-setup

manage-codex

Autonomous Codex batch orchestrator. Use for "/manage-codex", "manage codex", "use codex", "dispatch to codex", or long-running Codex work.

20 6
Explore
petekp/claude-code-setup

seo-audit

When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup. For AI search optimization, see ai-seo.

20 6
Explore
petekp/claude-code-setup

capture-learning

Analyze recent conversation context and capture learnings to project knowledge files (for project-specific insights) or skills/commands/subagents (for cross-project patterns). Use when the user asks to "capture this learning", "update the docs with this", "remember this for next time", "document this issue", "add this to CLAUDE.md", "save this knowledge", or "update project knowledge". Also triggers after resolving build/setup issues, discovering non-obvious patterns, or completing debugging sessions with valuable insights.

20 6
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results