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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
47addd84ba3b1d935fcb8d65 | test | performance_fix | huggingface | https://huggingface.co/datasets/livecodebench/code_generation_lite | livecodebench/code_generation_lite | developer_tool | shell | cloud | Create a web-performance optimization plan for a developer_tool. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "livecodebench/code_generation_lite", "source_url": "https://huggingface.co/datasets/livecodeb... | Measure first, then optimize bundle size, images, network requests, rendering, caching, and critical resources. | web-research-coding-5m-1.1.0 | |
7fa1040e30406c48eb5ac17a | test | form_ui | github | https://github.com/n8n-io/n8n | n8n-io/n8n | analytics | css | caching | Design an accessible form for caching. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "n8n-io/n8n", "source_url": "https://github.com/n8n-io/n8n", "source_type": "repository", "top... | Use labels, validation, clear errors, keyboard navigation, appropriate autocomplete, and accessible status messaging. | web-research-coding-5m-1.1.0 | |
f54100aa61e17d8180b540e8 | test | integration_testing | npm | https://www.npmjs.com/package/playwright | playwright | portfolio | c | frontend | Design integration tests for a c system involving frontend. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "playwright", "source_url": "https://www.npmjs.com/package/playwright", "source_type": "packag... | Test real component boundaries, persistence, configuration, external interfaces, errors, cleanup, and realistic workflows. | web-research-coding-5m-1.1.0 | |
ee2ae42d1ea138d78f7b5d93 | test | accessibility_analysis | stackexchange | https://stackoverflow.com/questions/1911109/how-do-i-clone-a-specific-git-branch | How do I clone a specific Git branch? | ecommerce | java | sql | Perform a deep multi-layer analysis of sql for a ecommerce using java. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How do I clone a specific Git branch?", "source_url": "https://stackoverflow.com/questions/19... | === 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 'How do I clone a specific Git branch?' as a source anchor and identify relevant APIs, dependencies, ver... | web-research-coding-5m-1.1.0 | |
3a1f4309878689d2faca2fd3 | test | maintainability_analysis | codeberg | https://codeberg.org/nilikk/-webshop.com | nilikk/-webshop.com | landing_page | kotlin | open_source | Perform a deep multi-layer analysis of open_source for a landing_page 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": "nilikk/-webshop.com", "source_url": "https://codeberg.org/nilikk/-webshop.com", "source_type"... | === 1. PROBLEM ===
Define the exact problem involving open_source. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around open_source. Use 'nilikk/-webshop.com' as a source anchor and identify relevant APIs, dependencies, versi... | web-research-coding-5m-1.1.0 | |
1a4baddbf4bd4fa3cba95e77 | test | refactoring_testability | gitlab | https://gitlab.com/nanuchi/python-programming | nanuchi/python-programming | education | shell | nodejs | Refactor a shell system related to nodejs. Focus on refactoring testability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "nanuchi/python-programming", "source_url": "https://gitlab.com/nanuchi/python-programming", "... | === 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 | |
fa380d14e6f791a1b57d6cdf | test | web_search_query | pypi | https://pypi.org/project/flask/ | flask | marketplace | kotlin | backend | Write an effective web search query to research the topic: backend. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "flask", "source_url": "https://pypi.org/project/flask/", "source_type": "package", "topic": "... | === QUERY ===
backend best practices documentation tutorial
=== INTENT ===
Find authoritative documentation, tutorials, and real-world examples related to the topic.
=== KEYWORDS ===
- backend
- documentation
- best practices
- examples
- reference
=== SOURCE PREFERENCE ===
Prefer official documentation, well-mainta... | web-research-coding-5m-1.1.0 | |
01535f180865039919aa8c64 | test | security_review | gitlab | https://gitlab.com/MrTREX/lineage2ts | MrTREX/lineage2ts | search_interface | go | cloud | Perform a security review of a search_interface application. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "MrTREX/lineage2ts", "source_url": "https://gitlab.com/MrTREX/lineage2ts", "source_type": "rep... | Review authentication, authorization, input validation, XSS, CSRF, injection risks, secrets, dependencies, security headers, and logging. | web-research-coding-5m-1.1.0 | |
1131076f2c3de2289e5aac7f | test | refactoring_modularization | huggingface | https://huggingface.co/datasets/joey234/mmlu-machine_learning | joey234/mmlu-machine_learning | marketplace | java | database | Refactor a java system related to database. Focus on refactoring modularization. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "joey234/mmlu-machine_learning", "source_url": "https://huggingface.co/datasets/joey234/mmlu-m... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Split large modules into cohesive units with explicit responsibilities.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify d... | web-research-coding-5m-1.1.0 | |
85bbeeac100695f7af4edd1c | test | product_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/Performance | Performance | developer_tool | scala | docker | Perform a deep multi-layer analysis of docker 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 docker. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around docker. Use 'Performance' as a source anchor and identify relevant APIs, dependencies, versions, standards, an... | web-research-coding-5m-1.1.0 | |
030c2546cca1bf9c47f0187c | test | repository_dependency_analysis | codeberg | https://codeberg.org/ccoenen/Advent-of-Code-2021-JavaScript | ccoenen/Advent-of-Code-2021-JavaScript | saas | swift | redis | Perform a deep multi-layer analysis of redis 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": "ccoenen/Advent-of-Code-2021-JavaScript", "source_url": "https://codeberg.org/ccoenen/Advent-o... | === 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 'ccoenen/Advent-of-Code-2021-JavaScript' as a source anchor and identify relevant APIs, dependencies... | web-research-coding-5m-1.1.0 | |
b8416488ecc9400124b89849 | test | typescript_generation | mdn | https://developer.mozilla.org/en-US/docs/Web/CSS | CSS | analytics | kotlin | docker | Implement TypeScript logic for a analytics. | {"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... | 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 |
aef6972b634abbbc7040e4ab | test | build_experience | huggingface | https://huggingface.co/datasets/Nan-Do/code-search-net-javascript | Nan-Do/code-search-net-javascript | developer_tool | css | developer_experience | Perform a deep developer-experience analysis for a css project involving developer_experience. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Nan-Do/code-search-net-javascript", "source_url": "https://huggingface.co/datasets/Nan-Do/cod... | === 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 | |
825c208bf1701755a09a17dc | test | repository_documentation | codeberg | https://codeberg.org/kawas44/2025-aoc-python | kawas44/2025-aoc-python | portfolio | kotlin | javascript | Perform a deep multi-layer analysis of javascript for a portfolio 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": "kawas44/2025-aoc-python", "source_url": "https://codeberg.org/kawas44/2025-aoc-python", "sour... | === 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 'kawas44/2025-aoc-python' as a source anchor and identify relevant APIs, dependencies, ver... | web-research-coding-5m-1.1.0 | |
1bf8e4c1e12d555160f050d7 | test | responsive_website | pypi | https://pypi.org/project/transformers/ | transformers | developer_tool | kotlin | css | Design a complete responsive developer_tool for css. | {"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... | Cover mobile, tablet, and desktop layouts, semantic structure, responsive components, accessibility, performance, and UX. | web-research-coding-5m-1.1.0 | |
05d875ce27ac0856e92c4ee9 | test | web_search_query | huggingface | https://huggingface.co/datasets/embedl/documentation-images | embedl/documentation-images | ecommerce | dart | observability | Write an effective web search query to research the topic: observability. | {"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... | === QUERY ===
observability best practices documentation tutorial
=== INTENT ===
Find authoritative documentation, tutorials, and real-world examples related to the topic.
=== KEYWORDS ===
- observability
- documentation
- best practices
- examples
- reference
=== SOURCE PREFERENCE ===
Prefer official documentation,... | web-research-coding-5m-1.1.0 | |
7a7ce5479dcd0a654a0c3a93 | test | testing_experience | codeberg | https://codeberg.org/VE3VVS/_cargo-index | VE3VVS/_cargo-index | admin_panel | go | nodejs | Perform a deep developer-experience analysis for a go project involving nodejs. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "VE3VVS/_cargo-index", "source_url": "https://codeberg.org/VE3VVS/_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 | |
a0d2ee251fe6914e4a50e55c | test | debugging | github | https://github.com/immich-app/immich | immich-app/immich | productivity | kotlin | data_engineering | Create a realistic kotlin debugging problem involving data_engineering. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "immich-app/immich", "source_url": "https://github.com/immich-app/immich", "source_type": "rep... | Provide symptoms, reproduction strategy, diagnostic steps, root-cause analysis, minimal fix, and regression coverage. | web-research-coding-5m-1.1.0 | |
eb77b997e396e1d74eb3e7ef | test | refactoring_scalability | github | https://github.com/ashishpatel26/500-AI-Machine-learning-Deep-learning-Computer-vision-NLP-Projects-with-code | ashishpatel26/500-AI-Machine-learning-Deep-learning-Computer-vision-NLP-Projects-with-code | portfolio | php | authorization | Refactor a php system related to authorization. Focus on refactoring scalability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "ashishpatel26/500-AI-Machine-learning-Deep-learning-Computer-vision-NLP-Projects-with-code", ... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Restructure the system to handle increased load without unnecessary complexity.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Id... | web-research-coding-5m-1.1.0 | |
6386c561df890f0f9763cbad | test | root_cause_analysis | gitlab | https://gitlab.com/fdroid/repomaker | fdroid/repomaker | productivity | swift | api_design | Perform a deep multi-layer analysis of api_design for a productivity 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": "fdroid/repomaker", "source_url": "https://gitlab.com/fdroid/repomaker", "source_type": "repos... | === 1. PROBLEM ===
Define the exact problem involving api_design. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around api_design. Use 'fdroid/repomaker' as a source anchor and identify relevant APIs, dependencies, versions, ... | web-research-coding-5m-1.1.0 | |
eae006f8f1a273d72e61db00 | test | api_developer_experience | gitlab | https://gitlab.com/cyber5k/mistborn | cyber5k/mistborn | saas | javascript | deep_learning | Perform a deep developer-experience analysis for a javascript project involving deep_learning. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "cyber5k/mistborn", "source_url": "https://gitlab.com/cyber5k/mistborn", "source_type": "repos... | === 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 | |
ff6547c26471c1dec1ba924c | test | debugging | stackexchange | https://stackoverflow.com/questions/1129216/sort-array-of-objects-by-string-property-value | Sort array of objects by string property value | analytics | typescript | redis | Create a realistic typescript debugging problem involving redis. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Sort array of objects by string property value", "source_url": "https://stackoverflow.com/que... | Provide symptoms, reproduction strategy, diagnostic steps, root-cause analysis, minimal fix, and regression coverage. | web-research-coding-5m-1.1.0 | |
220f5968ccc82c950bc69c01 | test | dependency_management_experience | web_docs | https://doc.rust-lang.org/ | Rust Documentation | ecommerce | typescript | javascript | Perform a deep developer-experience analysis for a typescript project involving javascript. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Rust Documentation", "source_url": "https://doc.rust-lang.org/", "source_type": "documentatio... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
45bb9af5c5076359e786768b | test | maintainability_analysis | huggingface | https://huggingface.co/datasets/semeru/code-text-javascript | semeru/code-text-javascript | productivity | python | caching | Perform a deep multi-layer analysis of caching for a productivity 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": "semeru/code-text-javascript", "source_url": "https://huggingface.co/datasets/semeru/code-text... | === 1. PROBLEM ===
Define the exact problem involving caching. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around caching. Use 'semeru/code-text-javascript' as a source anchor and identify relevant APIs, dependencies, versi... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
9ff21acee8746f3e9f6e5d9a | test | performance_analysis | github | https://github.com/fastapi/fastapi | fastapi/fastapi | saas | typescript | sql | Perform a deep multi-layer analysis of sql for a saas 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": "fastapi/fastapi", "source_url": "https://github.com/fastapi/fastapi", "source_type": "reposit... | === 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 'fastapi/fastapi' as a source anchor and identify relevant APIs, dependencies, versions, standards, and ... | web-research-coding-5m-1.1.0 | |
562287843090d65306062c58 | test | design_components | huggingface | https://huggingface.co/datasets/CohereLabs/wikipedia-2023-11-embed-multilingual-v3 | CohereLabs/wikipedia-2023-11-embed-multilingual-v3 | saas | c | kubernetes | Create a component architecture for a saas. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "CohereLabs/wikipedia-2023-11-embed-multilingual-v3", "source_url": "https://huggingface.co/da... | Define primitive components, composite components, variants, states, composition rules, and accessibility contracts. | web-research-coding-5m-1.1.0 | |
ab79ead00fb7e32390c8af74 | test | scalability_analysis | stackexchange | https://stackoverflow.com/questions/5767325/how-can-i-remove-a-specific-item-from-an-array-in-javascript | How can I remove a specific item from an array in JavaScript? | education | ruby | serverless | Perform a deep multi-layer analysis of serverless for a education 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": "How can I remove a specific item from an array in JavaScript?", "source_url": "https://stacko... | === 1. PROBLEM ===
Define the exact problem involving serverless. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around serverless. Use 'How can I remove a specific item from an array in JavaScript?' as a source anchor and ide... | web-research-coding-5m-1.1.0 | |
82c67edb65261ee7eae56b94 | test | testing_experience | huggingface | https://huggingface.co/datasets/Delcastillo8/machine_learning_project | Delcastillo8/machine_learning_project | marketplace | ruby | sql | Perform a deep developer-experience analysis for a ruby project involving sql. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Delcastillo8/machine_learning_project", "source_url": "https://huggingface.co/datasets/Delcas... | === 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 | |
2eb18da4c6907144ec08de09 | test | tradeoff_analysis | github | https://github.com/abi/screenshot-to-code | abi/screenshot-to-code | ecommerce | kotlin | caching | Perform a deep multi-layer analysis of caching for a ecommerce 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": "abi/screenshot-to-code", "source_url": "https://github.com/abi/screenshot-to-code", "source_t... | === 1. PROBLEM ===
Define the exact problem involving caching. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around caching. Use 'abi/screenshot-to-code' as a source anchor and identify relevant APIs, dependencies, versions, ... | web-research-coding-5m-1.1.0 | |
92bebd68dea05cf141410700 | test | react_generation | pypi | https://pypi.org/project/rich/ | rich | landing_page | swift | fullstack | Design React components for a landing_page. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "rich", "source_url": "https://pypi.org/project/rich/", "source_type": "package", "topic": "fu... | 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 |
95cf516add41acdf127a08e9 | test | design_review | github | https://github.com/scikit-learn/scikit-learn | scikit-learn/scikit-learn | search_interface | c | react | Perform a professional design review of a search_interface. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "scikit-learn/scikit-learn", "source_url": "https://github.com/scikit-learn/scikit-learn", "so... | Review hierarchy, consistency, responsiveness, accessibility, interaction design, content clarity, and implementation feasibility. | web-research-coding-5m-1.1.0 | |
405023a3e041d41e25348ad6 | test | repository_architecture | mdn | https://developer.mozilla.org/en-US/docs/Web/Accessibility | Accessibility | search_interface | rust | postgresql | Perform a deep multi-layer analysis of postgresql for a search_interface using rust. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Accessibility", "source_url": "https://developer.mozilla.org/en-US/docs/Web/Accessibility", "... | === 1. PROBLEM ===
Define the exact problem involving postgresql. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around postgresql. Use 'Accessibility' as a source anchor and identify relevant APIs, dependencies, versions, sta... | web-research-coding-5m-1.1.0 | |
4b380ada7fdd0765649da394 | test | unit_testing | gitlab | https://gitlab.com/q-dev/q-js-sdk | q-dev/q-js-sdk | admin_panel | ruby | fullstack | Create a unit-testing strategy for ruby code involving fullstack. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "q-dev/q-js-sdk", "source_url": "https://gitlab.com/q-dev/q-js-sdk", "source_type": "repositor... | Cover normal cases, edge cases, invalid inputs, failure modes, mocks, and regression tests. | web-research-coding-5m-1.1.0 | |
1ab93697c4007291d63b24b3 | test | fact_verification | stackexchange | https://stackoverflow.com/questions/5797852/how-do-i-include-functions-from-my-other-files | How do I "include" functions from my other files? | ecommerce | swift | 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": "How do I "include" functions from my other files?", "source_url": "https://stackove... | === 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 | |
aed5a29adfa52cc41d0801fc | test | visual_hierarchy | stackexchange | https://stackoverflow.com/questions/30950032/how-can-i-run-multiple-npm-scripts-in-parallel | How can I run multiple npm scripts in parallel? | saas | css | linux | Improve visual hierarchy in a saas. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How can I run multiple npm scripts in parallel?", "source_url": "https://stackoverflow.com/qu... | Use heading structure, typography, spacing, grouping, alignment, contrast, and consistent affordances. | web-research-coding-5m-1.1.0 | |
6a79eea614a3292ee4b6c8ab | test | search_intent_classification | web_docs | https://www.postgresql.org/docs/ | PostgreSQL Documentation | finance | c | algorithms | Classify the search intent for a query about algorithms. | {"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": "... | === POSSIBLE INTENTS ===
- informational (learn a concept)
- navigational (find a specific site/tool)
- transactional (install / download / run)
- troubleshooting (fix an error)
- comparative (choose between options)
=== EXAMPLE QUERY ===
"algorithms vs alternatives"
=== CLASSIFICATION ===
Comparative / informational... | web-research-coding-5m-1.1.0 | |
1c2e9f14fb34d8b31bdff0c7 | test | refactoring_security | mdn | https://developer.mozilla.org/en-US/docs/Web/API | Web APIs | productivity | dart | developer_experience | Refactor a dart system related to developer_experience. Focus on refactoring security. | {"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": "... | === 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 | |
089653d50ac892cfc2ed8f3c | test | scalability_analysis | web_docs | https://doc.rust-lang.org/ | Rust Documentation | portfolio | python | testing | Perform a deep multi-layer analysis of testing for a portfolio using python. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Rust Documentation", "source_url": "https://doc.rust-lang.org/", "source_type": "documentatio... | === 1. PROBLEM ===
Define the exact problem involving testing. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around testing. Use 'Rust Documentation' as a source anchor and identify relevant APIs, dependencies, versions, stan... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
ae322390f750b806a0a96ee9 | test | refactoring_dependency | huggingface | https://huggingface.co/datasets/GudduButt/schemaforge-machine-learning-research-13 | GudduButt/schemaforge-machine-learning-research-13 | landing_page | sql | graphql | Refactor a sql system related to graphql. Focus on refactoring dependency. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "GudduButt/schemaforge-machine-learning-research-13", "source_url": "https://huggingface.co/da... | === 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 | |
12cb4f43624bf48d7be028b0 | test | javascript_generation | pypi | https://pypi.org/project/rich/ | rich | documentation | dart | design_system | Implement JavaScript interactions for a documentation. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "rich", "source_url": "https://pypi.org/project/rich/", "source_type": "package", "topic": "de... | 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 |
f69f220b25c744eaf7d07de2 | test | landing_page | stackexchange | https://stackoverflow.com/questions/5064928/difference-between-classification-and-clustering-in-data-mining | Difference between classification and clustering in data mining? | marketplace | sql | data_engineering | Design a landing page for a data_engineering product. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Difference between classification and clustering in data mining?", "source_url": "https://sta... | Include hero, value proposition, features, CTA, FAQ, responsive behavior, SEO, accessibility, and analytics. | web-research-coding-5m-1.1.0 | |
ac4d34ba2dac1a6538b18c34 | test | repository_architecture | gitlab | https://gitlab.com/MrTREX/lineage2ts | MrTREX/lineage2ts | marketplace | dart | typescript | Perform a deep multi-layer analysis of typescript for a marketplace using dart. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "MrTREX/lineage2ts", "source_url": "https://gitlab.com/MrTREX/lineage2ts", "source_type": "rep... | === 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 'MrTREX/lineage2ts' as a source anchor and identify relevant APIs, dependencies, versions,... | web-research-coding-5m-1.1.0 | |
e7aabc173872f05074822d56 | test | ux_design | mdn | https://developer.mozilla.org/en-US/docs/Web/API | Web APIs | portfolio | sql | css | Design the complete UX flow of a portfolio for css. | {"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": "... | Map user goals, entry points, navigation, primary actions, feedback, loading states, empty states, errors, recovery paths, and completion. | web-research-coding-5m-1.1.0 | |
3780169df06f2fa97760387b | test | testing_experience | gitlab | https://gitlab.com/hsleisink/cauldron | hsleisink/cauldron | documentation | python | distributed_systems | Perform a deep developer-experience analysis for a python project involving distributed_systems. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "hsleisink/cauldron", "source_url": "https://gitlab.com/hsleisink/cauldron", "source_type": "r... | === 1. 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 |
0191be0a076b4f8edb9468f7 | test | documentation_lookup | huggingface | https://huggingface.co/datasets/RazinAleks/SO-Python_QA-Web_Development_class | RazinAleks/SO-Python_QA-Web_Development_class | saas | java | sql | Find and summarize the relevant documentation for sql. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "RazinAleks/SO-Python_QA-Web_Development_class", "source_url": "https://huggingface.co/dataset... | === RELEVANT DOCS ===
- RazinAleks/SO-Python_QA-Web_Development_class
https://huggingface.co/datasets/RazinAleks/SO-Python_QA-Web_Development_class
- Official project documentation
- API reference
=== KEY SECTIONS ===
- Getting started
- API reference
- Configuration
- Troubleshooting
=== SUMMARY ===
Summarize each... | web-research-coding-5m-1.1.0 | |
9277c3d462ed2716c62487cf | test | refactoring_performance | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API | Fetch API | admin_panel | shell | devops | Refactor a shell system related to devops. Focus on refactoring performance. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Fetch API", "source_url": "https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API", "sour... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
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 | |
2d3af2fa245af591e4f669c5 | test | repository_understanding | huggingface | https://huggingface.co/datasets/jamesdborin/Nemotron-Competitive-Programming-v1-prompt-only | jamesdborin/Nemotron-Competitive-Programming-v1-prompt-only | finance | swift | authentication | Perform a deep multi-layer analysis of authentication for a finance 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": "jamesdborin/Nemotron-Competitive-Programming-v1-prompt-only", "source_url": "https://huggingf... | === 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 'jamesdborin/Nemotron-Competitive-Programming-v1-prompt-only' as a source anchor a... | web-research-coding-5m-1.1.0 | |
7436a5dbc34077adde52eb41 | test | documentation_lookup | npm | https://www.npmjs.com/package/svelte | svelte | search_interface | scala | cloud | Find and summarize the relevant documentation for cloud. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "svelte", "source_url": "https://www.npmjs.com/package/svelte", "source_type": "package", "top... | === RELEVANT DOCS ===
- svelte
https://www.npmjs.com/package/svelte
- Official project documentation
- API reference
=== KEY SECTIONS ===
- Getting started
- API reference
- Configuration
- Troubleshooting
=== SUMMARY ===
Summarize each section in 1–3 sentences and quote exact signatures where relevant. | web-research-coding-5m-1.1.0 | |
b1641e865c730c62ac3ad908 | test | repository_documentation | pypi | https://pypi.org/project/pytest/ | pytest | education | css | distributed_systems | Perform a deep multi-layer analysis of distributed_systems for a education 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": "pytest", "source_url": "https://pypi.org/project/pytest/", "source_type": "package", "topic":... | === 1. PROBLEM ===
Define the exact problem involving distributed_systems. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around distributed_systems. Use 'pytest' as a source anchor and identify relevant APIs, dependencies, ve... | web-research-coding-5m-1.1.0 | |
c499642eb12146ff511e6bfc | test | css_generation | stackexchange | https://stackoverflow.com/questions/3040833/how-do-i-stash-only-one-file-out-of-multiple-files-that-have-changed | How do I stash only one file out of multiple files that have changed? | education | shell | nodejs | Create responsive CSS for a education. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How do I stash only one file out of multiple files that have changed?", "source_url": "https:... | Use reusable rules, responsive layouts, scalable typography, spacing, focus states, and mobile support. | :root {
--space: 1rem;
}
* {
box-sizing: border-box;
}
body {
margin: 0;
font-family: system-ui, sans-serif;
}
.container {
width: min(100% - 2rem, 1200px);
margin-inline: auto;
} | web-research-coding-5m-1.1.0 |
d241f31fbd1c68b96f1edffc | test | security_analysis | web_docs | https://docs.python.org/3/ | Python Documentation | landing_page | javascript | security | Perform a deep multi-layer analysis of security for a landing_page using javascript. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Python Documentation", "source_url": "https://docs.python.org/3/", "source_type": "documentat... | === 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 'Python Documentation' as a source anchor and identify relevant APIs, dependencies, versions, ... | web-research-coding-5m-1.1.0 | |
0b050788206ef08c19e73199 | test | integration_testing | npm | https://www.npmjs.com/package/axios | axios | analytics | typescript | javascript | Design integration tests for a typescript system involving javascript. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "axios", "source_url": "https://www.npmjs.com/package/axios", "source_type": "package", "topic... | Test real component boundaries, persistence, configuration, external interfaces, errors, cleanup, and realistic workflows. | web-research-coding-5m-1.1.0 | |
eb8ef4a767590ecfd7bbbaf1 | test | tradeoff_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/Accessibility | Accessibility | finance | css | linux | Perform a deep multi-layer analysis of linux for a finance 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": "Accessibility", "source_url": "https://developer.mozilla.org/en-US/docs/Web/Accessibility", "... | === 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 'Accessibility' as a source anchor and identify relevant APIs, dependencies, versions, standards, an... | web-research-coding-5m-1.1.0 | |
016a6fe6636569f48c117def | test | deployment_experience | stackexchange | https://stackoverflow.com/questions/28329382/understanding-unique-keys-for-array-children-in-react-js | Understanding unique keys for array children in React.js | admin_panel | sql | microservices | Perform a deep developer-experience analysis for a sql project involving microservices. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Understanding unique keys for array children in React.js", "source_url": "https://stackoverfl... | === 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 | |
2f152a24653b9627dc0c4f8f | test | refactoring_architecture | mdn | https://developer.mozilla.org/en-US/docs/Web/API | Web APIs | ecommerce | javascript | open_source | Refactor a javascript system related to open_source. Focus on refactoring architecture. | {"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": "... | === 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 | |
544a8fb69dacaab40c859290 | test | performance_fix | mdn | https://developer.mozilla.org/en-US/docs/Web/Accessibility | Accessibility | developer_tool | kotlin | cloud | Create a web-performance optimization plan for a developer_tool. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Accessibility", "source_url": "https://developer.mozilla.org/en-US/docs/Web/Accessibility", "... | Measure first, then optimize bundle size, images, network requests, rendering, caching, and critical resources. | web-research-coding-5m-1.1.0 | |
f94eb2f3fc48d5daf3fc51a5 | test | cli_experience | huggingface | https://huggingface.co/datasets/joey234/mmlu-machine_learning | joey234/mmlu-machine_learning | admin_panel | c | api_design | Perform a deep developer-experience analysis for a c project involving api_design. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "joey234/mmlu-machine_learning", "source_url": "https://huggingface.co/datasets/joey234/mmlu-m... | === 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 | |
e4669e88812d64f42ef591e8 | test | refactoring_scalability | pypi | https://pypi.org/project/typer/ | typer | productivity | sql | docker | Refactor a sql system related to docker. Focus on refactoring scalability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "typer", "source_url": "https://pypi.org/project/typer/", "source_type": "package", "topic": "... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
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 | |
2692e4afd4c08293623c6590 | test | refactoring_modularization | huggingface | https://huggingface.co/datasets/Ujjwal-Tyagi/JavaScript-Code-Large | Ujjwal-Tyagi/JavaScript-Code-Large | documentation | ruby | web_performance | Refactor a ruby system related to web_performance. Focus on refactoring modularization. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Ujjwal-Tyagi/JavaScript-Code-Large", "source_url": "https://huggingface.co/datasets/Ujjwal-Ty... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Split large modules into cohesive units with explicit responsibilities.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify d... | web-research-coding-5m-1.1.0 | |
7c1df9ea88b6f5ee078c87bb | test | refactoring_observability | huggingface | https://huggingface.co/datasets/jamesdborin/Nemotron-Competitive-Programming-v1-prompt-only | jamesdborin/Nemotron-Competitive-Programming-v1-prompt-only | blog | python | kubernetes | Refactor a python system related to kubernetes. Focus on refactoring observability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "jamesdborin/Nemotron-Competitive-Programming-v1-prompt-only", "source_url": "https://huggingf... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Improve logging, metrics, tracing, diagnostics, and failure visibility.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify d... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
8c1cd9f711f2563d719a4464 | test | dx_analysis | codeberg | https://codeberg.org/FloveDocs/4-PsicoSocial-FREE-TRUSTFUL-SOULS | FloveDocs/4-PsicoSocial-FREE-TRUSTFUL-SOULS | dashboard | typescript | kubernetes | Perform a deep developer-experience analysis for a typescript project involving kubernetes. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "FloveDocs/4-PsicoSocial-FREE-TRUSTFUL-SOULS", "source_url": "https://codeberg.org/FloveDocs/4... | === 1. 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 | |
065af02f73343e744a0e0732 | test | ux_analysis | huggingface | https://huggingface.co/datasets/WillHeld/paloma_programming_languages | WillHeld/paloma_programming_languages | dashboard | c | documentation | Perform a deep multi-layer analysis of documentation for a dashboard 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": "WillHeld/paloma_programming_languages", "source_url": "https://huggingface.co/datasets/WillHe... | === 1. PROBLEM ===
Define the exact problem involving documentation. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around documentation. Use 'WillHeld/paloma_programming_languages' as a source anchor and identify relevant API... | web-research-coding-5m-1.1.0 | |
aaf4ce3f26761de9e26f450f | test | source_selection | github | https://github.com/denoland/deno | denoland/deno | dashboard | typescript | developer_experience | Select the most reliable sources to research developer_experience. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "denoland/deno", "source_url": "https://github.com/denoland/deno", "source_type": "repository"... | === 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 | |
5e0be165a2d37fecbbb3b9b2 | test | refactoring_observability | stackexchange | https://stackoverflow.com/questions/5064928/difference-between-classification-and-clustering-in-data-mining | Difference between classification and clustering in data mining? | dashboard | php | docker | Refactor a php system related to docker. Focus on refactoring observability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Difference between classification and clustering in data mining?", "source_url": "https://sta... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Improve logging, metrics, tracing, diagnostics, and failure visibility.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify d... | web-research-coding-5m-1.1.0 | |
f3401cb41c2cd057c8eb6363 | test | evidence_extraction | npm | https://www.npmjs.com/package/eslint | eslint | dashboard | css | api_design | Extract verifiable evidence about api_design from the given source. | {"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... | === SOURCE ===
eslint
https://www.npmjs.com/package/eslint
=== EVIDENCE ITEMS ===
1. Explicit claims made by the source
2. Code examples or API signatures
3. Version / compatibility statements
4. Performance or security notes
=== QUALITY CHECK ===
- Is the claim specific and testable?
- Is the version and environment... | web-research-coding-5m-1.1.0 | |
735ed24cf3a6c6f30708311a | test | responsive_design | huggingface | https://huggingface.co/datasets/joey234/mmlu-machine_learning-verbal-neg-prepend | joey234/mmlu-machine_learning-verbal-neg-prepend | documentation | ruby | authentication | Create a responsive design strategy for a documentation. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "joey234/mmlu-machine_learning-verbal-neg-prepend", "source_url": "https://huggingface.co/data... | Define mobile, tablet, and desktop behavior, layout transitions, navigation, content priority, typography, and interaction targets. | web-research-coding-5m-1.1.0 | |
12f506ab47079b41f3498115 | test | performance_analysis | huggingface | https://huggingface.co/datasets/pruna-test/documentation-media | pruna-test/documentation-media | productivity | css | serverless | Perform a deep multi-layer analysis of serverless for a productivity 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": "pruna-test/documentation-media", "source_url": "https://huggingface.co/datasets/pruna-test/do... | === 1. PROBLEM ===
Define the exact problem involving serverless. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around serverless. Use 'pruna-test/documentation-media' as a source anchor and identify relevant APIs, dependenci... | web-research-coding-5m-1.1.0 | |
2bfb544a37e5b311f323631a | test | upgrade_experience | mdn | https://developer.mozilla.org/en-US/docs/Web/JavaScript | JavaScript | education | php | web_accessibility | Perform a deep developer-experience analysis for a php project involving web_accessibility. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "JavaScript", "source_url": "https://developer.mozilla.org/en-US/docs/Web/JavaScript", "source... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
59e6465ef5071d3aa225edb2 | test | fact_verification | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model | DOM | marketplace | java | javascript | Verify a technical claim about javascript. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "DOM", "source_url": "https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model",... | === CLAIM ===
A common claim about javascript.
=== VERIFICATION STEPS ===
1. Locate the primary source (docs, spec, RFC).
2. Reproduce the claim in a minimal environment.
3. Check version-specific behavior.
4. Identify edge cases and exceptions.
=== RESULT ===
Classify: confirmed / partially true / false / context-de... | web-research-coding-5m-1.1.0 | |
3f3fde7f38fd3d87eeb80a61 | test | refactoring_api | npm | https://www.npmjs.com/package/express | express | ecommerce | ruby | algorithms | Refactor a ruby system related to algorithms. Focus on refactoring api. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "express", "source_url": "https://www.npmjs.com/package/express", "source_type": "package", "t... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Improve API contracts, validation, error semantics, compatibility, and versioning.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4.... | web-research-coding-5m-1.1.0 | |
389c4693f5458a201563a75e | test | repository_comparison | huggingface | https://huggingface.co/datasets/rgismondi/code-fill-dataset | rgismondi/code-fill-dataset | ecommerce | ruby | redis | Perform a deep multi-layer analysis of redis for a ecommerce 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": "rgismondi/code-fill-dataset", "source_url": "https://huggingface.co/datasets/rgismondi/code-f... | === 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 'rgismondi/code-fill-dataset' as a source anchor and identify relevant APIs, dependencies, versions,... | web-research-coding-5m-1.1.0 | |
11cbc79d59dc7530635355d8 | test | algorithm_design | huggingface | https://huggingface.co/datasets/Ujjwal-Tyagi/JavaScript-Code-Large | Ujjwal-Tyagi/JavaScript-Code-Large | ecommerce | html | typescript | Design a html algorithm for a typescript problem. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Ujjwal-Tyagi/JavaScript-Code-Large", "source_url": "https://huggingface.co/datasets/Ujjwal-Ty... | State assumptions, algorithm, complexity, edge cases, correctness reasoning, and testing strategy. | web-research-coding-5m-1.1.0 | |
1f16bdef2816168c8c0698d0 | test | product_analysis | pypi | https://pypi.org/project/typer/ | typer | community | shell | rest_api | Perform a deep multi-layer analysis of rest_api for a community 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": "typer", "source_url": "https://pypi.org/project/typer/", "source_type": "package", "topic": "... | === 1. PROBLEM ===
Define the exact problem involving rest_api. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around rest_api. Use 'typer' as a source anchor and identify relevant APIs, dependencies, versions, standards, and ... | web-research-coding-5m-1.1.0 | |
c886749a859510111bfd3683 | test | repository_comparison | huggingface | https://huggingface.co/datasets/alphuuuu02/Machine-Learning-Credit-Card-Fraud-Detection-Project | alphuuuu02/Machine-Learning-Credit-Card-Fraud-Detection-Project | portfolio | javascript | software_architecture | Perform a deep multi-layer analysis of software_architecture for a portfolio using javascript. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "alphuuuu02/Machine-Learning-Credit-Card-Fraud-Detection-Project", "source_url": "https://hugg... | === 1. PROBLEM ===
Define the exact problem involving software_architecture. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around software_architecture. Use 'alphuuuu02/Machine-Learning-Credit-Card-Fraud-Detection-Project' as... | web-research-coding-5m-1.1.0 | |
e78689b0a56d8e4d6236af52 | test | refactoring_performance | web_docs | https://docs.djangoproject.com/ | Django Documentation | finance | ruby | web_performance | Refactor a ruby system related to web_performance. Focus on refactoring performance. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Django Documentation", "source_url": "https://docs.djangoproject.com/", "source_type": "docum... | === 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 | |
754974c18cdc4cac16e2771e | test | fact_verification | gitlab | https://gitlab.com/pymarc/pymarc | pymarc/pymarc | documentation | javascript | react | Verify a technical claim about react. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "pymarc/pymarc", "source_url": "https://gitlab.com/pymarc/pymarc", "source_type": "repository"... | === CLAIM ===
A common claim about react.
=== 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 | |
a14df5e06acf218ac5f3c441 | test | design_system | web_docs | https://doc.rust-lang.org/ | Rust Documentation | productivity | rust | computer_vision | Create a scalable design system for a productivity. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Rust Documentation", "source_url": "https://doc.rust-lang.org/", "source_type": "documentatio... | Define tokens, typography, spacing, components, variants, states, responsive rules, accessibility, and documentation. | web-research-coding-5m-1.1.0 | |
f72f5f5f0f06f167141fee66 | test | react_generation | stackexchange | https://stackoverflow.com/questions/133051/what-is-the-difference-between-visibilityhidden-and-displaynone | What is the difference between visibility:hidden and display:none? | education | python | nodejs | 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": "What is the difference between visibility:hidden and display:none?", "source_url": "https://s... | 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 |
65a0a4fd49247b6d383222ce | test | ux_analysis | gitlab | https://gitlab.com/gitlab-ci-utils/gitlab-semgrep-plus | gitlab-ci-utils/gitlab-semgrep-plus | saas | c | graphql | Perform a deep multi-layer analysis of graphql for a saas using c. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "gitlab-ci-utils/gitlab-semgrep-plus", "source_url": "https://gitlab.com/gitlab-ci-utils/gitla... | === 1. PROBLEM ===
Define the exact problem involving graphql. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around graphql. Use 'gitlab-ci-utils/gitlab-semgrep-plus' as a source anchor and identify relevant APIs, dependencie... | web-research-coding-5m-1.1.0 | |
9e5438c979081670a262ef16 | test | design_review | pypi | https://pypi.org/project/fastapi/ | fastapi | admin_panel | typescript | deep_learning | Perform a professional design review of a admin_panel. | {"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... | Review hierarchy, consistency, responsiveness, accessibility, interaction design, content clarity, and implementation feasibility. | web-research-coding-5m-1.1.0 | |
f9c78a891d6b277638ec2e1d | test | refactoring_readability | codeberg | https://codeberg.org/Scratch-Lee/_cargo-index | Scratch-Lee/_cargo-index | dashboard | cpp | microservices | Refactor a cpp system related to microservices. Focus on refactoring readability. | {"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... | === 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 | |
e55551228e95247c1d8dfa56 | test | react_generation | mdn | https://developer.mozilla.org/en-US/docs/Web/Performance | Performance | blog | python | graphql | Design React components for a blog. | {"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... | 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 |
740a6529c847da55fb6c5a1d | test | deployment_experience | stackexchange | https://stackoverflow.com/questions/47236963/no-provider-for-httpclient | No provider for HttpClient | developer_tool | cpp | user_experience | Perform a deep developer-experience analysis for a cpp project involving user_experience. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "No provider for HttpClient", "source_url": "https://stackoverflow.com/questions/47236963/no-p... | === 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 | |
c6176ecd6355d017c2dbea6f | test | debugging | stackexchange | https://stackoverflow.com/questions/178325/how-do-i-check-if-an-element-is-hidden-in-jquery | How do I check if an element is hidden in jQuery? | social_app | c | sql | Create a realistic c debugging problem involving sql. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How do I check if an element is hidden in jQuery?", "source_url": "https://stackoverflow.com/... | Provide symptoms, reproduction strategy, diagnostic steps, root-cause analysis, minimal fix, and regression coverage. | web-research-coding-5m-1.1.0 | |
f99ff133886447389b75d08b | test | refactoring_maintainability | mdn | https://developer.mozilla.org/en-US/docs/Web/API | Web APIs | social_app | c | serverless | Refactor a c system related to serverless. Focus on refactoring maintainability. | {"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": "... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Improve cohesion, reduce coupling, isolate volatile behavior, and remove duplication.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.... | web-research-coding-5m-1.1.0 | |
571195b9ed09c92d8f618cd4 | test | refactoring_security | gitlab | https://gitlab.com/The_Quantum_Alpha/the-quantum-ad-list | The_Quantum_Alpha/the-quantum-ad-list | analytics | ruby | linux | Refactor a ruby system related to linux. Focus on refactoring security. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "The_Quantum_Alpha/the-quantum-ad-list", "source_url": "https://gitlab.com/The_Quantum_Alpha/t... | === 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 | |
b0bbf7abfca488e0043b0bd6 | test | maintainability_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/CSS | CSS | blog | scala | database | Perform a deep multi-layer analysis of database 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": "CSS", "source_url": "https://developer.mozilla.org/en-US/docs/Web/CSS", "source_type": "docum... | === 1. PROBLEM ===
Define the exact problem involving database. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around database. Use 'CSS' as a source anchor and identify relevant APIs, dependencies, versions, standards, and te... | web-research-coding-5m-1.1.0 | |
2a92cd83eb26e2c92620f9dc | test | research_summary | gitlab | https://gitlab.com/b4ckup/ts-tex | b4ckup/ts-tex | community | typescript | sql | Summarize the current state of knowledge about sql. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "b4ckup/ts-tex", "source_url": "https://gitlab.com/b4ckup/ts-tex", "source_type": "repository"... | === OVERVIEW ===
sql 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 ===
b4ckup/ts-tex (https://git... | web-research-coding-5m-1.1.0 | |
f1f1fea6f3cefb24e7385a1a | test | technical_research | npm | https://www.npmjs.com/package/eslint | eslint | saas | ruby | kubernetes | Perform a technical research task about kubernetes, focused on implementation details. | {"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... | === SCOPE ===
Technical behavior of kubernetes.
=== QUESTIONS ===
- What are the inputs, outputs, and invariants?
- What are the performance characteristics?
- What are the security implications?
- What are the compatibility constraints?
=== EVIDENCE ===
- eslint (https://www.npmjs.com/package/eslint)
- Official docu... | web-research-coding-5m-1.1.0 | |
49e1f48873e710c0fcaa6b8b | test | design_components | npm | https://www.npmjs.com/package/express | express | search_interface | typescript | postgresql | Create a component architecture for a search_interface. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "express", "source_url": "https://www.npmjs.com/package/express", "source_type": "package", "t... | Define primitive components, composite components, variants, states, composition rules, and accessibility contracts. | web-research-coding-5m-1.1.0 | |
25a055fe0db5dcbde0633d3e | test | developer_experience | huggingface | https://huggingface.co/datasets/xszheng2020/the_stack_dedup_python | xszheng2020/the_stack_dedup_python | education | css | python | Perform a deep developer-experience analysis for a css project involving python. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "xszheng2020/the_stack_dedup_python", "source_url": "https://huggingface.co/datasets/xszheng20... | === 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 | |
aaa70c3cf839e0ed944d6743 | test | multi_hop_research | pypi | https://pypi.org/project/fastapi/ | fastapi | education | javascript | devops | Perform multi-hop research about devops: 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": "fastapi", "source_url": "https://pypi.org/project/fastapi/", "source_type": "package", "topic... | === HOP 1 ===
Start at: fastapi
https://pypi.org/project/fastapi/
Extract core claims and references.
=== HOP 2 ===
Follow references to official docs, RFCs, or specs.
Extract primary-source evidence.
=== HOP 3 ===
Check community discussions for real-world issues.
Extract failure modes and workarounds.
=== SYNTHESI... | web-research-coding-5m-1.1.0 | |
d41fb05be7755bd6a343040e | test | typescript_generation | stackexchange | https://stackoverflow.com/questions/339923/set-cellpadding-and-cellspacing-in-css | Set cellpadding and cellspacing in CSS? | search_interface | cpp | backend | Implement TypeScript logic for a search_interface. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Set cellpadding and cellspacing in CSS?", "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 |
42197c5008158697c3ee4248 | test | source_selection | codeberg | https://codeberg.org/saba2002/-my_simple_website..... | saba2002/-my_simple_website..... | ecommerce | sql | authorization | Select the most reliable sources to research authorization. | {"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... | === 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 | |
b965f73d3c5becd12d9f1231 | test | interaction_design | huggingface | https://huggingface.co/datasets/Programming-Language/codeagent-python | Programming-Language/codeagent-python | documentation | java | testing | Design interaction states for a documentation. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Programming-Language/codeagent-python", "source_url": "https://huggingface.co/datasets/Progra... | Specify default, hover, focus, active, disabled, loading, success, error, and empty states. | web-research-coding-5m-1.1.0 | |
fea7083adf7031b73bc50e0d | test | refactoring_modularization | stackexchange | https://stackoverflow.com/questions/29685421/hide-keyboard-in-react-native | Hide keyboard in react-native | productivity | cpp | docker | Refactor a cpp system related to docker. Focus on refactoring modularization. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Hide keyboard in react-native", "source_url": "https://stackoverflow.com/questions/29685421/h... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Split large modules into cohesive units with explicit responsibilities.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify d... | web-research-coding-5m-1.1.0 | |
dad23a76f1d122eab2a5d272 | test | root_cause_analysis | github | https://github.com/microsoft/ML-For-Beginners | microsoft/ML-For-Beginners | dashboard | cpp | fullstack | Perform a deep multi-layer analysis of fullstack for a dashboard 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": "microsoft/ML-For-Beginners", "source_url": "https://github.com/microsoft/ML-For-Beginners", "... | === 1. PROBLEM ===
Define the exact problem involving fullstack. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around fullstack. Use 'microsoft/ML-For-Beginners' as a source anchor and identify relevant APIs, dependencies, ve... | web-research-coding-5m-1.1.0 | |
34def14175ffad68e1f8aad4 | test | refactoring_legacy_code | huggingface | https://huggingface.co/datasets/SciCodePile/SciCode-Programming-Problems | SciCodePile/SciCode-Programming-Problems | saas | javascript | api_design | Refactor a javascript system related to api_design. Focus on refactoring legacy code. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "SciCodePile/SciCode-Programming-Problems", "source_url": "https://huggingface.co/datasets/Sci... | === 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 | |
115de335c3286f384a217f13 | test | accessibility_fix | pypi | https://pypi.org/project/pydantic/ | pydantic | admin_panel | html | software_architecture | Create an accessibility remediation plan for a admin_panel. | {"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... | Check semantic HTML, keyboard navigation, focus management, accessible names, labels, errors, contrast, and screen-reader behavior. | web-research-coding-5m-1.1.0 | |
b2f7041ede84c4c26289d0ab | test | tradeoff_analysis | huggingface | https://huggingface.co/datasets/GudduButt/schemaforge-ai-and-machine-learning-11 | GudduButt/schemaforge-ai-and-machine-learning-11 | productivity | java | css | Perform a deep multi-layer analysis of css 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": "GudduButt/schemaforge-ai-and-machine-learning-11", "source_url": "https://huggingface.co/data... | === 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 'GudduButt/schemaforge-ai-and-machine-learning-11' as a source anchor and identify relevant APIs, depend... | 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.