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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
97838845b8988fee1ec9d934 | train | ux_design | npm | https://www.npmjs.com/package/prettier | prettier | dashboard | typescript | debugging | Design the complete UX flow of a dashboard for debugging. | {"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", ... | 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 | |
bf5b0c1559870b5e275e816d | train | responsive_website | npm | https://www.npmjs.com/package/webpack | webpack | blog | go | cloud | Design a complete responsive blog for cloud. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "webpack", "source_url": "https://www.npmjs.com/package/webpack", "source_type": "package", "t... | Cover mobile, tablet, and desktop layouts, semantic structure, responsive components, accessibility, performance, and UX. | web-research-coding-5m-1.1.0 | |
8ed94acb43886e02783ce1b3 | train | documentation_lookup | huggingface | https://huggingface.co/datasets/thedruid831/JavaScript-Code-Large | thedruid831/JavaScript-Code-Large | documentation | shell | user_experience | Find and summarize the relevant documentation for user_experience. | {"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... | === RELEVANT DOCS ===
- thedruid831/JavaScript-Code-Large
https://huggingface.co/datasets/thedruid831/JavaScript-Code-Large
- Official project documentation
- API reference
=== KEY SECTIONS ===
- Getting started
- API reference
- Configuration
- Troubleshooting
=== SUMMARY ===
Summarize each section in 1–3 sentence... | web-research-coding-5m-1.1.0 | |
fbd9f51ed4c22e95af8699e3 | train | multi_hop_research | npm | https://www.npmjs.com/package/three | three | dashboard | ruby | html | Perform multi-hop research about html: 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": "three", "source_url": "https://www.npmjs.com/package/three", "source_type": "package", "topic... | === HOP 1 ===
Start at: three
https://www.npmjs.com/package/three
Extract core claims and references.
=== HOP 2 ===
Follow references to official docs, RFCs, or specs.
Extract primary-source evidence.
=== HOP 3 ===
Check community discussions for real-world issues.
Extract failure modes and workarounds.
=== SYNTHESI... | web-research-coding-5m-1.1.0 | |
3d1b4b9df61d0664ccdce908 | train | architecture_analysis | stackexchange | https://stackoverflow.com/questions/34240703/what-are-logits-what-is-the-difference-between-softmax-and-softmax-cross-entrop | What are logits? What is the difference between softmax and softmax_cross_entropy_with_logits? | ecommerce | dart | nodejs | Perform a deep multi-layer analysis of nodejs for a ecommerce 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": "What are logits? What is the difference between softmax and softmax_cross_entropy_with_logits... | === 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 'What are logits? What is the difference between softmax and softmax_cross_entropy_with_logits?' a... | web-research-coding-5m-1.1.0 | |
4143fc6c95b36043704ea312 | train | repository_documentation | mdn | https://developer.mozilla.org/en-US/docs/Web/CSS | CSS | portfolio | javascript | computer_vision | Perform a deep multi-layer analysis of computer_vision for a portfolio using javascript. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "CSS", "source_url": "https://developer.mozilla.org/en-US/docs/Web/CSS", "source_type": "docum... | === 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 'CSS' as a source anchor and identify relevant APIs, dependencies, versions, sta... | web-research-coding-5m-1.1.0 | |
eaa80fb74874ba9eef6699fd | train | developer_experience | gitlab | https://gitlab.com/unimatrix/larod | unimatrix/larod | community | html | documentation | Perform a deep developer-experience analysis for a html project involving documentation. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "unimatrix/larod", "source_url": "https://gitlab.com/unimatrix/larod", "source_type": "reposit... | === 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 | |
4989febea321547c6d1b3101 | train | information_architecture | stackexchange | https://stackoverflow.com/questions/10972176/find-the-version-of-an-installed-npm-package | Find the version of an installed npm package | social_app | php | 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": "Find the version of an installed npm package", "source_url": "https://stackoverflow.com/quest... | Organize content into logical categories, navigation levels, search, filtering, and discoverable paths. | web-research-coding-5m-1.1.0 | |
323ddb17a4bea13557f95bf7 | train | repository_documentation | huggingface | https://huggingface.co/datasets/code-rag-bench/github-repos-python | code-rag-bench/github-repos-python | documentation | java | backend | Perform a deep multi-layer analysis of backend for a documentation 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": "code-rag-bench/github-repos-python", "source_url": "https://huggingface.co/datasets/code-rag-... | === 1. PROBLEM ===
Define the exact problem involving backend. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around backend. Use 'code-rag-bench/github-repos-python' as a source anchor and identify relevant APIs, dependencies... | web-research-coding-5m-1.1.0 | |
b3710ea889294dd91a5834d7 | train | scalability_analysis | pypi | https://pypi.org/project/flask/ | flask | admin_panel | swift | deep_learning | Perform a deep multi-layer analysis of deep_learning for a admin_panel 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": "flask", "source_url": "https://pypi.org/project/flask/", "source_type": "package", "topic": "... | === 1. PROBLEM ===
Define the exact problem involving deep_learning. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around deep_learning. Use 'flask' as a source anchor and identify relevant APIs, dependencies, versions, stand... | web-research-coding-5m-1.1.0 | |
b34ad247f728e7bc9ec98cf1 | train | refactoring_testability | huggingface | https://huggingface.co/datasets/Nan-Do/instructional_code-search-net-python | Nan-Do/instructional_code-search-net-python | dashboard | html | fullstack | Refactor a html system related to fullstack. Focus on refactoring testability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Nan-Do/instructional_code-search-net-python", "source_url": "https://huggingface.co/datasets/... | === 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 | |
c7802fc0c9e49370989d694d | train | design_review | npm | https://www.npmjs.com/package/vite | vite | admin_panel | c | docker | Perform a professional design review of a admin_panel. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "vite", "source_url": "https://www.npmjs.com/package/vite", "source_type": "package", "topic":... | Review hierarchy, consistency, responsiveness, accessibility, interaction design, content clarity, and implementation feasibility. | web-research-coding-5m-1.1.0 | |
e5748d3a10695fd1dd12e986 | train | information_architecture | huggingface | https://huggingface.co/datasets/abanm/arjoonn-codechef-competitive-programming-ChatGPT4o | abanm/arjoonn-codechef-competitive-programming-ChatGPT4o | portfolio | dart | ci_cd | Design the information architecture for ci_cd. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "abanm/arjoonn-codechef-competitive-programming-ChatGPT4o", "source_url": "https://huggingface... | Organize content into logical categories, navigation levels, search, filtering, and discoverable paths. | web-research-coding-5m-1.1.0 | |
3ba96dc24c25ec4d28822a09 | train | security_analysis | codeberg | https://codeberg.org/nilikk/-webshop.com | nilikk/-webshop.com | saas | ruby | serverless | Perform a deep multi-layer analysis of serverless 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": "nilikk/-webshop.com", "source_url": "https://codeberg.org/nilikk/-webshop.com", "source_type"... | === 1. PROBLEM ===
Define the exact problem involving serverless. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around serverless. Use 'nilikk/-webshop.com' as a source anchor and identify relevant APIs, dependencies, version... | web-research-coding-5m-1.1.0 | |
d782b025e71e0012817272af | train | design_system | codeberg | https://codeberg.org/argrento/100-exercises-to-learn-rust | argrento/100-exercises-to-learn-rust | saas | ruby | docker | Create a scalable design system for a saas. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "argrento/100-exercises-to-learn-rust", "source_url": "https://codeberg.org/argrento/100-exerc... | Define tokens, typography, spacing, components, variants, states, responsive rules, accessibility, and documentation. | web-research-coding-5m-1.1.0 | |
14d2be7278732efb44605fe4 | train | debugging | stackexchange | https://stackoverflow.com/questions/14727044/what-is-the-difference-between-types-string-and-string | What is the difference between types String and string? | documentation | python | machine_learning | Create a realistic python debugging problem involving machine_learning. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "What is the difference between types String and string?", "source_url": "https://stackoverflo... | Provide symptoms, reproduction strategy, diagnostic steps, root-cause analysis, minimal fix, and regression coverage. | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
7974e3858bfddac2c24194e6 | train | documentation_experience | mdn | https://developer.mozilla.org/en-US/docs/Web/HTTP | HTTP | blog | python | web_accessibility | Perform a deep developer-experience analysis for a python project involving web_accessibility. | {"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... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
8d2b23069fbebccbed5e3225 | train | debugging_experience | web_docs | https://docs.python.org/3/ | Python Documentation | documentation | ruby | nlp | Perform a deep developer-experience analysis for a ruby project involving nlp. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Python Documentation", "source_url": "https://docs.python.org/3/", "source_type": "documentat... | === 1. 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 | |
611d2ceaaa3a4149ce4ffdcb | train | performance_analysis | web_docs | https://docs.python.org/3/ | Python Documentation | documentation | javascript | frontend | Perform a deep multi-layer analysis of frontend for a documentation using javascript. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Python Documentation", "source_url": "https://docs.python.org/3/", "source_type": "documentat... | === 1. PROBLEM ===
Define the exact problem involving frontend. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around frontend. Use 'Python Documentation' as a source anchor and identify relevant APIs, dependencies, versions, ... | web-research-coding-5m-1.1.0 | |
ce1b60a43887bb5079e20d92 | train | research_plan | web_docs | https://fastapi.tiangolo.com/ | FastAPI Documentation | developer_tool | ruby | caching | Build a structured research plan to deeply understand caching. | {"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... | === GOAL ===
Produce a reliable, current, and actionable understanding of caching.
=== PHASES ===
1. Orientation — skim official docs and README.
2. Deep read — study specs, RFCs, changelogs.
3. Hands-on — reproduce examples locally.
4. Comparison — compare alternatives and trade-offs.
5. Synthesis — write findings wi... | web-research-coding-5m-1.1.0 | |
6934472734ae4a5d6b60d7d4 | train | css_generation | mdn | https://developer.mozilla.org/en-US/docs/Web/CSS | CSS | admin_panel | python | ci_cd | Create responsive CSS for a admin_panel. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "CSS", "source_url": "https://developer.mozilla.org/en-US/docs/Web/CSS", "source_type": "docum... | Use reusable rules, responsive layouts, scalable typography, spacing, focus states, and mobile support. | :root {
--space: 1rem;
}
* {
box-sizing: border-box;
}
body {
margin: 0;
font-family: system-ui, sans-serif;
}
.container {
width: min(100% - 2rem, 1200px);
margin-inline: auto;
} | web-research-coding-5m-1.1.0 |
aadcb671dd7a66d66bc24276 | train | repository_comparison | codeberg | https://codeberg.org/plaublin/100-exercises-to-learn-rust | plaublin/100-exercises-to-learn-rust | finance | css | html | Perform a deep multi-layer analysis of html for a finance using css. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "plaublin/100-exercises-to-learn-rust", "source_url": "https://codeberg.org/plaublin/100-exerc... | === 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 'plaublin/100-exercises-to-learn-rust' as a source anchor and identify relevant APIs, dependencies, ve... | web-research-coding-5m-1.1.0 | |
856221a4fb922eef4d3d3de1 | train | algorithm_design | gitlab | https://gitlab.com/msts-public/general/typescript-cacheable | msts-public/general/typescript-cacheable | ecommerce | typescript | nextjs | Design a typescript algorithm for a nextjs problem. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "msts-public/general/typescript-cacheable", "source_url": "https://gitlab.com/msts-public/gene... | State assumptions, algorithm, complexity, edge cases, correctness reasoning, and testing strategy. | web-research-coding-5m-1.1.0 | |
af9a9fd9b8b18a4d676d9d94 | train | research_plan | mdn | https://developer.mozilla.org/en-US/docs/Web/HTML | HTML | saas | c | data_structures | Build a structured research plan to deeply understand data_structures. | {"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... | === GOAL ===
Produce a reliable, current, and actionable understanding of data_structures.
=== 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... | web-research-coding-5m-1.1.0 | |
1a939cc48bda290d63aba36b | train | multi_hop_research | pypi | https://pypi.org/project/beautifulsoup4/ | beautifulsoup4 | finance | typescript | cloud | Perform multi-hop research about cloud: 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": "beautifulsoup4", "source_url": "https://pypi.org/project/beautifulsoup4/", "source_type": "pa... | === HOP 1 ===
Start at: beautifulsoup4
https://pypi.org/project/beautifulsoup4/
Extract core claims and references.
=== HOP 2 ===
Follow references to official docs, RFCs, or specs.
Extract primary-source evidence.
=== HOP 3 ===
Check community discussions for real-world issues.
Extract failure modes and workarounds.... | web-research-coding-5m-1.1.0 | |
bc2e7b7667968c1ada683c4e | train | design_tokens | stackexchange | https://stackoverflow.com/questions/2595176/which-machine-learning-classifier-to-choose-in-general | Which machine learning classifier to choose, in general? | documentation | sql | testing | Create design tokens for a documentation. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Which machine learning classifier to choose, in general?", "source_url": "https://stackoverfl... | Define reusable tokens for typography, spacing, radii, sizing, elevation, interaction states, and responsive behavior. | web-research-coding-5m-1.1.0 | |
f531de4413a7c1a6dc2fca41 | train | maintainability_analysis | codeberg | https://codeberg.org/ccoenen/Advent-of-Code-2021-JavaScript | ccoenen/Advent-of-Code-2021-JavaScript | documentation | rust | data_engineering | Perform a deep multi-layer analysis of data_engineering for a documentation using rust. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "ccoenen/Advent-of-Code-2021-JavaScript", "source_url": "https://codeberg.org/ccoenen/Advent-o... | === 1. PROBLEM ===
Define the exact problem involving data_engineering. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around data_engineering. Use 'ccoenen/Advent-of-Code-2021-JavaScript' as a source anchor and identify relev... | web-research-coding-5m-1.1.0 | |
0badbb23cd091c34be37cc7f | train | ux_analysis | web_docs | https://docs.djangoproject.com/ | Django Documentation | education | sql | authorization | Perform a deep multi-layer analysis of authorization for a education using sql. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Django Documentation", "source_url": "https://docs.djangoproject.com/", "source_type": "docum... | === 1. PROBLEM ===
Define the exact problem involving authorization. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around authorization. Use 'Django Documentation' as a source anchor and identify relevant APIs, dependencies, ... | web-research-coding-5m-1.1.0 | |
1591abc50c099f97814f99b9 | train | maintainability_analysis | pypi | https://pypi.org/project/fastapi/ | fastapi | dashboard | python | authorization | Perform a deep multi-layer analysis of authorization for a dashboard 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": "fastapi", "source_url": "https://pypi.org/project/fastapi/", "source_type": "package", "topic... | === 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 'fastapi' as a source anchor and identify relevant APIs, dependencies, versions, sta... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
fc376a9c58d42d055741766f | train | research_plan | web_docs | https://docs.python.org/3/ | Python Documentation | dashboard | ruby | microservices | Build a structured research plan to deeply understand microservices. | {"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... | === GOAL ===
Produce a reliable, current, and actionable understanding of microservices.
=== 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 findi... | web-research-coding-5m-1.1.0 | |
6a27b93bcf2a0ead3eccff96 | train | landing_page | web_docs | https://nodejs.org/docs/latest/api/ | Node.js Documentation | education | scala | algorithms | Design a landing page for a algorithms product. | {"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": "... | Include hero, value proposition, features, CTA, FAQ, responsive behavior, SEO, accessibility, and analytics. | web-research-coding-5m-1.1.0 | |
44e11d95d3811c49eeec2e83 | train | evidence_chain_analysis | stackexchange | https://stackoverflow.com/questions/24718709/reactjs-does-render-get-called-any-time-setstate-is-called | ReactJS - Does render get called any time "setState" is called? | social_app | html | css | Perform a deep multi-layer analysis of css for a social_app 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": "ReactJS - Does render get called any time "setState" is called?", "source_url": "ht... | === 1. PROBLEM ===
Define the exact problem involving css. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around css. Use 'ReactJS - Does render get called any time "setState" is called?' as a source anchor and ident... | web-research-coding-5m-1.1.0 | |
72859e1d5313fc1116cd1021 | train | cli_experience | web_docs | https://git-scm.com/doc | Git Documentation | blog | javascript | web_performance | Perform a deep developer-experience analysis for a javascript project involving web_performance. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Git Documentation", "source_url": "https://git-scm.com/doc", "source_type": "documentation", ... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
3cb19827ad44c77041985cc0 | train | refactoring_security | pypi | https://pypi.org/project/scikit-learn/ | scikit-learn | community | shell | user_experience | Refactor a shell system related to user_experience. Focus on refactoring security. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "scikit-learn", "source_url": "https://pypi.org/project/scikit-learn/", "source_type": "packag... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
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 | |
c176087931dfd351055fdabf | train | design_system | pypi | https://pypi.org/project/httpx/ | httpx | education | css | security | Create a scalable design system for a education. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "httpx", "source_url": "https://pypi.org/project/httpx/", "source_type": "package", "topic": "... | Define tokens, typography, spacing, components, variants, states, responsive rules, accessibility, and documentation. | web-research-coding-5m-1.1.0 | |
fe0965b6a0838642f2798ae3 | train | landing_page | gitlab | https://gitlab.com/comentario/comentario | comentario/comentario | blog | cpp | api_design | Design a landing page for a api_design product. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "comentario/comentario", "source_url": "https://gitlab.com/comentario/comentario", "source_typ... | Include hero, value proposition, features, CTA, FAQ, responsive behavior, SEO, accessibility, and analytics. | web-research-coding-5m-1.1.0 | |
f96712b18840f3e1f05d9d46 | train | research_plan | mdn | https://developer.mozilla.org/en-US/docs/Web/API | Web APIs | finance | shell | microservices | Build a structured research plan to deeply understand microservices. | {"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": "... | === GOAL ===
Produce a reliable, current, and actionable understanding of microservices.
=== 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 findi... | web-research-coding-5m-1.1.0 | |
d441b8678f1b620a905e7f00 | train | design_consistency | mdn | https://developer.mozilla.org/en-US/docs/Web/Accessibility | Accessibility | portfolio | cpp | web_performance | Audit design consistency across a portfolio. | {"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", "... | Check repeated patterns, component variants, spacing, typography, interaction states, terminology, and responsiveness. | web-research-coding-5m-1.1.0 | |
98d688d8803a8bf165456585 | train | root_cause_analysis | huggingface | https://huggingface.co/datasets/CoIR-Retrieval/CodeSearchNet-ccr-javascript-queries-corpus | CoIR-Retrieval/CodeSearchNet-ccr-javascript-queries-corpus | documentation | ruby | user_experience | Perform a deep multi-layer analysis of user_experience for a documentation 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": "CoIR-Retrieval/CodeSearchNet-ccr-javascript-queries-corpus", "source_url": "https://huggingfa... | === 1. PROBLEM ===
Define the exact problem involving user_experience. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around user_experience. Use 'CoIR-Retrieval/CodeSearchNet-ccr-javascript-queries-corpus' as a source anchor ... | web-research-coding-5m-1.1.0 | |
be1e3023a7732b0e070aecc1 | train | design_review | stackexchange | https://stackoverflow.com/questions/134882/undoing-a-git-rebase | Undoing a git rebase | documentation | python | nodejs | Perform a professional design review of a documentation. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Undoing a git rebase", "source_url": "https://stackoverflow.com/questions/134882/undoing-a-gi... | Review hierarchy, consistency, responsiveness, accessibility, interaction design, content clarity, and implementation feasibility. | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
77d792a7ce64c307ba07527e | train | performance_fix | codeberg | https://codeberg.org/UI-Programming-23-24/01-Web-Basics-And-Git-Jack-Sweeney2 | UI-Programming-23-24/01-Web-Basics-And-Git-Jack-Sweeney2 | search_interface | python | developer_experience | Create a web-performance optimization plan for a search_interface. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "UI-Programming-23-24/01-Web-Basics-And-Git-Jack-Sweeney2", "source_url": "https://codeberg.or... | Measure first, then optimize bundle size, images, network requests, rendering, caching, and critical resources. | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
6572fc06cc203e44bd227ec7 | train | research_plan | gitlab | https://gitlab.com/pavel.krupala/pyqt-node-editor | pavel.krupala/pyqt-node-editor | marketplace | typescript | javascript | Build a structured research plan to deeply understand javascript. | {"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... | === GOAL ===
Produce a reliable, current, and actionable understanding of javascript.
=== PHASES ===
1. Orientation — skim official docs and README.
2. Deep read — study specs, RFCs, changelogs.
3. Hands-on — reproduce examples locally.
4. Comparison — compare alternatives and trade-offs.
5. Synthesis — write findings... | web-research-coding-5m-1.1.0 | |
c98fd76a09b1b2ec588acdc1 | train | architecture_analysis | huggingface | https://huggingface.co/datasets/mxzoo/CFFI-javascript-obfuscated-DPO | mxzoo/CFFI-javascript-obfuscated-DPO | finance | shell | html | Perform a deep multi-layer analysis of html for a finance 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": "mxzoo/CFFI-javascript-obfuscated-DPO", "source_url": "https://huggingface.co/datasets/mxzoo/C... | === 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 'mxzoo/CFFI-javascript-obfuscated-DPO' as a source anchor and identify relevant APIs, dependencies, ve... | web-research-coding-5m-1.1.0 | |
198a5204b2a745b06e6f6e13 | train | repository_issue_reasoning | huggingface | https://huggingface.co/datasets/codeparrot/github-code-clean | codeparrot/github-code-clean | dashboard | scala | debugging | Perform a deep multi-layer analysis of debugging for a dashboard using scala. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "codeparrot/github-code-clean", "source_url": "https://huggingface.co/datasets/codeparrot/gith... | === 1. PROBLEM ===
Define the exact problem involving debugging. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around debugging. Use 'codeparrot/github-code-clean' as a source anchor and identify relevant APIs, dependencies, ... | web-research-coding-5m-1.1.0 | |
728763ccc4b58dd07e6f8fd3 | train | design_consistency | github | https://github.com/unionlabs/union | unionlabs/union | finance | kotlin | caching | Audit design consistency across a finance. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "unionlabs/union", "source_url": "https://github.com/unionlabs/union", "source_type": "reposit... | Check repeated patterns, component variants, spacing, typography, interaction states, terminology, and responsiveness. | web-research-coding-5m-1.1.0 | |
86d7df2893f6b20fda7af067 | train | source_selection | stackexchange | https://stackoverflow.com/questions/3518002/how-can-i-set-the-default-value-for-an-html-select-element | How can I set the default value for an HTML <select> element? | ecommerce | shell | frontend | Select the most reliable sources to research frontend. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How can I set the default value for an HTML <select> element?", "source_url": "https://... | === 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 | |
97c1b75c60a510315281eba1 | train | code_explanation | codeberg | https://codeberg.org/import-benjamin/.dotfiles | import-benjamin/.dotfiles | documentation | typescript | debugging | Explain a typescript implementation related to debugging. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "import-benjamin/.dotfiles", "source_url": "https://codeberg.org/import-benjamin/.dotfiles", "... | Explain inputs, outputs, control flow, algorithms, complexity, edge cases, errors, and maintainability. | web-research-coding-5m-1.1.0 | |
03c49954e311c6884ab5d507 | train | fact_verification | huggingface | https://huggingface.co/datasets/HuggingFaceH4/testing_codealpaca_small | HuggingFaceH4/testing_codealpaca_small | developer_tool | c | open_source | Verify a technical claim about open_source. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "HuggingFaceH4/testing_codealpaca_small", "source_url": "https://huggingface.co/datasets/Huggi... | === CLAIM ===
A common claim about open_source.
=== VERIFICATION STEPS ===
1. Locate the primary source (docs, spec, RFC).
2. Reproduce the claim in a minimal environment.
3. Check version-specific behavior.
4. Identify edge cases and exceptions.
=== RESULT ===
Classify: confirmed / partially true / false / context-d... | web-research-coding-5m-1.1.0 | |
5a66f24413ccbb442d6299fe | train | refactoring_modularization | mdn | https://developer.mozilla.org/en-US/docs/Web/CSS | CSS | documentation | python | linux | Refactor a python system related to linux. 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... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
cabc64dd4dc5687e18d5dca9 | train | seo_fix | mdn | https://developer.mozilla.org/en-US/docs/Web/API | Web APIs | social_app | python | algorithms | Create an SEO improvement plan for a social_app about algorithms. | {"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": "... | Cover titles, descriptions, headings, canonical URLs, structured data, internal links, crawlability, and performance. | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
b01f7aa6f3937a8f90e6a784 | train | design_accessibility | mdn | https://developer.mozilla.org/en-US/docs/Web/API | Web APIs | landing_page | c | api_design | Audit accessibility for a landing_page. | {"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": "... | Check semantic structure, keyboard navigation, focus visibility, accessible names, labels, errors, contrast, and screen-reader behavior. | web-research-coding-5m-1.1.0 | |
c35042de22e12d9e0f29544c | train | performance_analysis | stackexchange | https://stackoverflow.com/questions/4181861/message-src-refspec-master-does-not-match-any-when-pushing-commits-in-git | Message 'src refspec master does not match any' when pushing commits in Git | admin_panel | rust | data_engineering | Perform a deep multi-layer analysis of data_engineering for a admin_panel using rust. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Message 'src refspec master does not match any' when pushing commits in Git", "source... | === 1. PROBLEM ===
Define the exact problem involving data_engineering. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around data_engineering. Use 'Message 'src refspec master does not match any' when pushing commits ... | web-research-coding-5m-1.1.0 | |
0e05c2a005e2ebfb353c692b | train | evidence_chain_analysis | pypi | https://pypi.org/project/pytest/ | pytest | education | php | design_system | Perform a deep multi-layer analysis of design_system for a education using php. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "pytest", "source_url": "https://pypi.org/project/pytest/", "source_type": "package", "topic":... | === 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 'pytest' as a source anchor and identify relevant APIs, dependencies, versions, stan... | web-research-coding-5m-1.1.0 | |
8d28b63e9e37421c47ebc1a2 | train | form_ui | huggingface | https://huggingface.co/datasets/kaydenfu/documentation-images | kaydenfu/documentation-images | portfolio | rust | python | Design an accessible form for python. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "kaydenfu/documentation-images", "source_url": "https://huggingface.co/datasets/kaydenfu/docum... | Use labels, validation, clear errors, keyboard navigation, appropriate autocomplete, and accessible status messaging. | web-research-coding-5m-1.1.0 | |
bbff9f14e365cb4e8a60f4c5 | train | integration_testing | stackexchange | https://stackoverflow.com/questions/3207219/how-do-i-list-all-files-of-a-directory | How do I list all files of a directory? | social_app | dart | nodejs | Design integration tests for a dart system involving nodejs. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How do I list all files of a directory?", "source_url": "https://stackoverflow.com/questions/... | Test real component boundaries, persistence, configuration, external interfaces, errors, cleanup, and realistic workflows. | web-research-coding-5m-1.1.0 | |
4cf626daf8af2f23b49eec3c | train | refactoring_dependency | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model | DOM | admin_panel | php | postgresql | Refactor a php system related to postgresql. Focus on refactoring dependency. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "DOM", "source_url": "https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model",... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Audit dependencies and isolate external integrations.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify developer-experienc... | web-research-coding-5m-1.1.0 | |
b31b81d80c5d07aee8657233 | train | algorithm_design | gitlab | https://gitlab.com/panoramax/clients/web-viewer | panoramax/clients/web-viewer | search_interface | kotlin | design_system | Design a kotlin algorithm for a design_system problem. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "panoramax/clients/web-viewer", "source_url": "https://gitlab.com/panoramax/clients/web-viewer... | State assumptions, algorithm, complexity, edge cases, correctness reasoning, and testing strategy. | web-research-coding-5m-1.1.0 | |
8092853aaee39b9c84fb06c6 | train | performance_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/CSS | CSS | portfolio | python | fullstack | Perform a deep multi-layer analysis of fullstack for a portfolio using python. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "CSS", "source_url": "https://developer.mozilla.org/en-US/docs/Web/CSS", "source_type": "docum... | === 1. PROBLEM ===
Define the exact problem involving fullstack. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around fullstack. Use 'CSS' as a source anchor and identify relevant APIs, dependencies, versions, standards, and ... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
2124cc3b89c19c3fedb6b3c2 | train | evidence_extraction | stackexchange | https://stackoverflow.com/questions/31048953/what-are-these-three-dots-in-react-doing | What are these three dots in React doing? | documentation | cpp | developer_experience | Extract verifiable evidence about developer_experience from the given source. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "What are these three dots in React doing?", "source_url": "https://stackoverflow.com/question... | === SOURCE ===
What are these three dots in React doing?
https://stackoverflow.com/questions/31048953/what-are-these-three-dots-in-react-doing
=== EVIDENCE ITEMS ===
1. Explicit claims made by the source
2. Code examples or API signatures
3. Version / compatibility statements
4. Performance or security notes
=== QUAL... | web-research-coding-5m-1.1.0 | |
130014d60f1460a65963fe1c | train | root_cause_analysis | web_docs | https://react.dev/ | React Documentation | landing_page | ruby | observability | Perform a deep multi-layer analysis of observability for a landing_page 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": "React Documentation", "source_url": "https://react.dev/", "source_type": "documentation", "to... | === 1. PROBLEM ===
Define the exact problem involving observability. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around observability. Use 'React Documentation' as a source anchor and identify relevant APIs, dependencies, v... | web-research-coding-5m-1.1.0 | |
69e53d6f3d1c5d4c53658de4 | train | design_system | npm | https://www.npmjs.com/package/react | react | search_interface | typescript | backend | Create a scalable design system for a search_interface. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "react", "source_url": "https://www.npmjs.com/package/react", "source_type": "package", "topic... | Define tokens, typography, spacing, components, variants, states, responsive rules, accessibility, and documentation. | web-research-coding-5m-1.1.0 | |
a6d9e97d449f3657a42c78df | train | design_components | stackexchange | https://stackoverflow.com/questions/134845/which-href-value-should-i-use-for-javascript-links-or-javascriptvoid0 | Which "href" value should I use for JavaScript links, "#" or "javascript:void(0)"? | productivity | dart | user_experience | Create a component architecture for a productivity. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Which "href" value should I use for JavaScript links, "#" or "javasc... | Define primitive components, composite components, variants, states, composition rules, and accessibility contracts. | web-research-coding-5m-1.1.0 | |
09031313a6c6d15775998274 | train | source_comparison | web_docs | https://www.typescriptlang.org/docs/ | TypeScript Documentation | landing_page | kotlin | postgresql | Compare multiple sources about postgresql and identify agreements, contradictions, and gaps. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "TypeScript Documentation", "source_url": "https://www.typescriptlang.org/docs/", "source_type... | === SOURCES ===
- TypeScript Documentation (https://www.typescriptlang.org/docs/)
- Official documentation
- Community discussions
=== AGREEMENTS ===
Identify claims supported by multiple independent sources.
=== CONTRADICTIONS ===
Identify conflicting claims and their likely cause (version differences, environment, ... | web-research-coding-5m-1.1.0 | |
3bf571128e071a9e73a370a3 | train | dependency_impact_analysis | codeberg | https://codeberg.org/0x0079/4ring | 0x0079/4ring | social_app | css | linux | Perform a deep multi-layer analysis of linux for a social_app using css. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "0x0079/4ring", "source_url": "https://codeberg.org/0x0079/4ring", "source_type": "repository"... | === 1. PROBLEM ===
Define the exact problem involving linux. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around linux. Use '0x0079/4ring' as a source anchor and identify relevant APIs, dependencies, versions, standards, and... | web-research-coding-5m-1.1.0 | |
8421223693e6f271b815d2df | train | source_comparison | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API | Fetch API | finance | javascript | debugging | Compare multiple sources about debugging and identify agreements, contradictions, and gaps. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Fetch API", "source_url": "https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API", "sour... | === SOURCES ===
- Fetch API (https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API)
- Official documentation
- Community discussions
=== AGREEMENTS ===
Identify claims supported by multiple independent sources.
=== CONTRADICTIONS ===
Identify conflicting claims and their likely cause (version differences, enviro... | web-research-coding-5m-1.1.0 | |
f6a2b4bbf4ccfe4d610b3289 | train | ux_design | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model | DOM | analytics | kotlin | data_structures | Design the complete UX flow of a analytics for data_structures. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "DOM", "source_url": "https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model",... | 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 | |
6b8f28f3e4aa6ac722de79e3 | train | documentation_page | pypi | https://pypi.org/project/pydantic/ | pydantic | marketplace | css | algorithms | Design a developer documentation page for algorithms. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "pydantic", "source_url": "https://pypi.org/project/pydantic/", "source_type": "package", "top... | Include navigation, overview, prerequisites, installation, examples, API reference, troubleshooting, and search. | web-research-coding-5m-1.1.0 | |
ae3a4d2ff29d11d6f6fb9f85 | train | responsive_website | pypi | https://pypi.org/project/requests/ | requests | saas | css | developer_experience | Design a complete responsive saas for developer_experience. | {"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... | Cover mobile, tablet, and desktop layouts, semantic structure, responsive components, accessibility, performance, and UX. | web-research-coding-5m-1.1.0 | |
11089b0e0982917a2006e390 | train | javascript_generation | pypi | https://pypi.org/project/typer/ | typer | productivity | swift | postgresql | Implement JavaScript interactions for a productivity. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "typer", "source_url": "https://pypi.org/project/typer/", "source_type": "package", "topic": "... | 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 |
823d67c6e7be25339a8eed97 | train | maintainability_analysis | stackexchange | https://stackoverflow.com/questions/6237295/how-can-i-update-node-js-and-npm-to-their-latest-versions | How can I update Node.js and npm to their latest versions? | portfolio | java | backend | Perform a deep multi-layer analysis of backend for a portfolio using java. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How can I update Node.js and npm to their latest versions?", "source_url": "https://stackover... | === 1. PROBLEM ===
Define the exact problem involving backend. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around backend. Use 'How can I update Node.js and npm to their latest versions?' as a source anchor and identify rel... | web-research-coding-5m-1.1.0 | |
277c28f4677d90cc1857a1ed | train | refactoring_testability | web_docs | https://kubernetes.io/docs/ | Kubernetes Documentation | search_interface | javascript | fullstack | Refactor a javascript system related to fullstack. Focus on refactoring testability. | {"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... | === 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 | |
2b335a2a06a3617f6361a1dc | train | system_analysis | github | https://github.com/appwrite/appwrite | appwrite/appwrite | social_app | shell | database | Perform a deep multi-layer analysis of database for a social_app 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": "appwrite/appwrite", "source_url": "https://github.com/appwrite/appwrite", "source_type": "rep... | === 1. PROBLEM ===
Define the exact problem involving database. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around database. Use 'appwrite/appwrite' as a source anchor and identify relevant APIs, dependencies, versions, sta... | web-research-coding-5m-1.1.0 | |
02986cb4a37a29e5778444b1 | train | visual_hierarchy | github | https://github.com/eugeneyan/applied-ml | eugeneyan/applied-ml | productivity | python | distributed_systems | Improve visual hierarchy in a productivity. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "eugeneyan/applied-ml", "source_url": "https://github.com/eugeneyan/applied-ml", "source_type"... | Use heading structure, typography, spacing, grouping, alignment, contrast, and consistent affordances. | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
20b4fea6c9103520c56627ad | train | refactoring_architecture | huggingface | https://huggingface.co/datasets/BatsResearch/trove-lib-documentation-assets | BatsResearch/trove-lib-documentation-assets | developer_tool | shell | linux | Refactor a shell system related to linux. Focus on refactoring architecture. | {"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/... | === 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 | |
c83e0ed3f63edbdd4a5c324d | train | deep_technical_analysis | huggingface | https://huggingface.co/datasets/pruna-test/documentation-media | pruna-test/documentation-media | marketplace | css | observability | Perform a deep multi-layer analysis of observability for a marketplace using css. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "pruna-test/documentation-media", "source_url": "https://huggingface.co/datasets/pruna-test/do... | === 1. PROBLEM ===
Define the exact problem involving observability. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around observability. Use 'pruna-test/documentation-media' as a source anchor and identify relevant APIs, depe... | web-research-coding-5m-1.1.0 | |
495566543b71fc23549eb630 | train | dependency_management_experience | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API | Fetch API | documentation | kotlin | fullstack | Perform a deep developer-experience analysis for a kotlin project involving fullstack. | {"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 | |
4d28b02c1ec05dab6caf019a | train | refactoring_modularization | codeberg | https://codeberg.org/veroxis/_cargo-index | veroxis/_cargo-index | productivity | go | javascript | Refactor a go system related to javascript. Focus on refactoring modularization. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "veroxis/_cargo-index", "source_url": "https://codeberg.org/veroxis/_cargo-index", "source_typ... | === 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 | |
4c9730fd251b70070308909b | train | build_experience | mdn | https://developer.mozilla.org/en-US/docs/Web/JavaScript | JavaScript | portfolio | java | nodejs | Perform a deep developer-experience analysis for a java project involving nodejs. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "JavaScript", "source_url": "https://developer.mozilla.org/en-US/docs/Web/JavaScript", "source... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
1962fc27e2349cd6c87a06f4 | train | repository_issue_reasoning | npm | https://www.npmjs.com/package/prettier | prettier | productivity | ruby | web_performance | Perform a deep multi-layer analysis of web_performance for a productivity 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": "prettier", "source_url": "https://www.npmjs.com/package/prettier", "source_type": "package", ... | === 1. PROBLEM ===
Define the exact problem involving web_performance. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around web_performance. Use 'prettier' as a source anchor and identify relevant APIs, dependencies, versions... | web-research-coding-5m-1.1.0 | |
4eb7a10c2ad779638766e882 | train | dashboard | mdn | https://developer.mozilla.org/en-US/docs/Web/JavaScript | JavaScript | search_interface | sql | api_design | Design a production dashboard for api_design. | {"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 navigation, KPIs, tables/charts, filters, loading states, empty states, errors, and responsive behavior. | web-research-coding-5m-1.1.0 | |
68a784fdc1227b3f44ec48d0 | train | ux_design | web_docs | https://docs.djangoproject.com/ | Django Documentation | finance | shell | postgresql | Design the complete UX flow of a finance for postgresql. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Django Documentation", "source_url": "https://docs.djangoproject.com/", "source_type": "docum... | 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 | |
a44426b32e2fdc03ee8ffebf | train | accessibility_analysis | pypi | https://pypi.org/project/uvicorn/ | uvicorn | social_app | cpp | computer_vision | Perform a deep multi-layer analysis of computer_vision for a social_app using cpp. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "uvicorn", "source_url": "https://pypi.org/project/uvicorn/", "source_type": "package", "topic... | === 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 'uvicorn' as a source anchor and identify relevant APIs, dependencies, versions,... | web-research-coding-5m-1.1.0 | |
fe0bd55bbe85066295d8ff06 | train | refactoring_dependency | codeberg | https://codeberg.org/jiacai2050/1History | jiacai2050/1History | productivity | java | deep_learning | Refactor a java system related to deep_learning. Focus on refactoring dependency. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "jiacai2050/1History", "source_url": "https://codeberg.org/jiacai2050/1History", "source_type"... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Audit dependencies and isolate external integrations.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify developer-experienc... | web-research-coding-5m-1.1.0 | |
3067eb8042270f70b045df74 | train | multi_layer_analysis | gitlab | https://gitlab.com/catamphetamine/libphonenumber-js | catamphetamine/libphonenumber-js | ecommerce | css | backend | Perform a deep multi-layer analysis of backend for a ecommerce using css. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "catamphetamine/libphonenumber-js", "source_url": "https://gitlab.com/catamphetamine/libphonen... | === 1. PROBLEM ===
Define the exact problem involving backend. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around backend. Use 'catamphetamine/libphonenumber-js' as a source anchor and identify relevant APIs, dependencies, ... | web-research-coding-5m-1.1.0 | |
c2ef89a33509dbac39801962 | train | developer_experience | gitlab | https://gitlab.com/pencillabs/ej/ej-application | pencillabs/ej/ej-application | dashboard | sql | testing | Perform a deep developer-experience analysis for a sql project involving testing. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "pencillabs/ej/ej-application", "source_url": "https://gitlab.com/pencillabs/ej/ej-application... | === 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 | |
2dc500d3a81bbe470e5efecf | train | research_summary | stackexchange | https://stackoverflow.com/questions/7073484/how-do-css-triangles-work | How do CSS triangles work? | marketplace | cpp | deep_learning | Summarize the current state of knowledge about deep_learning. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How do CSS triangles work?", "source_url": "https://stackoverflow.com/questions/7073484/how-d... | === OVERVIEW ===
deep_learning 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 ===
How do CSS trian... | web-research-coding-5m-1.1.0 | |
6c2ad7508e10efaf04aa1789 | train | root_cause_analysis | huggingface | https://huggingface.co/datasets/ratanon/claude-code | ratanon/claude-code | search_interface | java | microservices | Perform a deep multi-layer analysis of microservices for a search_interface 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": "ratanon/claude-code", "source_url": "https://huggingface.co/datasets/ratanon/claude-code", "s... | === 1. PROBLEM ===
Define the exact problem involving microservices. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around microservices. Use 'ratanon/claude-code' as a source anchor and identify relevant APIs, dependencies, v... | web-research-coding-5m-1.1.0 | |
8a907018c3965b17d938173c | train | information_architecture | stackexchange | https://stackoverflow.com/questions/12952729/how-to-understand-locality-sensitive-hashing | How to understand Locality Sensitive Hashing? | documentation | rust | software_architecture | Design the information architecture for software_architecture. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How to understand Locality Sensitive Hashing?", "source_url": "https://stackoverflow.com/ques... | Organize content into logical categories, navigation levels, search, filtering, and discoverable paths. | web-research-coding-5m-1.1.0 | |
afef4757e3fc78fe02803333 | train | accessibility_fix | mdn | https://developer.mozilla.org/en-US/docs/Web/Performance | Performance | dashboard | kotlin | developer_experience | Create an accessibility remediation plan for a dashboard. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Performance", "source_url": "https://developer.mozilla.org/en-US/docs/Web/Performance", "sour... | Check semantic HTML, keyboard navigation, focus management, accessible names, labels, errors, contrast, and screen-reader behavior. | web-research-coding-5m-1.1.0 | |
dce4d8131798dbe1107bc0d4 | train | api_design | pypi | https://pypi.org/project/httpx/ | httpx | saas | c | redis | Design a production API for a redis application. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "httpx", "source_url": "https://pypi.org/project/httpx/", "source_type": "package", "topic": "... | Specify resources, endpoints, schemas, validation, authentication, authorization, errors, pagination, versioning, idempotency, and tests. | web-research-coding-5m-1.1.0 | |
895c040877e71afe6977d833 | train | performance_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/API | Web APIs | search_interface | c | mongodb | Perform a deep multi-layer analysis of mongodb for a search_interface using c. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Web APIs", "source_url": "https://developer.mozilla.org/en-US/docs/Web/API", "source_type": "... | === 1. PROBLEM ===
Define the exact problem involving mongodb. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around mongodb. Use 'Web APIs' as a source anchor and identify relevant APIs, dependencies, versions, standards, and... | web-research-coding-5m-1.1.0 | |
9cf7607d4c00c5bf7b8e855c | train | dependency_management_experience | stackexchange | https://stackoverflow.com/questions/5767325/how-can-i-remove-a-specific-item-from-an-array-in-javascript | How can I remove a specific item from an array in JavaScript? | finance | typescript | python | Perform a deep developer-experience analysis for a typescript project involving python. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How can I remove a specific item from an array in JavaScript?", "source_url": "https://stacko... | === 1. 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 | |
0ccda776995826e4410fc480 | train | repository_dependency_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/API | Web APIs | developer_tool | scala | security | Perform a deep multi-layer analysis of security for a developer_tool using scala. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Web APIs", "source_url": "https://developer.mozilla.org/en-US/docs/Web/API", "source_type": "... | === 1. PROBLEM ===
Define the exact problem involving security. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around security. Use 'Web APIs' as a source anchor and identify relevant APIs, dependencies, versions, standards, a... | web-research-coding-5m-1.1.0 | |
d35258e8bc2923ca49f9cfe7 | train | dependency_impact_analysis | github | https://github.com/jobbole/awesome-python-cn | jobbole/awesome-python-cn | landing_page | ruby | nodejs | Perform a deep multi-layer analysis of nodejs for a landing_page 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": "jobbole/awesome-python-cn", "source_url": "https://github.com/jobbole/awesome-python-cn", "so... | === 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 'jobbole/awesome-python-cn' as a source anchor and identify relevant APIs, dependencies, versions,... | web-research-coding-5m-1.1.0 | |
b7a0bf1b4e291bacc000d6f2 | train | source_selection | huggingface | https://huggingface.co/datasets/pruna-test/documentation-media | pruna-test/documentation-media | dashboard | scala | nodejs | Select the most reliable sources to research nodejs. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "pruna-test/documentation-media", "source_url": "https://huggingface.co/datasets/pruna-test/do... | === 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 | |
08d90d876efbadaceee746f9 | train | tradeoff_analysis | web_docs | https://kubernetes.io/docs/ | Kubernetes Documentation | social_app | rust | data_structures | Perform a deep multi-layer analysis of data_structures for a social_app using rust. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "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 | |
9a80e9c3dfca66d9778b113b | train | css_generation | huggingface | https://huggingface.co/datasets/aheadmint/machine-learning-glossary-ai | aheadmint/machine-learning-glossary-ai | finance | cpp | redis | Create responsive CSS for a finance. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "aheadmint/machine-learning-glossary-ai", "source_url": "https://huggingface.co/datasets/ahead... | Use reusable rules, responsive layouts, scalable typography, spacing, focus states, and mobile support. | :root {
--space: 1rem;
}
* {
box-sizing: border-box;
}
body {
margin: 0;
font-family: system-ui, sans-serif;
}
.container {
width: min(100% - 2rem, 1200px);
margin-inline: auto;
} | web-research-coding-5m-1.1.0 |
3fe05694d1dae30e25288cb6 | train | design_tokens | huggingface | https://huggingface.co/datasets/finbarr/rlvr-code-data-javascript-edited | finbarr/rlvr-code-data-javascript-edited | documentation | swift | debugging | Create design tokens for a documentation. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "finbarr/rlvr-code-data-javascript-edited", "source_url": "https://huggingface.co/datasets/fin... | Define reusable tokens for typography, spacing, radii, sizing, elevation, interaction states, and responsive behavior. | web-research-coding-5m-1.1.0 | |
c24645a9e987c0765d626b2e | train | refactoring_readability | stackexchange | https://stackoverflow.com/questions/252703/what-is-the-difference-between-pythons-list-methods-append-and-extend | What is the difference between Python's list methods append and extend? | ecommerce | c | deep_learning | Refactor a c system related to deep_learning. Focus on refactoring readability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "What is the difference between Python's list methods append and extend?", "source_url": "... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Improve naming, control flow, function boundaries, and local reasoning.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify d... | web-research-coding-5m-1.1.0 | |
bceadc77794989b774c723b1 | train | error_message_design | stackexchange | https://stackoverflow.com/questions/53332321/react-hook-warnings-for-async-function-in-useeffect-useeffect-function-must-ret | React Hook Warnings for async function in useEffect: useEffect function must return a cleanup function or nothing | developer_tool | rust | authentication | Perform a deep developer-experience analysis for a rust project involving authentication. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "React Hook Warnings for async function in useEffect: useEffect function must return a cleanup... | === 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 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.