Mark-Life
- 12 skills
- 0 followers
- 16 hours ago last updated
- ▌ Product · mark-life bundlePrimitive-first product design. Use when shaping a new product, app, SDK, API, or tool surface, deciding what to build and what to leave to the caller, writing a spec or PRD, or judging whether an idea is worth building.
- ▌ Pr Issue · mark-life bundleUse when writing a pull request, issue, or ticket — title or body — or before running `gh pr create` or `gh issue create`.
- ▌ Media Cdn · mark-life bundleUse for public file uploading: when a screenshot, GIF, or video has to be embedded in a PR, issue, doc, or message.
- ▌ New Project · mark-lifeUse when starting a brand-new project or repository from scratch. Triggers on "create a new project", "spin up a new app", "scaffold a new repo", "start a new Next.js project". Scaffolds from the personal Next.js monorepo template (Mark-Life/netxjs-monorepo) and runs the standard bootstrap.
- ▌ Agent To Human · mark-lifeUse when producing the final output a person will read — a chat reply, summary, status update, handoff, or a PR, issue, or commit message — not your private reasoning. Triggers on wrapping up a task or reporting back to the user.
- ▌ Human To Agent · mark-lifeUse when writing or editing instructions a model will later execute — anything future context windows load as guidance. Triggers on 'edit this skill', 'update CLAUDE.md / AGENTS.md', 'write agent rules', 'improve this prompt'.
- ▌ Memory View · mark-life bundleA viewer for Claude Code's per-project auto-memory. A zero-dep TypeScript script scans ~/.claude/projects/<project>/memory/, renders a self-contained, secret-redacted HTML explorer, and opens it in the browser. No model curation, no edits, no findings — the model only runs the script and opens the report. Local, human-facing, never auto-fired.
- ▌ Observability · mark-life bundleObservability for TypeScript services: one wide event per request or job, high-cardinality fields, span and metric design, OTel export, tail sampling. Use when adding or reviewing logging, tracing, telemetry, metrics or OTel wiring, deciding what a request or job should record, or debugging production from what a service already emits. Owns instrumentation decisions — prefer over general TypeScript-quality guidance. Triggers on 'add logging', 'instrument this', 'add tracing', 'wire up OTel', 'I can't tell what happened in prod'.
- ▌ Context Doctor · mark-lifeAudit and shrink the fixed context a coding agent auto-loads every session — tool/MCP definitions, plugins, skills, subagents, memory/rules files, built-in tools & feature subsystems — by pruning, gating, denying, or routing what's loaded but unused. User-invoked: type it when the context feels bloated.
- ▌ Harness Doctor · mark-life bundleAudit the last N days of agent transcripts across every project at once and find where wall-clock, tokens, and repeated human corrections are going. A zero-dependency script mines every transcript into five fact tables and prints a summary; the model reads the numbers, digs into the tables, and returns a ranked, copy-pasteable list of fixes to the repo, the config, and the rules files.
- ▌ Session Report · mark-life bundleGenerate a self-contained HTML report that debugs what is in a Claude Code or Codex session's context window and how every token is spent — context budget, the hidden cost of retained thinking, the dumb-zone cutoff, loaded CLAUDE.md/skills, and the full history.
- ▌ Writing For Readers · mark-life bundleWriting prose a reader chose to read. Use when drafting or editing a blog post, article, docs page, landing page or newsletter, or when a draft reads like AI. For output handed back to the user, use agent-to-human.