PWV Portfolio Feed

tested on real macOS apps (VS Code, MTLReplayer, etc). handles nested dicts, arrays, dates, buffers, booleans. all the plist types.

built with Command Code. following the taste system for consistency.

if you work with plists and want modern tooling, give it a try.

const data = parse(xmlString);

build js objects back to xml:
const { build } = require('plist-next');
const xml = build(data);

also ships with a CLI:
$ npm install -g plist-cli
$ plist parse Info.plist
$ plist build '{"name":"app"}'

• Zod validation at boundaries — catch errors early
• 45 comprehensive tests — edge cases covered
• ESM + CJS — both module formats, tree-shakeable
• Zero CLI dependencies — library stays lean

$ npm install plist-next

parse xml plists to js objects:
const { parse } = require('plist-next');

introducing plist-next 📋

i wanted a modern plist parser that just works. no bloat, no legacy baggage, just typescript + strict types + zod validation.

the original plist.js is solid, but it's 2026. we can do better.

plist-next:
• TypeScript first — strict mode, full type safety

Know a woman building with AI? Drop a link. 👇

“I built this app to solve my own pain-point. Most options on the market are tailored to children and feel demotivating to me as an adult learner.”

Know a woman building with AI? Drop a link. 👇

if you're using coding agents seriously, curious what surprised you most about how your workflow actually changed.

here's what i didn't expect: rebuilding old projects to teach Command Code my taste is more valuable than i thought. each one reinforces patterns i want the agent to know. not because my way is universal, but because consistency matters when you're working at this pace.

the result isn't just speed. it's that i can trust the output without the usual "let me rewrite half of this" step. i'm shipping a project most days now because the friction dropped to nearly zero.

what changed: the agent actually learns how i code. my guard clause preference. my CLI patterns from 200+ tools over 10 years. functional style. it picks up my architecture decisions without me explaining them every time.

stopped watching TV lately. not because i'm disciplined. because building with coding agents (Command Code) became more interesting than Netflix.

sounds absurd. but i'm polyphasic. wake up twice a day. used to split it: once for work, once for TV. now both sessions are building sessions.

⌘ let's go!!

applescript and shell logic is preserved as searchable text. rich text is stripped to plain text. no manual exports. no noise. no leaks.

$ 𝚗𝚙𝚡 𝚝𝚎𝚡𝚝𝚎𝚡𝚙𝚊𝚗𝚍𝚎𝚛-𝚝𝚘-𝚛𝚊𝚢𝚌𝚊𝚜𝚝

if you are optimizing your local setup, this should save you quite a few gradient descent steps.