Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
These skills turn messy transcripts and workflow sketches into structured artifacts: affordance tables, framing documents, and kickoff references. The shaping methodology iterates on problem definition and solution options, while breadboarding makes the resulting parts map explicit. Breadboard analysis then checks the map against code for naming resistance, hidden stores, and incoherent wiring. The audience includes product designers, technical leads, and project shapers who need to keep design decisions visible and testable.
WHO IT'S FOR
Product Managers and Product Designers
shaping product solutions and mapping system interactions
Software Architects and Engineers
mapping existing systems and analyzing design smells
UX Researchers and Design Researchers
creating framing documents from conversation transcripts
Project Managers and Team Leads
documenting shaped project kickoffs for builder reference
Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.
Follow the documented setup, then try a first task.
Claude Code — Shaping Skills bundle (obsolete)
Installs: Installs the documented Shaping Skills bundle entries: framing-doc, kickoff-doc, breadboarding, and shaping. The author marks these skills obsolete. · Claude Code
Before you start
Claude Code
Git
A filesystem that supports symbolic links
In a terminal, clone the repository into the documented local data path.
The intended order if supplying multiple transcripts
Use the framing-doc skill. Read the transcript at <TRANSCRIPT_PATH> for the topic area <TOPIC_AREA>. Draft the Source section with attributed, contextual quotes and the Pre-work section describing the options raised, their signal strength, and why one should be pursued now. Treat <TRANSCRIPT_PATH> and <TOPIC_AREA> as placeholders that I will replace with the actual path and topic.
Any related visuals, screenshots, mockups, or breadboards
Use the kickoff-doc skill. Read the full kickoff transcript at <TRANSCRIPT_PATH> and create a builder-facing reference for <PRIMARY_AUDIENCE>. Organize it by the territory being built, with Frame and Shape sections, rather than by conversation or build sequence. Use the participants' language, keep design decisions with the relevant system area, and flag any synthesis that cannot be traced clearly to the transcript. Treat the angle-bracketed values as placeholders to replace.
Concrete operator- or caller-focused workflow replacing <WORKFLOW_DESCRIPTION>
Use the breadboarding skill. Analyze the code repository at <REPO_PATH> and map how <WORKFLOW_DESCRIPTION> works from the operator's or caller's perspective. Produce UI Affordances and Code Affordances tables with numbered entries, controls, Wires Out, and Returns To relationships. If the workflow crosses applications, represent it as one breadboard and label each system. Treat <REPO_PATH> and <WORKFLOW_DESCRIPTION> as placeholders to replace.
Claude