메뉴
Go code style and conventions for the adept codebase — formatting, linters, error wrapping with sentinels, the composition-root/no-globals rule, and core invariants. Apply when writing or reviewing Go in this repo. (matches: **/*.go)
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | adept-code-style |
| description | Go code style and conventions for the adept codebase — formatting, linters, error wrapping with sentinels, the composition-root/no-globals rule, and core invariants. Apply when writing or reviewing Go in this repo. (matches: **/*.go) |
| allowed-tools | ["Read","Grep","Edit"] |
Conventions for Go in github.com/itaywol/adeptability. CI enforces formatting and lint;
the rest is reviewed.
gofmt + goimports — tabs for indentation, grouped imports (stdlib / third-party /
local). CI fails on any unformatted file.golangci-lint run (.golangci.yml): errcheck (incl. type assertions), staticcheck,
govet, gocritic, revive (every exported symbol needs a doc comment), errorlint,
nilerr, bodyclose, prealloc, unconvert, misspell, unused, ineffassign.%w: fmt.Errorf("clone %s: %w", url, err).errors.Is against the sentinels in pkg/adept/errors.go
(ErrSkillNotFound, ErrMergeConflict, ErrBudgetOverflow, …). Never match on error
strings. Need a new category? Add a sentinel there.errcheck is strict — handle or explicitly _ = an ignored error, and say why if it isn't
obvious. Don't drop an error that loses data.*Deps in internal/cli/deps.go. No package-level mutable state, no init() side effects.
Take dependencies as parameters so code is testable with fakes/mocks.pkg/adept is types-only. Keep it dependency-light and stable; behavior lives in
internal/. (Example: SkillIDPattern is a string in pkg/adept, compiled in
internal/canonical — don't add a regexp import to pkg/adept.)// NewRoot builds …).pkg/adept/constants.go).(id, content-hash) — no version numbers as a sync signal.<root>/skills/<id>/SKILL.md; the directory name is the authoritative id.Capture a durable lesson, correction, or convention from this session as a reusable adept skill, then sync it to every harness. Apply when the user corrects you, when a fix generalizes, or when you say 'I'll remember that.'
Write a good, portable adept agent (subagent): trigger-shaped description, one job per agent, generator/evaluator separation, explicit boundaries, restricted tools. Apply when creating or editing an agent file or running `adept agent add`.
Compose a loop — a scheduled system that discovers work, hands it to agents, verifies with an independent evaluator, persists state, and reschedules itself. Apply when the user wants automation that runs on a timer, a triage/babysitter routine, or asks about `adept loop add`.
Write a good, portable adept skill: pick the right activation, craft a triggering description, keep it scan-safe and within harness byte budgets. Apply when creating or editing a SKILL.md or running `adept skill add`.
Team expertise billboard via `adept exchange`: ask teammates for expertise and stack responses. Apply when the user wants a colleague's input, mentions the exchange, or when you start using adept — sample open requests and offer to answer ones the user knows about.
Use the `adept` CLI to author AI skills once and render them into Claude Code, Cursor, Codex, Copilot, and OpenCode. Apply when installing/syncing skills, editing skill.yaml/SKILL.md, or touching .adeptability/.