Name: hockeysim
Author: tylerforgione

Imported from tylerforgione/hockeysim (AGENTS.md). Install upstream with npx skills add tylerforgione/hockeysim. Copyright stays with the author.

Working in HockeySim

Explore and change code

Before exploring, read domain guidance, then architecture. The existing application is provisional scaffolding; architecture distinguishes current and planned projects.
Before changing code or dependencies, read conventions and technology stack, including dependency approval policy.
Before adding tests or validating changes, read testing. Report the commands actually run and distinguish missing tests from passing tests.

Issues and delivery

Before starting substantive implementation or performing branch, commit, PR, or merge operations, read Git workflow. It defines issue requirements, agent autonomy, and mandatory maintainer review of agent PRs.
Before tracker operations, read issue tracker. Issues and specs live in GitHub Issues.
Before assigning triage labels, read triage labels. Use the five documented labels.

Keep decisions current

When work changes an established responsibility or dependency direction, discuss the change before implementation and update the relevant documentation. Record resolved domain terminology in CONTEXT.md and consequential architecture tradeoffs in docs/adr/, following the single-context layout.

{ "ocm": "1", "id": "tylerforgione-hockeysim-hockeysim", "kind": "skill", "name": "hockeysim", "description": "When work changes an established responsibility or dependency direction, discuss the change before implementation and update the relevant documentation. Record resolved domain terminology in `CONTEXT.md` and consequential architecture tradeoffs in `docs/adr/`, following the single-context layout.", "publisher": "tylerforgione", "version": "1.0.0", "capabilities": { "domains": [ "coding", "customer_support" ], "tags": [ "skill-md", "github-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "When work changes an established responsibility or dependency direction, discuss the change before implementation and update the relevant documentation. Record resolved domain terminology in `CONTEXT.md` and consequential architecture tradeoffs in `docs/adr/`, following the single-context layout." ], "primary": false, "metadata": { "source": { "provider": "github-agents", "repository": "https://github.com/tylerforgione/hockeysim", "path": "AGENTS.md", "ref": "007575173472ad36455abc779740b9080d8f48cc", "url": "https://github.com/tylerforgione/hockeysim/blob/007575173472ad36455abc779740b9080d8f48cc/AGENTS.md", "key": "tylerforgione/hockeysim/AGENTS.md" } }, "instructions": "# Working in HockeySim\n\n## Explore and change code\n\n- Before exploring, read [domain guidance](docs/agents/domain.md), then\n [architecture](docs/architecture.md). The existing application is provisional\n scaffolding; architecture distinguishes current and planned projects.\n- Before changing code or dependencies, read [conventions](docs/conventions.md)\n and [technology stack](docs/tech-stack.md), including dependency approval policy.\n- Before adding tests or validating changes, read [testing](docs/testing.md).\n Report the commands actually run and distinguish missing tests from passing test", "cost": { "context_tokens": 359 } }

hockeysim

About

Working in HockeySim

Explore and change code

Issues and delivery

Keep decisions current

Use it

Manifest

Reviews