Add AI Workflow guide - #11
Conversation
| The tools fall into four groups. You rarely call them yourself - the agent does, | ||
| while it works - but it is worth knowing what is available, because that tells you | ||
| what you can reasonably ask for. |
There was a problem hiding this comment.
IMO this sentence needs a rewrite. It flows a bit weird, especially the "the agent does, while it works - but it is worth knowing..."
| :::caution[Gameface Player only] | ||
| The server refuses to launch or connect to anything that is not Gameface Player. | ||
| Every connection is verified over CDP - `navigator.userAgent` must contain |
There was a problem hiding this comment.
I thought it can work directly with the game as well. If it really does not currently work with a game, we should put a sentence in this aside to state it and make it 100% clear
| ## Checking it works | ||
|
|
||
| Ask your agent to launch the Player and screenshot your current view. If it comes |
There was a problem hiding this comment.
What should they do if it doesn't work ? Should we add a "Troubleshooting" section after this one, for people that can't run it for whatever reason?
| The six `09_*` files are the Gameface UI component library, split by category, and | ||
| they are the ones that pay off fastest in day-to-day work: an agent that knows | ||
| `Slider`, `Navigation` and `ScrollView` already exist will use them instead of | ||
| building its own out of divs. |
There was a problem hiding this comment.
I think this will sit better in an aside (note or caution). And also we should emphasize that we are talking strictly in a "Gameface UI" project.. not in any other. Just to make it 100% clear for people that are reading but aren't as acquainted with our tools and gf ui.
| permanently in its unchecked state. | ||
|
|
||
| :::caution[The ruleset is a snapshot, not a contract] | ||
| It reflects what feature detection found on the versions it was run against, and |
There was a problem hiding this comment.
The heading reads a bit weird imo
| <Link href="https://frontend-tools.coherent-labs.com/eslint-plugin-gameface/getting-started/">eslint-plugin-gameface</Link> | ||
| flags unsupported patterns and data-binding mistakes across CSS, SCSS, HTML, | ||
| JSX/TSX and JavaScript. It ships pre-wired in the Gameface UI boilerplate and in | ||
| every framework template. |
There was a problem hiding this comment.
| every framework template. | |
| every <Link href="/planning-and-setup/alternative-frameworks/overview/">framework template.</Link> |
| The [Conductor skill](/building-with-ai/the-conductor-skill/) runs this battery | ||
| automatically as its validation stage. Without the skill, ask for it explicitly. |
There was a problem hiding this comment.
| The [Conductor skill](/building-with-ai/the-conductor-skill/) runs this battery | |
| automatically as its validation stage. Without the skill, ask for it explicitly. | |
| The [Conductor skill](/building-with-ai/the-conductor-skill/) runs this | |
| automatically as its validation stage. Without the skill, ask for it explicitly. |
battery? :D
| Both were decided before a line was written. Discovering either one in week three | ||
| is a rewrite. |
There was a problem hiding this comment.
The "week" jargon sounds a bit off here ;d
Can we emphasize on project longevity in a different way ?
|
|
||
| Written before the first chart, not measured afterwards: | ||
|
|
||
| > Target ≤ 200 marks; warn in dev above 500. Exactly one tween signal write per |
There was a problem hiding this comment.
What is a mark?
| > measured off the DOM. The chart emits its own geometry, so the length is | ||
| > *derived*. | ||
|
|
||
| An earlier decision, recorded with its reasoning, was revisited months later and |
There was a problem hiding this comment.
Wasn't it made in a week or so why "months later" ?
|
|
||
| ## Layer 1 - Lint the source | ||
|
|
||
| The cheapest check, and it needs no agent involvement. |
There was a problem hiding this comment.
In fact if you have eslint plugin setup in your project it is possible Claude or other AI to try to run and check for mistakes. Maybe, describe this possibility here.
| * **Visual coherence** - does this belong to the same interface as the screen next | ||
| to it? See [Design first](/building-with-ai/design-first/). | ||
| * **Hierarchy** - does the most important thing read as the most important thing? | ||
| * **Feel** - transitions, timing, feedback on press. An agent will add a 300ms |
There was a problem hiding this comment.
"An agent will add a 300ms ease to everything and call it polish." Will this happen every time? I don't understand the context of this sentence.
|
|
||
| This is the layer people skip, and it is the one that caught the worst bug we hit. | ||
|
|
||
| While building the Chart component, an overlay element that should have covered the |
There was a problem hiding this comment.
Who has built the Chart component? Why we mention Chart component out of nowhere and out of context :D
| :::caution[An internal experiment, and still in development] | ||
| The Chart family is being developed for the Gameface UI library and is not | ||
| released. This article is about the working method, not an announcement. See the | ||
| <Link href="https://gameface-ui.coherent-labs.com/components/">component library</Link> | ||
| for what is actually available today. | ||
| ::: |
There was a problem hiding this comment.
Are we sure we want to mention that it is not released?
3 participants
No description provided.