Prism is a small YAML block for tone, persona, and boundaries for AI. In a Fragment it usually lives inside a fenced block like yaml block:prism. On this page you can switch between profiles and see how the same note and request would be answered as a neutral model, a study partner, a direct editor, or a gentle coach.
This is a simulated demo. Replies are pre-rendered, but they show the qualitative difference Prism is designed to make when Fragment sends a page plus a block:prism YAML profile to an AI model.
1. The note and request
The note and the request stay the same. Only the Prism profile changes.
Example requestFragment + AI
You’re drafting a short internal note about burnout for your team.
Rewrite it so that:
- it is easy to read,
- it does not blame individuals,
- and it offers 2–3 concrete next steps for the team.
2. Choose a Prism profile
Each profile is a small YAML block ( yaml block:prism ) that says “please answer like this kind of helper.”
3. The Prism YAML for this profile
This is the kind of block:prism snippet you would store inside a Fragment.
Neutral defaultBaseline
# No Prism block
# The model sees only:
# - your note (Markdown)
# - your request
#
# Behaviour is:
# - neutral tone
# - no shared boundaries
# - generic but usually correct
The schema is intentionally small so it feels like writing a short profile, not configuring a system.
4. How the reply feels with this Prism
Same note, same request — only the profile changes.
• Straightforward and impersonal.
• Optimised for generic correctness.
• No shared sense of your situation.
AI replySimulated · demo only
Here's a clearer version of your note about burnout:
---
Burnout is not just “being tired.” It usually means:
- long-term stress,
- little control over what to work on,
- and a feeling that effort doesn't change anything.
To reduce burnout in this team, we could:
1. Make workload visible, not hidden in calendars.
2. Protect focus time instead of filling every gap with meetings.
3. Make it normal to say “this is too much right now” without penalty.
You can use this as a starting outline for your team message.
In Fragment, you can reuse a few Prism profiles across many notes: for example “work editor”, “study partner”, or “family mode”. The note stays yours — Prism just shapes how AI sits beside you.
What Prism does in a real Fragment
In Fragment, a single page (a Fragment) can contain:
• your main note, written in Markdown
• a small yaml block:prism with tone, persona, and boundaries
• optional config or diagram blocks next to the text
When you ask AI to help with that page, Fragment sends the note together with the block:prism YAML. The model reads the content through that “lens”, instead of acting like a blank, context-free assistant.
Who this demo is for
This demo is for anyone who wants AI to feel more consistent and less random:
• people building repeatable ways of working with AI
• teams who want “house styles” for feedback and reviews
• individuals who need different modes: work, study, care, etc.
If you like how these profiles feel, the next step is to copy and adapt one into your own Fragment and slowly build a small library of Prism profiles that match your real work.
Bring Prism into your own notes
Take a profile from this page, tweak the YAML inside the block:prism snippet, and drop it into a Fragment. Over time you can keep a few favourites — for example “work editor”, “study partner”, “gentle coach” — and reuse them instead of rewriting prompts.
気に入ったプロフィールがあれば、block:prism の YAML を少しだけ自分用に書き換えて、 実際の Fragment に貼り付けてみてください。 「仕事用の編集者」「学習モードのパートナー」「やさしいコーチ」など、いくつかお気に入りの Prism を育てておくと、毎回プロンプトを書く必要がなくなります。