القائمة
Research open-source repositories to understand how something is built or works.
Headless and headful browser automation with natural language control. Saves tokens by delegating all Playwright logic to a dedicated browser automation layer.
Unified multi-agent role system. Covers Builder, Coder, Council, Orchestrator, Plan, Researcher, Reviewer, and Scribe personas. Use when coordinating multi-agent workflows with MECE principle and role delegation.
Bold aesthetic principles for AI-native interfaces, conversational UI, and trust-forward design. Use when building Claude-like interfaces, trust signals, conversational layouts, or intellectual generosity patterns.
Automates detection and prioritization of audit-related issues across the workspace. Scans for performance, accessibility, and monitoring signals. Use when analyzing audit errors or requesting actionable improvement patches.
Use this skill when the user asks you something that requires searching a code base
Research existing architecture before implementing a complex feature.
| name | code-research |
| description | Research open-source repositories to understand how something is built or works. |
| metadata | {"author":"morph","version":"0.1.0","argument-hint":"<question about an external repo>"} |
Use github_codebase_search to explore external open-source repositories and understand their implementation details.
vercel/next.js, facebook/react).github_codebase_search calls in parallel — one per angle. Do not run them sequentially.Always decompose the research into 2-4 concurrent searches. For example, to understand how a repo handles authentication:
Run all queries at the same time to minimize latency.
"Find how implements . Include entry points, key functions, and data flow."