Repository navigation
Docs: explain native intent styling with executable examples - #138
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The guide incorrectly described intent trees as unable to carry styling, encouraging unnecessary HTML conversion. It also lacked current alignment and headerless-table examples and treated one image/text mapping as universal. Closes #130.
Solution
Explain explicit native attributes versus interpretation of authored HTML/CSS. Add an executable styling and headerless-table example, plus a short sequential realize snippet using the existing API. Keep generic structural defaults while allowing verified theme layout contracts.
Diff
+109 / −9 across five files.
Testing & verification
Reviewed revision:
0590aa5b0d0f33952cd4d8d226e92b86c7576d76· Environment: Node 24.18.0, macOS arm64.npx vitest run dev/test/skill.test.ts dev/test/engine-skill.test.ts dev/test/intent.test.ts: 44 passed, including the documented JSON through realize and parsed-attribute assertions.npm run typecheck,git diff --check, andnpm run build: passed.node dist/cli.js skill --install --dir <fresh-temp-directory>: installed both edited references; commands remain version-pinned.npm run benchbefore and after the intent fixes: all 63 SCORE values unchanged.Not verified: new model behavior or target-theme/editor presentation. No model benchmark ran; the guide distinguishes pinned headless support from destination proof.
Risk / rollout
Guidance changes the recommended authoring route for explicit native styles. Generic structure and visible-container defaults remain; no runtime feature, batch runner, or expected benchmark tree is added.
Detection: executable guide regression and skill contracts. Rollback: revert this documentation and its example test.