amitray007

A skill provided by a plugin — not reachable by skillOverrides (skills.md §9.1).

A skill with unknown/third-party frontmatter keys (skills.md §3), for R1u's golden-fixture requirement that a skill with unknown frontmatter keys be covered.

A project-scope skill.

Lives outside ~/.claude/skills; reached via a symlink (skills.md §1.2).

This directory is secretly a plugin (has .claude-plugin/plugin.json) and must NOT be classified as a plain skill by the scanner.

A plain skill for the golden fixture tree.

A fixture skill used to prove ccstack never reads the real ~/.claude.

How to run, build, and test junction. Use when starting work on junction, running the CLI, building packages, running tests, or setting up the dev environment. Grows as each increment adds runnable surface.

Maintain junction's cross-session memory and hand off cleanly between Claude Code sessions. Use at the END of an increment (to log progress), when CONTEXT is getting heavy (to decide continue-vs-new-session), or at the START of a new session (to resume). Keeps docs/STATE.md current so any future agent can pick up with full context.

Drive the real, built, running @junction/web server to verify it actually works — not just that types/tests/build passed. Use at the QA step of any web increment, and before accepting a builder's "done" on web work. Catches the "green but blind" class of bug (unstyled build, dead SSR cookie, leaked secrets, layout desync, theme/motion regressions).

Junction's clean-code conventions for humans and agents. Use when writing or reviewing junction code, deciding how to structure a module, handling errors, or asking "how should I write this here". Points at the enforceable rules in docs/rules/.

Audit SDK coverage against the Etsy OAS spec to find gaps, drift, and stale enums

Fetch the latest Etsy OAS spec and diff it against the baseline to detect API changes

Check for new Etsy Open API releases on GitHub and analyze their impact on the SDK

Use whenever changing a contract type, shared interface, or any package consumed by multiple units in Sym. Forces you to think through how every other unit reacts to the change, with production-grade migration discipline drawn from how Stripe, Shopify, Linear, Honeycomb, GitHub, and DHH-style Rails shops manage live systems. Run BEFORE writing the change and again before opening the PR.