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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
13b389d562bf777d92f2e2c5 | train | api_design | npm | https://www.npmjs.com/package/vite | vite | marketplace | rust | frontend | Design a production API for a frontend application. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "vite", "source_url": "https://www.npmjs.com/package/vite", "source_type": "package", "topic":... | Specify resources, endpoints, schemas, validation, authentication, authorization, errors, pagination, versioning, idempotency, and tests. | web-research-coding-5m-1.1.0 | |
da919fa580bd90c2173988ba | train | nextjs_generation | pypi | https://pypi.org/project/typer/ | typer | marketplace | sql | web_performance | Design a Next.js architecture for a marketplace. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "typer", "source_url": "https://pypi.org/project/typer/", "source_type": "package", "topic": "... | Specify routing, server/client boundaries, data fetching, caching, metadata, errors, and deployment. | export default function Page() {
return (
<main>
<h1>Application</h1>
<p>Production-ready page structure.</p>
</main>
);
} | web-research-coding-5m-1.1.0 |
03f224bfad859f74cf700a14 | train | debugging_experience | stackexchange | https://stackoverflow.com/questions/3680429/click-through-div-to-underlying-elements | Click through div to underlying elements | marketplace | ruby | distributed_systems | Perform a deep developer-experience analysis for a ruby project involving distributed_systems. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Click through div to underlying elements", "source_url": "https://stackoverflow.com/questions... | === 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 | |
0de2cf75e3655e77e84305e1 | train | multi_layer_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/HTML | HTML | landing_page | shell | docker | Perform a deep multi-layer analysis of docker for a landing_page 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": "HTML", "source_url": "https://developer.mozilla.org/en-US/docs/Web/HTML", "source_type": "doc... | === 1. PROBLEM ===
Define the exact problem involving docker. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around docker. Use 'HTML' as a source anchor and identify relevant APIs, dependencies, versions, standards, and techn... | web-research-coding-5m-1.1.0 | |
b1af66f7e4007e45da5afaad | train | api_developer_experience | 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 | typescript | redis | Perform a deep developer-experience analysis for a typescript project involving redis. | {"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... | === 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 | |
6bd97d00ddb41f7095edfeff | train | fact_verification | mdn | https://developer.mozilla.org/en-US/docs/Web/Performance | Performance | productivity | scala | kubernetes | Verify a technical claim about kubernetes. | {"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... | === CLAIM ===
A common claim about kubernetes.
=== 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 | |
85406fbf29e2ed72aa0f8be3 | train | deployment_experience | github | https://github.com/TheAlgorithms/C-Plus-Plus | TheAlgorithms/C-Plus-Plus | developer_tool | scala | typescript | Perform a deep developer-experience analysis for a scala project involving typescript. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "TheAlgorithms/C-Plus-Plus", "source_url": "https://github.com/TheAlgorithms/C-Plus-Plus", "so... | === 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 | |
db2c64405e5b43cd9109d58e | train | scalability_analysis | gitlab | https://gitlab.com/roth1002/awesome-javascript | roth1002/awesome-javascript | documentation | sql | redis | Perform a deep multi-layer analysis of redis for a documentation 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": "roth1002/awesome-javascript", "source_url": "https://gitlab.com/roth1002/awesome-javascript",... | === 1. PROBLEM ===
Define the exact problem involving redis. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around redis. Use 'roth1002/awesome-javascript' as a source anchor and identify relevant APIs, dependencies, versions,... | web-research-coding-5m-1.1.0 | |
689cb68eeb8b2a9f83d998ca | train | dependency_management_experience | mdn | https://developer.mozilla.org/en-US/docs/Web/JavaScript | JavaScript | education | typescript | react | Perform a deep developer-experience analysis for a typescript project involving react. | {"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... | === 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 | |
c7a0e4b4fb99693f25bfb32e | train | cli_experience | web_docs | https://doc.rust-lang.org/ | Rust Documentation | developer_tool | javascript | api_design | Perform a deep developer-experience analysis for a javascript project involving api_design. | {"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. 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 | |
73d1140ee1462a03ea274175 | train | typescript_generation | huggingface | https://huggingface.co/datasets/tikushitam/documentation-images | tikushitam/documentation-images | dashboard | typescript | fullstack | Implement TypeScript logic for a dashboard. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "tikushitam/documentation-images", "source_url": "https://huggingface.co/datasets/tikushitam/d... | Use explicit types, interfaces, safe narrowing, validation, and maintainable modules. | function validateInput(value) {
if (!value || value.trim().length === 0) {
throw new Error("Input is required");
}
return value.trim();
} | web-research-coding-5m-1.1.0 |
aad3b0778e1f2c832b88f106 | train | architecture_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/CSS | CSS | social_app | swift | serverless | Perform a deep multi-layer analysis of serverless for a social_app 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": "CSS", "source_url": "https://developer.mozilla.org/en-US/docs/Web/CSS", "source_type": "docum... | === 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 'CSS' as a source anchor and identify relevant APIs, dependencies, versions, standards, an... | web-research-coding-5m-1.1.0 | |
12eed807cd1309d34ee9580a | train | developer_onboarding | gitlab | https://gitlab.com/ironfox-oss/IronFox | ironfox-oss/IronFox | community | javascript | design_system | Perform a deep developer-experience analysis for a javascript project involving design_system. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "ironfox-oss/IronFox", "source_url": "https://gitlab.com/ironfox-oss/IronFox", "source_type": ... | === 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 | |
821340a92e2afce6eea8e0d7 | train | refactoring_scalability | mdn | https://developer.mozilla.org/en-US/docs/Web/HTTP | HTTP | finance | java | api_design | Refactor a java system related to api_design. Focus on refactoring scalability. | {"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... | === 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 | |
64151717175eab234e4940de | train | refactoring_modularization | gitlab | https://gitlab.com/unconed/use.gpu | unconed/use.gpu | saas | sql | data_engineering | Refactor a sql system related to data_engineering. Focus on refactoring modularization. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "unconed/use.gpu", "source_url": "https://gitlab.com/unconed/use.gpu", "source_type": "reposit... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Split large modules into cohesive units with explicit responsibilities.
=== 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 | |
a0bf8ffe62944354c9b06d42 | train | dx_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/API | Web APIs | community | scala | distributed_systems | Perform a deep developer-experience analysis for a scala project involving distributed_systems. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Web APIs", "source_url": "https://developer.mozilla.org/en-US/docs/Web/API", "source_type": "... | === 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 | |
5315581f39bb806cad8d4767 | train | data_structure_design | huggingface | https://huggingface.co/datasets/kwatcharasupat/dnr-v3-multilingual | kwatcharasupat/dnr-v3-multilingual | social_app | dart | microservices | Design a data structure in dart for microservices. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "kwatcharasupat/dnr-v3-multilingual", "source_url": "https://huggingface.co/datasets/kwatchara... | Explain representation, operations, complexity, memory trade-offs, and workload suitability. | web-research-coding-5m-1.1.0 | |
5ece982ce72400e6947fc5bc | train | repository_issue_reasoning | gitlab | https://gitlab.com/rebornos-team/fenix/fenix-installer | rebornos-team/fenix/fenix-installer | documentation | html | devops | Perform a deep multi-layer analysis of devops 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": "rebornos-team/fenix/fenix-installer", "source_url": "https://gitlab.com/rebornos-team/fenix/f... | === 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 'rebornos-team/fenix/fenix-installer' as a source anchor and identify relevant APIs, dependencies,... | web-research-coding-5m-1.1.0 | |
6d90b3f5e76ad31f07ca18cd | train | technical_research | web_docs | https://git-scm.com/doc | Git Documentation | finance | php | linux | Perform a technical research task about linux, focused on implementation details. | {"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", ... | === SCOPE ===
Technical behavior of linux.
=== QUESTIONS ===
- What are the inputs, outputs, and invariants?
- What are the performance characteristics?
- What are the security implications?
- What are the compatibility constraints?
=== EVIDENCE ===
- Git Documentation (https://git-scm.com/doc)
- Official documentati... | web-research-coding-5m-1.1.0 | |
cff44b044f48810724c77453 | train | integration_testing | stackexchange | https://stackoverflow.com/questions/2941189/how-to-overlay-one-div-over-another-div | How to overlay one div over another div | marketplace | shell | computer_vision | Design integration tests for a shell system involving computer_vision. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How to overlay one div over another div", "source_url": "https://stackoverflow.com/questions/... | Test real component boundaries, persistence, configuration, external interfaces, errors, cleanup, and realistic workflows. | web-research-coding-5m-1.1.0 | |
b80505096923c01061d0c4cb | train | refactoring_performance | huggingface | https://huggingface.co/datasets/ShawRickZia/machine-learning-forecasting-data | ShawRickZia/machine-learning-forecasting-data | portfolio | typescript | nodejs | Refactor a typescript system related to nodejs. Focus on refactoring performance. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "ShawRickZia/machine-learning-forecasting-data", "source_url": "https://huggingface.co/dataset... | === 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 | |
61962856d2e2a6323acaf039 | train | dx_analysis | web_docs | https://nodejs.org/docs/latest/api/ | Node.js Documentation | education | python | backend | Perform a deep developer-experience analysis for a python project involving backend. | {"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": "... | === 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 |
a47f23e9fc492e866c2e29d9 | train | dashboard | stackexchange | https://stackoverflow.com/questions/287871/how-do-i-print-colored-text-to-the-terminal | How do I print colored text to the terminal? | ecommerce | shell | debugging | Design a production dashboard for debugging. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How do I print colored text to the terminal?", "source_url": "https://stackoverflow.com/quest... | Include navigation, KPIs, tables/charts, filters, loading states, empty states, errors, and responsive behavior. | web-research-coding-5m-1.1.0 | |
addf5c88a919e6ace1f0089b | train | design_accessibility | gitlab | https://gitlab.com/cyber5k/mistborn | cyber5k/mistborn | ecommerce | dart | mongodb | Audit accessibility for a ecommerce. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "cyber5k/mistborn", "source_url": "https://gitlab.com/cyber5k/mistborn", "source_type": "repos... | Check semantic structure, keyboard navigation, focus visibility, accessible names, labels, errors, contrast, and screen-reader behavior. | web-research-coding-5m-1.1.0 | |
802cd4c508943696e22b376f | train | security_analysis | gitlab | https://gitlab.com/nfriend/tree-online | nfriend/tree-online | marketplace | java | data_engineering | Perform a deep multi-layer analysis of data_engineering for a marketplace using java. 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": "nfriend/tree-online", "source_url": "https://gitlab.com/nfriend/tree-online", "source_type": ... | === 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 'nfriend/tree-online' as a source anchor and identify relevant APIs, dependenc... | web-research-coding-5m-1.1.0 | |
18297ff462986b0e0e53b179 | train | refactoring_performance | gitlab | https://gitlab.com/philbooth/check-types.js | philbooth/check-types.js | social_app | ruby | web_accessibility | Refactor a ruby system related to web_accessibility. Focus on refactoring performance. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "philbooth/check-types.js", "source_url": "https://gitlab.com/philbooth/check-types.js", "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... | web-research-coding-5m-1.1.0 | |
9c13898d0a4830183f107e55 | train | ux_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/HTML | HTML | documentation | php | devops | Perform a deep multi-layer analysis of devops for a documentation 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": "HTML", "source_url": "https://developer.mozilla.org/en-US/docs/Web/HTML", "source_type": "doc... | === 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 'HTML' as a source anchor and identify relevant APIs, dependencies, versions, standards, and techn... | web-research-coding-5m-1.1.0 | |
4de52397c41b9feb31f98ff4 | train | cli_experience | npm | https://www.npmjs.com/package/eslint | eslint | blog | go | database | Perform a deep developer-experience analysis for a go project involving database. | {"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... | === 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 | |
184372babbc183456fc68720 | train | security_review | web_docs | https://docs.djangoproject.com/ | Django Documentation | landing_page | css | linux | Perform a security review of a landing_page application. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Django Documentation", "source_url": "https://docs.djangoproject.com/", "source_type": "docum... | Review authentication, authorization, input validation, XSS, CSRF, injection risks, secrets, dependencies, security headers, and logging. | web-research-coding-5m-1.1.0 | |
3f494921b2035cc2e60c3892 | train | search_intent_classification | huggingface | https://huggingface.co/datasets/livecodebench/code_generation_lite | livecodebench/code_generation_lite | developer_tool | ruby | microservices | Classify the search intent for a query about microservices. | {"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... | === 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 ===
"microservices vs alternatives"
=== CLASSIFICATION ===
Comparative / informatio... | web-research-coding-5m-1.1.0 | |
185d4ff2124d601af8945318 | train | multi_hop_research | huggingface | https://huggingface.co/datasets/nomic-ai/cornstack-python-v1 | nomic-ai/cornstack-python-v1 | dashboard | java | 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": "nomic-ai/cornstack-python-v1", "source_url": "https://huggingface.co/datasets/nomic-ai/cornst... | === HOP 1 ===
Start at: nomic-ai/cornstack-python-v1
https://huggingface.co/datasets/nomic-ai/cornstack-python-v1
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.
Extr... | web-research-coding-5m-1.1.0 | |
746d10880e46c065832e200d | train | dx_analysis | gitlab | https://gitlab.com/nfriend/ts-key-enum | nfriend/ts-key-enum | landing_page | python | fullstack | Perform a deep developer-experience analysis for a python project involving fullstack. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "nfriend/ts-key-enum", "source_url": "https://gitlab.com/nfriend/ts-key-enum", "source_type": ... | === 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 |
54e89f06ef14d8000b4b90c5 | train | fact_verification | stackexchange | https://stackoverflow.com/questions/13315131/enforcing-the-type-of-the-indexed-members-of-a-typescript-object | Enforcing the type of the indexed members of a Typescript object? | finance | java | linux | Verify a technical claim about linux. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Enforcing the type of the indexed members of a Typescript object?", "source_url": "https://st... | === CLAIM ===
A common claim about linux.
=== 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-depende... | web-research-coding-5m-1.1.0 | |
2e0930c7479d4fc88e618293 | train | deployment_experience | huggingface | https://huggingface.co/datasets/Lots-of-LoRAs/task718_mmmlu_answer_generation_machine_learning | Lots-of-LoRAs/task718_mmmlu_answer_generation_machine_learning | education | css | api_design | Perform a deep developer-experience analysis for a css project involving api_design. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Lots-of-LoRAs/task718_mmmlu_answer_generation_machine_learning", "source_url": "https://huggi... | === 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 | |
b35b7231dc0a44a2b25d6fdb | train | visual_hierarchy | web_docs | https://www.typescriptlang.org/docs/ | TypeScript Documentation | analytics | javascript | testing | Improve visual hierarchy in a analytics. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "TypeScript Documentation", "source_url": "https://www.typescriptlang.org/docs/", "source_type... | Use heading structure, typography, spacing, grouping, alignment, contrast, and consistent affordances. | web-research-coding-5m-1.1.0 | |
50c11d45c5c253d93149dcf3 | train | refactoring_maintainability | mdn | https://developer.mozilla.org/en-US/docs/Web/CSS | CSS | dashboard | php | algorithms | Refactor a php system related to algorithms. Focus on refactoring maintainability. | {"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... | === 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 | |
9d8847760d5a42d6cca49b3c | train | repository_architecture | stackexchange | https://stackoverflow.com/questions/4351521/how-do-i-pass-command-line-arguments-to-a-node-js-program-and-receive-them | How do I pass command line arguments to a Node.js program and receive them? | social_app | javascript | typescript | Perform a deep multi-layer analysis of typescript for a social_app 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": "How do I pass command line arguments to a Node.js program and receive them?", "source_url": "... | === 1. PROBLEM ===
Define the exact problem involving typescript. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around typescript. Use 'How do I pass command line arguments to a Node.js program and receive them?' as a source ... | web-research-coding-5m-1.1.0 | |
eef8e6f86c2ecf514ba9b646 | train | refactoring_modularization | stackexchange | https://stackoverflow.com/questions/5805059/how-do-i-make-a-placeholder-for-a-select-box | How do I make a placeholder for a 'select' box? | social_app | css | backend | Refactor a css system related to backend. Focus on refactoring modularization. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How do I make a placeholder for a 'select' box?", "source_url": "https://stackoverflo... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Split large modules into cohesive units with explicit responsibilities.
=== 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 | |
a26b9ff15d462f1b2322e635 | train | design_components | github | https://github.com/shap/shap | shap/shap | marketplace | python | database | Create a component architecture for a marketplace. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "shap/shap", "source_url": "https://github.com/shap/shap", "source_type": "repository", "topic... | Define primitive components, composite components, variants, states, composition rules, and accessibility contracts. | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
19dda25bdcf92118a50887bb | train | source_comparison | gitlab | https://gitlab.com/bvobart/python-ml-analysis | bvobart/python-ml-analysis | blog | html | postgresql | Compare multiple sources about postgresql and identify agreements, contradictions, and gaps. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "bvobart/python-ml-analysis", "source_url": "https://gitlab.com/bvobart/python-ml-analysis", "... | === SOURCES ===
- bvobart/python-ml-analysis (https://gitlab.com/bvobart/python-ml-analysis)
- Official documentation
- Community discussions
=== AGREEMENTS ===
Identify claims supported by multiple independent sources.
=== CONTRADICTIONS ===
Identify conflicting claims and their likely cause (version differences, en... | web-research-coding-5m-1.1.0 | |
e7eb57ad999da0a7f66e499c | train | refactoring | huggingface | https://huggingface.co/datasets/dougiefresh/systems_programming_code_conversations | dougiefresh/systems_programming_code_conversations | analytics | dart | ci_cd | Create a production coding task in dart for ci_cd. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "dougiefresh/systems_programming_code_conversations", "source_url": "https://huggingface.co/da... | Provide implementation requirements, edge cases, testing requirements, security considerations, performance constraints, and documentation requirements. | web-research-coding-5m-1.1.0 | |
ab45e03c6480794ccd89449d | train | typescript_generation | stackexchange | https://stackoverflow.com/questions/1789945/how-to-check-whether-a-string-contains-a-substring-in-javascript | How to check whether a string contains a substring in JavaScript? | search_interface | cpp | devops | Implement TypeScript logic for a search_interface. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How to check whether a string contains a substring in JavaScript?", "source_url": "https://st... | Use explicit types, interfaces, safe narrowing, validation, and maintainable modules. | function validateInput(value) {
if (!value || value.trim().length === 0) {
throw new Error("Input is required");
}
return value.trim();
} | web-research-coding-5m-1.1.0 |
86b27b02d233a4b2d5cb6481 | train | debugging_experience | pypi | https://pypi.org/project/httpx/ | httpx | landing_page | sql | open_source | Perform a deep developer-experience analysis for a sql project involving open_source. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "httpx", "source_url": "https://pypi.org/project/httpx/", "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 | |
f14bc53bb8e4c1251242497e | train | build_experience | codeberg | https://codeberg.org/m5blum/acweb | m5blum/acweb | saas | java | api_design | Perform a deep developer-experience analysis for a java project involving api_design. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "m5blum/acweb", "source_url": "https://codeberg.org/m5blum/acweb", "source_type": "repository"... | === 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 | |
2e77531c9a5480fed20861ed | train | maintainability_analysis | stackexchange | https://stackoverflow.com/questions/31163693/how-do-i-conditionally-add-attributes-to-react-components | How do I conditionally add attributes to React components? | portfolio | python | web_accessibility | Perform a deep multi-layer analysis of web_accessibility for a portfolio 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": "How do I conditionally add attributes to React components?", "source_url": "https://stackover... | === 1. PROBLEM ===
Define the exact problem involving web_accessibility. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around web_accessibility. Use 'How do I conditionally add attributes to React components?' as a source anc... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
7883ac0c07b87fdef8b6648b | train | refactoring_api | mdn | https://developer.mozilla.org/en-US/docs/Web/HTML | HTML | blog | c | sql | Refactor a c system related to sql. Focus on refactoring api. | {"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... | === 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 | |
150ac692059c6bbc68a3705b | train | refactoring_architecture | web_docs | https://git-scm.com/doc | Git Documentation | documentation | cpp | developer_experience | Refactor a cpp system related to developer_experience. Focus on refactoring architecture. | {"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", ... | === 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 | |
c2247d3ada151f4d8a577890 | train | research_plan | gitlab | https://gitlab.com/FirstTerraner/proclubs-api | FirstTerraner/proclubs-api | social_app | sql | rest_api | Build a structured research plan to deeply understand rest_api. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "FirstTerraner/proclubs-api", "source_url": "https://gitlab.com/FirstTerraner/proclubs-api", "... | === GOAL ===
Produce a reliable, current, and actionable understanding of rest_api.
=== 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 w... | web-research-coding-5m-1.1.0 | |
e675272a5b66636acadc02c0 | train | source_comparison | web_docs | https://react.dev/ | React Documentation | developer_tool | typescript | rest_api | Compare multiple sources about rest_api and identify agreements, contradictions, and gaps. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "React Documentation", "source_url": "https://react.dev/", "source_type": "documentation", "to... | === SOURCES ===
- React Documentation (https://react.dev/)
- Official documentation
- Community discussions
=== AGREEMENTS ===
Identify claims supported by multiple independent sources.
=== CONTRADICTIONS ===
Identify conflicting claims and their likely cause (version differences, environment, outdated info).
=== GA... | web-research-coding-5m-1.1.0 | |
54c038536daa7ff8c03d58ab | train | documentation_page | github | https://github.com/storybookjs/storybook | storybookjs/storybook | landing_page | kotlin | 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": "storybookjs/storybook", "source_url": "https://github.com/storybookjs/storybook", "source_typ... | Include navigation, overview, prerequisites, installation, examples, API reference, troubleshooting, and search. | web-research-coding-5m-1.1.0 | |
a7cb00d2a900f070b035fcdf | train | repository_documentation | gitlab | https://gitlab.com/ai_lab_cs_lm/2024_2025/ai_course_template | ai_lab_cs_lm/2024_2025/ai_course_template | education | python | computer_vision | Perform a deep multi-layer analysis of computer_vision for a education 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": "ai_lab_cs_lm/2024_2025/ai_course_template", "source_url": "https://gitlab.com/ai_lab_cs_lm/20... | === 1. PROBLEM ===
Define the exact problem involving computer_vision. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around computer_vision. Use 'ai_lab_cs_lm/2024_2025/ai_course_template' as a source anchor and identify rele... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
b2d422d49efe633383e7096e | train | refactoring_scalability | npm | https://www.npmjs.com/package/next | next | admin_panel | rust | machine_learning | Refactor a rust 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": "next", "source_url": "https://www.npmjs.com/package/next", "source_type": "package", "topic":... | === 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 | |
63cfc2efe7c9dfa92f2eb5c2 | train | data_structure_design | gitlab | https://gitlab.com/panoramax/clients/web-viewer | panoramax/clients/web-viewer | productivity | css | user_experience | Design a data structure in css for user_experience. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "panoramax/clients/web-viewer", "source_url": "https://gitlab.com/panoramax/clients/web-viewer... | Explain representation, operations, complexity, memory trade-offs, and workload suitability. | web-research-coding-5m-1.1.0 | |
753a985bbebe39c19793162a | train | risk_analysis | gitlab | https://gitlab.com/gitlab-ci-utils/gitlab-semgrep-plus | gitlab-ci-utils/gitlab-semgrep-plus | productivity | sql | user_experience | Perform a deep multi-layer analysis of user_experience 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": "gitlab-ci-utils/gitlab-semgrep-plus", "source_url": "https://gitlab.com/gitlab-ci-utils/gitla... | === 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 'gitlab-ci-utils/gitlab-semgrep-plus' as a source anchor and identify relevant A... | web-research-coding-5m-1.1.0 | |
ea6bed68992c65d3a3590710 | train | system_analysis | pypi | https://pypi.org/project/gradio/ | gradio | social_app | dart | open_source | Perform a deep multi-layer analysis of open_source for a social_app 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": "gradio", "source_url": "https://pypi.org/project/gradio/", "source_type": "package", "topic":... | === 1. PROBLEM ===
Define the exact problem involving open_source. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around open_source. Use 'gradio' as a source anchor and identify relevant APIs, dependencies, versions, standard... | web-research-coding-5m-1.1.0 | |
5ce79fbe2ba63a20ced4314f | train | component_design | web_docs | https://go.dev/doc/ | Go Documentation | developer_tool | scala | algorithms | Design reusable UI components for a developer_tool. | {"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... | Define component responsibilities, props/data contracts, variants, states, composition rules, accessibility, testing, and documentation. | web-research-coding-5m-1.1.0 | |
9b09fb0862ae71567c9e55a4 | train | javascript_generation | web_docs | https://go.dev/doc/ | Go Documentation | marketplace | java | nodejs | Implement JavaScript interactions for a marketplace. | {"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... | Use modular event handling, validation, state management, error handling, and progressive enhancement. | function validateInput(value) {
if (!value || value.trim().length === 0) {
throw new Error("Input is required");
}
return value.trim();
} | web-research-coding-5m-1.1.0 |
4568be127caa2008a1c62c90 | train | interaction_design | npm | https://www.npmjs.com/package/webpack | webpack | landing_page | css | data_structures | Design interaction states for a landing_page. | {"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... | Specify default, hover, focus, active, disabled, loading, success, error, and empty states. | web-research-coding-5m-1.1.0 | |
226f2eb4aaf8647c8d159f0e | train | security_analysis | stackexchange | https://stackoverflow.com/questions/336859/var-functionname-function-vs-function-functionname | var functionName = function() {} vs function functionName() {} | community | java | open_source | Perform a deep multi-layer analysis of open_source for a community using java. 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": "var functionName = function() {} vs function functionName() {}", "source_url": "https://stack... | === 1. PROBLEM ===
Define the exact problem involving open_source. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around open_source. Use 'var functionName = function() {} vs function functionName() {}' as a source anchor and ... | web-research-coding-5m-1.1.0 | |
8fb79616863f183ec4d2872f | train | refactoring_security | codeberg | https://codeberg.org/UI-Programming-23-24/01-Web-basics-and-git-Corey-Doyle | UI-Programming-23-24/01-Web-basics-and-git-Corey-Doyle | community | shell | docker | Refactor a shell system related to docker. Focus on refactoring security. | {"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-Corey-Doyle", "source_url": "https://codeberg.org/... | === 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 | |
2b94722eb9ba5c91a5ae2a41 | train | search_query_rewrite | 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 | ecommerce | typescript | distributed_systems | Rewrite and improve a vague search query about distributed_systems 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": "ashishpatel26/500-AI-Machine-learning-Deep-learning-Computer-vision-NLP-Projects-with-code", ... | === ORIGINAL (VAGUE) ===
how to do distributed_systems
=== REWRITTEN QUERIES ===
1. distributed_systems official documentation guide
2. distributed_systems production best practices 2025
3. distributed_systems common pitfalls and solutions
4. distributed_systems architecture patterns with examples
=== RATIONALE ===
A... | web-research-coding-5m-1.1.0 | |
94caa9c63f2e89d7b4e02ab5 | train | code_review | huggingface | https://huggingface.co/datasets/ajibawa-2023/JavaScript-Code-Large | ajibawa-2023/JavaScript-Code-Large | education | dart | cloud | Perform a production code review of dart code related to cloud. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "ajibawa-2023/JavaScript-Code-Large", "source_url": "https://huggingface.co/datasets/ajibawa-2... | Review correctness, security, performance, readability, architecture, testing, maintainability, and error handling. | web-research-coding-5m-1.1.0 | |
fbb227a4c9732582351011f4 | train | multi_layer_analysis | codeberg | https://codeberg.org/import-benjamin/.dotfiles | import-benjamin/.dotfiles | finance | javascript | authorization | Perform a deep multi-layer analysis of authorization for a finance 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": "import-benjamin/.dotfiles", "source_url": "https://codeberg.org/import-benjamin/.dotfiles", "... | === 1. PROBLEM ===
Define the exact problem involving authorization. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around authorization. Use 'import-benjamin/.dotfiles' as a source anchor and identify relevant APIs, dependenc... | web-research-coding-5m-1.1.0 | |
807389502ad6eb84cf298135 | train | fact_verification | web_docs | https://docs.python.org/3/ | Python Documentation | analytics | kotlin | nodejs | Verify a technical claim about nodejs. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Python Documentation", "source_url": "https://docs.python.org/3/", "source_type": "documentat... | === CLAIM ===
A common claim about nodejs.
=== 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-depend... | web-research-coding-5m-1.1.0 | |
98b46aa8eeddc43a4dcba848 | train | root_cause_analysis | pypi | https://pypi.org/project/httpx/ | httpx | marketplace | cpp | web_performance | Perform a deep multi-layer analysis of web_performance for a marketplace 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": "httpx", "source_url": "https://pypi.org/project/httpx/", "source_type": "package", "topic": "... | === 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 'httpx' as a source anchor and identify relevant APIs, dependencies, versions, s... | web-research-coding-5m-1.1.0 | |
a543431406aad554a8792ff1 | train | repository_understanding | npm | https://www.npmjs.com/package/vue | vue | dashboard | scala | data_engineering | Perform a deep multi-layer analysis of data_engineering for a dashboard using scala. 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": "vue", "source_url": "https://www.npmjs.com/package/vue", "source_type": "package", "topic": "... | === 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 'vue' as a source anchor and identify relevant APIs, dependencies, versions, s... | web-research-coding-5m-1.1.0 | |
e9ba82ef5b57e56818bd2ac6 | train | build_experience | gitlab | https://gitlab.com/doctormo/python-crontab | doctormo/python-crontab | search_interface | dart | backend | Perform a deep developer-experience analysis for a dart project involving backend. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "doctormo/python-crontab", "source_url": "https://gitlab.com/doctormo/python-crontab", "source... | === 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 | |
8ce6a5c1cd0455949a553d67 | train | search_intent_classification | stackexchange | https://stackoverflow.com/questions/21247278/about-d-ts-in-typescript | About "*.d.ts" in TypeScript | finance | sql | devops | Classify the search intent for a query about devops. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "About "*.d.ts" in TypeScript", "source_url": "https://stackoverflow.com/questions/2... | === 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 ===
"devops vs alternatives"
=== CLASSIFICATION ===
Comparative / informational.
=... | web-research-coding-5m-1.1.0 | |
293804726968086f4a6041f9 | train | interaction_design | github | https://github.com/thedaviddias/Front-End-Checklist | thedaviddias/Front-End-Checklist | social_app | swift | deep_learning | Design interaction states for a social_app. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "thedaviddias/Front-End-Checklist", "source_url": "https://github.com/thedaviddias/Front-End-C... | Specify default, hover, focus, active, disabled, loading, success, error, and empty states. | web-research-coding-5m-1.1.0 | |
5537e1e1a57f44c4ea123203 | train | search_query_rewrite | pypi | https://pypi.org/project/scikit-learn/ | scikit-learn | analytics | kotlin | javascript | Rewrite and improve a vague search query about javascript 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": "scikit-learn", "source_url": "https://pypi.org/project/scikit-learn/", "source_type": "packag... | === ORIGINAL (VAGUE) ===
how to do javascript
=== REWRITTEN QUERIES ===
1. javascript official documentation guide
2. javascript production best practices 2025
3. javascript common pitfalls and solutions
4. javascript architecture patterns with examples
=== RATIONALE ===
Add intent (learn / implement / debug), specif... | web-research-coding-5m-1.1.0 | |
bef65a4d8dc3d3b26b98d144 | train | design_components | pypi | https://pypi.org/project/sqlalchemy/ | sqlalchemy | dashboard | kotlin | debugging | Create a component architecture for a dashboard. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "sqlalchemy", "source_url": "https://pypi.org/project/sqlalchemy/", "source_type": "package", ... | Define primitive components, composite components, variants, states, composition rules, and accessibility contracts. | web-research-coding-5m-1.1.0 | |
7019163efad4ad0a5cb94d28 | train | ui_design | huggingface | https://huggingface.co/datasets/HuggingFaceTB/python-edu-annotations | HuggingFaceTB/python-edu-annotations | developer_tool | ruby | computer_vision | Design a production-quality UI for a developer_tool focused on computer_vision. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "HuggingFaceTB/python-edu-annotations", "source_url": "https://huggingface.co/datasets/Hugging... | Define layout, typography, spacing, hierarchy, components, states, responsive behavior, and accessibility. | web-research-coding-5m-1.1.0 | |
55903eaec840e23c73fd6549 | train | risk_analysis | web_docs | https://git-scm.com/doc | Git Documentation | saas | java | web_accessibility | Perform a deep multi-layer analysis of web_accessibility for a saas using java. 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 web_accessibility. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around web_accessibility. Use 'Git Documentation' as a source anchor and identify relevant APIs, dependenc... | web-research-coding-5m-1.1.0 | |
46a2ec5a75c46c77b11eb23d | train | search_query_rewrite | pypi | https://pypi.org/project/scrapy/ | scrapy | ecommerce | c | rest_api | Rewrite and improve a vague search query about rest_api 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": "scrapy", "source_url": "https://pypi.org/project/scrapy/", "source_type": "package", "topic":... | === ORIGINAL (VAGUE) ===
how to do rest_api
=== REWRITTEN QUERIES ===
1. rest_api official documentation guide
2. rest_api production best practices 2025
3. rest_api common pitfalls and solutions
4. rest_api architecture patterns with examples
=== RATIONALE ===
Add intent (learn / implement / debug), specificity (ver... | web-research-coding-5m-1.1.0 | |
0c8847a6b44ad316728f6bcd | train | design_to_code | npm | https://www.npmjs.com/package/hono | hono | social_app | python | docker | Translate a social_app design into maintainable python code. | {"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":... | 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 |
98574c9e519855a701a0a116 | train | api_developer_experience | huggingface | https://huggingface.co/datasets/arolstar52/ocr-synthetic-multilingual-v1-tokenized-en | arolstar52/ocr-synthetic-multilingual-v1-tokenized-en | admin_panel | javascript | web_accessibility | Perform a deep developer-experience analysis for a javascript project involving web_accessibility. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "arolstar52/ocr-synthetic-multilingual-v1-tokenized-en", "source_url": "https://huggingface.co... | === 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 | |
202b9c99020f9989e4427271 | train | design_components | stackexchange | https://stackoverflow.com/questions/21247278/about-d-ts-in-typescript | About "*.d.ts" in TypeScript | admin_panel | cpp | mongodb | Create a component architecture for a admin_panel. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "About "*.d.ts" in TypeScript", "source_url": "https://stackoverflow.com/questions/2... | Define primitive components, composite components, variants, states, composition rules, and accessibility contracts. | web-research-coding-5m-1.1.0 | |
9dec3789f0de80713c46f258 | train | documentation_page | stackexchange | https://stackoverflow.com/questions/4810841/pretty-print-json-using-javascript | pretty-print JSON using JavaScript | developer_tool | dart | algorithms | Design a developer documentation page for algorithms. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "pretty-print JSON using JavaScript", "source_url": "https://stackoverflow.com/questions/48108... | Include navigation, overview, prerequisites, installation, examples, API reference, troubleshooting, and search. | web-research-coding-5m-1.1.0 | |
6b681b8ba936d8829bb8a0f4 | train | cli_experience | github | https://github.com/enaqx/awesome-react | enaqx/awesome-react | social_app | typescript | mongodb | Perform a deep developer-experience analysis for a typescript project involving mongodb. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "enaqx/awesome-react", "source_url": "https://github.com/enaqx/awesome-react", "source_type": ... | === 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 | |
5a3c10715ab4b08f4cb4876f | train | refactoring_scalability | stackexchange | https://stackoverflow.com/questions/4775722/how-can-i-check-if-an-object-is-an-array | How can I check if an object is an array? | portfolio | sql | software_architecture | Refactor a sql system related to software_architecture. Focus on refactoring scalability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How can I check if an object is an array?", "source_url": "https://stackoverflow.com/question... | === 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 | |
0946ca890a00922b3f37dcec | train | upgrade_experience | huggingface | https://huggingface.co/datasets/hsultanbey/javascript | hsultanbey/javascript | documentation | cpp | mongodb | Perform a deep developer-experience analysis for a cpp project involving mongodb. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "hsultanbey/javascript", "source_url": "https://huggingface.co/datasets/hsultanbey/javascript"... | === 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 | |
806e087757df4e300217ad31 | train | accessibility_analysis | codeberg | https://codeberg.org/CryptoJones/120xSocrates | CryptoJones/120xSocrates | admin_panel | sql | database | Perform a deep multi-layer analysis of database for a admin_panel 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": "CryptoJones/120xSocrates", "source_url": "https://codeberg.org/CryptoJones/120xSocrates", "so... | === 1. PROBLEM ===
Define the exact problem involving database. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around database. Use 'CryptoJones/120xSocrates' as a source anchor and identify relevant APIs, dependencies, versio... | web-research-coding-5m-1.1.0 | |
1ff9cb7daf5b1d6b0ad95340 | train | error_message_design | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API | Fetch API | documentation | typescript | nextjs | Perform a deep developer-experience analysis for a typescript project involving nextjs. | {"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... | === 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 | |
d1b24106a1c429da0b55716d | train | repository_architecture | huggingface | https://huggingface.co/datasets/jamesdborin/Nemotron-SFT-Competitive-Programming-v2-prompt-only | jamesdborin/Nemotron-SFT-Competitive-Programming-v2-prompt-only | education | dart | typescript | Perform a deep multi-layer analysis of typescript for a education 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": "jamesdborin/Nemotron-SFT-Competitive-Programming-v2-prompt-only", "source_url": "https://hugg... | === 1. PROBLEM ===
Define the exact problem involving typescript. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around typescript. Use 'jamesdborin/Nemotron-SFT-Competitive-Programming-v2-prompt-only' as a source anchor and i... | web-research-coding-5m-1.1.0 | |
1d3623712251bf14879ebd49 | train | architecture_analysis | codeberg | https://codeberg.org/quidome/100-exercises-to-learn-rust | quidome/100-exercises-to-learn-rust | community | ruby | rest_api | Perform a deep multi-layer analysis of rest_api for a community 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": "quidome/100-exercises-to-learn-rust", "source_url": "https://codeberg.org/quidome/100-exercis... | === 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 'quidome/100-exercises-to-learn-rust' as a source anchor and identify relevant APIs, dependenc... | web-research-coding-5m-1.1.0 | |
b6f2fbf27b74fb3e23cffc29 | train | developer_experience | stackexchange | https://stackoverflow.com/questions/30626030/can-you-force-a-react-component-to-rerender-without-calling-setstate | Can you force a React component to rerender without calling setState? | ecommerce | typescript | javascript | Perform a deep developer-experience analysis for a typescript project involving javascript. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Can you force a React component to rerender without calling setState?", "source_url": "https:... | === 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 | |
e771a9ba4807672eb6cda0af | train | search_intent_classification | mdn | https://developer.mozilla.org/en-US/docs/Web/HTML | HTML | admin_panel | typescript | 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": "HTML", "source_url": "https://developer.mozilla.org/en-US/docs/Web/HTML", "source_type": "doc... | === 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 | |
f7f44e256ccf1ed7bb67020f | train | source_selection | github | https://github.com/expo/expo | expo/expo | community | kotlin | linux | Select the most reliable sources to research linux. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "expo/expo", "source_url": "https://github.com/expo/expo", "source_type": "repository", "topic... | === 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 | |
38d1458e11c924362e893ec9 | train | documentation_lookup | web_docs | https://nodejs.org/docs/latest/api/ | Node.js Documentation | landing_page | html | css | Find and summarize the relevant documentation for css. | {"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": "... | === RELEVANT DOCS ===
- Node.js Documentation
https://nodejs.org/docs/latest/api/
- 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 relevan... | web-research-coding-5m-1.1.0 | |
871bcb1cca6073f0d7e576a9 | train | architecture_analysis | pypi | https://pypi.org/project/httpx/ | httpx | analytics | kotlin | data_structures | Perform a deep multi-layer analysis of data_structures 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": "httpx", "source_url": "https://pypi.org/project/httpx/", "source_type": "package", "topic": "... | === 1. PROBLEM ===
Define the exact problem involving data_structures. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around data_structures. Use 'httpx' as a source anchor and identify relevant APIs, dependencies, versions, s... | web-research-coding-5m-1.1.0 | |
84eaa08e65bb84952a51fc8f | train | security_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/HTTP | HTTP | documentation | swift | software_architecture | Perform a deep multi-layer analysis of software_architecture for a documentation 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": "HTTP", "source_url": "https://developer.mozilla.org/en-US/docs/Web/HTTP", "source_type": "doc... | === 1. PROBLEM ===
Define the exact problem involving software_architecture. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around software_architecture. Use 'HTTP' as a source anchor and identify relevant APIs, dependencies, ... | web-research-coding-5m-1.1.0 | |
4d86eb61bf154f5e56ff5fb3 | train | design_to_code | mdn | https://developer.mozilla.org/en-US/docs/Web/HTML | HTML | blog | cpp | deep_learning | Translate a blog design into maintainable cpp code. | {"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... | Map design tokens to code, identify reusable components, preserve responsive behavior, implement accessible states, and avoid unnecessary one-off styling. | web-research-coding-5m-1.1.0 | |
19b3955d958c4f38cdceaeae | train | build_experience | npm | https://www.npmjs.com/package/vue | vue | documentation | c | sql | Perform a deep developer-experience analysis for a c project involving sql. | {"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": "... | === 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 | |
ff44ecfd133247ab7cb7d5c9 | train | repository_dependency_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model | DOM | ecommerce | java | machine_learning | Perform a deep multi-layer analysis of machine_learning for a ecommerce using java. 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": "DOM", "source_url": "https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model",... | === 1. PROBLEM ===
Define the exact problem involving machine_learning. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around machine_learning. Use 'DOM' as a source anchor and identify relevant APIs, dependencies, versions, s... | web-research-coding-5m-1.1.0 | |
90afdc88680995b2e30c4319 | train | fact_verification | stackexchange | https://stackoverflow.com/questions/3294889/iterating-over-a-dictionary-using-a-for-loop-getting-keys | Iterating over a dictionary using a 'for' loop, getting keys | developer_tool | shell | machine_learning | Verify a technical claim about machine_learning. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Iterating over a dictionary using a 'for' loop, getting keys", "source_url": "https:/... | === CLAIM ===
A common claim about machine_learning.
=== 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 / cont... | web-research-coding-5m-1.1.0 | |
c51cd24f7ac17b48d80cc11a | train | html_generation | stackexchange | https://stackoverflow.com/questions/4752626/epoch-vs-iteration-when-training-neural-networks | Epoch vs Iteration when training neural networks | education | shell | serverless | Create semantic HTML for a education about serverless. | {"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... | 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 |
6cc9ebeb0e4936ecf107bf89 | train | html_generation | gitlab | https://gitlab.com/snowball-dev-group/snowball-bot | snowball-dev-group/snowball-bot | social_app | dart | data_engineering | Create semantic HTML for a social_app about data_engineering. | {"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... | 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 |
dc4264a18e990ceb9cc165fa | train | repository_architecture | web_docs | https://docs.docker.com/ | Docker Documentation | community | ruby | authorization | Perform a deep multi-layer analysis of authorization for a community 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": "Docker Documentation", "source_url": "https://docs.docker.com/", "source_type": "documentatio... | === 1. PROBLEM ===
Define the exact problem involving authorization. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around authorization. Use 'Docker Documentation' as a source anchor and identify relevant APIs, dependencies, ... | web-research-coding-5m-1.1.0 | |
fc8e159c91e6cd865afe03a4 | train | testing_experience | web_docs | https://docs.docker.com/ | Docker Documentation | portfolio | c | redis | Perform a deep developer-experience analysis for a c project involving redis. | {"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. 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 | |
cc57ddff3d0b0ecba37ce68a | train | refactoring_readability | pypi | https://pypi.org/project/typer/ | typer | documentation | php | open_source | Refactor a php system related to open_source. Focus on refactoring readability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "typer", "source_url": "https://pypi.org/project/typer/", "source_type": "package", "topic": "... | === 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 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.