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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
6f41e1b6837f734b0fcb0137 | test | maintainability_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/Performance | Performance | productivity | swift | caching | Perform a deep multi-layer analysis of caching for a productivity using swift. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Performance", "source_url": "https://developer.mozilla.org/en-US/docs/Web/Performance", "sour... | === 1. PROBLEM ===
Define the exact problem involving caching. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around caching. Use 'Performance' as a source anchor and identify relevant APIs, dependencies, versions, standards, ... | web-research-coding-5m-1.1.0 | |
8e5fed4c4c34b096dd08357a | test | ui_design | stackexchange | https://stackoverflow.com/questions/679915/how-do-i-test-for-an-empty-javascript-object | How do I test for an empty JavaScript object? | community | ruby | nextjs | Design a production-quality UI for a community focused on nextjs. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How do I test for an empty JavaScript object?", "source_url": "https://stackoverflow.com/ques... | Define layout, typography, spacing, hierarchy, components, states, responsive behavior, and accessibility. | web-research-coding-5m-1.1.0 | |
ded02cd17b1b5667c49c58a6 | test | information_architecture | huggingface | https://huggingface.co/datasets/aamanlamba/Machine_Learning_QA_Dataset_Llama | aamanlamba/Machine_Learning_QA_Dataset_Llama | analytics | php | design_system | Design the information architecture for design_system. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "aamanlamba/Machine_Learning_QA_Dataset_Llama", "source_url": "https://huggingface.co/datasets... | Organize content into logical categories, navigation levels, search, filtering, and discoverable paths. | web-research-coding-5m-1.1.0 | |
d88931418fd5ba6fa1a125a7 | test | form_ui | stackexchange | https://stackoverflow.com/questions/5009324/node-js-nginx-what-now | Node.js + Nginx - What now? | dashboard | scala | debugging | Design an accessible form for debugging. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Node.js + Nginx - What now?", "source_url": "https://stackoverflow.com/questions/5009324/node... | Use labels, validation, clear errors, keyboard navigation, appropriate autocomplete, and accessible status messaging. | web-research-coding-5m-1.1.0 | |
8eaea5913ebbb09197bcae34 | test | refactoring_modularization | stackexchange | https://stackoverflow.com/questions/90178/make-a-div-fill-the-height-of-the-remaining-screen-space | Make a div fill the height of the remaining screen space | developer_tool | kotlin | html | Refactor a kotlin system related to html. Focus on refactoring modularization. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Make a div fill the height of the remaining screen space", "source_url": "https://stackoverfl... | === 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 | |
f935d681ed9dccf263e5ffc3 | test | maintainability_analysis | huggingface | https://huggingface.co/datasets/OLMo-Coding/starcoder-python-instruct | OLMo-Coding/starcoder-python-instruct | landing_page | java | react | Perform a deep multi-layer analysis of react for a landing_page 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": "OLMo-Coding/starcoder-python-instruct", "source_url": "https://huggingface.co/datasets/OLMo-C... | === 1. PROBLEM ===
Define the exact problem involving react. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around react. Use 'OLMo-Coding/starcoder-python-instruct' as a source anchor and identify relevant APIs, dependencies,... | web-research-coding-5m-1.1.0 | |
7c6ff54d85bad21dd6a4df9d | test | component_design | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API | Fetch API | saas | cpp | software_architecture | Design reusable UI components for a saas. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Fetch API", "source_url": "https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API", "sour... | Define component responsibilities, props/data contracts, variants, states, composition rules, accessibility, testing, and documentation. | web-research-coding-5m-1.1.0 | |
541016083e9fe7d5dd4d24a7 | test | refactoring_architecture | npm | https://www.npmjs.com/package/hono | hono | landing_page | python | authentication | Refactor a python system related to authentication. Focus on refactoring architecture. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "hono", "source_url": "https://www.npmjs.com/package/hono", "source_type": "package", "topic":... | === 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... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
cfbb73bcff1a27c0f4cc6b89 | test | cli_experience | stackexchange | https://stackoverflow.com/questions/34518656/how-to-interpret-loss-and-accuracy-for-a-machine-learning-model | How to interpret loss and accuracy for a machine learning model | blog | go | html | Perform a deep developer-experience analysis for a go project involving html. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How to interpret loss and accuracy for a machine learning model", "source_url": "https://stac... | === 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 | |
45e2315215e32d212b8ca588 | test | risk_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API | Fetch API | productivity | java | caching | Perform a deep multi-layer analysis of caching for a productivity using java. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Fetch API", "source_url": "https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API", "sour... | === 1. PROBLEM ===
Define the exact problem involving caching. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around caching. Use 'Fetch API' as a source anchor and identify relevant APIs, dependencies, versions, standards, an... | web-research-coding-5m-1.1.0 | |
8c56e9e1c5bbcaf135d65a10 | test | repository_architecture | mdn | https://developer.mozilla.org/en-US/docs/Web/HTML | HTML | saas | javascript | testing | Perform a deep multi-layer analysis of testing for a saas 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": "HTML", "source_url": "https://developer.mozilla.org/en-US/docs/Web/HTML", "source_type": "doc... | === 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 'HTML' as a source anchor and identify relevant APIs, dependencies, versions, standards, and tec... | web-research-coding-5m-1.1.0 | |
607f55f739a33821334cff1b | test | developer_onboarding | stackexchange | https://stackoverflow.com/questions/16670931/hide-scroll-bar-but-while-still-being-able-to-scroll | Hide scroll bar, but while still being able to scroll | social_app | rust | debugging | Perform a deep developer-experience analysis for a rust project involving debugging. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Hide scroll bar, but while still being able to scroll", "source_url": "https://stackoverflow.... | === 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 | |
c3109bd9f08847648fc217e2 | test | search_query_rewrite | stackexchange | https://stackoverflow.com/questions/42883547/intuitive-understanding-of-1d-2d-and-3d-convolutions-in-convolutional-neural-n | Intuitive understanding of 1D, 2D, and 3D convolutions in convolutional neural networks | admin_panel | sql | 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": "Intuitive understanding of 1D, 2D, and 3D convolutions in convolutional neural networks", "so... | === 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 | |
3d868684b398531d59960c62 | test | refactoring_observability | huggingface | https://huggingface.co/datasets/darkknight25/Adversarial_Machine_Learning_TextFooler_Dataset | darkknight25/Adversarial_Machine_Learning_TextFooler_Dataset | social_app | sql | backend | Refactor a sql system related to backend. Focus on refactoring observability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "darkknight25/Adversarial_Machine_Learning_TextFooler_Dataset", "source_url": "https://hugging... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Improve logging, metrics, tracing, diagnostics, and failure visibility.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify d... | web-research-coding-5m-1.1.0 | |
5037f9e4b583bcb645507de8 | test | root_cause_analysis | github | https://github.com/reflex-dev/reflex | reflex-dev/reflex | developer_tool | javascript | nodejs | Perform a deep multi-layer analysis of nodejs for a developer_tool 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": "reflex-dev/reflex", "source_url": "https://github.com/reflex-dev/reflex", "source_type": "rep... | === 1. PROBLEM ===
Define the exact problem involving nodejs. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around nodejs. Use 'reflex-dev/reflex' as a source anchor and identify relevant APIs, dependencies, versions, standar... | web-research-coding-5m-1.1.0 | |
cde62e378adf3d41707f3742 | test | refactoring_legacy_code | stackexchange | https://stackoverflow.com/questions/306252/how-to-align-checkboxes-and-their-labels-consistently-cross-browsers | How to align checkboxes and their labels consistently cross-browsers | dashboard | kotlin | documentation | Refactor a kotlin system related to documentation. Focus on refactoring legacy code. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How to align checkboxes and their labels consistently cross-browsers", "source_url": "https:/... | === 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 | |
627728817eacba977931b8f5 | test | research_plan | gitlab | https://gitlab.com/a_akgun/gitlab-rapid-machine-learning-prototypes | a_akgun/gitlab-rapid-machine-learning-prototypes | documentation | python | computer_vision | Build a structured research plan to deeply understand computer_vision. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "a_akgun/gitlab-rapid-machine-learning-prototypes", "source_url": "https://gitlab.com/a_akgun/... | === GOAL ===
Produce a reliable, current, and actionable understanding of computer_vision.
=== 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 fin... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
57ac754d1a3f5b98ed01a02b | test | ui_design | mdn | https://developer.mozilla.org/en-US/docs/Web/HTML | HTML | marketplace | swift | typescript | Design a production-quality UI for a marketplace focused on typescript. | {"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... | Define layout, typography, spacing, hierarchy, components, states, responsive behavior, and accessibility. | web-research-coding-5m-1.1.0 | |
d12b221665f5def30fc38010 | test | refactoring_modularization | npm | https://www.npmjs.com/package/hono | hono | blog | rust | api_design | Refactor a rust 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": "hono", "source_url": "https://www.npmjs.com/package/hono", "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 | |
a89164516a3a67d3790a8ef8 | test | refactoring_modularization | mdn | https://developer.mozilla.org/en-US/docs/Web/CSS | CSS | education | php | css | Refactor a php system related to css. Focus on refactoring modularization. | {"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 ===
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 | |
c1ad7237667cb155b8f2e1db | test | performance_analysis | pypi | https://pypi.org/project/rich/ | rich | documentation | sql | html | Perform a deep multi-layer analysis of html for a documentation 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": "rich", "source_url": "https://pypi.org/project/rich/", "source_type": "package", "topic": "ht... | === 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 'rich' as a source anchor and identify relevant APIs, dependencies, versions, standards, and technical... | web-research-coding-5m-1.1.0 | |
2b2f9c377be3a18051af1ef5 | test | tradeoff_analysis | huggingface | https://huggingface.co/datasets/MachineLearningVisionRG/CattleSSFR | MachineLearningVisionRG/CattleSSFR | ecommerce | typescript | rest_api | Perform a deep multi-layer analysis of rest_api for a ecommerce 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": "MachineLearningVisionRG/CattleSSFR", "source_url": "https://huggingface.co/datasets/MachineLe... | === 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 'MachineLearningVisionRG/CattleSSFR' as a source anchor and identify relevant APIs, dependenci... | web-research-coding-5m-1.1.0 | |
5174ecc32185046ebed6d532 | test | tradeoff_analysis | huggingface | https://huggingface.co/datasets/code-search-net/code_search_net | code-search-net/code_search_net | community | html | kubernetes | Perform a deep multi-layer analysis of kubernetes for a community 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": "code-search-net/code_search_net", "source_url": "https://huggingface.co/datasets/code-search-... | === 1. PROBLEM ===
Define the exact problem involving kubernetes. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around kubernetes. Use 'code-search-net/code_search_net' as a source anchor and identify relevant APIs, dependenc... | web-research-coding-5m-1.1.0 | |
66f93388ffee9b4a1f4aa8c4 | test | nextjs_generation | huggingface | https://huggingface.co/datasets/h4iku/coconut_javascript2010 | h4iku/coconut_javascript2010 | ecommerce | scala | postgresql | Design a Next.js architecture for a ecommerce. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "h4iku/coconut_javascript2010", "source_url": "https://huggingface.co/datasets/h4iku/coconut_j... | Specify routing, server/client boundaries, data fetching, caching, metadata, errors, and deployment. | export default function Page() {
return (
<main>
<h1>Application</h1>
<p>Production-ready page structure.</p>
</main>
);
} | web-research-coding-5m-1.1.0 |
ad720e293e6d3b04dcd1c668 | test | design_accessibility | stackexchange | https://stackoverflow.com/questions/40050397/deep-learning-nan-loss-reasons | Deep-Learning Nan loss reasons | search_interface | java | fullstack | Audit accessibility for a search_interface. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Deep-Learning Nan loss reasons", "source_url": "https://stackoverflow.com/questions/40050397/... | Check semantic structure, keyboard navigation, focus visibility, accessible names, labels, errors, contrast, and screen-reader behavior. | web-research-coding-5m-1.1.0 | |
42165785379a6f250ce5eec3 | test | code_review | mdn | https://developer.mozilla.org/en-US/docs/Web/HTTP | HTTP | landing_page | go | design_system | Perform a production code review of go code related to design_system. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "HTTP", "source_url": "https://developer.mozilla.org/en-US/docs/Web/HTTP", "source_type": "doc... | Review correctness, security, performance, readability, architecture, testing, maintainability, and error handling. | web-research-coding-5m-1.1.0 | |
e3a24ed0b1e6327098d73a71 | test | html_generation | mdn | https://developer.mozilla.org/en-US/docs/Web/Performance | Performance | saas | html | computer_vision | Create semantic HTML for a saas about computer_vision. | {"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 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 |
9c1ab02ae5bf640118c5e62e | test | performance_fix | stackexchange | https://stackoverflow.com/questions/5009324/node-js-nginx-what-now | Node.js + Nginx - What now? | saas | css | mongodb | Create a web-performance optimization plan for a saas. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Node.js + Nginx - What now?", "source_url": "https://stackoverflow.com/questions/5009324/node... | Measure first, then optimize bundle size, images, network requests, rendering, caching, and critical resources. | web-research-coding-5m-1.1.0 | |
3a754c092e144d770a76f1e5 | test | typescript_generation | mdn | https://developer.mozilla.org/en-US/docs/Web/HTTP | HTTP | blog | swift | nextjs | Implement TypeScript logic for a blog. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "HTTP", "source_url": "https://developer.mozilla.org/en-US/docs/Web/HTTP", "source_type": "doc... | 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 |
9be1df062fbc22cc7d0b5121 | test | refactoring | stackexchange | https://stackoverflow.com/questions/179123/how-to-modify-existing-unpushed-commit-messages | How to modify existing, unpushed commit messages? | education | java | authorization | Create a production coding task in java for authorization. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How to modify existing, unpushed commit messages?", "source_url": "https://stackoverflow.com/... | Provide implementation requirements, edge cases, testing requirements, security considerations, performance constraints, and documentation requirements. | web-research-coding-5m-1.1.0 | |
8d51652f95ce37c6c5bd742a | test | refactoring_performance | huggingface | https://huggingface.co/datasets/theblackcat102/evol-codealpaca-v1 | theblackcat102/evol-codealpaca-v1 | social_app | go | nlp | Refactor a go system related to nlp. Focus on refactoring performance. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "theblackcat102/evol-codealpaca-v1", "source_url": "https://huggingface.co/datasets/theblackca... | === 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 | |
0ddfd2bbfcf32b54d2feac8c | test | ui_design | huggingface | https://huggingface.co/datasets/shwetha729/quantum-machine-learning | shwetha729/quantum-machine-learning | ecommerce | html | fullstack | Design a production-quality UI for a ecommerce focused on fullstack. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "shwetha729/quantum-machine-learning", "source_url": "https://huggingface.co/datasets/shwetha7... | Define layout, typography, spacing, hierarchy, components, states, responsive behavior, and accessibility. | web-research-coding-5m-1.1.0 | |
f0c3c575ee3c41ba314b9b90 | test | repository_understanding | huggingface | https://huggingface.co/datasets/shangshang/programming-interview-zh-extended | shangshang/programming-interview-zh-extended | admin_panel | kotlin | software_architecture | Perform a deep multi-layer analysis of software_architecture for a admin_panel 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": "shangshang/programming-interview-zh-extended", "source_url": "https://huggingface.co/datasets... | === 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 'shangshang/programming-interview-zh-extended' as a source anchor an... | web-research-coding-5m-1.1.0 | |
9d2b10f3a125ab27feaa350a | test | api_design | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API | Fetch API | blog | java | open_source | Design a production API for a open_source application. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Fetch API", "source_url": "https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API", "sour... | Specify resources, endpoints, schemas, validation, authentication, authorization, errors, pagination, versioning, idempotency, and tests. | web-research-coding-5m-1.1.0 | |
0d0f70387475428bfc4592ff | test | evidence_extraction | npm | https://www.npmjs.com/package/next | next | dashboard | go | docker | Extract verifiable evidence about docker from the given source. | {"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":... | === SOURCE ===
next
https://www.npmjs.com/package/next
=== EVIDENCE ITEMS ===
1. Explicit claims made by the source
2. Code examples or API signatures
3. Version / compatibility statements
4. Performance or security notes
=== QUALITY CHECK ===
- Is the claim specific and testable?
- Is the version and environment sta... | web-research-coding-5m-1.1.0 | |
22e5f1f735db68b77b89a6a7 | test | tradeoff_analysis | npm | https://www.npmjs.com/package/rollup | rollup | ecommerce | javascript | data_structures | Perform a deep multi-layer analysis of data_structures for a ecommerce 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": "rollup", "source_url": "https://www.npmjs.com/package/rollup", "source_type": "package", "top... | === 1. PROBLEM ===
Define the exact problem involving data_structures. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around data_structures. Use 'rollup' as a source anchor and identify relevant APIs, dependencies, versions, ... | web-research-coding-5m-1.1.0 | |
d652106c80247c8ec7f6f2e8 | test | security_review | codeberg | https://codeberg.org/shewolf/_cargo-index | shewolf/_cargo-index | dashboard | sql | nlp | Perform a security review of a dashboard application. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "shewolf/_cargo-index", "source_url": "https://codeberg.org/shewolf/_cargo-index", "source_typ... | Review authentication, authorization, input validation, XSS, CSRF, injection risks, secrets, dependencies, security headers, and logging. | web-research-coding-5m-1.1.0 | |
3df2157814fe82ebb138604f | test | maintainability_analysis | pypi | https://pypi.org/project/requests/ | requests | education | python | html | Perform a deep multi-layer analysis of html for a education 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": "requests", "source_url": "https://pypi.org/project/requests/", "source_type": "package", "top... | === 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 'requests' as a source anchor and identify relevant APIs, dependencies, versions, standards, and techn... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
e9070a2aea012ad2d2aef3d9 | test | refactoring_architecture | npm | https://www.npmjs.com/package/three | three | admin_panel | javascript | kubernetes | Refactor a javascript system related to kubernetes. Focus on refactoring architecture. | {"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 ===
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 | |
d626ec8dd9efc73429681566 | test | testing_experience | npm | https://www.npmjs.com/package/vite | vite | finance | css | nodejs | Perform a deep developer-experience analysis for a css project involving nodejs. | {"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":... | === 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 | |
bbd42ad26d3ee1666ba4f8c9 | test | visual_hierarchy | mdn | https://developer.mozilla.org/en-US/docs/Web/Performance | Performance | admin_panel | cpp | open_source | Improve visual hierarchy in a admin_panel. | {"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 heading structure, typography, spacing, grouping, alignment, contrast, and consistent affordances. | web-research-coding-5m-1.1.0 | |
30fc06f1fb49c705ec750b09 | test | documentation_page | pypi | https://pypi.org/project/rich/ | rich | social_app | css | deep_learning | Design a developer documentation page for deep_learning. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "rich", "source_url": "https://pypi.org/project/rich/", "source_type": "package", "topic": "de... | Include navigation, overview, prerequisites, installation, examples, API reference, troubleshooting, and search. | web-research-coding-5m-1.1.0 | |
d4b5620718cd5c9798013387 | test | visual_hierarchy | web_docs | https://docs.python.org/3/ | Python Documentation | admin_panel | javascript | cloud | Improve visual hierarchy in a admin_panel. | {"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... | Use heading structure, typography, spacing, grouping, alignment, contrast, and consistent affordances. | web-research-coding-5m-1.1.0 | |
e023ab4d1594594306aef281 | test | refactoring_modularization | web_docs | https://docs.docker.com/ | Docker Documentation | documentation | scala | documentation | Refactor a scala system related to documentation. Focus on refactoring modularization. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Docker Documentation", "source_url": "https://docs.docker.com/", "source_type": "documentatio... | === 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 | |
dc2edc149e5a67544fd31697 | test | multi_layer_analysis | gitlab | https://gitlab.com/soapbox-pub/nostrify | soapbox-pub/nostrify | portfolio | cpp | authentication | Perform a deep multi-layer analysis of authentication for a portfolio 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": "soapbox-pub/nostrify", "source_url": "https://gitlab.com/soapbox-pub/nostrify", "source_type"... | === 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 'soapbox-pub/nostrify' as a source anchor and identify relevant APIs, dependencies... | web-research-coding-5m-1.1.0 | |
9399623b71cea37d420e3321 | test | deep_technical_analysis | huggingface | https://huggingface.co/datasets/BatsResearch/trove-lib-documentation-assets | BatsResearch/trove-lib-documentation-assets | search_interface | kotlin | machine_learning | Perform a deep multi-layer analysis of machine_learning for a search_interface using kotlin. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "BatsResearch/trove-lib-documentation-assets", "source_url": "https://huggingface.co/datasets/... | === 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 'BatsResearch/trove-lib-documentation-assets' as a source anchor and identify ... | web-research-coding-5m-1.1.0 | |
c0bdaea5d9e22cd48c9ead35 | test | unit_testing | web_docs | https://react.dev/ | React Documentation | portfolio | java | microservices | Create a unit-testing strategy for java code involving microservices. | {"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... | Cover normal cases, edge cases, invalid inputs, failure modes, mocks, and regression tests. | web-research-coding-5m-1.1.0 | |
e656e577aee5089720f3ccc7 | test | refactoring_security | stackexchange | https://stackoverflow.com/questions/4696499/meta-charset-utf-8-vs-meta-http-equiv-content-type | <meta charset="utf-8"> vs <meta http-equiv="Content-Type"> | productivity | kotlin | cloud | Refactor a kotlin system related to cloud. Focus on refactoring security. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "<meta charset="utf-8"> vs <meta http-equiv="Content-Type">", ... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Strengthen validation, trust boundaries, authorization, and secret handling.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Ident... | web-research-coding-5m-1.1.0 | |
3ba5022a794f780dd39fc167 | test | integration_testing | gitlab | https://gitlab.com/reubenlillie/eleventy-dot-js-blog | reubenlillie/eleventy-dot-js-blog | landing_page | css | authentication | Design integration tests for a css system involving authentication. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "reubenlillie/eleventy-dot-js-blog", "source_url": "https://gitlab.com/reubenlillie/eleventy-d... | Test real component boundaries, persistence, configuration, external interfaces, errors, cleanup, and realistic workflows. | web-research-coding-5m-1.1.0 | |
d8ab2ce3b28ec13460f4b79c | test | dashboard | huggingface | https://huggingface.co/datasets/semeru/code-text-javascript | semeru/code-text-javascript | documentation | swift | design_system | Design a production dashboard for design_system. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "semeru/code-text-javascript", "source_url": "https://huggingface.co/datasets/semeru/code-text... | Include navigation, KPIs, tables/charts, filters, loading states, empty states, errors, and responsive behavior. | web-research-coding-5m-1.1.0 | |
c81e09fe2cd31a0a77d492dc | test | dependency_management_experience | gitlab | https://gitlab.com/jlp-jobs/jlp-fe/jlp-typescript-fed-test | jlp-jobs/jlp-fe/jlp-typescript-fed-test | analytics | 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": "jlp-jobs/jlp-fe/jlp-typescript-fed-test", "source_url": "https://gitlab.com/jlp-jobs/jlp-fe/j... | === 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 |
8c3c41a6003531a491b4fd7e | test | upgrade_experience | gitlab | https://gitlab.com/pavel.krupala/pyqt-node-editor | pavel.krupala/pyqt-node-editor | blog | sql | caching | Perform a deep developer-experience analysis for a sql project involving caching. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "pavel.krupala/pyqt-node-editor", "source_url": "https://gitlab.com/pavel.krupala/pyqt-node-ed... | === 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 | |
b2927e73f57d1491322aaf53 | test | performance_analysis | web_docs | https://nodejs.org/docs/latest/api/ | Node.js Documentation | social_app | swift | authorization | Perform a deep multi-layer analysis of authorization for a social_app 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": "Node.js Documentation", "source_url": "https://nodejs.org/docs/latest/api/", "source_type": "... | === 1. PROBLEM ===
Define the exact problem involving authorization. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around authorization. Use 'Node.js Documentation' as a source anchor and identify relevant APIs, dependencies,... | web-research-coding-5m-1.1.0 | |
608738ce8c7641f8729556d5 | test | performance_fix | mdn | https://developer.mozilla.org/en-US/docs/Web/API | Web APIs | education | c | kubernetes | Create a web-performance optimization plan for a education. | {"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": "... | Measure first, then optimize bundle size, images, network requests, rendering, caching, and critical resources. | web-research-coding-5m-1.1.0 | |
1c84f5b2fe2f43b03f371c00 | test | developer_experience | mdn | https://developer.mozilla.org/en-US/docs/Web/HTTP | HTTP | social_app | rust | ci_cd | Perform a deep developer-experience analysis for a rust project involving ci_cd. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "HTTP", "source_url": "https://developer.mozilla.org/en-US/docs/Web/HTTP", "source_type": "doc... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
a02e90a0dbdf2adbfc2b02fc | test | information_architecture | mdn | https://developer.mozilla.org/en-US/docs/Web/Accessibility | Accessibility | finance | c | redis | Design the information architecture for redis. | {"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", "... | Organize content into logical categories, navigation levels, search, filtering, and discoverable paths. | web-research-coding-5m-1.1.0 | |
d2d5f930d621a4c316e15969 | test | responsive_website | stackexchange | https://stackoverflow.com/questions/16056591/font-scaling-based-on-size-of-container | Font scaling based on size of container | landing_page | html | algorithms | Design a complete responsive landing_page for algorithms. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Font scaling based on size of container", "source_url": "https://stackoverflow.com/questions/... | Cover mobile, tablet, and desktop layouts, semantic structure, responsive components, accessibility, performance, and UX. | web-research-coding-5m-1.1.0 | |
a85cacf811fb439cd886f406 | test | refactoring_testability | huggingface | https://huggingface.co/datasets/TaskPuppyAI/lunamax-multitask-programming-1000 | TaskPuppyAI/lunamax-multitask-programming-1000 | productivity | html | testing | Refactor a html system related to testing. Focus on refactoring testability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "TaskPuppyAI/lunamax-multitask-programming-1000", "source_url": "https://huggingface.co/datase... | === 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 | |
0c74e884e8c03fdd63ce37aa | test | code_review | codeberg | https://codeberg.org/vvlad/_cargo-index | vvlad/_cargo-index | saas | css | cloud | Perform a production code review of css code related to cloud. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "vvlad/_cargo-index", "source_url": "https://codeberg.org/vvlad/_cargo-index", "source_type": ... | Review correctness, security, performance, readability, architecture, testing, maintainability, and error handling. | web-research-coding-5m-1.1.0 | |
79d69fb1357af68620156ecc | test | security_analysis | web_docs | https://www.postgresql.org/docs/ | PostgreSQL Documentation | portfolio | typescript | react | Perform a deep multi-layer analysis of react for a portfolio 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": "PostgreSQL Documentation", "source_url": "https://www.postgresql.org/docs/", "source_type": "... | === 1. PROBLEM ===
Define the exact problem involving react. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around react. Use 'PostgreSQL Documentation' as a source anchor and identify relevant APIs, dependencies, versions, st... | web-research-coding-5m-1.1.0 | |
39a602426aebabc2ac740990 | test | documentation_page | stackexchange | https://stackoverflow.com/questions/1026069/how-do-i-make-the-first-letter-of-a-string-uppercase-in-javascript | How do I make the first letter of a string uppercase in JavaScript? | ecommerce | sql | backend | Design a developer documentation page for backend. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How do I make the first letter of a string uppercase in JavaScript?", "source_url": "https://... | Include navigation, overview, prerequisites, installation, examples, API reference, troubleshooting, and search. | web-research-coding-5m-1.1.0 | |
6070952a56ed8336aa358f65 | test | multi_hop_research | stackexchange | https://stackoverflow.com/questions/16073603/how-can-i-update-each-dependency-in-package-json-to-the-latest-version | How can I update each dependency in package.json to the latest version? | dashboard | python | design_system | Perform multi-hop research about design_system: 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": "How can I update each dependency in package.json to the latest version?", "source_url": "http... | === HOP 1 ===
Start at: How can I update each dependency in package.json to the latest version?
https://stackoverflow.com/questions/16073603/how-can-i-update-each-dependency-in-package-json-to-the-latest-version
Extract core claims and references.
=== HOP 2 ===
Follow references to official docs, RFCs, or specs.
Extra... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
ef9ce3bf5667ab1edbdc06e6 | test | evidence_extraction | pypi | https://pypi.org/project/rich/ | rich | developer_tool | sql | typescript | Extract verifiable evidence about typescript from the given source. | {"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": "ty... | === SOURCE ===
rich
https://pypi.org/project/rich/
=== EVIDENCE ITEMS ===
1. Explicit claims made by the source
2. Code examples or API signatures
3. Version / compatibility statements
4. Performance or security notes
=== QUALITY CHECK ===
- Is the claim specific and testable?
- Is the version and environment stated?... | web-research-coding-5m-1.1.0 | |
433fb55ca2d69bf89f57bc95 | test | api_design | gitlab | https://gitlab.com/materials-modeling/icet | materials-modeling/icet | ecommerce | typescript | authorization | Design a production API for a authorization application. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "materials-modeling/icet", "source_url": "https://gitlab.com/materials-modeling/icet", "source... | Specify resources, endpoints, schemas, validation, authentication, authorization, errors, pagination, versioning, idempotency, and tests. | web-research-coding-5m-1.1.0 | |
48286bfeb16d78b877add537 | test | component_design | pypi | https://pypi.org/project/flask/ | flask | saas | swift | fullstack | Design reusable UI components for a saas. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "flask", "source_url": "https://pypi.org/project/flask/", "source_type": "package", "topic": "... | Define component responsibilities, props/data contracts, variants, states, composition rules, accessibility, testing, and documentation. | web-research-coding-5m-1.1.0 | |
7e485587a5345e371854c5af | test | integration_testing | mdn | https://developer.mozilla.org/en-US/docs/Web/Accessibility | Accessibility | saas | cpp | api_design | Design integration tests for a cpp system involving api_design. | {"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", "... | Test real component boundaries, persistence, configuration, external interfaces, errors, cleanup, and realistic workflows. | web-research-coding-5m-1.1.0 | |
d978892a4c423dcb18facd81 | test | ux_design | mdn | https://developer.mozilla.org/en-US/docs/Web/HTML | HTML | marketplace | scala | nodejs | Design the complete UX flow of a marketplace for nodejs. | {"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... | 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 | |
95255d51499edc804b48b7ca | test | tradeoff_analysis | gitlab | https://gitlab.com/electrum-cash/network | electrum-cash/network | documentation | c | data_structures | Perform a deep multi-layer analysis of data_structures for a documentation using c. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "electrum-cash/network", "source_url": "https://gitlab.com/electrum-cash/network", "source_typ... | === 1. PROBLEM ===
Define the exact problem involving data_structures. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around data_structures. Use 'electrum-cash/network' as a source anchor and identify relevant APIs, dependenc... | web-research-coding-5m-1.1.0 | |
6fa476a6a2b3ee09f8825b1c | test | data_structure_design | github | https://github.com/react/react | react/react | admin_panel | cpp | debugging | Design a data structure in cpp for debugging. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "react/react", "source_url": "https://github.com/react/react", "source_type": "repository", "t... | Explain representation, operations, complexity, memory trade-offs, and workload suitability. | web-research-coding-5m-1.1.0 | |
a9873c70522a869c3369c639 | test | build_experience | huggingface | https://huggingface.co/datasets/livecodebench/code_generation_lite | livecodebench/code_generation_lite | analytics | kotlin | devops | Perform a deep developer-experience analysis for a kotlin project involving devops. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "livecodebench/code_generation_lite", "source_url": "https://huggingface.co/datasets/livecodeb... | === 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 | |
5aa6ef7f8fd37a6a6802b463 | test | multi_hop_research | huggingface | https://huggingface.co/datasets/mxzoo/CFFI-javascript-obfuscated-codeonly | mxzoo/CFFI-javascript-obfuscated-codeonly | productivity | ruby | devops | Perform multi-hop research about devops: start from a source, follow references, and combine findings. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "mxzoo/CFFI-javascript-obfuscated-codeonly", "source_url": "https://huggingface.co/datasets/mx... | === HOP 1 ===
Start at: mxzoo/CFFI-javascript-obfuscated-codeonly
https://huggingface.co/datasets/mxzoo/CFFI-javascript-obfuscated-codeonly
Extract core claims and references.
=== HOP 2 ===
Follow references to official docs, RFCs, or specs.
Extract primary-source evidence.
=== HOP 3 ===
Check community discussions f... | web-research-coding-5m-1.1.0 | |
1f7a5f0222bc36f209efeb5c | test | debugging | stackexchange | https://stackoverflow.com/questions/53975717/pytorch-connection-between-loss-backward-and-optimizer-step | pytorch - connection between loss.backward() and optimizer.step() | admin_panel | html | css | Create a realistic html debugging problem involving css. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "pytorch - connection between loss.backward() and optimizer.step()", "source_url": "https://st... | Provide symptoms, reproduction strategy, diagnostic steps, root-cause analysis, minimal fix, and regression coverage. | web-research-coding-5m-1.1.0 | |
2aeed599321b6868f65bd42e | test | architecture_analysis | web_docs | https://kubernetes.io/docs/ | Kubernetes Documentation | ecommerce | javascript | data_structures | Perform a deep multi-layer analysis of data_structures for a ecommerce 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": "Kubernetes Documentation", "source_url": "https://kubernetes.io/docs/", "source_type": "docum... | === 1. PROBLEM ===
Define the exact problem involving data_structures. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around data_structures. Use 'Kubernetes Documentation' as a source anchor and identify relevant APIs, depend... | web-research-coding-5m-1.1.0 | |
c7fc56bc1ba585dc9e76bb2e | test | repository_issue_reasoning | huggingface | https://huggingface.co/datasets/mxzoo/javascript_obfuscated_DPO_max | mxzoo/javascript_obfuscated_DPO_max | search_interface | dart | ci_cd | Perform a deep multi-layer analysis of ci_cd for a search_interface using dart. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "mxzoo/javascript_obfuscated_DPO_max", "source_url": "https://huggingface.co/datasets/mxzoo/ja... | === 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 'mxzoo/javascript_obfuscated_DPO_max' as a source anchor and identify relevant APIs, dependencies, v... | web-research-coding-5m-1.1.0 | |
63945f0e6fceed771fc76ed5 | test | deployment_experience | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API | Fetch API | marketplace | swift | kubernetes | Perform a deep developer-experience analysis for a swift project involving kubernetes. | {"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... | web-research-coding-5m-1.1.0 | |
f2feb15e93614c71e77cc7e1 | test | ux_analysis | huggingface | https://huggingface.co/datasets/multilingual-tts/open-bible | multilingual-tts/open-bible | analytics | scala | sql | Perform a deep multi-layer analysis of sql for a analytics 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": "multilingual-tts/open-bible", "source_url": "https://huggingface.co/datasets/multilingual-tts... | === 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 'multilingual-tts/open-bible' as a source anchor and identify relevant APIs, dependencies, versions, sta... | web-research-coding-5m-1.1.0 | |
8f00833924b284e646e71ff8 | test | security_analysis | github | https://github.com/DavidHDev/react-bits | DavidHDev/react-bits | documentation | swift | api_design | Perform a deep multi-layer analysis of api_design for a documentation 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": "DavidHDev/react-bits", "source_url": "https://github.com/DavidHDev/react-bits", "source_type"... | === 1. PROBLEM ===
Define the exact problem involving api_design. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around api_design. Use 'DavidHDev/react-bits' as a source anchor and identify relevant APIs, dependencies, versio... | web-research-coding-5m-1.1.0 | |
6e4553f0b92cfee593b85f07 | test | refactoring_testability | codeberg | https://codeberg.org/rutgerclaes/2025-advent-of-code-rs | rutgerclaes/2025-advent-of-code-rs | blog | sql | web_performance | Refactor a sql system related to web_performance. Focus on refactoring testability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "rutgerclaes/2025-advent-of-code-rs", "source_url": "https://codeberg.org/rutgerclaes/2025-adv... | === 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 | |
047d90785a87b17f6a35ed99 | test | interaction_design | npm | https://www.npmjs.com/package/rollup | rollup | social_app | typescript | nlp | Design interaction states for a social_app. | {"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... | Specify default, hover, focus, active, disabled, loading, success, error, and empty states. | web-research-coding-5m-1.1.0 | |
d88b4cc311b7c16220a0a6eb | test | refactoring_testability | codeberg | https://codeberg.org/13thab/2 | 13thab/2 | finance | python | nlp | Refactor a python system related to nlp. Focus on refactoring testability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "13thab/2", "source_url": "https://codeberg.org/13thab/2", "source_type": "repository", "topic... | === 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... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
3ab68830802ebff4ad49bd12 | test | information_architecture | gitlab | https://gitlab.com/flectra-hq/flectra | flectra-hq/flectra | admin_panel | go | nlp | Design the information architecture for nlp. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "flectra-hq/flectra", "source_url": "https://gitlab.com/flectra-hq/flectra", "source_type": "r... | Organize content into logical categories, navigation levels, search, filtering, and discoverable paths. | web-research-coding-5m-1.1.0 | |
01d4796d0917ae86ca321a56 | test | responsive_website | huggingface | https://huggingface.co/datasets/CM/codexglue_code2text_javascript | CM/codexglue_code2text_javascript | search_interface | go | machine_learning | Design a complete responsive search_interface for machine_learning. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "CM/codexglue_code2text_javascript", "source_url": "https://huggingface.co/datasets/CM/codexgl... | Cover mobile, tablet, and desktop layouts, semantic structure, responsive components, accessibility, performance, and UX. | web-research-coding-5m-1.1.0 | |
9d761ad9ffb2f8c15869c266 | test | evidence_chain_analysis | huggingface | https://huggingface.co/datasets/thedruid831/JavaScript-Code-Large | thedruid831/JavaScript-Code-Large | analytics | kotlin | computer_vision | Perform a deep multi-layer analysis of computer_vision for a analytics 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": "thedruid831/JavaScript-Code-Large", "source_url": "https://huggingface.co/datasets/thedruid83... | === 1. PROBLEM ===
Define the exact problem involving computer_vision. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around computer_vision. Use 'thedruid831/JavaScript-Code-Large' as a source anchor and identify relevant API... | web-research-coding-5m-1.1.0 | |
790fb6e5166b8992ed7554db | test | source_selection | huggingface | https://huggingface.co/datasets/BigScienceBiasEval/crows_pairs_multilingual | BigScienceBiasEval/crows_pairs_multilingual | admin_panel | kotlin | microservices | Select the most reliable sources to research microservices. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "BigScienceBiasEval/crows_pairs_multilingual", "source_url": "https://huggingface.co/datasets/... | === 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 | |
e7dcdfcc13a4beb33089f49d | test | developer_experience | pypi | https://pypi.org/project/streamlit/ | streamlit | productivity | c | nextjs | Perform a deep developer-experience analysis for a c project involving nextjs. | {"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. 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 | |
7e6fc7ae8c31233a9c34e1dd | test | evidence_extraction | npm | https://www.npmjs.com/package/prettier | prettier | dashboard | ruby | debugging | Extract verifiable evidence about debugging from the given source. | {"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", ... | === SOURCE ===
prettier
https://www.npmjs.com/package/prettier
=== 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 environ... | web-research-coding-5m-1.1.0 | |
d88c93d7b3f5fb69698ef708 | test | accessibility_analysis | stackexchange | https://stackoverflow.com/questions/784929/what-does-the-double-exclamation-mark-operator-do-in-javascript | What does the !! (double exclamation mark) operator do in JavaScript? | social_app | kotlin | software_architecture | Perform a deep multi-layer analysis of software_architecture for a social_app 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": "What does the !! (double exclamation mark) operator do in JavaScript?", "source_url": "https:... | === 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 'What does the !! (double exclamation mark) operator do in JavaScrip... | web-research-coding-5m-1.1.0 | |
d90eacd0866661c0b553d0e4 | test | responsive_design | web_docs | https://www.typescriptlang.org/docs/ | TypeScript Documentation | marketplace | javascript | web_accessibility | Create a responsive design strategy for a marketplace. | {"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... | Define mobile, tablet, and desktop behavior, layout transitions, navigation, content priority, typography, and interaction targets. | web-research-coding-5m-1.1.0 | |
a86d8430bab575d53cbc8fbd | test | search_query_rewrite | huggingface | https://huggingface.co/datasets/win-wang/Machine_Learning_QA_Collection | win-wang/Machine_Learning_QA_Collection | search_interface | sql | distributed_systems | Rewrite and improve a vague search query about distributed_systems 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": "win-wang/Machine_Learning_QA_Collection", "source_url": "https://huggingface.co/datasets/win-... | === ORIGINAL (VAGUE) ===
how to do distributed_systems
=== REWRITTEN QUERIES ===
1. distributed_systems official documentation guide
2. distributed_systems production best practices 2025
3. distributed_systems common pitfalls and solutions
4. distributed_systems architecture patterns with examples
=== RATIONALE ===
A... | web-research-coding-5m-1.1.0 | |
057d9b588ea4434abef64220 | test | maintainability_analysis | huggingface | https://huggingface.co/datasets/Machine-Learning-Oncology/orena-segment-annotations | Machine-Learning-Oncology/orena-segment-annotations | saas | typescript | design_system | Perform a deep multi-layer analysis of design_system for a saas using typescript. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Machine-Learning-Oncology/orena-segment-annotations", "source_url": "https://huggingface.co/d... | === 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 'Machine-Learning-Oncology/orena-segment-annotations' as a source anchor and identif... | web-research-coding-5m-1.1.0 | |
84997ab1d87b779d2eee6c64 | test | javascript_generation | web_docs | https://react.dev/ | React Documentation | marketplace | python | redis | Implement JavaScript interactions for a marketplace. | {"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 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 |
26b9c65b7765f454b9b56670 | test | product_analysis | npm | https://www.npmjs.com/package/prettier | prettier | community | java | authorization | Perform a deep multi-layer analysis of authorization for a community 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": "prettier", "source_url": "https://www.npmjs.com/package/prettier", "source_type": "package", ... | === 1. PROBLEM ===
Define the exact problem involving authorization. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around authorization. Use 'prettier' as a source anchor and identify relevant APIs, dependencies, versions, st... | web-research-coding-5m-1.1.0 | |
07bf308fd232f2e9a0c48279 | test | research_summary | huggingface | https://huggingface.co/datasets/prima02/SWE-smith-python | prima02/SWE-smith-python | education | swift | developer_experience | Summarize the current state of knowledge about developer_experience. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "prima02/SWE-smith-python", "source_url": "https://huggingface.co/datasets/prima02/SWE-smith-p... | === OVERVIEW ===
developer_experience 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 ===
prima02/S... | web-research-coding-5m-1.1.0 | |
d2799c72e6aaee16686b9173 | test | landing_page | mdn | https://developer.mozilla.org/en-US/docs/Web/JavaScript | JavaScript | landing_page | css | authorization | Design a landing page for a authorization product. | {"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... | Include hero, value proposition, features, CTA, FAQ, responsive behavior, SEO, accessibility, and analytics. | web-research-coding-5m-1.1.0 | |
04f10dd557d35861495830ea | test | refactoring_performance | stackexchange | https://stackoverflow.com/questions/2480650/what-is-the-role-of-the-bias-in-neural-networks | What is the role of the bias in neural networks? | social_app | java | distributed_systems | Refactor a java system related to distributed_systems. Focus on refactoring performance. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "What is the role of the bias in neural networks?", "source_url": "https://stackoverflow.com/q... | === 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 | |
fea12106608a7e4e7c5854a0 | test | multi_layer_analysis | codeberg | https://codeberg.org/lesbianlucy/_cargo-index | lesbianlucy/_cargo-index | saas | ruby | open_source | Perform a deep multi-layer analysis of open_source for a saas 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": "lesbianlucy/_cargo-index", "source_url": "https://codeberg.org/lesbianlucy/_cargo-index", "so... | === 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 'lesbianlucy/_cargo-index' as a source anchor and identify relevant APIs, dependencies, ... | web-research-coding-5m-1.1.0 | |
10188e7558c243fea355fc6b | test | interaction_design | huggingface | https://huggingface.co/datasets/codeparrot/github-code | codeparrot/github-code | dashboard | scala | web_performance | Design interaction states for a dashboard. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "codeparrot/github-code", "source_url": "https://huggingface.co/datasets/codeparrot/github-cod... | Specify default, hover, focus, active, disabled, loading, success, error, and empty states. | web-research-coding-5m-1.1.0 | |
73fe3f2ae50dc2a70c205a8d | test | refactoring_maintainability | web_docs | https://fastapi.tiangolo.com/ | FastAPI Documentation | analytics | php | typescript | Refactor a php system related to typescript. Focus on refactoring maintainability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "FastAPI Documentation", "source_url": "https://fastapi.tiangolo.com/", "source_type": "docume... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
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 | |
9c60cc818cc894d3c0df2c29 | test | product_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/HTML | HTML | analytics | shell | documentation | Perform a deep multi-layer analysis of documentation for a analytics 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": "HTML", "source_url": "https://developer.mozilla.org/en-US/docs/Web/HTML", "source_type": "doc... | === 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 'HTML' as a source anchor and identify relevant APIs, dependencies, versions, standa... | web-research-coding-5m-1.1.0 | |
b4f0ba32dd1a13aae6254010 | test | component_design | mdn | https://developer.mozilla.org/en-US/docs/Web/Accessibility | Accessibility | marketplace | kotlin | javascript | Design reusable UI components for a marketplace. | {"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", "... | Define component responsibilities, props/data contracts, variants, states, composition rules, accessibility, testing, and documentation. | 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.