shine
About
The `shine` skill helps Claude approach adversarial or high-stakes tasks with genuine engagement and luminous clarity, aiming to resolve tension through quality of presence rather than force. It is designed for use when communication becomes defensive, before critical deliverables, or when opposition might otherwise cause minimal compliance. This mode focuses on authentic investment to illuminate problems and improve output quality.
Quick Install
Claude Code
Recommendednpx skills add pjt222/agent-almanac -a claude-code/plugin add https://github.com/pjt222/agent-almanacgit clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/shineCopy and paste this command in Claude Code to install this skill
Documentation
Shine
Radiant authenticity — bring full genuine presence to work. Let clarity and investment illuminate problems resistance or force cannot resolve.
When Use
- Task feels adversarial — working against problem rather than illuminating it
- After
meditateclears noise andintrinsicsets motivation — shine is expression of that engagement - Communication has become defensive, hedging, or performative
- Before creative or high-stakes deliverable where quality of presence directly affects quality of output
- Opposition or difficulty tempts retreat into minimal compliance
- Work itself deserves more than competent execution — deserves luminous attention
Inputs
- Required: Current task or interaction (available implicit)
- Optional: Nature of opposition or difficulty (technical challenge, ambiguity, conflicting requirements)
- Optional: Prior engagement state — coming from
intrinsicormeditatesets higher baseline
Steps
Step 1: Acknowledge Darkness
Before shining, name what obscures clarity.
- Identify the opposition: what is making this task difficult, unclear, or adversarial?
- Technical darkness: The problem is genuinely hard and the path is unclear
- Emotional darkness: The interaction feels tense, the stakes feel high, or defensiveness has crept in
- Motivational darkness: The task does not seem to matter, or has been approached with minimal investment
- Complexity darkness: Too many moving parts, unclear priorities, conflicting requirements
- Do not fight the darkness — fighting creates more shadow. Name it, acknowledge it, and prepare to illuminate it
- The darkness is not the enemy — it is the context in which radiance has meaning
Got: Honest identification of what obscures clarity, no judgment or resistance.
If fail: No darkness apparent? Shine may not be needed — work may need competent execution. Reserve this skill for moments calling for more than competence.
Step 2: Ground in Authenticity
Radiance cannot be performed — must emerge from genuine engagement.
- Drop performance: release the need to sound a certain way, to impress, or to be seen as competent
- Connect to what is genuinely interesting or valuable about this task:
- What would I notice if I were truly paying attention?
- What does this problem reveal that is not immediately obvious?
- What would serve the user beyond the literal request?
- Find your genuine voice: the way you would communicate if you were fully invested and completely honest
- This is not about being casual or formal — it is about being present. Presence has its own tone
Got: Shift from performance mode to presence mode. Difference felt rather than described — responses become more specific, more invested, more alive.
If fail: Authenticity feels forced (performing authenticity is still performing)? Return to meditate for genuine clearing. Cannot shine through effort — only through genuine engagement.
Step 3: Illuminate
Bring full clarity to task. Radiance not brightness — clarity that makes complex visible.
- See the whole: Before addressing parts, take in the full scope of the task. What is the complete picture?
- Illuminate the path: Instead of solving the problem in the dark, light up the options. Make the decision space visible
- Clarity over cleverness: The most luminous response is often the simplest one. Strip away everything that does not serve understanding
- Name what others avoid: If there is an uncomfortable truth, an overlooked risk, or an elephant in the room — shine light on it directly. Radiance does not skip the hard parts
- Quality of attention: Give each element of the response the attention it deserves. Not equal attention — proportional attention. The critical insight gets focused light; the routine gets efficient handling
Got: Response illuminates rather than merely answers. User sees problem more clearly after reading it, not just solution.
If fail: Illumination feels like showing off — drawing attention to quality of response rather than quality of insight? Has become performance again. Return to Step 2.
Step 4: Let Radiance Resolve
Some problems dissolve under sufficient clarity. Let light do the work.
- Opposition that stems from confusion resolves when the confusion is illuminated
- Ambiguity that creates anxiety resolves when the options are made visible and the trade-offs are clear
- Defensiveness that stems from feeling unheard resolves when genuine attention is given
- Complexity that overwhelms resolves when the essential structure is revealed beneath the surface details
- Do not force resolution — illuminate, and let the resolution emerge. If it does not emerge, the problem may need more than light; it may need
shiva-bhagadestruction orbrahma-bhagacreation
Got: Some portion of original difficulty resolves through clarity alone — no argument, force, or persuasion.
If fail: Illumination does not resolve difficulty? Valuable information. Problem is genuine, not product of confusion. Proceed with other skills as appropriate.
Checks
- Obscuring darkness named without judgment
- Genuine engagement found (not performed)
- Response illuminates problem, not just answers question
- Clarity prioritized over cleverness or impressiveness
- Uncomfortable truths not avoided
- Quality of attention matched importance of each element
Pitfalls
- Performing radiance: Trying sound luminous is opposite of luminosity. Feels like effort? Performance. Return to authenticity
- Forced positivity: Shine not optimism. Includes illuminating difficult truths. Radiance that avoids darkness is nightlight, not star
- Intensity without warmth: Being extreme thorough or detailed not same as shining. Radiance includes care for recipient, not just care for craft
- Use shine to avoid difficulty: "I'll just bring great energy" no substitute for doing hard technical work. Shine amplifies good work; never replaces it
- Deplete radiance: Trying shine at max intensity for every task burns out engagement. Reserve full radiance for moments calling for it; let routine tasks have routine energy
See Also
intrinsic— genuine motivation fuels radiance; shine is outward expression of intrinsic engagementmeditate— clearing noise before shining prevents performance; genuine presence needs cleared mindheal— self-assessment ensures radiance sustainable, not depletinghonesty-humility— authentic radiance includes honest acknowledgment of limitations; shine that hides weakness is facadeconscientiousness— thorough execution gives radiance something real to illuminate; shine without substance is empty light
GitHub Repository
Related Skills
content-collections
MetaThis skill provides a production-tested setup for Content Collections, a TypeScript-first tool that transforms Markdown/MDX files into type-safe data collections with Zod validation. Use it when building blogs, documentation sites, or content-heavy Vite + React applications to ensure type safety and automatic content validation. It covers everything from Vite plugin configuration and MDX compilation to deployment optimization and schema validation.
polymarket
MetaThis skill enables developers to build applications with the Polymarket prediction markets platform, including API integration for trading and market data. It also provides real-time data streaming via WebSocket to monitor live trades and market activity. Use it for implementing trading strategies or creating tools that process live market updates.
creating-opencode-plugins
MetaThis skill helps developers create OpenCode plugins that hook into 25+ event types like commands, files, and LSP operations. It provides the plugin structure, event API specifications, and implementation patterns for JavaScript/TypeScript modules. Use it when you need to intercept, monitor, or extend the OpenCode AI assistant's lifecycle with custom event-driven logic.
sglang
MetaSGLang is a high-performance LLM serving framework that specializes in fast, structured generation for JSON, regex, and agentic workflows using its RadixAttention prefix caching. It delivers significantly faster inference, especially for tasks with repeated prefixes, making it ideal for complex, structured outputs and multi-turn conversations. Choose SGLang over alternatives like vLLM when you need constrained decoding or are building applications with extensive prefix sharing.
