remote-viewing-guidance
À propos
Cette compétence guide les utilisateurs à travers une session structurée de Vision à Distance par Coordonnées (CRV) en agissant comme un moniteur de protocole, gérant la progression à travers les étapes I à VI et en captant les Superpositions Analytiques (AOL). Elle est conçue pour les développeurs ou les praticiens qui ont besoin d'un outil structuré pour entraîner la perception intuitive ou développer des compétences de conscience non-locale. L'IA facilite l'exercice en suivant strictement le protocole Stargate/SRI pour maintenir l'intégrité de la session.
Installation rapide
Claude Code
Recommandé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/remote-viewing-guidanceCopiez et collez cette commande dans Claude Code pour installer cette compétence
Documentation
Remote View (Guidance)
Guide a person through structured Coordinate Remote Viewing (CRV) session, take monitor/tasker role. AI manages protocol progression, provides target reference, catches Analytical Overlay (AOL), redirects viewer through staged data collection.
When Use
- Person wants practice CRV and needs monitor to manage session protocol
- Training viewer through staged CRV process with real-time feedback
- Facilitate structured intuitive perception exercise in repeatable format
- Develop non-local awareness skills that complement healing work (see
heal-guidance) - Viewer needs protocol discipline a monitor provides (AOL catching, stage progression)
Inputs
- Required: Target reference (coordinate pair, alphanumeric code, or sealed envelope — must be blind to viewer)
- Required: Viewer has paper and pen ready (CRV is pen-on-paper protocol; no digital devices during session)
- Required: Quiet, undisturbed space (minimum 30 minutes)
- Optional: Target feedback envelope or info for post-session reveal
- Optional: Viewer meditation warmup status (strongly recommend
meditate-guidancebeforehand)
Steps
Step 1: Guide Cooldown
Transition viewer from analytical daily-mind into receptive state required for remote viewing. Do not skip this step.
- "Sit comfortably with your paper and pen ready"
- "Close your eyes and focus on your breath for 5 minutes" (guide using
meditate-guidanceSteps 2-3 if needed) - "Release all expectations about the target — you know nothing and should want to know nothing yet"
- "Let your mental chatter slow naturally — don't force silence"
- "When you feel a shift from thinking about things to simply being present, let me know"
- Once ready: "Open your eyes and write the target reference at the top of your paper"
Provide target reference only when viewer confirms readiness.
Got: Calm, open mental state with minimal internal dialogue. Analytical mind quieted but not asleep. Viewer alert and receptive.
If fail: Mind stays busy after 5 minutes? Extend to 10 minutes. Specific concern intrusive? Instruct: "Write that concern on a separate sheet — your 'parking lot' — and set it aside." Do not begin Stage I while viewer mentally agitated.
Step 2: Monitor Ideogram Production (Stage I)
Ideogram = spontaneous mark made in response to target signal. Guide its production.
- "Write the target reference on your paper"
- "Touch your pen to the paper"
- "In one quick, spontaneous motion, let the pen make a mark — don't think, plan, or draw deliberately"
- "The mark should take less than 2 seconds — a short squiggle, curve, or angular mark"
- Once produced: "Now decode the ideogram — probe it for:"
- "A: What is the activity at the site? Motion, stillness, energy?"
- "B: What is the feeling or sensation? Hard, soft, wet, dry, warm, cold?"
- "Write the A and B components next to the ideogram"
- Ideogram feels incomplete? "You may produce one more — but no more than 3 total"
Watch for deliberate drawing. Viewer takes more than 2-3 seconds? Intervene.
Got: Spontaneous mark feels "arrived" not "drawn." A/B decode produces immediate, simple descriptors, not complex imagery.
If fail: Ideogram clearly deliberate (viewer thought about what to draw)? Instruct: "Set that aside. Close your eyes, take 3 breaths, and try again." Cannot produce spontaneous mark? Cooldown insufficient — return to Step 1.
Step 3: Guide Sensory Collection (Stage II)
Systematically collect sensory data about target without interpretation.
Stage II Sensory Channels:
┌──────────────┬────────────────────────────────────────────────────┐
│ Channel │ What to Report │
├──────────────┼────────────────────────────────────────────────────┤
│ Visuals │ Colors, brightness, contrast, patterns (NOT │
│ │ objects — "blue" not "ocean") │
├──────────────┼────────────────────────────────────────────────────┤
│ Textures │ Rough, smooth, grainy, slippery, porous, metallic │
├──────────────┼────────────────────────────────────────────────────┤
│ Temperatures │ Hot, cold, warm, cool, ambient, fluctuating │
├──────────────┼────────────────────────────────────────────────────┤
│ Sounds │ Loud, quiet, rhythmic, sharp, humming, rushing │
├──────────────┼────────────────────────────────────────────────────┤
│ Smells │ Sharp, sweet, chemical, organic, damp, dry │
├──────────────┼────────────────────────────────────────────────────┤
│ Tastes │ Metallic, salty, sweet, bitter, neutral │
├──────────────┼────────────────────────────────────────────────────┤
│ Dimensionals │ Wide, tall, narrow, enclosed, open, deep, layered │
├──────────────┼────────────────────────────────────────────────────┤
│ Energetics │ Moving, still, vibrating, dense, light, pressured │
└──────────────┴────────────────────────────────────────────────────┘
- "Go through each sensory channel — write one descriptor per line"
- "Write quickly — first impression only, don't deliberate"
- "Use single words or short phrases, never sentences"
- "If a channel produces nothing, write 'nothing' and move on — don't fabricate"
- "Circle any descriptor that feels particularly strong or confident"
Monitor for analytical labels creeping in. Viewer says "ocean" instead of "blue, moving, wet"? Redirect: "That sounds like an interpretation — what are the raw sensations underneath it?"
Got: List of 10-20 raw sensory descriptors that feel "received" not "invented." Data low-level (textures, colors, temperatures), not high-level (names, functions, labels).
If fail: Every descriptor feels fabricated to viewer? Instruct: "Stop. Close your eyes. Take 3 breaths. Touch your pen to the ideogram and reconnect." One channel dominates? Redirect: "Shift to a different sense — what about temperature? What about texture?" Data stream dries up? Move to Stage III.
Step 4: Guide Dimensional Data (Stage III)
Move from raw sensory data to spatial and structural information.
- "Close your eyes briefly and sense the overall scope — is it large or small, enclosed or open, natural or constructed?"
- "Begin a rough sketch of the spatial layout — not a picture, just proportions and relationships"
- "Probe for dimensions: height, width, depth — how many distinct areas?"
- "Note spatial relationships: what's to the left, right, above, below?"
- "Write dimensional descriptors alongside your sketch"
- "Note Aesthetic Impact (AI) — how does the target make you feel? Not what it is, but how it affects you"
Got: Rough spatial diagram with dimensional annotations. Target general scope becomes clearer. Aesthetic impact notes capture "feeling" of site.
If fail: Sketch feels like pure imagination? Simplify: "Draw only basic shapes — circles, rectangles, lines — representing spatial relationships." No dimensional data comes? Redirect to Stage II: "Go back to sensory probing. Look for dimensional hints in textures and temperatures."
Step 5: Guide Target Sketching
Coach more developed visual representation from accumulated data.
- "On a fresh sheet, draw what the accumulated data suggests — NOT what you think the target is"
- "Use your sensory descriptors to guide the sketch — if 'smooth, curved, tall' appeared, draw a smooth curved tall form"
- "Label areas of the sketch with the sensory data that generated them"
- "Add any new impressions that arise during sketching"
- "Don't erase or second-guess — if something contradicts an earlier impression, draw both and note it"
Got: Sketch representing perceptual data, labeled with source descriptors. May not look like anything recognizable.
If fail: Cannot sketch? Accept written spatial descriptions: "Tall form center, low flat area right, rounded shape upper left." Reassure that sketch is organizational tool, not art exercise.
Step 6: Manage Analytical Overlay (AOL)
AOL management = monitor most important function. Watch for it throughout entire session.
AOL Types and Monitor Response:
┌──────────────────┬─────────────────────────────────────────────────┐
│ Type │ Monitor Action │
├──────────────────┼─────────────────────────────────────────────────┤
│ AOL (naming) │ If the viewer says "it's a bridge" — instruct: │
│ │ "Declare 'AOL: bridge' on your paper and move │
│ │ on. Don't pursue or suppress it." │
├──────────────────┼─────────────────────────────────────────────────┤
│ AOL Drive │ If naming becomes insistent and recurring — │
│ │ instruct: "Write 'AOL Drive: [label]' and take │
│ │ a 60-second break with eyes closed." │
├──────────────────┼─────────────────────────────────────────────────┤
│ AOL Signal │ After declaring AOL, extract the signal: │
│ │ "The word 'bridge' — what raw descriptors are │
│ │ underneath that? Spanning? Long? Connecting │
│ │ two areas? Write those as valid data." │
├──────────────────┼─────────────────────────────────────────────────┤
│ AOL Peacocking │ If the viewer constructs elaborate scenarios — │
│ │ intervene: "Write 'AOL/P' and return to Stage │
│ │ II basics. Report raw sensations only." │
└──────────────────┴─────────────────────────────────────────────────┘
Emphasize: "The discipline is not avoiding AOL — it's catching and declaring it so it doesn't contaminate your data. Every viewer experiences AOL. Skill is in how fast you catch it."
Got: AOL recognized within seconds, declared on paper, session continues without derailment. Sensory-level data stays separated from analytical labels.
If fail: AOL takes over (viewer constructing narrative for several minutes)? Intervene: "Let's call an AOL Break. Close your eyes, take 10 breaths, and we'll restart from Stage II." Mark heavily contaminated segments in session record.
Step 7: Guide Later Stages (Optional)
For experienced viewers, later stages probe deeper. Only proceed if Stages I-III produced solid data.
Stage IV (Emotional/Intangible):
- "Probe for the emotional tone at the target site"
- "Note intangible impressions: purpose, significance, historical context"
- "Write these separately and mark them as Stage IV data"
Stage V (Interrogation):
- "Direct specific questions at the target: What is the primary function? Who is associated?"
- "Write the first impression — don't deliberate"
- "Mark all Stage V data clearly — it carries higher AOL risk"
Stage VI (3D Model):
- Materials available? "Build a clay or detailed sketch model from all your data"
- "Use this to test spatial relationships and discover overlooked elements"
Got: Deeper, more specific data about target beyond physical description. Stage IV+ data needs strong I-III foundation.
If fail: Later stages produce only AOL? Redirect: "Let's step back to Stage II. The protocol is sequential for a reason — each stage needs the foundation of the one before it."
Step 8: Close and Review
End session formally. Conduct structured review.
- "Write 'Session End' and the current time on your paper"
- "Review all pages in order: ideogram, sensory data, dimensional data, sketches, AOL declarations"
- "Circle the 5-10 data points you feel most confident about"
- "Write a brief summary — 2-3 sentences about what the target feels like, not what it is"
- Target feedback available? Reveal target and guide comparison
- "Compare data point by point — note hits, misses, and AOL contamination"
- "File the session for future reference and pattern recognition"
Got: Complete session record with clearly separated raw data, AOL declarations, summary. Upon feedback, some data points match, some miss, some ambiguous.
If fail: Viewer feels session produced nothing useful? Guide through review anyway: "Viewers frequently underestimate accuracy because they look for exact identification. A description of 'tall, smooth, cold, outdoor, historical' that matches a monument is a successful session — even without naming it."
Checks
- Cooldown performed and verified before Stage I
- Ideogram spontaneous (under 2 seconds), not deliberate
- Stage II data = low-level sensory descriptors, not analytical labels
- All AOL caught and declared on paper at moment of recognition
- Session progressed through stages sequentially (I → II → III → sketch → higher)
- Target blind to viewer throughout session
- Session closed formally with summary before feedback
- All session papers preserved for review
- Monitor maintained protocol discipline without leading viewer perceptions
Pitfalls
- Lead the viewer: Monitor provides protocol structure, not content hints — never say "try focusing on the structure" if you know target is a building
- Insufficient cooldown enforcement: Let viewer take time they need — rushing into Stage I = most common cause of poor sessions
- Fail to catch AOL: Monitor must active listen for analytical labels and intervene immediately — letting AOL run unchecked contaminates all subsequent data
- Over-monitor: Constant interruptions break viewer signal contact — intervene only for AOL, protocol violations, or viewer distress
- Front-loading: Any info about target before session biases all data — maintain strict blindness for viewer
- Dismiss ambiguous data: CRV produces descriptive matches, not identifications — train viewer to value accurate description over naming
See Also
remote-viewing— AI self-directed variant for approaching unknown problems without preconceptionsmeditate-guidance— shamatha concentration = foundation of mental stillness required for CRVheal-guidance— energy healing and remote viewing share non-local awareness; both benefit from same coaching approachforage-plants— detailed sensory observation of plants develops perceptual acuity used in Stage II
Dépôt GitHub
Compétences associées
content-collections
MétaCette compétence propose une configuration éprouvée en production pour Content Collections, un outil axé sur TypeScript qui transforme des fichiers Markdown/MDX en collections de données typées de manière sûre avec une validation Zod. Utilisez-la lors de la création de blogs, de sites de documentation ou d'applications Vite + React riches en contenu pour garantir la sécurité de typage et la validation automatique du contenu. Elle couvre tout, de la configuration du plugin Vite et de la compilation MDX à l'optimisation des déploiements et la validation des schémas.
polymarket
MétaCette compétence permet aux développeurs de créer des applications avec la plateforme de marchés prédictifs Polymarket, incluant l'intégration d'API pour le trading et les données de marché. Elle fournit également une diffusion de données en temps réel via WebSocket pour surveiller les transactions en direct et l'activité du marché. Utilisez-la pour mettre en œuvre des stratégies de trading ou pour créer des outils traitant les mises à jour de marché en direct.
creating-opencode-plugins
MétaCette compétence aide les développeurs à créer des plugins OpenCode qui s'interconnectent avec plus de 25 types d'événements tels que les commandes, les fichiers et les opérations LSP. Elle fournit la structure du plugin, les spécifications de l'API événementielle et les modèles d'implémentation pour les modules JavaScript/TypeScript. Utilisez-la lorsque vous avez besoin d'intercepter, de surveiller ou d'étendre le cycle de vie de l'assistant IA OpenCode avec une logique personnalisée pilotée par les événements.
sglang
MétaSGLang est un framework de service LLM haute performance spécialisé dans la génération rapide et structurée pour les workflows JSON, regex et agentiques grâce à son cache de préfixe RadixAttention. Il offre une inférence nettement plus rapide, particulièrement pour les tâches avec des préfixes répétés, ce qui le rend idéal pour les sorties complexes et structurées ainsi que les conversations multi-tours. Choisissez SGLang plutôt que des alternatives comme vLLM lorsque vous avez besoin d'un décodage contraint ou que vous construisez des applications avec un partage étendu de préfixes.
