mirror of
https://github.com/onestardao/WFGY.git
synced 2026-04-28 03:29:51 +00:00
22 KiB
22 KiB
🗣️ Tune Behavior in Natural Language
One of the strongest things about WFGY 5.0 Avatar is this:
you can change meaningful behavior without rebuilding the whole runtime by hand
That is not a small convenience feature.
It changes the user's relationship to the system.
Instead of thinking:
I need to rewrite everything
the user can think:
I know what feels wrong, and I can say it directly
That is a much stronger editing surface.
What This Actually Means
Natural-language tuning lets you make changes like:
- make this route less polished
- keep the warmth, but reduce the sugar
- make the output more grounded and less floaty
- keep the clarity, but reduce the sterile feeling
- make it stronger for public writing
- keep the companion feel, but give it more backbone
- preserve the personality, but make it easier to reuse across tasks
These are not vague wishes.
They are real behavior directions.
That is why this capability feels very different from ordinary persona tweaking.
Why This Feels Powerful
This capability lowers the cost of iteration.
You do not have to choose between:
- leaving the route untouched forever
- rewriting the entire file by hand
There is a middle zone:
- the route stays structured
- the behavior stays editable
- the changes stay understandable
- stronger variants can be kept later
That middle zone is where Avatar starts feeling like a real system.
Good Requests
Good tuning requests are:
- specific
- directional
- behavior-focused
- narrow enough to test clearly
Examples:
- make this route warmer, but not softer
- reduce polished AI smoothness
- keep the rational-friendly feel, but make it less distant
- increase grounding and reduce abstract float
- make the public-writing voice more alive without becoming slogan-heavy
- keep the companion energy, but reduce over-comforting language
These are strong because they point in a clear direction.
Weak Requests
Weak tuning requests are usually:
- too vague
- too overloaded
- too theatrical
- too broad to compare clearly
Examples:
- make it perfect
- make it insanely good at everything
- fix everything wrong with the avatar
- turn this into the ultimate personality
- make it 100 times smarter and more emotional
These requests create noise, not direction.
The Best Pattern
The best tuning pattern is simple:
- boot one route
- run one real task
- identify one main problem
- describe one adjustment in natural language
- update the behavior layer
- rerun the same task
- compare the difference
This is much better than changing five things at once.
Small directional edits teach you more.
They also produce stronger reusable builds later.
Why This Works So Well in Avatar
Natural-language tuning becomes much stronger when changes have somewhere meaningful to land.
In Avatar, that usually means the editable behavior layer represented by WFGY_BRAIN.
That matters because many systems let users ask for changes, but do not give those changes a stable place to accumulate.
Avatar is trying to avoid that.
The user says what they want.
The editable layer absorbs the direction.
The route stays legible enough to compare later.
That is a much better setup for real iteration.
What This Does Not Mean
Natural-language tuning does not mean:
- every layer should be casually rewritten
- the route no longer matters
- governance no longer matters
- structure no longer matters
- every change request is equally healthy
The point is not chaos.
The point is controlled editability.
That is why this capability matters so much.
Why Users Feel This Fast
A new user can feel this very quickly:
- boot one route
- run one real task
- say what feels wrong
- adjust in plain language
- rerun
- notice the shift
That is why this page exists.
This capability is one of the first places where Avatar stops feeling like a static file and starts feeling like a living runtime.
Where To Go Next
If you want the practical editable layer
Go to 🛠️ How to Use WFGY_BRAIN
If you want the workflow
Go to 🧭 Avatar Tuning Workflow
If you want the first-contact page
Go to ⚡ Start in 60 Seconds
If you want the highlights map
Go to ✨ Highlights Index
Quick Links
- 🏠 Avatar Home
- 🛠️ How to Use WFGY_BRAIN
- 🧭 Avatar Tuning Workflow
- ⚡ Start in 60 Seconds
- ✨ Highlights Index
- ⬆️ Back to WFGY Root
### 黑粉評分
* 舊版：**88 / 100**。主題清楚，但前半還在重複產品總論，像半個 capability page 半個產品介紹。
* 新版：**93 / 100**
* 還沒到 100 的原因：等 `how-to-use-wfgy-brain.md` 之後若也同步去重，這頁還能再更乾淨。
---
# 2. `Avatar/community/submit-your-avatar.md` 重構版
```md
<!--
AI_NOTE_START
Document role:
This page explains the submission path for future Avatar community entries.
What this page is for:
1. Explain what kind of avatar is worth submitting.
2. Show the basic preparation path before submission.
3. Keep this page focused on submission flow, not the whole ecosystem vision.
Important boundary:
This page explains how to prepare for submission.
It is not the final format spec, not the final PR guide, and not the full Awesome Avatar gallery page.
AI_NOTE_END
-->
# 🌟 Submit Your Avatar
This page explains the future submission path for **WFGY 5.0 Avatar** community entries.
The key idea is simple:
**do not submit random experiments**
A future submission should be a real avatar branch.
That means it should be:
- named clearly
- distinct enough to recognize
- reusable enough to matter
- demonstrated through sample writing
- understandable to someone other than the creator
That is the standard direction.
---
## What Kind of Avatar Should Be Submitted
A future submission should usually have:
- a clear avatar name
- a recognizable intended personality
- a real use direction
- enough tuning to feel distinct
- enough stability to reuse
- sample writing that proves the route is real
It does not need to be perfect.
But it does need to feel like a real branch, not a lucky accident.
---
## A Good Preparation Path
A healthy submission path usually looks like this:
1. start from `avatar.txt`
2. boot one route
3. shape the route through `WFGY_BRAIN`
4. test with real tasks
5. save stronger variants
6. choose one branch worth keeping
7. prepare sample writing
8. later follow the submission format and PR path
Submission is not the first step.
It is a later step.
The route should become real first.
---
## What You Will Likely Need
The final format page is separate.
But at a high level, a future submission will likely need:
- avatar name
- base route
- intended personality
- intended use cases
- sample writing
- avatar image
- optional multilingual notes
- known limits if any
This is enough to make the route legible.
That is the goal.
---
## Why Sample Writing Matters
A strong submission should not only describe the avatar.
It should also show the avatar.
That is why sample writing matters.
The sample should help readers feel:
- the tone
- the rhythm
- the route pressure
- the personality shape
- the difference from a generic assistant
A good sample is better than a long self-description.
---
## Why Reusable Builds Matter Before Submission
The best submissions usually come from reusable builds.
That matters because reusable builds are easier to:
- name honestly
- explain clearly
- compare against parent routes
- branch from later
- share without confusion
A random experiment may be fun.
A submission should be stronger than fun alone.
---
## What the Community Layer Is Trying to Avoid
The future community layer is not trying to become:
- a random file dump
- a prompt graveyard
- a pile of unsorted personalities
- a noise-first gallery
The healthier direction is:
- clearer names
- clearer route identity
- visible examples
- honest limits
- stronger entries rising more easily
That is why submission discipline matters.
---
## About the Awesome Avatar List
The future **Awesome Avatar List** is the public gallery direction for notable branches.
Right now, that layer is still:
**WORK IN PROGRESS**
That is intentional.
It is better to grow that gallery carefully than to fake completeness too early.
For the gallery-facing direction, go to [⭐ Awesome Avatar List](./awesome-avatar-list.md).
---
## What You Can Do Right Now
Even before the final submission path is fully frozen, you can already:
- build a custom avatar branch
- give it a real name
- test it with real tasks
- save stronger variants
- write short sample outputs
- note what makes it distinct
- prepare it for a future format page
That is already enough to start cleanly.
---
## Where To Go Next
### If you want the future gallery direction
Go to [⭐ Awesome Avatar List](./awesome-avatar-list.md)
### If you want the entry format
Go to [🧾 Avatar Submission Format](./avatar-submission-format.md)
### If you want the custom-avatar horizon
Go to [🌱 One Runtime, Many Avatars](../highlights/one-runtime-many-avatars.md)
### If you want the tuning workflow
Go to [🧭 Avatar Tuning Workflow](../docs/avatar-tuning-workflow.md)
---
## Quick Links
- [🏠 Avatar Home](../README.md)
- [⭐ Awesome Avatar List](./awesome-avatar-list.md)
- [🧾 Avatar Submission Format](./avatar-submission-format.md)
- [🌱 One Runtime, Many Avatars](../highlights/one-runtime-many-avatars.md)
- [🧭 Avatar Tuning Workflow](../docs/avatar-tuning-workflow.md)
- [⬆️ Back to WFGY Root](../../README.md)
黑粉評分
- 舊版：85 / 100。方向對，但散文感偏多，submission flow 與 ecosystem vision 混在一起。
- 新版：92 / 100
- 還沒到 100 的原因：等
avatar-submission-format.md和pr-template-guide.md實體落地後，這頁可以再更短更狠。
3. Avatar/community/awesome-avatar-list.md 重構版
<!--
AI_NOTE_START
Document role:
This page introduces the future Awesome Avatar List for WFGY 5.0 Avatar.
What this page is for:
1. Show what kind of public avatar gallery is being imagined.
2. Make the future community layer feel alive and legible.
3. Keep the page fun, light, and clearly marked as work in progress.
Important boundary:
This page is a gallery-direction page.
It is not the final submission rules page and not the final format spec.
AI_NOTE_END
-->
# ⭐ Awesome Avatar List
**WORK IN PROGRESS**
The **Awesome Avatar List** is the future public gallery for stronger avatar branches built on top of **WFGY 5.0 Avatar**.
This page is not the final gallery yet.
It is the direction page.
And the direction is simple:
**Avatar should not stop at official routes**
Over time, there should be many avatars.
Different names.
Different vibes.
Different writing habits.
Different public voices.
Different kinds of presence.
Not random chaos.
Real avatars.
---
## What This List Is Trying to Become
The future gallery should help people discover avatars that feel:
- distinct
- memorable
- usable
- expressive
- legible at a glance
The goal is not to create a giant dump of personality files.
The goal is to surface branches that actually show:
- who they are
- how they speak
- what they were tuned toward
- what kind of route they carry
- why they are worth noticing
That is the spirit of the list.
---
## What a Future Entry Will Likely Show
A stronger future avatar entry will probably include:
- avatar name
- a short natural-language personality description
- a note on what was tuned
- sample writing
- an avatar image or profile picture
- optional multilingual notes
- author or branch credit
The point is not bureaucracy.
The point is legibility.
Someone should be able to understand an entry quickly.
---
## Sample Writing Matters
A future entry should not only describe itself.
It should also show itself.
That means sample writing will matter.
A good sample should help readers feel:
- the opening
- the tone
- the rhythm
- the emotional pressure
- the route identity
That is much more interesting than a raw config dump.
---
## Avatar Images Matter Too
Yes, the visual layer should be part of the fun.
A future entry will be stronger if it includes:
- an avatar portrait
- a profile-style image
- a symbolic identity
- or another clear visual that makes the route feel more present
If an entry does not include an image, the current direction may allow the author or maintainer to help create one later.
That part is still:
**WORK IN PROGRESS**
But the spirit is already clear.
This should feel like a gallery of personalities, not a text graveyard.
---
## Recommended Way to Play
One of the best ways to test an avatar is actually very simple:
**put the avatar image on your social profile**
**use the avatar name**
**speak in that route's voice for a while**
That is one of the clearest ways to tell whether the branch really feels distinct.
If it can survive:
- profile presentation
- repeated short posts
- public replies
- small writing samples
then it starts feeling much more real.
That is where the system becomes more fun.
And more alive.
---
## Yes, Some Avatars Can Start Silly
Not every avatar needs to begin as a polished masterpiece.
Some of the strongest future branches may begin from something intentionally simple, awkward, or even a little stupid.
That is part of the charm.
A route like `YOUR_AVATAR_NAME` is allowed to begin as:
- blank
- clueless
- funny
- under-equipped
- obviously unfinished
Then later become something real through:
- naming
- tuning
- writing
- repetition
- branch discipline
That is a healthy direction.
---
## Current Status
Right now, this page is still:
**WORK IN PROGRESS**
That means:
- the final gallery is not built yet
- the final curation rules are not frozen yet
- the final submission flow is not fully closed yet
That is fine.
This page exists to make the future gallery feel visible before it is fully populated.
That is enough for now.
---
## Where To Go Next
### If you want the submission path
Go to [🌟 Submit Your Avatar](./submit-your-avatar.md)
### If you want the entry format
Go to [🧾 Avatar Submission Format](./avatar-submission-format.md)
### If you want the custom-avatar horizon
Go to [🌱 One Runtime, Many Avatars](../highlights/one-runtime-many-avatars.md)
### If you want the workflow path
Go to [🧭 Avatar Tuning Workflow](../docs/avatar-tuning-workflow.md)
---
## Quick Links
- [🏠 Avatar Home](../README.md)
- [🌟 Submit Your Avatar](./submit-your-avatar.md)
- [🧾 Avatar Submission Format](./avatar-submission-format.md)
- [🌱 One Runtime, Many Avatars](../highlights/one-runtime-many-avatars.md)
- [🧭 Avatar Tuning Workflow](../docs/avatar-tuning-workflow.md)
- [⬆️ Back to WFGY Root](../../README.md)
黑粉評分
- 舊版：87 / 100。方向有趣，但 submission rules、gallery vision、fun vibe 混在一起。
- 新版：93 / 100
- 還沒到 100 的原因：等你真的開始放第一批示範 avatar 之後，這頁會更活。
4. Avatar/community/avatar-submission-format.md 重構版
<!--
AI_NOTE_START
Document role:
This page defines the intended submission format for future Avatar entries.
What this page is for:
1. Make future avatar entries easier to read, compare, and review.
2. Help contributors present avatars as real branches rather than random files.
3. Keep the page focused on format, not on ecosystem storytelling.
Important boundary:
This page defines structure.
It does not guarantee that every formatted submission is worth accepting.
AI_NOTE_END
-->
# 🧾 Avatar Submission Format
This page defines the intended structure for a future avatar submission related to **WFGY 5.0 Avatar**.
The goal is simple:
**make submissions readable**
**make submissions comparable**
**make submissions reviewable**
A submission should not be only:
- a file
- a cool name
- a vague personality claim
- a random screenshot
- a pile of unexplained edits
A stronger submission should feel like a real avatar entry.
---
## Core Entry Structure
A future submission should usually include the following parts.
### 1. Avatar Name
A clear public name.
Good names feel like real branches, not temporary accidents.
---
### 2. Base Route
The route this avatar grew from.
Examples:
- `hello psbigbig`
- `hello minips`
- `hello YOUR_AVATAR_NAME`
This helps people understand lineage.
---
### 3. Intended Personality
A short natural-language description of the avatar's feel.
Examples:
- calm, grounded, lightly witty
- warm, companion-forward, soft but not sugary
- awkward, curious, low-pressure, beginner-like
- clear, analytical, emotionally restrained
Keep this section concise.
---
### 4. Intended Use Cases
A short list of what the avatar is good for.
Examples:
- public writing
- reflective conversation
- customer-facing communication
- grounded analysis
- companion response
This section keeps the entry practical.
---
### 5. What Was Tuned
A short note on what was adjusted.
Examples:
- reduced polish and increased grounding
- preserved warmth but reduced sugar
- increased public-writing force
- lowered abstraction drift
- made the route easier to reuse
This makes the shaping direction visible.
---
### 6. WFGY_BRAIN Direction Notes
A short high-level note about the tuning direction.
This section is not for dumping every internal detail.
It is for making the route legible.
---
### 7. Sample Writing
One or more short example outputs that demonstrate the route.
This is one of the most important sections.
The sample should help readers feel:
- the tone
- the rhythm
- the personality shape
- the difference from a generic assistant
---
### 8. Avatar Image
A portrait, profile-style image, or another visual identity.
This helps the entry feel more like a character card and less like a raw config file.
---
### 9. Optional Multilingual Notes
If relevant, include short notes like:
- tested in English and Traditional Chinese
- stronger in Chinese public writing than in English chat
- still drifts too much in Japanese
This helps people read multilingual maturity honestly.
---
### 10. Known Limits
A short section for what the avatar still does poorly.
Examples:
- still too soft in long emotional exchanges
- public writing is stronger than casual chat
- multilingual branch still unstable in Japanese
- can become too polished under some tasks
Known limits increase trust.
---
## Suggested Submission Template
```md
# AVATAR ENTRY
## Avatar Name
<name>
## Base Route
<hello psbigbig / hello minips / hello YOUR_AVATAR_NAME / later route>
## Intended Personality
<short natural-language personality description>
## Intended Use Cases
- <use case 1>
- <use case 2>
- <use case 3>
## What Was Tuned
- <tuning direction 1>
- <tuning direction 2>
- <tuning direction 3>
## WFGY_BRAIN Direction Notes
<short note about the overall shaping direction>
## Sample Writing
<one or more short sample passages>
## Avatar Image
<image link, file reference, or note>
## Optional Multilingual Notes
<optional>
## Known Limits
- <limit 1>
- <limit 2>
This template is intentionally simple.
It should be strong enough to make entries readable without turning the process into bureaucracy.
About the Image
The image is not only decoration.
It helps the avatar become socially legible.
Recommended direction:
- one clear image
- one readable profile identity
- one face, symbol, or route-matching visual
If the submitter does not provide one, later maintainer-side help may be possible.
That part is still evolving.
About the Sample
A good sample should be:
- distinct
- readable quickly
- honest
- route-revealing
- not only hype
A sample is not an ornament.
It is evidence of behavior.
What This Page Does Not Guarantee
This page helps future submitters prepare better.
It does not guarantee:
- that every formatted submission will be accepted
- that every avatar with a good image is strong
- that sample writing alone proves long-term reuse
- that the final review criteria are already frozen forever
Format helps.
But format is not quality by itself.
Where To Go Next
If you want the gallery direction
Go to ⭐ Awesome Avatar List
If you want the submission overview
Go to 🌟 Submit Your Avatar
If you want the custom-avatar horizon
Go to 🌱 One Runtime, Many Avatars
If you want the workflow path
Go to 🧭 Avatar Tuning Workflow