Repository navigation
Add: surface-scoped-system-prompt - #157
Merged
nibzard merged 1 commit intoOct 14, 2026
Merged
Conversation
|
@xizhuomengcontin is attempting to deploy a commit to the nkkko's projects Team on Vercel. A member of the Team first needs to authorize it. |
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
nibzard
force-pushed
the
add-surface-scoped-system-prompt
branch
from
October 14, 2026 22:28
fe1f35a to
a72fe87
Compare
Owner
|
Thanks — merged with a small maintenance pass: rebased onto the current 🤖 Generated with Claude Code |
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.
Add: surface-scoped-system-prompt— one pattern,Context & Memory.The pattern. A harness ships a separate system prompt per invocation surface — interactive, headless, declared task mode — and selects it at launch, instead of sending one prompt everywhere and asking the model to work out which situation it is in.
Why it is not a repeat of
agent-modes-by-model-personality. That pattern makes the model the variable: different models, different modes. This one is the opposite finding, and I have the negative control for it. Seven models across six labs driven through the same MiniMax Code surface produced prompts identical line for line except- Model: <id>; change the surface instead and you get three different documents. The two patterns compose, and I have listed the other one underrelated.Both implementations are checkable.
assets/agents/_v2/*/SYSTEM.md.hbsand picks one per--prompt-mode(tui,coding,work).codingswaps theDeliverable Filessection forMedia Output;workadds anArtifact Completion Contract. Tool schema identical across all three.cc_entrypoint=cliversussdk-cli— and both prompt and tool set change with it. The identity line is rewritten from "You are Claude Code, Anthropic's official CLI for Claude" to "You are a Claude agent, built on Anthropic's Claude Agent SDK", and the tool count drops.Disclosure. The character and tool counts in the Evidence section were measured from wire captures in an archive my team maintains, which is why it appears in
authorsand is labelled in References as the measurement source rather than an implementation. The primarysourceis MiniMax's own repository, not ours, and the pattern stands without our archive — the MiniMax templates are readable in their repo and the Claude Code entrypoint header is visible to anyone proxying their own session.Checks.
bun run validate:patternsandbun run validate:patterns:contentboth pass on this file (the one remaining content error in the tree is pre-existing, incross-agent-lesson-sharing.md— missing References).bun run build:datarun and its output included. I revertedapps/web/src/data/github-stars.json, since that diff was only the live star count refreshing and had nothing to do with this pattern.🤖 Generated with Claude Code