architecting-software
Designs software architecture from a confirmed PRD. Use when a PRD exists and architecture must be designed before implementation, when writing ADRs, choosing…
Conducts research. Use when asked to research, investigate, explore, look into a topic, compare options, learn about an unfamiliar domain, or understand current state.
$ npx -y skills add isvlasov/rageatc-oss --skill conducting-research --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/conducting-researchContext preview
The summary Claude sees to decide when to auto-load this skill.
Conducts research. Use when asked to research, investigate, explore, look into a topic, compare options, learn about an unfamiliar domain, or understand current state.
name: conducting-research description: Conducts research. Use when asked to research, investigate, explore, look into a topic, compare options, learn about an unfamiliar domain, or understand current state.
Guide systematic research: frame the question, find and judge sources, gather and synthesise, stop at the right point, present findings with confidence levels. This is process guidance, not domain expertise — findings are only as good as the sources available.
Skip when a single lookup or a straightforward answer from existing knowledge suffices.
Before searching, establish (ask the user if unclear):
Aim for at least 3 high-quality sources before concluding anything.
Source hierarchy — start at the top, expand downward as needed:
1. **Primary** — official documentation, research papers, primary data, project repositories and changelogs 2. **Secondary** — established books and guides, expert blog posts (verify expertise), reputable analysis sites 3. **Community** — Stack Overflow, Reddit/HN discussions, GitHub issues, conference talks — useful but verify
Judge each source on: **authority** (who wrote it; official or third-party), **recency** (still current? prioritise recent sources in fast-moving fields), **accuracy** (cites reliable sources; key claims verifiable elsewhere), **bias** (conflicts of interest; promotion disguised as neutral content), **relevance** (addresses the question in a context like yours).
Deprioritise sources with: no author attribution, promotional language, outdated information, no citations, claims conflicting with multiple reliable sources, or strong opinion without evidence.
By research type: **technology evaluation** — official docs first, then neutral benchmarks and production experience reports; **concept understanding** — authoritative introductions, cross-referencing multiple explanations; **current events** — sources from the last 6–12 months, verified across several; **troubleshooting** — official docs, then GitHub issues and dated Stack Overflow answers.
Default to hybrid exploration: breadth-first to map the territory and identify 2–4 key areas, then depth-first on each, returning to breadth if gaps appear. Keep structured notes as you go: findings with their sources, open questions, and contradictions between sources.
Build a mental model: core concepts, how they connect, where sources agree and where they debate. Before concluding:
**Stop when** the original question has a clear answer, key claims are verified by multiple reliable sources, understanding suffices for the stated purpose, and further searching shows diminishing returns.
**Keep going when** core concepts remain confusing, contradictions are unresolved, key claims rest on low-quality sources, or critical assumptions are untested.
If time runs out first: state what wasn't covered, separate what you know / think / don't know, and flag where the gaps carry risk.
Adapt format to purpose — a quick investigation may need only a summary. For substantial research include: executive summary (core answer plus key takeaways), scope and constraints, findings organised by theme or sub-question with evidence, source quality and confidence levels, implications or recommendation, open questions. Cite sources for quotes and key claims: `[claim] (Source: name, URL)`.
Watch for these while working:
Rage Against The C - pick your own C to rage against. Two plugins for Claude Code / Cowork, built on the idea that we're using AI wrong: the speed of its output tricks us into rushing the input.
Repo: isvlasov/rageatc-oss
Designs software architecture from a confirmed PRD. Use when a PRD exists and architecture must be designed before implementation, when writing ADRs, choosing…
Writes correct, version-aware Telegram bot code. Use when writing, extending, or debugging a Telegram bot in python-telegram-bot, aiogram, grammY, or Telegraf.…
Converts an approved ARCHITECTURE.md into an implementation roadmap of isolated, dependency-ordered chunks. Use when architecture has been approved and work…
Delegates a task to OpenAI Codex running as an interactive session in a herdr pane - uses the user's ChatGPT subscription, visible in herdr, steerable…
Delegates a task to a local LLM running as a Pi coding-agent session in a herdr pane - the subagent is visible in herdr, can be steered mid-session, and costs…
Creates a design system for software with a UI. Use when a project has a user interface and architecture is confirmed — whether creating from scratch or…