interview

Sterne0

Forks0

Aktualisiert11. Mai 2026 um 19:49

Interview the user in depth to create a detailed spec. Use when the user wants requirements discovery, product or technical specification writing, UX exploration, or a structured design interview before implementation.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

fdb

fdb/dotfiles

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

ProjektmanagementspezialistenWirtschafts- und Finanzberufe·SOC 13-1082

Datei-Explorer

2 Dateien

SKILL.md

readonly

name	interview
description	Interview the user in depth to create a detailed spec. Use when the user wants requirements discovery, product or technical specification writing, UX exploration, or a structured design interview before implementation.

Follow the user instructions and interview me in detail about literally anything: technical implementation, UI & UX, concerns, tradeoffs, etc. but make sure the questions are not obvious. be very in-depth and continue interviewing me continually until it's complete. then, write the spec to a file. Use the user request as the interview topic.

Mehr aus diesem Repository

gleiches Repository

bespoke-tool

fdb/dotfiles

Build a throwaway single-file tool for a specific use case — runs on file://, persists to localStorage, no build step. Stack scales from static HTML to React-via-CDN based on interaction complexity.

2026-05-220

code-explainer

fdb/dotfiles

Use when the user asks to create an interactive HTML explainer, visual walkthrough, or "making of" page for a codebase, feature, protocol, spec, architecture, commit history, board design, or technical documentation. Triggered by requests like "explain this code visually", "create an explainer", "make an interactive walkthrough", "explain this protocol", "visualize the architecture". Produces a long-form, top-to-bottom scrolling page in which interactive diagrams carry the explanation and prose threads them together.

2026-05-110

diagnose

fdb/dotfiles

Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.

2026-05-110

docs-to-kindle

fdb/dotfiles

Scrape a documentation website and convert it to .epub and .azw3 for Kindle. Use when the user asks to turn docs, guides, or a documentation site into an ebook for Kindle or EPUB readers.

2026-05-110

electron

fdb/dotfiles

Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.

2026-05-110

explorable-explanations

fdb/dotfiles

Use when creating interactive scrollytelling pages, playable essays, model-driven explanations, or explorable explanations for concepts, phenomena, societal issues, geopolitical situations, scientific research, or public-interest themes. Triggered by "make an explorable explanation", "build a playable essay", "explain this interactively", "scrollytelling piece for X", or references to authors and projects in the lineage — Bartosz Ciechanowski, Nicky Case, Vi Hart, Bret Victor, Parable of the Polygons, Distill, Mathigon, explorabl.es.

2026-05-110

Jeden Skill mit einem Klick ausführen