Run any Skill in Manus with one click

$pwd:

domain-research

Name: Domain Research
Author: Ibrahim-3d

// Research a domain end-to-end before scaffolding an agentic system for it. Use when the user asks to "research [domain]", "learn about [field]", "what are the best practices for X", "survey the tools for Y", "what MCPs exist for Z", "before we build the agent, understand [topic]", or when kicking off a new /agents-architect:new for an unfamiliar domain. Covers methodology: taxonomy → tools → MCPs → idioms → anti-patterns → eval cases. Produces DOMAIN.md.

Run Skill in Manus

$ git log --oneline --stat

stars:0

forks:0

updated:April 14, 2026 at 19:07

SKILL.md

readonly

name

domain-research

description

Research a domain end-to-end before scaffolding an agentic system for it. Use when the user asks to "research [domain]", "learn about [field]", "what are the best practices for X", "survey the tools for Y", "what MCPs exist for Z", "before we build the agent, understand [topic]", or when kicking off a new /agents-architect:new for an unfamiliar domain. Covers methodology: taxonomy → tools → MCPs → idioms → anti-patterns → eval cases. Produces DOMAIN.md.

Domain Research

Before you build an agentic system for a domain, you research the domain the way a senior practitioner would brief a new hire. Output: a single DOMAIN.md that later agents consume.

Research layers

Taxonomy: core concepts, sub-fields, canonical workflows. (e.g., 3D modeling → modeling / UV / rigging / animation / shading / lighting / rendering / post.)
Tools: the 5-10 dominant programs, libraries, APIs. Note open-source vs. commercial, CLI vs. GUI, scriptable vs. not.
MCPs / programmatic interfaces: what's already exposed via MCP? What's scriptable via SDK? What requires GUI automation?
Idioms & conventions: how do practitioners name things, structure projects, version files, share work? (e.g., Blender → bpy API, collections, linked libraries.)
Best practices: top 10 rules practitioners would cite unprompted. Sourced from docs, style guides, community consensus.
Anti-patterns: top 10 ways novices and AI go wrong. Common failure modes.
Eval seeds: 10 concrete tasks that an agent in this domain should ace, and 10 harder ones it should survive.

Research methodology

WebSearch for current-year docs, "best practices ", "[tool] Python API", "anti-patterns in ".
WebFetch the official docs, top 3 community style guides, one textbook if available.
MCP registry search (search_mcp_registry) for each major tool.
arxiv / scholar (if connected) for recent methodology papers.
Cross-check sources: a practice is only "consensus" if it appears in 3+ independent sources.

DOMAIN.md structure

# Domain: <name>

## One-line definition

## Taxonomy
- Concept A — what it is, when it matters.
- ...

## Dominant tools
| Tool | License | Interface | Notes |
|---|---|---|---|

## Available MCPs
| MCP | Registry ID | Capabilities | Auth |
|---|---|---|---|

## Idioms
- Naming: ...
- Project layout: ...
- File versioning: ...

## Best practices (prioritized)
1. ...

## Anti-patterns
1. ...

## Eval seeds
### Core (must pass)
1. ...

### Stretch
1. ...

## Sources
- [Doc title](url)
- ...

Scope discipline

Time-box: 15-20 min of research per pass. Go deeper only when the user specifies a narrow sub-domain.
Breadth before depth: taxonomy + tool list first. Drill into the top 2-3 tools only.
Cite sources. Every best-practice bullet has a source link.

Output

Produce DOMAIN.md in the architect session's working directory. Return a 10-line summary to the orchestrator: scope, top 3 tools, recommended MCPs, top 3 anti-patterns to encode as red-lines, eval seed count.

related-skills.json

same repository

agents-architect-skill.md

from "Ibrahim-3d/agents-architect"

Author a single skill from a short brief. Use to add a skill to an existing plugin or iterate on a skill's description/body.

2026-04-140

agent-authoring.md

from "Ibrahim-3d/agents-architect"

Write or refactor Claude Code sub-agent definitions (files in agents/*.md). Use when the user asks to "create a subagent", "add an agent for X", "build a specialist agent", "make a research agent", "write an agent file", "agent YAML", "delegate to a subagent", "design a multi-agent workflow", or when a task needs a fresh context window, restricted tools, or isolation. Covers frontmatter (tools/model/effort/maxTurns/isolation), delegation patterns, read-only constraints, and orchestrator↔specialist contracts.

2026-04-140

command-authoring.md

from "Ibrahim-3d/agents-architect"

Write or refactor Claude Code slash commands (files in commands/<ns>/<cmd>.md). Use when the user asks to "create a slash command", "add /<name>", "write a command file", "make a /command", "turn this workflow into a command", "argument hints", "allowed-tools", or when packaging a repeatable workflow as a one-keystroke invocation. Covers frontmatter, $ARGUMENTS parsing, @-imports for context files, and orchestration patterns.

2026-04-140

context-management.md

from "Ibrahim-3d/agents-architect"

Design and optimize context windows for agentic workflows. Use when the user asks to "manage context", "optimize context", "compact context", "context budget", "CLAUDE.md", "memory hierarchy", "context degradation", "agent is forgetting", "agent hallucinating after many turns", "long conversation", "hit token limit", "prune context", "memory tiers", or when a multi-turn workflow shows quality decay. Covers CLAUDE.md authoring, tiered memory, scratchpads, /compact strategies, read-depth rules, and subagent delegation for context relief.

2026-04-140

mcp-integration.md

from "Ibrahim-3d/agents-architect"

Select, scaffold, or integrate Model Context Protocol (MCP) servers with a Claude Code plugin. Use when the user asks to "add an MCP", "which MCP for X", "connect to [service]", "find a server for [API/tool]", "wrap [tool] as an MCP", ".mcp.json", "MCP server config", or when a domain needs external tools Claude doesn't have (Blender, Figma, ClickUp, arxiv, a CAD program, etc.). Covers MCP discovery via registry, config schema, env/userConfig wiring, and fallback to CLI when no MCP exists.

2026-04-140

plugin-packaging.md

from "Ibrahim-3d/agents-architect"

Package a collection of skills/agents/commands/hooks as a distributable Claude Code plugin. Use when the user asks to "package this as a plugin", "create a plugin.json", "build a marketplace entry", "make this installable", "publish my plugin", "plugin manifest", "validate my plugin", or when bundling work for others to install via /plugin marketplace add. Covers plugin.json schema, marketplace.json, CLAUDE_PLUGIN_ROOT, userConfig, and validation.

2026-04-140

package.json

"author": "Ibrahim-3d"

"repository": "Ibrahim-3d/agents-architect"

View GitHub Repository View Creator Repositories

$ install --global

$ download --local

Run Skill in Manus

$ useful --forSOC

Management AnalystsBusiness and Financial Operations Occupations13-1111L4

name

domain-research

description

Domain Research

Before you build an agentic system for a domain, you research the domain the way a senior practitioner would brief a new hire. Output: a single DOMAIN.md that later agents consume.

Research layers

Taxonomy: core concepts, sub-fields, canonical workflows. (e.g., 3D modeling → modeling / UV / rigging / animation / shading / lighting / rendering / post.)
Tools: the 5-10 dominant programs, libraries, APIs. Note open-source vs. commercial, CLI vs. GUI, scriptable vs. not.
MCPs / programmatic interfaces: what's already exposed via MCP? What's scriptable via SDK? What requires GUI automation?
Idioms & conventions: how do practitioners name things, structure projects, version files, share work? (e.g., Blender → bpy API, collections, linked libraries.)
Best practices: top 10 rules practitioners would cite unprompted. Sourced from docs, style guides, community consensus.
Anti-patterns: top 10 ways novices and AI go wrong. Common failure modes.
Eval seeds: 10 concrete tasks that an agent in this domain should ace, and 10 harder ones it should survive.

Research methodology

WebSearch for current-year docs, "best practices ", "[tool] Python API", "anti-patterns in ".
WebFetch the official docs, top 3 community style guides, one textbook if available.
MCP registry search (search_mcp_registry) for each major tool.
arxiv / scholar (if connected) for recent methodology papers.
Cross-check sources: a practice is only "consensus" if it appears in 3+ independent sources.

DOMAIN.md structure

# Domain: <name>

## One-line definition

## Taxonomy
- Concept A — what it is, when it matters.
- ...

## Dominant tools
| Tool | License | Interface | Notes |
|---|---|---|---|

## Available MCPs
| MCP | Registry ID | Capabilities | Auth |
|---|---|---|---|

## Idioms
- Naming: ...
- Project layout: ...
- File versioning: ...

## Best practices (prioritized)
1. ...

## Anti-patterns
1. ...

## Eval seeds
### Core (must pass)
1. ...

### Stretch
1. ...

## Sources
- [Doc title](url)
- ...

Scope discipline

Time-box: 15-20 min of research per pass. Go deeper only when the user specifies a narrow sub-domain.
Breadth before depth: taxonomy + tool list first. Drill into the top 2-3 tools only.
Cite sources. Every best-practice bullet has a source link.

domain-research

Domain Research

Research layers

Research methodology

DOMAIN.md structure

Scope discipline

Output

More from this repository

More from this repository

Domain Research

Research layers

Research methodology

DOMAIN.md structure

Scope discipline

Output