@geminilight/mindos 0.1.0

package/templates/en//360/237/221/244 Profile/INSTRUCTION.md"

@@ -0,0 +1,21 @@
+# Directory Instruction Set
+
+## Goal
+
+- Define local execution rules for this first-level directory.
+
+## Local Rules
+
+- Read root `INSTRUCTION.md` first.
+- Then read this directory `README.md` for navigation.
+- Keep edits minimal, structured, and traceable.
+
+## Execution Order
+
+1. Root `INSTRUCTION.md`
+2. This directory `INSTRUCTION.md`
+3. This directory `README.md` and target files
+
+## Boundary
+
+- Root rules win on conflict.

package/templates/en//360/237/221/244 Profile/README.md"

@@ -0,0 +1,15 @@
+# Profile
+
+Primary entry for stable personal context and current operating state.
+
+## Fill First
+
+1. `👤 Identity.md`: who you are (identity, background, key achievements)
+2. `⚙️ Preferences.md`: how you work (tools, communication, writing preferences)
+3. `🎯 Focus.md`: what you are doing now (goals, current focus, routine)
+
+## Maintenance Rules
+
+- Keep it minimal and practical; avoid over-fragmentation.
+- Update `🎯 Focus.md` regularly (for example, weekly).
+- Put stable facts in `👤 Identity.md` and behavior preferences in `⚙️ Preferences.md`.

package/templates/en//360/237/221/244 Profile//342/232/231/357/270/217 Preferences.md"

@@ -0,0 +1,21 @@
+# ⚙️ Preferences
+
+## Work Style
+
+<!-- Working hours, focus style, rest rhythm -->
+
+## Tool Preferences
+
+<!-- Editor, terminal, browser, notes tooling -->
+
+## Communication Preferences
+
+<!-- concise/detailed, Chinese/English, formal/casual -->
+
+## Writing Preferences
+
+<!-- tone, structure preference, wording to avoid -->
+
+## AI Interaction Preferences
+
+<!-- preferred response style, length, and format -->

package/templates/en//360/237/221/244 Profile//360/237/216/257 Focus.md"

@@ -0,0 +1,31 @@
+# 🎯 Focus
+
+> Current-stage snapshot. Update regularly.
+
+## Long-Term Goals (3-5 years)
+
+-
+
+## Annual Goals
+
+-
+
+## Current Quarter Priorities
+
+-
+
+## Current Focus
+
+<!-- What you are working on and current stage -->
+
+## Recent Context
+
+<!-- Important recent events, decisions, or changes -->
+
+## Active Projects
+
+<!-- Project name -> current status / phase -->
+
+## Routine
+
+<!-- Deep-work windows and recurring commitments -->

package/templates/en//360/237/221/244 Profile//360/237/221/244 Identity.md"

@@ -0,0 +1,22 @@
+# 👤 Identity
+
+## Basic Info
+
+- **Name**:
+- **Role**:
+- **Location**:
+- **Organization/Company**:
+
+## Professional Background
+
+<!-- Education, research areas, work experience -->
+
+## Current Roles
+
+<!-- Primary roles: researcher / engineer / founder / student -->
+
+## Key Achievements
+
+- Academic:
+- Product:
+- Other:

package/templates/en//360/237/223/232 Resources/INSTRUCTION.md"

@@ -0,0 +1,29 @@
+# Resources Directory Instruction Set
+
+## Goal
+
+- Define local execution rules for `📚 Resources/`.
+- Standardize maintenance of AI resource index CSV files.
+
+## Local Rules
+
+- Read root `INSTRUCTION.md` first, then this file.
+- This directory is CSV-first; avoid unindexed temporary documents.
+- Reuse existing CSV themes before creating new ones.
+- Validate header and field semantics before appending rows.
+
+## Execution Order
+
+1. Root `INSTRUCTION.md`
+2. This directory `INSTRUCTION.md`
+3. This directory `README.md` and target files
+
+## Boundary
+
+- Root rules win on conflict.
+
+## Sync Rules (Resources)
+
+- On add/rename of CSV files: update `📚 Resources/README.md` structure and usage.
+- On schema changes: sync field semantics across related CSV files.
+- After bulk changes: run `rg` to clean stale references.

package/templates/en//360/237/223/232 Resources/README.md"

@@ -0,0 +1,21 @@
+# Resources
+
+External resource collections and structured indexes.
+
+## Structure
+
+```bash
+📚 Resources/
+├── README.md
+├── INSTRUCTION.md
+├── 🧾 AI Products.csv
+├── 🧾 AI Influencers.csv
+├── 🧾 AI Tools.csv
+└── 🧾 AI Scholars.csv
+```
+
+## Usage
+
+- Use CSV as the primary index for resource tracking.
+- Validate headers and field semantics before appending rows.
+- Follow execution and sync rules in `INSTRUCTION.md`.

package/templates/en//360/237/223/232 Resources//360/237/247/276 AI Influencers.csv"

@@ -0,0 +1 @@
+Name,Platform,Focus,Region,Link,Status,UpdatedAt,Notes

package/templates/en//360/237/223/232 Resources//360/237/247/276 AI Products.csv"

@@ -0,0 +1 @@
+Name,Category,Website,CoreValue,Pricing,Status,UpdatedAt,Notes

package/templates/en//360/237/223/232 Resources//360/237/247/276 AI Scholars.csv"

@@ -0,0 +1 @@
+Name,Institution,ResearchArea,ProfileLink,Region,Status,UpdatedAt,Notes

package/templates/en//360/237/223/232 Resources//360/237/247/276 AI Tools.csv"

@@ -0,0 +1 @@
+Name,Type,PrimaryUse,Website,Pricing,Status,UpdatedAt,Notes

package/templates/en//360/237/223/235 Notes/INSTRUCTION.md"

@@ -0,0 +1,31 @@
+# Notes Directory Instruction Set
+
+## Goal
+
+- Define local execution rules for `📝 Notes/`.
+- Keep quick capture and archive flow consistent.
+
+## Local Rules
+
+- Read root `INSTRUCTION.md` first, then this file.
+- Use this directory for short-lived drafts and capture notes.
+- New notes should start in `Inbox/`, then be routed into `Waiting/`, `Meetings/`, or `Ideas/`.
+- Move stabilized content into domain directories (`👤 Profile/`, `🔄 Workflows/`, `🚀 Projects/`, `📚 Resources/`).
+- Remove or archive source notes after migration when no longer needed.
+
+## Execution Order
+
+1. Root `INSTRUCTION.md`
+2. This directory `INSTRUCTION.md`
+3. This directory `README.md` and target files
+
+## Boundary
+
+- Root rules win on conflict.
+
+## Sync Rules (Notes)
+
+- On add/rename of second-level folders: update `📝 Notes/README.md` structure and usage.
+- Keep filename language and naming policy consistent.
+- On note migration: update affected references to avoid dangling paths.
+- Confirm scope before bulk triage/refactor.

package/templates/en//360/237/223/235 Notes/Ideas/README.md"

@@ -0,0 +1,8 @@
+# Ideas
+
+Idea pool for product concepts, topics, and experiment ideas.
+
+## Usage
+
+- Capture the core idea first, then add validation steps.
+- Promote high-potential ideas into `🚀 Projects/` or `🔄 Workflows/`.

package/templates/en//360/237/223/235 Notes/Ideas//360/237/247/252_example_product_idea.md"

@@ -0,0 +1,16 @@
+# 💡 Product Idea Example: Trust Layer for Personal AI
+
+## Concept
+- Add a "Trust Trace" panel that shows where each generated answer came from in the user's own knowledge base.
+
+## User Promise
+- "You don't just get answers. You see evidence."
+
+## Why It Can Win
+- Converts skepticism into confidence.
+- Creates strong differentiation against black-box assistants.
+
+## Validation Plan
+1. Prototype trace UI in one workflow.
+2. Run 10 user sessions.
+3. Measure confidence score before/after.

package/templates/en//360/237/223/235 Notes/Inbox/README.md"

@@ -0,0 +1,8 @@
+# Inbox
+
+Quick capture area for raw, unprocessed notes.
+
+## Usage
+
+- Capture fast without strict structure.
+- Regularly triage into `Waiting/`, `Meetings/`, `Ideas/`, or domain folders.

package/templates/en//360/237/223/235 Notes/Inbox//360/237/247/252_example_quick_capture.md"

@@ -0,0 +1,14 @@
+# 📝 Quick Capture Example: Viral Positioning Spark
+
+## Raw Input
+- User quote from onboarding call: "I don't need another notes app. I need a system that thinks with me."
+- Candidate promise: "From capture to action in one flow."
+- Hook idea: "MindOS is your second brain with execution memory."
+
+## Why This Matters
+- This line can become the homepage hero message.
+- It directly answers category fatigue and highlights differentiation.
+
+## Next Routing
+- Move positioning statement to `Ideas/`.
+- Move user quote + source link to `Meetings/` evidence note.

package/templates/en//360/237/223/235 Notes/Meetings/README.md"

@@ -0,0 +1,8 @@
+# Meetings
+
+Meeting notes, decisions, and action items.
+
+## Usage
+
+- Record date, attendees, decisions, and action items.
+- Each action item should have an owner and due date.

package/templates/en//360/237/223/235 Notes/Meetings//360/237/247/252_example_meeting_note.md"

@@ -0,0 +1,17 @@
+# 📌 Meeting Note Example: GTM Alignment
+
+## Date
+- 2026-03-10
+
+## Participants
+- Founder, Product, Growth, Content
+
+## Key Decisions
+- Positioning: "MindOS turns scattered knowledge into reliable execution."
+- Primary audience: builders and creators overwhelmed by tool fragmentation.
+- Launch narrative: less setup friction, more weekly momentum.
+
+## Action Items
+- Growth: draft 3 landing page variants by Friday.
+- Product: prepare 60-second onboarding demo.
+- Content: publish case-based thread on consistency gains.

package/templates/en//360/237/223/235 Notes/README.md"

@@ -0,0 +1,24 @@
+# Notes
+
+Quick capture and lightweight notes.
+
+## Structure
+
+```bash
+📝 Notes/
+├── README.md
+├── INSTRUCTION.md
+├── Inbox/
+├── Waiting/
+├── Meetings/
+└── Ideas/
+```
+
+## Usage
+
+- `Inbox/`: quick capture for unprocessed notes.
+- `Waiting/`: items blocked by external dependency or feedback.
+- `Meetings/`: meeting notes, decisions, and action items.
+- `Ideas/`: idea pool for product concepts, topics, and experiments.
+- Move stable knowledge into `👤 Profile/`, `🔄 Workflows/`, `🚀 Projects/`, or `📚 Resources/` regularly.
+- Follow execution and sync rules in `INSTRUCTION.md`.

package/templates/en//360/237/223/235 Notes/Waiting/README.md"

@@ -0,0 +1,8 @@
+# Waiting
+
+Items blocked by external dependency or pending feedback.
+
+## Usage
+
+- Track owner, dependency, and next follow-up date.
+- Move out once dependency is resolved.

package/templates/en//360/237/223/235 Notes/Waiting//360/237/247/252_example_blocked_item.md"

@@ -0,0 +1,16 @@
+# ⏳ Blocked Item Example: Launch Asset Dependency
+
+## Item
+- Marketing launch page cannot publish until new product visuals are approved.
+
+## Owner
+- Design lead
+
+## Dependency
+- Final approval from founder + legal review for testimonial usage.
+
+## Impact If Delayed
+- Delays Product Hunt launch window and partner newsletter slot.
+
+## Next Follow-up
+- 2026-03-15 10:00 AM

package/templates/en//360/237/224/204 Workflows/Configurations/README.md"

@@ -0,0 +1,3 @@
+# Configurations Workflow
+
+Operational workflows for configuration and environment setup.

package/templates/en//360/237/224/204 Workflows/Configurations//360/237/247/252_example_config_update_sop.md"

@@ -0,0 +1,14 @@
+# ⚙️ Configuration Update SOP Example: Zero-Repeat Setup
+
+## Goal
+- Ensure agents can run with minimal reconfiguration across sessions.
+
+## Steps
+1. Update `CONFIG.json` for structured keys.
+2. Update `CONFIG.md` for semantic intent.
+3. Verify naming-level rules (emoji + hierarchy) remain consistent.
+4. Run `rg` sweep for stale paths and obsolete labels.
+5. Validate one real workflow end-to-end.
+
+## Success Criteria
+- New session can execute core flows without extra setup prompts.

package/templates/en//360/237/224/204 Workflows/INSTRUCTION.md"

@@ -0,0 +1,21 @@
+# Directory Instruction Set
+
+## Goal
+
+- Define local execution rules for this first-level directory.
+
+## Local Rules
+
+- Read root `INSTRUCTION.md` first.
+- Then read this directory `README.md` for navigation.
+- Keep edits minimal, structured, and traceable.
+
+## Execution Order
+
+1. Root `INSTRUCTION.md`
+2. This directory `INSTRUCTION.md`
+3. This directory `README.md` and target files
+
+## Boundary
+
+- Root rules win on conflict.

package/templates/en//360/237/224/204 Workflows/Information/README.md"

@@ -0,0 +1,16 @@
+# Information
+
+SOP folder for information collection and knowledge flow.
+
+## Structure
+
+```bash
+Information/
+└── <SOP file>.md
+```
+
+## Usage
+
+- Store search, triage, extraction, and sync procedures.
+- Define source criteria and archive targets when possible.
+- Follow parent rules in `🔄 Workflows/INSTRUCTION.md`.

package/templates/en//360/237/224/204 Workflows/Information//360/237/247/252_example_info_capture_sop.md"

@@ -0,0 +1,13 @@
+# 🔎 Information Capture SOP Example: Signal-First Intake
+
+## Input
+- User interviews, social comments, competitor launches, support tickets.
+
+## Steps
+1. Capture source, date, and quote.
+2. Tag by theme: activation, retention, trust, differentiation.
+3. Extract one actionable product or messaging implication.
+4. Route to `Projects/` if execution is needed this week.
+
+## Outcome
+- Insight backlog that directly feeds roadmap and marketing copy.

package/templates/en//360/237/224/204 Workflows/Media/README.md"

@@ -0,0 +1,16 @@
+# Media
+
+SOP folder for media and content workflows.
+
+## Structure
+
+```bash
+Media/
+└── <SOP file>.md
+```
+
+## Usage
+
+- Store content production, publishing, and review SOPs.
+- Keep procedures concise and executable.
+- Follow parent rules in `🔄 Workflows/INSTRUCTION.md`.

package/templates/en//360/237/224/204 Workflows/Media//360/237/247/252_example_content_publish_sop.md"

@@ -0,0 +1,13 @@
+# 📰 Content Publish SOP Example: Promise-to-Proof Distribution
+
+## Goal
+- Turn product claims into believable public proof.
+
+## Pipeline
+1. Pick one claim (for example: faster weekly execution).
+2. Attach one concrete case or metric.
+3. Publish in 3 formats: short post, visual card, long-form note.
+4. Track saves, replies, and demo requests.
+
+## Quality Gate
+- Every post must include: problem, mechanism, evidence, next action.

package/templates/en//360/237/224/204 Workflows/README.md"

@@ -0,0 +1,22 @@
+# Workflows
+
+Overview and usage guide for workflow SOPs.
+
+## Structure
+
+```bash
+🔄 Workflows/
+├── README.md
+├── INSTRUCTION.md
+├── Research/
+├── Startup/
+├── Media/
+├── Information/
+└── Configurations/
+```
+
+## Usage
+
+- Pick the subdirectory by scenario.
+- Keep SOPs executable and step-oriented.
+- Follow execution and sync rules in `INSTRUCTION.md`.

package/templates/en//360/237/224/204 Workflows/Research/README.md"

@@ -0,0 +1,16 @@
+# Research
+
+SOP folder for research workflows.
+
+## Structure
+
+```bash
+Research/
+└── <SOP file>.md
+```
+
+## Usage
+
+- Store retrievable and executable research SOPs.
+- Keep steps explicit with clear inputs and outputs.
+- Follow parent rules in `🔄 Workflows/INSTRUCTION.md`.

package/templates/en//360/237/224/204 Workflows/Research//360/237/247/252_example_lit_review_sop.md"

@@ -0,0 +1,16 @@
+# 🔬 Literature Review SOP Example: Proof-Backed Product Claims
+
+## Goal
+- Strengthen product messaging with credible research evidence.
+
+## Steps
+1. Search 10 recent papers on memory systems and agent reliability.
+2. Extract 3 claims that map to MindOS value propositions.
+3. Convert each claim into one user-facing sentence + citation note.
+4. Store reusable snippets for landing page and investor updates.
+
+## Output Template
+- Claim:
+- Evidence source:
+- Product implication:
+- Safe marketing phrasing:

package/templates/en//360/237/224/204 Workflows/Startup/README.md"

@@ -0,0 +1,3 @@
+# Startup Workflow
+
+Workflows for startup-related execution (product, development, marketing).

package/templates/en//360/237/224/204 Workflows/Startup//360/237/247/252_example_weekly_founder_ops.md"

@@ -0,0 +1,22 @@
+# 🚀 Weekly Founder Ops Example: Momentum System
+
+## Objective
+- Keep product, growth, and narrative execution aligned every week.
+
+## Monday Setup
+1. Define one growth metric and one product metric.
+2. Pick top 3 bets (ship, distribute, learn).
+3. Set one public proof artifact (demo, post, case).
+
+## Midweek Check
+1. Review blockers and decision latency.
+2. Cut low-leverage work.
+3. Re-allocate time to highest learning loop.
+
+## Friday Review
+1. Publish weekly build log.
+2. Summarize wins, misses, and key evidence.
+3. Convert insights into next-week backlog.
+
+## Marketing Output
+- One narrative asset per week to show compounding progress.

package/templates/en//360/237/224/227 Connections/Classmates/README.md"

@@ -0,0 +1,11 @@
+# Classmates
+
+Track classmates from school or training programs.
+
+## Suggested fields
+
+- Name
+- School or program
+- Cohort or year
+- Current role
+- Notes

package/templates/en//360/237/224/227 Connections/Classmates//360/237/247/252_example_leo_chen.md"

@@ -0,0 +1,16 @@
+# Leo Chen
+
+## Relationship
+- Graduate classmate
+
+## Current Role
+- ML Engineer
+
+## MindOS Relevance
+- Can evaluate technical credibility of agent architecture claims.
+
+## Collaboration Potential
+- Review technical positioning before public launch.
+
+## Next Action
+- Schedule a 30-minute architecture + messaging review.

package/templates/en//360/237/224/227 Connections/Colleagues/README.md"

@@ -0,0 +1,11 @@
+# Colleagues
+
+Track professional contacts across teams and companies.
+
+## Suggested fields
+
+- Name
+- Team or company
+- Role
+- Working style
+- Notes

package/templates/en//360/237/224/227 Connections/Colleagues//360/237/247/252_example_ethan_zhao.md"

@@ -0,0 +1,16 @@
+# Ethan Zhao
+
+## Relationship
+- Former colleague
+
+## Current Role
+- Engineering Lead
+
+## MindOS Relevance
+- Experienced in scaling developer workflows and team adoption.
+
+## Collaboration Potential
+- Can advise adoption strategy for power users and teams.
+
+## Next Action
+- Ask for rollout playbook feedback (pilot -> expansion).

package/templates/en//360/237/224/227 Connections/Connections Overview.csv"

@@ -0,0 +1,5 @@
+Name,Category,Relationship,CurrentRole,Location,Status,LastInteraction,MdPath,UpdatedAt
+James Wang,Family,Father,Retired Teacher,Hangzhou,active,2026-03-01,Family/🧪_example_james_wang.md,2026-03-10
+Lily Lin,Friends,College Friend,Product Manager,Shanghai,active,2026-03-05,Friends/🧪_example_lily_lin.md,2026-03-10
+Leo Chen,Classmates,Graduate School Classmate,ML Engineer,Beijing,warm,2026-02-20,Classmates/🧪_example_leo_chen.md,2026-03-10
+Ethan Zhao,Colleagues,Former Colleague,Engineering Lead,Shenzhen,active,2026-03-08,Colleagues/🧪_example_ethan_zhao.md,2026-03-10

package/templates/en//360/237/224/227 Connections/Family/README.md"

@@ -0,0 +1,11 @@
+# Family
+
+Track important family members and relationship context.
+
+## Suggested fields
+
+- Name
+- Relationship
+- Location
+- Communication preference
+- Notes

package/templates/en//360/237/224/227 Connections/Family//360/237/247/252_example_james_wang.md"

@@ -0,0 +1,16 @@
+# James Wang
+
+## Relationship
+- Father
+
+## Context
+- Former teacher, values long-term discipline and clear routines.
+
+## MindOS Relevance
+- Useful sounding board for habit consistency and weekly planning cadence.
+
+## Collaboration Potential
+- Can review personal execution rhythm and suggest simplification.
+
+## Next Action
+- Share monthly reflection summary and ask for one improvement suggestion.

package/templates/en//360/237/224/227 Connections/Friends/README.md"

@@ -0,0 +1,11 @@
+# Friends
+
+Track close friends and trusted peers.
+
+## Suggested fields
+
+- Name
+- Background
+- Shared interests
+- Collaboration opportunities
+- Notes