Leaderboard/Product/shaping-skills
Last commit on April 10, 2026·Created on January 29, 2026

rjs/shaping-skills

Shapes raw conversations into maps of what a system actually does.
Combined rank
#229
across all skills
In Product
#4
category rank
Stars
1.4k
+0.3% in last 7d
Forks
90
-1.1% in last 7d
Watchers
17
0.0% in last 7d
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.
TL;DR

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
Repository contents

5 skill files

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.

Use this skill collection

Follow the documented setup, then try a first task.

Claude Code symlink installation

Installs: Documented Shaping Skills bundle containing framing-doc, kickoff-doc, breadboarding, and shaping; symlinks keep the installed skills updatable with git pull. · Claude Code

Before you start
  • Claude Code
  • Git
  1. Run this complete block in a terminal. It clones the repository to `~/.local/share/shaping-skills` and symlinks each documented skill as a direct child of `~/.claude/skills/`.

    # Clone the repo, then symlink each skill into your Claude Code skills directory
    git clone https://github.com/rjs/shaping-skills.git ~/.local/share/shaping-skills
    ln -s ~/.local/share/shaping-skills/framing-doc ~/.claude/skills/framing-doc
    ln -s ~/.local/share/shaping-skills/kickoff-doc ~/.claude/skills/kickoff-doc
    ln -s ~/.local/share/shaping-skills/breadboarding ~/.claude/skills/breadboarding
    ln -s ~/.local/share/shaping-skills/shaping ~/.claude/skills/shaping
README.md · Checked Sep 18, 2026

Give it something to do.

Suggested first task

Create a frame from conversation transcripts

Uses framing-doc

  • Ordered transcript file paths replacing `<TRANSCRIPT_PATHS>`
  • Topic area replacing `<TOPIC_AREA>`
Use the framing-doc skill to create a framing document from the conversation transcripts at `<TRANSCRIPT_PATHS>`, read in the order listed. The topic area is `<TOPIC_AREA>`. Capture attributed source quotes, the options that surfaced and their signals, and the case for which problem should be pursued now without dismissing the other options permanently.
framing-doc/SKILL.md · Checked Sep 18, 2026
Suggested first task

Turn a kickoff transcript into a builder reference

Uses kickoff-doc

  • Kickoff transcript path replacing `<KICKOFF_TRANSCRIPT_PATH>`
  • Primary audience replacing `<PRIMARY_AUDIENCE>`
  • Optional supporting-input paths replacing `<SUPPORTING_INPUT_PATHS>`
Use the kickoff-doc skill on `<KICKOFF_TRANSCRIPT_PATH>` to produce a reference document for `<PRIMARY_AUDIENCE>`. Also consider the supporting visuals, screenshots, mockups, or breadboards at `<SUPPORTING_INPUT_PATHS>`. Organize the document by the territory being built, with Frame and Shape sections, and keep every claim grounded in what participants said or clearly meant.
kickoff-doc/SKILL.md · Checked Sep 18, 2026
Suggested first task

Breadboard an existing workflow

Uses breadboarding

  • Code repository path replacing `<CODE_REPOSITORY_PATH>`
  • Operator-facing workflow description replacing `<WORKFLOW_DESCRIPTION>`
Use the breadboarding skill to map the existing system in `<CODE_REPOSITORY_PATH>` for this operator-facing workflow: `<WORKFLOW_DESCRIPTION>`. Produce UI Affordances and Code Affordances tables showing controls, wires out, and returns-to relationships. If the workflow crosses multiple applications, represent the full story in one breadboard and label each system.
breadboarding/skill.md · Checked Sep 18, 2026