Skip to content

oliver-kriska/claude-elixir-phoenix / targets/codex/skills/phx-brief

phx-brief

Verified

Interactive briefing of a plan file — explains reasoning, schema; Use when developers need to understand a plan…

FileKindSize
SKILL.mdskill md4.7 KB
references/briefing-guide.mdmarkdown9.6 KB
references/visual-explainer.mdmarkdown2.3 KB

references/visual-explainer.md

View on GitHub
# Visual Explainer Integration

When a plan's complexity exceeds what terminal-based briefings handle
well, consider generating a visual HTML artifact using the
[visual-explainer](https://github.com/nicobailon/visual-explainer)
skill.

## When to Suggest Visual Output

Suggest visual rendering when ANY of these apply:

- Plan has **5+ phases** with cross-phase dependencies
- Plan has **4+ key decisions** with competing trade-offs
- Plan includes a **System Map** with 3+ pages and wiring
- Post-work briefing shows **mixed completion** (some phases
  blocked, others done) — progress burndown is clearer visually

## What Visual-Explainer Provides

| Cognitive Issue | Terminal Brief | Visual-Explainer |
|----------------|---------------|-----------------|
| Phase sequencing | Flat table | Mermaid flowchart with dependencies |
| Decision trade-offs | Linear text per decision | CSS Grid constraint cards (pros/cons/rejected) |
| Data model connections | Prose description | Entity diagrams with phase annotations |
| Post-work progress | Text table with counts | Chart.js burndown / progress bars |
| System Map wiring | Flat page list | Interactive Mermaid sequence diagram |

## How to Suggest

At the end of Section 3 (Solution Shape / How It Was Built), if
complexity thresholds are met, add:

```
This plan has {N} phases with cross-dependencies.
Want a visual diagram? Try: `/generate-visual-plan`
(requires visual-explainer skill)
```

Keep it as a **suggestion only** — never block the briefing flow.
The terminal briefing remains the primary output; visual rendering
is a complement for complex cases.

## Key Commands from Visual-Explainer

- `/generate-visual-plan` — Render plan as styled HTML with Mermaid
  phase flow diagrams and decision cards
- `/generate-slides` — Magazine-quality slide deck of the briefing
- `/diff-review --slides` — Visual diff analysis (pairs well with
  post-work brief)
- `/project-recap` — Context-switching snapshot (useful when
  resuming work on a plan after time away)

## Installation

```bash
# Via Claude Code
# Clone to ~/.claude/skills/visual-explainer
git clone https://github.com/nicobailon/visual-explainer ~/.claude/skills/visual-explainer
```

See the [visual-explainer README](https://github.com/nicobailon/visual-explainer)
for full setup instructions.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall