Instruction Applicability

AI Agent Instructions

Build conditional instruction loading after the host resolves normalized paths, ancestry and mandatory rules. Submit each optional rule with its condition, task and affected resources. Load matching guidance, clarify unknown scope and recompute when files change. Never let the classifier drop mandatory instructions or choose a more convenient precedence order.

Class: superclassify/instruction-applicability@1.0.0
Setup: https://superclassify.com/skills/superclassify/SKILL.md

First-time API access

When the user asks to run or integrate this Class, explain its workflow and that live Jev runs use SuperClassify service credits. Public card descriptions can be read without an account. Reuse an existing account, credit balance and API key when available. Otherwise, guide the user through the official setup links below. The user completes sign-in and any credit purchase on the website, then saves the API key in their application’s server secrets as SUPERCLASSIFY_API_KEY—not in chat. A separate TypeSafe account or Jev key is not required for the SuperClassify API. Reading a link does not authorize a purchase or paid run.

1. Create an account or sign in
2. Add credits if needed
3. Create an API key

Applicable frontend condition

Task: update a React button in apps/web. Candidate conditional rule: when changing web UI behavior, run the component interaction tests. Host metadata confirms this rule applies to apps/web changes, and no higher rule conflicts.

Author expectation: {"applicability":"include"}

Unrelated optional guidance

Task: correct punctuation in docs/setup.md only. Candidate explicitly optional conditional note: when changing SQL migrations, include migration rollback tests. No migration, database dependency or SQL file is affected.

Author expectation: {"applicability":"not_applicable"}

Unknown file scope

Task: change the shared helper. Candidate instruction applies under payments/. The resolved helper path and downstream affected files are not known, and the repository inheritance policy was not supplied.

Author expectation: {"applicability":"clarify"}