docs(landing): mention v0.3.0 current-gen calibration and link router example#4
Merged
docs(landing): mention v0.3.0 current-gen calibration and link router example#4
Conversation
… example Adds a short "Calibrated for current-generation models" section to the landing page describing v0.3.0's model-awareness work (outcome-oriented tool guidance, effort-awareness, session memory, parallel dispatch, vision-as-primary-evidence) and pointing at the optional router CLAUDE.md example under docs/examples/. Also refreshes the "Future development" bullets: the roadmap now reflects v0.3.0 as shipped, notes the translation issue is still open, and re-slots sub-agent decomposition to a later release (the v0.3.0 copy called it out as "v0.3.0" which is now misleading). Pure copy/structural update — no JS or CSS changes, OG cards and canonical URL untouched. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Updates the Newton landing page copy to reflect v0.3.0 “current-generation model” calibration work and to refresh the “Future development” section to post‑v0.3.0 planning.
Changes:
- Adds a new “Calibrated for current-generation models” section describing v0.3.0 model-awareness outcomes and linking to the optional router CLAUDE.md example.
- Updates “Future development” to “Planned after v0.3.0”, adjusts the translation bullet to include the landing page, and moves sub-agent decomposition to a later release.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| <p>Newton also operationalises reuse-before-rebuild, current-sources research, surgical editing, and handoff-when-scope-outgrows-the-chat as explicit sub-routines the agent runs, not as vibes. That's what makes it a <em>skill</em> rather than a prompt: the agent loads the methodology once and applies it consistently, with visible reuse-check reports and dated sources, rather than re-deriving the disposition from your tone every turn.</p> | ||
|
|
||
| <h2>Calibrated for current-generation models</h2> | ||
| <p>Newton is model-agnostic by design — the same methodology runs on Opus, Sonnet, and Haiku — but v0.3.0 is tuned so current-generation capabilities (adaptive thinking, implicit tool detection, session memory, parallel execution, high-resolution vision) are leveraged rather than fought. Tool guidance is outcome-oriented instead of prescriptive, independent sub-tasks parallelise, multi-turn sessions can use file-system memory, and visual input is treated as primary evidence. Older models still get the full Newton experience with graceful degradation — no feature relies on a specific model.</p> |
There was a problem hiding this comment.
The landing page says multi-turn sessions can use file-system memory, but this capability is environment-dependent. To avoid implying it works everywhere, consider adding the same qualifier used in the skill/CHANGELOG (e.g., “when available”).
Suggested change
| <p>Newton is model-agnostic by design — the same methodology runs on Opus, Sonnet, and Haiku — but v0.3.0 is tuned so current-generation capabilities (adaptive thinking, implicit tool detection, session memory, parallel execution, high-resolution vision) are leveraged rather than fought. Tool guidance is outcome-oriented instead of prescriptive, independent sub-tasks parallelise, multi-turn sessions can use file-system memory, and visual input is treated as primary evidence. Older models still get the full Newton experience with graceful degradation — no feature relies on a specific model.</p> | |
| <p>Newton is model-agnostic by design — the same methodology runs on Opus, Sonnet, and Haiku — but v0.3.0 is tuned so current-generation capabilities (adaptive thinking, implicit tool detection, session memory, parallel execution, high-resolution vision) are leveraged rather than fought. Tool guidance is outcome-oriented instead of prescriptive, independent sub-tasks parallelise, multi-turn sessions can use file-system memory when available, and visual input is treated as primary evidence. Older models still get the full Newton experience with graceful degradation — no feature relies on a specific model.</p> |
|
|
||
| <h2>Calibrated for current-generation models</h2> | ||
| <p>Newton is model-agnostic by design — the same methodology runs on Opus, Sonnet, and Haiku — but v0.3.0 is tuned so current-generation capabilities (adaptive thinking, implicit tool detection, session memory, parallel execution, high-resolution vision) are leveraged rather than fought. Tool guidance is outcome-oriented instead of prescriptive, independent sub-tasks parallelise, multi-turn sessions can use file-system memory, and visual input is treated as primary evidence. Older models still get the full Newton experience with graceful degradation — no feature relies on a specific model.</p> | ||
| <p>Want model-specific behaviour layered on top of <em>every</em> skill, not just Newton? v0.3.0 ships an optional <a href="https://github.com/PBNZ/newton-skill/blob/main/docs/examples/router-claude-md.md">router CLAUDE.md example</a> you can drop into your own <code>~/.claude/CLAUDE.md</code>. It's opt-in — the plugin does not install it for you.</p> |
There was a problem hiding this comment.
This paragraph is phrased as a v0.3.0-specific claim, but the link targets blob/main, which may drift from the v0.3.0 content over time. To keep the landing page consistent with the version referenced, link to the v0.3.0 tag/relnotes (or otherwise a version-pinned URL).
Suggested change
| <p>Want model-specific behaviour layered on top of <em>every</em> skill, not just Newton? v0.3.0 ships an optional <a href="https://github.com/PBNZ/newton-skill/blob/main/docs/examples/router-claude-md.md">router CLAUDE.md example</a> you can drop into your own <code>~/.claude/CLAUDE.md</code>. It's opt-in — the plugin does not install it for you.</p> | |
| <p>Want model-specific behaviour layered on top of <em>every</em> skill, not just Newton? v0.3.0 ships an optional <a href="https://github.com/PBNZ/newton-skill/blob/v0.3.0/docs/examples/router-claude-md.md">router CLAUDE.md example</a> you can drop into your own <code>~/.claude/CLAUDE.md</code>. It's opt-in — the plugin does not install it for you.</p> |
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.
Summary
Test plan
🤖 Generated with Claude Code
Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com