Results for “research-before-coding”

Research existing tools, libraries, and patterns before writing custom code by invoking a researcher agent.

Guides a research-before-coding workflow, searching existing tools, libraries, and patterns before writing custom code, with decision matrices and integration with agent workflows.

Guides the agent to research existing tools, libraries, and patterns before writing custom code, using parallel searches across package registries, MCP servers, skills, and GitHub, then evaluating and deciding to adopt, extend, or build.

Use before any creative or ambiguous work - new features, new components, or behavior changes - to explore intent, requirements, and design before implementation starts.

Systematic codebase exploration following the Iron Law - understand the problem before exploring code. Four phases with file-finder and web-researcher agents.

Run evidence-first research, web/source search, Exa search, iterative retrieval, and research-before-coding workflows. Use when prompts ask for current facts, source-backed recommendations, market or company research, code/library discovery, query refinement, cited synthesis, deep research, or the old deep-research/research-ops/exa-search/iterative-retrieval/search-first skills.

Diagnose bugs by establishing a tight feedback loop, tracing root cause, and verifying fixes with regression tests before making changes.

Use when coding interviews, focus groups, or open-ended responses with AI assistance, when a codebook needs building or auditing, when intercoder reliability must be computed, or when qualitative quotes need integrity checks before publication.

Explora el código y el dominio del problema antes de proponer un cambio, documentando hallazgos y recomendaciones.

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written.

Expert Socratic discovery skill for exploring ideas, architecture decisions, and technical design before writing any code. Use this skill — proactively and always first — when requirements are vague, when the user is debating between technical approaches, when the problem is unclear, or when a design decision could have significant architectural consequences. Triggers on: "should we use X or Y", "help me think through", "I'm not sure how to approach this", "what's the best architecture for", "trade-offs between", "design before I code", "let's think through this", "I have an idea", "how should I structure", "help me design", "I want to build X but not sure how", "what approach would you recommend", "is this the right way to". Produces a validated design doc with 2-3 implementation options, trade-offs, and a recommendation. Always use before planning when the approach is not yet locked.

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Guides collaborative dialogue to turn ideas into approved designs and specs before any implementation begins.

Forces investigation of file dependencies before editing code to prevent cascade failures.

Guides collaborative dialogue to turn ideas into designs and specs, exploring intent and requirements before any implementation.

Turns a spec or requirements into a detailed, bite-sized implementation plan with exact file paths, code, and test steps for engineers with no codebase context.

Turns rough ideas into approved, decision-complete plans with validated structure before coding. Use when users ask in any language for planning, architecture, design direction, feasibility, value judgment, or whether a feature is worth doing before implementation. Not for bug fixes or small edits.

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Use this skill before architecture, dependency, integration, parser, bot, UI, deployment, or non-trivial bugfix tasks. It forces Codex to search GitHub, compare open-source solutions, check licenses, and extract reusable patterns without copying unsafe code.

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Verifies a code change before it lands by scanning the staged diff, running tests, and delegating to an independent reviewer.

Dispatches a code-reviewer subagent to evaluate work against requirements and plan, then acts on the feedback before merging.

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Guides collaborative dialogue to turn ideas into approved designs and specs before any implementation begins.

Runs a structured self-review checklist before committing substantial code changes, covering edge cases, error paths, test coverage, documentation, and code quality.

Use for standard or complex new work before coding or planning. Also handles vague goals — clarifies before designing.

Use BEFORE generating, refactoring, reviewing, or debugging code. Trigger phrases include "write a function/script/class for X", "review this code/diff/PR", "refactor this", "debug this error", "is this implementation correct", "what's wrong with this code", "improve this code", "translate from X to Y", or any prompt with a code block the user wants you to act on. Also fires when planning architectural changes, picking algorithms or data structures, or evaluating dependency upgrades. Calls the code MCP tool to retrieve an engineering scaffold (failure pattern, procedure, correct-pattern example, verification step) before generating. Catches hallucinated APIs, lost edge cases, premature algorithm commitment, silent contract violations, refactors that change behavior masked by passing tests. Do NOT trigger for pure code reading with no action requested, simple syntax questions, file...