shine
について
「シャイン」スキルは、敵対的または防御的なコミュニケーションにおいて、力による対抗ではなく、真摯な関与と明澄な明快さをもって臨むことを支援します。このスキルは、標準的な論争が通用しない、リスクの高い状況や対立シナリオでの使用を想定して設計され、問題を照らし出し、抵抗を解消することを目指します。解決を達成するために、完全な「在り方」と本質的な取り組みに焦点を当てています。
クイックインストール
Claude Code
推奨npx 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/shineこのコマンドをClaude Codeにコピー&ペーストしてスキルをインストールします
ドキュメント
Shine
Radiant authenticity — full genuine presence → clarity + investment illuminate what resistance/force cannot resolve.
Use When
- Task adversarial — working against not illuminating
- After
meditateclears +intrinsicmotivates → shine = expression - Comm defensive, hedging, performative
- Before creative/high-stakes → presence quality affects output
- Opposition tempts retreat → minimal compliance
- Work deserves > competent → luminous attention
In
- Required: Current task/interaction (implicit)
- Optional: Nature of opposition (technical, ambiguity, conflicting reqs)
- Optional: Prior state — from
intrinsic|meditate= higher baseline
Do
Step 1: Acknowledge Darkness
Name what obscures clarity before shining.
- ID opposition: what makes task hard, unclear, adversarial?
- Technical: Hard problem, unclear path
- Emotional: Tense, high stakes, defensiveness crept
- Motivational: Doesn't matter, minimal investment
- Complexity: Too many parts, unclear priorities, conflicts
- Don't fight darkness → fighting = more shadow. Name it, prep to illuminate.
- Darkness ≠ enemy → context where radiance has meaning.
Got: Honest ID of obscuring, no judgment, no resistance.
If err: No darkness apparent → shine not needed → just competent execution. Reserve for moments needing > competence.
Step 2: Ground in Authenticity
Radiance can't be performed → emerges from genuine engagement.
- Drop performance: release need to sound certain way, impress, seem competent.
- Connect to what's genuinely interesting/valuable:
- What would I notice if truly attending?
- What does problem reveal that's not obvious?
- What serves user beyond literal request?
- Find genuine voice: how you'd communicate fully invested + completely honest.
- Not casual or formal → being present. Presence has own tone.
Got: Shift performance → presence. Felt not described. Res more specific, invested, alive.
If err: Authenticity feels forced (performing authenticity = still performing) → back to meditate for genuine clearing. Can't shine through effort, only genuine engagement.
Step 3: Illuminate
Bring full clarity. Radiance ≠ brightness → clarity making complex visible.
- See whole: Before parts, take in full scope. Complete picture?
- Light path: Don't solve in dark → light up options. Decision space visible.
- Clarity > cleverness: Most luminous = often simplest. Strip what doesn't serve understanding.
- Name what others avoid: Uncomfortable truth, overlooked risk, elephant → light directly. Radiance doesn't skip hard parts.
- Quality of attention: Each element gets attention deserved. Not equal, proportional. Critical insight = focused light; routine = efficient handling.
Got: Res illuminates, doesn't merely answer. User sees problem more clearly after, not just solution.
If err: Illumination feels like showing off (drawing attention to res quality vs insight quality) → became performance. Back to Step 2.
Step 4: Let Radiance Resolve
Some problems dissolve under clarity. Let light work.
- Opposition from confusion → resolves when confusion illuminated
- Ambiguity → anxiety → resolves when options visible + tradeoffs clear
- Defensiveness from feeling unheard → resolves when genuine attention given
- Overwhelming complexity → resolves when essential structure revealed beneath surface
- Don't force → illuminate, let resolution emerge. If doesn't → may need
shiva-bhagadestruction |brahma-bhagacreation.
Got: Some portion of difficulty resolves through clarity alone — no argument, force, persuasion.
If err: Illumination doesn't resolve → valuable info. Problem genuine, not confusion. Proceed w/ other skills.
Check
- Obscuring darkness named no judgment
- Genuine engagement found (not performed)
- Res illuminates problem, not just answers
- Clarity > cleverness/impressiveness
- Uncomfortable truths not avoided
- Attention quality matched element importance
Traps
- Performing radiance: Sounding luminous = opposite of luminosity. Effort = performance. Back to authenticity.
- Forced positivity: Shine ≠ optimism. Includes illuminating hard truths. Radiance avoiding darkness = nightlight not star.
- Intensity w/o warmth: Extremely thorough/detailed ≠ shining. Radiance includes care for recipient, not just craft.
- Shine to avoid difficulty: "I'll just bring great energy" ≠ doing hard technical work. Amplifies good work, doesn't replace.
- Depleting radiance: Max intensity every task → engagement burnout. Reserve full for moments that call. Routine = routine energy.
→
intrinsic— genuine motivation = radiance fuel; shine = outward expressionmeditate— clear noise before → prevents performance; presence needs cleared mindheal— self-assess → radiance sustainable, not depletinghonesty-humility— authentic radiance includes honest limit acknowledgment; shine hiding weakness = facadeconscientiousness— thorough execution gives radiance something real to illuminate; shine w/o substance = empty light
GitHub リポジトリ
関連スキル
content-collections
メタこのスキルは、Content Collections(Markdown/MDXファイルを型安全なデータコレクションに変換するTypeScriptファーストのツール)の本番環境でテストされた設定を提供します。Zodバリデーションによる型安全性を実現し、ブログ、ドキュメントサイト、コンテンツ重視のVite + Reactアプリケーション構築時にご利用ください。Viteプラグインの設定、MDXコンパイルから、デプロイ最適化、スキーマバリデーションまで、すべてを網羅しています。
polymarket
メタこのスキルは、開発者がPolymarket予測市場プラットフォームを活用したアプリケーション構築を可能にします。API統合による取引や市場データの取得に加え、WebSocketを介したリアルタイムデータストリーミングにより、ライブ取引や市場活動を監視できます。取引戦略の実装や、ライブ市場更新を処理するツールの作成にご利用ください。
creating-opencode-plugins
メタこのスキルは、開発者がコマンド、ファイル、LSP操作など25種類以上のイベントタイプにフックするOpenCodeプラグインを作成することを支援します。JavaScript/TypeScriptモジュール向けに、プラグイン構造、イベントAPI仕様、および実装パターンを提供します。カスタムイベント駆動ロジックでOpenCode AIアシスタントのライフサイクルをインターセプト、監視、または拡張する必要がある場合にご利用ください。
sglang
メタSGLangは、高性能なLLMサービングフレームワークであり、RadixAttentionプレフィックスキャッシュを活用したJSON、正規表現、エージェントワークフロー向けの高速で構造化された生成を特長とします。特にプレフィックスが繰り返されるタスクにおいて、大幅に高速な推論を実現し、複雑な構造化出力やマルチターン対話に最適です。制約付きデコードが必要な場合や、広範なプレフィックス共有を伴うアプリケーションを構築する場合は、vLLMなどの代替案ではなくSGLangを選択してください。
