Distillation

Date: Sep 9, 2026

• 🔴 [enforced-workflow] (23:50) User stated to always load repo-setup before situation skills; repository skills live under .agents/skills/, are generated from the canonical skills/ tree by scripts/sync-skills.mjs, and target-repository AGENTS.md / CONTRIBUTING.md files must be read first.
• 🔴 [enforced-workflow] (23:50) User stated to always check package.json for the latest scripts.
• 🔴 [enforced-dependency-policy] (23:50) User stated all packages must be added to devDependencies, never dependencies, because everything is bundled at build time via esbuild; CI enforces this with pnpm run check:deps.
• 🔴 [enforced-dependency-policy] (23:50) User stated package additions must always use pnpm add -D <package> with the -D flag.
• 🔴 [enforced-testing-property] (23:50) User stated properties should “always hold regardless of input.”
• 🟡 (23:50) Repository guidance in packages/cli/CONTRIBUTING.md specifies command conventions: list commands use optional positional context; view commands use optional primary identifiers; target forms are <org>/<project>, <org>/, <project>, or omitted for auto-detection; context priority is 1. positional arguments, 2. config defaults, 3. DSN auto-detection from SENTRY_DSN or source code.
• 🟡 (23:50) packages/cli/CONTRIBUTING.md requires new commands to: 1. choose list or view patterns, 2. reuse resolveOrg() / resolveOrgAndProject() from lib/resolve-target.ts, 3. support --json, 4. support -w / --web for view commands, 5. use ContextError for missing context, and 6. add E2E tests under test/e2e/.
• 🟡 (23:50) packages/cli/CONTRIBUTING.md code-style rules are TypeScript strict mode, explicit types for public APIs, JSDoc documentation, and small focused functions.
• 🟡 (23:51) packages/cli/.cursor/rules/ultracite.mdc identifies Ultracite as the project’s zero-config Biome preset and documents commands: npx ultracite fix to format/fix, npx ultracite check to check issues, and npx ultracite doctor to diagnose setup.
• 🟡 (23:51) Ultracite review priorities are ordered as: 1. business-logic correctness, 2. meaningful naming, 3. architecture decisions, 4. edge cases, 5. user experience, and 6. documentation; npx ultracite fix should run before committing.