Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

debug-trace

Étoiles2

Forks0

Mis à jour8 juin 2026 à 09:48

Systematic debugging, state the error, form hypotheses in order of likelihood, and test each one before jumping to a fix.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

teamplanes

teamplanes/hangar

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	debug-trace
description	Systematic debugging, state the error, form hypotheses in order of likelihood, and test each one before jumping to a fix.

What it does

Walks through a bug systematically, traces the error to its root cause before suggesting a fix. Stops Claude jumping straight to a guess that misses the real problem.

When to use

When you have an error you can't immediately explain
When you've tried two obvious fixes and neither worked
When you want to understand why, not just get it patched

The skill

I have a bug. Before suggesting any fix, work through this process:

Restate the error. What exactly is happening? What was expected?
Trace the path. Walk through the code or system involved, step by step. Where could this break?
Form hypotheses. List 3–5 possible causes, ranked by likelihood.
What to check first. For the top 2 hypotheses, what's the fastest way to confirm or rule each one out?
Then suggest a fix, only once we've narrowed it down.

Don't jump to the fix. Don't guess. If you need more information to form hypotheses, ask for it.

Here's the bug:

[describe what's happening, paste the error message, paste relevant code]

Plus depuis ce dépôt

même dépôt

planes-deck

teamplanes/hangar

Use when building or recreating a Planes-style presentation deck: a playback, pitch, demo, strategy or client deck in the studio's house design (the "big playback deck" look people liked). Also use when someone wants an on-brand HTML slide deck with Planes fonts, colours, transitions and layouts, or asks to "make a deck like the Lewis Silkin playback" or "build a deck in the Planes style".

Use when writing, rewriting, or reviewing any copy that should sound like Planes: pitch decks, proposals, playbacks, credentials and RFP responses, website and product copy, case studies, emails, taglines, headlines, or any client-facing or internal writing that needs to be on brand. Also use when copy reads generic, corporate, hypey, or off-voice and someone wants it to "sound like us" or "sound like Planes".

Designs a collaborative workshop and builds it as a ready-to-run FigJam board, plus a facilitator run-sheet and a participant invite email. Use this skill whenever Fiona (or anyone at Planes) wants to plan, design, structure, or build a workshop, session, or facilitated meeting — and especially whenever FigJam is mentioned. Trigger on phrases like "create a workshop", "design a workshop", "build a FigJam board", "set up a workshop in FigJam", "I'm running a session with [client]", "plan a discovery workshop", "kickoff workshop", "ideation session", "retro board", "prioritisation workshop", "journey mapping session", "we need a workshop for X", "turn this into a FigJam", or any request to prepare a participatory session. Always use this skill for workshop design even if the person doesn't say "FigJam" explicitly — it produces the agenda, the board, the run-sheet, and the invite together so the whole session is ready to facilitate.

name	debug-trace
description	Systematic debugging, state the error, form hypotheses in order of likelihood, and test each one before jumping to a fix.

What it does

Walks through a bug systematically, traces the error to its root cause before suggesting a fix. Stops Claude jumping straight to a guess that misses the real problem.

When to use

When you have an error you can't immediately explain
When you've tried two obvious fixes and neither worked
When you want to understand why, not just get it patched

The skill

I have a bug. Before suggesting any fix, work through this process:

Restate the error. What exactly is happening? What was expected?
Trace the path. Walk through the code or system involved, step by step. Where could this break?
Form hypotheses. List 3–5 possible causes, ranked by likelihood.
What to check first. For the top 2 hypotheses, what's the fastest way to confirm or rule each one out?
Then suggest a fix, only once we've narrowed it down.

Don't jump to the fix. Don't guess. If you need more information to form hypotheses, ask for it.

Here's the bug:

[describe what's happening, paste the error message, paste relevant code]