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

ReleaseKit development

ReleaseKit is an independent, brand-neutral release content toolkit. Describe its visual language through composition, contrast, materials, hierarchy, and interaction. External references may inform those traits, but never put reference-company names, attributed style labels, product marks, reference-site URLs, or copied reference artwork into repository files, fixtures, generated instructions, prompts, or assets. Integration tool names and a user's own product identity are separate from visual reference attribution.

Keep the CLI deterministic. The user's coding agent performs editorial work and calls its available image tools. Do not add model API calls, API key setup, a viewer, or a publishing service without a corresponding request.

Project image generation defaults to both dark and light. Respect a project's explicit single-theme choice. A pair shares one scene specification; preserve geometry, feature meaning, and semantic colors between variants. Never manufacture a second variant through color inversion or claim that a pending image is ready.

Generate restrained flat explanatory graphics. Icons use compact filled glyphs, quiet flat tiles, and broad margins; do not turn them into sculpted objects or decorative 3D illustrations. Use neutral supporting elements and purposeful focal color. Prefer accent on a supported primary action, selected/enabled state, active path, or defining information when it guides attention; color need not be indispensable in grayscale. Generic information icons normally remain neutral. Review both decorative overuse and suppressed functional accents, without a fixed color quota. Map generated schematic elements to the captured palette roles by hierarchy. Review each theme at equal display widths: dark uses compact mid-light neutral glyphs, subordinate details, and distinct charcoal layers; light uses medium-gray neutral glyphs and softer supporting values. Keep shared geometry consistent and do not add arbitrary shades, tints, or material effects. A light-only palette correction preserves accepted dark images. Preserve explicit project palette overrides. Real physical details and content previews require supplied captures, photographs, or approved artwork. If that input is absent, request it and keep the image pending. One supplied image can be a shared asset across viewer themes without recoloring or duplication.

Store changes per release. Follow explicit previous-release links when assembling recent history, preserving version boundaries and entries with similar names. Resolve Git references to immutable commits before analyzing them.

Use Node.js 22.12 or later; develop with Node.js 24. Run npm run check, npm test, and npm run build for implementation changes. Tests should verify observable behavior, data integrity, and useful failure cases, rather than exact editorial wording. Keep documentation and public JSON schemas aligned with behavior.