Agent skill

Eng Code Guidelines

by compozy in compozy/compozy

Go production discipline for Compozy. An agent skill from compozy/compozy.

MITAuto-check passedDevelopment

Install Eng Code Guidelines

skills CLI
$ npx skills add compozy/compozy --skill eng-code-guidelines -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install compozy/compozy eng-code-guidelines --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/compozy/compozy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/eng/eng-code-guidelines .claude/skills/eng-code-guidelines && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
eng-code-guidelines
GitHub stars
2.8k
Token cost
~567 tokens
SKILL.md length
240 words
Files
3 (incl. references)
Skills in repo
47
Repo updated
First seen
Licence
MIT

At a glance

Go production discipline for Compozy. An agent skill from compozy/compozy.

  • Editing non-test Go files under cmd
  • Calls make
  • Including config
  • Process-lifecycle paths

What it does

Eng Code Guidelines is an agent skill from compozy/compozy. Go production discipline for Compozy. Use when writing or editing non-test Go files under cmd or internal, including config, logging, CLI, concurrency, and process-lifecycle paths. Do not use for Go tests; pair it with the narrower schema, contract, or cleanup skill when those domains apply.

Its SKILL.md is about 570 tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/coding-style.md` and `references/concurrency-patterns.md`).

It sits in Development. The repository describes itself as: An operating system for AI agents. Plug in the agent CLIs you already use (Claude Code, Codex, Gemini CLI, Cursor) and they become a team: they split the work, hand tasks to each… The licence is MIT.

When your agent uses it

  • Editing non-test Go files under cmd
  • Including config
  • Process-lifecycle paths
  • Pair it with the narrower schema

Example prompts

  • “/eng-code-guidelines”

What it can do on your machine

Read from SKILL.md and the folder at commit eec2ed1. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • make

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Eng Code Guidelines loads about 567 tokens when it runs, and up to ~2.2k if it reads all its reference files. Until then it costs about 78 tokens; SKILL.md has 240 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~78
When it runs · the whole SKILL.md, loaded when a task matches
~567
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from compozy/compozy at commit eec2ed1, republished under its MIT licence (© compozy). 240 words, ~567 tokens.

Download SKILL.mdSave it as .claude/skills/eng-code-guidelines/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
eng-code-guidelines
description
Go production discipline for Compozy. Use when writing or editing non-test Go files under cmd or internal, including config, logging, CLI, concurrency, and process-lifecycle paths. Do not use for Go tests; pair it with the narrower schema, contract, or cleanup skill when those domains apply.
trigger
implicit

Compozy Code Guidelines

Apply repository-specific Go conventions to production files under cmd/ and internal/. Read the relevant sections of references/coding-style.md; for goroutines, shared state, detached execution, subprocesses, shutdown, timers, locks, or channels, also use references/concurrency-patterns.md.

  • Trace the changed behavior through its applicable error, context, configuration, CLI, logging, type, and resource boundaries. Fix touched violations without expanding into unrelated debt.
  • Each changed resource, goroutine, process, or mutable shared state has an owner. Use eng-cleanup-failure-paths when multiple fallible acquisitions make partial failure relevant.
  • Add a companion skill only for a distinct unresolved concern. golang-master supplies deeper language guidance when needed; it is not an automatic prerequisite.
  • For public behavior/contract changes, update the owning docs/_memory/change-impact.md audit. Cite an existing spec/task/PR audit instead of writing one per skill.

Run the focused owning check and reuse current scoped lint/race evidence. Cross-build and Linux-race parity checks follow the concurrency reference's applicable branches. Root make gate and PR CI policy apply at the enclosing commit/push or PR-delivery stage, not after each edit.

Specific failure cases

  • A dependency with only string errors may need one typed wrapper at its boundary so downstream code can match error identity.
  • Reflection in codegen/decoders needs an adjacent reason; lint exceptions retain a justified //nolint: directive.
  • A reachable production panic needs an explicit error path. For a proven unreachable invariant, prefer panic("invariant: ...") with its explanation over log.Fatal.
  • For silently ignored CLI flags, check cmd.Flags().Changed(name), the documented resolution chain, and the default-resolution debug log.

© compozy, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in .agents/skills/eng/eng-code-guidelines of compozy/compozy.

  • SKILL.md
  • references/coding-style.md
  • references/concurrency-patterns.md

Open the folder on GitHubat commit eec2ed1

Compare with similar skills

Eng Code Guidelines next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Eng Code Guidelines compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Eng Code Guidelines this skillcompozy/compozy2.8k—~567Automated safety check: PassMIT
Vercel Composition Patternssupabase/supabase111k59 repos~726Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Typescript Advanced Typesrolling-scopes/rsschool-app10k25 repos~4.2kAutomated safety check: PassMPL-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Official

    React composition patterns that scale. An agent skill from supabase/supabase.

    111k GitHub starsUsed in 59 repos~726 tokens
    DevelopmentAuto-check passed
  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Typescript Advanced Types

    rolling-scopes/rsschool-app

    Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.

    10k GitHub starsUsed in 25 repos~4.2k tokens
    DevelopmentAuto-check passed
  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

More from compozy/compozy

All 47 skills in this repo
  • Eng Real Scenario QA

    compozy/compozy

    Dogfoods Compozy through an autonomous startup scenario with live providers, cross-surface observation, and strict evidence audit.

    2.8k GitHub stars~3.4k tokensUpdated today
    Auto-check passed
  • Eng Test Conventions

    compozy/compozy

    Go test-shape discipline for Compozy. An agent skill from compozy/compozy.

    2.8k GitHub stars~467 tokensUpdated today
    Auto-check passed
  • Assistant UI

    compozy/compozy

    Guide for assistant-ui library - AI chat UI components. An agent skill from compozy/compozy.

    2.8k GitHub stars~958 tokensUpdated today
    Auto-check passed
  • Guide for assistant-ui UI primitives - ThreadPrimitive, ComposerPrimitive, MessagePrimitive.

    2.8k GitHub stars~999 tokensUpdated today
    Auto-check passed
  • Assistant UI Runtime

    compozy/compozy

    Guide for assistant-ui runtime system and state management. An agent skill from compozy/compozy.

    2.8k GitHub stars~856 tokensUpdated today
    Auto-check passed
  • Assistant UI Streaming

    compozy/compozy

    Guide for assistant-stream package and streaming protocols. An agent skill from compozy/compozy.

    2.8k GitHub stars~813 tokensUpdated today
    Auto-check passed

Categories

Questions about Eng Code Guidelines

What does Eng Code Guidelines do?

Go production discipline for Compozy. An agent skill from compozy/compozy. Eng Code Guidelines is an agent skill from compozy/compozy. Go production discipline for Compozy.

When should I use Eng Code Guidelines?

Eng Code Guidelines fits situations like: editing non-test Go files under cmd; including config; process-lifecycle paths; pair it with the narrower schema.

How do I install Eng Code Guidelines in Claude Code?

Run `npx skills add compozy/compozy --skill eng-code-guidelines -a claude-code`. Or copy the skill folder (.agents/skills/eng/eng-code-guidelines in compozy/compozy) into .claude/skills/eng-code-guidelines in your project. Claude Code loads it when a task matches its description.

How do I install Eng Code Guidelines in Codex?

Run `npx skills add compozy/compozy --skill eng-code-guidelines -a codex`. Or copy the skill folder (.agents/skills/eng/eng-code-guidelines in compozy/compozy) into .agents/skills/eng-code-guidelines in your project. Codex loads it when a task matches its description.

Can I use Eng Code Guidelines in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add compozy/compozy --skill eng-code-guidelines -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/eng-code-guidelines, .gemini/skills/eng-code-guidelines, .github/skills/eng-code-guidelines and .opencode/skills/eng-code-guidelines in your project.

What does Eng Code Guidelines need to run?

Going by SKILL.md and its folder, Eng Code Guidelines needs the command-line tools its instructions call (make).

Does Eng Code Guidelines access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Eng Code Guidelines safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Eng Code Guidelines use?

Eng Code Guidelines is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Eng Code Guidelines use?

About 567 tokens (SKILL.md is roughly 2.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.7k tokens, read only when the agent opens those files.

What are the alternatives to Eng Code Guidelines?

Skills that share tags, products or a category with Eng Code Guidelines: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 296k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Eng Code Guidelines?

compozy (a GitHub organization) maintains it in compozy/compozy, which has 2,792 GitHub stars. The repository holds 47 skills in this directory. The repository was last updated on October 8, 2026.

Source: compozy/compozy on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.