npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

livecv

v1.6.6

Published

Your portfolio answers questions. Define a KB, render a live persona.

Downloads

303

Readme

livecv

Your portfolio answers questions.

Define a KB. Render a live persona.

npm version license

Demo · Example · npm · Issues


What is it

Static portfolios show every visitor the same page. livecv turns a typed config + markdown KB into a generative-UI portfolio: a visitor types a question, an LLM picks components from a Zod-typed catalog, and the page assembles itself live as the answer.

Same site, different shape per visitor. A recruiter sees the patent and the metrics. A friend sees the writing. A founding-team CEO sees the agent-infrastructure thinking.

Built on top of @json-render (the streaming renderer + Zod catalog runtime) and Anthropic's Claude.

Bootstrap from a resume (fastest path)

livecv has a companion Claude Code skill that scaffolds a complete project from a resume PDF. The skill is in this repo's skill/livecv/ folder — not bundled in the npm tarball.

Install the skill (two commands, no Node tooling required):

git clone --depth=1 https://github.com/sayantan94/livecv.git
cp -r livecv/skill/livecv ~/.claude/skills/livecv

Use it:

claude -p "use the livecv skill to scaffold ./my-portfolio from ./resume.pdf"

Claude Code reads the PDF natively, extracts identity + career + projects + patent + education, writes 17 files (the same structure as example/), and prints next steps. Then: cd my-portfolio && cp .env.local.example .env.local && npm install && npm run dev.

Identity, career, and projects files are generated dynamically using livecv's defineXxx constructors — their shape depends on what's actually on the resume.

If you'd rather set up by hand, keep reading.

Install

npm install livecv \
  @ai-sdk/anthropic @ai-sdk/react ai \
  @json-render/core @json-render/react @json-render/shadcn \
  motion lucide-react zod

Four files. That's the whole user surface.

my-portfolio/
├── livecv.config.ts          — typed config (identity, career, projects, blog)
├── content/kb.md             — prose KB (voice, principles, what you're focused on)
├── app/page.tsx              — <PersonaSite config={config} />
└── app/api/generate/route.ts — export const POST = createHandler({ config })

Quick start

1. Config — assemble your persona with the typed constructors:

// livecv.config.ts
import fs from "node:fs";
import path from "node:path";
import {
  defineConfig,
  defineIdentity,
  defineCareer,
  defineProjects,
  defineClusters,
  defineBlog,
} from "livecv";

const identity = defineIdentity({
  name: "Jane Doe",
  role: "Software Engineer",
  bio: "...",
  email: "[email protected]",
  links: { github: "https://github.com/janedoe" },
});

const career = defineCareer([
  { start: "2024", end: "Present", title: "Senior Engineer", org: "Foo",
    detail: "...", tech: ["TypeScript"], status: "current" },
]);

const projects = defineProjects([
  { id: "thing", title: "thing", tldr: "...", description: "...",
    tech: ["TypeScript"], cluster: "tools",
    howItWorks: ["..."], keyInsight: "..." },
]);

const clusters = defineClusters([{ id: "tools", label: "Tools" }]);
const blog = defineBlog([]);

export default defineConfig({
  identity, career, projects, clusters, blog,
  kbContent: fs.readFileSync(path.join(process.cwd(), "content/kb.md"), "utf-8"),
  model: "claude-haiku-4-5",
});

2. Page — five lines:

// app/page.tsx
import { PersonaSite } from "livecv";
import config from "@/livecv.config";

export default function Page() {
  return <PersonaSite config={config} />;
}

3. API route — five lines:

// app/api/generate/route.ts
import { createHandler } from "livecv";
import config from "@/livecv.config";

export const POST = createHandler({ config });
export const maxDuration = 60;

4. Styles — three imports:

/* app/globals.css */
@import "tailwindcss";
@import "livecv/styles.css";
@import "livecv/theme.css";

5. Env — one variable:

# .env.local
ANTHROPIC_API_KEY=sk-ant-...

npm run dev. You have a live persona portfolio.

What renders

The LLM picks from this catalog per question:

| Component | When it renders | |---|---| | ProfileBlock | "who are you", "about" | | CareerTimeline | "career", "background" — supports focus + highlightTech for topical lensing | | ProjectGrid | "show me your X work" — filtered by cluster | | ProjectDeepDive | specific project by id | | TechStack | tag cloud sized by frequency | | BlogList / BlogPostCard | your writing | | PrincipleList | philosophy questions only | | LeadershipStories | STAR-format experience stories — fresh per question | | ProofPoints | tag + claim + evidence rows | | PersonalNote | one-sentence first-person opener | | Callout / Text / Link | prose primitives |

Project IDs, blog slugs, and cluster IDs become Zod enums automatically — the LLM cannot reference an artifact that doesn't exist. Bad specs fail validation and the renderer falls back gracefully.

Example

A complete starter template lives in example/ — a fictional "Jordan Lee, Staff Engineer" persona with 3 career steps, 4 projects across 3 clusters, 3 blog posts, and a prose KB. Clone, replace data, deploy.

cd example
cp .env.local.example .env.local   # paste your Anthropic key
npm install
npm run dev

Theme

Override any CSS variable from livecv/theme.css in your own stylesheet:

:root {
  --lc-foreground: #000;
  --lc-background: #fff;
  /* ... */
}

Dark mode = .dark class on <html> (or any ancestor).

Reference implementation

ai.sayantan.sh is the real-world site this was extracted from. Same code, real persona. The companion blog post walks through the architecture decisions.

License

MIT © Sayantan Bhowmik