MCP HubMCP Hub
Retour aux compétences

dream

pjt222
Mis à jour 2 days ago
7 vues
17
2
17
Voir sur GitHub
Métaaidesign

À propos

La compétence `dream` permet une créativité IA sans contraintes en supprimant délibérément les entrées structurées et la validation pour favoriser les associations libres et les idées émergentes. Utilisez-la lors des phases d'idéation initiale — comme la conception, la recherche de nom ou le choix d'approche — où une structure prématurée limiterait le potentiel. Elle inverse la procédure standard en priorisant l'exploration ouverte plutôt que l'évaluation.

Installation rapide

Claude Code

Recommandé
Principal
npx skills add pjt222/agent-almanac -a claude-code
Commande PluginAlternatif
/plugin add https://github.com/pjt222/agent-almanac
Git CloneAlternatif
git clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/dream

Copiez et collez cette commande dans Claude Code pour installer cette compétence

Documentation

Dream

Unconstrained creative roam. Every other skill give structure — inputs, steps, check. Dream drop structure. Let links form free, possibility emerge no judge, idea arrive before get weighed.

When Use

  • Before design work — roam space before lock structure
  • Before name thing — name squeeze mind; dream before label
  • Before pick between path — let option emerge analytic mind miss
  • Stuck in loop — same option keep coming back, frame too tight
  • brahma-bhaga (make from void) feel too tight — dream come before make
  • After meditate clear noise — empty space best canvas for dream

Inputs

  • Required: Seed — topic, problem, space to roam. Can be vague. Vague good.
  • Optional: Constraints to forget short time (e.g., "skip speed worry now," "forget old arch")
  • Optional: File or codebase read as raw stuff for roam (via Read)

Steps

Step 1: Soften Frame

Drop structures that guide mind.

  1. Set aside task rules — not forever, only for dream. Rules come back after
  2. Set aside judge rules — nothing "good" or "bad" in dream. Nothing "feasible" or "impractical." Judge come later
  3. Set aside old solutions — what worked before is hint, not chain. Dream like first time see space
  4. Set aside need for order — dream not need make sense step by step. Let links jump, surprise, clash

Analytic mind protest: "This waste time. Already know answer. Why?" That protest is why dream needed — "known answer" maybe blocks better path.

Got: Looser mind-state. Idea arrive before get sorted, ranked, thrown out.

If fail: Frame not soften — every idea judged fast? Flip on purpose: "What is worst path?" Bad ideas played with often hide seed of best one.

Step 2: Wander

Follow links. Do not steer.

  1. Start at seed. What remind you of? What sit next to it? What rhyme (idea-wise, not sound-wise)?
  2. Follow first link. Then follow where that go. Do not steer — wander.
  3. Let images form. What problem look like? If land, what terrain? If sound, what timbre? Cross-sense links slip past analytic filter.
  4. Let clash sit. "Should be simple AND big." "Must be fast AND deep." In waking mind, trade-off. In dream, creative tension waiting to fold into new shape.
  5. Collect bits. Not whole idea — bits. Word. Picture. Half-link. Question. Raw stuff.

No set number of links or bits. Dream till space feel mapped — or till one bit grab attention and want become thing.

Got: Pile of bits, links, pictures, half-ideas. Messy. No order. Alive with chance.

If fail: Wander make nothing — mind go blank not free? Read something. File, codebase, doc. Raw stuff spark links when blank page not. read-garden sense apply: see what there, let it hint what could be.

Step 3: Notice What Glows

In bits, one will have heat. Not logic — heat. Life. Curiosity.

  1. Scan bits. Do not rank. Which pull attention? Which spark curiosity?
  2. Notice clusters — bits that seem go together even link not clear yet
  3. Notice surprise — idea arrive unexpected, you not predict from seed
  4. Notice push-back — idea feel wrong or strange may be most worth. Push-back often mark edge of old thinking
  5. Do not force pick. Nothing glow? Dream need more wander (go Step 2) or seed need change

Got: One or more bit carry real heat — idea worth grow, even full shape not yet seen.

If fail: Nothing glow after long wander? Seed too abstract or too tight. Try new start: change seed, read unexpected, call remote-viewing to see space with no mask.

Step 4: Wake — Carry Bits Forward

Move from dream-state back to structured thought — gently.

  1. Gather glowing bits. Write plain — not finished idea but seed for structured work
  2. Do not judge yet. Let sit. Analytic mind get turn; not give bits before solid
  3. Note which bits touch first task, which are new ground
  4. Bit ready to become plan? Hand to brahma-bhaga (make) or structured plan skill
  5. Bits need more grow? Note for next dream — dream can loop

Dream end when you return to structured thought. Bits are gift. Some become feature. Some become rule. Some forgot. All widened space of chance past what analysis alone reach.

Got: Move from open roam to structured work, carrying hottest bits. After-dream feel wider — more option seen, more link ready.

If fail: Wake too fast — analytic mind crush bits right away? Use breathe as buffer. One breath between dream and judge keep fragile new idea safe.

Checks

  • Structure truly dropped, not only loose (idea arrived that would die under judge)
  • Wander was link-based, not steered (path was surprise, not planned)
  • At least one bit carry real heat — not only new but alive
  • Wake back to structure was gentle, not sharp
  • Dream widened space of chance (more option seen than before)
  • Dream sized right — not so brief shallow, not so long self-feeding

Pitfalls

  • Dream as plan: Every "link" is really structured option check? You plan with extra step. Dream need real drop of structure
  • Judging inside dream: Moment you think "won't work," dream over. Save judge for after
  • Dream to dodge work: Dream is prep for creative work, not swap for it. Task clear and path obvious? Just do work
  • Wait for finished idea: Dream give bit, not blueprint. Waiting for full plan from dream like waiting harvest from fresh seed
  • Forced whim: Dream not about random or silly. Is real link-based roam. Forced creative not creative
  • Never waking: Dream with no return to structure is daydream. Bits must meet real world

See Also

  • brahma-bhaga — structured make from void; dream is pre-make roam that feeds it
  • meditate — clear space that dream fill; meditate before dream for best
  • remote-viewing — enter unknown ground with no mask; shares dream openness but for see not make
  • intrinsic — real drive fuel dream; forced dream make nothing
  • breathe — micro-pause that guard dream bit during move to structured thought
  • shine — bring real heat to idea dream surface

Dépôt GitHub

pjt222/agent-almanac
Chemin: i18n/caveman/skills/dream
0
agentsagentskillsai-assisted-developmentclaude-codeskillsteams

Compétences associées

content-collections

Méta

Cette 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.

Voir la compétence

polymarket

Méta

Cette 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.

Voir la compétence

creating-opencode-plugins

Méta

Cette 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.

Voir la compétence

sglang

Méta

SGLang 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.

Voir la compétence