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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
638e0b31370157fbef8d1da2 | train | dependency_management_experience | stackexchange | https://stackoverflow.com/questions/52522565/git-is-not-working-after-macos-update-xcrun-error-invalid-active-developer-p | Git is not working after macOS update ("xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools") | marketplace | swift | algorithms | Perform a deep developer-experience analysis for a swift project involving algorithms. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Git is not working after macOS update ("xcrun: error: invalid active developer path (/Li... | === 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 | |
abe66f8eb989f3b4c322ef33 | train | technical_research | stackexchange | https://stackoverflow.com/questions/43040721/how-to-update-nested-state-properties-in-react | How to update nested state properties in React | community | php | serverless | Perform a technical research task about serverless, focused on implementation details. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How to update nested state properties in React", "source_url": "https://stackoverflow.com/que... | === SCOPE ===
Technical behavior of serverless.
=== QUESTIONS ===
- What are the inputs, outputs, and invariants?
- What are the performance characteristics?
- What are the security implications?
- What are the compatibility constraints?
=== EVIDENCE ===
- How to update nested state properties in React (https://stack... | web-research-coding-5m-1.1.0 | |
a98d7c53fda8bbf88ab65515 | train | performance_fix | mdn | https://developer.mozilla.org/en-US/docs/Web/HTML | HTML | ecommerce | java | caching | Create a web-performance optimization plan for a ecommerce. | {"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... | Measure first, then optimize bundle size, images, network requests, rendering, caching, and critical resources. | web-research-coding-5m-1.1.0 | |
51688e5f759eb9e9f40edc48 | train | multi_hop_research | stackexchange | https://stackoverflow.com/questions/3790935/can-i-hide-the-html5-number-input-s-spin-box | Can I hide the HTML5 number input’s spin box? | blog | sql | frontend | Perform multi-hop research about frontend: 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": "Can I hide the HTML5 number input’s spin box?", "source_url": "https://stackoverflow.com/ques... | === HOP 1 ===
Start at: Can I hide the HTML5 number input’s spin box?
https://stackoverflow.com/questions/3790935/can-i-hide-the-html5-number-input-s-spin-box
Extract core claims and references.
=== HOP 2 ===
Follow references to official docs, RFCs, or specs.
Extract primary-source evidence.
=== HOP 3 ===
Check comm... | web-research-coding-5m-1.1.0 | |
2849644df77ef206172655f8 | train | code_review | gitlab | https://gitlab.com/gitlab-org/gitlab-docs | gitlab-org/gitlab-docs | community | ruby | docker | Perform a production code review of ruby code related to docker. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "gitlab-org/gitlab-docs", "source_url": "https://gitlab.com/gitlab-org/gitlab-docs", "source_t... | Review correctness, security, performance, readability, architecture, testing, maintainability, and error handling. | web-research-coding-5m-1.1.0 | |
1f426bdf42c4caa2077d9094 | train | design_accessibility | codeberg | https://codeberg.org/lexxy23/_cargo-index | lexxy23/_cargo-index | social_app | cpp | nodejs | Audit accessibility for a social_app. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "lexxy23/_cargo-index", "source_url": "https://codeberg.org/lexxy23/_cargo-index", "source_typ... | Check semantic structure, keyboard navigation, focus visibility, accessible names, labels, errors, contrast, and screen-reader behavior. | web-research-coding-5m-1.1.0 | |
c64ece2db13907f6716ab1ed | train | multi_hop_research | huggingface | https://huggingface.co/datasets/ceyron/machine-learning-and-simulation | ceyron/machine-learning-and-simulation | portfolio | c | user_experience | Perform multi-hop research about user_experience: start from a source, follow references, and combine findings. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "ceyron/machine-learning-and-simulation", "source_url": "https://huggingface.co/datasets/ceyro... | === HOP 1 ===
Start at: ceyron/machine-learning-and-simulation
https://huggingface.co/datasets/ceyron/machine-learning-and-simulation
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 rea... | web-research-coding-5m-1.1.0 | |
a738ab6f497e4b088bc3ff92 | train | risk_analysis | stackexchange | https://stackoverflow.com/questions/586182/how-can-i-insert-an-item-into-an-array-at-a-specific-index | How can I insert an item into an array at a specific index? | education | php | security | Perform a deep multi-layer analysis of security 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": "How can I insert an item into an array at a specific index?", "source_url": "https://stackove... | === 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 'How can I insert an item into an array at a specific index?' as a source anchor and identify ... | web-research-coding-5m-1.1.0 | |
5bc5ef658b1f69655c46c1c2 | train | local_development_experience | huggingface | https://huggingface.co/datasets/hotchpotch/multilingual_cc_news | hotchpotch/multilingual_cc_news | developer_tool | java | debugging | Perform a deep developer-experience analysis for a java project involving debugging. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "hotchpotch/multilingual_cc_news", "source_url": "https://huggingface.co/datasets/hotchpotch/m... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
7ea18939c21ed61c61ed5691 | train | design_tokens | 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? | community | sql | react | Create design tokens for a community. | {"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... | Define reusable tokens for typography, spacing, radii, sizing, elevation, interaction states, and responsive behavior. | web-research-coding-5m-1.1.0 | |
67becc43cb4f1c094ccb5efd | train | refactoring_maintainability | stackexchange | https://stackoverflow.com/questions/27991366/what-is-the-difference-between-state-and-props-in-react | What is the difference between state and props in React? | productivity | shell | authentication | Refactor a shell system related to authentication. Focus on refactoring maintainability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "What is the difference between state and props in React?", "source_url": "https://stackoverfl... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Improve cohesion, reduce coupling, isolate volatile behavior, and remove duplication.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.... | web-research-coding-5m-1.1.0 | |
f1cff8596299d3e60c246072 | train | performance_fix | github | https://github.com/lutzroeder/netron | lutzroeder/netron | community | kotlin | user_experience | Create a web-performance optimization plan for a community. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "lutzroeder/netron", "source_url": "https://github.com/lutzroeder/netron", "source_type": "rep... | Measure first, then optimize bundle size, images, network requests, rendering, caching, and critical resources. | web-research-coding-5m-1.1.0 | |
eb14daec8f949ee07f95e492 | train | refactoring_observability | npm | https://www.npmjs.com/package/hono | hono | education | php | docker | Refactor a php system related to docker. Focus on refactoring observability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "hono", "source_url": "https://www.npmjs.com/package/hono", "source_type": "package", "topic":... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Improve logging, metrics, tracing, diagnostics, and failure visibility.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify d... | web-research-coding-5m-1.1.0 | |
c2db7373af479c17a250f751 | train | local_development_experience | npm | https://www.npmjs.com/package/react | react | community | html | nodejs | Perform a deep developer-experience analysis for a html project involving nodejs. | {"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... | === 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 | |
22c246b9d2b7d57a7361122e | train | developer_onboarding | github | https://github.com/n8n-io/n8n | n8n-io/n8n | dashboard | cpp | debugging | Perform a deep developer-experience analysis for a cpp project involving debugging. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "n8n-io/n8n", "source_url": "https://github.com/n8n-io/n8n", "source_type": "repository", "top... | === 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 | |
254f8aaf2727c06a88cffb4e | train | ui_design | mdn | https://developer.mozilla.org/en-US/docs/Web/HTTP | HTTP | saas | python | ci_cd | Design a production-quality UI for a saas focused on ci_cd. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "HTTP", "source_url": "https://developer.mozilla.org/en-US/docs/Web/HTTP", "source_type": "doc... | Define layout, typography, spacing, hierarchy, components, states, responsive behavior, and accessibility. | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
5b1ccde5ac3ef2e16a1f29c4 | train | performance_analysis | huggingface | https://huggingface.co/datasets/IFM/Code-Reasoning | IFM/Code-Reasoning | portfolio | scala | debugging | Perform a deep multi-layer analysis of debugging for a portfolio 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": "IFM/Code-Reasoning", "source_url": "https://huggingface.co/datasets/IFM/Code-Reasoning", "sou... | === 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 'IFM/Code-Reasoning' as a source anchor and identify relevant APIs, dependencies, versions, ... | web-research-coding-5m-1.1.0 | |
dd56beb15d8a24d2f3731b8c | train | upgrade_experience | mdn | https://developer.mozilla.org/en-US/docs/Web/Accessibility | Accessibility | blog | javascript | microservices | Perform a deep developer-experience analysis for a javascript project involving microservices. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Accessibility", "source_url": "https://developer.mozilla.org/en-US/docs/Web/Accessibility", "... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
2d8f72442dfe46f3307a532c | train | error_message_design | stackexchange | https://stackoverflow.com/questions/1776915/how-can-i-center-an-absolutely-positioned-element-in-a-div | How can I center an absolutely positioned element in a div? | community | sql | frontend | Perform a deep developer-experience analysis for a sql project involving frontend. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How can I center an absolutely positioned element in a div?", "source_url": "https://stackove... | === 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 | |
fed9e2645872cefcc1625b56 | train | accessibility_analysis | stackexchange | https://stackoverflow.com/questions/1033156/how-can-i-write-ahover-in-inline-css | How can I write 'a:hover' in inline CSS? | education | javascript | redis | Perform a deep multi-layer analysis of redis for a education using javascript. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How can I write 'a:hover' in inline CSS?", "source_url": "https://stackoverflow.com/q... | === 1. PROBLEM ===
Define the exact problem involving redis. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around redis. Use 'How can I write 'a:hover' in inline CSS?' as a source anchor and identify relevant APIs, de... | web-research-coding-5m-1.1.0 | |
995c896d1132a4fcb2c29616 | train | interaction_design | npm | https://www.npmjs.com/package/prettier | prettier | marketplace | typescript | css | Design interaction states for a marketplace. | {"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", ... | Specify default, hover, focus, active, disabled, loading, success, error, and empty states. | web-research-coding-5m-1.1.0 | |
501c5d32705d8d2a6d13faa1 | train | documentation_lookup | npm | https://www.npmjs.com/package/tailwindcss | tailwindcss | saas | kotlin | design_system | Find and summarize the relevant documentation for design_system. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "tailwindcss", "source_url": "https://www.npmjs.com/package/tailwindcss", "source_type": "pack... | === RELEVANT DOCS ===
- tailwindcss
https://www.npmjs.com/package/tailwindcss
- Official project documentation
- API reference
=== KEY SECTIONS ===
- Getting started
- API reference
- Configuration
- Troubleshooting
=== SUMMARY ===
Summarize each section in 1–3 sentences and quote exact signatures where relevant. | web-research-coding-5m-1.1.0 | |
bdb3c867e7b9182e14a8e366 | train | evidence_extraction | gitlab | https://gitlab.com/john.carroll.p/rschedule | john.carroll.p/rschedule | community | python | software_architecture | Extract verifiable evidence about software_architecture from the given source. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "john.carroll.p/rschedule", "source_url": "https://gitlab.com/john.carroll.p/rschedule", "sour... | === SOURCE ===
john.carroll.p/rschedule
https://gitlab.com/john.carroll.p/rschedule
=== EVIDENCE ITEMS ===
1. Explicit claims made by the source
2. Code examples or API signatures
3. Version / compatibility statements
4. Performance or security notes
=== QUALITY CHECK ===
- Is the claim specific and testable?
- Is th... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
dc177b24cbebede86fba9f79 | train | algorithm_design | pypi | https://pypi.org/project/pydantic/ | pydantic | developer_tool | dart | data_structures | Design a dart algorithm for a data_structures problem. | {"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... | State assumptions, algorithm, complexity, edge cases, correctness reasoning, and testing strategy. | web-research-coding-5m-1.1.0 | |
97e900cbb7ea6ed9e589dbf8 | train | visual_hierarchy | mdn | https://developer.mozilla.org/en-US/docs/Web/HTTP | HTTP | blog | cpp | caching | Improve visual hierarchy in a blog. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "HTTP", "source_url": "https://developer.mozilla.org/en-US/docs/Web/HTTP", "source_type": "doc... | Use heading structure, typography, spacing, grouping, alignment, contrast, and consistent affordances. | web-research-coding-5m-1.1.0 | |
9daf64a7233e0fb889bc69b0 | train | refactoring_performance | codeberg | https://codeberg.org/kawas44/2025-aoc-python | kawas44/2025-aoc-python | blog | dart | redis | Refactor a dart system related to redis. Focus on refactoring performance. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "kawas44/2025-aoc-python", "source_url": "https://codeberg.org/kawas44/2025-aoc-python", "sour... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Reduce unnecessary computation, allocations, I/O, and network requests.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify d... | web-research-coding-5m-1.1.0 | |
636690dd15cbe75b959b5209 | train | ux_analysis | huggingface | https://huggingface.co/datasets/smcleod/golang-programming-style-best-practices | smcleod/golang-programming-style-best-practices | analytics | swift | microservices | Perform a deep multi-layer analysis of microservices for a analytics 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": "smcleod/golang-programming-style-best-practices", "source_url": "https://huggingface.co/datas... | === 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 'smcleod/golang-programming-style-best-practices' as a source anchor and identify re... | web-research-coding-5m-1.1.0 | |
67507bf57df69b6f23ab213e | train | dashboard | github | https://github.com/ashishpatel26/500-AI-Machine-learning-Deep-learning-Computer-vision-NLP-Projects-with-code | ashishpatel26/500-AI-Machine-learning-Deep-learning-Computer-vision-NLP-Projects-with-code | marketplace | java | postgresql | Design a production dashboard for postgresql. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "ashishpatel26/500-AI-Machine-learning-Deep-learning-Computer-vision-NLP-Projects-with-code", ... | Include navigation, KPIs, tables/charts, filters, loading states, empty states, errors, and responsive behavior. | web-research-coding-5m-1.1.0 | |
611054f35da49ee0582ef684 | train | source_comparison | stackexchange | https://stackoverflow.com/questions/8318911/why-does-html-think-chucknorris-is-a-color | Why does HTML think “chucknorris” is a color? | landing_page | rust | deep_learning | Compare multiple sources about deep_learning 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": "Why does HTML think “chucknorris” is a color?", "source_url": "https://stackoverflow.com/ques... | === SOURCES ===
- Why does HTML think “chucknorris” is a color? (https://stackoverflow.com/questions/8318911/why-does-html-think-chucknorris-is-a-color)
- Official documentation
- Community discussions
=== AGREEMENTS ===
Identify claims supported by multiple independent sources.
=== CONTRADICTIONS ===
Identify confli... | web-research-coding-5m-1.1.0 | |
60d3acd36551affd5ed4ff45 | train | refactoring_observability | gitlab | https://gitlab.com/reubenlillie/eleventy-dot-js-blog | reubenlillie/eleventy-dot-js-blog | productivity | rust | docker | Refactor a rust system related to docker. Focus on refactoring observability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "reubenlillie/eleventy-dot-js-blog", "source_url": "https://gitlab.com/reubenlillie/eleventy-d... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Improve logging, metrics, tracing, diagnostics, and failure visibility.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify d... | web-research-coding-5m-1.1.0 | |
ce6d246193f9f89c7238f9f2 | train | unit_testing | gitlab | https://gitlab.com/reubenlillie/eleventy-dot-js-blog | reubenlillie/eleventy-dot-js-blog | documentation | css | design_system | Create a unit-testing strategy for css code involving design_system. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "reubenlillie/eleventy-dot-js-blog", "source_url": "https://gitlab.com/reubenlillie/eleventy-d... | Cover normal cases, edge cases, invalid inputs, failure modes, mocks, and regression tests. | web-research-coding-5m-1.1.0 | |
2778643c7b58678cbdf034ac | train | dependency_management_experience | pypi | https://pypi.org/project/transformers/ | transformers | developer_tool | kotlin | observability | Perform a deep developer-experience analysis for a kotlin project involving observability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "transformers", "source_url": "https://pypi.org/project/transformers/", "source_type": "packag... | === 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 | |
c9a3a14d0ba93ab7b0dbf51d | train | typescript_generation | huggingface | https://huggingface.co/datasets/livecodebench/code_generation_lite | livecodebench/code_generation_lite | search_interface | ruby | debugging | Implement TypeScript logic for a search_interface. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "livecodebench/code_generation_lite", "source_url": "https://huggingface.co/datasets/livecodeb... | Use explicit types, interfaces, safe narrowing, validation, and maintainable modules. | function validateInput(value) {
if (!value || value.trim().length === 0) {
throw new Error("Input is required");
}
return value.trim();
} | web-research-coding-5m-1.1.0 |
6c3411667eda7020cc5daf56 | train | dashboard | huggingface | https://huggingface.co/datasets/NickyNicky/Code-290k-labels-programming_languages-NO_Chatgpt | NickyNicky/Code-290k-labels-programming_languages-NO_Chatgpt | saas | c | sql | Design a production dashboard for sql. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "NickyNicky/Code-290k-labels-programming_languages-NO_Chatgpt", "source_url": "https://hugging... | Include navigation, KPIs, tables/charts, filters, loading states, empty states, errors, and responsive behavior. | web-research-coding-5m-1.1.0 | |
509720bbe1d045b32fe9c838 | train | refactoring_readability | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API | Fetch API | search_interface | ruby | database | Refactor a ruby system related to database. Focus on refactoring readability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Fetch API", "source_url": "https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API", "sour... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
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 | |
0acf9d090d8b8b52af46ac55 | train | source_comparison | huggingface | https://huggingface.co/datasets/mondk/documentation-images | mondk/documentation-images | analytics | sql | computer_vision | Compare multiple sources about computer_vision 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": "mondk/documentation-images", "source_url": "https://huggingface.co/datasets/mondk/documentati... | === SOURCES ===
- mondk/documentation-images (https://huggingface.co/datasets/mondk/documentation-images)
- Official documentation
- Community discussions
=== AGREEMENTS ===
Identify claims supported by multiple independent sources.
=== CONTRADICTIONS ===
Identify conflicting claims and their likely cause (version di... | web-research-coding-5m-1.1.0 | |
ed41be9aca95adde68b0c22c | train | api_developer_experience | mdn | https://developer.mozilla.org/en-US/docs/Web/CSS | CSS | blog | shell | authentication | Perform a deep developer-experience analysis for a shell project involving authentication. | {"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. 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 | |
52f43e3f3418a1d1500bebb8 | train | refactoring_performance | mdn | https://developer.mozilla.org/en-US/docs/Web/Performance | Performance | marketplace | css | mongodb | Refactor a css system related to mongodb. Focus on refactoring performance. | {"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... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Reduce unnecessary computation, allocations, I/O, and network requests.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify d... | web-research-coding-5m-1.1.0 | |
26cfdc8be02e74fc2d895ad8 | train | architecture_analysis | gitlab | https://gitlab.com/hsleisink/cauldron | hsleisink/cauldron | social_app | shell | cloud | Perform a deep multi-layer analysis of cloud 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": "hsleisink/cauldron", "source_url": "https://gitlab.com/hsleisink/cauldron", "source_type": "r... | === 1. PROBLEM ===
Define the exact problem involving cloud. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around cloud. Use 'hsleisink/cauldron' as a source anchor and identify relevant APIs, dependencies, versions, standard... | web-research-coding-5m-1.1.0 | |
1ee0d21dfc902e289584da6f | train | testing_experience | npm | https://www.npmjs.com/package/hono | hono | marketplace | javascript | docker | Perform a deep developer-experience analysis for a javascript project involving docker. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "hono", "source_url": "https://www.npmjs.com/package/hono", "source_type": "package", "topic":... | === 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 | |
6e2de4903a79359a07a29295 | train | maintainability_analysis | stackexchange | https://stackoverflow.com/questions/12827266/get-and-set-in-typescript | get and set in TypeScript | community | java | machine_learning | Perform a deep multi-layer analysis of machine_learning for a community using java. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "get and set in TypeScript", "source_url": "https://stackoverflow.com/questions/12827266/get-a... | === 1. PROBLEM ===
Define the exact problem involving machine_learning. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around machine_learning. Use 'get and set in TypeScript' as a source anchor and identify relevant APIs, dep... | web-research-coding-5m-1.1.0 | |
adb448cd69ccc8a0f6852b0e | train | documentation_lookup | github | https://github.com/apache/superset | apache/superset | analytics | python | 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": "apache/superset", "source_url": "https://github.com/apache/superset", "source_type": "reposit... | === RELEVANT DOCS ===
- apache/superset
https://github.com/apache/superset
- Official project documentation
- API reference
=== KEY SECTIONS ===
- Getting started
- API reference
- Configuration
- Troubleshooting
=== SUMMARY ===
Summarize each section in 1–3 sentences and quote exact signatures where relevant. | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
ec38bbdd2ddf5b3a70aa56e4 | train | design_review | pypi | https://pypi.org/project/typer/ | typer | finance | javascript | open_source | Perform a professional design review of a finance. | {"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": "... | Review hierarchy, consistency, responsiveness, accessibility, interaction design, content clarity, and implementation feasibility. | web-research-coding-5m-1.1.0 | |
2b29317daa07e532199697d0 | train | refactoring_maintainability | gitlab | https://gitlab.com/ai_lab_cs_lm/2024_2025/ai_course_template | ai_lab_cs_lm/2024_2025/ai_course_template | saas | swift | caching | Refactor a swift system related to caching. Focus on refactoring maintainability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "ai_lab_cs_lm/2024_2025/ai_course_template", "source_url": "https://gitlab.com/ai_lab_cs_lm/20... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Improve cohesion, reduce coupling, isolate volatile behavior, and remove duplication.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.... | web-research-coding-5m-1.1.0 | |
866fec3d47c04996d14628ec | train | deep_technical_analysis | web_docs | https://react.dev/ | React Documentation | productivity | javascript | deep_learning | Perform a deep multi-layer analysis of deep_learning for a productivity 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": "React Documentation", "source_url": "https://react.dev/", "source_type": "documentation", "to... | === 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 'React Documentation' as a source anchor and identify relevant APIs, dependencies, v... | web-research-coding-5m-1.1.0 | |
730299f48d72c37a13a81109 | train | accessibility_fix | npm | https://www.npmjs.com/package/svelte | svelte | education | scala | serverless | Create an accessibility remediation plan for a education. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "svelte", "source_url": "https://www.npmjs.com/package/svelte", "source_type": "package", "top... | Check semantic HTML, keyboard navigation, focus management, accessible names, labels, errors, contrast, and screen-reader behavior. | web-research-coding-5m-1.1.0 | |
3bb63efd44ba7f33e198bd3b | train | debugging_experience | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API | Fetch API | saas | typescript | caching | Perform a deep developer-experience analysis for a typescript project involving caching. | {"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 | |
b1d784bc6f05ca2eccbc5ace | train | repository_architecture | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model | DOM | blog | c | typescript | Perform a deep multi-layer analysis of typescript for a blog 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": "DOM", "source_url": "https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model",... | === 1. PROBLEM ===
Define the exact problem involving typescript. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around typescript. Use 'DOM' as a source anchor and identify relevant APIs, dependencies, versions, standards, an... | web-research-coding-5m-1.1.0 | |
565026047fc2740b2b3bd24e | train | design_to_code | stackexchange | https://stackoverflow.com/questions/34930735/pros-cons-of-using-redux-saga-with-es6-generators-vs-redux-thunk-with-es2017-asy | Pros/cons of using redux-saga with ES6 generators vs redux-thunk with ES2017 async/await | education | cpp | database | Translate a education design into maintainable cpp code. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Pros/cons of using redux-saga with ES6 generators vs redux-thunk with ES2017 async/await", "s... | Map design tokens to code, identify reusable components, preserve responsive behavior, implement accessible states, and avoid unnecessary one-off styling. | web-research-coding-5m-1.1.0 | |
7c1325f93059981f6b0beed4 | train | performance_analysis | huggingface | https://huggingface.co/datasets/arolstar52/ocr-synthetic-multilingual-v1-tokenized-zh-hans | arolstar52/ocr-synthetic-multilingual-v1-tokenized-zh-hans | 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": "arolstar52/ocr-synthetic-multilingual-v1-tokenized-zh-hans", "source_url": "https://huggingfa... | === 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 'arolstar52/ocr-synthetic-multilingual-v1-tokenized-zh-hans' as a source anchor and ... | web-research-coding-5m-1.1.0 | |
a5fc66a721c03879d8e94b52 | train | developer_experience | codeberg | https://codeberg.org/LadueCS/2048 | LadueCS/2048 | community | kotlin | frontend | Perform a deep developer-experience analysis for a kotlin project involving frontend. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "LadueCS/2048", "source_url": "https://codeberg.org/LadueCS/2048", "source_type": "repository"... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
69f9e6642b9cf2ec59041715 | train | integration_testing | github | https://github.com/parcel-bundler/parcel | parcel-bundler/parcel | finance | html | html | Design integration tests for a html system involving html. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "parcel-bundler/parcel", "source_url": "https://github.com/parcel-bundler/parcel", "source_typ... | Test real component boundaries, persistence, configuration, external interfaces, errors, cleanup, and realistic workflows. | web-research-coding-5m-1.1.0 | |
8c912dc36e359a92801d511a | train | refactoring_observability | web_docs | https://fastapi.tiangolo.com/ | FastAPI Documentation | analytics | cpp | machine_learning | Refactor a cpp system related to machine_learning. Focus on refactoring observability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "FastAPI Documentation", "source_url": "https://fastapi.tiangolo.com/", "source_type": "docume... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Improve logging, metrics, tracing, diagnostics, and failure visibility.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify d... | web-research-coding-5m-1.1.0 | |
395511dc93ca0bc7bf3079bb | train | system_analysis | web_docs | https://doc.rust-lang.org/ | Rust Documentation | saas | java | fullstack | Perform a deep multi-layer analysis of fullstack for a saas 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": "Rust Documentation", "source_url": "https://doc.rust-lang.org/", "source_type": "documentatio... | === 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 'Rust Documentation' as a source anchor and identify relevant APIs, dependencies, versions, ... | web-research-coding-5m-1.1.0 | |
757cfb32d9b5ab812c9afa09 | train | security_analysis | web_docs | https://www.postgresql.org/docs/ | PostgreSQL Documentation | marketplace | cpp | documentation | Perform a deep multi-layer analysis of documentation for a marketplace 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": "PostgreSQL Documentation", "source_url": "https://www.postgresql.org/docs/", "source_type": "... | === 1. PROBLEM ===
Define the exact problem involving documentation. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around documentation. Use 'PostgreSQL Documentation' as a source anchor and identify relevant APIs, dependenci... | web-research-coding-5m-1.1.0 | |
da86f8cc24c6021e5b86bee6 | train | build_experience | web_docs | https://nodejs.org/docs/latest/api/ | Node.js Documentation | landing_page | html | authentication | Perform a deep developer-experience analysis for a html project involving authentication. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Node.js Documentation", "source_url": "https://nodejs.org/docs/latest/api/", "source_type": "... | === 1. 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 | |
a9ca1cbf8fc83afec6602343 | train | maintainability_analysis | huggingface | https://huggingface.co/datasets/jamesdborin/Nemotron-Competitive-Programming-v1-prompt-only | jamesdborin/Nemotron-Competitive-Programming-v1-prompt-only | portfolio | html | mongodb | Perform a deep multi-layer analysis of mongodb for a portfolio 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": "jamesdborin/Nemotron-Competitive-Programming-v1-prompt-only", "source_url": "https://huggingf... | === 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 'jamesdborin/Nemotron-Competitive-Programming-v1-prompt-only' as a source anchor and identify re... | web-research-coding-5m-1.1.0 | |
10bd62b1523e2e053e669843 | train | refactoring_scalability | gitlab | https://gitlab.com/gitlab-ci-utils/gitlab-semgrep-plus | gitlab-ci-utils/gitlab-semgrep-plus | landing_page | php | html | Refactor a php system related to html. Focus on refactoring scalability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "gitlab-ci-utils/gitlab-semgrep-plus", "source_url": "https://gitlab.com/gitlab-ci-utils/gitla... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Restructure the system to handle increased load without unnecessary complexity.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Id... | web-research-coding-5m-1.1.0 | |
3b0e49ef0309a3ffef17f37a | train | design_tokens | web_docs | https://www.postgresql.org/docs/ | PostgreSQL Documentation | landing_page | javascript | software_architecture | Create design tokens for a landing_page. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "PostgreSQL Documentation", "source_url": "https://www.postgresql.org/docs/", "source_type": "... | Define reusable tokens for typography, spacing, radii, sizing, elevation, interaction states, and responsive behavior. | web-research-coding-5m-1.1.0 | |
8dbf4fbceff68d5e1ca3a915 | train | refactoring_observability | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API | Fetch API | productivity | html | css | Refactor a html system related to css. Focus on refactoring observability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Fetch API", "source_url": "https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API", "sour... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Improve logging, metrics, tracing, diagnostics, and failure visibility.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify d... | web-research-coding-5m-1.1.0 | |
d51146fc86061cfc653f2992 | train | refactoring_observability | npm | https://www.npmjs.com/package/zod | zod | analytics | java | react | Refactor a java system related to react. Focus on refactoring observability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "zod", "source_url": "https://www.npmjs.com/package/zod", "source_type": "package", "topic": "... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Improve logging, metrics, tracing, diagnostics, and failure visibility.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify d... | web-research-coding-5m-1.1.0 | |
c45eb18217dc7ab56e5f70de | train | repository_issue_reasoning | pypi | https://pypi.org/project/pandas/ | pandas | documentation | ruby | typescript | Perform a deep multi-layer analysis of typescript 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": "pandas", "source_url": "https://pypi.org/project/pandas/", "source_type": "package", "topic":... | === 1. PROBLEM ===
Define the exact problem involving typescript. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around typescript. Use 'pandas' as a source anchor and identify relevant APIs, dependencies, versions, standards,... | web-research-coding-5m-1.1.0 | |
8d535ecd26d90d1e5822ea04 | train | local_development_experience | pypi | https://pypi.org/project/pandas/ | pandas | documentation | rust | ci_cd | Perform a deep developer-experience analysis for a rust project involving ci_cd. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "pandas", "source_url": "https://pypi.org/project/pandas/", "source_type": "package", "topic":... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
6e086000263ebc74a4a21ed7 | train | debugging_experience | gitlab | https://gitlab.com/TheOneWithTheBraid/xournalpp_mobile | TheOneWithTheBraid/xournalpp_mobile | marketplace | typescript | deep_learning | Perform a deep developer-experience analysis for a typescript project involving deep_learning. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "TheOneWithTheBraid/xournalpp_mobile", "source_url": "https://gitlab.com/TheOneWithTheBraid/xo... | === 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 | |
10c34a6a40d9c2a145587402 | train | refactoring_api | pypi | https://pypi.org/project/httpx/ | httpx | finance | dart | user_experience | Refactor a dart system related to user_experience. Focus on refactoring api. | {"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": "... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Improve API contracts, validation, error semantics, compatibility, and versioning.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4.... | web-research-coding-5m-1.1.0 | |
46f8b47cd964bf8001038623 | train | code_explanation | github | https://github.com/puppeteer/puppeteer | puppeteer/puppeteer | finance | go | deep_learning | Explain a go implementation related to deep_learning. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "puppeteer/puppeteer", "source_url": "https://github.com/puppeteer/puppeteer", "source_type": ... | Explain inputs, outputs, control flow, algorithms, complexity, edge cases, errors, and maintainability. | web-research-coding-5m-1.1.0 | |
85428d2a8d32a906e2758c9f | train | dependency_management_experience | codeberg | https://codeberg.org/Roboe/advent-of-code | Roboe/advent-of-code | landing_page | kotlin | observability | Perform a deep developer-experience analysis for a kotlin project involving observability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Roboe/advent-of-code", "source_url": "https://codeberg.org/Roboe/advent-of-code", "source_typ... | === 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 | |
39607b5d42f2c9464e391513 | train | design_to_code | pypi | https://pypi.org/project/scikit-learn/ | scikit-learn | documentation | kotlin | serverless | Translate a documentation design into maintainable kotlin code. | {"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... | Map design tokens to code, identify reusable components, preserve responsive behavior, implement accessible states, and avoid unnecessary one-off styling. | web-research-coding-5m-1.1.0 | |
a8087a1c1118e14fba329846 | train | technical_research | codeberg | https://codeberg.org/nopeppermint/_cargo-index | nopeppermint/_cargo-index | landing_page | python | testing | Perform a technical research task about testing, focused on implementation details. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "nopeppermint/_cargo-index", "source_url": "https://codeberg.org/nopeppermint/_cargo-index", "... | === SCOPE ===
Technical behavior of testing.
=== QUESTIONS ===
- What are the inputs, outputs, and invariants?
- What are the performance characteristics?
- What are the security implications?
- What are the compatibility constraints?
=== EVIDENCE ===
- nopeppermint/_cargo-index (https://codeberg.org/nopeppermint/_ca... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
117723a884fbb7e3558ebd35 | train | tradeoff_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/Accessibility | Accessibility | community | ruby | docker | Perform a deep multi-layer analysis of docker for a community 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": "Accessibility", "source_url": "https://developer.mozilla.org/en-US/docs/Web/Accessibility", "... | === 1. PROBLEM ===
Define the exact problem involving docker. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around docker. Use 'Accessibility' as a source anchor and identify relevant APIs, dependencies, versions, standards, ... | web-research-coding-5m-1.1.0 | |
971d5943ddd7ad0ff466be81 | train | search_query_rewrite | huggingface | https://huggingface.co/datasets/gangiswag/javascript_ablation | gangiswag/javascript_ablation | blog | javascript | testing | Rewrite and improve a vague search query about testing into a precise, high-signal query. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "gangiswag/javascript_ablation", "source_url": "https://huggingface.co/datasets/gangiswag/java... | === ORIGINAL (VAGUE) ===
how to do testing
=== REWRITTEN QUERIES ===
1. testing official documentation guide
2. testing production best practices 2025
3. testing common pitfalls and solutions
4. testing architecture patterns with examples
=== RATIONALE ===
Add intent (learn / implement / debug), specificity (version,... | web-research-coding-5m-1.1.0 | |
21d533154f07483672c5a879 | train | repository_comparison | huggingface | https://huggingface.co/datasets/bezzam/documentation-images | bezzam/documentation-images | search_interface | python | docker | Perform a deep multi-layer analysis of docker for a search_interface 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": "bezzam/documentation-images", "source_url": "https://huggingface.co/datasets/bezzam/documenta... | === 1. PROBLEM ===
Define the exact problem involving docker. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around docker. Use 'bezzam/documentation-images' as a source anchor and identify relevant APIs, dependencies, version... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
ef4fc4ef84ed61b83144b91d | train | refactoring_testability | gitlab | https://gitlab.com/mailman/postorius | mailman/postorius | community | css | debugging | Refactor a css system related to debugging. Focus on refactoring testability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "mailman/postorius", "source_url": "https://gitlab.com/mailman/postorius", "source_type": "rep... | === 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 | |
f7a445f1f132b77c056529be | train | evidence_chain_analysis | huggingface | https://huggingface.co/datasets/Lots-of-LoRAs/task718_mmmlu_answer_generation_machine_learning | Lots-of-LoRAs/task718_mmmlu_answer_generation_machine_learning | community | python | software_architecture | Perform a deep multi-layer analysis of software_architecture for a community 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": "Lots-of-LoRAs/task718_mmmlu_answer_generation_machine_learning", "source_url": "https://huggi... | === 1. PROBLEM ===
Define the exact problem involving software_architecture. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around software_architecture. Use 'Lots-of-LoRAs/task718_mmmlu_answer_generation_machine_learning' as ... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
9e5f742278817d512fb6f65c | train | api_developer_experience | huggingface | https://huggingface.co/datasets/prhbrt/machine_learning_courses | prhbrt/machine_learning_courses | admin_panel | 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": "prhbrt/machine_learning_courses", "source_url": "https://huggingface.co/datasets/prhbrt/machi... | === 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 | |
d01c3d92477becadec4f446d | train | landing_page | pypi | https://pypi.org/project/httpx/ | httpx | documentation | scala | software_architecture | Design a landing page for a software_architecture product. | {"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": "... | Include hero, value proposition, features, CTA, FAQ, responsive behavior, SEO, accessibility, and analytics. | web-research-coding-5m-1.1.0 | |
e8cc99ab273c2ec4a8a7ef9c | train | ui_design | huggingface | https://huggingface.co/datasets/HighFive-OPJ/Implementation_1-Machine_learning | HighFive-OPJ/Implementation_1-Machine_learning | search_interface | scala | data_engineering | Design a production-quality UI for a search_interface focused on data_engineering. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "HighFive-OPJ/Implementation_1-Machine_learning", "source_url": "https://huggingface.co/datase... | Define layout, typography, spacing, hierarchy, components, states, responsive behavior, and accessibility. | web-research-coding-5m-1.1.0 | |
8f90638c114be6d263583d7d | train | build_experience | pypi | https://pypi.org/project/rich/ | rich | landing_page | java | computer_vision | Perform a deep developer-experience analysis for a java project involving computer_vision. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "rich", "source_url": "https://pypi.org/project/rich/", "source_type": "package", "topic": "co... | === 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 | |
e33781fc3e207e4ef74fcec3 | train | architecture_analysis | codeberg | TheAnimateurY/.svg | social_app | ruby | mongodb | Perform a deep multi-layer analysis of mongodb for a social_app 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": "TheAnimateurY/.svg", "source_url": "https://codeberg.org/TheAnimateurY/.svg", "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 'TheAnimateurY/.svg' as a source anchor and identify relevant APIs, dependencies, versions, stan... | web-research-coding-5m-1.1.0 | ||
2ccdfb7771201e61b2bba0a9 | train | refactoring_scalability | mdn | https://developer.mozilla.org/en-US/docs/Web/Performance | Performance | social_app | kotlin | ci_cd | Refactor a kotlin system related to ci_cd. Focus on refactoring scalability. | {"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... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Restructure the system to handle increased load without unnecessary complexity.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Id... | web-research-coding-5m-1.1.0 | |
909cd511a36a58cbee5e44b1 | train | maintainability_analysis | stackexchange | https://stackoverflow.com/questions/47012169/a-component-is-changing-an-uncontrolled-input-of-type-text-to-be-controlled-erro | A component is changing an uncontrolled input of type text to be controlled error in ReactJS | saas | scala | testing | Perform a deep multi-layer analysis of testing for a saas 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": "A component is changing an uncontrolled input of type text to be controlled error in ReactJS"... | === 1. PROBLEM ===
Define the exact problem involving testing. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around testing. Use 'A component is changing an uncontrolled input of type text to be controlled error in ReactJS' a... | web-research-coding-5m-1.1.0 | |
9681463e53dcb141a0f91712 | train | code_explanation | huggingface | https://huggingface.co/datasets/codeparrot/github-code-clean | codeparrot/github-code-clean | community | css | data_engineering | Explain a css implementation related to data_engineering. | {"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... | Explain inputs, outputs, control flow, algorithms, complexity, edge cases, errors, and maintainability. | web-research-coding-5m-1.1.0 | |
800993fa2da7abe065009cb3 | train | security_review | mdn | https://developer.mozilla.org/en-US/docs/Web/Performance | Performance | marketplace | css | postgresql | Perform a security review of a marketplace application. | {"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... | Review authentication, authorization, input validation, XSS, CSRF, injection risks, secrets, dependencies, security headers, and logging. | web-research-coding-5m-1.1.0 | |
4f20ef68d9bb1a42802ba385 | train | system_analysis | stackexchange | https://stackoverflow.com/questions/100003/what-are-metaclasses-in-python | What are metaclasses in Python? | admin_panel | shell | caching | Perform a deep multi-layer analysis of caching for a admin_panel 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": "What are metaclasses in Python?", "source_url": "https://stackoverflow.com/questions/100003/w... | === 1. PROBLEM ===
Define the exact problem involving caching. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around caching. Use 'What are metaclasses in Python?' as a source anchor and identify relevant APIs, dependencies, v... | web-research-coding-5m-1.1.0 | |
e01fd37f35e65144e8068e85 | train | search_intent_classification | pypi | https://pypi.org/project/sqlalchemy/ | sqlalchemy | documentation | php | security | Classify the search intent for a query about security. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "sqlalchemy", "source_url": "https://pypi.org/project/sqlalchemy/", "source_type": "package", ... | === POSSIBLE INTENTS ===
- informational (learn a concept)
- navigational (find a specific site/tool)
- transactional (install / download / run)
- troubleshooting (fix an error)
- comparative (choose between options)
=== EXAMPLE QUERY ===
"security vs alternatives"
=== CLASSIFICATION ===
Comparative / informational.
... | web-research-coding-5m-1.1.0 | |
1d6b246f0bc39af55f23d5d4 | train | architecture_analysis | stackexchange | https://stackoverflow.com/questions/986006/how-do-i-pass-a-variable-by-reference | How do I pass a variable by reference? | education | javascript | web_accessibility | Perform a deep multi-layer analysis of web_accessibility for a education using javascript. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How do I pass a variable by reference?", "source_url": "https://stackoverflow.com/questions/9... | === 1. PROBLEM ===
Define the exact problem involving web_accessibility. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around web_accessibility. Use 'How do I pass a variable by reference?' as a source anchor and identify rel... | web-research-coding-5m-1.1.0 | |
25a57b1758e8253cc7571a11 | train | react_generation | huggingface | https://huggingface.co/datasets/bezzam/documentation-images | bezzam/documentation-images | analytics | php | developer_experience | Design React components for a analytics. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "bezzam/documentation-images", "source_url": "https://huggingface.co/datasets/bezzam/documenta... | Separate reusable components, state, data fetching, loading/error states, accessibility, and testing. | export function Card({ title, children }) {
return (
<article className="card">
<h2>{title}</h2>
<div>{children}</div>
</article>
);
} | web-research-coding-5m-1.1.0 |
52b85cf51ee007c0b422a81c | train | developer_onboarding | npm | https://www.npmjs.com/package/prettier | prettier | social_app | sql | database | Perform a deep developer-experience analysis for a sql project involving database. | {"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. 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 | |
69985d8ba4e8f73caeb0804f | train | api_developer_experience | web_docs | https://www.typescriptlang.org/docs/ | TypeScript Documentation | documentation | go | observability | Perform a deep developer-experience analysis for a go project involving observability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "TypeScript Documentation", "source_url": "https://www.typescriptlang.org/docs/", "source_type... | === 1. 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 | |
852f9021b06a5d26dfcae05d | train | repository_comparison | mdn | https://developer.mozilla.org/en-US/docs/Web/Accessibility | Accessibility | blog | ruby | graphql | Perform a deep multi-layer analysis of graphql for a blog 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": "Accessibility", "source_url": "https://developer.mozilla.org/en-US/docs/Web/Accessibility", "... | === 1. PROBLEM ===
Define the exact problem involving graphql. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around graphql. Use 'Accessibility' as a source anchor and identify relevant APIs, dependencies, versions, standards... | web-research-coding-5m-1.1.0 | |
b4d81e74341dbaa6f2209e8d | train | refactoring_api | huggingface | https://huggingface.co/datasets/puttatidam/software-documentation-zsm-bitextmining | puttatidam/software-documentation-zsm-bitextmining | developer_tool | dart | fullstack | Refactor a dart system related to fullstack. Focus on refactoring api. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "puttatidam/software-documentation-zsm-bitextmining", "source_url": "https://huggingface.co/da... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Improve API contracts, validation, error semantics, compatibility, and versioning.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4.... | web-research-coding-5m-1.1.0 | |
83c8ae33012ca0597ca178f9 | train | refactoring_scalability | mdn | https://developer.mozilla.org/en-US/docs/Web/HTTP | HTTP | admin_panel | swift | software_architecture | Refactor a swift system related to software_architecture. Focus on refactoring scalability. | {"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... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Restructure the system to handle increased load without unnecessary complexity.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Id... | web-research-coding-5m-1.1.0 | |
7b63a9bee8a250a585c8a424 | train | design_accessibility | huggingface | https://huggingface.co/datasets/SivilTaram/starcoder2-documentation | SivilTaram/starcoder2-documentation | developer_tool | go | nlp | Audit accessibility for a developer_tool. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "SivilTaram/starcoder2-documentation", "source_url": "https://huggingface.co/datasets/SivilTar... | Check semantic structure, keyboard navigation, focus visibility, accessible names, labels, errors, contrast, and screen-reader behavior. | web-research-coding-5m-1.1.0 | |
4b7466853142b319d61bb0bc | train | documentation_experience | pypi | https://pypi.org/project/transformers/ | transformers | social_app | sql | javascript | Perform a deep developer-experience analysis for a sql project involving javascript. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "transformers", "source_url": "https://pypi.org/project/transformers/", "source_type": "packag... | === 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 | |
2343a6a74d4bc7d870838963 | train | design_to_code | npm | https://www.npmjs.com/package/typescript | typescript | blog | kotlin | caching | Translate a blog design into maintainable kotlin code. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "typescript", "source_url": "https://www.npmjs.com/package/typescript", "source_type": "packag... | Map design tokens to code, identify reusable components, preserve responsive behavior, implement accessible states, and avoid unnecessary one-off styling. | web-research-coding-5m-1.1.0 | |
32e8b9893a63d9a98d249893 | train | information_architecture | stackexchange | https://stackoverflow.com/questions/396145/how-can-i-vertically-center-a-div-element-for-all-browsers-using-css | How can I vertically center a div element for all browsers using CSS? | saas | kotlin | caching | Design the information architecture for caching. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How can I vertically center a div element for all browsers using CSS?", "source_url": "https:... | Organize content into logical categories, navigation levels, search, filtering, and discoverable paths. | web-research-coding-5m-1.1.0 | |
6a8d1efe355f52d8a8b4a8a9 | train | refactoring_dependency | web_docs | https://git-scm.com/doc | Git Documentation | documentation | scala | typescript | Refactor a scala system related to typescript. Focus on refactoring dependency. | {"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", ... | === 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 | |
4886a2f1220392401c4b1bad | train | refactoring_maintainability | pypi | https://pypi.org/project/httpx/ | httpx | community | html | mongodb | Refactor a html system related to mongodb. Focus on refactoring maintainability. | {"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": "... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Improve cohesion, reduce coupling, isolate volatile behavior, and remove duplication.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.... | web-research-coding-5m-1.1.0 | |
ddb885f708c150edabee4e65 | train | error_message_design | pypi | https://pypi.org/project/scrapy/ | scrapy | ecommerce | cpp | serverless | Perform a deep developer-experience analysis for a cpp project involving serverless. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "scrapy", "source_url": "https://pypi.org/project/scrapy/", "source_type": "package", "topic":... | === 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 | |
4dc6f2275413176d1357f114 | train | ux_analysis | stackexchange | https://stackoverflow.com/questions/12952729/how-to-understand-locality-sensitive-hashing | How to understand Locality Sensitive Hashing? | finance | swift | debugging | Perform a deep multi-layer analysis of debugging for a finance using swift. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How to understand Locality Sensitive Hashing?", "source_url": "https://stackoverflow.com/ques... | === 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 'How to understand Locality Sensitive Hashing?' as a source anchor and identify relevant API... | 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.