Open source

Code and systems, in public

Agent skills, design tooling, and demo pipelines from the practice. Nothing here is a slide about AI. It is public code and provenance, reviewed before adoption.

5 REPOS · 3 AGENT SKILLS · 8-CHECK REVIEW · github.com/andrewluxem

Agent skills

Portable skills, no external network access.

customer-journey-lifecycle

A portable agent skill for customer-state modeling, lifecycle journey design, contact governance, and incremental measurement.

SKILL.MD · LIFECYCLE · MEASUREMENT

View on GitHub

generational-marketing-review

A portable agent skill for reviewing marketing plans and assets for generational audience fit.

SKILL.MD · AUDIENCE · REVIEW

View on GitHub

decision-card

A static Claude skill that stress-tests a decision and returns an answer-first card. Explicit invocation only: no self-firing, no remote fetch, no auto-update.

SKILL.MD · DECISIONS · STATIC

View on GitHub

Tooling and pipelines

Infrastructure for the design and demo work.

penpot-throughline

A Penpot port of ThroughLine, the Claude Code plugin that syncs design tokens and components from a design tool into a monorepo. Targets self-hosted Penpot, so no Figma license is required. Pre-alpha and in active development.

PENPOT · DESIGN TOKENS · PRE-ALPHA

View on GitHub

ultrademo

Demo video pipeline: Playwright capture to TTS to Remotion render. A provenance-pinned copy of new-xp/ultrademo with a conditional audit recorded for that commit.

TYPESCRIPT · PLAYWRIGHT · REMOTION

View on GitHub

Method

The audit before adoption

Every repository, fork, and third-party tool goes through the same eight-point review before it is adopted or recommended: where it came from, how it is licensed, what it depends on, whether it reaches the network, how it is invoked, how it updates, how it handles data, and how much it can break. The skepticism I bring to a vendor deck, pointed at code.

01 PROVENANCE
02 LICENSE
03 DEPENDENCIES
04 NETWORK CALLS
05 INVOCATION
06 UPDATE PATH
07 DATA HANDLING
08 BLAST RADIUS

The playbook library is built for execution

The library is structured for execution. The 3Ps framework currently ships as a downloadable skill, with additional packages added only as their source content is completed.

Browse the skills library