dckc/mad-skills
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

hackmd-deck: drop the no-questions rule

Browse Source 
It came from one deck's revision, not from how these talks go; step 4
returns to the draft's wording.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
dckcandClaude Opus 5.5 committed 2026-10-09 14:09:46 -05:00
1 parent 6d150c4450
commit a4308a5722
1 file changed
+1 -2
Download Patch File Download Diff File Expand all files Collapse all files
hackmd-deck/SKILL.md
+1 -2
View File
@@ -36,7 +36,6 @@ A talk at something like Agoric's engineering show & tell: "Presentations should
## Forces ## Forces
- The audience follows up afterward, or doesn't; the deck is no place to ask.
- A TADA from a side thread leaves the audience waiting for a payoff that never comes. - A TADA from a side thread leaves the audience waiting for a payoff that never comes.
- Designed, built in dev, and deployed look alike on a slide. - Designed, built in dev, and deployed look alike on a slide.
- Real code and real output convince; paraphrase doesn't. - Real code and real output convince; paraphrase doesn't.
@@ -52,7 +51,7 @@ The arc:
1. 🎉 TADA! Look what I did. It must be on the thread the talk follows. 1. 🎉 TADA! Look what I did. It must be on the thread the talk follows.
2. Now that you're hooked, how I did that. 2. Now that you're hooked, how I did that.
3. Eye candy along the way: diagrams, verbatim code, test output. 3. Eye candy along the way: diagrams, verbatim code, test output.
4. Conclusions and challenges. Slides **show** challenges; they don't pose questions. 4. Conclusions and/or challenges that lead to discussion.
Ground every slide in the record: quote code and test output verbatim (trim with `...`), check claims against the code and git history, and mark what's only designed or not deployed with ⏳. Ground every slide in the record: quote code and test output verbatim (trim with `...`), check claims against the code and git history, and mark what's only designed or not deployed with ⏳.