Prompt safety
Creytix Prompt Guard
Guardrails, eval hooks, and prompt-pack exports — safety modules before customer-facing AI ships.
Prompt safety
Creytix Prompt Guard
Prompt Guard ships guardrails, eval hooks, and prompt-pack exports — safety modules and PG-AC verification before customer-facing AI goes live.
What does Creytix Prompt Guard enforce?
No plaintext secrets in prompts, HF model defaults, cross-brand bans on non-EP jobs, and mandatory prompt-sync after paste edits. npm run prompts:eval gates CI.
How does Prompt Guard connect to the stack?
brand/creytix/prompt-pack/ is the Creytix umbrella SSOT. Rules in .cursor/rules/ mirror modules; Inspector verifies PG-AC on ship.
Operator entry vs this public page
Marketing summarizes guardrails. Operators run prompt compile and eval on ECP platform studio — planned until compiler phase 5 lands.
Key capabilities
Guardrail modules
Tone, safety, SEO storefront, and review gates in prompt-pack/.
Eval hooks
prompts:eval and audit:ai-prompts:ci before merge.
HF prompt-sync
Staging rebuild after any PROMPT_MODULES or job paste change.
Cross-brand protection
Non-EP Nano jobs include automotive brand ban blocks.
Related modules in the Creytix stack
Creytix Prompt Guard connects to other umbrella modules — explore adjacent lanes before you contact us.
Prompt pack SSOT
Prompt Guard reads the same AUTO_PROMPT_SYSTEM.json manifest as Forge — guardrail modules in brand/creytix/prompt-pack/ mirror .cursor/rules/ before customer-facing AI ships. Run npm run prompts:eval after compile; ECP prompt-eval tab for operator review.
- Manifest SSOT
- brand/creytix/AUTO_PROMPT_SYSTEM.json
- Example intake
- brand/forge/examples/auto-prompt-intake.creytix.example.json
- Prompt pack
- brand/creytix/prompt-pack/
- Regenerate
- npm run brand:forge:auto-prompt -- --intake brand/forge/examples/auto-prompt-intake.creytix.example.json
Platform scope & Creytix Connect
Fleet tracker platform.prompt-guard phase 5 — compileFromLockedRecipe and eval commands on ECP locally. Auto-run prompts:eval on compile fail is optional backlog — not a shipped customer API.
- Fleet tracker row
- platform.prompt-guard
- Connect registry
- forge.platform
- Fleet phase
- 5 · Beta (operator)
- ECP tab (dev)
- ?tab=prompt-eval
Registry SSOT: brand/creytix/CREYTIX_CONNECT_REGISTRY.json · Tracker: docs/fleet/FLEET_SERVICES_PHASE_TRACKER.json
One platform
The full Creytix suite — Forge, Studio, Design Labs, Inspector, Prompt Guard, and the IDE.
Six modules, one governed workspace — no separate logins, no per-tool billing.
See all modules
Explore the umbrella
See how modules connect
Creytix Prompt Guard is one lane in the Creytix stack. Browse related modules and Connect capabilities on the homepage — use Admin sign in in the header for the operator console.