Package Exports

@rewrlution/paper-cli

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@rewrlution/paper-cli) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

Paper

A journaling CLI for developers that builds career intelligence over time.

Write daily. Review now and then. Generate resumes, STAR stories, and coaching from your own words.

Install

npm install -g @rewrlution/paper-cli
paper setup        # pick provider (Anthropic/OpenAI), paste your API key, set your goal

Commands

Write

paper              # guided entry — AI asks 2-3 follow-up questions, then saves
paper add          # open $EDITOR, save
paper log "..."    # quick one-liner append
paper show         # read today's (or any) entry

Review

paper recap                        # last 7 days: standup notes + confirm wins into memory
paper recap --since monday         # from last Monday
paper recap --since yesterday      # daily standup notes
paper recap --days 14              # any window

Career

paper resume       # generate resume from confirmed wins, edit inline
paper star         # compose a STAR interview story from a win
paper coach        # career coaching conversation — knows your wins and goal

Sync (optional)

paper register                     # create a Paper account
paper login                        # log in on another device
paper sync                         # push journals + memory to cloud, pull to other devices
paper logout

Setup

paper import ~/obsidian/daily/    # bring in existing notes, build memory once
paper config --set sync_url=https://your-api.com
paper config --set editor=nvim
paper setup        # re-run onboarding

How it works

You write daily. paper recap periodically digests a window of entries — producing standup bullets and proposed wins you confirm. Confirmed wins live in memory.md. paper resume, paper star, and paper coach all read that memory.

Corrections you make during review ("gyroscope is part of code-video, not its own project") are saved to memory.notes so every future output gets them right — without re-asking.

Storage: five plain-text files in ~/.local/share/paper/:

File	What it is
`journals/YYYYMMDD.md`	your words — immutable, never edited by AI
`memory.md`	what Paper learned about you (you confirm it)
`resume.md`	your resume
`stars/<slug>.md`	STAR interview stories
`coach/<timestamp>.md`	saved coach conversations

Sync (multi-device)

Journals and memory sync via a small API backed by Supabase. See docs/DEPLOYMENT.md for the full setup — it takes about 15 minutes.

Short version:

Deploy packages/api/ to Render (free tier works)
paper config --set sync_url=https://your-api.onrender.com
paper register
paper sync

Documentation

Product Design — vision, principles, command reference
Data Structures — storage layer and formats
Architecture — code layout, layer boundaries
Deployment — running the full stack (API + CLI sync)
Roadmap — what's built and what's next