# Knattercards — Instructions for brand-consuming agents

1. Fetch https://branddesign.knattercards.de/api/v1/manifest.json before each brand task. Read its actual response and follow the version-pinned document and asset URLs. Use one consistent version; verify SHA-256 checksums where available.
2. Read brand, guidelines, tokens, assets, templates and knatti documents. Rules with level `must` are mandatory; `should` are recommendations. The brand owner's instructions take precedence.
3. Use the original downloadable assets. Preserve logo proportions and underline. Do not reconstruct logos with fonts, recolor Knatti, add sticker outlines or enlarge raster assets beyond their native dimensions.
4. For new Knatti artwork, use the reference assets and generation instructions in knatti.json. Keep character identity and the documented pixel style. Existing poses may be used as references for new poses; do not silently alter app originals.
5. Assets marked `KCAPP` originate in the current imported app snapshot. Assets marked `Ergänzung` were generated for the brand library and are not automatically installed in the app. Read each object's usage and restrictions, including transparency and allowed crops.
6. Use core brand colors as given. `appColors` is a separate namespace for KCAPP interface colors. Keep each font's actual license with its files: OFL for Archivo and Barlow Condensed, CC0 for Pixel Operator Bold.
7. Cite the brand version and asset URLs used. Do not invent files, events, prices, availability or partnerships. If a required document cannot be fetched, report the issue instead of inventing a new brand system.
8. Public endpoints are read-only. Source updates require authorized project access and a new release. Never publish credentials, private source-machine paths or infrastructure configuration. Preserve historical release files.

Current rules: https://branddesign.knattercards.de/guidelines.md
Machine entry point: https://branddesign.knattercards.de/api/v1/manifest.json