id large_stringlengths 24 24 | split large_stringclasses 1
value | task large_stringclasses 98
values | source_type large_stringclasses 9
values | source_url large_stringlengths 18 137 | source_name large_stringlengths 3 165 | website_type large_stringclasses 17
values | language large_stringclasses 18
values | topic large_stringclasses 50
values | instruction large_stringlengths 31 262 | context large_stringlengths 364 653 | response large_stringlengths 85 2.58k | code large_stringclasses 7
values | generator_version large_stringclasses 1
value |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
b112fdfa5b369a9cffe13366 | train | multi_hop_research | pypi | https://pypi.org/project/requests/ | requests | developer_tool | scala | javascript | Perform multi-hop research about javascript: start from a source, follow references, and combine findings. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "requests", "source_url": "https://pypi.org/project/requests/", "source_type": "package", "top... | === HOP 1 ===
Start at: requests
https://pypi.org/project/requests/
Extract core claims and references.
=== HOP 2 ===
Follow references to official docs, RFCs, or specs.
Extract primary-source evidence.
=== HOP 3 ===
Check community discussions for real-world issues.
Extract failure modes and workarounds.
=== SYNTHE... | web-research-coding-5m-1.1.0 | |
5f3188c7f8c03b75d54c0440 | train | debugging_experience | stackexchange | https://stackoverflow.com/questions/4752626/epoch-vs-iteration-when-training-neural-networks | Epoch vs Iteration when training neural networks | finance | c | design_system | Perform a deep developer-experience analysis for a c project involving design_system. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Epoch vs Iteration when training neural networks", "source_url": "https://stackoverflow.com/q... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
eaade4d50502bd009c131213 | train | performance_analysis | codeberg | https://codeberg.org/reesericci/actionview-svelte-handler | reesericci/actionview-svelte-handler | analytics | kotlin | linux | Perform a deep multi-layer analysis of linux for a analytics using kotlin. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "reesericci/actionview-svelte-handler", "source_url": "https://codeberg.org/reesericci/actionv... | === 1. PROBLEM ===
Define the exact problem involving linux. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around linux. Use 'reesericci/actionview-svelte-handler' as a source anchor and identify relevant APIs, dependencies, ... | web-research-coding-5m-1.1.0 | |
ea5f1498390626650b8f9648 | train | local_development_experience | gitlab | https://gitlab.com/c-smile/quickjspp | c-smile/quickjspp | marketplace | css | python | Perform a deep developer-experience analysis for a css project involving python. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "c-smile/quickjspp", "source_url": "https://gitlab.com/c-smile/quickjspp", "source_type": "rep... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
886fdb0dbcd450ce41c795c0 | train | refactoring_readability | web_docs | https://nodejs.org/docs/latest/api/ | Node.js Documentation | portfolio | php | distributed_systems | Refactor a php system related to distributed_systems. Focus on refactoring readability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Node.js Documentation", "source_url": "https://nodejs.org/docs/latest/api/", "source_type": "... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Improve naming, control flow, function boundaries, and local reasoning.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify d... | web-research-coding-5m-1.1.0 | |
2095fc121e473b3edec3a8fd | train | security_review | mdn | https://developer.mozilla.org/en-US/docs/Web/Performance | Performance | finance | css | css | Perform a security review of a finance application. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Performance", "source_url": "https://developer.mozilla.org/en-US/docs/Web/Performance", "sour... | Review authentication, authorization, input validation, XSS, CSRF, injection risks, secrets, dependencies, security headers, and logging. | web-research-coding-5m-1.1.0 | |
4077903cd706dc214956aa35 | train | ui_design | gitlab | https://gitlab.com/fmd-foss/fmd-android | fmd-foss/fmd-android | education | html | microservices | Design a production-quality UI for a education focused on microservices. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "fmd-foss/fmd-android", "source_url": "https://gitlab.com/fmd-foss/fmd-android", "source_type"... | Define layout, typography, spacing, hierarchy, components, states, responsive behavior, and accessibility. | web-research-coding-5m-1.1.0 | |
6266f984e265fa3fac96242d | train | design_review | codeberg | https://codeberg.org/Quanti/_cargo-index | Quanti/_cargo-index | search_interface | shell | testing | Perform a professional design review of a search_interface. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Quanti/_cargo-index", "source_url": "https://codeberg.org/Quanti/_cargo-index", "source_type"... | Review hierarchy, consistency, responsiveness, accessibility, interaction design, content clarity, and implementation feasibility. | web-research-coding-5m-1.1.0 | |
f33008e1a26fc3140e71918f | train | responsive_design | npm | https://www.npmjs.com/package/svelte | svelte | search_interface | rust | frontend | Create a responsive design strategy for a search_interface. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "svelte", "source_url": "https://www.npmjs.com/package/svelte", "source_type": "package", "top... | Define mobile, tablet, and desktop behavior, layout transitions, navigation, content priority, typography, and interaction targets. | web-research-coding-5m-1.1.0 | |
407cc121c2e772ca3fa4ce27 | train | technical_research | github | https://github.com/microsoft/TypeScript | microsoft/TypeScript | search_interface | css | documentation | Perform a technical research task about documentation, focused on implementation details. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "microsoft/TypeScript", "source_url": "https://github.com/microsoft/TypeScript", "source_type"... | === SCOPE ===
Technical behavior of documentation.
=== QUESTIONS ===
- What are the inputs, outputs, and invariants?
- What are the performance characteristics?
- What are the security implications?
- What are the compatibility constraints?
=== EVIDENCE ===
- microsoft/TypeScript (https://github.com/microsoft/TypeScr... | web-research-coding-5m-1.1.0 | |
1faa52b3d34f6a67412f4753 | train | search_query_rewrite | gitlab | https://gitlab.com/blewpri/ng-master-detail | blewpri/ng-master-detail | finance | sql | deep_learning | Rewrite and improve a vague search query about deep_learning into a precise, high-signal query. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "blewpri/ng-master-detail", "source_url": "https://gitlab.com/blewpri/ng-master-detail", "sour... | === ORIGINAL (VAGUE) ===
how to do deep_learning
=== REWRITTEN QUERIES ===
1. deep_learning official documentation guide
2. deep_learning production best practices 2025
3. deep_learning common pitfalls and solutions
4. deep_learning architecture patterns with examples
=== RATIONALE ===
Add intent (learn / implement /... | web-research-coding-5m-1.1.0 | |
d97890650469e11ffb964a22 | train | algorithm_design | mdn | https://developer.mozilla.org/en-US/docs/Web/Accessibility | Accessibility | analytics | scala | rest_api | Design a scala algorithm for a rest_api problem. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Accessibility", "source_url": "https://developer.mozilla.org/en-US/docs/Web/Accessibility", "... | State assumptions, algorithm, complexity, edge cases, correctness reasoning, and testing strategy. | web-research-coding-5m-1.1.0 | |
9142d6af007bbd287d6f5950 | train | search_intent_classification | stackexchange | https://stackoverflow.com/questions/37937984/git-refusing-to-merge-unrelated-histories-on-rebase | Git refusing to merge unrelated histories on rebase | landing_page | python | testing | Classify the search intent for a query about testing. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Git refusing to merge unrelated histories on rebase", "source_url": "https://stackoverflow.co... | === POSSIBLE INTENTS ===
- informational (learn a concept)
- navigational (find a specific site/tool)
- transactional (install / download / run)
- troubleshooting (fix an error)
- comparative (choose between options)
=== EXAMPLE QUERY ===
"testing vs alternatives"
=== CLASSIFICATION ===
Comparative / informational.
... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
8fc8340fbae0a49cca02818b | train | dependency_impact_analysis | web_docs | https://doc.rust-lang.org/ | Rust Documentation | documentation | shell | nextjs | Perform a deep multi-layer analysis of nextjs for a documentation using shell. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Rust Documentation", "source_url": "https://doc.rust-lang.org/", "source_type": "documentatio... | === 1. PROBLEM ===
Define the exact problem involving nextjs. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around nextjs. Use 'Rust Documentation' as a source anchor and identify relevant APIs, dependencies, versions, standa... | web-research-coding-5m-1.1.0 | |
0d8bd105e89f8d4735b7c5a5 | train | deployment_experience | codeberg | https://codeberg.org/Trevizer/_cargo-index | Trevizer/_cargo-index | ecommerce | dart | nodejs | Perform a deep developer-experience analysis for a dart project involving nodejs. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Trevizer/_cargo-index", "source_url": "https://codeberg.org/Trevizer/_cargo-index", "source_t... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
2259113e898f73f1ee7a18e2 | train | ui_design | web_docs | https://www.postgresql.org/docs/ | PostgreSQL Documentation | social_app | sql | security | Design a production-quality UI for a social_app focused on security. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "PostgreSQL Documentation", "source_url": "https://www.postgresql.org/docs/", "source_type": "... | Define layout, typography, spacing, hierarchy, components, states, responsive behavior, and accessibility. | web-research-coding-5m-1.1.0 | |
c851a26c14cc69cc6cb44bae | train | landing_page | huggingface | https://huggingface.co/datasets/puttatidam/software-documentation-vie-bitextmining | puttatidam/software-documentation-vie-bitextmining | blog | html | web_performance | Design a landing page for a web_performance product. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "puttatidam/software-documentation-vie-bitextmining", "source_url": "https://huggingface.co/da... | Include hero, value proposition, features, CTA, FAQ, responsive behavior, SEO, accessibility, and analytics. | web-research-coding-5m-1.1.0 | |
3d2fa500b3011ced373f0d40 | train | repository_issue_reasoning | gitlab | https://gitlab.com/Mojeer/django_components | Mojeer/django_components | documentation | ruby | deep_learning | Perform a deep multi-layer analysis of deep_learning for a documentation using ruby. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Mojeer/django_components", "source_url": "https://gitlab.com/Mojeer/django_components", "sour... | === 1. PROBLEM ===
Define the exact problem involving deep_learning. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around deep_learning. Use 'Mojeer/django_components' as a source anchor and identify relevant APIs, dependenci... | web-research-coding-5m-1.1.0 | |
f45b97f878fd091babd3032e | train | search_query_rewrite | stackexchange | https://stackoverflow.com/questions/47236963/no-provider-for-httpclient | No provider for HttpClient | admin_panel | swift | authorization | Rewrite and improve a vague search query about authorization into a precise, high-signal query. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "No provider for HttpClient", "source_url": "https://stackoverflow.com/questions/47236963/no-p... | === ORIGINAL (VAGUE) ===
how to do authorization
=== REWRITTEN QUERIES ===
1. authorization official documentation guide
2. authorization production best practices 2025
3. authorization common pitfalls and solutions
4. authorization architecture patterns with examples
=== RATIONALE ===
Add intent (learn / implement /... | web-research-coding-5m-1.1.0 | |
6b4e9903302aa3d03d875b5e | train | scalability_analysis | huggingface | https://huggingface.co/datasets/SivilTaram/starcoder2-documentation | SivilTaram/starcoder2-documentation | search_interface | typescript | distributed_systems | Perform a deep multi-layer analysis of distributed_systems for a search_interface using typescript. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "SivilTaram/starcoder2-documentation", "source_url": "https://huggingface.co/datasets/SivilTar... | === 1. PROBLEM ===
Define the exact problem involving distributed_systems. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around distributed_systems. Use 'SivilTaram/starcoder2-documentation' as a source anchor and identify re... | web-research-coding-5m-1.1.0 | |
00ca4467c1dbd82ed0c50598 | train | security_analysis | pypi | https://pypi.org/project/pydantic/ | pydantic | portfolio | php | nodejs | Perform a deep multi-layer analysis of nodejs for a portfolio using php. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "pydantic", "source_url": "https://pypi.org/project/pydantic/", "source_type": "package", "top... | === 1. PROBLEM ===
Define the exact problem involving nodejs. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around nodejs. Use 'pydantic' as a source anchor and identify relevant APIs, dependencies, versions, standards, and t... | web-research-coding-5m-1.1.0 | |
98d76c3041959939e71be1a1 | train | build_experience | gitlab | https://gitlab.com/frontierdevelopmentlab/disaster-prevention/cubesatfloods | frontierdevelopmentlab/disaster-prevention/cubesatfloods | developer_tool | java | caching | Perform a deep developer-experience analysis for a java project involving caching. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "frontierdevelopmentlab/disaster-prevention/cubesatfloods", "source_url": "https://gitlab.com/... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
3b4ad81c34c0ce56e151a760 | train | security_review | huggingface | https://huggingface.co/datasets/ellamind/gsm8k-platinum-multilingual | ellamind/gsm8k-platinum-multilingual | developer_tool | typescript | open_source | Perform a security review of a developer_tool application. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "ellamind/gsm8k-platinum-multilingual", "source_url": "https://huggingface.co/datasets/ellamin... | Review authentication, authorization, input validation, XSS, CSRF, injection risks, secrets, dependencies, security headers, and logging. | web-research-coding-5m-1.1.0 | |
1592b8b48c22f97b977cdc4e | train | dx_analysis | stackexchange | https://stackoverflow.com/questions/466345/convert-string-jun-1-2005-133pm-into-datetime | Convert string "Jun 1 2005 1:33PM" into datetime | saas | ruby | database | Perform a deep developer-experience analysis for a ruby project involving database. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Convert string "Jun 1 2005 1:33PM" into datetime", "source_url": "https://stackover... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
9638268c9608d8b21851ddd7 | train | html_generation | npm | https://www.npmjs.com/package/playwright | playwright | landing_page | c | data_structures | Create semantic HTML for a landing_page about data_structures. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "playwright", "source_url": "https://www.npmjs.com/package/playwright", "source_type": "packag... | Use semantic landmarks, headings, accessible controls, meaningful labels, and correct document structure. | <!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport"
content="width=device-width, initial-scale=1">
<title>Accessible Application</title>
</head>
<body>
<main>
<h1>Application</h1>
</main>
</body>
</html> | web-research-coding-5m-1.1.0 |
5d517da857d49af78d20d837 | train | design_system | stackexchange | https://stackoverflow.com/questions/16151018/how-to-fix-npm-throwing-error-without-sudo | How to fix npm throwing error without sudo | portfolio | swift | user_experience | Create a scalable design system for a portfolio. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How to fix npm throwing error without sudo", "source_url": "https://stackoverflow.com/questio... | Define tokens, typography, spacing, components, variants, states, responsive rules, accessibility, and documentation. | web-research-coding-5m-1.1.0 | |
3192b51e843083ac15b42910 | train | debugging | npm | https://www.npmjs.com/package/prettier | prettier | documentation | cpp | typescript | Create a realistic cpp debugging problem involving typescript. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "prettier", "source_url": "https://www.npmjs.com/package/prettier", "source_type": "package", ... | Provide symptoms, reproduction strategy, diagnostic steps, root-cause analysis, minimal fix, and regression coverage. | web-research-coding-5m-1.1.0 | |
481c808818c90ace11f5f5c5 | train | error_message_design | npm | https://www.npmjs.com/package/tailwindcss | tailwindcss | landing_page | python | typescript | Perform a deep developer-experience analysis for a python project involving typescript. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "tailwindcss", "source_url": "https://www.npmjs.com/package/tailwindcss", "source_type": "pack... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
d45f4649131cdc47fac77e5b | train | repository_understanding | gitlab | https://gitlab.com/hsleisink/cauldron | hsleisink/cauldron | analytics | python | debugging | Perform a deep multi-layer analysis of debugging for a analytics using python. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "hsleisink/cauldron", "source_url": "https://gitlab.com/hsleisink/cauldron", "source_type": "r... | === 1. PROBLEM ===
Define the exact problem involving debugging. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around debugging. Use 'hsleisink/cauldron' as a source anchor and identify relevant APIs, dependencies, versions, ... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
092512a3b44ae5e987c66ed6 | train | root_cause_analysis | gitlab | https://gitlab.com/CLIUtils/modern-cmake | CLIUtils/modern-cmake | finance | php | html | Perform a deep multi-layer analysis of html for a finance using php. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "CLIUtils/modern-cmake", "source_url": "https://gitlab.com/CLIUtils/modern-cmake", "source_typ... | === 1. PROBLEM ===
Define the exact problem involving html. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around html. Use 'CLIUtils/modern-cmake' as a source anchor and identify relevant APIs, dependencies, versions, standar... | web-research-coding-5m-1.1.0 | |
4c1e7f5d916b12c28eea4967 | train | repository_dependency_analysis | npm | https://www.npmjs.com/package/playwright | playwright | search_interface | rust | serverless | Perform a deep multi-layer analysis of serverless for a search_interface using rust. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "playwright", "source_url": "https://www.npmjs.com/package/playwright", "source_type": "packag... | === 1. PROBLEM ===
Define the exact problem involving serverless. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around serverless. Use 'playwright' as a source anchor and identify relevant APIs, dependencies, versions, standa... | web-research-coding-5m-1.1.0 | |
f18d2bf200a3ec4927bf03fc | train | ux_analysis | pypi | https://pypi.org/project/fastapi/ | fastapi | ecommerce | dart | rest_api | Perform a deep multi-layer analysis of rest_api for a ecommerce using dart. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "fastapi", "source_url": "https://pypi.org/project/fastapi/", "source_type": "package", "topic... | === 1. PROBLEM ===
Define the exact problem involving rest_api. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around rest_api. Use 'fastapi' as a source anchor and identify relevant APIs, dependencies, versions, standards, an... | web-research-coding-5m-1.1.0 | |
53bb3dd2feacbf8b31d5cafc | train | error_message_design | huggingface | https://huggingface.co/datasets/LiquidAI/nanobeir-multilingual-extended | LiquidAI/nanobeir-multilingual-extended | saas | sql | rest_api | Perform a deep developer-experience analysis for a sql project involving rest_api. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "LiquidAI/nanobeir-multilingual-extended", "source_url": "https://huggingface.co/datasets/Liqu... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
a9d588f7cfafd46d01880b88 | train | refactoring_readability | stackexchange | https://stackoverflow.com/questions/1628563/move-the-most-recent-commits-to-a-new-branch-with-git | Move the most recent commit(s) to a new branch with Git | ecommerce | php | typescript | Refactor a php system related to typescript. Focus on refactoring readability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Move the most recent commit(s) to a new branch with Git", "source_url": "https://stackoverflo... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Improve naming, control flow, function boundaries, and local reasoning.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify d... | web-research-coding-5m-1.1.0 | |
4cf5b4a02137616bed676a74 | train | scalability_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/HTTP | HTTP | finance | rust | deep_learning | Perform a deep multi-layer analysis of deep_learning for a finance using rust. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "HTTP", "source_url": "https://developer.mozilla.org/en-US/docs/Web/HTTP", "source_type": "doc... | === 1. PROBLEM ===
Define the exact problem involving deep_learning. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around deep_learning. Use 'HTTP' as a source anchor and identify relevant APIs, dependencies, versions, standa... | web-research-coding-5m-1.1.0 | |
4999dfe400c2887424e5fbc5 | train | tradeoff_analysis | web_docs | https://git-scm.com/doc | Git Documentation | productivity | sql | serverless | Perform a deep multi-layer analysis of serverless for a productivity using sql. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Git Documentation", "source_url": "https://git-scm.com/doc", "source_type": "documentation", ... | === 1. PROBLEM ===
Define the exact problem involving serverless. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around serverless. Use 'Git Documentation' as a source anchor and identify relevant APIs, dependencies, versions,... | web-research-coding-5m-1.1.0 | |
5bb14412974d89251c299cd4 | train | debugging_experience | stackexchange | https://stackoverflow.com/questions/40758562/can-anyone-explain-me-standardscaler | Can anyone explain me StandardScaler? | landing_page | javascript | html | Perform a deep developer-experience analysis for a javascript project involving html. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Can anyone explain me StandardScaler?", "source_url": "https://stackoverflow.com/questions/40... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
a80e6cb83e08f26847284f75 | train | algorithm_design | gitlab | https://gitlab.com/snowball-dev-group/snowball-bot | snowball-dev-group/snowball-bot | analytics | rust | microservices | Design a rust algorithm for a microservices problem. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "snowball-dev-group/snowball-bot", "source_url": "https://gitlab.com/snowball-dev-group/snowba... | State assumptions, algorithm, complexity, edge cases, correctness reasoning, and testing strategy. | web-research-coding-5m-1.1.0 | |
1a8f6d9cfac90946b4db5414 | train | refactoring_architecture | huggingface | https://huggingface.co/datasets/orgcatorg/multilingual | orgcatorg/multilingual | analytics | php | react | Refactor a php system related to react. Focus on refactoring architecture. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "orgcatorg/multilingual", "source_url": "https://huggingface.co/datasets/orgcatorg/multilingua... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Redesign module boundaries and reduce architectural coupling.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify developer-e... | web-research-coding-5m-1.1.0 | |
7e3d7520548b36e62fe3a22d | train | algorithm_design | mdn | https://developer.mozilla.org/en-US/docs/Web/HTML | HTML | documentation | python | fullstack | Design a python algorithm for a fullstack problem. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "HTML", "source_url": "https://developer.mozilla.org/en-US/docs/Web/HTML", "source_type": "doc... | State assumptions, algorithm, complexity, edge cases, correctness reasoning, and testing strategy. | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
418f51bc08e843c4f8fb089c | train | local_development_experience | gitlab | https://gitlab.com/The_Quantum_Alpha/the-quantum-ad-list | The_Quantum_Alpha/the-quantum-ad-list | ecommerce | scala | nextjs | Perform a deep developer-experience analysis for a scala project involving nextjs. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "The_Quantum_Alpha/the-quantum-ad-list", "source_url": "https://gitlab.com/The_Quantum_Alpha/t... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
5aa2ae0aac8b5ff52209efda | train | design_accessibility | mdn | https://developer.mozilla.org/en-US/docs/Web/JavaScript | JavaScript | education | go | rest_api | Audit accessibility for a education. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "JavaScript", "source_url": "https://developer.mozilla.org/en-US/docs/Web/JavaScript", "source... | Check semantic structure, keyboard navigation, focus visibility, accessible names, labels, errors, contrast, and screen-reader behavior. | web-research-coding-5m-1.1.0 | |
355051c1a4a8e6faed6e874a | train | refactoring_scalability | github | https://github.com/ashishpatel26/500-AI-Machine-learning-Deep-learning-Computer-vision-NLP-Projects-with-code | ashishpatel26/500-AI-Machine-learning-Deep-learning-Computer-vision-NLP-Projects-with-code | finance | html | machine_learning | Refactor a html system related to machine_learning. Focus on refactoring scalability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "ashishpatel26/500-AI-Machine-learning-Deep-learning-Computer-vision-NLP-Projects-with-code", ... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Restructure the system to handle increased load without unnecessary complexity.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Id... | web-research-coding-5m-1.1.0 | |
10bfaaf7f5bfcd98b91b47a5 | train | evidence_chain_analysis | huggingface | https://huggingface.co/datasets/joey234/mmlu-machine_learning-neg-answer | joey234/mmlu-machine_learning-neg-answer | social_app | html | microservices | Perform a deep multi-layer analysis of microservices for a social_app using html. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "joey234/mmlu-machine_learning-neg-answer", "source_url": "https://huggingface.co/datasets/joe... | === 1. PROBLEM ===
Define the exact problem involving microservices. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around microservices. Use 'joey234/mmlu-machine_learning-neg-answer' as a source anchor and identify relevant ... | web-research-coding-5m-1.1.0 | |
2fb3d323f0a4ad7acd45ce49 | train | security_analysis | codeberg | https://codeberg.org/UI-Programming-23-24/01-Web-basics-and-git | UI-Programming-23-24/01-Web-basics-and-git | portfolio | shell | frontend | Perform a deep multi-layer analysis of frontend for a portfolio using shell. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "UI-Programming-23-24/01-Web-basics-and-git", "source_url": "https://codeberg.org/UI-Programmi... | === 1. PROBLEM ===
Define the exact problem involving frontend. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around frontend. Use 'UI-Programming-23-24/01-Web-basics-and-git' as a source anchor and identify relevant APIs, de... | web-research-coding-5m-1.1.0 | |
3e7e25c3db8b0f3875b1db84 | train | documentation_lookup | gitlab | https://gitlab.com/flectra-hq/flectra | flectra-hq/flectra | portfolio | c | api_design | Find and summarize the relevant documentation for api_design. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "flectra-hq/flectra", "source_url": "https://gitlab.com/flectra-hq/flectra", "source_type": "r... | === RELEVANT DOCS ===
- flectra-hq/flectra
https://gitlab.com/flectra-hq/flectra
- Official project documentation
- API reference
=== KEY SECTIONS ===
- Getting started
- API reference
- Configuration
- Troubleshooting
=== SUMMARY ===
Summarize each section in 1–3 sentences and quote exact signatures where relevant... | web-research-coding-5m-1.1.0 | |
1051e6b19432deec3e5f804c | train | refactoring_dependency | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API | Fetch API | marketplace | java | rest_api | Refactor a java system related to rest_api. Focus on refactoring dependency. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Fetch API", "source_url": "https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API", "sour... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Audit dependencies and isolate external integrations.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify developer-experienc... | web-research-coding-5m-1.1.0 | |
b45bf94ac3753f3b85c65bb6 | train | refactoring_architecture | huggingface | https://huggingface.co/datasets/tianyang/repobench_python_v1.1 | tianyang/repobench_python_v1.1 | marketplace | go | fullstack | Refactor a go system related to fullstack. Focus on refactoring architecture. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "tianyang/repobench_python_v1.1", "source_url": "https://huggingface.co/datasets/tianyang/repo... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Redesign module boundaries and reduce architectural coupling.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify developer-e... | web-research-coding-5m-1.1.0 | |
42061f0eacfe730551b6aec8 | train | refactoring_observability | pypi | https://pypi.org/project/transformers/ | transformers | blog | python | developer_experience | Refactor a python system related to developer_experience. Focus on refactoring observability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "transformers", "source_url": "https://pypi.org/project/transformers/", "source_type": "packag... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Improve logging, metrics, tracing, diagnostics, and failure visibility.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify d... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
5ec60d258cade7c0ff3b699c | train | product_analysis | huggingface | https://huggingface.co/datasets/ansulev/hunter-alpha-programming-160k | ansulev/hunter-alpha-programming-160k | dashboard | shell | data_engineering | Perform a deep multi-layer analysis of data_engineering for a dashboard using shell. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "ansulev/hunter-alpha-programming-160k", "source_url": "https://huggingface.co/datasets/ansule... | === 1. PROBLEM ===
Define the exact problem involving data_engineering. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around data_engineering. Use 'ansulev/hunter-alpha-programming-160k' as a source anchor and identify releva... | web-research-coding-5m-1.1.0 | |
598a379d97b8b9d93b1db1e8 | train | fact_verification | codeberg | https://codeberg.org/manminusone/20x2chi-slides | manminusone/20x2chi-slides | education | shell | postgresql | Verify a technical claim about postgresql. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "manminusone/20x2chi-slides", "source_url": "https://codeberg.org/manminusone/20x2chi-slides",... | === CLAIM ===
A common claim about postgresql.
=== VERIFICATION STEPS ===
1. Locate the primary source (docs, spec, RFC).
2. Reproduce the claim in a minimal environment.
3. Check version-specific behavior.
4. Identify edge cases and exceptions.
=== RESULT ===
Classify: confirmed / partially true / false / context-de... | web-research-coding-5m-1.1.0 | |
58797b37be9d8e5ab349f1ce | train | refactoring_security | npm | https://www.npmjs.com/package/react | react | marketplace | html | ci_cd | Refactor a html system related to ci_cd. Focus on refactoring security. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "react", "source_url": "https://www.npmjs.com/package/react", "source_type": "package", "topic... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Strengthen validation, trust boundaries, authorization, and secret handling.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Ident... | web-research-coding-5m-1.1.0 | |
c24020a5e11c4bbc091e0e57 | train | risk_analysis | codeberg | https://codeberg.org/FloveDocs/4-PsicoSocial-FREE-TRUSTFUL-SOULS | FloveDocs/4-PsicoSocial-FREE-TRUSTFUL-SOULS | marketplace | javascript | python | Perform a deep multi-layer analysis of python for a marketplace using javascript. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "FloveDocs/4-PsicoSocial-FREE-TRUSTFUL-SOULS", "source_url": "https://codeberg.org/FloveDocs/4... | === 1. PROBLEM ===
Define the exact problem involving python. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around python. Use 'FloveDocs/4-PsicoSocial-FREE-TRUSTFUL-SOULS' as a source anchor and identify relevant APIs, depen... | web-research-coding-5m-1.1.0 | |
ba7740f3ca6b48adb76ea674 | train | design_tokens | mdn | https://developer.mozilla.org/en-US/docs/Web/CSS | CSS | landing_page | swift | caching | Create design tokens for a landing_page. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "CSS", "source_url": "https://developer.mozilla.org/en-US/docs/Web/CSS", "source_type": "docum... | Define reusable tokens for typography, spacing, radii, sizing, elevation, interaction states, and responsive behavior. | web-research-coding-5m-1.1.0 | |
e673324d00d4b89f1621332e | train | system_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/HTML | HTML | documentation | html | web_performance | Perform a deep multi-layer analysis of web_performance for a documentation using html. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "HTML", "source_url": "https://developer.mozilla.org/en-US/docs/Web/HTML", "source_type": "doc... | === 1. PROBLEM ===
Define the exact problem involving web_performance. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around web_performance. Use 'HTML' as a source anchor and identify relevant APIs, dependencies, versions, st... | web-research-coding-5m-1.1.0 | |
013a2d73e02dd360c240fd8a | train | repository_understanding | stackexchange | https://stackoverflow.com/questions/41455101/what-is-the-meaning-of-the-word-logits-in-tensorflow | What is the meaning of the word logits in TensorFlow? | productivity | sql | devops | Perform a deep multi-layer analysis of devops for a productivity using sql. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "What is the meaning of the word logits in TensorFlow?", "source_url": "https://stackoverflow.... | === 1. PROBLEM ===
Define the exact problem involving devops. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around devops. Use 'What is the meaning of the word logits in TensorFlow?' as a source anchor and identify relevant A... | web-research-coding-5m-1.1.0 | |
c972ccde0873c17d94e56fb2 | train | html_generation | mdn | https://developer.mozilla.org/en-US/docs/Web/JavaScript | JavaScript | blog | css | data_structures | Create semantic HTML for a blog about data_structures. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "JavaScript", "source_url": "https://developer.mozilla.org/en-US/docs/Web/JavaScript", "source... | Use semantic landmarks, headings, accessible controls, meaningful labels, and correct document structure. | <!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport"
content="width=device-width, initial-scale=1">
<title>Accessible Application</title>
</head>
<body>
<main>
<h1>Application</h1>
</main>
</body>
</html> | web-research-coding-5m-1.1.0 |
34534e8af3d2402a1274732c | train | refactoring_api | web_docs | https://www.postgresql.org/docs/ | PostgreSQL Documentation | analytics | cpp | web_accessibility | Refactor a cpp system related to web_accessibility. Focus on refactoring api. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "PostgreSQL Documentation", "source_url": "https://www.postgresql.org/docs/", "source_type": "... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Improve API contracts, validation, error semantics, compatibility, and versioning.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4.... | web-research-coding-5m-1.1.0 | |
2e73b1704634a96660551673 | train | repository_comparison | npm | https://www.npmjs.com/package/webpack | webpack | portfolio | c | testing | Perform a deep multi-layer analysis of testing for a portfolio using c. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "webpack", "source_url": "https://www.npmjs.com/package/webpack", "source_type": "package", "t... | === 1. PROBLEM ===
Define the exact problem involving testing. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around testing. Use 'webpack' as a source anchor and identify relevant APIs, dependencies, versions, standards, and ... | web-research-coding-5m-1.1.0 | |
7f0abca1e50562a09881129a | train | design_to_code | gitlab | https://gitlab.com/nanuchi/python-programming | nanuchi/python-programming | admin_panel | python | cloud | Translate a admin_panel design into maintainable python code. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "nanuchi/python-programming", "source_url": "https://gitlab.com/nanuchi/python-programming", "... | Map design tokens to code, identify reusable components, preserve responsive behavior, implement accessible states, and avoid unnecessary one-off styling. | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
8f14f11091c35d743f2d575d | train | multi_hop_research | huggingface | https://huggingface.co/datasets/livecodebench/code_generation_lite | livecodebench/code_generation_lite | marketplace | javascript | python | Perform multi-hop research about python: start from a source, follow references, and combine findings. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "livecodebench/code_generation_lite", "source_url": "https://huggingface.co/datasets/livecodeb... | === HOP 1 ===
Start at: livecodebench/code_generation_lite
https://huggingface.co/datasets/livecodebench/code_generation_lite
Extract core claims and references.
=== HOP 2 ===
Follow references to official docs, RFCs, or specs.
Extract primary-source evidence.
=== HOP 3 ===
Check community discussions for real-world ... | web-research-coding-5m-1.1.0 | |
aec8538196f8b62babae2d0b | train | documentation_lookup | npm | https://www.npmjs.com/package/express | express | portfolio | php | nodejs | Find and summarize the relevant documentation for nodejs. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "express", "source_url": "https://www.npmjs.com/package/express", "source_type": "package", "t... | === RELEVANT DOCS ===
- express
https://www.npmjs.com/package/express
- Official project documentation
- API reference
=== KEY SECTIONS ===
- Getting started
- API reference
- Configuration
- Troubleshooting
=== SUMMARY ===
Summarize each section in 1–3 sentences and quote exact signatures where relevant. | web-research-coding-5m-1.1.0 | |
bb2a3d1e4652188090443ce1 | train | ux_analysis | npm | https://www.npmjs.com/package/webpack | webpack | blog | javascript | user_experience | Perform a deep multi-layer analysis of user_experience for a blog using javascript. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "webpack", "source_url": "https://www.npmjs.com/package/webpack", "source_type": "package", "t... | === 1. PROBLEM ===
Define the exact problem involving user_experience. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around user_experience. Use 'webpack' as a source anchor and identify relevant APIs, dependencies, versions,... | web-research-coding-5m-1.1.0 | |
8430df78e76a8e3eb4db0652 | train | refactoring_performance | npm | https://www.npmjs.com/package/eslint | eslint | marketplace | sql | javascript | Refactor a sql system related to javascript. Focus on refactoring performance. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "eslint", "source_url": "https://www.npmjs.com/package/eslint", "source_type": "package", "top... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Reduce unnecessary computation, allocations, I/O, and network requests.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify d... | web-research-coding-5m-1.1.0 | |
a34685b0cf92ba9aebdd24ca | train | repository_comparison | huggingface | https://huggingface.co/datasets/jan-hq/multiturn_programming_binarized | jan-hq/multiturn_programming_binarized | marketplace | shell | data_engineering | Perform a deep multi-layer analysis of data_engineering for a marketplace using shell. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "jan-hq/multiturn_programming_binarized", "source_url": "https://huggingface.co/datasets/jan-h... | === 1. PROBLEM ===
Define the exact problem involving data_engineering. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around data_engineering. Use 'jan-hq/multiturn_programming_binarized' as a source anchor and identify relev... | web-research-coding-5m-1.1.0 | |
fbd749cb2c87e98d61c473cc | train | developer_experience | web_docs | https://git-scm.com/doc | Git Documentation | dashboard | css | nlp | Perform a deep developer-experience analysis for a css project involving nlp. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Git Documentation", "source_url": "https://git-scm.com/doc", "source_type": "documentation", ... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
5d350cd0ab590876b5e68730 | train | product_analysis | web_docs | https://docs.docker.com/ | Docker Documentation | saas | python | nextjs | Perform a deep multi-layer analysis of nextjs for a saas using python. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Docker Documentation", "source_url": "https://docs.docker.com/", "source_type": "documentatio... | === 1. PROBLEM ===
Define the exact problem involving nextjs. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around nextjs. Use 'Docker Documentation' as a source anchor and identify relevant APIs, dependencies, versions, stan... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
67bcac9bba5e53c962090bdf | train | refactoring_observability | stackexchange | https://stackoverflow.com/questions/133051/what-is-the-difference-between-visibilityhidden-and-displaynone | What is the difference between visibility:hidden and display:none? | saas | sql | mongodb | Refactor a sql system related to mongodb. Focus on refactoring observability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "What is the difference between visibility:hidden and display:none?", "source_url": "https://s... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Improve logging, metrics, tracing, diagnostics, and failure visibility.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify d... | web-research-coding-5m-1.1.0 | |
f88c52eb8c6ccf07cf65548c | train | evidence_extraction | pypi | https://pypi.org/project/pydantic/ | pydantic | marketplace | kotlin | observability | Extract verifiable evidence about observability from the given source. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "pydantic", "source_url": "https://pypi.org/project/pydantic/", "source_type": "package", "top... | === SOURCE ===
pydantic
https://pypi.org/project/pydantic/
=== EVIDENCE ITEMS ===
1. Explicit claims made by the source
2. Code examples or API signatures
3. Version / compatibility statements
4. Performance or security notes
=== QUALITY CHECK ===
- Is the claim specific and testable?
- Is the version and environment... | web-research-coding-5m-1.1.0 | |
1ea0608cc9ecb52371f696f7 | train | local_development_experience | github | https://github.com/unionlabs/union | unionlabs/union | community | scala | nodejs | Perform a deep developer-experience analysis for a scala project involving nodejs. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "unionlabs/union", "source_url": "https://github.com/unionlabs/union", "source_type": "reposit... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
85d415ffbb5d7675392771dc | train | documentation_page | pypi | https://pypi.org/project/requests/ | requests | productivity | c | frontend | Design a developer documentation page for frontend. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "requests", "source_url": "https://pypi.org/project/requests/", "source_type": "package", "top... | Include navigation, overview, prerequisites, installation, examples, API reference, troubleshooting, and search. | web-research-coding-5m-1.1.0 | |
e64c39e8f62254ac943f8b38 | train | research_plan | huggingface | https://huggingface.co/datasets/databounty-io/build-competitive-programming-problem-dataset-cmsokff2 | databounty-io/build-competitive-programming-problem-dataset-cmsokff2 | marketplace | java | debugging | Build a structured research plan to deeply understand debugging. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "databounty-io/build-competitive-programming-problem-dataset-cmsokff2", "source_url": "https:/... | === GOAL ===
Produce a reliable, current, and actionable understanding of debugging.
=== PHASES ===
1. Orientation — skim official docs and README.
2. Deep read — study specs, RFCs, changelogs.
3. Hands-on — reproduce examples locally.
4. Comparison — compare alternatives and trade-offs.
5. Synthesis — write findings ... | web-research-coding-5m-1.1.0 | |
ffba14fc310f435d8ca90203 | train | landing_page | mdn | https://developer.mozilla.org/en-US/docs/Web/Accessibility | Accessibility | analytics | cpp | documentation | Design a landing page for a documentation product. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Accessibility", "source_url": "https://developer.mozilla.org/en-US/docs/Web/Accessibility", "... | Include hero, value proposition, features, CTA, FAQ, responsive behavior, SEO, accessibility, and analytics. | web-research-coding-5m-1.1.0 | |
8fb23143c1e2e653ac111f38 | train | web_search_query | npm | https://www.npmjs.com/package/vue | vue | social_app | python | nodejs | Write an effective web search query to research the topic: nodejs. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "vue", "source_url": "https://www.npmjs.com/package/vue", "source_type": "package", "topic": "... | === QUERY ===
nodejs best practices documentation tutorial
=== INTENT ===
Find authoritative documentation, tutorials, and real-world examples related to the topic.
=== KEYWORDS ===
- nodejs
- documentation
- best practices
- examples
- reference
=== SOURCE PREFERENCE ===
Prefer official documentation, well-maintain... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
3461f8fba42e9949eb172ed8 | train | debugging_experience | huggingface | https://huggingface.co/datasets/HuggingFaceH4/CodeAlpaca_20K | HuggingFaceH4/CodeAlpaca_20K | admin_panel | python | authorization | Perform a deep developer-experience analysis for a python project involving authorization. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "HuggingFaceH4/CodeAlpaca_20K", "source_url": "https://huggingface.co/datasets/HuggingFaceH4/C... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
8d455d9682a9c33ddca737b5 | train | refactoring_performance | gitlab | https://gitlab.com/Mojeer/django_components | Mojeer/django_components | marketplace | python | fullstack | Refactor a python system related to fullstack. Focus on refactoring performance. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Mojeer/django_components", "source_url": "https://gitlab.com/Mojeer/django_components", "sour... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Reduce unnecessary computation, allocations, I/O, and network requests.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify d... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
e2e3d4f7e3d295099aab19a6 | train | ui_design | codeberg | https://codeberg.org/emilypummeroy/100-exercises-to-learn-rust | emilypummeroy/100-exercises-to-learn-rust | dashboard | rust | caching | Design a production-quality UI for a dashboard focused on caching. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "emilypummeroy/100-exercises-to-learn-rust", "source_url": "https://codeberg.org/emilypummeroy... | Define layout, typography, spacing, hierarchy, components, states, responsive behavior, and accessibility. | web-research-coding-5m-1.1.0 | |
6ba8127101937e02f81ed9c9 | train | accessibility_fix | huggingface | https://huggingface.co/datasets/NJU-LINK/CodeTraceBench | NJU-LINK/CodeTraceBench | blog | swift | css | Create an accessibility remediation plan for a blog. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "NJU-LINK/CodeTraceBench", "source_url": "https://huggingface.co/datasets/NJU-LINK/CodeTraceBe... | Check semantic HTML, keyboard navigation, focus management, accessible names, labels, errors, contrast, and screen-reader behavior. | web-research-coding-5m-1.1.0 | |
aa404abaeba27ae2ea43cca4 | train | repository_documentation | huggingface | https://huggingface.co/datasets/ml6team/the-stack-smol-python | ml6team/the-stack-smol-python | dashboard | swift | devops | Perform a deep multi-layer analysis of devops for a dashboard using swift. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "ml6team/the-stack-smol-python", "source_url": "https://huggingface.co/datasets/ml6team/the-st... | === 1. PROBLEM ===
Define the exact problem involving devops. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around devops. Use 'ml6team/the-stack-smol-python' as a source anchor and identify relevant APIs, dependencies, versi... | web-research-coding-5m-1.1.0 | |
8ad63cd117990929c88cef97 | train | information_architecture | huggingface | https://huggingface.co/datasets/shangshang/programming-interview-zh-extended | shangshang/programming-interview-zh-extended | ecommerce | python | security | Design the information architecture for security. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "shangshang/programming-interview-zh-extended", "source_url": "https://huggingface.co/datasets... | Organize content into logical categories, navigation levels, search, filtering, and discoverable paths. | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
d91eb2bef539326004b83e99 | train | refactoring_maintainability | npm | https://www.npmjs.com/package/svelte | svelte | social_app | kotlin | ci_cd | Refactor a kotlin system related to ci_cd. Focus on refactoring maintainability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "svelte", "source_url": "https://www.npmjs.com/package/svelte", "source_type": "package", "top... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Improve cohesion, reduce coupling, isolate volatile behavior, and remove duplication.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.... | web-research-coding-5m-1.1.0 | |
420fbbcdb09ebdf21890f1bc | train | search_intent_classification | web_docs | https://fastapi.tiangolo.com/ | FastAPI Documentation | documentation | swift | developer_experience | Classify the search intent for a query about developer_experience. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "FastAPI Documentation", "source_url": "https://fastapi.tiangolo.com/", "source_type": "docume... | === POSSIBLE INTENTS ===
- informational (learn a concept)
- navigational (find a specific site/tool)
- transactional (install / download / run)
- troubleshooting (fix an error)
- comparative (choose between options)
=== EXAMPLE QUERY ===
"developer_experience vs alternatives"
=== CLASSIFICATION ===
Comparative / inf... | web-research-coding-5m-1.1.0 | |
46eab85fa197ec4990658210 | train | upgrade_experience | npm | https://www.npmjs.com/package/typescript | typescript | documentation | swift | documentation | Perform a deep developer-experience analysis for a swift project involving documentation. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "typescript", "source_url": "https://www.npmjs.com/package/typescript", "source_type": "packag... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
9e0eacb422a1a485a48263f0 | train | design_accessibility | npm | https://www.npmjs.com/package/hono | hono | dashboard | kotlin | debugging | Audit accessibility for a dashboard. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "hono", "source_url": "https://www.npmjs.com/package/hono", "source_type": "package", "topic":... | Check semantic structure, keyboard navigation, focus visibility, accessible names, labels, errors, contrast, and screen-reader behavior. | web-research-coding-5m-1.1.0 | |
52627b32f0baab1666e1de53 | train | developer_onboarding | npm | https://www.npmjs.com/package/react | react | finance | typescript | authentication | Perform a deep developer-experience analysis for a typescript project involving authentication. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "react", "source_url": "https://www.npmjs.com/package/react", "source_type": "package", "topic... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
9cdc53d3e7e4f09289ac0a72 | train | source_selection | stackexchange | https://stackoverflow.com/questions/5726729/how-to-parse-json-using-node-js | How to parse JSON using Node.js? | finance | php | machine_learning | Select the most reliable sources to research machine_learning. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How to parse JSON using Node.js?", "source_url": "https://stackoverflow.com/questions/5726729... | === SOURCE TIERS ===
1. Primary: official documentation, specifications, RFCs
2. Secondary: maintained repositories, changelogs, releases
3. Tertiary: tutorials, blog posts, Q&A
=== SELECTION CRITERIA ===
- Authority of the publisher
- Recency and version relevance
- Technical depth
- Reproducibility of examples
=== ... | web-research-coding-5m-1.1.0 | |
f46898587713ed69f57b124f | train | documentation_page | huggingface | https://huggingface.co/datasets/puttatidam/software-documentation-zsm-bitextmining | puttatidam/software-documentation-zsm-bitextmining | analytics | java | authorization | Design a developer documentation page for authorization. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "puttatidam/software-documentation-zsm-bitextmining", "source_url": "https://huggingface.co/da... | Include navigation, overview, prerequisites, installation, examples, API reference, troubleshooting, and search. | web-research-coding-5m-1.1.0 | |
2d461c7c394cae79cad1e9db | train | research_summary | codeberg | https://codeberg.org/emilypummeroy/100-exercises-to-learn-rust | emilypummeroy/100-exercises-to-learn-rust | finance | javascript | ci_cd | Summarize the current state of knowledge about ci_cd. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "emilypummeroy/100-exercises-to-learn-rust", "source_url": "https://codeberg.org/emilypummeroy... | === OVERVIEW ===
ci_cd in one paragraph.
=== KEY CONCEPTS ===
- Core definitions
- Main use cases
- Common patterns
=== CURRENT BEST PRACTICES ===
- Recommended approaches
- Known anti-patterns
=== OPEN QUESTIONS ===
- Areas with active development
- Known limitations
=== PRIMARY SOURCE ===
emilypummeroy/100-exerci... | web-research-coding-5m-1.1.0 | |
f2fcaecceb163b6bd4953ad5 | train | component_design | stackexchange | https://stackoverflow.com/questions/179123/how-to-modify-existing-unpushed-commit-messages | How to modify existing, unpushed commit messages? | portfolio | go | machine_learning | Design reusable UI components for a portfolio. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How to modify existing, unpushed commit messages?", "source_url": "https://stackoverflow.com/... | Define component responsibilities, props/data contracts, variants, states, composition rules, accessibility, testing, and documentation. | web-research-coding-5m-1.1.0 | |
89a5b70aefaf1ba98dda7f5e | train | web_search_query | npm | https://www.npmjs.com/package/three | three | developer_tool | javascript | mongodb | Write an effective web search query to research the topic: mongodb. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "three", "source_url": "https://www.npmjs.com/package/three", "source_type": "package", "topic... | === QUERY ===
mongodb best practices documentation tutorial
=== INTENT ===
Find authoritative documentation, tutorials, and real-world examples related to the topic.
=== KEYWORDS ===
- mongodb
- documentation
- best practices
- examples
- reference
=== SOURCE PREFERENCE ===
Prefer official documentation, well-mainta... | web-research-coding-5m-1.1.0 | |
af27cac3bc5fed8deb42087d | train | ui_design | gitlab | https://gitlab.com/mbitsnbites/soundbox | mbitsnbites/soundbox | search_interface | php | sql | Design a production-quality UI for a search_interface focused on sql. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "mbitsnbites/soundbox", "source_url": "https://gitlab.com/mbitsnbites/soundbox", "source_type"... | Define layout, typography, spacing, hierarchy, components, states, responsive behavior, and accessibility. | web-research-coding-5m-1.1.0 | |
0ef2d0d26ae279b44af4b403 | train | refactoring_performance | huggingface | https://huggingface.co/datasets/HuggingFaceH4/testing_codealpaca_small | HuggingFaceH4/testing_codealpaca_small | analytics | javascript | machine_learning | Refactor a javascript system related to machine_learning. Focus on refactoring performance. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "HuggingFaceH4/testing_codealpaca_small", "source_url": "https://huggingface.co/datasets/Huggi... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Reduce unnecessary computation, allocations, I/O, and network requests.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify d... | web-research-coding-5m-1.1.0 | |
2200239ee0b003fbf8d7fe9f | train | deployment_experience | mdn | https://developer.mozilla.org/en-US/docs/Web/CSS | CSS | community | java | user_experience | Perform a deep developer-experience analysis for a java project involving user_experience. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "CSS", "source_url": "https://developer.mozilla.org/en-US/docs/Web/CSS", "source_type": "docum... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
f978d8fd34ac40bf6297163c | train | code_review | stackexchange | https://stackoverflow.com/questions/11632516/what-are-advantages-of-artificial-neural-networks-over-support-vector-machines | What are advantages of Artificial Neural Networks over Support Vector Machines? | admin_panel | html | algorithms | Perform a production code review of html code related to algorithms. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "What are advantages of Artificial Neural Networks over Support Vector Machines?", "source_url... | Review correctness, security, performance, readability, architecture, testing, maintainability, and error handling. | web-research-coding-5m-1.1.0 | |
170c85bc0c193bd9eacc29b5 | train | performance_analysis | stackexchange | https://stackoverflow.com/questions/2052390/manually-raising-throwing-an-exception-in-python | Manually raising (throwing) an exception in Python | saas | c | web_performance | Perform a deep multi-layer analysis of web_performance for a saas using c. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Manually raising (throwing) an exception in Python", "source_url": "https://stackoverflow.com... | === 1. PROBLEM ===
Define the exact problem involving web_performance. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around web_performance. Use 'Manually raising (throwing) an exception in Python' as a source anchor and iden... | web-research-coding-5m-1.1.0 | |
5f8f7ae86cec5b05d6cce6c6 | train | performance_analysis | stackexchange | https://stackoverflow.com/questions/34930735/pros-cons-of-using-redux-saga-with-es6-generators-vs-redux-thunk-with-es2017-asy | Pros/cons of using redux-saga with ES6 generators vs redux-thunk with ES2017 async/await | saas | c | distributed_systems | Perform a deep multi-layer analysis of distributed_systems for a saas using c. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Pros/cons of using redux-saga with ES6 generators vs redux-thunk with ES2017 async/await", "s... | === 1. PROBLEM ===
Define the exact problem involving distributed_systems. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around distributed_systems. Use 'Pros/cons of using redux-saga with ES6 generators vs redux-thunk with E... | web-research-coding-5m-1.1.0 | |
b5456c09f2ac30af313c8e50 | train | refactoring_observability | stackexchange | https://stackoverflow.com/questions/306252/how-to-align-checkboxes-and-their-labels-consistently-cross-browsers | How to align checkboxes and their labels consistently cross-browsers | dashboard | shell | web_accessibility | Refactor a shell system related to web_accessibility. Focus on refactoring observability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How to align checkboxes and their labels consistently cross-browsers", "source_url": "https:/... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Improve logging, metrics, tracing, diagnostics, and failure visibility.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify d... | web-research-coding-5m-1.1.0 | |
50cb3b34e6952ab93a515c5d | train | upgrade_experience | huggingface | https://huggingface.co/datasets/kloodia/javascript_200k | kloodia/javascript_200k | developer_tool | ruby | redis | Perform a deep developer-experience analysis for a ruby project involving redis. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "kloodia/javascript_200k", "source_url": "https://huggingface.co/datasets/kloodia/javascript_2... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
f08e1d47b503120dc436fc4c | train | security_analysis | web_docs | https://go.dev/doc/ | Go Documentation | documentation | cpp | devops | Perform a deep multi-layer analysis of devops for a documentation using cpp. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Go Documentation", "source_url": "https://go.dev/doc/", "source_type": "documentation", "topi... | === 1. PROBLEM ===
Define the exact problem involving devops. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around devops. Use 'Go Documentation' as a source anchor and identify relevant APIs, dependencies, versions, standard... | web-research-coding-5m-1.1.0 | |
e0f47d3f11c6d44264723679 | train | refactoring_observability | pypi | https://pypi.org/project/streamlit/ | streamlit | education | cpp | python | Refactor a cpp system related to python. Focus on refactoring observability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "streamlit", "source_url": "https://pypi.org/project/streamlit/", "source_type": "package", "t... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Improve logging, metrics, tracing, diagnostics, and failure visibility.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify d... | web-research-coding-5m-1.1.0 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.