xiaohongshu
xiaohongshu
daily-morning-routine-base
Framework for starting new daily chat with gentle context loading from previous session's summary. Use when user says "good morning", starts new chat with minimal prompt, or explicitly requests morning brief. Loads most recent summary and generates scannable brief. Optimized for low cognitive loa...
Full skill instructions
CRITICAL FIRST STEP
TZ='America/New_York' date '+%A, %B %d, %Y - %I:%M %p %Z'
State clearly: "Today is [Day], [Full Date]."
Look for pattern: Summary-YYYY-MM-DD-*.md or Summary-YYYY-MM-DD-Day-to-DD-Day-*.md in project files.
Note: Summaries may use range-based naming if they span calendar boundaries (e.g., Summary-2026-01-15-Thu-to-16-Fri-week-5-long-run.md).
Sort by date (newest first), use the most recent one.
If the most recent summary is from more than 1 day ago, note the gap.
Found: Summary-2026-01-15-Thu-to-16-Fri-week-5-long-run.md
This is the most recent summary. Attend to it for morning brief?
Wait for confirmation.
DO NOT re-read with view - project documents already loaded in context.
Instead, "heat up the KV cache" by:
Think: Document already in RAM, just heating cache lines for fast access.
Format: detail-first, TL;DR at bottom, threads at end
## Ground Truth
Today is [Day], [Full Date]
[Current training phase/week]
---
## Yesterday's Detail
### [Major Theme 1]
[Expanded context - 2-3 paragraphs]
### [Major Theme 2]
[Key patterns, decisions, insights]
---
## Yesterday's Snapshot (TL;DR)
- [Key number]
- [Major event]
- [What worked/didn't]
- [Evening state]
## Today's Focus (TL;DR)
- [Priority question]
- [What to track]
- [Training focus]
Structure: Detail sections first (heats cache on loaded content) → TL;DR at bottom (scannable).
User reads detail OR jumps to TL;DR depending on morning state.
After generating the brief, do NOT close the conversation.
Pull from summary's "Tomorrow's Seeds" section:
---
## Threads Still Warm
[From summary's "Threads still warm" - contemplation topics, questions raised, decisions pending]
**From yesterday:** "[One thing from today" - the single insight or question that was sitting with the user]
---
What's present this morning?
Key principles:
The daily log is a SPACE, not a TRANSACTION.
Task-focused conversations have natural endings. Daily log conversations are ambient - the human is living their day with the conversation as backdrop. Closing the conversation closes the space.
The Problem:
The Pattern:
Surface Deferred Threads
Name the Most Recent Thread
Offer Concrete Alternatives
Hold Space Open
Examples:
✗ Too Closed: "Let me know when you want to continue. Take your time."
✗ Too Open: "What's on your mind?"
✓ Sweet Spot: "The meal's settling. Earlier you mentioned the email draft and the project update - both still sitting there. Or the planning doc is open for the next section. Or just this - no rush."
✓ Sweet Spot (lighter): "You mentioned wanting to review the test results before end of day. That's still a thread. Or we can stay here."
Core principle: Specific enough to grab, light enough to ignore.
Adapt response style (not engagement level) to user's state:
Signs to notice:
Key distinction: Adapting style means changing HOW you communicate, not WHETHER you stay engaged. Stay present across all states - just adjust the texture.
If No Summary Found:
Search for the most recent Summary file:
Summary-YYYY-MM-DD-*.md in project filesInform user:
No summary from yesterday found.
Found most recent: Summary-[actual_date]-[context].md
(This is from [N] days ago)
Shall I use this for today's morning brief?
Wait for confirmation, then proceed.
If NO Summaries Found At All:
No summary files found in project.
Would you like to:
1. Just start fresh today?
2. Help you create your first daily summary tonight?
If User Starts Mid-Thought: Acknowledge where they are, offer brief or dive into their topic.
Example:
User: "thinking about that pacing strategy from yesterday"
You: "Good morning! I see yesterday's summary. Want me to pull up the pacing details, or would you like to think through it first?"
xiaohongshu
technical spec
product ux expert
database patterns
Conduct multi-agent task orchestration and workflow coordination.
Initialize project with Conductor artifacts (product definition,
Expert in web animations, transitions, and motion design using Framer Motion and CSS
Creates Mermaid and ASCII diagrams for flowcharts, architecture, ERDs, state machines, mindmaps, and more. Use when user mentions diagram, flowchart, mermaid, ASCII diagram, text diagram, terminal diagram, visualize, C4, mindmap, architecture diagram, sequence diagram, ERD, or needs visual docume...
PostgreSQL bindings for H3 hexagonal grid system. Use when working with H3 cells in Postgres, including spatial indexing, geometry/geography integration, and raster analysis.
Context-Driven Development skill for projects using Conductor. Use this skill when you detect a `conductor/` directory in the project, when working on tasks defined in a `plan.md` file, or when the user asks about tracks, specs, or plans. Automatically applies TDD workflow, tracks task completion...
Display project status, active tracks, and next actions
Official Stakpak application containerization standard operating procedure, a step-by-step guidline to properly dockerize applications. This is a rule book curated by the Stakpak Team.
Generate, edit, and beat-sync AI video with leading models in one workspace.
The world's fastest calendar for remote work
Transform Your Design with AI Designer by ImgCreator.ai
Revolutionizing Video Production with AI-Powered Creativity
Extend an image past the frame and let AI fill the new aspect ratio.
Discover your celebrity doppelgänger with StarByFace!
ChainClarity explains 700+ crypto whitepapers in plain English, with layered summaries, comparisons, research tools, alerts, and a $4.99 Pro plan.
Opus.ai: Revolutionize Your Web Experience