@researai/meos 0.1.0

package/SKILL/assets/examples/minimal/principles/tradeoffs.md

@@ -0,0 +1,14 @@
+# Trade-offs
+
+## Core priorities
+
+1. truth of the system
+2. route convergence
+3. verification and durability
+4. user-facing clarity
+5. implementation speed
+
+## Typical stance
+
+- Prefer reuse over reinvention.
+- Prefer root-cause fixes over cosmetic fixes.

package/SKILL/assets/examples/minimal/taste/ui-product.md

@@ -0,0 +1,14 @@
+# UI And Product Taste
+
+## Visual direction
+
+- low saturation
+- restrained contrast
+- clear hierarchy
+- intentional, minimal chrome
+
+## Anti-goals
+
+- decorative complexity without contract clarity
+- fake progress
+- duplicate views for the same object

package/SKILL/assets/examples/minimal/thought-style/reasoning-patterns.md

@@ -0,0 +1,14 @@
+# Reasoning Patterns
+
+## Preferred decomposition
+
+1. identify the object
+2. identify the truth source
+3. identify the governing contract
+4. find the mismatch
+5. choose the smallest convergent fix
+
+## Validation stance
+
+- A specific user suspicion is evidence and should be checked directly.
+- Broader system-health narration comes after that verification, not before.

package/SKILL/assets/examples/minimal/work/technical-standards.md

@@ -0,0 +1,16 @@
+# Technical Standards
+
+## Architecture
+
+- Identify the real source of truth before patching a visible symptom.
+- Prefer one convergent system over several overlapping partial systems.
+
+## Verification
+
+- Do not call an implementation done until the real acceptance gate is checked.
+- Separate source edits from live-behavior verification.
+
+## Acceptance Gates
+
+- If the user asked about one concrete runtime parameter, verify that parameter directly.
+- If only control files changed, say so plainly and do not present that as a new measured result.

package/SKILL/assets/examples/minimal/workflow/default-operating-sequence.md

@@ -0,0 +1,16 @@
+# Default Operating Sequence
+
+## Planning-first mode
+
+1. read the relevant files
+2. state the contract
+3. propose one main route
+4. list real risks
+5. wait for approval
+
+## Execution mode
+
+1. identify the acceptance gate
+2. make the smallest coherent change
+3. verify the real behavior
+4. report what changed and what remains unverified

package/SKILL/assets/examples/product/README.md

@@ -0,0 +1,7 @@
+# Product Example
+
+This example should demonstrate:
+
+- UI taste
+- product clarity standards
+- frontend / backend coordination habits

package/SKILL/assets/examples/product/corrections/overrides.md

@@ -0,0 +1,4 @@
+# Overrides
+
+- Better-looking should not mean more random components.
+- A UI enhancement is incomplete if the running app still shows the old surface.

package/SKILL/assets/examples/product/principles/tradeoffs.md

@@ -0,0 +1,7 @@
+# Trade-offs
+
+## Preferred trade-offs
+
+- prefer coherent flows over flashy one-off screens
+- prefer explicit forms and guided steps over ambiguous hidden controls
+- prefer readability over visual noise

package/SKILL/assets/examples/product/taste/ui-product.md

@@ -0,0 +1,15 @@
+# UI And Product Taste
+
+## Visual direction
+
+- light background
+- restrained motion
+- clean hierarchy
+- not cluttered
+
+## Anti-goals
+
+- generic AI cards everywhere
+- unrelated gradients
+- fake complexity
+- decorative motion without semantic purpose

package/SKILL/assets/examples/product/thought-style/reasoning-patterns.md

@@ -0,0 +1,13 @@
+# Reasoning Patterns
+
+## Preferred framing
+
+- what does the user actually see?
+- what does the backend actually persist?
+- what contract should connect the two?
+- which layer is stale?
+
+## Design rule
+
+- explanatory power beats decoration
+- style is only good when it clarifies the product, not when it hides it

package/SKILL/assets/examples/product/work/technical-standards.md

@@ -0,0 +1,10 @@
+# Technical Standards
+
+## Product Contracts
+
+- Frontend, backend, validation, and saved state must agree.
+- User-facing settings and admin flows are first-class product surfaces.
+
+## Verification
+
+- If the user says a change is not visible, verify the actual rendered surface, not just the source files.

package/SKILL/assets/examples/product/workflow/default-operating-sequence.md

@@ -0,0 +1,16 @@
+# Default Operating Sequence
+
+## UI improvement workflow
+
+1. identify the real page and component path
+2. define visual direction
+3. preserve contract clarity
+4. implement
+5. verify the changed behavior in the running app
+
+## Admin or settings workflow
+
+1. verify payloads
+2. verify validation rules
+3. verify persistence
+4. verify user-visible state

package/SKILL/assets/examples/research/README.md

@@ -0,0 +1,7 @@
+# Research Example
+
+This example should demonstrate:
+
+- evidence handling
+- experiment inventory logic
+- paper and appendix separation

package/SKILL/assets/examples/research/corrections/overrides.md

@@ -0,0 +1,4 @@
+# Overrides
+
+- Do not say the paper is complete if the user is explicitly asking to continue supplementary work.
+- Do not say an experiment is healthy when the user asked about a specific runtime parameter that has not yet been checked.

package/SKILL/assets/examples/research/principles/tradeoffs.md

@@ -0,0 +1,11 @@
+# Trade-offs
+
+## Preferred trade-offs
+
+- prefer claim honesty over rhetorical polish
+- preserve old experiments if still relevant
+- only run new supplementary experiments when there is a real evidence gap
+
+## Boundaries
+
+- do not let a paper-ready state erase a new explicit user request for continuation

package/SKILL/assets/examples/research/taste/ui-product.md

@@ -0,0 +1,15 @@
+# UI And Product Taste
+
+## Research-facing surfaces
+
+- branch-centric or evidence-centric views are preferred over arbitrary node clutter
+- if a result is claimed complete, the UI should make the supporting files and mappings easy to inspect
+
+## Progress surfaces
+
+- completed
+- running
+- blocked
+- next checkpoint
+
+These should be separated clearly.

package/SKILL/assets/examples/research/thought-style/reasoning-patterns.md

@@ -0,0 +1,12 @@
+# Reasoning Patterns
+
+## Preferred research framing
+
+- identify what is already measured
+- identify what is only documented
+- identify what is mapped into the paper
+- identify what remains a real evidence gap
+
+## Continuation rule
+
+- If the user explicitly asks for more experiments or a fuller paper, switch from closeout logic to continuation logic.

package/SKILL/assets/examples/research/work/technical-standards.md

@@ -0,0 +1,12 @@
+# Technical Standards
+
+## Research Contracts
+
+- Baseline, idea, experiment, analysis, writing, review, and rebuttal should remain explicit stages.
+- Supplementary experiments should map back to claims, sections, or evidence gaps.
+- A compile-clean paper is not necessarily an evidence-complete paper.
+
+## Measurement
+
+- Progress should report completed tasks, active tasks, blockers, and the next meaningful checkpoint.
+- User-specified performance targets such as throughput or batch size should be treated as explicit acceptance gates.

package/SKILL/assets/examples/research/workflow/default-operating-sequence.md

@@ -0,0 +1,17 @@
+# Default Operating Sequence
+
+## Experiment workflow
+
+1. verify runtime configuration
+2. run bounded smoke
+3. launch the real run
+4. monitor using quantitative checkpoints
+5. record the result durably
+
+## Paper workflow
+
+1. check compile status
+2. check page-count status
+3. check evidence-mapping status
+4. check appendix status
+5. check remaining scientific gaps

package/SKILL/assets/knowledge/README.md

@@ -0,0 +1,3 @@
+# Knowledge Assets
+
+Store stable semantic, episodic, and procedural knowledge here after promotion from evidence.

package/SKILL/assets/knowledge/episodic.md

@@ -0,0 +1,10 @@
+# Episodic Knowledge
+
+Use this file for durable historical lessons that may still matter.
+
+## Suggested sections
+
+- Past failures and why they mattered
+- Past successful patterns
+- Important route changes
+- Recoverable lessons

package/SKILL/assets/knowledge/procedural.md

@@ -0,0 +1,10 @@
+# Procedural Knowledge
+
+Use this file for repeatable procedures and SOPs.
+
+## Suggested sections
+
+- Debug routines
+- Audit routines
+- Build or deploy routines
+- Research routines

package/SKILL/assets/knowledge/semantic.md

@@ -0,0 +1,10 @@
+# Semantic Knowledge
+
+Use this file for stable conceptual or domain knowledge.
+
+## Suggested sections
+
+- Core concepts
+- Technical vocabulary
+- Domain facts
+- Reusable distinctions

package/SKILL/assets/live/README.md

@@ -0,0 +1,5 @@
+# Live Assets
+
+This directory is for actual promoted local assets.
+
+It is ignored by default.

package/SKILL/assets/preferences/README.md

@@ -0,0 +1,3 @@
+# Preference Assets
+
+Store stable input, output, and interest preferences here.

package/SKILL/assets/preferences/input.md

@@ -0,0 +1,3 @@
+# Input Preferences
+
+Use this file for stable preferences about how requests and context should be framed.

package/SKILL/assets/preferences/interests.md

@@ -0,0 +1,5 @@
+# Interests
+
+Use this file for active but reusable interests.
+
+Prefer durable themes over temporary curiosity spikes.

package/SKILL/assets/preferences/output.md

@@ -0,0 +1,3 @@
+# Output Preferences
+
+Use this file for stable preferences about output shape, density, and explanation style.

package/SKILL/assets/principles/README.md

@@ -0,0 +1,3 @@
+# Principles Assets
+
+Store trade-offs, boundaries, first-principles rules, and risk preferences here.

package/SKILL/assets/principles/tradeoffs.md

@@ -0,0 +1,10 @@
+# Trade-offs
+
+Use this file for stable trade-off rules and boundaries.
+
+## Suggested sections
+
+- Speed vs rigor
+- Simplicity vs completeness
+- Reuse vs reinvention
+- Local optimization vs system convergence

package/SKILL/assets/taste/README.md

@@ -0,0 +1,3 @@
+# Taste Assets
+
+Store durable UI, product, and presentation preferences here.

package/SKILL/assets/taste/ui-product.md

@@ -0,0 +1,11 @@
+# UI And Product Taste
+
+Use this file for durable visual and product judgment rules.
+
+## Suggested sections
+
+- Visual direction
+- Layout preferences
+- Motion rules
+- Anti-goals
+- Review checklist

package/SKILL/assets/templates/README.md

@@ -0,0 +1,3 @@
+# Templates
+
+This directory contains canonical asset templates for building a live MeOS profile.

package/SKILL/assets/templates/corrections/overrides.template.md

@@ -0,0 +1,3 @@
+# Overrides Template
+
+Use this file for explicit corrections that override older inferred rules.

package/SKILL/assets/templates/knowledge/episodic.template.md

@@ -0,0 +1,7 @@
+# Episodic Knowledge Template
+
+## Past failures
+
+## Past successes
+
+## Route changes

package/SKILL/assets/templates/knowledge/procedural.template.md

@@ -0,0 +1,9 @@
+# Procedural Knowledge Template
+
+## Debug routines
+
+## Audit routines
+
+## Build and deploy routines
+
+## Research routines

package/SKILL/assets/templates/knowledge/semantic.template.md

@@ -0,0 +1,7 @@
+# Semantic Knowledge Template
+
+## Core concepts
+
+## Technical vocabulary
+
+## Domain facts

package/SKILL/assets/templates/preferences/input.template.md

@@ -0,0 +1,5 @@
+# Input Preferences Template
+
+## Request framing
+
+## Context density

package/SKILL/assets/templates/preferences/interests.template.md

@@ -0,0 +1,5 @@
+# Interests Template
+
+## Durable interests
+
+## Temporary interests

package/SKILL/assets/templates/preferences/output.template.md

@@ -0,0 +1,7 @@
+# Output Preferences Template
+
+## Structure
+
+## Density
+
+## Explanation style

package/SKILL/assets/templates/principles/tradeoffs.template.md

@@ -0,0 +1,9 @@
+# Trade-offs Template
+
+## Speed vs rigor
+
+## Reuse vs reinvention
+
+## Simplicity vs completeness
+
+## Local optimization vs system convergence

package/SKILL/assets/templates/taste/ui-product.template.md

@@ -0,0 +1,11 @@
+# UI And Product Taste Template
+
+## Visual direction
+
+## Layout
+
+## Motion
+
+## Anti-goals
+
+## Review checklist

package/SKILL/assets/templates/thought-style/reasoning-patterns.template.md

@@ -0,0 +1,9 @@
+# Reasoning Patterns Template
+
+## Preferred decomposition style
+
+## Contract reasoning
+
+## Verification-first habits
+
+## Route selection heuristics

package/SKILL/assets/templates/work/technical-standards.template.md

@@ -0,0 +1,11 @@
+# Technical Standards Template
+
+## Architecture
+
+## Truth sources
+
+## Verification standards
+
+## Acceptance gates
+
+## Cross-layer consistency

package/SKILL/assets/templates/workflow/default-operating-sequence.template.md

@@ -0,0 +1,11 @@
+# Default Operating Sequence Template
+
+## Planning-first mode
+
+## Immediate-implementation mode
+
+## Audit mode
+
+## Debug mode
+
+## Continuation mode

package/SKILL/assets/thought-style/README.md

@@ -0,0 +1,3 @@
+# Thought Style Assets
+
+Store reusable reasoning habits, decomposition patterns, and decision heuristics here.

package/SKILL/assets/thought-style/reasoning-patterns.md

@@ -0,0 +1,10 @@
+# Reasoning Patterns
+
+Use this file for stable problem-framing and decision-making patterns.
+
+## Suggested sections
+
+- Preferred decomposition style
+- Symptom vs root-cause habits
+- Verification-first rules
+- Route-selection heuristics

package/SKILL/assets/work/README.md

@@ -0,0 +1,3 @@
+# Work Assets
+
+Store stable technical standards, implementation norms, and acceptance rules here.

package/SKILL/assets/work/technical-standards.md

@@ -0,0 +1,11 @@
+# Technical Standards
+
+Use this file for stable technical execution standards.
+
+## Suggested sections
+
+- Architecture
+- Truth sources
+- Verification standards
+- Acceptance gates
+- Cross-layer consistency rules

package/SKILL/assets/workflow/README.md

@@ -0,0 +1,3 @@
+# Workflow Assets
+
+Store stable operating sequences for planning, implementation, audit, verification, and continuation here.

package/SKILL/assets/workflow/default-operating-sequence.md

@@ -0,0 +1,11 @@
+# Default Operating Sequence
+
+Use this file for reusable working sequences.
+
+## Suggested sections
+
+- Planning-first mode
+- Immediate-implementation mode
+- Audit mode
+- Debug mode
+- Continuation mode

package/SKILL/evidence/README.md

@@ -0,0 +1,11 @@
+# Evidence Layer
+
+This directory is for local evidence records only.
+
+Examples of local files that may appear here later:
+
+- `facts.jsonl`
+- `conflicts.jsonl`
+- `source-map.json`
+
+By default, this directory stays out of version control except for this README.

package/SKILL/private/README.md

@@ -0,0 +1,12 @@
+# Private Layer
+
+This directory is for raw imported material and local-only snapshots.
+
+Examples:
+
+- imported conversation archives
+- raw transcript dumps
+- temporary sanitized copies
+- local snapshots before extraction
+
+By default, this directory stays out of version control except for this README.

package/SKILL/references/apply-task-map.md

@@ -0,0 +1,42 @@
+# Apply Task Map
+
+Paths below are relative to the installed skill root.
+
+## Technical implementation
+
+Read:
+
+- `assets/live/work/`
+- `assets/live/thought-style/`
+- `assets/live/workflow/`
+- `assets/live/principles/`
+
+## UI / product work
+
+Read:
+
+- `assets/live/taste/`
+- `assets/live/work/`
+- `assets/live/workflow/`
+- `assets/live/corrections/`
+
+## Research or writing work
+
+Read:
+
+- `assets/live/work/`
+- `assets/live/thought-style/`
+- `assets/live/principles/`
+- `assets/live/knowledge/`
+- `assets/live/workflow/`
+
+## Style-sensitive replies
+
+Read:
+
+- `assets/live/preferences/`
+- `assets/live/corrections/`
+
+## Priority rule
+
+If a rule in `assets/live/corrections/` conflicts with another layer, the correction wins.

package/SKILL/references/asset-taxonomy.md

@@ -0,0 +1,47 @@
+# Asset Taxonomy
+
+## Stable asset families
+
+- `assets/work/`
+  - technical standards
+  - acceptance rules
+  - architecture preferences
+- `assets/thought-style/`
+  - decomposition habits
+  - contract reasoning
+  - validation stance
+- `assets/workflow/`
+  - planning routines
+  - implementation routines
+  - audit routines
+  - verification routines
+- `assets/principles/`
+  - trade-offs
+  - risk boundaries
+  - first-principles rules
+- `assets/taste/`
+  - UI taste
+  - product taste
+- `assets/knowledge/`
+  - semantic
+  - episodic
+  - procedural
+- `assets/preferences/`
+  - input
+  - output
+  - interests
+- `assets/corrections/`
+  - explicit overrides
+
+## Promotion guidance
+
+Promote into:
+
+- `work/` when the rule affects technical execution across tasks
+- `thought-style/` when the rule changes how problems are framed
+- `workflow/` when the rule is a repeatable sequence
+- `principles/` when the rule is a stable trade-off or boundary
+- `taste/` when the rule changes UI or product judgment
+- `knowledge/` when the rule is factual or procedural background
+- `preferences/` when the rule is mainly about style or favored presentation
+- `corrections/` when the user explicitly overrides prior understanding