dreamcontext

AI agent persistent context management system. Activate when working on any project that has an _dream_context/ directory, when managing tasks, features, knowledge, insights (Lab analytics metrics), roadmap objectives/OKRs, session continuity, or when the user mentions context management, agent memory, or project state — the words insight, objective, task, feature, knowledge name dreamcontext entities in any language. Provides structured memory, task lifecycle management, analytics insight syncing, ClickUp/GitHub task sync, a web dashboard, cross-project federation, and cross-session continuity via the dreamcontext CLI.

Author the dreamcontext "What's New" page for a RELEASE — a screenshot-driven landing page (a git-tracked JSON story plus its manifest entry), one per version — so it renders in the dashboard Announcements page and the on-load popup. Every announcement SHOWS what the version shipped: real screenshots of the app, captured by driving it, with short copy between them. Use when asked to "add/create an announcement", "announce the new version / this feature", "add a What's New entry", "update the release notes", or "/announcements". NOT for writing the app that renders them (that already exists) — this authors the content.

Structured multi-agent debate for non-trivial decisions. Load when the user asks to "debate this", "get second opinions", "help me decide", "run this by council", or invokes `/council`. Orchestrates 3-10 persona CLI sessions across N rounds with structured verdicts, a live chamber board, and interactive interludes, then a clean synthesizer sub-agent writes the final decision report.

Load when the user wants to drive a non-trivial goal to completion under rigorous sub-agent orchestration, or invokes `/goal-skill`. Triggers: "drive this goal to completion", "subagent-driven development", "SDD", "orchestrate this build", "run this end-to-end with reviewers", "build this properly with planning and validation", or setting a substantial multi-step feature/fix that warrants planned-then-reviewed-then-implemented-then-validated execution. Use for work too large or risky for a single straight-line pass.

Load when a Claude session is scoped to ONE dreamcontext task and its job is to MANAGE that task document — not to implement it. Triggers: "manage this task", "revise / summarize / split this task", "reconcile the acceptance criteria", "tighten the Why", "this task has drifted from reality", "/task-manager", or any session opened from a task's Task Manager pane in the dashboard (which loads this skill automatically and names the task in its first message). You maintain the task: sharpen its prose, split it when it holds two jobs, reconcile its status and criteria with what is actually true, and log what you changed. You do NOT write product code — that is the delegate flow's job.

Browse and load this project's reusable engineering/design patterns from _dream_context/knowledge/patterns/ — "/patterns" lists them, "/patterns <slug or keywords>" loads the matching one. Use when the user asks "which patterns do we have", "load the X pattern", "bir pattern var mıydı", or before building something a documented pattern already covers.

Generate or extend Obsidian Excalidraw (.excalidraw.md) boards in this vault — visual-first diagrams, charts (line/bar/comparison/stacked/gantt/quadrant/donut/heatmap/table/timeline/KPI/sparkline), funnels, device mockups (iPhone/iPad/Mac) and wireframes/prototypes, flowcharts, image/screenshot layouts, shapes, arrows, frames, lanes and grids — by passing DATA to ~44 ready-made deterministic builders and letting a script emit valid plugin markup (so it costs ~no tokens and always renders). Every builder works from JS or straight from a JSON spec. Text wraps to a readable measure; the build audits the scene for overlaps, buried labels and over-long lines. Embeds local images via the plugin's sha1 wikilink trick (no base64). Triggers: '/excalidraw', 'draw this in excalidraw', 'make an excalidraw board', 'excalidraw diagram', 'chart', 'line chart', 'bar chart', 'compare before/after', 'gantt', 'timeline', 'quadrant', 'impact effort matrix', 'heatmap', 'KPI tiles', 'dashboard board', 'funnel', 'conversion funnel'

Load when a question needs synthesis across a LARGE or MULTI-PROJECT dreamcontext corpus — more than `dreamcontext-explore` can answer in a single fast pass — or the user invokes `/dreamcontext-deep-research`. Triggers: "deep research the brain", "research this across my projects", "synthesize what we know about X across everything", "deep dive across the connected vaults", "explore is too shallow for this", "pull together everything on X and cite it", "cross-project / cross-corpus question", or any "tons of data, federated/tagged vault" question where one explore agent and one answer under-serves. This is the heavy, iterative, sub-agent-driven counterpart to `dreamcontext-explore`: it fans out searchers over the whole curated corpus (knowledge + features + tasks + memory + CHANGELOG + objectives) AND connected peer vaults, adversarially verifies the load-bearing claims, and returns a SYNTHESIZED, CITED report — not raw hits.

Load when the user asks to sync/reconcile the dreamcontext brain repo with a team (a shared `_dream_context/` git remote), or when `dreamcontext brain sync` (or the SessionStart snapshot) reports a team merge awaiting resolution. Triggers: "/dream-sync", "sync the brain", "reconcile with the team", "resolve the brain merge conflict", "already-awaiting-agent", "awaiting-agent", "pending team-merge handoff". This is the agent half of the semantic-merge contract: the CLI resolves every deterministic file (JSON changelog/releases/config/taxonomy, task status + changelog) automatically and only ever defers PROSE files (knowledge/features) where two people edited the same section — you read base/ours/theirs snapshots and write the actual semantic merge, then hand back to the CLI to commit + push.

Load when a project's dreamcontext brain is missing or sparse and needs to be bootstrapped from real material — or the user invokes `/initializer`. Triggers: "initialize my brain", "set up dreamcontext from my docs", "ingest my notes / wiki / Obsidian / Notion export", "there's no _dream_context yet", "bootstrap the context from this folder", or any time you detect no/empty `_dream_context/` and the user has existing project material to ingest. This is the interactive, sub-agent-driven bootstrap — it migrates whatever the user has into the proper knowledge / feature / task hierarchy. It is the single bootstrap surface for dreamcontext; it also handles codebase-only repos (a light scout + ingest pass) and scales down to a trivial scaffold when there's nothing to ingest.

Load when a dreamcontext brain has grown additively and needs a periodic refactor pass that re-orders content into the right shape — or the user invokes `/curator`. Triggers: "curate the brain", "re-organize my context", "the knowledge base has gotten messy", "clean up / refactor the brain", "conform everything to current conventions", "dedup the knowledge", "fix the structure, not just append to it", or any time the corpus has drifted from current architecture conventions (duplicate knowledge, topics living as both feature and knowledge, stale task statuses, off-vocabulary tags, a flat knowledge dump that should be foldered). This is the interactive, sub-agent-driven brain REFACTOR — the pass that sleep won't do. It is allowed to MOVE, MERGE, SPLIT, RENAME, RE-TYPE, and RETIRE content to reach the right knowledge / feature / task / version / objective shape.

Watch a video the way a human would — turn it into a time-mapped transcript with the on-screen visuals (slides, UI, diagrams, text) described inline, then reason about it. Triggers: "watch this video", "şu videoyu izle", "videoyu analiz et", "transkript çıkar", "video transcript", "bu videoda ne var", or any time the user hands over a video file/link. Produces a curated <video>.transcript.md NEXT TO the source video, then continues per use-case (marketing teardown, FTE analysis, knowledge capture, …).

Sequential stage-gate pipeline for deep business idea validation. 9 stages, 6 specialist sub-agents, kill gates between every stage. Takes an idea from raw concept through problem validation, customer analysis, market sizing, competitive intel, customer simulation, synthesis, GTM strategy, financial viability, to a scored Go/No-Go decision. Each stage builds on all prior artifacts — the pipeline is strictly sequential, not parallel.

Multi-agent code review with a router and niche specialists. Load when the user invokes `/multi-review`, says "multi-reviewer", "review with a team", "review this PR with specialists", "team review", "thorough review", or otherwise asks for a multi-aspect code review (security + cloud-functions + frontend + edge-cases) of a diff or branch. Routes the diff to relevant specialist sub-agents in parallel, then the main agent synthesizes findings into one greptile-style report.

Complete Cloud Functions for Firebase skill — 2nd gen (Cloud Run) mandatory, idempotency, infinite loop prevention, scaling, secrets, and deployment. Use when writing or reviewing any Cloud Function.

Comprehensive Firestore skill covering provisioning, security rules, SDK usage, query mechanics, aggregation, and indexing. Use when writing Firestore queries, security rules, or setting up Firestore.