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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
5e0c4cb9d02677f534b76a66 | train | refactoring_architecture | stackexchange | https://stackoverflow.com/questions/16056591/font-scaling-based-on-size-of-container | Font scaling based on size of container | documentation | scala | redis | Refactor a scala system related to redis. Focus on refactoring architecture. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Font scaling based on size of container", "source_url": "https://stackoverflow.com/questions/... | === 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 | |
cecd3649ba826f6cd212caf3 | train | source_comparison | mdn | https://developer.mozilla.org/en-US/docs/Web/JavaScript | JavaScript | social_app | php | open_source | Compare multiple sources about open_source 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": "JavaScript", "source_url": "https://developer.mozilla.org/en-US/docs/Web/JavaScript", "source... | === SOURCES ===
- JavaScript (https://developer.mozilla.org/en-US/docs/Web/JavaScript)
- Official documentation
- Community discussions
=== AGREEMENTS ===
Identify claims supported by multiple independent sources.
=== CONTRADICTIONS ===
Identify conflicting claims and their likely cause (version differences, environm... | web-research-coding-5m-1.1.0 | |
9c55b841ca90bb38e895f3db | train | testing_experience | mdn | https://developer.mozilla.org/en-US/docs/Web/API | Web APIs | developer_tool | python | frontend | Perform a deep developer-experience analysis for a python project involving frontend. | {"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... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
4657a3935f08ae24e726382c | train | repository_comparison | stackexchange | https://stackoverflow.com/questions/450903/how-can-i-make-a-div-not-larger-than-its-contents | How can I make a div not larger than its contents? | admin_panel | c | developer_experience | Perform a deep multi-layer analysis of developer_experience for a admin_panel 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 can I make a div not larger than its contents?", "source_url": "https://stackoverflow.com... | === 1. PROBLEM ===
Define the exact problem involving developer_experience. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around developer_experience. Use 'How can I make a div not larger than its contents?' as a source ancho... | web-research-coding-5m-1.1.0 | |
d7edf6eb6f2444198b370b9a | train | refactoring_scalability | gitlab | https://gitlab.com/gorlapraveen/TheLearningDocumentationProject | gorlapraveen/TheLearningDocumentationProject | dashboard | c | javascript | Refactor a c 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": "gorlapraveen/TheLearningDocumentationProject", "source_url": "https://gitlab.com/gorlapraveen... | === 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 | |
9156d2e52cdf8b46af394254 | train | design_to_code | mdn | https://developer.mozilla.org/en-US/docs/Web/HTTP | HTTP | ecommerce | typescript | typescript | Translate a ecommerce design into maintainable typescript code. | {"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... | 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 | |
077aa7c271910d080c490b27 | train | scalability_analysis | web_docs | https://docs.docker.com/ | Docker Documentation | productivity | java | typescript | Perform a deep multi-layer analysis of typescript for a productivity 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": "Docker Documentation", "source_url": "https://docs.docker.com/", "source_type": "documentatio... | === 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 'Docker Documentation' as a source anchor and identify relevant APIs, dependencies, versio... | web-research-coding-5m-1.1.0 | |
912575dc7b4de138924e0b4e | train | typescript_generation | stackexchange | https://stackoverflow.com/questions/3207219/how-do-i-list-all-files-of-a-directory | How do I list all files of a directory? | marketplace | php | rest_api | Implement TypeScript logic for a marketplace. | {"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/... | 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 |
455d373c2fc5ba8297f408e1 | train | visual_hierarchy | stackexchange | https://stackoverflow.com/questions/879432/what-is-the-difference-between-a-generative-and-a-discriminative-algorithm | What is the difference between a generative and a discriminative algorithm? | education | shell | deep_learning | Improve visual hierarchy in a education. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "What is the difference between a generative and a discriminative algorithm?", "source_url": "... | Use heading structure, typography, spacing, grouping, alignment, contrast, and consistent affordances. | web-research-coding-5m-1.1.0 | |
10af890f771c348d8f16efed | train | upgrade_experience | npm | https://www.npmjs.com/package/react | react | marketplace | go | data_structures | Perform a deep developer-experience analysis for a go project involving data_structures. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "react", "source_url": "https://www.npmjs.com/package/react", "source_type": "package", "topic... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
a285f70cd15cbce49e03ea50 | train | seo_fix | huggingface | https://huggingface.co/datasets/hchautran/javascript-small | hchautran/javascript-small | blog | swift | debugging | Create an SEO improvement plan for a blog about debugging. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "hchautran/javascript-small", "source_url": "https://huggingface.co/datasets/hchautran/javascr... | Cover titles, descriptions, headings, canonical URLs, structured data, internal links, crawlability, and performance. | web-research-coding-5m-1.1.0 | |
dbf6629bf7bff897f797e8ac | train | repository_understanding | codeberg | https://codeberg.org/Scratch-Lee/_cargo-index | Scratch-Lee/_cargo-index | admin_panel | rust | sql | Perform a deep multi-layer analysis of sql for a admin_panel 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": "Scratch-Lee/_cargo-index", "source_url": "https://codeberg.org/Scratch-Lee/_cargo-index", "so... | === 1. PROBLEM ===
Define the exact problem involving sql. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around sql. Use 'Scratch-Lee/_cargo-index' as a source anchor and identify relevant APIs, dependencies, versions, standa... | web-research-coding-5m-1.1.0 | |
8bf838ce0164e09c0cb4eb34 | train | repository_architecture | github | https://github.com/zulip/zulip | zulip/zulip | documentation | cpp | ci_cd | Perform a deep multi-layer analysis of ci_cd for a documentation using cpp. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "zulip/zulip", "source_url": "https://github.com/zulip/zulip", "source_type": "repository", "t... | === 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 'zulip/zulip' as a source anchor and identify relevant APIs, dependencies, versions, standards, and ... | web-research-coding-5m-1.1.0 | |
98eb34647f5871ce3f2ecf4d | train | design_components | huggingface | https://huggingface.co/datasets/PrunaAI/documentation-images | PrunaAI/documentation-images | ecommerce | javascript | python | Create a component architecture for a ecommerce. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "PrunaAI/documentation-images", "source_url": "https://huggingface.co/datasets/PrunaAI/documen... | Define primitive components, composite components, variants, states, composition rules, and accessibility contracts. | web-research-coding-5m-1.1.0 | |
b43b5baef8c983cd0db2f2a6 | train | deployment_experience | pypi | https://pypi.org/project/fastapi/ | fastapi | education | css | html | Perform a deep developer-experience analysis for a css project involving html. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "fastapi", "source_url": "https://pypi.org/project/fastapi/", "source_type": "package", "topic... | === 1. 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 | |
2f2135e533c277c300f00130 | train | research_summary | codeberg | https://codeberg.org/anth1y/100-exercises-to-learn-rust | anth1y/100-exercises-to-learn-rust | landing_page | dart | microservices | Summarize the current state of knowledge about microservices. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "anth1y/100-exercises-to-learn-rust", "source_url": "https://codeberg.org/anth1y/100-exercises... | === OVERVIEW ===
microservices in one paragraph.
=== KEY CONCEPTS ===
- Core definitions
- Main use cases
- Common patterns
=== CURRENT BEST PRACTICES ===
- Recommended approaches
- Known anti-patterns
=== OPEN QUESTIONS ===
- Areas with active development
- Known limitations
=== PRIMARY SOURCE ===
anth1y/100-exerc... | web-research-coding-5m-1.1.0 | |
41f61accb8a1194fc6e44f4c | train | javascript_generation | mdn | https://developer.mozilla.org/en-US/docs/Web/JavaScript | JavaScript | blog | dart | css | Implement JavaScript interactions for a blog. | {"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 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 |
9762e34e8221627fb4a226bb | train | nextjs_generation | codeberg | https://codeberg.org/I-ATE-OREO/2025uyltut76 | I-ATE-OREO/2025uyltut76 | dashboard | kotlin | typescript | Design a Next.js architecture for a dashboard. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "I-ATE-OREO/2025uyltut76", "source_url": "https://codeberg.org/I-ATE-OREO/2025uyltut76", "sour... | 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 |
dbf4697aafdab48f111078f5 | train | architecture_analysis | web_docs | https://www.postgresql.org/docs/ | PostgreSQL Documentation | search_interface | kotlin | design_system | Perform a deep multi-layer analysis of design_system for a search_interface 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": "PostgreSQL Documentation", "source_url": "https://www.postgresql.org/docs/", "source_type": "... | === 1. PROBLEM ===
Define the exact problem involving design_system. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around design_system. Use 'PostgreSQL Documentation' as a source anchor and identify relevant APIs, dependenci... | web-research-coding-5m-1.1.0 | |
ddb75b4c63c8cd2326b2bd07 | train | cli_experience | pypi | https://pypi.org/project/pytest/ | pytest | marketplace | ruby | cloud | Perform a deep developer-experience analysis for a ruby project involving cloud. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "pytest", "source_url": "https://pypi.org/project/pytest/", "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 | |
ac14fc5ac145698455c8d3bf | train | integration_testing | huggingface | https://huggingface.co/datasets/nvidia/Nemotron-SFT-Multilingual-v2 | nvidia/Nemotron-SFT-Multilingual-v2 | admin_panel | swift | rest_api | Design integration tests for a swift system involving rest_api. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "nvidia/Nemotron-SFT-Multilingual-v2", "source_url": "https://huggingface.co/datasets/nvidia/N... | Test real component boundaries, persistence, configuration, external interfaces, errors, cleanup, and realistic workflows. | web-research-coding-5m-1.1.0 | |
b2fea00702fd251867d58413 | train | refactoring_dependency | npm | https://www.npmjs.com/package/jest | jest | search_interface | javascript | postgresql | Refactor a javascript system related to postgresql. Focus on refactoring dependency. | {"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":... | === 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 | |
e62d212ae2efce125af0f7cf | train | api_design | gitlab | https://gitlab.com/algomus.fr/dezrann/dezrann-front | algomus.fr/dezrann/dezrann-front | admin_panel | shell | 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": "algomus.fr/dezrann/dezrann-front", "source_url": "https://gitlab.com/algomus.fr/dezrann/dezra... | Specify resources, endpoints, schemas, validation, authentication, authorization, errors, pagination, versioning, idempotency, and tests. | web-research-coding-5m-1.1.0 | |
291aef1c1d2392f52c81b33f | train | repository_understanding | gitlab | https://gitlab.com/papalingua/papalingua-app | papalingua/papalingua-app | search_interface | c | web_performance | Perform a deep multi-layer analysis of web_performance for a search_interface 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": "papalingua/papalingua-app", "source_url": "https://gitlab.com/papalingua/papalingua-app", "so... | === 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 'papalingua/papalingua-app' as a source anchor and identify relevant APIs, depen... | web-research-coding-5m-1.1.0 | |
9f05c25348e61c261643136d | train | debugging_experience | huggingface | https://huggingface.co/datasets/MachineLearningLM/machinelearninglm-scm-synthetic-tabularml | MachineLearningLM/machinelearninglm-scm-synthetic-tabularml | saas | typescript | developer_experience | Perform a deep developer-experience analysis for a typescript project involving developer_experience. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "MachineLearningLM/machinelearninglm-scm-synthetic-tabularml", "source_url": "https://huggingf... | === 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 | |
3b7486a1f0650273843bf36c | train | scalability_analysis | stackexchange | https://stackoverflow.com/questions/13142635/how-can-i-create-an-object-based-on-an-interface-file-definition-in-typescript | How can I create an object based on an interface file definition in TypeScript? | productivity | shell | ci_cd | Perform a deep multi-layer analysis of ci_cd for a productivity 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 can I create an object based on an interface file definition in TypeScript?", "source_url... | === 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 'How can I create an object based on an interface file definition in TypeScript?' as a source anchor... | web-research-coding-5m-1.1.0 | |
19865db7d399837f50e52996 | train | api_developer_experience | stackexchange | https://stackoverflow.com/questions/3680429/click-through-div-to-underlying-elements | Click through div to underlying elements | dashboard | kotlin | software_architecture | Perform a deep developer-experience analysis for a kotlin project involving software_architecture. | {"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 | |
a0c83a2c2326a2cdd1a20a0b | train | developer_experience | gitlab | https://gitlab.com/philbooth/check-types.js | philbooth/check-types.js | marketplace | ruby | kubernetes | Perform a deep developer-experience analysis for a ruby project involving kubernetes. | {"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... | === 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 | |
6c2dc14effe23d1c627bcc8c | train | refactoring_dependency | pypi | https://pypi.org/project/scikit-learn/ | scikit-learn | saas | scala | sql | Refactor a scala system related to sql. Focus on refactoring dependency. | {"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... | === 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 | |
c0853abe2eecc4fadc145428 | train | performance_fix | npm | https://www.npmjs.com/package/eslint | eslint | documentation | typescript | api_design | Create a web-performance optimization plan for a documentation. | {"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... | Measure first, then optimize bundle size, images, network requests, rendering, caching, and critical resources. | web-research-coding-5m-1.1.0 | |
24874b4177b9a4ff4fa661b5 | train | repository_issue_reasoning | huggingface | https://huggingface.co/datasets/IFM/Code-Reasoning | IFM/Code-Reasoning | blog | scala | deep_learning | Perform a deep multi-layer analysis of deep_learning for a blog 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": "IFM/Code-Reasoning", "source_url": "https://huggingface.co/datasets/IFM/Code-Reasoning", "sou... | === 1. PROBLEM ===
Define the exact problem involving deep_learning. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around deep_learning. Use 'IFM/Code-Reasoning' as a source anchor and identify relevant APIs, dependencies, ve... | web-research-coding-5m-1.1.0 | |
5ad458ce66264625ed92d095 | train | refactoring_readability | web_docs | https://www.typescriptlang.org/docs/ | TypeScript Documentation | documentation | c | testing | Refactor a c system related to testing. Focus on refactoring readability. | {"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... | === 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 | |
5b469d8166fe98f1f961f708 | train | search_query_rewrite | web_docs | https://kubernetes.io/docs/ | Kubernetes Documentation | education | c | nodejs | Rewrite and improve a vague search query about nodejs 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": "Kubernetes Documentation", "source_url": "https://kubernetes.io/docs/", "source_type": "docum... | === ORIGINAL (VAGUE) ===
how to do nodejs
=== REWRITTEN QUERIES ===
1. nodejs official documentation guide
2. nodejs production best practices 2025
3. nodejs common pitfalls and solutions
4. nodejs architecture patterns with examples
=== RATIONALE ===
Add intent (learn / implement / debug), specificity (version, fram... | web-research-coding-5m-1.1.0 | |
5604f6537cea67e684f0d053 | train | deep_technical_analysis | web_docs | https://docs.docker.com/ | Docker Documentation | marketplace | html | algorithms | Perform a deep multi-layer analysis of algorithms for a marketplace 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": "Docker Documentation", "source_url": "https://docs.docker.com/", "source_type": "documentatio... | === 1. PROBLEM ===
Define the exact problem involving algorithms. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around algorithms. Use 'Docker Documentation' as a source anchor and identify relevant APIs, dependencies, versio... | web-research-coding-5m-1.1.0 | |
b957bdf7cdaa4192fbce0d1e | train | component_design | npm | https://www.npmjs.com/package/prettier | prettier | saas | css | fullstack | Design reusable UI components for a saas. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "prettier", "source_url": "https://www.npmjs.com/package/prettier", "source_type": "package", ... | Define component responsibilities, props/data contracts, variants, states, composition rules, accessibility, testing, and documentation. | web-research-coding-5m-1.1.0 | |
7aaa6e416876b7a1ab2f133a | train | code_explanation | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API | Fetch API | social_app | javascript | ci_cd | Explain a javascript implementation related to ci_cd. | {"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... | Explain inputs, outputs, control flow, algorithms, complexity, edge cases, errors, and maintainability. | web-research-coding-5m-1.1.0 | |
d6589994cb4382c6f18d10fc | train | product_analysis | pypi | https://pypi.org/project/pytest/ | pytest | marketplace | kotlin | javascript | Perform a deep multi-layer analysis of javascript for a marketplace 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": "pytest", "source_url": "https://pypi.org/project/pytest/", "source_type": "package", "topic":... | === 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 'pytest' as a source anchor and identify relevant APIs, dependencies, versions, standards,... | web-research-coding-5m-1.1.0 | |
41542526dbba775c636f9f7f | train | refactoring_scalability | 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? | search_interface | dart | devops | Refactor a dart system related to devops. Focus on refactoring scalability. | {"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:... | === 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 | |
e6ec085b034d2dfbb4add190 | train | refactoring_security | github | https://github.com/shadcn-ui/ui | shadcn-ui/ui | community | css | fullstack | Refactor a css system related to fullstack. Focus on refactoring security. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "shadcn-ui/ui", "source_url": "https://github.com/shadcn-ui/ui", "source_type": "repository", ... | === 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 | |
2ec37bd5facbdbc8737acb75 | train | maintainability_analysis | npm | https://www.npmjs.com/package/rollup | rollup | admin_panel | css | web_performance | Perform a deep multi-layer analysis of web_performance for a admin_panel 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": "rollup", "source_url": "https://www.npmjs.com/package/rollup", "source_type": "package", "top... | === 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 'rollup' as a source anchor and identify relevant APIs, dependencies, versions, ... | web-research-coding-5m-1.1.0 | |
3b6ac24d146b42e7a5f9fc6c | train | accessibility_analysis | web_docs | https://kubernetes.io/docs/ | Kubernetes Documentation | saas | kotlin | authorization | Perform a deep multi-layer analysis of authorization 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": "Kubernetes Documentation", "source_url": "https://kubernetes.io/docs/", "source_type": "docum... | === 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 'Kubernetes Documentation' as a source anchor and identify relevant APIs, dependenci... | web-research-coding-5m-1.1.0 | |
9c67296eb1be702c633d8b55 | train | integration_testing | stackexchange | https://stackoverflow.com/questions/105034/how-do-i-create-a-guid-uuid | How do I create a GUID / UUID? | developer_tool | ruby | observability | Design integration tests for a ruby system involving observability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How do I create a GUID / UUID?", "source_url": "https://stackoverflow.com/questions/105034/ho... | Test real component boundaries, persistence, configuration, external interfaces, errors, cleanup, and realistic workflows. | web-research-coding-5m-1.1.0 | |
162b0e072e86f93a4e2f5740 | train | refactoring_architecture | gitlab | https://gitlab.com/unconed/use.gpu | unconed/use.gpu | productivity | kotlin | devops | Refactor a kotlin 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": "unconed/use.gpu", "source_url": "https://gitlab.com/unconed/use.gpu", "source_type": "reposit... | === 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 | |
086c0b0054054fb7eef82985 | train | repository_issue_reasoning | npm | https://www.npmjs.com/package/three | three | marketplace | ruby | observability | Perform a deep multi-layer analysis of observability for a marketplace 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": "three", "source_url": "https://www.npmjs.com/package/three", "source_type": "package", "topic... | === 1. PROBLEM ===
Define the exact problem involving observability. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around observability. Use 'three' as a source anchor and identify relevant APIs, dependencies, versions, stand... | web-research-coding-5m-1.1.0 | |
0466aaa637a48e4ac98937fe | train | cli_experience | codeberg | https://codeberg.org/Quanti/_cargo-index | Quanti/_cargo-index | portfolio | javascript | distributed_systems | Perform a deep developer-experience analysis for a javascript project involving distributed_systems. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Quanti/_cargo-index", "source_url": "https://codeberg.org/Quanti/_cargo-index", "source_type"... | === 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 | |
0beb3ead6447e0d159c2a30c | train | landing_page | gitlab | https://gitlab.com/john.carroll.p/rschedule | john.carroll.p/rschedule | education | html | ci_cd | Design a landing page for a ci_cd product. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "john.carroll.p/rschedule", "source_url": "https://gitlab.com/john.carroll.p/rschedule", "sour... | Include hero, value proposition, features, CTA, FAQ, responsive behavior, SEO, accessibility, and analytics. | web-research-coding-5m-1.1.0 | |
1253491b123ff269a4d1c23c | train | source_selection | pypi | https://pypi.org/project/pydantic/ | pydantic | ecommerce | c | user_experience | Select the most reliable sources to research user_experience. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "pydantic", "source_url": "https://pypi.org/project/pydantic/", "source_type": "package", "top... | === SOURCE 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 | |
2a9bcc87ca1001f987c8c60d | train | dx_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/CSS | CSS | portfolio | ruby | microservices | Perform a deep developer-experience analysis for a ruby project involving microservices. | {"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 | |
6981bd0815210d5e9b8e14ff | train | multi_hop_research | huggingface | https://huggingface.co/datasets/embedl/documentation-images | embedl/documentation-images | portfolio | html | javascript | Perform multi-hop research about javascript: start from a source, follow references, and combine findings. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "embedl/documentation-images", "source_url": "https://huggingface.co/datasets/embedl/documenta... | === HOP 1 ===
Start at: embedl/documentation-images
https://huggingface.co/datasets/embedl/documentation-images
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.
Extrac... | web-research-coding-5m-1.1.0 | |
decee42b3d4dcbcc54228f58 | train | refactoring_performance | web_docs | https://nodejs.org/docs/latest/api/ | Node.js Documentation | portfolio | python | authentication | Refactor a python system related to authentication. Focus on refactoring performance. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Node.js Documentation", "source_url": "https://nodejs.org/docs/latest/api/", "source_type": "... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Reduce unnecessary computation, allocations, I/O, and network requests.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify d... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
82997705938a3335edda8715 | train | deep_technical_analysis | github | https://github.com/D4Vinci/Scrapling | D4Vinci/Scrapling | social_app | python | css | Perform a deep multi-layer analysis of css for a social_app 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": "D4Vinci/Scrapling", "source_url": "https://github.com/D4Vinci/Scrapling", "source_type": "rep... | === 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 'D4Vinci/Scrapling' as a source anchor and identify relevant APIs, dependencies, versions, standards, an... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
406fa9830773d91b5d17ea2f | train | refactoring | gitlab | https://gitlab.com/pyspread/pyspread | pyspread/pyspread | saas | python | nlp | Create a production coding task in python for nlp. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "pyspread/pyspread", "source_url": "https://gitlab.com/pyspread/pyspread", "source_type": "rep... | Provide implementation requirements, edge cases, testing requirements, security considerations, performance constraints, and documentation requirements. | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
f2f51700b10d01b4f7e87d7e | train | ux_analysis | web_docs | https://docs.docker.com/ | Docker Documentation | finance | scala | redis | Perform a deep multi-layer analysis of redis for a finance 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": "Docker Documentation", "source_url": "https://docs.docker.com/", "source_type": "documentatio... | === 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 'Docker Documentation' as a source anchor and identify relevant APIs, dependencies, versions, standa... | web-research-coding-5m-1.1.0 | |
1eee6f0b192ba9399c37b581 | train | html_generation | huggingface | https://huggingface.co/datasets/nomic-ai/cornstack-javascript-v1 | nomic-ai/cornstack-javascript-v1 | marketplace | sql | observability | Create semantic HTML for a marketplace about observability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "nomic-ai/cornstack-javascript-v1", "source_url": "https://huggingface.co/datasets/nomic-ai/co... | 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 |
8e14576f22cdb2e22ffb552a | train | ux_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/Performance | Performance | developer_tool | scala | frontend | Perform a deep multi-layer analysis of frontend 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": "Performance", "source_url": "https://developer.mozilla.org/en-US/docs/Web/Performance", "sour... | === 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 'Performance' as a source anchor and identify relevant APIs, dependencies, versions, standards... | web-research-coding-5m-1.1.0 | |
9101328fbe3a0cddd0e92b15 | train | refactoring_dependency | stackexchange | https://stackoverflow.com/questions/391005/how-can-i-add-html-and-css-into-pdf | How Can I add HTML And CSS Into PDF | ecommerce | php | open_source | Refactor a php system related to open_source. Focus on refactoring dependency. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How Can I add HTML And CSS Into PDF", "source_url": "https://stackoverflow.com/questions/3910... | === 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 | |
b3c1b159cacf2874e6137925 | train | responsive_website | npm | https://www.npmjs.com/package/vite | vite | ecommerce | kotlin | database | Design a complete responsive ecommerce for database. | {"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":... | Cover mobile, tablet, and desktop layouts, semantic structure, responsive components, accessibility, performance, and UX. | web-research-coding-5m-1.1.0 | |
c7e8b6f0e93a8cdb9309d77f | train | refactoring_readability | npm | https://www.npmjs.com/package/vue | vue | search_interface | ruby | deep_learning | Refactor a ruby system related to deep_learning. Focus on refactoring readability. | {"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": "... | === 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 | |
53a41cd3a88e6e93764bc580 | train | performance_analysis | huggingface | https://huggingface.co/datasets/jan-hq/multiturn_programming_binarized | jan-hq/multiturn_programming_binarized | saas | php | security | Perform a deep multi-layer analysis of security for a saas 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": "jan-hq/multiturn_programming_binarized", "source_url": "https://huggingface.co/datasets/jan-h... | === 1. PROBLEM ===
Define the exact problem involving security. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around security. Use 'jan-hq/multiturn_programming_binarized' as a source anchor and identify relevant APIs, depend... | web-research-coding-5m-1.1.0 | |
214f2c3cf37ae3fcf2978d43 | train | scalability_analysis | stackexchange | https://stackoverflow.com/questions/50605219/difference-between-npx-and-npm | Difference between npx and npm | admin_panel | shell | authentication | Perform a deep multi-layer analysis of authentication for a admin_panel 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": "Difference between npx and npm", "source_url": "https://stackoverflow.com/questions/50605219/... | === 1. PROBLEM ===
Define the exact problem involving authentication. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around authentication. Use 'Difference between npx and npm' as a source anchor and identify relevant APIs, de... | web-research-coding-5m-1.1.0 | |
ffd15dec5e9f90c508f78a63 | train | react_generation | pypi | https://pypi.org/project/gradio/ | gradio | education | sql | html | Design React components for a education. | {"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":... | 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 |
485514da105e3dc8bb905201 | train | fact_verification | web_docs | https://www.typescriptlang.org/docs/ | TypeScript Documentation | developer_tool | kotlin | sql | Verify a technical claim about sql. | {"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... | === CLAIM ===
A common claim about sql.
=== 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-dependent... | web-research-coding-5m-1.1.0 | |
cdd0cab1a0fdae823e122586 | train | repository_documentation | npm | https://www.npmjs.com/package/rollup | rollup | saas | swift | sql | Perform a deep multi-layer analysis of sql for a saas 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": "rollup", "source_url": "https://www.npmjs.com/package/rollup", "source_type": "package", "top... | === 1. PROBLEM ===
Define the exact problem involving sql. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around sql. Use 'rollup' as a source anchor and identify relevant APIs, dependencies, versions, standards, and technical... | web-research-coding-5m-1.1.0 | |
2bb577a90310fce3b64eaa36 | train | maintainability_analysis | web_docs | https://react.dev/ | React Documentation | productivity | typescript | linux | Perform a deep multi-layer analysis of linux 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": "React Documentation", "source_url": "https://react.dev/", "source_type": "documentation", "to... | === 1. PROBLEM ===
Define the exact problem involving linux. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around linux. Use 'React Documentation' as a source anchor and identify relevant APIs, dependencies, versions, standar... | web-research-coding-5m-1.1.0 | |
6ed13a471bbccc346c6a375a | train | tradeoff_analysis | npm | https://www.npmjs.com/package/vue | vue | marketplace | scala | microservices | Perform a deep multi-layer analysis of microservices for a marketplace 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 microservices. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around microservices. Use 'vue' as a source anchor and identify relevant APIs, dependencies, versions, standar... | web-research-coding-5m-1.1.0 | |
8c75c08d284e44666810e8e0 | train | source_comparison | codeberg | https://codeberg.org/nathawat/_cargo-index | nathawat/_cargo-index | productivity | shell | css | Compare multiple sources about css 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": "nathawat/_cargo-index", "source_url": "https://codeberg.org/nathawat/_cargo-index", "source_t... | === SOURCES ===
- nathawat/_cargo-index (https://codeberg.org/nathawat/_cargo-index)
- Official documentation
- Community discussions
=== AGREEMENTS ===
Identify claims supported by multiple independent sources.
=== CONTRADICTIONS ===
Identify conflicting claims and their likely cause (version differences, environmen... | web-research-coding-5m-1.1.0 | |
f360545bac4285067388eeab | train | refactoring_testability | stackexchange | https://stackoverflow.com/questions/134882/undoing-a-git-rebase | Undoing a git rebase | developer_tool | cpp | nextjs | Refactor a cpp system related to nextjs. Focus on refactoring testability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Undoing a git rebase", "source_url": "https://stackoverflow.com/questions/134882/undoing-a-gi... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Separate side effects and dependencies so behavior can be tested independently.
=== 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 | |
c40571224e3c08c569a5aeb4 | train | refactoring_legacy_code | stackexchange | https://stackoverflow.com/questions/37949981/call-child-method-from-parent | Call child method from parent | portfolio | go | open_source | Refactor a go system related to open_source. Focus on refactoring legacy code. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Call child method from parent", "source_url": "https://stackoverflow.com/questions/37949981/c... | === 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 | |
1d7135af088dee97150a35fc | train | algorithm_design | gitlab | https://gitlab.com/gemseo/dev/gemseo-mlearning | gemseo/dev/gemseo-mlearning | admin_panel | php | devops | Design a php algorithm for a devops problem. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "gemseo/dev/gemseo-mlearning", "source_url": "https://gitlab.com/gemseo/dev/gemseo-mlearning",... | State assumptions, algorithm, complexity, edge cases, correctness reasoning, and testing strategy. | web-research-coding-5m-1.1.0 | |
c84f4bf7280209430f931242 | train | performance_fix | stackexchange | https://stackoverflow.com/questions/20224526/how-to-extract-the-decision-rules-from-scikit-learn-decision-tree | How to extract the decision rules from scikit-learn decision-tree? | analytics | swift | machine_learning | Create a web-performance optimization plan for a analytics. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How to extract the decision rules from scikit-learn decision-tree?", "source_url": "https://s... | Measure first, then optimize bundle size, images, network requests, rendering, caching, and critical resources. | web-research-coding-5m-1.1.0 | |
b56b54ad03fcdb6effd833c7 | train | fact_verification | npm | https://www.npmjs.com/package/webpack | webpack | portfolio | shell | ci_cd | Verify a technical claim about ci_cd. | {"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... | === CLAIM ===
A common claim about ci_cd.
=== 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 | |
cc93498d1c06ef8ec5e96760 | train | design_tokens | pypi | https://pypi.org/project/gradio/ | gradio | admin_panel | shell | security | Create design tokens for a admin_panel. | {"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":... | Define reusable tokens for typography, spacing, radii, sizing, elevation, interaction states, and responsive behavior. | web-research-coding-5m-1.1.0 | |
32589bf6749beba3a3491d57 | train | developer_experience | web_docs | https://git-scm.com/doc | Git Documentation | social_app | typescript | caching | Perform a deep developer-experience analysis for a typescript project involving caching. | {"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 | |
2d58ad83d08d452ddd6038c2 | train | documentation_experience | huggingface | https://huggingface.co/datasets/Shuu12121/github-file-programs-dataset-javascript | Shuu12121/github-file-programs-dataset-javascript | ecommerce | php | postgresql | Perform a deep developer-experience analysis for a php project involving postgresql. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Shuu12121/github-file-programs-dataset-javascript", "source_url": "https://huggingface.co/dat... | === 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 | |
c419f762efa3725248879f3b | train | repository_documentation | mdn | https://developer.mozilla.org/en-US/docs/Web/JavaScript | JavaScript | blog | typescript | user_experience | Perform a deep multi-layer analysis of user_experience for a blog 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": "JavaScript", "source_url": "https://developer.mozilla.org/en-US/docs/Web/JavaScript", "source... | === 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 'JavaScript' as a source anchor and identify relevant APIs, dependencies, versio... | web-research-coding-5m-1.1.0 | |
a08eec04c2ff9ab631b5dc36 | train | code_explanation | web_docs | https://www.typescriptlang.org/docs/ | TypeScript Documentation | saas | shell | rest_api | Explain a shell implementation related to rest_api. | {"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... | Explain inputs, outputs, control flow, algorithms, complexity, edge cases, errors, and maintainability. | web-research-coding-5m-1.1.0 | |
f956d6e54f99765416bc3800 | train | nextjs_generation | pypi | https://pypi.org/project/pandas/ | pandas | analytics | ruby | graphql | Design a Next.js architecture for a analytics. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "pandas", "source_url": "https://pypi.org/project/pandas/", "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 |
ad7689d142ac27b5c515b39f | train | design_to_code | github | https://github.com/qeeqbox/social-analyzer | qeeqbox/social-analyzer | landing_page | go | database | Translate a landing_page design into maintainable go code. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "qeeqbox/social-analyzer", "source_url": "https://github.com/qeeqbox/social-analyzer", "source... | 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 | |
6541b9780a47d96f982227ff | train | dx_analysis | stackexchange | https://stackoverflow.com/questions/42081257/why-binary-crossentropy-and-categorical-crossentropy-give-different-performances | Why binary_crossentropy and categorical_crossentropy give different performances for the same problem? | portfolio | css | ci_cd | Perform a deep developer-experience analysis for a css project involving ci_cd. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Why binary_crossentropy and categorical_crossentropy give different performances for the same... | === 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 | |
79c391757553f220465f2364 | train | repository_dependency_analysis | huggingface | https://huggingface.co/datasets/Pq234/documentation-images | Pq234/documentation-images | finance | c | linux | Perform a deep multi-layer analysis of linux for a finance 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": "Pq234/documentation-images", "source_url": "https://huggingface.co/datasets/Pq234/documentati... | === 1. PROBLEM ===
Define the exact problem involving linux. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around linux. Use 'Pq234/documentation-images' as a source anchor and identify relevant APIs, dependencies, versions, ... | web-research-coding-5m-1.1.0 | |
53b8fc08a849b414a73da571 | train | refactoring_performance | huggingface | https://huggingface.co/datasets/bysismo/Turkish-Python-instruction | bysismo/Turkish-Python-instruction | portfolio | rust | ci_cd | Refactor a rust system related to ci_cd. Focus on refactoring performance. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "bysismo/Turkish-Python-instruction", "source_url": "https://huggingface.co/datasets/bysismo/T... | === 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 | |
97020423d2a47e5383cbc29f | train | design_to_code | huggingface | https://huggingface.co/datasets/JanSchTech/starcoderdata-python-edu-lang-score | JanSchTech/starcoderdata-python-edu-lang-score | developer_tool | cpp | observability | Translate a developer_tool design into maintainable cpp code. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "JanSchTech/starcoderdata-python-edu-lang-score", "source_url": "https://huggingface.co/datase... | 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 | |
f116372c4b540ebbaa64b42c | train | refactoring_dependency | pypi | https://pypi.org/project/fastapi/ | fastapi | search_interface | c | redis | Refactor a c system related to redis. Focus on refactoring dependency. | {"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... | === 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 | |
b80bd804265b372b489c85ab | train | tradeoff_analysis | pypi | https://pypi.org/project/pytest/ | pytest | marketplace | swift | nodejs | Perform a deep multi-layer analysis of nodejs for a marketplace 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": "pytest", "source_url": "https://pypi.org/project/pytest/", "source_type": "package", "topic":... | === 1. PROBLEM ===
Define the exact problem involving nodejs. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around nodejs. Use 'pytest' as a source anchor and identify relevant APIs, dependencies, versions, standards, and tec... | web-research-coding-5m-1.1.0 | |
19e7908ae72dfa0ff1e30d7d | train | source_selection | stackexchange | https://stackoverflow.com/questions/1125968/how-do-i-force-git-pull-to-overwrite-local-files | How do I force "git pull" to overwrite local files? | community | java | machine_learning | Select the most reliable sources to research machine_learning. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How do I force "git pull" to overwrite local files?", "source_url": "https://stacko... | === 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 | |
a166631a35d6cf70359ad06f | train | search_query_rewrite | pypi | https://pypi.org/project/requests/ | requests | blog | cpp | mongodb | Rewrite and improve a vague search query about mongodb 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": "requests", "source_url": "https://pypi.org/project/requests/", "source_type": "package", "top... | === ORIGINAL (VAGUE) ===
how to do mongodb
=== REWRITTEN QUERIES ===
1. mongodb official documentation guide
2. mongodb production best practices 2025
3. mongodb common pitfalls and solutions
4. mongodb architecture patterns with examples
=== RATIONALE ===
Add intent (learn / implement / debug), specificity (version,... | web-research-coding-5m-1.1.0 | |
6d9591e45569c34ad8215171 | train | documentation_experience | github | https://github.com/Ebazhanov/linkedin-skill-assessments-quizzes | Ebazhanov/linkedin-skill-assessments-quizzes | community | swift | graphql | Perform a deep developer-experience analysis for a swift project involving graphql. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Ebazhanov/linkedin-skill-assessments-quizzes", "source_url": "https://github.com/Ebazhanov/li... | === 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 | |
c3232a64519ca11f1ace865a | train | web_search_query | stackexchange | https://stackoverflow.com/questions/520650/make-an-existing-git-branch-track-a-remote-branch | Make an existing Git branch track a remote branch? | finance | ruby | machine_learning | Write an effective web search query to research the topic: machine_learning. | {"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... | === QUERY ===
machine_learning best practices documentation tutorial
=== INTENT ===
Find authoritative documentation, tutorials, and real-world examples related to the topic.
=== KEYWORDS ===
- machine_learning
- documentation
- best practices
- examples
- reference
=== SOURCE PREFERENCE ===
Prefer official document... | web-research-coding-5m-1.1.0 | |
6528d506b33393298efdefd4 | train | dashboard | web_docs | https://git-scm.com/doc | Git Documentation | dashboard | java | nlp | Design a production dashboard for nlp. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Git Documentation", "source_url": "https://git-scm.com/doc", "source_type": "documentation", ... | Include navigation, KPIs, tables/charts, filters, loading states, empty states, errors, and responsive behavior. | web-research-coding-5m-1.1.0 | |
591d5c09ff7804910ad728f3 | train | refactoring_architecture | gitlab | https://gitlab.com/malware-filter/tracking-filter | malware-filter/tracking-filter | dashboard | go | debugging | Refactor a go system related to debugging. Focus on refactoring architecture. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "malware-filter/tracking-filter", "source_url": "https://gitlab.com/malware-filter/tracking-fi... | === 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 | |
cca3b33392b0811b06180722 | train | maintainability_analysis | huggingface | https://huggingface.co/datasets/Weyaxi/huggingface-spaces-codes | Weyaxi/huggingface-spaces-codes | ecommerce | css | user_experience | Perform a deep multi-layer analysis of user_experience for a ecommerce 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": "Weyaxi/huggingface-spaces-codes", "source_url": "https://huggingface.co/datasets/Weyaxi/huggi... | === 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 'Weyaxi/huggingface-spaces-codes' as a source anchor and identify relevant APIs,... | web-research-coding-5m-1.1.0 | |
545a5ea0101a055fea2316c8 | train | testing_experience | huggingface | https://huggingface.co/datasets/hwaseem04/Documentation-files | hwaseem04/Documentation-files | search_interface | c | frontend | Perform a deep developer-experience analysis for a c project involving frontend. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "hwaseem04/Documentation-files", "source_url": "https://huggingface.co/datasets/hwaseem04/Docu... | === 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 | |
38874cf651efaa7cd1a33366 | train | root_cause_analysis | npm | https://www.npmjs.com/package/react | react | admin_panel | rust | backend | Perform a deep multi-layer analysis of backend for a admin_panel 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": "react", "source_url": "https://www.npmjs.com/package/react", "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 'react' as a source anchor and identify relevant APIs, dependencies, versions, standards, and te... | web-research-coding-5m-1.1.0 | |
e7420dddf81abc10f452b4f8 | train | refactoring_security | mdn | https://developer.mozilla.org/en-US/docs/Web/HTTP | HTTP | portfolio | typescript | distributed_systems | Refactor a typescript system related to distributed_systems. Focus on refactoring security. | {"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 ===
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 | |
e2a6cf0cebcb8013636e244c | train | fact_verification | codeberg | https://codeberg.org/saba2002/-my_simple_website..... | saba2002/-my_simple_website..... | ecommerce | sql | 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": "saba2002/-my_simple_website.....", "source_url": "https://codeberg.org/saba2002/-my_simple_we... | === 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 | |
af0d2c24ebfca4b0d0d8d335 | train | refactoring_readability | codeberg | https://codeberg.org/AjeshCasual/12DoF-Quadruped-Kinematics | AjeshCasual/12DoF-Quadruped-Kinematics | portfolio | ruby | react | Refactor a ruby system related to react. Focus on refactoring readability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "AjeshCasual/12DoF-Quadruped-Kinematics", "source_url": "https://codeberg.org/AjeshCasual/12Do... | === 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 | |
28ff867d9576bbd3ac46b051 | train | refactoring_readability | huggingface | https://huggingface.co/datasets/codeparrot/codeparrot-clean-valid | codeparrot/codeparrot-clean-valid | portfolio | swift | typescript | Refactor a swift system related to typescript. Focus on refactoring readability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "codeparrot/codeparrot-clean-valid", "source_url": "https://huggingface.co/datasets/codeparrot... | === 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 | |
49ad69f76c6d532f772818c7 | train | root_cause_analysis | huggingface | https://huggingface.co/datasets/dslighfdsl/humaneval_python | dslighfdsl/humaneval_python | saas | scala | docker | Perform a deep multi-layer analysis of docker for a saas 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": "dslighfdsl/humaneval_python", "source_url": "https://huggingface.co/datasets/dslighfdsl/human... | === 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 'dslighfdsl/humaneval_python' as a source anchor and identify relevant APIs, dependencies, version... | web-research-coding-5m-1.1.0 | |
2b2e53a5dacd0c1af0dc37e6 | train | code_explanation | huggingface | https://huggingface.co/datasets/BigScienceBiasEval/crows_pairs_multilingual | BigScienceBiasEval/crows_pairs_multilingual | documentation | scala | web_performance | Explain a scala implementation related to web_performance. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "BigScienceBiasEval/crows_pairs_multilingual", "source_url": "https://huggingface.co/datasets/... | Explain inputs, outputs, control flow, algorithms, complexity, edge cases, errors, and maintainability. | web-research-coding-5m-1.1.0 | |
f150beae4bdb36ac2b457081 | train | dashboard | pypi | https://pypi.org/project/transformers/ | transformers | ecommerce | go | typescript | Design a production dashboard for typescript. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "transformers", "source_url": "https://pypi.org/project/transformers/", "source_type": "packag... | Include navigation, KPIs, tables/charts, filters, loading states, empty states, errors, and responsive behavior. | 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.