Results for “guy-debord”

Creates a tech sharing deck for internal engineering talks with GitHub-dark theme and JetBrains Mono code blocks.

Creates a course or training module deck with persistent learning objectives, MCQ self-test pages, and warm paper background with Playfair serif typography.

Packages an existing talking-head, interview, or podcast video with timed, designed graphic overlay cards—kinetic titles, lower-thirds, data callouts, quotes, side panels, picture-in-picture—synced to the transcript, on a 16:9, 9:16, or 4:5 canvas.

Build board and investor update decks with structured narratives, metrics dashboards, and C-suite perspectives for board meetings, quarterly reviews, and fundraising.

Gdb reference tool. Use when working with gdb in devtools contexts.

Learn to combine DeFi protocols safely: Uniswap V4 hooks, Aave flash loans, ERC-4626 vaults, Aerodrome on Base, GMX/Pendle on Arbitrum, and dominant DEX per L2.

Systematic debugging with root cause investigation. (gstack)

Creates a presenter-mode deck with speaker notes, theme switching, and a popup teleprompter.

Router for the gstack skill suite. (gstack)

ade-ops setup — START HERE on a fresh clone. Scenario-aware onboarding for Databricks with Power BI and/or Microsoft Fabric.

Investigate a problem, log it to the debug changelog, cross-check past issues, and suggest a non-duplicate fix.

Visualização estatística. Gráficos de dispersão, boxplots, violins, mapas de calor, matriz de pares, regressão, matrizes de correlação, KDE, gráficos facetados, para análise exploratória e figuras para publicação.

Regenerate the iOS debug bridge against the latest upstream gstack templates. (gstack)

Debug Python: pdb REPL + debugpy remote (DAP).

Manage decentralized git repositories, identities, pull requests, issues, bounties, and agent tasks on the gitlawb network using cryptographic DIDs and Ed25519 signatures.

Creates developer tutorial decks with GitHub-dark theme, purple-blue ambient light, gradient titles, and code blocks.

Runs an interactive QA session, clarifying user-reported problems, exploring the codebase for context, and filing durable, user-focused GitHub issues.

Prepare a Quarterly Business Review deck and narrative that proves value and sets the next quarter's plan.

Systematic debugging with root cause investigation. Four phases: investigate, analyze, hypothesize, implement. Iron Law: no fixes without root cause. Use when asked to "debug this", "fix this bug", "why is this broken", "investigate this error", or "root cause analysis". Proactively invoke this skill (do NOT debug directly) when the user reports errors, 500 errors, stack traces, unexpected behavior, "it was working yesterday", or is troubleshooting why something stopped working. (gstack)

Load this skill when the user says "tech debt", "tech-debt", or "/tech-debt", or asks to file/track something they've identified as tech debt. Verifies the claimed problem still exists in the current code, drafts a single [Tech Debt]-prefixed issue from `.github/ISSUE_TEMPLATE/tech-debt-issue.md`, and creates it via `gh issue create` only after the user approves the draft.

Remove the DebugBridge SPM package and all #if DEBUG wiring from an iOS app. (gstack)

Creates safety alert decks with hazard stripes, tiered cards, and policy code blocks for incident reviews and risk communication.