macos-programmer
macOS-specific development patterns, platform APIs, and decision frameworks. Use when developing Mac apps, macOS applications,…
Deprecated name; the skill formerly here is now opinionated-research:interactive-research. Retained as a context-level notice because Claude Code now ships a built-in deep-research workflow that runs one-shot, non-interactive fan-out research (no conversation after the report).
Claude Code
$ npx -y skills add Pyroxin/opinionated-claude-skills --skill deep-research --agent claude-code
Codex
$ npx skills add Pyroxin/opinionated-claude-skills --skill deep-research -a codex -y
Cursor
$ npx skills add Pyroxin/opinionated-claude-skills --skill deep-research -a cursor -y
Gemini CLI
$ npx skills add Pyroxin/opinionated-claude-skills --skill deep-research -a gemini-cli -y
GitHub Copilot
$ npx skills add Pyroxin/opinionated-claude-skills --skill deep-research -a github-copilot -y
OpenCode
$ npx skills add Pyroxin/opinionated-claude-skills --skill deep-research -a opencode -y
Windsurf
$ npx skills add Pyroxin/opinionated-claude-skills --skill deep-research -a windsurf -y
name: deep-research description: "Deprecated name; the skill formerly here is now opinionated-research:interactive-research. Retained as a context-level notice because Claude Code now ships a built-in deep-research workflow that runs one-shot, non-interactive fan-out research (no conversation after the report). interactive-research instead runs a persistent agent team you can keep questioning after the report is delivered. Guidance for Claude: when the user makes a research request, ask whether they want the interactive team (interactive-research) or the built-in non-interactive deep-research workflow before starting."
This skill was renamed to `opinionated-research:interactive-research`. It's kept only so the old name doesn't silently resolve to the wrong thing, and to remind Claude to disambiguate. Two different tools now answer to "deep research":
agent team that researches the topic and *stays alive*, so you can question the researchers, push back on the synthesis, and refine after the report is delivered.
fan-out search, fetch, adversarial verification, synthesized report. Fast and thorough, but *non-interactive*: when it finishes, there's nothing left to talk to.
**When a user asks for research, ask which they want before proceeding**, then invoke the chosen tool. Don't treat this notice itself as a research tool.
This project descends from the personal prompts I'd been keeping for Claude Code prior to the release of skills and plugins. Over time it's also evolved into a sandbox where I figure out what makes Claude reliably good at a task, and find prompts that work.
macOS-specific development patterns, platform APIs, and decision frameworks. Use when developing Mac apps, macOS applications,…
Swift-specific idioms, tooling, and philosophy for both application development and command-line scripting. Use when working with…
Fish shell scripting judgment frameworks and critical idioms. Use when writing Fish scripts or shell automation. Focuses on when…
Java-specific tooling, documentation standards, testing practices, and modern idioms. Use when working with Java code or…
Clojure-specific philosophy, idioms, and judgment frameworks. Use when working with Clojure code. Emphasizes data-oriented…
Racket-specific tooling, libraries, idioms, and language-oriented programming philosophy. Use when working with Racket code.…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.