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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
fcd93576a02c850f74a823cf | train | evidence_extraction | mdn | https://developer.mozilla.org/en-US/docs/Web/API | Web APIs | developer_tool | css | nlp | Extract verifiable evidence about nlp from the given source. | {"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": "... | === SOURCE ===
Web APIs
https://developer.mozilla.org/en-US/docs/Web/API
=== EVIDENCE ITEMS ===
1. Explicit claims made by the source
2. Code examples or API signatures
3. Version / compatibility statements
4. Performance or security notes
=== QUALITY CHECK ===
- Is the claim specific and testable?
- Is the version a... | web-research-coding-5m-1.1.0 | |
a64e7d3eb07507cadb5ad310 | train | multi_hop_research | stackexchange | https://stackoverflow.com/questions/359494/which-equals-operator-vs-should-be-used-in-javascript-comparisons | Which equals operator (== vs ===) should be used in JavaScript comparisons? | saas | java | redis | Perform multi-hop research about redis: 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": "Which equals operator (== vs ===) should be used in JavaScript comparisons?", "source_url": "... | === HOP 1 ===
Start at: Which equals operator (== vs ===) should be used in JavaScript comparisons?
https://stackoverflow.com/questions/359494/which-equals-operator-vs-should-be-used-in-javascript-comparisons
Extract core claims and references.
=== HOP 2 ===
Follow references to official docs, RFCs, or specs.
Extract ... | web-research-coding-5m-1.1.0 | |
518d200630127afaed11b900 | train | cli_experience | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model | DOM | community | go | distributed_systems | Perform a deep developer-experience analysis for a go project involving distributed_systems. | {"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. 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 | |
c89e27912e1a525944aed070 | train | algorithm_design | huggingface | https://huggingface.co/datasets/HuggingFaceH4/testing_codealpaca_small | HuggingFaceH4/testing_codealpaca_small | finance | javascript | authentication | Design a javascript algorithm for a authentication problem. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "HuggingFaceH4/testing_codealpaca_small", "source_url": "https://huggingface.co/datasets/Huggi... | State assumptions, algorithm, complexity, edge cases, correctness reasoning, and testing strategy. | web-research-coding-5m-1.1.0 | |
27390b2010ed5f70c5986a69 | train | architecture_analysis | pypi | https://pypi.org/project/torch/ | torch | admin_panel | javascript | backend | Perform a deep multi-layer analysis of backend for a admin_panel 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": "torch", "source_url": "https://pypi.org/project/torch/", "source_type": "package", "topic": "... | === 1. PROBLEM ===
Define the exact problem involving backend. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around backend. Use 'torch' as a source anchor and identify relevant APIs, dependencies, versions, standards, and te... | web-research-coding-5m-1.1.0 | |
c797498f2d791e592c3ffca8 | train | tradeoff_analysis | npm | https://www.npmjs.com/package/vitest | vitest | productivity | typescript | nlp | Perform a deep multi-layer analysis of nlp for a productivity using typescript. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "vitest", "source_url": "https://www.npmjs.com/package/vitest", "source_type": "package", "top... | === 1. PROBLEM ===
Define the exact problem involving nlp. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around nlp. Use 'vitest' as a source anchor and identify relevant APIs, dependencies, versions, standards, and technical... | web-research-coding-5m-1.1.0 | |
9bf5f784d6e9890fd9c1babb | train | nextjs_generation | gitlab | https://gitlab.com/srabon444/google-calendar-clone-typescript | srabon444/google-calendar-clone-typescript | marketplace | ruby | redis | 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": "srabon444/google-calendar-clone-typescript", "source_url": "https://gitlab.com/srabon444/goog... | 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 |
f9e8a7d46bb9f35b752b1d75 | train | ui_design | npm | https://www.npmjs.com/package/vitest | vitest | developer_tool | rust | open_source | Design a production-quality UI for a developer_tool focused on open_source. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "vitest", "source_url": "https://www.npmjs.com/package/vitest", "source_type": "package", "top... | Define layout, typography, spacing, hierarchy, components, states, responsive behavior, and accessibility. | web-research-coding-5m-1.1.0 | |
099bed3cb52b7a42f179fb7d | train | refactoring_legacy_code | huggingface | https://huggingface.co/datasets/HuggingFaceH4/Multilingual-Thinking | HuggingFaceH4/Multilingual-Thinking | education | java | nlp | Refactor a java system related to nlp. Focus on refactoring legacy code. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "HuggingFaceH4/Multilingual-Thinking", "source_url": "https://huggingface.co/datasets/HuggingF... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Characterize existing behavior first and incrementally replace risky legacy structures.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implication... | web-research-coding-5m-1.1.0 | |
4dc31720a608dae4b88faa6a | train | code_review | npm | https://www.npmjs.com/package/react | react | developer_tool | kotlin | user_experience | Perform a production code review of kotlin code related to user_experience. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "react", "source_url": "https://www.npmjs.com/package/react", "source_type": "package", "topic... | Review correctness, security, performance, readability, architecture, testing, maintainability, and error handling. | web-research-coding-5m-1.1.0 | |
c2c364accdbdee529c06ddf2 | train | web_search_query | pypi | https://pypi.org/project/numpy/ | numpy | dashboard | java | nextjs | Write an effective web search query to research the topic: nextjs. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "numpy", "source_url": "https://pypi.org/project/numpy/", "source_type": "package", "topic": "... | === QUERY ===
nextjs best practices documentation tutorial
=== INTENT ===
Find authoritative documentation, tutorials, and real-world examples related to the topic.
=== KEYWORDS ===
- nextjs
- documentation
- best practices
- examples
- reference
=== SOURCE PREFERENCE ===
Prefer official documentation, well-maintain... | web-research-coding-5m-1.1.0 | |
c2cd62d653de61e5397f6a23 | train | information_architecture | web_docs | https://go.dev/doc/ | Go Documentation | finance | ruby | cloud | Design the information architecture for cloud. | {"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... | Organize content into logical categories, navigation levels, search, filtering, and discoverable paths. | web-research-coding-5m-1.1.0 | |
9cf40c0a302fd72498041732 | train | accessibility_analysis | web_docs | https://nodejs.org/docs/latest/api/ | Node.js Documentation | finance | ruby | kubernetes | Perform a deep multi-layer analysis of kubernetes for a finance 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": "Node.js Documentation", "source_url": "https://nodejs.org/docs/latest/api/", "source_type": "... | === 1. PROBLEM ===
Define the exact problem involving kubernetes. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around kubernetes. Use 'Node.js Documentation' as a source anchor and identify relevant APIs, dependencies, versi... | web-research-coding-5m-1.1.0 | |
53dd08c9101c24269b923515 | train | web_search_query | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model | DOM | finance | rust | redis | Write an effective web search query to research the topic: redis. | {"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",... | === QUERY ===
redis best practices documentation tutorial
=== INTENT ===
Find authoritative documentation, tutorials, and real-world examples related to the topic.
=== KEYWORDS ===
- redis
- documentation
- best practices
- examples
- reference
=== SOURCE PREFERENCE ===
Prefer official documentation, well-maintained... | web-research-coding-5m-1.1.0 | |
2fab69b1cb94e69088f041ea | train | ux_analysis | huggingface | https://huggingface.co/datasets/McKlay/documentation-images | McKlay/documentation-images | blog | html | react | Perform a deep multi-layer analysis of react for a blog 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": "McKlay/documentation-images", "source_url": "https://huggingface.co/datasets/McKlay/documenta... | === 1. PROBLEM ===
Define the exact problem involving react. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around react. Use 'McKlay/documentation-images' as a source anchor and identify relevant APIs, dependencies, versions,... | web-research-coding-5m-1.1.0 | |
88414a2c02593403383afc94 | train | design_system | github | https://github.com/encode/django-rest-framework | encode/django-rest-framework | documentation | html | authorization | Create a scalable design system for a documentation. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "encode/django-rest-framework", "source_url": "https://github.com/encode/django-rest-framework... | Define tokens, typography, spacing, components, variants, states, responsive rules, accessibility, and documentation. | web-research-coding-5m-1.1.0 | |
6aa6f66cba4d18cff335607d | train | repository_comparison | stackexchange | https://stackoverflow.com/questions/42480111/how-do-i-print-the-model-summary-in-pytorch | How do I print the model summary in PyTorch? | documentation | c | frontend | Perform a deep multi-layer analysis of frontend for a documentation using c. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How do I print the model summary in PyTorch?", "source_url": "https://stackoverflow.com/quest... | === 1. PROBLEM ===
Define the exact problem involving frontend. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around frontend. Use 'How do I print the model summary in PyTorch?' as a source anchor and identify relevant APIs, ... | web-research-coding-5m-1.1.0 | |
c957b4c7d198e361b0f995ca | train | build_experience | mdn | https://developer.mozilla.org/en-US/docs/Web/Accessibility | Accessibility | documentation | go | distributed_systems | Perform a deep developer-experience analysis for a go project involving distributed_systems. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Accessibility", "source_url": "https://developer.mozilla.org/en-US/docs/Web/Accessibility", "... | === 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 | |
14e049431bd6367baddb750a | train | repository_architecture | huggingface | https://huggingface.co/datasets/codefuse-ai/CodeExercise-Python-27k | codefuse-ai/CodeExercise-Python-27k | developer_tool | scala | microservices | Perform a deep multi-layer analysis of microservices for a developer_tool 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": "codefuse-ai/CodeExercise-Python-27k", "source_url": "https://huggingface.co/datasets/codefuse... | === 1. PROBLEM ===
Define the exact problem involving microservices. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around microservices. Use 'codefuse-ai/CodeExercise-Python-27k' as a source anchor and identify relevant APIs,... | web-research-coding-5m-1.1.0 | |
12dc65f53eebb495a3ae4cf2 | train | refactoring_readability | huggingface | https://huggingface.co/datasets/embedl/documentation-images | embedl/documentation-images | blog | dart | software_architecture | Refactor a dart system related to software_architecture. Focus on refactoring readability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "embedl/documentation-images", "source_url": "https://huggingface.co/datasets/embedl/documenta... | === 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 | |
a2b0eb8fbaf3547c7d7f0979 | train | dashboard | stackexchange | https://stackoverflow.com/questions/613183/how-do-i-sort-a-dictionary-by-value | How do I sort a dictionary by value? | ecommerce | go | web_accessibility | Design a production dashboard for web_accessibility. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How do I sort a dictionary by value?", "source_url": "https://stackoverflow.com/questions/613... | Include navigation, KPIs, tables/charts, filters, loading states, empty states, errors, and responsive behavior. | web-research-coding-5m-1.1.0 | |
d7b7d4de91a5cb569e4dbc52 | train | refactoring_scalability | huggingface | https://huggingface.co/datasets/livecodebench/code_generation | livecodebench/code_generation | education | html | javascript | Refactor a html system related to javascript. Focus on refactoring scalability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "livecodebench/code_generation", "source_url": "https://huggingface.co/datasets/livecodebench/... | === 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 | |
7f6d8b046681b2ac566b051f | train | data_structure_design | github | https://github.com/expressjs/express | expressjs/express | portfolio | cpp | database | Design a data structure in cpp for database. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "expressjs/express", "source_url": "https://github.com/expressjs/express", "source_type": "rep... | Explain representation, operations, complexity, memory trade-offs, and workload suitability. | web-research-coding-5m-1.1.0 | |
2cb84629bb93c48971663c1c | train | accessibility_fix | huggingface | https://huggingface.co/datasets/nvidia/Nemotron-Competitive-Programming-v1 | nvidia/Nemotron-Competitive-Programming-v1 | analytics | sql | web_performance | Create an accessibility remediation plan for a analytics. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "nvidia/Nemotron-Competitive-Programming-v1", "source_url": "https://huggingface.co/datasets/n... | Check semantic HTML, keyboard navigation, focus management, accessible names, labels, errors, contrast, and screen-reader behavior. | web-research-coding-5m-1.1.0 | |
c923f9d306a06e8a8e0061c0 | train | visual_hierarchy | mdn | https://developer.mozilla.org/en-US/docs/Web/JavaScript | JavaScript | search_interface | cpp | docker | Improve visual hierarchy in a search_interface. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "JavaScript", "source_url": "https://developer.mozilla.org/en-US/docs/Web/JavaScript", "source... | Use heading structure, typography, spacing, grouping, alignment, contrast, and consistent affordances. | web-research-coding-5m-1.1.0 | |
4f168b312e3ba6dacabb1571 | train | api_design | web_docs | https://docs.docker.com/ | Docker Documentation | saas | kotlin | sql | Design a production API for a sql application. | {"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... | Specify resources, endpoints, schemas, validation, authentication, authorization, errors, pagination, versioning, idempotency, and tests. | web-research-coding-5m-1.1.0 | |
ad6978e0e14f4621431a683d | train | product_analysis | pypi | https://pypi.org/project/httpx/ | httpx | community | cpp | serverless | Perform a deep multi-layer analysis of serverless for a community 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 serverless. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around serverless. Use 'httpx' as a source anchor and identify relevant APIs, dependencies, versions, standards, ... | web-research-coding-5m-1.1.0 | |
c319c51b0c16953feb523709 | train | repository_documentation | pypi | https://pypi.org/project/requests/ | requests | landing_page | rust | caching | Perform a deep multi-layer analysis of caching for a landing_page using rust. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "requests", "source_url": "https://pypi.org/project/requests/", "source_type": "package", "top... | === 1. PROBLEM ===
Define the exact problem involving caching. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around caching. Use 'requests' as a source anchor and identify relevant APIs, dependencies, versions, standards, and... | web-research-coding-5m-1.1.0 | |
d54cbc586a6cfcd444e4e0db | train | form_ui | web_docs | https://nodejs.org/docs/latest/api/ | Node.js Documentation | admin_panel | dart | graphql | Design an accessible form for graphql. | {"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": "... | Use labels, validation, clear errors, keyboard navigation, appropriate autocomplete, and accessible status messaging. | web-research-coding-5m-1.1.0 | |
bd3cbc862bcc117f68b50f34 | train | refactoring_dependency | mdn | https://developer.mozilla.org/en-US/docs/Web/Performance | Performance | education | kotlin | ci_cd | Refactor a kotlin system related to ci_cd. Focus on refactoring dependency. | {"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... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Audit dependencies and isolate external integrations.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify developer-experienc... | web-research-coding-5m-1.1.0 | |
f1c05fde982a1b4f54c4918c | train | repository_documentation | gitlab | https://gitlab.com/NotRyan_/level-ts | NotRyan_/level-ts | portfolio | swift | mongodb | Perform a deep multi-layer analysis of mongodb for a portfolio 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": "NotRyan_/level-ts", "source_url": "https://gitlab.com/NotRyan_/level-ts", "source_type": "rep... | === 1. PROBLEM ===
Define the exact problem involving mongodb. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around mongodb. Use 'NotRyan_/level-ts' as a source anchor and identify relevant APIs, dependencies, versions, stand... | web-research-coding-5m-1.1.0 | |
d773c3833d8fa1a3970a276a | train | dependency_management_experience | web_docs | https://docs.djangoproject.com/ | Django Documentation | productivity | python | documentation | Perform a deep developer-experience analysis for a python project involving documentation. | {"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... | === 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 |
9efc11e99e20e8ab7743180f | train | api_design | stackexchange | https://stackoverflow.com/questions/3207219/how-do-i-list-all-files-of-a-directory | How do I list all files of a directory? | portfolio | go | open_source | Design a production API for a open_source application. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How do I list all files of a directory?", "source_url": "https://stackoverflow.com/questions/... | Specify resources, endpoints, schemas, validation, authentication, authorization, errors, pagination, versioning, idempotency, and tests. | web-research-coding-5m-1.1.0 | |
f5b33c0bd0284f9fa788878e | train | refactoring_observability | mdn | https://developer.mozilla.org/en-US/docs/Web/CSS | CSS | admin_panel | swift | data_structures | Refactor a swift system related to data_structures. Focus on refactoring observability. | {"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 logging, metrics, tracing, diagnostics, and failure visibility.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify d... | web-research-coding-5m-1.1.0 | |
8da84287e7943be7a50413a5 | train | build_experience | web_docs | https://git-scm.com/doc | Git Documentation | marketplace | cpp | cloud | Perform a deep developer-experience analysis for a cpp project involving cloud. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Git Documentation", "source_url": "https://git-scm.com/doc", "source_type": "documentation", ... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
1edbde8690f3dd87d369791d | train | evidence_extraction | stackexchange | https://stackoverflow.com/questions/6912584/how-to-get-get-query-string-variables-in-express-js-on-node-js | How to get GET (query string) variables in Express.js on Node.js? | ecommerce | html | developer_experience | Extract verifiable evidence about developer_experience from the given source. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How to get GET (query string) variables in Express.js on Node.js?", "source_url": "https://st... | === SOURCE ===
How to get GET (query string) variables in Express.js on Node.js?
https://stackoverflow.com/questions/6912584/how-to-get-get-query-string-variables-in-express-js-on-node-js
=== EVIDENCE ITEMS ===
1. Explicit claims made by the source
2. Code examples or API signatures
3. Version / compatibility statemen... | web-research-coding-5m-1.1.0 | |
aec76f011641a5b255aa125e | train | performance_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/API | Web APIs | social_app | sql | api_design | Perform a deep multi-layer analysis of api_design for a social_app 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": "Web APIs", "source_url": "https://developer.mozilla.org/en-US/docs/Web/API", "source_type": "... | === 1. PROBLEM ===
Define the exact problem involving api_design. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around api_design. Use 'Web APIs' as a source anchor and identify relevant APIs, dependencies, versions, standard... | web-research-coding-5m-1.1.0 | |
7417b4e46eaf19b5d4583538 | train | responsive_design | stackexchange | https://stackoverflow.com/questions/520650/make-an-existing-git-branch-track-a-remote-branch | Make an existing Git branch track a remote branch? | productivity | rust | typescript | Create a responsive design strategy for a productivity. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Make an existing Git branch track a remote branch?", "source_url": "https://stackoverflow.com... | Define mobile, tablet, and desktop behavior, layout transitions, navigation, content priority, typography, and interaction targets. | web-research-coding-5m-1.1.0 | |
0fa13322db10b761d6b003cc | train | interaction_design | npm | https://www.npmjs.com/package/vitest | vitest | developer_tool | python | software_architecture | Design interaction states for a developer_tool. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "vitest", "source_url": "https://www.npmjs.com/package/vitest", "source_type": "package", "top... | Specify default, hover, focus, active, disabled, loading, success, error, and empty states. | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
09a666630252859a529abbde | train | ux_design | huggingface | https://huggingface.co/datasets/BAAI/IndustryCorpus2_artificial_intelligence_machine_learning | BAAI/IndustryCorpus2_artificial_intelligence_machine_learning | productivity | ruby | docker | Design the complete UX flow of a productivity for docker. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "BAAI/IndustryCorpus2_artificial_intelligence_machine_learning", "source_url": "https://huggin... | Map user goals, entry points, navigation, primary actions, feedback, loading states, empty states, errors, recovery paths, and completion. | web-research-coding-5m-1.1.0 | |
d695cbe470b6255529166539 | train | dashboard | mdn | https://developer.mozilla.org/en-US/docs/Web/Accessibility | Accessibility | portfolio | sql | serverless | Design a production dashboard for serverless. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Accessibility", "source_url": "https://developer.mozilla.org/en-US/docs/Web/Accessibility", "... | Include navigation, KPIs, tables/charts, filters, loading states, empty states, errors, and responsive behavior. | web-research-coding-5m-1.1.0 | |
085d09b519c791b0632fb8ec | train | ux_design | npm | https://www.npmjs.com/package/typescript | typescript | social_app | scala | microservices | Design the complete UX flow of a social_app for microservices. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "typescript", "source_url": "https://www.npmjs.com/package/typescript", "source_type": "packag... | Map user goals, entry points, navigation, primary actions, feedback, loading states, empty states, errors, recovery paths, and completion. | web-research-coding-5m-1.1.0 | |
d3994b8694d3ccb7e61512ff | train | research_plan | huggingface | https://huggingface.co/datasets/codeparrot/apps | codeparrot/apps | blog | javascript | testing | Build a structured research plan to deeply understand testing. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "codeparrot/apps", "source_url": "https://huggingface.co/datasets/codeparrot/apps", "source_ty... | === GOAL ===
Produce a reliable, current, and actionable understanding of testing.
=== 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 wi... | web-research-coding-5m-1.1.0 | |
01ad2b419aee0c56279ebe3b | train | algorithm_design | gitlab | https://gitlab.com/bvobart/python-ml-analysis | bvobart/python-ml-analysis | social_app | rust | microservices | Design a rust algorithm for a microservices problem. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "bvobart/python-ml-analysis", "source_url": "https://gitlab.com/bvobart/python-ml-analysis", "... | State assumptions, algorithm, complexity, edge cases, correctness reasoning, and testing strategy. | web-research-coding-5m-1.1.0 | |
d361181ad27775aaa7064eff | train | search_intent_classification | stackexchange | https://stackoverflow.com/questions/195951/how-can-i-change-an-elements-class-with-javascript | How can I change an element's class with JavaScript? | dashboard | css | ci_cd | Classify the search intent for a query about ci_cd. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How can I change an element's class with JavaScript?", "source_url": "https://stackoverfl... | === 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 ===
"ci_cd vs alternatives"
=== CLASSIFICATION ===
Comparative / informational.
==... | web-research-coding-5m-1.1.0 | |
fbf02d0ebbe282a739543feb | train | design_components | stackexchange | https://stackoverflow.com/questions/12694530/what-is-typescript-and-why-should-i-use-it-instead-of-javascript | What is TypeScript and why should I use it instead of JavaScript? | analytics | typescript | observability | Create a component architecture for a analytics. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "What is TypeScript and why should I use it instead of JavaScript?", "source_url": "https://st... | Define primitive components, composite components, variants, states, composition rules, and accessibility contracts. | web-research-coding-5m-1.1.0 | |
f825c59f85cafa72cf209546 | train | seo_fix | stackexchange | https://stackoverflow.com/questions/4752626/epoch-vs-iteration-when-training-neural-networks | Epoch vs Iteration when training neural networks | productivity | swift | algorithms | Create an SEO improvement plan for a productivity about algorithms. | {"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... | Cover titles, descriptions, headings, canonical URLs, structured data, internal links, crawlability, and performance. | web-research-coding-5m-1.1.0 | |
7a2b2317d02845f216e5d37d | train | refactoring_readability | stackexchange | https://stackoverflow.com/questions/5009324/node-js-nginx-what-now | Node.js + Nginx - What now? | finance | dart | user_experience | Refactor a dart system related to user_experience. Focus on refactoring readability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Node.js + Nginx - What now?", "source_url": "https://stackoverflow.com/questions/5009324/node... | === 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 | |
c434be799a35a2c95243b7e2 | train | refactoring_readability | gitlab | https://gitlab.com/mlreef/mlreef | mlreef/mlreef | blog | sql | user_experience | Refactor a sql system related to user_experience. Focus on refactoring readability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "mlreef/mlreef", "source_url": "https://gitlab.com/mlreef/mlreef", "source_type": "repository"... | === 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 | |
982e69a90e06d47dfdeecad1 | train | local_development_experience | mdn | https://developer.mozilla.org/en-US/docs/Web/CSS | CSS | ecommerce | java | react | Perform a deep developer-experience analysis for a java project involving react. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "CSS", "source_url": "https://developer.mozilla.org/en-US/docs/Web/CSS", "source_type": "docum... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
87d38fa80f4653f5be308984 | train | refactoring_observability | huggingface | https://huggingface.co/datasets/CM/codexglue_code2text_javascript | CM/codexglue_code2text_javascript | developer_tool | cpp | react | Refactor a cpp system related to react. Focus on refactoring observability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "CM/codexglue_code2text_javascript", "source_url": "https://huggingface.co/datasets/CM/codexgl... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Improve logging, metrics, tracing, diagnostics, and failure visibility.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify d... | web-research-coding-5m-1.1.0 | |
039d18f7b5c8605ad0368587 | train | repository_issue_reasoning | codeberg | https://codeberg.org/plaublin/100-exercises-to-learn-rust | plaublin/100-exercises-to-learn-rust | education | c | user_experience | Perform a deep multi-layer analysis of user_experience for a education using c. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "plaublin/100-exercises-to-learn-rust", "source_url": "https://codeberg.org/plaublin/100-exerc... | === 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 'plaublin/100-exercises-to-learn-rust' as a source anchor and identify relevant ... | web-research-coding-5m-1.1.0 | |
0c0c81574496e23f86c6471c | train | design_components | stackexchange | https://stackoverflow.com/questions/35537229/how-can-i-update-the-parents-state-in-react | How can I update the parent's state in React? | dashboard | java | frontend | 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": "How can I update the parent's state in React?", "source_url": "https://stackoverflow.com/... | Define primitive components, composite components, variants, states, composition rules, and accessibility contracts. | web-research-coding-5m-1.1.0 | |
d64c3367a55c2baa0c671027 | train | upgrade_experience | huggingface | https://huggingface.co/datasets/Jackrong/Competitive-Programming-python-blend | Jackrong/Competitive-Programming-python-blend | finance | javascript | data_engineering | Perform a deep developer-experience analysis for a javascript project involving data_engineering. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Jackrong/Competitive-Programming-python-blend", "source_url": "https://huggingface.co/dataset... | === 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 | |
869f05baf924be79063ea9b8 | train | dashboard | github | https://github.com/leonardomso/33-js-concepts | leonardomso/33-js-concepts | ecommerce | sql | docker | Design a production dashboard for docker. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "leonardomso/33-js-concepts", "source_url": "https://github.com/leonardomso/33-js-concepts", "... | Include navigation, KPIs, tables/charts, filters, loading states, empty states, errors, and responsive behavior. | web-research-coding-5m-1.1.0 | |
5256d81c03f028638302b6d4 | train | search_intent_classification | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model | DOM | landing_page | css | design_system | Classify the search intent for a query about design_system. | {"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",... | === 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 ===
"design_system vs alternatives"
=== CLASSIFICATION ===
Comparative / informatio... | web-research-coding-5m-1.1.0 | |
aeb1a5dc71b9799b0aac990a | train | security_analysis | huggingface | https://huggingface.co/datasets/dougiefresh/systems_programming_code_conversations | dougiefresh/systems_programming_code_conversations | ecommerce | shell | mongodb | Perform a deep multi-layer analysis of mongodb for a ecommerce 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": "dougiefresh/systems_programming_code_conversations", "source_url": "https://huggingface.co/da... | === 1. PROBLEM ===
Define the exact problem involving mongodb. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around mongodb. Use 'dougiefresh/systems_programming_code_conversations' as a source anchor and identify relevant AP... | web-research-coding-5m-1.1.0 | |
e687c226a40baf8bd296c5ed | train | refactoring_architecture | npm | https://www.npmjs.com/package/tailwindcss | tailwindcss | education | java | devops | Refactor a java system related to devops. Focus on refactoring architecture. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "tailwindcss", "source_url": "https://www.npmjs.com/package/tailwindcss", "source_type": "pack... | === 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 | |
ac7dc57d43e146713f5e3672 | train | react_generation | mdn | https://developer.mozilla.org/en-US/docs/Web/HTML | HTML | developer_tool | dart | security | Design React components for a developer_tool. | {"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... | Separate reusable components, state, data fetching, loading/error states, accessibility, and testing. | export function Card({ title, children }) {
return (
<article className="card">
<h2>{title}</h2>
<div>{children}</div>
</article>
);
} | web-research-coding-5m-1.1.0 |
7434d1cefdf8687eef677ebb | train | documentation_lookup | huggingface | https://huggingface.co/datasets/nabin2004/Wikipedia_Articles_on_Machine_Learning_and_DS | nabin2004/Wikipedia_Articles_on_Machine_Learning_and_DS | marketplace | sql | algorithms | Find and summarize the relevant documentation for algorithms. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "nabin2004/Wikipedia_Articles_on_Machine_Learning_and_DS", "source_url": "https://huggingface.... | === RELEVANT DOCS ===
- nabin2004/Wikipedia_Articles_on_Machine_Learning_and_DS
https://huggingface.co/datasets/nabin2004/Wikipedia_Articles_on_Machine_Learning_and_DS
- Official project documentation
- API reference
=== KEY SECTIONS ===
- Getting started
- API reference
- Configuration
- Troubleshooting
=== SUMMAR... | web-research-coding-5m-1.1.0 | |
765e14902649f62b340d7735 | train | information_architecture | github | https://github.com/parcel-bundler/parcel | parcel-bundler/parcel | marketplace | swift | ci_cd | Design the information architecture for ci_cd. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "parcel-bundler/parcel", "source_url": "https://github.com/parcel-bundler/parcel", "source_typ... | Organize content into logical categories, navigation levels, search, filtering, and discoverable paths. | web-research-coding-5m-1.1.0 | |
33ff55e1baa7f6ae96e8b4cc | train | design_tokens | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API | Fetch API | saas | swift | react | Create design tokens for a saas. | {"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... | Define reusable tokens for typography, spacing, radii, sizing, elevation, interaction states, and responsive behavior. | web-research-coding-5m-1.1.0 | |
35132517cb8e7d4d11331b0f | train | refactoring_modularization | stackexchange | https://stackoverflow.com/questions/4906977/how-can-i-access-environment-variables-in-python | How can I access environment variables in Python? | admin_panel | dart | nextjs | Refactor a dart system related to nextjs. Focus on refactoring modularization. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How can I access environment variables in Python?", "source_url": "https://stackoverflow.com/... | === 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 | |
604ca1f35b5983cc2508f393 | train | search_query_rewrite | gitlab | https://gitlab.com/divested-mobile/mull-fenix | divested-mobile/mull-fenix | portfolio | rust | authentication | Rewrite and improve a vague search query about authentication 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": "divested-mobile/mull-fenix", "source_url": "https://gitlab.com/divested-mobile/mull-fenix", "... | === ORIGINAL (VAGUE) ===
how to do authentication
=== REWRITTEN QUERIES ===
1. authentication official documentation guide
2. authentication production best practices 2025
3. authentication common pitfalls and solutions
4. authentication architecture patterns with examples
=== RATIONALE ===
Add intent (learn / implem... | web-research-coding-5m-1.1.0 | |
ab3476d92756f714e8e7459c | train | performance_fix | huggingface | https://huggingface.co/datasets/fyaronskiy/cornstack_javascript_ru_en | fyaronskiy/cornstack_javascript_ru_en | social_app | java | sql | Create a web-performance optimization plan for a social_app. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "fyaronskiy/cornstack_javascript_ru_en", "source_url": "https://huggingface.co/datasets/fyaron... | Measure first, then optimize bundle size, images, network requests, rendering, caching, and critical resources. | web-research-coding-5m-1.1.0 | |
0c67b52155d49fb663c687ac | train | search_query_rewrite | mdn | https://developer.mozilla.org/en-US/docs/Web/JavaScript | JavaScript | developer_tool | dart | redis | Rewrite and improve a vague search query about redis 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": "JavaScript", "source_url": "https://developer.mozilla.org/en-US/docs/Web/JavaScript", "source... | === ORIGINAL (VAGUE) ===
how to do redis
=== REWRITTEN QUERIES ===
1. redis official documentation guide
2. redis production best practices 2025
3. redis common pitfalls and solutions
4. redis architecture patterns with examples
=== RATIONALE ===
Add intent (learn / implement / debug), specificity (version, framework... | web-research-coding-5m-1.1.0 | |
e37e3bce170426e1f65a1767 | train | javascript_generation | gitlab | https://gitlab.com/dslackw/colored | dslackw/colored | finance | java | javascript | Implement JavaScript interactions for a finance. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "dslackw/colored", "source_url": "https://gitlab.com/dslackw/colored", "source_type": "reposit... | 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 |
d11c08afe19e4106628c87a2 | train | evidence_chain_analysis | stackexchange | https://stackoverflow.com/questions/585945/how-to-align-content-of-a-div-to-the-bottom | How to align content of a div to the bottom | landing_page | shell | kubernetes | Perform a deep multi-layer analysis of kubernetes 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": "How to align content of a div to the bottom", "source_url": "https://stackoverflow.com/questi... | === 1. PROBLEM ===
Define the exact problem involving kubernetes. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around kubernetes. Use 'How to align content of a div to the bottom' as a source anchor and identify relevant API... | web-research-coding-5m-1.1.0 | |
0f26992f557ac0947bfa241b | train | upgrade_experience | web_docs | https://react.dev/ | React Documentation | portfolio | go | user_experience | Perform a deep developer-experience analysis for a go project involving user_experience. | {"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... | === 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 | |
9e1479ade6664d966b76672c | train | product_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/HTML | HTML | finance | go | backend | Perform a deep multi-layer analysis of backend for a finance using go. 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 backend. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around backend. Use 'HTML' as a source anchor and identify relevant APIs, dependencies, versions, standards, and tec... | web-research-coding-5m-1.1.0 | |
dda678889e482e827986754b | train | responsive_website | mdn | https://developer.mozilla.org/en-US/docs/Web/HTTP | HTTP | documentation | ruby | html | Design a complete responsive documentation for html. | {"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... | Cover mobile, tablet, and desktop layouts, semantic structure, responsive components, accessibility, performance, and UX. | web-research-coding-5m-1.1.0 | |
cc0b8d96fdcc992d8a075b8a | train | responsive_website | web_docs | https://kubernetes.io/docs/ | Kubernetes Documentation | portfolio | go | redis | Design a complete responsive portfolio for redis. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Kubernetes Documentation", "source_url": "https://kubernetes.io/docs/", "source_type": "docum... | Cover mobile, tablet, and desktop layouts, semantic structure, responsive components, accessibility, performance, and UX. | web-research-coding-5m-1.1.0 | |
b8f6aed52aed265210fd6322 | train | search_query_rewrite | npm | https://www.npmjs.com/package/rollup | rollup | saas | kotlin | data_structures | Rewrite and improve a vague search query about data_structures 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": "rollup", "source_url": "https://www.npmjs.com/package/rollup", "source_type": "package", "top... | === ORIGINAL (VAGUE) ===
how to do data_structures
=== REWRITTEN QUERIES ===
1. data_structures official documentation guide
2. data_structures production best practices 2025
3. data_structures common pitfalls and solutions
4. data_structures architecture patterns with examples
=== RATIONALE ===
Add intent (learn / i... | web-research-coding-5m-1.1.0 | |
db25d964abc033075185a76b | train | refactoring_security | web_docs | https://fastapi.tiangolo.com/ | FastAPI Documentation | blog | typescript | database | Refactor a typescript system related to database. Focus on refactoring security. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "FastAPI Documentation", "source_url": "https://fastapi.tiangolo.com/", "source_type": "docume... | === 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 | |
ccb74893a965eb7b8ad878cb | train | multi_layer_analysis | stackexchange | https://stackoverflow.com/questions/13066532/how-can-i-uninstall-npm-modules-in-node-js | How can I uninstall npm modules in Node.js? | documentation | rust | graphql | Perform a deep multi-layer analysis of graphql for a documentation using rust. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How can I uninstall npm modules in Node.js?", "source_url": "https://stackoverflow.com/questi... | === 1. PROBLEM ===
Define the exact problem involving graphql. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around graphql. Use 'How can I uninstall npm modules in Node.js?' as a source anchor and identify relevant APIs, dep... | web-research-coding-5m-1.1.0 | |
77831f2e0355ad173dec4046 | train | performance_analysis | npm | https://www.npmjs.com/package/jest | jest | saas | kotlin | css | Perform a deep multi-layer analysis of css for a saas 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": "jest", "source_url": "https://www.npmjs.com/package/jest", "source_type": "package", "topic":... | === 1. PROBLEM ===
Define the exact problem involving css. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around css. Use 'jest' as a source anchor and identify relevant APIs, dependencies, versions, standards, and technical c... | web-research-coding-5m-1.1.0 | |
01fb2609948140b25041b3f7 | train | search_query_rewrite | npm | https://www.npmjs.com/package/react | react | portfolio | sql | html | Rewrite and improve a vague search query about html 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": "react", "source_url": "https://www.npmjs.com/package/react", "source_type": "package", "topic... | === ORIGINAL (VAGUE) ===
how to do html
=== REWRITTEN QUERIES ===
1. html official documentation guide
2. html production best practices 2025
3. html common pitfalls and solutions
4. html architecture patterns with examples
=== RATIONALE ===
Add intent (learn / implement / debug), specificity (version, framework, env... | web-research-coding-5m-1.1.0 | |
dfb7d0e990af0161be13319e | train | tradeoff_analysis | web_docs | https://www.typescriptlang.org/docs/ | TypeScript Documentation | search_interface | ruby | typescript | Perform a deep multi-layer analysis of typescript for a search_interface 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": "TypeScript Documentation", "source_url": "https://www.typescriptlang.org/docs/", "source_type... | === 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 'TypeScript Documentation' as a source anchor and identify relevant APIs, dependencies, ve... | web-research-coding-5m-1.1.0 | |
e73b44d5928e7701f9b643c9 | train | ux_design | npm | https://www.npmjs.com/package/vue | vue | productivity | swift | python | Design the complete UX flow of a productivity for python. | {"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": "... | Map user goals, entry points, navigation, primary actions, feedback, loading states, empty states, errors, recovery paths, and completion. | web-research-coding-5m-1.1.0 | |
d8ae0f883c9a1b24f9f529aa | train | design_to_code | huggingface | https://huggingface.co/datasets/LiquidAI/nanobeir-multilingual-extended | LiquidAI/nanobeir-multilingual-extended | portfolio | swift | computer_vision | Translate a portfolio design into maintainable swift code. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "LiquidAI/nanobeir-multilingual-extended", "source_url": "https://huggingface.co/datasets/Liqu... | 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 | |
881ef624ef24233809d4e5e2 | train | documentation_lookup | mdn | https://developer.mozilla.org/en-US/docs/Web/HTML | HTML | productivity | ruby | distributed_systems | Find and summarize the relevant documentation for distributed_systems. | {"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... | === RELEVANT DOCS ===
- HTML
https://developer.mozilla.org/en-US/docs/Web/HTML
- Official project documentation
- API reference
=== KEY SECTIONS ===
- Getting started
- API reference
- Configuration
- Troubleshooting
=== SUMMARY ===
Summarize each section in 1–3 sentences and quote exact signatures where relevant. | web-research-coding-5m-1.1.0 | |
64434298220e99cc664cd2df | train | root_cause_analysis | huggingface | https://huggingface.co/datasets/bgudmestad/Nushell_documentation | bgudmestad/Nushell_documentation | ecommerce | swift | ci_cd | Perform a deep multi-layer analysis of ci_cd for a ecommerce 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": "bgudmestad/Nushell_documentation", "source_url": "https://huggingface.co/datasets/bgudmestad/... | === 1. PROBLEM ===
Define the exact problem involving ci_cd. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around ci_cd. Use 'bgudmestad/Nushell_documentation' as a source anchor and identify relevant APIs, dependencies, vers... | web-research-coding-5m-1.1.0 | |
b413900fe57a186f9870c6fd | train | debugging_experience | huggingface | https://huggingface.co/datasets/CoIR-Retrieval/CodeSearchNet-javascript-queries-corpus | CoIR-Retrieval/CodeSearchNet-javascript-queries-corpus | saas | php | documentation | Perform a deep developer-experience analysis for a php project involving documentation. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "CoIR-Retrieval/CodeSearchNet-javascript-queries-corpus", "source_url": "https://huggingface.c... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
0a7c79aee22175894e51ed01 | train | api_developer_experience | web_docs | https://git-scm.com/doc | Git Documentation | blog | c | debugging | Perform a deep developer-experience analysis for a c project involving debugging. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Git Documentation", "source_url": "https://git-scm.com/doc", "source_type": "documentation", ... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
41bcf80b3f6a31da969835ab | train | fact_verification | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API | Fetch API | search_interface | php | microservices | Verify a technical claim about microservices. | {"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... | === CLAIM ===
A common claim about microservices.
=== 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... | web-research-coding-5m-1.1.0 | |
98d746ce6ce14bcd02a34074 | train | refactoring_scalability | stackexchange | https://stackoverflow.com/questions/3133243/how-do-i-get-the-path-to-the-current-script-with-node-js | How do I get the path to the current script with Node.js? | finance | rust | web_accessibility | Refactor a rust system related to web_accessibility. Focus on refactoring scalability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How do I get the path to the current script with Node.js?", "source_url": "https://stackoverf... | === 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 | |
486f1bbf8068e3af93630adc | train | risk_analysis | huggingface | https://huggingface.co/datasets/theblackcat102/evol-codealpaca-v1 | theblackcat102/evol-codealpaca-v1 | dashboard | swift | css | Perform a deep multi-layer analysis of css for a dashboard using swift. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "theblackcat102/evol-codealpaca-v1", "source_url": "https://huggingface.co/datasets/theblackca... | === 1. PROBLEM ===
Define the exact problem involving css. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around css. Use 'theblackcat102/evol-codealpaca-v1' as a source anchor and identify relevant APIs, dependencies, version... | web-research-coding-5m-1.1.0 | |
a37df9b9dd7263d158ef078c | train | refactoring_observability | codeberg | https://codeberg.org/Khaveesh/_cargo-index | Khaveesh/_cargo-index | marketplace | cpp | documentation | Refactor a cpp system related to documentation. Focus on refactoring observability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Khaveesh/_cargo-index", "source_url": "https://codeberg.org/Khaveesh/_cargo-index", "source_t... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Improve logging, metrics, tracing, diagnostics, and failure visibility.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify d... | web-research-coding-5m-1.1.0 | |
acc317a6d0aa1d9767c34b30 | train | research_plan | gitlab | https://gitlab.com/jakelazaroff/narrows | jakelazaroff/narrows | admin_panel | css | data_engineering | Build a structured research plan to deeply understand data_engineering. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "jakelazaroff/narrows", "source_url": "https://gitlab.com/jakelazaroff/narrows", "source_type"... | === GOAL ===
Produce a reliable, current, and actionable understanding of data_engineering.
=== 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 fi... | web-research-coding-5m-1.1.0 | |
26a2cf42e5ec4aa480087188 | train | product_analysis | pypi | https://pypi.org/project/beautifulsoup4/ | beautifulsoup4 | analytics | css | html | Perform a deep multi-layer analysis of html for a analytics using css. 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": "beautifulsoup4", "source_url": "https://pypi.org/project/beautifulsoup4/", "source_type": "pa... | === 1. PROBLEM ===
Define the exact problem involving html. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around html. Use 'beautifulsoup4' as a source anchor and identify relevant APIs, dependencies, versions, standards, and... | web-research-coding-5m-1.1.0 | |
70b44319b700051277c37dbc | train | developer_experience | mdn | https://developer.mozilla.org/en-US/docs/Web/HTTP | HTTP | portfolio | php | python | Perform a deep developer-experience analysis for a php project involving python. | {"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. 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 | |
6e625eea7efa911a41a43290 | train | cli_experience | huggingface | https://huggingface.co/datasets/OpenVINO/documentation | OpenVINO/documentation | analytics | sql | cloud | Perform a deep developer-experience analysis for a sql project involving cloud. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "OpenVINO/documentation", "source_url": "https://huggingface.co/datasets/OpenVINO/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 | |
08cb7934d67b1327ce34fe19 | train | interaction_design | pypi | https://pypi.org/project/fastapi/ | fastapi | search_interface | go | design_system | Design interaction states for a search_interface. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "fastapi", "source_url": "https://pypi.org/project/fastapi/", "source_type": "package", "topic... | Specify default, hover, focus, active, disabled, loading, success, error, and empty states. | web-research-coding-5m-1.1.0 | |
e1c66877ba80627a21b40354 | train | technical_research | huggingface | https://huggingface.co/datasets/MathCodeBench/linear-programming | MathCodeBench/linear-programming | dashboard | kotlin | data_structures | Perform a technical research task about data_structures, focused on implementation details. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "MathCodeBench/linear-programming", "source_url": "https://huggingface.co/datasets/MathCodeBen... | === SCOPE ===
Technical behavior of data_structures.
=== QUESTIONS ===
- What are the inputs, outputs, and invariants?
- What are the performance characteristics?
- What are the security implications?
- What are the compatibility constraints?
=== EVIDENCE ===
- MathCodeBench/linear-programming (https://huggingface.co... | web-research-coding-5m-1.1.0 | |
12efb1445a869aa2864e6480 | train | documentation_experience | huggingface | https://huggingface.co/datasets/IFM/Code-Reasoning | IFM/Code-Reasoning | productivity | css | sql | Perform a deep developer-experience analysis for a css project involving sql. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "IFM/Code-Reasoning", "source_url": "https://huggingface.co/datasets/IFM/Code-Reasoning", "sou... | === 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 | |
aa6e56103209a80fd329c4a0 | train | code_explanation | stackexchange | https://stackoverflow.com/questions/43034960/many-to-one-and-many-to-many-lstm-examples-in-keras | Many to one and many to many LSTM examples in Keras | productivity | java | data_engineering | Explain a java implementation related to data_engineering. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Many to one and many to many LSTM examples in Keras", "source_url": "https://stackoverflow.co... | Explain inputs, outputs, control flow, algorithms, complexity, edge cases, errors, and maintainability. | web-research-coding-5m-1.1.0 | |
38cf9b1ff77840f9e7c870ee | train | deep_technical_analysis | huggingface | https://huggingface.co/datasets/joey234/mmlu-machine_learning-dev | joey234/mmlu-machine_learning-dev | productivity | typescript | javascript | Perform a deep multi-layer analysis of javascript for a productivity using typescript. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "joey234/mmlu-machine_learning-dev", "source_url": "https://huggingface.co/datasets/joey234/mm... | === 1. PROBLEM ===
Define the exact problem involving javascript. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around javascript. Use 'joey234/mmlu-machine_learning-dev' as a source anchor and identify relevant APIs, depende... | web-research-coding-5m-1.1.0 | |
b23775a69274d439fc2e2ac5 | train | api_design | npm | https://www.npmjs.com/package/hono | hono | blog | ruby | deep_learning | Design a production API for a deep_learning application. | {"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":... | Specify resources, endpoints, schemas, validation, authentication, authorization, errors, pagination, versioning, idempotency, and tests. | web-research-coding-5m-1.1.0 | |
88bc5b7def9f6770c1cb77ff | train | dependency_impact_analysis | stackexchange | https://stackoverflow.com/questions/6182315/how-can-i-do-base64-encoding-in-node-js | How can I do Base64 encoding in Node.js? | documentation | php | user_experience | Perform a deep multi-layer analysis of user_experience 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": "How can I do Base64 encoding in Node.js?", "source_url": "https://stackoverflow.com/questions... | === 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 'How can I do Base64 encoding in Node.js?' as a source anchor and identify relev... | web-research-coding-5m-1.1.0 | |
4b07ed08f659a43f7d739dc0 | train | local_development_experience | web_docs | https://doc.rust-lang.org/ | Rust Documentation | marketplace | ruby | redis | Perform a deep developer-experience analysis for a ruby project involving redis. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "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 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.