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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
350a458e3d5d2705b7654072 | test | refactoring_scalability | huggingface | https://huggingface.co/datasets/OLMo-Coding/starcoder-python-instruct | OLMo-Coding/starcoder-python-instruct | marketplace | rust | backend | Refactor a rust system related to backend. Focus on refactoring scalability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "OLMo-Coding/starcoder-python-instruct", "source_url": "https://huggingface.co/datasets/OLMo-C... | === 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 | |
a811eaef2edb66e16288f88d | test | search_intent_classification | github | https://github.com/josephmisiti/awesome-machine-learning | josephmisiti/awesome-machine-learning | portfolio | css | user_experience | Classify the search intent for a query about user_experience. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "josephmisiti/awesome-machine-learning", "source_url": "https://github.com/josephmisiti/awesom... | === 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 ===
"user_experience vs alternatives"
=== CLASSIFICATION ===
Comparative / informat... | web-research-coding-5m-1.1.0 | |
7ad98ef3e1bd8c4e7f144cc5 | test | maintainability_analysis | huggingface | https://huggingface.co/datasets/smohammadi/the-stack-v2-python-shuffle | smohammadi/the-stack-v2-python-shuffle | developer_tool | scala | user_experience | Perform a deep multi-layer analysis of user_experience 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": "smohammadi/the-stack-v2-python-shuffle", "source_url": "https://huggingface.co/datasets/smoha... | === 1. PROBLEM ===
Define the exact problem involving user_experience. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around user_experience. Use 'smohammadi/the-stack-v2-python-shuffle' as a source anchor and identify relevan... | web-research-coding-5m-1.1.0 | |
3ee85d36958f78a0ee9c80cc | test | refactoring_legacy_code | huggingface | https://huggingface.co/datasets/bharath-nuthalapati/Vulnerable_Programming_Dataset | bharath-nuthalapati/Vulnerable_Programming_Dataset | marketplace | cpp | data_structures | Refactor a cpp system related to data_structures. Focus on refactoring legacy code. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "bharath-nuthalapati/Vulnerable_Programming_Dataset", "source_url": "https://huggingface.co/da... | === 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 | |
07d18bb731ba957c353474e5 | test | performance_analysis | npm | https://www.npmjs.com/package/playwright | playwright | saas | sql | nlp | Perform a deep multi-layer analysis of nlp for a saas using sql. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "playwright", "source_url": "https://www.npmjs.com/package/playwright", "source_type": "packag... | === 1. PROBLEM ===
Define the exact problem involving nlp. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around nlp. Use 'playwright' as a source anchor and identify relevant APIs, dependencies, versions, standards, and techn... | web-research-coding-5m-1.1.0 | |
5feff31ee806a37737519e79 | test | documentation_page | gitlab | https://gitlab.com/gitlab-com/books-clubs/bookclub-hands-on-machine-learning | gitlab-com/books-clubs/bookclub-hands-on-machine-learning | productivity | scala | microservices | Design a developer documentation page for microservices. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "gitlab-com/books-clubs/bookclub-hands-on-machine-learning", "source_url": "https://gitlab.com... | Include navigation, overview, prerequisites, installation, examples, API reference, troubleshooting, and search. | web-research-coding-5m-1.1.0 | |
30233e1b3446e52a6f6c71e3 | test | evidence_chain_analysis | web_docs | https://go.dev/doc/ | Go Documentation | marketplace | java | mongodb | Perform a deep multi-layer analysis of mongodb for a marketplace using java. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Go Documentation", "source_url": "https://go.dev/doc/", "source_type": "documentation", "topi... | === 1. PROBLEM ===
Define the exact problem involving mongodb. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around mongodb. Use 'Go Documentation' as a source anchor and identify relevant APIs, dependencies, versions, standa... | web-research-coding-5m-1.1.0 | |
bb0ad828d5e0d9c5605e4506 | test | refactoring_dependency | gitlab | https://gitlab.com/inkscape/extensions | inkscape/extensions | saas | kotlin | html | Refactor a kotlin system related to html. Focus on refactoring dependency. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "inkscape/extensions", "source_url": "https://gitlab.com/inkscape/extensions", "source_type": ... | === 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 | |
5b270f9c6cde89a03d9886ff | test | performance_analysis | stackexchange | https://stackoverflow.com/questions/510348/how-do-i-make-a-time-delay | How do I make a time delay? | admin_panel | python | devops | Perform a deep multi-layer analysis of devops for a admin_panel using python. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How do I make a time delay?", "source_url": "https://stackoverflow.com/questions/510348/how-d... | === 1. PROBLEM ===
Define the exact problem involving devops. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around devops. Use 'How do I make a time delay?' as a source anchor and identify relevant APIs, dependencies, version... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
25ebd7fba12ad4e43218761a | test | algorithm_design | gitlab | https://gitlab.com/comentario/comentario | comentario/comentario | productivity | java | testing | Design a java algorithm for a testing problem. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "comentario/comentario", "source_url": "https://gitlab.com/comentario/comentario", "source_typ... | State assumptions, algorithm, complexity, edge cases, correctness reasoning, and testing strategy. | web-research-coding-5m-1.1.0 | |
ed1e512008a9121cb190c620 | test | algorithm_design | huggingface | https://huggingface.co/datasets/ByteDance-Seed/Code-Contests-Plus | ByteDance-Seed/Code-Contests-Plus | search_interface | python | nodejs | Design a python algorithm for a nodejs problem. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "ByteDance-Seed/Code-Contests-Plus", "source_url": "https://huggingface.co/datasets/ByteDance-... | State assumptions, algorithm, complexity, edge cases, correctness reasoning, and testing strategy. | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
ad35c810529366a197804ca3 | test | accessibility_analysis | stackexchange | https://stackoverflow.com/questions/2052390/manually-raising-throwing-an-exception-in-python | Manually raising (throwing) an exception in Python | education | cpp | nlp | Perform a deep multi-layer analysis of nlp for a education 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": "Manually raising (throwing) an exception in Python", "source_url": "https://stackoverflow.com... | === 1. PROBLEM ===
Define the exact problem involving nlp. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around nlp. Use 'Manually raising (throwing) an exception in Python' as a source anchor and identify relevant APIs, depe... | web-research-coding-5m-1.1.0 | |
cfd532b9c231840a332a478e | test | design_components | huggingface | https://huggingface.co/datasets/hxyscott/mathematical_programming_dataset | hxyscott/mathematical_programming_dataset | dashboard | java | microservices | Create a component architecture for a dashboard. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "hxyscott/mathematical_programming_dataset", "source_url": "https://huggingface.co/datasets/hx... | Define primitive components, composite components, variants, states, composition rules, and accessibility contracts. | web-research-coding-5m-1.1.0 | |
7c0e8fab6ae50ffa14845382 | test | design_tokens | pypi | https://pypi.org/project/numpy/ | numpy | blog | java | postgresql | Create design tokens for a blog. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "numpy", "source_url": "https://pypi.org/project/numpy/", "source_type": "package", "topic": "... | Define reusable tokens for typography, spacing, radii, sizing, elevation, interaction states, and responsive behavior. | web-research-coding-5m-1.1.0 | |
8329f5b803578b3cc6b9c5e0 | test | testing_experience | web_docs | https://go.dev/doc/ | Go Documentation | developer_tool | python | data_structures | Perform a deep developer-experience analysis for a python project involving data_structures. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Go Documentation", "source_url": "https://go.dev/doc/", "source_type": "documentation", "topi... | === 1. 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 |
4dd3eb1b12797728a9b03e69 | test | documentation_page | mdn | https://developer.mozilla.org/en-US/docs/Web/API | Web APIs | education | cpp | docker | Design a developer documentation page for docker. | {"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": "... | Include navigation, overview, prerequisites, installation, examples, API reference, troubleshooting, and search. | web-research-coding-5m-1.1.0 | |
42c1344c27bce94117f8d24f | test | interaction_design | codeberg | https://codeberg.org/Trevizer/_cargo-index | Trevizer/_cargo-index | blog | go | html | Design interaction states for a blog. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Trevizer/_cargo-index", "source_url": "https://codeberg.org/Trevizer/_cargo-index", "source_t... | Specify default, hover, focus, active, disabled, loading, success, error, and empty states. | web-research-coding-5m-1.1.0 | |
41cab6dee1ec7d543ca4add1 | test | responsive_design | npm | https://www.npmjs.com/package/fastify | fastify | community | swift | serverless | Create a responsive design strategy for a community. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "fastify", "source_url": "https://www.npmjs.com/package/fastify", "source_type": "package", "t... | Define mobile, tablet, and desktop behavior, layout transitions, navigation, content priority, typography, and interaction targets. | web-research-coding-5m-1.1.0 | |
e75b82e032bcb4236f9dd5bf | test | html_generation | web_docs | https://nodejs.org/docs/latest/api/ | Node.js Documentation | marketplace | sql | docker | Create semantic HTML for a marketplace about docker. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Node.js Documentation", "source_url": "https://nodejs.org/docs/latest/api/", "source_type": "... | Use semantic landmarks, headings, accessible controls, meaningful labels, and correct document structure. | <!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport"
content="width=device-width, initial-scale=1">
<title>Accessible Application</title>
</head>
<body>
<main>
<h1>Application</h1>
</main>
</body>
</html> | web-research-coding-5m-1.1.0 |
1858b81430f3badf0bdec009 | test | unit_testing | codeberg | https://codeberg.org/fionaredmond/01-Web-basics-and-git-FionaRedmond | fionaredmond/01-Web-basics-and-git-FionaRedmond | search_interface | dart | web_performance | Create a unit-testing strategy for dart code involving web_performance. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "fionaredmond/01-Web-basics-and-git-FionaRedmond", "source_url": "https://codeberg.org/fionare... | Cover normal cases, edge cases, invalid inputs, failure modes, mocks, and regression tests. | web-research-coding-5m-1.1.0 | |
c1fdf55c7fb8525548eaa9d8 | test | search_intent_classification | stackexchange | https://stackoverflow.com/questions/3577641/how-do-you-parse-and-process-html-xml-in-php | How do you parse and process HTML/XML in PHP? | portfolio | typescript | distributed_systems | Classify the search intent for a query about distributed_systems. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How do you parse and process HTML/XML in PHP?", "source_url": "https://stackoverflow.com/ques... | === 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 ===
"distributed_systems vs alternatives"
=== CLASSIFICATION ===
Comparative / info... | web-research-coding-5m-1.1.0 | |
16a023509bf99bd883bb9df3 | test | seo_fix | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model | DOM | productivity | cpp | frontend | Create an SEO improvement plan for a productivity about frontend. | {"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",... | Cover titles, descriptions, headings, canonical URLs, structured data, internal links, crawlability, and performance. | web-research-coding-5m-1.1.0 | |
926191565d2e300d9371dc3b | test | evidence_extraction | mdn | https://developer.mozilla.org/en-US/docs/Web/CSS | CSS | finance | c | sql | Extract verifiable evidence about sql from the given source. | {"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... | === SOURCE ===
CSS
https://developer.mozilla.org/en-US/docs/Web/CSS
=== 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 en... | web-research-coding-5m-1.1.0 | |
c2ec4143b1e8a6480e353685 | test | repository_documentation | huggingface | https://huggingface.co/datasets/averoo/sc_JavaScript | averoo/sc_JavaScript | documentation | typescript | graphql | Perform a deep multi-layer analysis of graphql for a documentation 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": "averoo/sc_JavaScript", "source_url": "https://huggingface.co/datasets/averoo/sc_JavaScript", ... | === 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 'averoo/sc_JavaScript' as a source anchor and identify relevant APIs, dependencies, versions, st... | web-research-coding-5m-1.1.0 | |
4910fce2c2d7f8f0a4e352d7 | test | multi_hop_research | stackexchange | https://stackoverflow.com/questions/20035101/why-does-my-javascript-code-receive-a-no-access-control-allow-origin-header-i | Why does my JavaScript code receive a "No 'Access-Control-Allow-Origin' header is present on the requested resource" error, while Postman does not? | portfolio | javascript | nextjs | Perform multi-hop research about nextjs: 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": "Why does my JavaScript code receive a "No 'Access-Control-Allow-Origin' header i... | === HOP 1 ===
Start at: Why does my JavaScript code receive a "No 'Access-Control-Allow-Origin' header is present on the requested resource" error, while Postman does not?
https://stackoverflow.com/questions/20035101/why-does-my-javascript-code-receive-a-no-access-control-allow-origin-header-i
Extract... | web-research-coding-5m-1.1.0 | |
77c349fe30a5a7075f63c42d | test | responsive_website | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model | DOM | marketplace | dart | graphql | Design a complete responsive marketplace for graphql. | {"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",... | Cover mobile, tablet, and desktop layouts, semantic structure, responsive components, accessibility, performance, and UX. | web-research-coding-5m-1.1.0 | |
c0d5c632ccaee572a63e773a | test | source_selection | web_docs | https://docs.python.org/3/ | Python Documentation | documentation | python | react | Select the most reliable sources to research react. | {"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... | === 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
=== ... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
548260cdfc58874f9556ffb5 | test | unit_testing | web_docs | https://www.typescriptlang.org/docs/ | TypeScript Documentation | documentation | css | debugging | Create a unit-testing strategy for css code involving debugging. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "TypeScript Documentation", "source_url": "https://www.typescriptlang.org/docs/", "source_type... | Cover normal cases, edge cases, invalid inputs, failure modes, mocks, and regression tests. | web-research-coding-5m-1.1.0 | |
140f3faf08eab2cb418426aa | test | root_cause_analysis | huggingface | https://huggingface.co/datasets/gretelai/synthetic_pii_finance_multilingual | gretelai/synthetic_pii_finance_multilingual | blog | go | developer_experience | Perform a deep multi-layer analysis of developer_experience for a blog using go. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "gretelai/synthetic_pii_finance_multilingual", "source_url": "https://huggingface.co/datasets/... | === 1. PROBLEM ===
Define the exact problem involving developer_experience. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around developer_experience. Use 'gretelai/synthetic_pii_finance_multilingual' as a source anchor and i... | web-research-coding-5m-1.1.0 | |
81c5cad60919d3c0584d3c22 | test | error_message_design | web_docs | https://git-scm.com/doc | Git Documentation | landing_page | ruby | linux | Perform a deep developer-experience analysis for a ruby project involving linux. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Git Documentation", "source_url": "https://git-scm.com/doc", "source_type": "documentation", ... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
4c2d421b5df790279982d8c7 | test | refactoring_maintainability | huggingface | https://huggingface.co/datasets/liangnanying/cifar-10-python | liangnanying/cifar-10-python | finance | ruby | deep_learning | Refactor a ruby system related to deep_learning. Focus on refactoring maintainability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "liangnanying/cifar-10-python", "source_url": "https://huggingface.co/datasets/liangnanying/ci... | === 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 | |
2f0a38c8918afd51f7cf5938 | test | visual_hierarchy | web_docs | https://go.dev/doc/ | Go Documentation | ecommerce | php | software_architecture | Improve visual hierarchy in a ecommerce. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Go Documentation", "source_url": "https://go.dev/doc/", "source_type": "documentation", "topi... | Use heading structure, typography, spacing, grouping, alignment, contrast, and consistent affordances. | web-research-coding-5m-1.1.0 | |
f3bc412ec14577cf474e472d | test | technical_research | stackexchange | https://stackoverflow.com/questions/9329446/loop-for-each-over-an-array-in-javascript | Loop (for each) over an array in JavaScript | analytics | swift | design_system | Perform a technical research task about design_system, focused on implementation details. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Loop (for each) over an array in JavaScript", "source_url": "https://stackoverflow.com/questi... | === SCOPE ===
Technical behavior of design_system.
=== QUESTIONS ===
- What are the inputs, outputs, and invariants?
- What are the performance characteristics?
- What are the security implications?
- What are the compatibility constraints?
=== EVIDENCE ===
- Loop (for each) over an array in JavaScript (https://stack... | web-research-coding-5m-1.1.0 | |
d5676a67d3989de030331d55 | test | debugging_experience | stackexchange | https://stackoverflow.com/questions/30571875/whats-the-difference-between-super-and-superprops-in-react-when-using-e | What's the difference between "super()" and "super(props)" in React when using es6 classes? | social_app | javascript | authentication | Perform a deep developer-experience analysis for a javascript project involving authentication. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "What's the difference between "super()" and "super(props)" in React w... | === 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 | |
9a98c81ebf37758ae38d8312 | test | refactoring_modularization | huggingface | https://huggingface.co/datasets/code-search-net/code_search_net | code-search-net/code_search_net | ecommerce | html | observability | Refactor a html system related to observability. Focus on refactoring modularization. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "code-search-net/code_search_net", "source_url": "https://huggingface.co/datasets/code-search-... | === 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 | |
c198563c65947005288d8acc | test | multi_hop_research | web_docs | https://git-scm.com/doc | Git Documentation | search_interface | html | sql | Perform multi-hop research about sql: 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": "Git Documentation", "source_url": "https://git-scm.com/doc", "source_type": "documentation", ... | === HOP 1 ===
Start at: Git Documentation
https://git-scm.com/doc
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 | |
e80af2a26f3ccbfab9cae426 | test | typescript_generation | web_docs | https://react.dev/ | React Documentation | productivity | css | caching | Implement TypeScript logic for a productivity. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "React Documentation", "source_url": "https://react.dev/", "source_type": "documentation", "to... | 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 |
e1aff7a702004dcf88187e5b | test | search_query_rewrite | web_docs | https://nodejs.org/docs/latest/api/ | Node.js Documentation | dashboard | sql | testing | Rewrite and improve a vague search query about testing into a precise, high-signal query. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Node.js Documentation", "source_url": "https://nodejs.org/docs/latest/api/", "source_type": "... | === ORIGINAL (VAGUE) ===
how to do testing
=== REWRITTEN QUERIES ===
1. testing official documentation guide
2. testing production best practices 2025
3. testing common pitfalls and solutions
4. testing architecture patterns with examples
=== RATIONALE ===
Add intent (learn / implement / debug), specificity (version,... | web-research-coding-5m-1.1.0 | |
916c18a86b11884ac21e6481 | test | refactoring_maintainability | stackexchange | https://stackoverflow.com/questions/1720421/how-do-i-concatenate-two-lists-in-python | How do I concatenate two lists in Python? | dashboard | rust | user_experience | Refactor a rust system related to user_experience. Focus on refactoring maintainability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How do I concatenate two lists in Python?", "source_url": "https://stackoverflow.com/question... | === 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 | |
c23c3975c71d834db9474c42 | test | dashboard | stackexchange | https://stackoverflow.com/questions/5062614/how-to-decide-when-to-use-node-js | How to decide when to use Node.js? | saas | kotlin | developer_experience | Design a production dashboard for developer_experience. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How to decide when to use Node.js?", "source_url": "https://stackoverflow.com/questions/50626... | Include navigation, KPIs, tables/charts, filters, loading states, empty states, errors, and responsive behavior. | web-research-coding-5m-1.1.0 | |
2aebbd9c5d5b3714f12a6bdf | test | responsive_design | huggingface | https://huggingface.co/datasets/code-rag-bench/library-documentation | code-rag-bench/library-documentation | blog | go | nlp | Create a responsive design strategy for a blog. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "code-rag-bench/library-documentation", "source_url": "https://huggingface.co/datasets/code-ra... | Define mobile, tablet, and desktop behavior, layout transitions, navigation, content priority, typography, and interaction targets. | web-research-coding-5m-1.1.0 | |
df81d597e409633aed072fc1 | test | web_search_query | web_docs | https://www.postgresql.org/docs/ | PostgreSQL Documentation | landing_page | scala | redis | Write an effective web search query to research the topic: redis. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "PostgreSQL Documentation", "source_url": "https://www.postgresql.org/docs/", "source_type": "... | === QUERY ===
redis best practices documentation tutorial
=== INTENT ===
Find authoritative documentation, tutorials, and real-world examples related to the topic.
=== KEYWORDS ===
- redis
- documentation
- best practices
- examples
- reference
=== SOURCE PREFERENCE ===
Prefer official documentation, well-maintained... | web-research-coding-5m-1.1.0 | |
d79585efde354a2a877b5970 | test | ux_analysis | npm | https://www.npmjs.com/package/axios | axios | portfolio | shell | authentication | Perform a deep multi-layer analysis of authentication for a portfolio using shell. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "axios", "source_url": "https://www.npmjs.com/package/axios", "source_type": "package", "topic... | === 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 'axios' as a source anchor and identify relevant APIs, dependencies, versions, sta... | web-research-coding-5m-1.1.0 | |
fa8fd86d4cffe321a11c64e8 | test | local_development_experience | stackexchange | https://stackoverflow.com/questions/9339429/what-does-cherry-picking-a-commit-with-git-mean | What does cherry-picking a commit with Git mean? | documentation | c | rest_api | Perform a deep developer-experience analysis for a c project involving rest_api. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "What does cherry-picking a commit with Git mean?", "source_url": "https://stackoverflow.com/q... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
405c2849b2c0e48e8a534d2c | test | scalability_analysis | web_docs | https://kubernetes.io/docs/ | Kubernetes Documentation | admin_panel | php | cloud | Perform a deep multi-layer analysis of cloud for a admin_panel using php. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Kubernetes Documentation", "source_url": "https://kubernetes.io/docs/", "source_type": "docum... | === 1. PROBLEM ===
Define the exact problem involving cloud. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around cloud. Use 'Kubernetes Documentation' as a source anchor and identify relevant APIs, dependencies, versions, st... | web-research-coding-5m-1.1.0 | |
9f13eebcbf1e4896fe971585 | test | refactoring_performance | huggingface | https://huggingface.co/datasets/joey234/mmlu-machine_learning-neg-prepend-fix | joey234/mmlu-machine_learning-neg-prepend-fix | education | kotlin | data_engineering | Refactor a kotlin system related to data_engineering. Focus on refactoring performance. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "joey234/mmlu-machine_learning-neg-prepend-fix", "source_url": "https://huggingface.co/dataset... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Reduce unnecessary computation, allocations, I/O, and network requests.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify d... | web-research-coding-5m-1.1.0 | |
c04e3e9a69ec0402b2641c69 | test | refactoring_maintainability | codeberg | https://codeberg.org/belim_faux/3D-Tetris | belim_faux/3D-Tetris | admin_panel | cpp | rest_api | Refactor a cpp system related to rest_api. Focus on refactoring maintainability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "belim_faux/3D-Tetris", "source_url": "https://codeberg.org/belim_faux/3D-Tetris", "source_typ... | === 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 | |
61fdf5c9ec5826f710696bf6 | test | dependency_impact_analysis | codeberg | https://codeberg.org/cosmicbottle/100-Days-Of-Python-Stuff | cosmicbottle/100-Days-Of-Python-Stuff | finance | cpp | web_accessibility | Perform a deep multi-layer analysis of web_accessibility for a finance 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": "cosmicbottle/100-Days-Of-Python-Stuff", "source_url": "https://codeberg.org/cosmicbottle/100-... | === 1. PROBLEM ===
Define the exact problem involving web_accessibility. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around web_accessibility. Use 'cosmicbottle/100-Days-Of-Python-Stuff' as a source anchor and identify rele... | web-research-coding-5m-1.1.0 | |
a406e99caea59e2c7d056043 | test | design_components | npm | https://www.npmjs.com/package/vue | vue | dashboard | ruby | algorithms | Create a component architecture for a dashboard. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "vue", "source_url": "https://www.npmjs.com/package/vue", "source_type": "package", "topic": "... | Define primitive components, composite components, variants, states, composition rules, and accessibility contracts. | web-research-coding-5m-1.1.0 | |
1dee2d9c4168e1ae181dfd8e | test | refactoring_readability | mdn | https://developer.mozilla.org/en-US/docs/Web/API | Web APIs | finance | css | docker | Refactor a css system related to docker. Focus on refactoring readability. | {"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 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 | |
2f3fdd9dbdbefb87a09c7324 | test | debugging_experience | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model | DOM | community | ruby | api_design | Perform a deep developer-experience analysis for a ruby project involving api_design. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "DOM", "source_url": "https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model",... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
036c1901a79b023ab062a1cc | test | system_analysis | huggingface | https://huggingface.co/datasets/livecodebench/code_generation | livecodebench/code_generation | admin_panel | javascript | rest_api | Perform a deep multi-layer analysis of rest_api for a admin_panel using javascript. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "livecodebench/code_generation", "source_url": "https://huggingface.co/datasets/livecodebench/... | === 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 'livecodebench/code_generation' as a source anchor and identify relevant APIs, dependencies, v... | web-research-coding-5m-1.1.0 | |
e78df67c98deee4710ffc357 | test | design_system | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model | DOM | education | shell | web_performance | Create a scalable design system for a education. | {"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",... | Define tokens, typography, spacing, components, variants, states, responsive rules, accessibility, and documentation. | web-research-coding-5m-1.1.0 | |
7ca4378f1b8c8e3cbb123bc4 | test | build_experience | mdn | https://developer.mozilla.org/en-US/docs/Web/HTML | HTML | saas | rust | web_performance | Perform a deep developer-experience analysis for a rust project involving web_performance. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "HTML", "source_url": "https://developer.mozilla.org/en-US/docs/Web/HTML", "source_type": "doc... | === 1. 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 | |
532ab6daaabd0170cc6cd575 | test | html_generation | gitlab | https://gitlab.com/nfriend/tree-online | nfriend/tree-online | dashboard | swift | nextjs | Create semantic HTML for a dashboard about nextjs. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "nfriend/tree-online", "source_url": "https://gitlab.com/nfriend/tree-online", "source_type": ... | Use semantic landmarks, headings, accessible controls, meaningful labels, and correct document structure. | <!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport"
content="width=device-width, initial-scale=1">
<title>Accessible Application</title>
</head>
<body>
<main>
<h1>Application</h1>
</main>
</body>
</html> | web-research-coding-5m-1.1.0 |
fa9b5dc309e74c3a11a883b3 | test | testing_experience | github | https://github.com/realworld-apps/realworld | realworld-apps/realworld | social_app | php | devops | Perform a deep developer-experience analysis for a php project involving devops. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "realworld-apps/realworld", "source_url": "https://github.com/realworld-apps/realworld", "sour... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
33e15b69fba1e8e080023ff0 | test | upgrade_experience | huggingface | https://huggingface.co/datasets/Nishant2414/OCR-Synthetic-Multilingual-v1 | Nishant2414/OCR-Synthetic-Multilingual-v1 | finance | html | devops | Perform a deep developer-experience analysis for a html project involving devops. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Nishant2414/OCR-Synthetic-Multilingual-v1", "source_url": "https://huggingface.co/datasets/Ni... | === 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 | |
0721119a3e92f7deb9982d13 | test | multi_layer_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model | DOM | documentation | php | typescript | Perform a deep multi-layer analysis of typescript for a documentation using php. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "DOM", "source_url": "https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model",... | === 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 'DOM' as a source anchor and identify relevant APIs, dependencies, versions, standards, an... | web-research-coding-5m-1.1.0 | |
77fad10597df7966ad65982b | test | multi_hop_research | huggingface | https://huggingface.co/datasets/Nan-Do/code-search-net-python | Nan-Do/code-search-net-python | analytics | python | algorithms | Perform multi-hop research about algorithms: 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": "Nan-Do/code-search-net-python", "source_url": "https://huggingface.co/datasets/Nan-Do/code-se... | === HOP 1 ===
Start at: Nan-Do/code-search-net-python
https://huggingface.co/datasets/Nan-Do/code-search-net-python
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.
Ex... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
6cf8f727fbe8fcb69aa6a7a7 | test | deployment_experience | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API | Fetch API | dashboard | python | data_engineering | Perform a deep developer-experience analysis for a python project involving data_engineering. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Fetch API", "source_url": "https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API", "sour... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
2fdb5db71b70d6e88d044caf | test | repository_architecture | huggingface | https://huggingface.co/datasets/learning-machine-inc/musr-cot-opus5 | learning-machine-inc/musr-cot-opus5 | saas | swift | software_architecture | Perform a deep multi-layer analysis of software_architecture 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": "learning-machine-inc/musr-cot-opus5", "source_url": "https://huggingface.co/datasets/learning... | === 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 'learning-machine-inc/musr-cot-opus5' as a source anchor and identif... | web-research-coding-5m-1.1.0 | |
608b63ae45d74b09a564c71b | test | visual_hierarchy | github | https://github.com/expo/expo | expo/expo | saas | go | observability | 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": "expo/expo", "source_url": "https://github.com/expo/expo", "source_type": "repository", "topic... | Use heading structure, typography, spacing, grouping, alignment, contrast, and consistent affordances. | web-research-coding-5m-1.1.0 | |
6a8079f0918eaa3e51394a53 | test | typescript_generation | stackexchange | https://stackoverflow.com/questions/47012169/a-component-is-changing-an-uncontrolled-input-of-type-text-to-be-controlled-erro | A component is changing an uncontrolled input of type text to be controlled error in ReactJS | search_interface | scala | api_design | 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": "A component is changing an uncontrolled input of type text to be controlled error in ReactJS"... | 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 |
dbae8f198fa17700ac53bd28 | test | repository_documentation | huggingface | https://huggingface.co/datasets/HaomingSong/lerobot-documentation-images | HaomingSong/lerobot-documentation-images | education | sql | developer_experience | Perform a deep multi-layer analysis of developer_experience for a education using sql. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "HaomingSong/lerobot-documentation-images", "source_url": "https://huggingface.co/datasets/Hao... | === 1. PROBLEM ===
Define the exact problem involving developer_experience. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around developer_experience. Use 'HaomingSong/lerobot-documentation-images' as a source anchor and iden... | web-research-coding-5m-1.1.0 | |
2583d9129127874197b96ddd | test | refactoring_maintainability | stackexchange | https://stackoverflow.com/questions/986006/how-do-i-pass-a-variable-by-reference | How do I pass a variable by reference? | dashboard | typescript | data_engineering | Refactor a typescript system related to data_engineering. Focus on refactoring maintainability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How do I pass a variable by reference?", "source_url": "https://stackoverflow.com/questions/9... | === 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 | |
591e84c6953a532e49777bac | test | deep_technical_analysis | npm | https://www.npmjs.com/package/rollup | rollup | social_app | go | sql | Perform a deep multi-layer analysis of sql for a social_app using go. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "rollup", "source_url": "https://www.npmjs.com/package/rollup", "source_type": "package", "top... | === 1. PROBLEM ===
Define the exact problem involving sql. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around sql. Use 'rollup' as a source anchor and identify relevant APIs, dependencies, versions, standards, and technical... | web-research-coding-5m-1.1.0 | |
7969fa416b47bc67b7895656 | test | javascript_generation | mdn | https://developer.mozilla.org/en-US/docs/Web/Performance | Performance | dashboard | shell | debugging | Implement JavaScript interactions for a dashboard. | {"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... | 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 |
c3aad913ed72a4ea088fc242 | test | maintainability_analysis | huggingface | https://huggingface.co/datasets/Lots-of-LoRAs/task718_mmmlu_answer_generation_machine_learning | Lots-of-LoRAs/task718_mmmlu_answer_generation_machine_learning | documentation | shell | html | Perform a deep multi-layer analysis of html for a documentation using shell. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Lots-of-LoRAs/task718_mmmlu_answer_generation_machine_learning", "source_url": "https://huggi... | === 1. PROBLEM ===
Define the exact problem involving html. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around html. Use 'Lots-of-LoRAs/task718_mmmlu_answer_generation_machine_learning' as a source anchor and identify relev... | web-research-coding-5m-1.1.0 | |
177bf502f28346d2d07ad742 | test | debugging | web_docs | https://docs.djangoproject.com/ | Django Documentation | social_app | rust | react | Create a realistic rust debugging problem involving react. | {"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... | Provide symptoms, reproduction strategy, diagnostic steps, root-cause analysis, minimal fix, and regression coverage. | web-research-coding-5m-1.1.0 | |
c9c5af6b9daa0dae34ba4764 | test | form_ui | codeberg | https://codeberg.org/UI-Programming-23-24/01-Web-basics-and-git-Freya-Prananta | UI-Programming-23-24/01-Web-basics-and-git-Freya-Prananta | ecommerce | html | docker | Design an accessible form for docker. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "UI-Programming-23-24/01-Web-basics-and-git-Freya-Prananta", "source_url": "https://codeberg.o... | Use labels, validation, clear errors, keyboard navigation, appropriate autocomplete, and accessible status messaging. | web-research-coding-5m-1.1.0 | |
9b2796446c4b1805b6ccc299 | test | multi_hop_research | huggingface | https://huggingface.co/datasets/learning-machine-inc/mmlu-pro-cot-opus5 | learning-machine-inc/mmlu-pro-cot-opus5 | documentation | c | developer_experience | Perform multi-hop research about developer_experience: 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": "learning-machine-inc/mmlu-pro-cot-opus5", "source_url": "https://huggingface.co/datasets/lear... | === HOP 1 ===
Start at: learning-machine-inc/mmlu-pro-cot-opus5
https://huggingface.co/datasets/learning-machine-inc/mmlu-pro-cot-opus5
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 r... | web-research-coding-5m-1.1.0 | |
dcf2b87ec68fa8ab98eabd92 | test | code_explanation | huggingface | https://huggingface.co/datasets/rl-rag/hle-gpt-oss-120b-no-python-260222 | rl-rag/hle-gpt-oss-120b-no-python-260222 | search_interface | ruby | web_accessibility | Explain a ruby implementation related to web_accessibility. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "rl-rag/hle-gpt-oss-120b-no-python-260222", "source_url": "https://huggingface.co/datasets/rl-... | Explain inputs, outputs, control flow, algorithms, complexity, edge cases, errors, and maintainability. | web-research-coding-5m-1.1.0 | |
df98df7837f8b62b54b496a8 | test | refactoring_maintainability | gitlab | https://gitlab.com/knotteye/satyr | knotteye/satyr | developer_tool | kotlin | database | Refactor a kotlin system related to database. Focus on refactoring maintainability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "knotteye/satyr", "source_url": "https://gitlab.com/knotteye/satyr", "source_type": "repositor... | === 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 | |
04f6a89122af546156e6e873 | test | research_summary | huggingface | https://huggingface.co/datasets/BAAI/IndustryCorpus2_computer_programming_code | BAAI/IndustryCorpus2_computer_programming_code | dashboard | typescript | distributed_systems | Summarize the current state of knowledge about distributed_systems. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "BAAI/IndustryCorpus2_computer_programming_code", "source_url": "https://huggingface.co/datase... | === OVERVIEW ===
distributed_systems 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 ===
BAAI/Indus... | web-research-coding-5m-1.1.0 | |
1e57105b304c2fd7642d448c | test | html_generation | gitlab | https://gitlab.com/snowball-dev-group/snowball-bot | snowball-dev-group/snowball-bot | education | sql | security | Create semantic HTML for a education about security. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "snowball-dev-group/snowball-bot", "source_url": "https://gitlab.com/snowball-dev-group/snowba... | Use semantic landmarks, headings, accessible controls, meaningful labels, and correct document structure. | <!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport"
content="width=device-width, initial-scale=1">
<title>Accessible Application</title>
</head>
<body>
<main>
<h1>Application</h1>
</main>
</body>
</html> | web-research-coding-5m-1.1.0 |
d47d1eb86b09023adc93199a | test | typescript_generation | github | https://github.com/ionic-team/ionic-framework | ionic-team/ionic-framework | documentation | cpp | testing | Implement TypeScript logic for a documentation. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "ionic-team/ionic-framework", "source_url": "https://github.com/ionic-team/ionic-framework", "... | 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 |
bb5b01b0fa65711d01326a57 | test | repository_documentation | huggingface | https://huggingface.co/datasets/puttatidam/software-documentation-tha-bitextmining | puttatidam/software-documentation-tha-bitextmining | productivity | c | web_performance | Perform a deep multi-layer analysis of web_performance for a productivity 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": "puttatidam/software-documentation-tha-bitextmining", "source_url": "https://huggingface.co/da... | === 1. PROBLEM ===
Define the exact problem involving web_performance. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around web_performance. Use 'puttatidam/software-documentation-tha-bitextmining' as a source anchor and iden... | web-research-coding-5m-1.1.0 | |
70967c2e2335f0062f4a7245 | test | upgrade_experience | pypi | https://pypi.org/project/beautifulsoup4/ | beautifulsoup4 | education | sql | rest_api | Perform a deep developer-experience analysis for a sql project involving rest_api. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "beautifulsoup4", "source_url": "https://pypi.org/project/beautifulsoup4/", "source_type": "pa... | === 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 | |
dc06d7d4cd379de60c0bbdad | test | refactoring_readability | stackexchange | https://stackoverflow.com/questions/37987839/how-can-i-run-tensorboard-on-a-remote-server | How can I run Tensorboard on a remote server? | dashboard | ruby | docker | Refactor a ruby system related to docker. Focus on refactoring readability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How can I run Tensorboard on a remote server?", "source_url": "https://stackoverflow.com/ques... | === 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 | |
e18354b92c8b618983bb6319 | test | repository_comparison | stackexchange | https://stackoverflow.com/questions/4114095/how-do-i-revert-a-git-repository-to-a-previous-commit | How do I revert a Git repository to a previous commit? | dashboard | scala | distributed_systems | Perform a deep multi-layer analysis of distributed_systems for a dashboard using scala. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How do I revert a Git repository to a previous commit?", "source_url": "https://stackoverflow... | === 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 'How do I revert a Git repository to a previous commit?' as a source anc... | web-research-coding-5m-1.1.0 | |
d5c3d78d25cb6ce10c496ce1 | test | refactoring_api | web_docs | https://docs.djangoproject.com/ | Django Documentation | saas | java | open_source | Refactor a java system related to open_source. Focus on refactoring api. | {"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 ===
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 | |
2d771f417f5d6518e3248325 | test | refactoring_architecture | gitlab | https://gitlab.com/smolpxl/smolpxl | smolpxl/smolpxl | admin_panel | scala | software_architecture | Refactor a scala system related to software_architecture. Focus on refactoring architecture. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "smolpxl/smolpxl", "source_url": "https://gitlab.com/smolpxl/smolpxl", "source_type": "reposit... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Redesign module boundaries and reduce architectural coupling.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify developer-e... | web-research-coding-5m-1.1.0 | |
20e386f44f54c4080864fa80 | test | repository_documentation | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API | Fetch API | social_app | cpp | security | Perform a deep multi-layer analysis of security for a social_app 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": "Fetch API", "source_url": "https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API", "sour... | === 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 'Fetch API' as a source anchor and identify relevant APIs, dependencies, versions, standards, ... | web-research-coding-5m-1.1.0 | |
0de3d553def6df7040b54fce | test | ui_design | gitlab | https://gitlab.com/pygolo/py | pygolo/py | documentation | kotlin | serverless | Design a production-quality UI for a documentation focused on serverless. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "pygolo/py", "source_url": "https://gitlab.com/pygolo/py", "source_type": "repository", "topic... | Define layout, typography, spacing, hierarchy, components, states, responsive behavior, and accessibility. | web-research-coding-5m-1.1.0 | |
1ec37d8894e0cd9badd328de | test | deep_technical_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model | DOM | developer_tool | css | redis | Perform a deep multi-layer analysis of redis for a developer_tool 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": "DOM", "source_url": "https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model",... | === 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 'DOM' as a source anchor and identify relevant APIs, dependencies, versions, standards, and technica... | web-research-coding-5m-1.1.0 | |
bccb9372862ff17fbb7a21ce | test | documentation_page | stackexchange | https://stackoverflow.com/questions/18111657/how-to-get-names-of-enum-entries | How to get names of enum entries? | developer_tool | java | ci_cd | Design a developer documentation page for ci_cd. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How to get names of enum entries?", "source_url": "https://stackoverflow.com/questions/181116... | Include navigation, overview, prerequisites, installation, examples, API reference, troubleshooting, and search. | web-research-coding-5m-1.1.0 | |
9bdc3460347ebad3d3edbdf3 | test | refactoring_testability | huggingface | https://huggingface.co/datasets/EduardoPacheco/documentation-images | EduardoPacheco/documentation-images | saas | sql | debugging | Refactor a sql system related to debugging. Focus on refactoring testability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "EduardoPacheco/documentation-images", "source_url": "https://huggingface.co/datasets/EduardoP... | === 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 | |
af7851153111c26592fb2e3c | test | refactoring_modularization | pypi | https://pypi.org/project/sqlalchemy/ | sqlalchemy | documentation | ruby | api_design | Refactor a ruby system related to api_design. Focus on refactoring modularization. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "sqlalchemy", "source_url": "https://pypi.org/project/sqlalchemy/", "source_type": "package", ... | === 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 | |
2029f4d231469b4dc67de3be | test | documentation_page | mdn | https://developer.mozilla.org/en-US/docs/Web/CSS | CSS | landing_page | html | open_source | Design a developer documentation page for open_source. | {"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... | Include navigation, overview, prerequisites, installation, examples, API reference, troubleshooting, and search. | web-research-coding-5m-1.1.0 | |
432bd48bf97c0b317aa5bab9 | test | responsive_design | mdn | https://developer.mozilla.org/en-US/docs/Web/Performance | Performance | finance | shell | user_experience | Create a responsive design strategy for a finance. | {"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... | Define mobile, tablet, and desktop behavior, layout transitions, navigation, content priority, typography, and interaction targets. | web-research-coding-5m-1.1.0 | |
ea26f59c3937666702eb837c | test | scalability_analysis | npm | https://www.npmjs.com/package/tailwindcss | tailwindcss | analytics | typescript | ci_cd | Perform a deep multi-layer analysis of ci_cd for a analytics 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": "tailwindcss", "source_url": "https://www.npmjs.com/package/tailwindcss", "source_type": "pack... | === 1. PROBLEM ===
Define the exact problem involving ci_cd. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around ci_cd. Use 'tailwindcss' as a source anchor and identify relevant APIs, dependencies, versions, standards, and ... | web-research-coding-5m-1.1.0 | |
e15e9ff3e1c403d4aba2195f | test | research_plan | huggingface | https://huggingface.co/datasets/vikp/textbook_quality_programming | vikp/textbook_quality_programming | dashboard | scala | distributed_systems | Build a structured research plan to deeply understand distributed_systems. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "vikp/textbook_quality_programming", "source_url": "https://huggingface.co/datasets/vikp/textb... | === GOAL ===
Produce a reliable, current, and actionable understanding of distributed_systems.
=== PHASES ===
1. Orientation — skim official docs and README.
2. Deep read — study specs, RFCs, changelogs.
3. Hands-on — reproduce examples locally.
4. Comparison — compare alternatives and trade-offs.
5. Synthesis — write... | web-research-coding-5m-1.1.0 | |
7dea0f25f326766417ac7e91 | test | seo_fix | stackexchange | https://stackoverflow.com/questions/287871/how-do-i-print-colored-text-to-the-terminal | How do I print colored text to the terminal? | landing_page | rust | developer_experience | Create an SEO improvement plan for a landing_page about developer_experience. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How do I print colored text to the terminal?", "source_url": "https://stackoverflow.com/quest... | Cover titles, descriptions, headings, canonical URLs, structured data, internal links, crawlability, and performance. | web-research-coding-5m-1.1.0 | |
bcb1e6ae60869fef234c8e8c | test | javascript_generation | github | https://github.com/microsoft/TypeScript | microsoft/TypeScript | ecommerce | java | backend | Implement JavaScript interactions for a ecommerce. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "microsoft/TypeScript", "source_url": "https://github.com/microsoft/TypeScript", "source_type"... | 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 |
fe4d7ca6150964f02832dffc | test | root_cause_analysis | npm | https://www.npmjs.com/package/zod | zod | education | ruby | authentication | Perform a deep multi-layer analysis of authentication 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": "zod", "source_url": "https://www.npmjs.com/package/zod", "source_type": "package", "topic": "... | === 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 'zod' as a source anchor and identify relevant APIs, dependencies, versions, stand... | web-research-coding-5m-1.1.0 | |
fb9484756d3f9fcc8970fd3f | test | deployment_experience | huggingface | https://huggingface.co/datasets/OLMo-Coding/starcoder-python-instruct | OLMo-Coding/starcoder-python-instruct | finance | ruby | design_system | Perform a deep developer-experience analysis for a ruby project involving design_system. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "OLMo-Coding/starcoder-python-instruct", "source_url": "https://huggingface.co/datasets/OLMo-C... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
cae97c76d6725a8eb08f5553 | test | repository_issue_reasoning | npm | https://www.npmjs.com/package/jest | jest | dashboard | c | machine_learning | Perform a deep multi-layer analysis of machine_learning 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": "jest", "source_url": "https://www.npmjs.com/package/jest", "source_type": "package", "topic":... | === 1. PROBLEM ===
Define the exact problem involving machine_learning. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around machine_learning. Use 'jest' as a source anchor and identify relevant APIs, dependencies, versions, ... | web-research-coding-5m-1.1.0 | |
e6ec0da6abc175a303f7e777 | test | multi_hop_research | pypi | https://pypi.org/project/pytest/ | pytest | productivity | shell | postgresql | Perform multi-hop research about postgresql: 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": "pytest", "source_url": "https://pypi.org/project/pytest/", "source_type": "package", "topic":... | === HOP 1 ===
Start at: pytest
https://pypi.org/project/pytest/
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.
=== SYNTHESIS ... | web-research-coding-5m-1.1.0 | |
50f82d1e75b8b3632dff672c | test | refactoring_scalability | pypi | https://pypi.org/project/pytest/ | pytest | search_interface | dart | typescript | Refactor a dart system related to typescript. Focus on refactoring scalability. | {"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":... | === 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 | |
8a2dcea79710524b566af5f3 | test | research_summary | codeberg | https://codeberg.org/nathawat/_cargo-index | nathawat/_cargo-index | portfolio | cpp | ci_cd | Summarize the current state of knowledge about ci_cd. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "nathawat/_cargo-index", "source_url": "https://codeberg.org/nathawat/_cargo-index", "source_t... | === OVERVIEW ===
ci_cd in one paragraph.
=== KEY CONCEPTS ===
- Core definitions
- Main use cases
- Common patterns
=== CURRENT BEST PRACTICES ===
- Recommended approaches
- Known anti-patterns
=== OPEN QUESTIONS ===
- Areas with active development
- Known limitations
=== PRIMARY SOURCE ===
nathawat/_cargo-index (h... | 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.