Brand Style Fit

AI Agent Instructions

Use this Classifier via the SuperClassify API from server code, not browser playground automation.

Place this after drafting brand copy. Supply the approved style guide, audience, channel and draft; keep the guide outside the writer's control. On revise, rewrite against that same guide and check again, at most three times. Preserve factual claims and product details while changing voice; abstain sends missing guidance back to the owner.

Class: superclassify/brand-style-fit@1.0.0
Fetch setup as text: https://superclassify.com/skills/superclassify/SKILL.md
Contract (JSON): https://superclassify.com/v1/resolve?ref=superclassify%2Fbrand-style-fit%401.0.0

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

Matches guide · 1

Text:
You can export logs as JSON.

Reference:
Style guide:
Use short direct sentences, address the reader as you, avoid hype and exclamation marks. Technical terms are allowed when needed.

Audience:
Software developers

Author expectation: matches_guide

Revise · 2

Text:
UNLOCK AMAZING POTENTIAL!!!

Reference:
Style guide:
Use short direct sentences, address the reader as you, avoid hype and exclamation marks. Technical terms are allowed when needed.

Audience:
Software developers

Author expectation: revise

Matches guide · 3

Text:
Set the Content-Type header to application/json.

Reference:
Style guide:
Use short direct sentences, address the reader as you, avoid hype and exclamation marks. Technical terms are allowed when needed.

Audience:
Software developers

Author expectation: matches_guide