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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
384b79635f74e5852a5ad47a | test | design_review | gitlab | https://gitlab.com/gemseo/dev/gemseo-mlearning | gemseo/dev/gemseo-mlearning | analytics | cpp | developer_experience | Perform a professional design review of a analytics. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "gemseo/dev/gemseo-mlearning", "source_url": "https://gitlab.com/gemseo/dev/gemseo-mlearning",... | Review hierarchy, consistency, responsiveness, accessibility, interaction design, content clarity, and implementation feasibility. | web-research-coding-5m-1.1.0 | |
f3fe94f1521fea3a1e64e9cf | test | risk_analysis | huggingface | https://huggingface.co/datasets/liangnanying/cifar-10-python | liangnanying/cifar-10-python | marketplace | ruby | redis | Perform a deep multi-layer analysis of redis for a marketplace using ruby. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "liangnanying/cifar-10-python", "source_url": "https://huggingface.co/datasets/liangnanying/ci... | === 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 'liangnanying/cifar-10-python' as a source anchor and identify relevant APIs, dependencies, versions... | web-research-coding-5m-1.1.0 | |
1efb9a8b7c1c0a410df2b8d8 | test | refactoring | huggingface | https://huggingface.co/datasets/dougiefresh/systems_programming_code_conversations | dougiefresh/systems_programming_code_conversations | ecommerce | java | open_source | Create a production coding task in java for open_source. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "dougiefresh/systems_programming_code_conversations", "source_url": "https://huggingface.co/da... | Provide implementation requirements, edge cases, testing requirements, security considerations, performance constraints, and documentation requirements. | web-research-coding-5m-1.1.0 | |
778d1d2000838a1f913eb7b2 | test | responsive_website | stackexchange | https://stackoverflow.com/questions/2701192/what-characters-can-be-used-for-up-down-triangle-arrow-without-stem-for-displa | What characters can be used for up/down triangle (arrow without stem) for display in HTML? | landing_page | shell | cloud | Design a complete responsive landing_page for cloud. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "What characters can be used for up/down triangle (arrow without stem) for display in HTML?", ... | Cover mobile, tablet, and desktop layouts, semantic structure, responsive components, accessibility, performance, and UX. | web-research-coding-5m-1.1.0 | |
e9037251efe7f5ee2c20635f | test | fact_verification | npm | https://www.npmjs.com/package/vite | vite | landing_page | css | caching | Verify a technical claim about caching. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "vite", "source_url": "https://www.npmjs.com/package/vite", "source_type": "package", "topic":... | === CLAIM ===
A common claim about caching.
=== VERIFICATION STEPS ===
1. Locate the primary source (docs, spec, RFC).
2. Reproduce the claim in a minimal environment.
3. Check version-specific behavior.
4. Identify edge cases and exceptions.
=== RESULT ===
Classify: confirmed / partially true / false / context-depen... | web-research-coding-5m-1.1.0 | |
c1de52fc11b86d9c8c5ca479 | test | responsive_design | npm | https://www.npmjs.com/package/eslint | eslint | landing_page | cpp | linux | Create a responsive design strategy for a landing_page. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "eslint", "source_url": "https://www.npmjs.com/package/eslint", "source_type": "package", "top... | Define mobile, tablet, and desktop behavior, layout transitions, navigation, content priority, typography, and interaction targets. | web-research-coding-5m-1.1.0 | |
637d4a0448209c1d24500f24 | test | refactoring_scalability | stackexchange | https://stackoverflow.com/questions/28889826/how-to-set-focus-on-an-input-field-after-rendering | How to set focus on an input field after rendering? | dashboard | css | open_source | Refactor a css system related to open_source. Focus on refactoring scalability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How to set focus on an input field after rendering?", "source_url": "https://stackoverflow.co... | === 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 | |
120857c5e15c2d126a299a3c | test | refactoring_security | github | https://github.com/f/prompts.chat | f/prompts.chat | landing_page | php | linux | Refactor a php system related to linux. Focus on refactoring security. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "f/prompts.chat", "source_url": "https://github.com/f/prompts.chat", "source_type": "repositor... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Strengthen validation, trust boundaries, authorization, and secret handling.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Ident... | web-research-coding-5m-1.1.0 | |
39f02e79a230afff27e69f02 | test | refactoring_dependency | huggingface | https://huggingface.co/datasets/nomic-ai/cornstack-javascript-v1 | nomic-ai/cornstack-javascript-v1 | social_app | css | web_performance | Refactor a css system related to web_performance. Focus on refactoring dependency. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "nomic-ai/cornstack-javascript-v1", "source_url": "https://huggingface.co/datasets/nomic-ai/co... | === 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 | |
d0d57fe2e4863376769140fe | test | repository_comparison | github | https://github.com/donnemartin/system-design-primer | donnemartin/system-design-primer | education | typescript | web_performance | Perform a deep multi-layer analysis of web_performance for a education 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": "donnemartin/system-design-primer", "source_url": "https://github.com/donnemartin/system-desig... | === 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 'donnemartin/system-design-primer' as a source anchor and identify relevant APIs... | web-research-coding-5m-1.1.0 | |
51fd83b9a3043f30a590c69b | test | root_cause_analysis | huggingface | https://huggingface.co/datasets/model-metadata/code_execution_files | model-metadata/code_execution_files | ecommerce | cpp | rest_api | Perform a deep multi-layer analysis of rest_api for a ecommerce 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": "model-metadata/code_execution_files", "source_url": "https://huggingface.co/datasets/model-me... | === 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 'model-metadata/code_execution_files' as a source anchor and identify relevant APIs, dependenc... | web-research-coding-5m-1.1.0 | |
927083d80d986cd67f1fdbf4 | test | refactoring_scalability | mdn | https://developer.mozilla.org/en-US/docs/Web/CSS | CSS | search_interface | go | api_design | Refactor a go system related to api_design. Focus on refactoring scalability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "CSS", "source_url": "https://developer.mozilla.org/en-US/docs/Web/CSS", "source_type": "docum... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
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 | |
7942b81871ebd3719b7dea22 | test | search_query_rewrite | huggingface | https://huggingface.co/datasets/joey234/mmlu-machine_learning-neg-prepend-fix | joey234/mmlu-machine_learning-neg-prepend-fix | community | php | design_system | Rewrite and improve a vague search query about design_system 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": "joey234/mmlu-machine_learning-neg-prepend-fix", "source_url": "https://huggingface.co/dataset... | === ORIGINAL (VAGUE) ===
how to do design_system
=== REWRITTEN QUERIES ===
1. design_system official documentation guide
2. design_system production best practices 2025
3. design_system common pitfalls and solutions
4. design_system architecture patterns with examples
=== RATIONALE ===
Add intent (learn / implement /... | web-research-coding-5m-1.1.0 | |
5e40cf85634147f0cef93dcf | test | data_structure_design | web_docs | https://react.dev/ | React Documentation | ecommerce | swift | redis | Design a data structure in swift for redis. | {"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... | Explain representation, operations, complexity, memory trade-offs, and workload suitability. | web-research-coding-5m-1.1.0 | |
2d99de68801db0de4cdaa91e | test | risk_analysis | npm | https://www.npmjs.com/package/tailwindcss | tailwindcss | blog | java | nlp | Perform a deep multi-layer analysis of nlp for a blog 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": "tailwindcss", "source_url": "https://www.npmjs.com/package/tailwindcss", "source_type": "pack... | === 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 'tailwindcss' as a source anchor and identify relevant APIs, dependencies, versions, standards, and tech... | web-research-coding-5m-1.1.0 | |
c8a729fb6d5899673c3258a4 | test | repository_comparison | npm | https://www.npmjs.com/package/svelte | svelte | finance | typescript | documentation | Perform a deep multi-layer analysis of documentation for a finance 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": "svelte", "source_url": "https://www.npmjs.com/package/svelte", "source_type": "package", "top... | === 1. PROBLEM ===
Define the exact problem involving documentation. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around documentation. Use 'svelte' as a source anchor and identify relevant APIs, dependencies, versions, stan... | web-research-coding-5m-1.1.0 | |
20087e25889e668bf3d44c00 | test | search_intent_classification | pypi | https://pypi.org/project/typer/ | typer | blog | c | authentication | Classify the search intent for a query about authentication. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "typer", "source_url": "https://pypi.org/project/typer/", "source_type": "package", "topic": "... | === 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 ===
"authentication vs alternatives"
=== CLASSIFICATION ===
Comparative / informati... | web-research-coding-5m-1.1.0 | |
f457aabd1f9ef07cf991e3a3 | test | dependency_impact_analysis | stackexchange | https://stackoverflow.com/questions/1895476/how-do-i-style-a-select-dropdown-with-only-css | How do I style a <select> dropdown with only CSS? | documentation | javascript | frontend | Perform a deep multi-layer analysis of frontend for a documentation using javascript. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How do I style a <select> dropdown with only CSS?", "source_url": "https://stackoverflo... | === 1. PROBLEM ===
Define the exact problem involving frontend. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around frontend. Use 'How do I style a <select> dropdown with only CSS?' as a source anchor and identify rele... | web-research-coding-5m-1.1.0 | |
0fc58e5436c5d070bcce72ab | test | testing_experience | gitlab | https://gitlab.com/rmnvgr/metadata-cleaner | rmnvgr/metadata-cleaner | finance | cpp | cloud | Perform a deep developer-experience analysis for a cpp project involving cloud. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "rmnvgr/metadata-cleaner", "source_url": "https://gitlab.com/rmnvgr/metadata-cleaner", "source... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
804c389273b60fd466856180 | test | visual_hierarchy | pypi | https://pypi.org/project/rich/ | rich | analytics | shell | database | Improve visual hierarchy in a analytics. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "rich", "source_url": "https://pypi.org/project/rich/", "source_type": "package", "topic": "da... | Use heading structure, typography, spacing, grouping, alignment, contrast, and consistent affordances. | web-research-coding-5m-1.1.0 | |
f51750cce7e28b353ef24d74 | test | fact_verification | mdn | https://developer.mozilla.org/en-US/docs/Web/Performance | Performance | dashboard | shell | ci_cd | Verify a technical claim about ci_cd. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Performance", "source_url": "https://developer.mozilla.org/en-US/docs/Web/Performance", "sour... | === CLAIM ===
A common claim about ci_cd.
=== VERIFICATION STEPS ===
1. Locate the primary source (docs, spec, RFC).
2. Reproduce the claim in a minimal environment.
3. Check version-specific behavior.
4. Identify edge cases and exceptions.
=== RESULT ===
Classify: confirmed / partially true / false / context-depende... | web-research-coding-5m-1.1.0 | |
4b229938a54b68c90adb5d6b | test | repository_understanding | pypi | https://pypi.org/project/streamlit/ | streamlit | admin_panel | rust | sql | Perform a deep multi-layer analysis of sql for a admin_panel using rust. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "streamlit", "source_url": "https://pypi.org/project/streamlit/", "source_type": "package", "t... | === 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 'streamlit' as a source anchor and identify relevant APIs, dependencies, versions, standards, and techni... | web-research-coding-5m-1.1.0 | |
1d4748fbf6dc97336f042fcf | test | design_review | pypi | https://pypi.org/project/django/ | django | documentation | c | authentication | Perform a professional design review of a documentation. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "django", "source_url": "https://pypi.org/project/django/", "source_type": "package", "topic":... | Review hierarchy, consistency, responsiveness, accessibility, interaction design, content clarity, and implementation feasibility. | web-research-coding-5m-1.1.0 | |
4399d5cbea5092d75894e3f2 | test | refactoring_modularization | huggingface | https://huggingface.co/datasets/IFM/Code-Reasoning | IFM/Code-Reasoning | search_interface | c | distributed_systems | Refactor a c system related to distributed_systems. Focus on refactoring modularization. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "IFM/Code-Reasoning", "source_url": "https://huggingface.co/datasets/IFM/Code-Reasoning", "sou... | === 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 | |
8cfdf184d0d1a039f35bbfe2 | test | system_analysis | pypi | https://pypi.org/project/gradio/ | gradio | landing_page | kotlin | graphql | Perform a deep multi-layer analysis of graphql for a landing_page using kotlin. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "gradio", "source_url": "https://pypi.org/project/gradio/", "source_type": "package", "topic":... | === 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 'gradio' as a source anchor and identify relevant APIs, dependencies, versions, standards, and t... | web-research-coding-5m-1.1.0 | |
b612e87154c027c8359205bb | test | html_generation | mdn | https://developer.mozilla.org/en-US/docs/Web/Accessibility | Accessibility | productivity | rust | cloud | Create semantic HTML for a productivity about cloud. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Accessibility", "source_url": "https://developer.mozilla.org/en-US/docs/Web/Accessibility", "... | 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 |
89ed55a3f6dcb9384fc52cce | test | refactoring_legacy_code | npm | https://www.npmjs.com/package/next | next | community | ruby | user_experience | Refactor a ruby system related to user_experience. Focus on refactoring legacy code. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "next", "source_url": "https://www.npmjs.com/package/next", "source_type": "package", "topic":... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
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 | |
2e8cdafc68024682ce299b1c | test | debugging_experience | web_docs | https://docs.djangoproject.com/ | Django Documentation | productivity | ruby | frontend | Perform a deep developer-experience analysis for a ruby project involving frontend. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Django Documentation", "source_url": "https://docs.djangoproject.com/", "source_type": "docum... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
01c18a09b44356ab78e82ac4 | test | information_architecture | codeberg | https://codeberg.org/KokaKiwi/_cargo-index | KokaKiwi/_cargo-index | finance | scala | cloud | Design the information architecture for cloud. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "KokaKiwi/_cargo-index", "source_url": "https://codeberg.org/KokaKiwi/_cargo-index", "source_t... | Organize content into logical categories, navigation levels, search, filtering, and discoverable paths. | web-research-coding-5m-1.1.0 | |
99ea69b7f3041935fcbbb44c | test | refactoring_readability | stackexchange | https://stackoverflow.com/questions/307291/how-does-the-google-did-you-mean-algorithm-work | How does the Google "Did you mean?" Algorithm work? | finance | java | distributed_systems | Refactor a java system related to distributed_systems. Focus on refactoring readability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How does the Google "Did you mean?" Algorithm work?", "source_url": "https://stacko... | === 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 | |
4b1aeebaf9dfad0940891b40 | test | design_to_code | huggingface | https://huggingface.co/datasets/MachineLearningLM/machinelearninglm-scm-synthetic-tabularml | MachineLearningLM/machinelearninglm-scm-synthetic-tabularml | portfolio | scala | backend | Translate a portfolio design into maintainable scala code. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "MachineLearningLM/machinelearninglm-scm-synthetic-tabularml", "source_url": "https://huggingf... | Map design tokens to code, identify reusable components, preserve responsive behavior, implement accessible states, and avoid unnecessary one-off styling. | web-research-coding-5m-1.1.0 | |
d3e9b89ad162469ba875e1bd | test | technical_research | stackexchange | https://stackoverflow.com/questions/22891211/what-is-the-difference-between-save-and-save-dev | What is the difference between --save and --save-dev? | admin_panel | css | developer_experience | Perform a technical research task about developer_experience, focused on implementation details. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "What is the difference between --save and --save-dev?", "source_url": "https://stackoverflow.... | === SCOPE ===
Technical behavior of developer_experience.
=== QUESTIONS ===
- What are the inputs, outputs, and invariants?
- What are the performance characteristics?
- What are the security implications?
- What are the compatibility constraints?
=== EVIDENCE ===
- What is the difference between --save and --save-de... | web-research-coding-5m-1.1.0 | |
4b0289b16702b4f1e356b9a8 | test | research_plan | pypi | https://pypi.org/project/streamlit/ | streamlit | landing_page | java | typescript | Build a structured research plan to deeply understand typescript. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "streamlit", "source_url": "https://pypi.org/project/streamlit/", "source_type": "package", "t... | === GOAL ===
Produce a reliable, current, and actionable understanding of typescript.
=== PHASES ===
1. Orientation — skim official docs and README.
2. Deep read — study specs, RFCs, changelogs.
3. Hands-on — reproduce examples locally.
4. Comparison — compare alternatives and trade-offs.
5. Synthesis — write findings... | web-research-coding-5m-1.1.0 | |
aea2e335437304cf3504e29a | test | system_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/JavaScript | JavaScript | portfolio | java | software_architecture | Perform a deep multi-layer analysis of software_architecture for a portfolio 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": "JavaScript", "source_url": "https://developer.mozilla.org/en-US/docs/Web/JavaScript", "source... | === 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 'JavaScript' as a source anchor and identify relevant APIs, dependen... | web-research-coding-5m-1.1.0 | |
c0bb518efeb49452e2c8bbc4 | test | refactoring_performance | huggingface | https://huggingface.co/datasets/axay/javascript-dataset-sp | axay/javascript-dataset-sp | landing_page | sql | web_accessibility | Refactor a sql system related to web_accessibility. Focus on refactoring performance. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "axay/javascript-dataset-sp", "source_url": "https://huggingface.co/datasets/axay/javascript-d... | === 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 | |
02373fdb33410462ea24ffde | test | design_consistency | gitlab | https://gitlab.com/farshadzargary1997/Microsoft-Rewards-bot | farshadzargary1997/Microsoft-Rewards-bot | documentation | rust | user_experience | Audit design consistency across a documentation. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "farshadzargary1997/Microsoft-Rewards-bot", "source_url": "https://gitlab.com/farshadzargary19... | Check repeated patterns, component variants, spacing, typography, interaction states, terminology, and responsiveness. | web-research-coding-5m-1.1.0 | |
6b355c6d96c8db1538aa334e | test | code_explanation | huggingface | https://huggingface.co/datasets/RGES-PIT/MachineLearning | RGES-PIT/MachineLearning | blog | ruby | developer_experience | Explain a ruby implementation related to developer_experience. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "RGES-PIT/MachineLearning", "source_url": "https://huggingface.co/datasets/RGES-PIT/MachineLea... | Explain inputs, outputs, control flow, algorithms, complexity, edge cases, errors, and maintainability. | web-research-coding-5m-1.1.0 | |
838a320d65e1f7d6d0620bd2 | test | refactoring_performance | github | https://github.com/scikit-learn/scikit-learn | scikit-learn/scikit-learn | finance | shell | frontend | Refactor a shell system related to frontend. Focus on refactoring performance. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "scikit-learn/scikit-learn", "source_url": "https://github.com/scikit-learn/scikit-learn", "so... | === 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 | |
08a65479e1a317974b3371b7 | test | landing_page | npm | https://www.npmjs.com/package/prettier | prettier | marketplace | c | fullstack | Design a landing page for a fullstack product. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "prettier", "source_url": "https://www.npmjs.com/package/prettier", "source_type": "package", ... | Include hero, value proposition, features, CTA, FAQ, responsive behavior, SEO, accessibility, and analytics. | web-research-coding-5m-1.1.0 | |
3554f862618227810718b61f | test | repository_architecture | web_docs | https://www.typescriptlang.org/docs/ | TypeScript Documentation | marketplace | sql | testing | Perform a deep multi-layer analysis of testing for a marketplace 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": "TypeScript Documentation", "source_url": "https://www.typescriptlang.org/docs/", "source_type... | === 1. PROBLEM ===
Define the exact problem involving testing. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around testing. Use 'TypeScript Documentation' as a source anchor and identify relevant APIs, dependencies, versions... | web-research-coding-5m-1.1.0 | |
16102e967996ee7c02349062 | test | technical_research | stackexchange | https://stackoverflow.com/questions/45022048/why-does-npm-install-rewrite-package-lock-json | Why does "npm install" rewrite package-lock.json? | ecommerce | html | backend | Perform a technical research task about backend, focused on implementation details. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Why does "npm install" rewrite package-lock.json?", "source_url": "https://stackove... | === SCOPE ===
Technical behavior of backend.
=== QUESTIONS ===
- What are the inputs, outputs, and invariants?
- What are the performance characteristics?
- What are the security implications?
- What are the compatibility constraints?
=== EVIDENCE ===
- Why does "npm install" rewrite package-lock.json? (htt... | web-research-coding-5m-1.1.0 | |
fe8fcd751e239db6adc2a8a9 | test | deep_technical_analysis | npm | https://www.npmjs.com/package/typescript | typescript | admin_panel | css | algorithms | Perform a deep multi-layer analysis of algorithms for a admin_panel using css. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "typescript", "source_url": "https://www.npmjs.com/package/typescript", "source_type": "packag... | === 1. PROBLEM ===
Define the exact problem involving algorithms. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around algorithms. Use 'typescript' as a source anchor and identify relevant APIs, dependencies, versions, standa... | web-research-coding-5m-1.1.0 | |
3c8e411e419cbe21a7c48dfd | test | ux_design | stackexchange | https://stackoverflow.com/questions/739654/how-do-i-make-function-decorators-and-chain-them-together | How do I make function decorators and chain them together? | admin_panel | typescript | user_experience | Design the complete UX flow of a admin_panel for user_experience. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How do I make function decorators and chain them together?", "source_url": "https://stackover... | Map user goals, entry points, navigation, primary actions, feedback, loading states, empty states, errors, recovery paths, and completion. | web-research-coding-5m-1.1.0 | |
c7645739d30cec2bf913d894 | test | security_analysis | huggingface | https://huggingface.co/datasets/orgcatorg/multilingual | orgcatorg/multilingual | marketplace | ruby | nextjs | Perform a deep multi-layer analysis of nextjs for a marketplace using ruby. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "orgcatorg/multilingual", "source_url": "https://huggingface.co/datasets/orgcatorg/multilingua... | === 1. PROBLEM ===
Define the exact problem involving nextjs. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around nextjs. Use 'orgcatorg/multilingual' as a source anchor and identify relevant APIs, dependencies, versions, st... | web-research-coding-5m-1.1.0 | |
5475dc434ebb4e8baa07794a | test | design_components | stackexchange | https://stackoverflow.com/questions/17071871/how-do-i-select-rows-from-a-dataframe-based-on-column-values | How do I select rows from a DataFrame based on column values? | developer_tool | javascript | deep_learning | Create a component architecture for a developer_tool. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How do I select rows from a DataFrame based on column values?", "source_url": "https://stacko... | Define primitive components, composite components, variants, states, composition rules, and accessibility contracts. | web-research-coding-5m-1.1.0 | |
d94ee94c6c7412d0d62e9e01 | test | form_ui | stackexchange | https://stackoverflow.com/questions/1628563/move-the-most-recent-commits-to-a-new-branch-with-git | Move the most recent commit(s) to a new branch with Git | portfolio | sql | postgresql | Design an accessible form for postgresql. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Move the most recent commit(s) to a new branch with Git", "source_url": "https://stackoverflo... | Use labels, validation, clear errors, keyboard navigation, appropriate autocomplete, and accessible status messaging. | web-research-coding-5m-1.1.0 | |
0fd3cf3ef5093a601d644823 | test | refactoring_scalability | gitlab | https://gitlab.com/woob/woob | woob/woob | portfolio | javascript | web_performance | Refactor a javascript system related to web_performance. Focus on refactoring scalability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "woob/woob", "source_url": "https://gitlab.com/woob/woob", "source_type": "repository", "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 | |
bbc2c06dd3087a2c51f4c5dc | test | documentation_lookup | npm | https://www.npmjs.com/package/webpack | webpack | marketplace | cpp | frontend | Find and summarize the relevant documentation for frontend. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "webpack", "source_url": "https://www.npmjs.com/package/webpack", "source_type": "package", "t... | === RELEVANT DOCS ===
- webpack
https://www.npmjs.com/package/webpack
- Official project documentation
- API reference
=== KEY SECTIONS ===
- Getting started
- API reference
- Configuration
- Troubleshooting
=== SUMMARY ===
Summarize each section in 1–3 sentences and quote exact signatures where relevant. | web-research-coding-5m-1.1.0 | |
0f932251f5b5e698e97e14b3 | test | debugging | github | https://github.com/expo/expo | expo/expo | marketplace | typescript | frontend | Create a realistic typescript debugging problem involving frontend. | {"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... | Provide symptoms, reproduction strategy, diagnostic steps, root-cause analysis, minimal fix, and regression coverage. | web-research-coding-5m-1.1.0 | |
a45941b017d076a6e020b33b | test | deployment_experience | github | https://github.com/react/create-react-app | react/create-react-app | education | swift | backend | Perform a deep developer-experience analysis for a swift project involving backend. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "react/create-react-app", "source_url": "https://github.com/react/create-react-app", "source_t... | === 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 | |
b939291c546e6aea9d04b8a2 | test | dependency_management_experience | huggingface | https://huggingface.co/datasets/ytzi/the-stack-dedup-python-filtered-docstrings | ytzi/the-stack-dedup-python-filtered-docstrings | productivity | java | machine_learning | Perform a deep developer-experience analysis for a java project involving machine_learning. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "ytzi/the-stack-dedup-python-filtered-docstrings", "source_url": "https://huggingface.co/datas... | === 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 | |
f017b6c2ffef28f3326ea25a | test | refactoring_modularization | npm | https://www.npmjs.com/package/three | three | admin_panel | kotlin | devops | Refactor a kotlin system related to devops. Focus on refactoring modularization. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "three", "source_url": "https://www.npmjs.com/package/three", "source_type": "package", "topic... | === 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 | |
9e20801ab4d6e35684152570 | test | refactoring_dependency | huggingface | https://huggingface.co/datasets/kaydenfu/documentation-images | kaydenfu/documentation-images | search_interface | swift | user_experience | Refactor a swift system related to user_experience. Focus on refactoring dependency. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "kaydenfu/documentation-images", "source_url": "https://huggingface.co/datasets/kaydenfu/docum... | === 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 | |
4be09c8a0fa222c96f0ad2fb | test | performance_fix | codeberg | https://codeberg.org/UI-Programming-23-24/01-Web-basics-and-git-Dylan-Crimmings | UI-Programming-23-24/01-Web-basics-and-git-Dylan-Crimmings | social_app | kotlin | docker | Create a web-performance optimization plan for a social_app. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "UI-Programming-23-24/01-Web-basics-and-git-Dylan-Crimmings", "source_url": "https://codeberg.... | Measure first, then optimize bundle size, images, network requests, rendering, caching, and critical resources. | web-research-coding-5m-1.1.0 | |
6f051fcfaca4d742cb417539 | test | form_ui | npm | https://www.npmjs.com/package/express | express | landing_page | scala | frontend | Design an accessible form for frontend. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "express", "source_url": "https://www.npmjs.com/package/express", "source_type": "package", "t... | Use labels, validation, clear errors, keyboard navigation, appropriate autocomplete, and accessible status messaging. | web-research-coding-5m-1.1.0 | |
aa65d6c26341fbdd36711b99 | test | ux_design | gitlab | https://gitlab.com/panoramax/clients/web-viewer | panoramax/clients/web-viewer | blog | rust | authorization | Design the complete UX flow of a blog for authorization. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "panoramax/clients/web-viewer", "source_url": "https://gitlab.com/panoramax/clients/web-viewer... | Map user goals, entry points, navigation, primary actions, feedback, loading states, empty states, errors, recovery paths, and completion. | web-research-coding-5m-1.1.0 | |
78b1f6c9e45aca45997f0343 | test | landing_page | huggingface | https://huggingface.co/datasets/prsdm/Machine-Learning-QA-dataset | prsdm/Machine-Learning-QA-dataset | developer_tool | ruby | testing | Design a landing page for a testing product. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "prsdm/Machine-Learning-QA-dataset", "source_url": "https://huggingface.co/datasets/prsdm/Mach... | Include hero, value proposition, features, CTA, FAQ, responsive behavior, SEO, accessibility, and analytics. | web-research-coding-5m-1.1.0 | |
5167e27e6998a6ac518a8af5 | test | seo_fix | huggingface | https://huggingface.co/datasets/Romoamigo/SWE-Bench-MultilingualC_CPPFiletered | Romoamigo/SWE-Bench-MultilingualC_CPPFiletered | productivity | go | api_design | Create an SEO improvement plan for a productivity about api_design. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Romoamigo/SWE-Bench-MultilingualC_CPPFiletered", "source_url": "https://huggingface.co/datase... | Cover titles, descriptions, headings, canonical URLs, structured data, internal links, crawlability, and performance. | web-research-coding-5m-1.1.0 | |
8739f48f04eff3b76237799a | test | research_summary | gitlab | https://gitlab.com/hnickisch/gpml-matlab | hnickisch/gpml-matlab | ecommerce | cpp | typescript | Summarize the current state of knowledge about typescript. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "hnickisch/gpml-matlab", "source_url": "https://gitlab.com/hnickisch/gpml-matlab", "source_typ... | === OVERVIEW ===
typescript 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 ===
hnickisch/gpml-matl... | web-research-coding-5m-1.1.0 | |
c885eabf1164e6fc4be3e7b4 | test | refactoring_modularization | pypi | https://pypi.org/project/flask/ | flask | community | cpp | backend | Refactor a cpp system related to backend. Focus on refactoring modularization. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "flask", "source_url": "https://pypi.org/project/flask/", "source_type": "package", "topic": "... | === 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 | |
5419514dbdac3f5628cd36a5 | test | dx_analysis | npm | https://www.npmjs.com/package/express | express | ecommerce | cpp | devops | Perform a deep developer-experience analysis for a cpp project involving devops. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "express", "source_url": "https://www.npmjs.com/package/express", "source_type": "package", "t... | === 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 | |
8c916b68f2958d73409fe0f6 | test | debugging_experience | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model | DOM | landing_page | css | react | Perform a deep developer-experience analysis for a css project involving react. | {"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 | |
6b073716327cfe41f1335e93 | test | evidence_extraction | github | https://github.com/vercel/next.js | vercel/next.js | marketplace | ruby | data_structures | Extract verifiable evidence about data_structures from the given source. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "vercel/next.js", "source_url": "https://github.com/vercel/next.js", "source_type": "repositor... | === SOURCE ===
vercel/next.js
https://github.com/vercel/next.js
=== 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 enviro... | web-research-coding-5m-1.1.0 | |
a6a2381c94b7fb24267aaf8a | test | design_consistency | npm | https://www.npmjs.com/package/typescript | typescript | documentation | swift | nextjs | Audit design consistency across a documentation. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "typescript", "source_url": "https://www.npmjs.com/package/typescript", "source_type": "packag... | Check repeated patterns, component variants, spacing, typography, interaction states, terminology, and responsiveness. | web-research-coding-5m-1.1.0 | |
02cb92189b238f68788ab3ba | test | seo_fix | stackexchange | https://stackoverflow.com/questions/2939914/how-do-i-vertically-align-text-in-a-div | How do I vertically align text in a div? | saas | c | caching | Create an SEO improvement plan for a saas about caching. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How do I vertically align text in a div?", "source_url": "https://stackoverflow.com/questions... | Cover titles, descriptions, headings, canonical URLs, structured data, internal links, crawlability, and performance. | web-research-coding-5m-1.1.0 | |
c482c6d31a01d3cd8225b10d | test | search_intent_classification | web_docs | https://docs.python.org/3/ | Python Documentation | developer_tool | dart | machine_learning | Classify the search intent for a query about machine_learning. | {"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... | === 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 ===
"machine_learning vs alternatives"
=== CLASSIFICATION ===
Comparative / informa... | web-research-coding-5m-1.1.0 | |
20fff4ccf4ceeea0dd77eb3f | test | design_system | npm | https://www.npmjs.com/package/jest | jest | search_interface | kotlin | nextjs | Create a scalable design system for a search_interface. | {"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":... | Define tokens, typography, spacing, components, variants, states, responsive rules, accessibility, and documentation. | web-research-coding-5m-1.1.0 | |
6a001d595e731d1ed8f42e77 | test | unit_testing | mdn | https://developer.mozilla.org/en-US/docs/Web/JavaScript | JavaScript | community | sql | frontend | Create a unit-testing strategy for sql code involving frontend. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "JavaScript", "source_url": "https://developer.mozilla.org/en-US/docs/Web/JavaScript", "source... | Cover normal cases, edge cases, invalid inputs, failure modes, mocks, and regression tests. | web-research-coding-5m-1.1.0 | |
0879c11dc6c843817a813eda | test | source_selection | gitlab | https://gitlab.com/shyft-os/shyft | shyft-os/shyft | admin_panel | rust | html | Select the most reliable sources to research html. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "shyft-os/shyft", "source_url": "https://gitlab.com/shyft-os/shyft", "source_type": "repositor... | === SOURCE TIERS ===
1. Primary: official documentation, specifications, RFCs
2. Secondary: maintained repositories, changelogs, releases
3. Tertiary: tutorials, blog posts, Q&A
=== SELECTION CRITERIA ===
- Authority of the publisher
- Recency and version relevance
- Technical depth
- Reproducibility of examples
=== ... | web-research-coding-5m-1.1.0 | |
d982e03773bc7db0e7e89fa4 | test | refactoring | huggingface | https://huggingface.co/datasets/joey234/mmlu-machine_learning-neg-prepend-fix | joey234/mmlu-machine_learning-neg-prepend-fix | productivity | c | web_accessibility | Create a production coding task in c for web_accessibility. | {"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... | Provide implementation requirements, edge cases, testing requirements, security considerations, performance constraints, and documentation requirements. | web-research-coding-5m-1.1.0 | |
14089225d9d6f2b14937fc1c | test | information_architecture | npm | https://www.npmjs.com/package/vitest | vitest | analytics | go | frontend | Design the information architecture for frontend. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "vitest", "source_url": "https://www.npmjs.com/package/vitest", "source_type": "package", "top... | Organize content into logical categories, navigation levels, search, filtering, and discoverable paths. | web-research-coding-5m-1.1.0 | |
0473073758298ad0c22d0231 | test | dashboard | web_docs | https://go.dev/doc/ | Go Documentation | education | java | rest_api | Design a production dashboard for rest_api. | {"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... | Include navigation, KPIs, tables/charts, filters, loading states, empty states, errors, and responsive behavior. | web-research-coding-5m-1.1.0 | |
b1bd3d9025b3ff31d29f774f | test | accessibility_analysis | stackexchange | https://stackoverflow.com/questions/6771258/what-does-meta-http-equiv-x-ua-compatible-content-ie-edge-do | What does <meta http-equiv="X-UA-Compatible" content="IE=edge"> do? | analytics | css | typescript | Perform a deep multi-layer analysis of typescript for a analytics using css. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "What does <meta http-equiv="X-UA-Compatible" content="IE=edge"> do?... | === 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 'What does <meta http-equiv="X-UA-Compatible" content="IE=edge">... | web-research-coding-5m-1.1.0 | |
10ede44e3caef91caa08738e | test | refactoring_security | stackexchange | https://stackoverflow.com/questions/21733847/react-jsx-selecting-selected-on-selected-select-option | React JSX: selecting "selected" on selected <select> option | ecommerce | swift | computer_vision | Refactor a swift system related to computer_vision. Focus on refactoring security. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "React JSX: selecting "selected" on selected <select> option", "source_url": "... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Strengthen validation, trust boundaries, authorization, and secret handling.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Ident... | web-research-coding-5m-1.1.0 | |
df1645c3811be8d823da5a03 | test | research_summary | npm | https://www.npmjs.com/package/vite | vite | marketplace | cpp | html | Summarize the current state of knowledge about html. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "vite", "source_url": "https://www.npmjs.com/package/vite", "source_type": "package", "topic":... | === OVERVIEW ===
html 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 ===
vite (https://www.npmjs.c... | web-research-coding-5m-1.1.0 | |
916273cf2a14a9c6a85f49cc | test | evidence_chain_analysis | gitlab | https://gitlab.com/osp-group/flask-nginx-rtmp-manager | osp-group/flask-nginx-rtmp-manager | admin_panel | ruby | machine_learning | Perform a deep multi-layer analysis of machine_learning for a admin_panel 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": "osp-group/flask-nginx-rtmp-manager", "source_url": "https://gitlab.com/osp-group/flask-nginx-... | === 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 'osp-group/flask-nginx-rtmp-manager' as a source anchor and identify relevant ... | web-research-coding-5m-1.1.0 | |
09be0fa1e9732e0a572ac3eb | test | debugging | web_docs | https://fastapi.tiangolo.com/ | FastAPI Documentation | analytics | swift | data_structures | Create a realistic swift debugging problem involving data_structures. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "FastAPI Documentation", "source_url": "https://fastapi.tiangolo.com/", "source_type": "docume... | Provide symptoms, reproduction strategy, diagnostic steps, root-cause analysis, minimal fix, and regression coverage. | web-research-coding-5m-1.1.0 | |
45d3ad21c234e8040dfc2c52 | test | api_developer_experience | mdn | https://developer.mozilla.org/en-US/docs/Web/HTML | HTML | landing_page | python | serverless | Perform a deep developer-experience analysis for a python project involving serverless. | {"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... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
b8429c9aff3eba3b2f230726 | test | source_comparison | huggingface | https://huggingface.co/datasets/EssentialAI/eai-taxonomy-code-w-dclm | EssentialAI/eai-taxonomy-code-w-dclm | developer_tool | kotlin | database | Compare multiple sources about database and identify agreements, contradictions, and gaps. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "EssentialAI/eai-taxonomy-code-w-dclm", "source_url": "https://huggingface.co/datasets/Essenti... | === SOURCES ===
- EssentialAI/eai-taxonomy-code-w-dclm (https://huggingface.co/datasets/EssentialAI/eai-taxonomy-code-w-dclm)
- Official documentation
- Community discussions
=== AGREEMENTS ===
Identify claims supported by multiple independent sources.
=== CONTRADICTIONS ===
Identify conflicting claims and their like... | web-research-coding-5m-1.1.0 | |
066171c28a298ecfad092652 | test | code_review | mdn | https://developer.mozilla.org/en-US/docs/Web/CSS | CSS | community | go | debugging | Perform a production code review of go code related to debugging. | {"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... | Review correctness, security, performance, readability, architecture, testing, maintainability, and error handling. | web-research-coding-5m-1.1.0 | |
f9eccb965186bf5b925812f4 | test | repository_comparison | pypi | https://pypi.org/project/sqlalchemy/ | sqlalchemy | finance | c | design_system | Perform a deep multi-layer analysis of design_system for a finance using c. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "sqlalchemy", "source_url": "https://pypi.org/project/sqlalchemy/", "source_type": "package", ... | === 1. PROBLEM ===
Define the exact problem involving design_system. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around design_system. Use 'sqlalchemy' as a source anchor and identify relevant APIs, dependencies, versions, ... | web-research-coding-5m-1.1.0 | |
5cb2a492c3753e4b71f900f6 | test | design_accessibility | huggingface | https://huggingface.co/datasets/israellaguan/axay-javascript-dataset-pn | israellaguan/axay-javascript-dataset-pn | analytics | rust | frontend | Audit accessibility for a analytics. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "israellaguan/axay-javascript-dataset-pn", "source_url": "https://huggingface.co/datasets/isra... | Check semantic structure, keyboard navigation, focus visibility, accessible names, labels, errors, contrast, and screen-reader behavior. | web-research-coding-5m-1.1.0 | |
16598c0519286072a16d1a52 | test | technical_research | npm | https://www.npmjs.com/package/tailwindcss | tailwindcss | developer_tool | kotlin | documentation | Perform a technical research task about documentation, focused on implementation details. | {"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... | === SCOPE ===
Technical behavior of documentation.
=== QUESTIONS ===
- What are the inputs, outputs, and invariants?
- What are the performance characteristics?
- What are the security implications?
- What are the compatibility constraints?
=== EVIDENCE ===
- tailwindcss (https://www.npmjs.com/package/tailwindcss)
- ... | web-research-coding-5m-1.1.0 | |
c9c341314a4d4781dff53297 | test | error_message_design | huggingface | https://huggingface.co/datasets/styletts2-community/multilingual-pl-bert | styletts2-community/multilingual-pl-bert | landing_page | css | web_accessibility | Perform a deep developer-experience analysis for a css project involving web_accessibility. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "styletts2-community/multilingual-pl-bert", "source_url": "https://huggingface.co/datasets/sty... | === 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 | |
524bbf18a9e3c1683dbd3a26 | test | debugging_experience | pypi | https://pypi.org/project/gradio/ | gradio | admin_panel | swift | nlp | Perform a deep developer-experience analysis for a swift project involving nlp. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "gradio", "source_url": "https://pypi.org/project/gradio/", "source_type": "package", "topic":... | === 1. 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 | |
3965d74b48dec3d8f8dceb91 | test | api_developer_experience | codeberg | https://codeberg.org/Alex-Bowes/01_Web_basics_and_git_Alex_Bowes.C00287604 | Alex-Bowes/01_Web_basics_and_git_Alex_Bowes.C00287604 | saas | kotlin | postgresql | Perform a deep developer-experience analysis for a kotlin project involving postgresql. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Alex-Bowes/01_Web_basics_and_git_Alex_Bowes.C00287604", "source_url": "https://codeberg.org/A... | === 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 | |
a87d4054c9a626afd52705dc | test | performance_fix | pypi | https://pypi.org/project/transformers/ | transformers | community | html | nodejs | Create a web-performance optimization plan for a community. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "transformers", "source_url": "https://pypi.org/project/transformers/", "source_type": "packag... | Measure first, then optimize bundle size, images, network requests, rendering, caching, and critical resources. | web-research-coding-5m-1.1.0 | |
8ed5b629378163f7a397c675 | test | ui_design | npm | https://www.npmjs.com/package/prettier | prettier | blog | swift | react | Design a production-quality UI for a blog focused on react. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "prettier", "source_url": "https://www.npmjs.com/package/prettier", "source_type": "package", ... | Define layout, typography, spacing, hierarchy, components, states, responsive behavior, and accessibility. | web-research-coding-5m-1.1.0 | |
4b17215b0670a252d4835ef5 | test | refactoring_architecture | pypi | https://pypi.org/project/numpy/ | numpy | productivity | java | javascript | Refactor a java system related to javascript. Focus on refactoring architecture. | {"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": "... | === 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 | |
0536c0d85275ef5e4bcbe7b4 | test | api_developer_experience | github | https://github.com/vuejs/core | vuejs/core | ecommerce | rust | typescript | Perform a deep developer-experience analysis for a rust project involving typescript. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "vuejs/core", "source_url": "https://github.com/vuejs/core", "source_type": "repository", "top... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
c308c523663e1b77db738c3e | test | root_cause_analysis | huggingface | https://huggingface.co/datasets/AkshithAI/starcoderdata-javascript-ctx-6144 | AkshithAI/starcoderdata-javascript-ctx-6144 | education | html | open_source | Perform a deep multi-layer analysis of open_source for a education using html. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "AkshithAI/starcoderdata-javascript-ctx-6144", "source_url": "https://huggingface.co/datasets/... | === 1. PROBLEM ===
Define the exact problem involving open_source. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around open_source. Use 'AkshithAI/starcoderdata-javascript-ctx-6144' as a source anchor and identify relevant A... | web-research-coding-5m-1.1.0 | |
bbdc08b7f012b0fbe52b3aac | test | css_generation | huggingface | https://huggingface.co/datasets/mxzoo/CFFI-javascript-obfuscated-DPO | mxzoo/CFFI-javascript-obfuscated-DPO | search_interface | c | algorithms | Create responsive CSS for a search_interface. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "mxzoo/CFFI-javascript-obfuscated-DPO", "source_url": "https://huggingface.co/datasets/mxzoo/C... | Use reusable rules, responsive layouts, scalable typography, spacing, focus states, and mobile support. | :root {
--space: 1rem;
}
* {
box-sizing: border-box;
}
body {
margin: 0;
font-family: system-ui, sans-serif;
}
.container {
width: min(100% - 2rem, 1200px);
margin-inline: auto;
} | web-research-coding-5m-1.1.0 |
72fc2428aea399f91cbea22b | test | design_review | web_docs | https://doc.rust-lang.org/ | Rust Documentation | landing_page | dart | ci_cd | Perform a professional design review of a landing_page. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Rust Documentation", "source_url": "https://doc.rust-lang.org/", "source_type": "documentatio... | Review hierarchy, consistency, responsiveness, accessibility, interaction design, content clarity, and implementation feasibility. | web-research-coding-5m-1.1.0 | |
1421860437872cb7d6c9afce | test | testing_experience | mdn | https://developer.mozilla.org/en-US/docs/Web/Accessibility | Accessibility | portfolio | java | design_system | Perform a deep developer-experience analysis for a java project involving design_system. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Accessibility", "source_url": "https://developer.mozilla.org/en-US/docs/Web/Accessibility", "... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
0d575dbed2543e133d6c1a80 | test | multi_hop_research | pypi | https://pypi.org/project/scrapy/ | scrapy | social_app | ruby | caching | Perform multi-hop research about caching: 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": "scrapy", "source_url": "https://pypi.org/project/scrapy/", "source_type": "package", "topic":... | === HOP 1 ===
Start at: scrapy
https://pypi.org/project/scrapy/
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 | |
9f2a48bc6fdf6a0ace904f22 | test | documentation_lookup | npm | https://www.npmjs.com/package/rollup | rollup | social_app | sql | nlp | Find and summarize the relevant documentation for nlp. | {"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... | === RELEVANT DOCS ===
- rollup
https://www.npmjs.com/package/rollup
- Official project documentation
- API reference
=== KEY SECTIONS ===
- Getting started
- API reference
- Configuration
- Troubleshooting
=== SUMMARY ===
Summarize each section in 1–3 sentences and quote exact signatures where relevant. | web-research-coding-5m-1.1.0 | |
2aa8fa744a571280718464dc | test | integration_testing | huggingface | https://huggingface.co/datasets/jan-hq/multiturn_programming_binarized | jan-hq/multiturn_programming_binarized | marketplace | go | postgresql | Design integration tests for a go system involving postgresql. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "jan-hq/multiturn_programming_binarized", "source_url": "https://huggingface.co/datasets/jan-h... | Test real component boundaries, persistence, configuration, external interfaces, errors, cleanup, and realistic workflows. | web-research-coding-5m-1.1.0 | |
12cdb907e45b21034ade1849 | test | research_summary | web_docs | https://www.postgresql.org/docs/ | PostgreSQL Documentation | dashboard | python | nextjs | Summarize the current state of knowledge about nextjs. | {"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": "... | === OVERVIEW ===
nextjs 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 ===
PostgreSQL Documentatio... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
3482050b9ee1970a9720e000 | test | local_development_experience | github | https://github.com/shadcn-ui/ui | shadcn-ui/ui | education | dart | redis | Perform a deep developer-experience analysis for a dart project involving redis. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "shadcn-ui/ui", "source_url": "https://github.com/shadcn-ui/ui", "source_type": "repository", ... | === 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 | |
c03b617cce5dd62e2f193068 | test | refactoring_modularization | pypi | https://pypi.org/project/sqlalchemy/ | sqlalchemy | analytics | kotlin | redis | Refactor a kotlin system related to redis. 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 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.