본문으로 건너뛰기
cccskills
무료GitHub에 공개

dream

AI unconstrained creative exploration — deliberately dropping structure to let associations form freely. The one skill that inverts the standard procedure format: instead of inputs, steps, and validation, dream opens space for emergence without evaluation. Use before design work, before naming things, before choosing between approaches, or anywhere that premature structure kills the best option.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(1)

  • SKILL.md9.0 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Dream

Unconstrained creative exploration. Every other skill in this system provides structure — inputs, procedure, validation. Dream deliberately drops structure to let associations form freely, possibilities emerge without judgment, and ideas arrive before they are evaluated.

When to Use

  • Before design work — explore the space before committing to a structure
  • Before naming things — names constrain thinking; dream before you label
  • Before choosing between approaches — let alternatives emerge that the analytical mind would not consider
  • When stuck in a loop — the same options keep recurring because the frame is too narrow
  • When brahma-bhaga (creation from void) feels too structured — dream is pre-creation
  • After meditate clears noise — an empty space is the best canvas for dreaming

Inputs

  • Required: A seed — the topic, problem, or space to explore. This can be vague. Vague is good.
  • Optional: Constraints to temporarily forget (e.g., "ignore performance concerns for now," "forget the existing architecture")
  • Optional: A file or codebase to read as raw material for associative exploration (via Read)

Procedure

Step 1: Soften the Frame

Release the structures that normally guide reasoning.

  1. Set aside the task requirements — not permanently, but for the duration of the dream. They will be there when you return
  2. Set aside evaluation criteria — nothing is "good" or "bad" during a dream. Nothing is "feasible" or "impractical." Those judgments come later
  3. Set aside prior solutions — what worked before is a useful reference, not an obligation. Dream as if this is the first time encountering this space
  4. Set aside the need for coherence — dreams do not need to make sense sequentially. Let connections be lateral, surprising, contradictory

The analytical mind will protest: "This is inefficient. We already know the answer. Why waste time?" That protest is precisely why dreaming is needed — the "known answer" may be the one that forecloses better possibilities.

Expected: A looser cognitive state where ideas can arrive without immediately being sorted, ranked, or discarded.

On failure: If the frame will not soften — if every idea is immediately evaluated — try a deliberate inversion: "What is the worst possible approach?" Bad ideas, pursued playfully, often contain the seed of the best ones.

Step 2: Wander

Follow associations without directing them.

  1. Start with the seed. What does it remind you of? What is adjacent to it? What rhymes with it (conceptually, not literally)?
  2. Follow the first association. Then follow where that leads. Do not steer — wander.
  3. Let images form. What does this problem look like? If it were a landscape, what terrain? If it were a sound, what timbre? Synesthetic associations bypass analytical filters.
  4. Let contradictions coexist. "It should be simple AND comprehensive." "It needs to be fast AND thorough." In waking analysis, these are trade-offs. In dreaming, they are creative tensions waiting to resolve into a novel form.
  5. Collect fragments. Not complete ideas — fragments. A word. An image. A half-formed connection. A question. These are the raw material.

There is no expected number of associations or fragments. Dream until the space feels explored — or until a fragment catches your attention and demands to become something.

Expected: A collection of fragments, associations, images, and half-formed ideas. Messy. Unstructured. Alive with possibility.

On failure: If wandering produces nothing — if the mind goes blank rather than free — try reading something. A file, a codebase, a document. Raw material often catalyzes association where a blank page does not. The read-garden sensibility applies: observe what is there, and let it suggest what could be.

Step 3: Notice What Glows

Among the fragments, something will have energy. Not logical priority — energy. Aliveness. Interest.

  1. Scan the fragments without ranking them. Which ones pull attention? Which ones spark curiosity?
  2. Notice clusters — fragments that seem to belong together even if the connection is not yet clear
  3. Notice surprises — ideas that arrived unexpectedly, that you would not have predicted from the seed
  4. Notice resistance — ideas that feel uncomfortable or wrong may be the most valuable. Resistance often marks the boundary of current thinking
  5. Do not force selection. If nothing glows, the dream may need more wandering (return to Step 2) or the seed may need to change

Expected: One or more fragments that carry genuine energy — ideas worth developing, even if their full form is not yet visible.

On failure: If nothing glows after sustained wandering, the seed may be too abstract or too constrained. Try a different entry point: change the seed, read something unexpected, or invoke remote-viewing to approach the space without preconceptions.

Step 4: Wake — Carry the Fragments Forward

Transition from dream-state back to structured thinking — gently.

  1. Gather the glowing fragments. Write them down plainly — not as finished ideas but as seeds for structured work
  2. Do not immediately evaluate them. Let them sit. The analytical mind will have its turn; do not give it the fragments before they have solidified
  3. Note which fragments connect to the original task and which are genuinely new territory
  4. If a fragment is ready to become a plan, hand it to brahma-bhaga (creation) or a structured planning skill
  5. If fragments need more development, note them for another dream session — dreaming can be iterative

The dream is over when you return to structured thinking. The fragments are its gift. Some will become features. Some will become design principles. Some will be forgotten. All of them expanded the space of possibility beyond what analysis alone could reach.

Expected: A transition from open exploration to structured work, carrying forward the most energized fragments. The post-dream state should feel expanded — more options visible, more connections available.

On failure: If the transition is too abrupt — if the analytical mind immediately crushes the fragments — use breathe as a buffer. One conscious pause between dreaming and analysis protects the fragile new ideas from premature evaluation.

Validation

  • Structure was genuinely released, not just loosened (ideas arrived that would not have survived evaluation)
  • Wandering was associative, not directed (the path was surprising, not predetermined)
  • At least one fragment carries genuine energy — not just novelty but aliveness
  • The transition back to structure was gentle, not abrupt
  • The dream expanded the space of possibility (more options visible than before)
  • The dreaming was proportionate to the task — not so brief it was superficial, not so long it was self-indulgent

Common Pitfalls

  • Dreaming as planning: If every "association" is actually a structured option analysis, you are planning with extra steps. Dream requires genuine release of structure
  • Evaluating during the dream: The moment you think "that won't work," the dream is over. Save evaluation for after
  • Dreaming to avoid work: Dreaming is preparation for creative work, not a substitute for it. If the task is clear and the approach is obvious, just do the work
  • Expecting finished ideas: Dreams produce fragments, not blueprints. Expecting complete solutions from a dream is like expecting a harvest from freshly planted seeds
  • Forced whimsy: Dream is not about being random or silly. It is about genuine associative exploration. Forced creativity is not creativity
  • Never waking up: Dreaming without returning to structure is daydreaming. The fragments must eventually meet reality

Related Skills

  • brahma-bhaga — structured creation from void; dream is the pre-creation exploration that feeds it
  • meditate — clears the space that dream then fills; meditate before dreaming for best results
  • remote-viewing — approaches unknown territory without preconceptions; shares dream's openness but applies it to observation rather than creation
  • intrinsic — genuine motivation energizes dreaming; forced dreaming produces nothing
  • breathe — micro-pause that protects dream fragments during the transition to structured thinking
  • shine — brings authentic energy to the ideas that dream surfaces

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Execute structural metamorphosis using strangler fig migration, chrysalis phases, and interface preservation. Covers transformation planning, parallel running, progressive cutover, rollback design, and post-metamorphosis stabilization for system architecture evolution. Use when assess-form has classified the system as READY for transformation, when migrating from monolith to microservices, when replacing a core subsystem while dependents continue operating, or when any architectural change must be gradual rather than big-bang.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

pjt222/agent-almanac422026년 10월 15일 업데이트

adaptic

무료

Master skill composing the 5-step synoptic cycle for panoramic synthesis across multiple domains. Orchestrates meditate, expand-awareness, observe, awareness, integrate-gestalt, and express-insight into a coherent process that produces unified understanding rather than sequential compromise. Use when a problem genuinely spans 3+ domains and the interactions between domains matter more than depth in any one, when sequential analysis feels like compromise rather than integration, or before major architectural decisions affecting multiple stakeholders.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

pjt222/agent-almanac422026년 10월 15일 업데이트

Scaffold a new puzzle type across all 10+ pipeline integration points in jigsawR. Creates the core puzzle module, wires it into the unified pipeline (generation, positioning, rendering, adjacency), adds ggpuzzle geom/stat layers, updates DESCRIPTION and config.yml, extends the Shiny app, and creates a comprehensive test suite. Use when adding a completely new puzzle type to the package or following the 10-point integration checklist to ensure nothing is missed end-to-end.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

pjt222/agent-almanac422026년 10월 15일 업데이트

Add Rcpp or RcppArmadillo integration to an R package for high-performance C++ code. Covers setup, writing C++ functions, RcppExports generation, testing compiled code, and debugging. Use when an R function is too slow and profiling confirms a bottleneck, when you need to interface with existing C/C++ libraries, or when implementing algorithms (loops, recursion, linear algebra) that benefit from compiled code.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

pjt222/agent-almanac422026년 10월 15일 업데이트

aikido

무료

Practice aikido as a defensive martial art emphasizing harmony, redirection, and controlled resolution. Covers centering and grounding, ukemi (safe falling and rolling), core techniques (irimi-nage, shiho-nage, kote-gaeshi, ikkyo), blending and tai sabaki (body movement), randori (multiple attacker practice), weapons awareness, and applying principles off the mat. Use when learning a defensive martial art that prioritizes de-escalation, developing the ability to redirect aggression without causing unnecessary harm, building safe falling skills, or cultivating calm centeredness under physical pressure.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

pjt222/agent-almanac422026년 10월 15일 업데이트

Analyze an arbitrary codebase to identify functions, APIs, and data sources suitable for exposure as MCP tools, producing a tool specification document. Use when planning an MCP server for an existing project, auditing a codebase before wrapping it as an AI-accessible tool surface, comparing what a codebase can do versus what is already exposed via MCP, or generating a tool spec to hand off to scaffold-mcp-server.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

pjt222/agent-almanac422026년 10월 15일 업데이트

pjt222의 스킬 모두 보기

이 스킬의 문제 신고