Social Media Style Guide — Ironframe
Visual identity
| Element | Guideline |
|---|---|
| Primary palette | Slate/neutral backgrounds (slate-950, slate-900); accent cyan (telemetry), emerald (sustainability), amber (warnings) |
| Typography | Clean sans-serif; monospace for SHAs, cents, API paths |
| Imagery | Command Center UI crops, architecture diagrams, agent icons—no stock “hackers in hoodies” |
| Logo usage | [Ironframe wordmark — insert asset path when finalized] |
Tone examples
Good:
“Ironwatch detected 4 hours of degraded sustainability API fidelity. Ironframe entered Stale Data mode—maturity attestation thresholds raised until fidelity restored.”
Avoid:
“Our AI destroyed your risks instantly 🚀🔥”
Post formats
LinkedIn (professional)
- 150–300 words
- Hook → problem → Ironframe mechanism → proof → CTA
- One image or carousel
X / Twitter (technical)
- Thread-friendly: 1/5 architecture, 2/5 problem, etc.
- Link to docs hub or release evidence
Agent naming chart (for carousels)
| Agent | Color hint | One-line role |
|---|---|---|
| Ironcore | Blue | Orchestrator |
| Irontrust | Gold | ALE scoring |
| Irongate | Red | Ingest DMZ |
| Ironwatch | Cyan | External API health |
| Ironlock | Amber | Emergency lockdown |
| Ironbloom | Green | Sustainability analyst (Agent 17) |
| Kimbot | Rose | Bot B — Red Team Adversary Simulation for drills |
Accessibility
- Alt text on all UI screenshots
- Sufficient contrast on chart overlays
- No essential info only in image text