v1.1.0 #1
diShine-digital-agency
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
[1.1.0] — 2026-04-18
Context Efficiency Release. SHINE 1.0 auto-enabled all 16 plugins on install, pushing baseline context to ~95k — combined with user-configured MCPs and a large
CLAUDE.md, many sessions crossed Claude Code's effective token budget and became unusable. 1.1 introduces context profiles, slims the always-loaded instruction file, and makes plugin activation opt-in and switchable.Added
shine/profiles/*.json) — 6 curated bundles declaringenabledPlugins+disabledMcpjsonServers+estimatedContextTokens:minimal(~15k) — no plugins. New default.writing(~20k) — context7.outbound(~35k) — context7 + prospecting MCPs kept (Apollo, Gmail, CommonRoom).seo(~40k) — context7 + Ahrefs kept.dev(~70k) — full engineering stack (serena, LSPs, playwright, supabase, code-simplifier, superpowers).full(~95k) — all 16 plugins (parity with previous default).shine-profile.cjs— Node CLI that atomically rewrites~/.claude/settings.json'senabledPluginsanddisabledMcpjsonServersfrom a selected profile. Commands:list,show <name>,activate <name>,current. Atomic viafs.renameSyncfrom.tmp.shinebash shim (shine/bin/shine) — unified CLI dispatching toshine-profile.cjs(activate|list|show|current|profile) andshine-tools.cjs(doctor|onboard|help|index-skills|--version). Add~/.claude/shine/binto PATH to callshinedirectly.install.sh --profile=<name>— CLI flag and interactive picker (6 options, defaultminimal). Installer now parses the selected profile JSON vianodeto determine whichplugin@marketplaceentries to install — instead of the fixed 16-plugin loop.shine/references/integrations-map.md— full task-to-integration routing (wasCLAUDE.md§§1-14). Loaded on demand.shine/references/mcp-capability-map.md— BYO MCP inventory (wasCLAUDE.md§15).shine/references/agency-playbook.md— tone switching, GDPR guard, proposal assembly, lead enrichment (wasCLAUDE.md§§17-20).shine/references/tool-tiers.md— free-first fallback rule (wasCLAUDE.md§21).shine/references/decision-rules.md— full 29-rule matrix (wasCLAUDE.mdDecision Rules).Changed
settings.template.json— the key fix.enabledPluginsnow defaults to{}(was 16 entries = true),alwaysThinkingEnabledflipped tofalse,disabledMcpjsonServersadded with explanatory comment. Baseline context drops from ~95k to ~15k.CLAUDE.md— split from 31,798 bytes to ~6,300 bytes (80% reduction). Slim core retains identity, auto-use principle, top-level decision rules, and the full §16 Factual / RAG Discipline table (unchanged, MANDATORY). Detailed routing, MCP maps, agency playbooks, and the 29-rule matrix moved toshine/references/*.mdfor on-demand loading.install.sh— profile-aware install flow. Copiesshine-profile.cjs, theshineshim, andshine/profiles/*.json; runsshine-profile activateat end of install to syncsettings.jsonwith the chosen profile. Help text and next-steps output document theshine activatecommand.shine/VERSION— bumped1.0.3→1.1.0.README.md— new "Context profiles" subsection under Quick install,--profileflag documented in flags table, plugin section now describes profile-gated install.QUICKSTART.md— install step renumbered and extended with profile picker, new step 3 "Switch context profile", troubleshooting rows for heavy-context symptoms and missing MCPs.Fixed
hooks/shine-check-update.js— corrected hardcoded repo slug from the stalediShine-digital-agency/shine-claude-code-frameworktodiShine-digital-agency/SHINE-Code-System. Previously every update-check silently 404'd.Migration from 1.0.x
SHINE-Code-Systemand re-run./install.sh— your existing~/.claude/is backed up atomically before any change.minimalfor marketing work,devfor coding,outboundfor prospecting).shine activate <name>and restart Claude Code.memory/,MEMORY.md, and custom skills/agents are preserved.Why this matters
The SHINE 1.0 default combined with a typical user's claude.ai MCP server set easily crossed 200k tokens of context before the first prompt. On Haiku 4.5 sessions with a 200k window, this meant repeated compaction, missing tool schemas, and degraded answer quality. The 1.1 profile system restores headroom: a
minimalSHINE install + 5 user MCPs now sits comfortably under 40k, leaving 160k+ for actual work.This discussion was created from the release v1.1.0.
Beta Was this translation helpful? Give feedback.
All reactions