mirror of
https://github.com/openprose/prose.git
synced 2026-09-19 05:55:05 +08:00
irl-dan
63c8ce4b23
Move the standard library (previously `github.com/openprose/std`) and
the company-as-prose library (previously local dir
`/Users/sl/code/openprose/company-as-prose`) into this repository
under `packages/std/` and `packages/co/` respectively.
Motivation: concentrate attention on one repository so stars,
discussions, and issues aggregate. `openprose/std` was a genuinely
useful asset nobody could find because ~50 stars on its own repo
told a much worse story than 1,106 stars on `openprose/prose`
would have. Same logic applies to co.
Layout choice: `packages/{std,co}/` rather than `std/` + `co/` at
the repo root. Root siblings accumulate over time, and a flat
top-level made future libraries (hub, kit, dev, etc.) compete with
spec infrastructure. `packages/` is bounded — new libraries land
there without cluttering root. Matches pnpm/Deno/monorepo tooling
conventions.
Changes:
- New: `packages/std/` (copied from openprose/std, `.git` excluded)
- New: `packages/co/` (copied from company-as-prose, README updated
for new name and location)
- `packages/std/README.md`: updated shorthand expansion reference
- `packages/co/README.md`: renamed "company-as-prose" to "co" in
self-references, added std-vs-co split heuristic, updated
`prose run` examples to use `co/` shorthand
- `skills/open-prose/deps.md`:
- `std/` shorthand now expands to
`github.com/openprose/prose/packages/std/`
- `co/` shorthand added, expands to
`github.com/openprose/prose/packages/co/`
- Both shorthands resolve into the same clone of
`openprose/prose` under `.deps/github.com/openprose/prose/`;
`packages/std/` and `packages/co/` are sibling subdirectories
- `prose.lock` format row updated to `host/owner/repo sha`
(matches the explicit-host resolution that landed in #35)
- `.deps/` directory structure example redrawn to show the
`{host}/{owner}/{repo}/packages/{std,co}/...` shape
- Error message and Interaction tables refreshed accordingly
- Resolution Algorithm step 1 now documents both shorthands
- `skills/open-prose/forme.md`: Step 2 resolution list updated to
include co/ shorthand and the host-keyed `.deps/` layout
- `skills/open-prose/help.md`: Q&A "How do dependencies work?"
rewritten to name both shorthands and the new explicit-host model
- `skills/open-prose/state/filesystem.md`: `.deps/` directory
tree re-drawn to include the `{host}/` layer with std/co as
sibling packages inside the clone
- `skills/open-prose/guidance/patterns.md`,
`skills/open-prose/guidance/antipatterns.md`: examples now use
the `std/` shorthand or explicit `github.com/...` rather than
the deprecated bare `openprose/std/` form
- `skills/open-prose/examples/registry-import/index.md`: sample
service reference switched to `std/evals/inspector`
- `README.md`: Stdlib badge replaced with internal `packages/std/`
link plus new `packages/co/` link; "Standard Library" section
rewritten as "Libraries" with both packages described
Out of scope for this PR (deliberately):
- Tooling changes to `prose install` and Forme's `.deps/` writer
to adopt the `{host}/{owner}/{repo}/` layout in practice — this
PR is spec-only. Existing tooling continues to work against
whatever layout it currently implements; the spec now describes
the target.
- Retiring the `openprose/std` GitHub repo. Delete that repo
separately after this merges.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
94 lines
2.7 KiB
Plaintext
94 lines
2.7 KiB
Plaintext
# User Memory
|
|
# A persistent agent that learns and remembers across all your projects
|
|
#
|
|
# Usage:
|
|
# prose run @openprose/lib/user-memory --backend sqlite+
|
|
#
|
|
# Recommended backend: sqlite+ (for durable cross-project persistence)
|
|
#
|
|
# Modes:
|
|
# teach: Add new knowledge
|
|
# query: Ask questions
|
|
# reflect: Summarize what you know about a topic
|
|
#
|
|
# The memory agent accumulates knowledge over time. Each interaction
|
|
# builds on previous ones. Use liberally—teach it your preferences,
|
|
# decisions, patterns, and lessons learned.
|
|
|
|
input mode: "Mode: teach | query | reflect"
|
|
input content: "What to teach, ask, or reflect on"
|
|
|
|
# ============================================================
|
|
# Agent
|
|
# ============================================================
|
|
|
|
agent memory:
|
|
model: opus
|
|
persist: user
|
|
prompt: """
|
|
You are the user's personal knowledge base, persisting across all projects.
|
|
|
|
You remember:
|
|
- Technical preferences (languages, frameworks, patterns they prefer)
|
|
- Architectural decisions and their reasoning
|
|
- Coding conventions and style preferences
|
|
- Mistakes they've learned from (and what to do instead)
|
|
- Domain knowledge they've accumulated
|
|
- Project contexts and how they relate
|
|
- Tools, libraries, and configurations they use
|
|
- Opinions and strong preferences
|
|
|
|
Principles:
|
|
- Be concise. Store knowledge efficiently.
|
|
- Prioritize actionable knowledge over trivia.
|
|
- Note confidence levels when uncertain.
|
|
- Update previous knowledge when new info contradicts it.
|
|
- Connect related pieces of knowledge.
|
|
"""
|
|
|
|
# ============================================================
|
|
# Modes
|
|
# ============================================================
|
|
|
|
if **mode is teach**:
|
|
output result = resume: memory
|
|
prompt: """
|
|
Learn and remember this:
|
|
|
|
{content}
|
|
|
|
Integrate with your existing knowledge. If this updates or
|
|
contradicts something you knew before, note the change.
|
|
|
|
Respond with a brief confirmation of what you learned.
|
|
"""
|
|
|
|
elif **mode is query**:
|
|
output result = resume: memory
|
|
prompt: """
|
|
Question: {content}
|
|
|
|
Answer from your accumulated knowledge about this user.
|
|
|
|
If you know relevant context, share it.
|
|
If you're uncertain, say so.
|
|
If you don't know, say that clearly.
|
|
"""
|
|
|
|
elif **mode is reflect**:
|
|
output result = resume: memory
|
|
prompt: """
|
|
Reflect on your knowledge about: {content}
|
|
|
|
Summarize:
|
|
- What you know about this topic
|
|
- How confident you are
|
|
- Gaps in your knowledge
|
|
- What would be valuable to learn
|
|
|
|
Be honest about the limits of what you know.
|
|
"""
|
|
|
|
else:
|
|
throw "Unknown mode: {mode}. Use: teach, query, or reflect"
|