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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
b9688e749d940c7717fd2066 | train | api_design | npm | https://www.npmjs.com/package/jest | jest | community | rust | data_engineering | Design a production API for a data_engineering application. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "jest", "source_url": "https://www.npmjs.com/package/jest", "source_type": "package", "topic":... | Specify resources, endpoints, schemas, validation, authentication, authorization, errors, pagination, versioning, idempotency, and tests. | web-research-coding-5m-1.1.0 | |
692bab396b28c88bf11f1ef3 | train | error_message_design | codeberg | https://codeberg.org/paultustain/100DaysofCodePython | paultustain/100DaysofCodePython | blog | 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": "paultustain/100DaysofCodePython", "source_url": "https://codeberg.org/paultustain/100DaysofCo... | === 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 | |
176585f7bb2771c6f5177a63 | train | repository_dependency_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/CSS | CSS | social_app | swift | mongodb | Perform a deep multi-layer analysis of mongodb for a social_app using swift. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "CSS", "source_url": "https://developer.mozilla.org/en-US/docs/Web/CSS", "source_type": "docum... | === 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 'CSS' as a source anchor and identify relevant APIs, dependencies, versions, standards, and tech... | web-research-coding-5m-1.1.0 | |
b256616aaa525adb1154afaf | train | deployment_experience | github | https://github.com/harvard-edge/cs249r_book | harvard-edge/cs249r_book | blog | swift | open_source | Perform a deep developer-experience analysis for a swift project involving open_source. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "harvard-edge/cs249r_book", "source_url": "https://github.com/harvard-edge/cs249r_book", "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 | |
6e23dc3d7ef0e3f52807987e | train | upgrade_experience | github | https://github.com/Ebazhanov/linkedin-skill-assessments-quizzes | Ebazhanov/linkedin-skill-assessments-quizzes | admin_panel | c | security | Perform a deep developer-experience analysis for a c project involving security. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Ebazhanov/linkedin-skill-assessments-quizzes", "source_url": "https://github.com/Ebazhanov/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 | |
c66f6d1e14dc2e40e0997c01 | train | code_review | pypi | https://pypi.org/project/scrapy/ | scrapy | social_app | shell | react | Perform a production code review of shell code related to react. | {"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":... | Review correctness, security, performance, readability, architecture, testing, maintainability, and error handling. | web-research-coding-5m-1.1.0 | |
93450d876655ba3f62cff115 | train | information_architecture | pypi | https://pypi.org/project/fastapi/ | fastapi | dashboard | go | react | Design the information architecture for react. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "fastapi", "source_url": "https://pypi.org/project/fastapi/", "source_type": "package", "topic... | Organize content into logical categories, navigation levels, search, filtering, and discoverable paths. | web-research-coding-5m-1.1.0 | |
14c40ed2f9f0c577844fce3f | train | product_analysis | gitlab | https://gitlab.com/gitlab-ci-utils/gitlab-semgrep-plus | gitlab-ci-utils/gitlab-semgrep-plus | analytics | cpp | nlp | Perform a deep multi-layer analysis of nlp for a analytics 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": "gitlab-ci-utils/gitlab-semgrep-plus", "source_url": "https://gitlab.com/gitlab-ci-utils/gitla... | === 1. PROBLEM ===
Define the exact problem involving nlp. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around nlp. Use 'gitlab-ci-utils/gitlab-semgrep-plus' as a source anchor and identify relevant APIs, dependencies, versi... | web-research-coding-5m-1.1.0 | |
e6f702b5892809e69d780d16 | train | design_system | stackexchange | https://stackoverflow.com/questions/14727044/what-is-the-difference-between-types-string-and-string | What is the difference between types String and string? | admin_panel | javascript | nextjs | Create a scalable design system for a admin_panel. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "What is the difference between types String and string?", "source_url": "https://stackoverflo... | Define tokens, typography, spacing, components, variants, states, responsive rules, accessibility, and documentation. | web-research-coding-5m-1.1.0 | |
fefd092716e5172c814905cc | train | accessibility_analysis | stackexchange | https://stackoverflow.com/questions/37937984/git-refusing-to-merge-unrelated-histories-on-rebase | Git refusing to merge unrelated histories on rebase | education | python | authorization | Perform a deep multi-layer analysis of authorization for a education using python. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Git refusing to merge unrelated histories on rebase", "source_url": "https://stackoverflow.co... | === 1. PROBLEM ===
Define the exact problem involving authorization. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around authorization. Use 'Git refusing to merge unrelated histories on rebase' as a source anchor and identif... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
7bac572416b801a349717492 | train | architecture_analysis | codeberg | https://codeberg.org/UI-Programming-23-24/01-web-basics-and-git-Danny-Delaney | UI-Programming-23-24/01-web-basics-and-git-Danny-Delaney | portfolio | rust | ci_cd | Perform a deep multi-layer analysis of ci_cd for a portfolio using rust. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "UI-Programming-23-24/01-web-basics-and-git-Danny-Delaney", "source_url": "https://codeberg.or... | === 1. PROBLEM ===
Define the exact problem involving ci_cd. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around ci_cd. Use 'UI-Programming-23-24/01-web-basics-and-git-Danny-Delaney' as a source anchor and identify relevant ... | web-research-coding-5m-1.1.0 | |
35d0d460a7395bfac3909ccc | train | testing_experience | huggingface | https://huggingface.co/datasets/BigScienceBiasEval/crows_pairs_multilingual | BigScienceBiasEval/crows_pairs_multilingual | saas | python | authorization | Perform a deep developer-experience analysis for a python project involving authorization. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "BigScienceBiasEval/crows_pairs_multilingual", "source_url": "https://huggingface.co/datasets/... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
1a75c63ce2c484d790d5c3f8 | train | refactoring_observability | pypi | https://pypi.org/project/requests/ | requests | community | javascript | design_system | Refactor a javascript system related to design_system. Focus on refactoring observability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "requests", "source_url": "https://pypi.org/project/requests/", "source_type": "package", "top... | === 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 | |
f0c34e00bf8ec46d346c8750 | train | dependency_impact_analysis | huggingface | https://huggingface.co/datasets/theblackcat102/multiround-programming-convo | theblackcat102/multiround-programming-convo | finance | kotlin | web_performance | Perform a deep multi-layer analysis of web_performance for a finance using kotlin. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "theblackcat102/multiround-programming-convo", "source_url": "https://huggingface.co/datasets/... | === 1. PROBLEM ===
Define the exact problem involving web_performance. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around web_performance. Use 'theblackcat102/multiround-programming-convo' as a source anchor and identify re... | web-research-coding-5m-1.1.0 | |
82c059e665023acf2fd2b4c7 | train | refactoring | stackexchange | https://stackoverflow.com/questions/176918/how-can-i-find-the-index-for-a-given-item-in-a-list | How can I find the index for a given item in a list? | community | java | linux | Create a production coding task in java for linux. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How can I find the index for a given item in a list?", "source_url": "https://stackoverflow.c... | Provide implementation requirements, edge cases, testing requirements, security considerations, performance constraints, and documentation requirements. | web-research-coding-5m-1.1.0 | |
9ec15397d8d006f2298b4326 | train | evidence_extraction | github | https://github.com/f/prompts.chat | f/prompts.chat | productivity | kotlin | security | Extract verifiable evidence about security from the given source. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "f/prompts.chat", "source_url": "https://github.com/f/prompts.chat", "source_type": "repositor... | === SOURCE ===
f/prompts.chat
https://github.com/f/prompts.chat
=== EVIDENCE ITEMS ===
1. Explicit claims made by the source
2. Code examples or API signatures
3. Version / compatibility statements
4. Performance or security notes
=== QUALITY CHECK ===
- Is the claim specific and testable?
- Is the version and enviro... | web-research-coding-5m-1.1.0 | |
0d5d30ec67624232504ffe4a | train | refactoring_modularization | pypi | https://pypi.org/project/gradio/ | gradio | productivity | scala | serverless | Refactor a scala system related to serverless. Focus on refactoring modularization. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "gradio", "source_url": "https://pypi.org/project/gradio/", "source_type": "package", "topic":... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Split large modules into cohesive units with explicit responsibilities.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify d... | web-research-coding-5m-1.1.0 | |
b8f326643ac96d2c6b39bcf3 | train | deployment_experience | stackexchange | https://stackoverflow.com/questions/1789945/how-to-check-whether-a-string-contains-a-substring-in-javascript | How to check whether a string contains a substring in JavaScript? | community | css | css | Perform a deep developer-experience analysis for a css project involving css. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How to check whether a string contains a substring in JavaScript?", "source_url": "https://st... | === 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 | |
33a26bc8ffc6df7251367bb4 | train | performance_fix | gitlab | https://gitlab.com/surfraw/Surfraw | surfraw/Surfraw | dashboard | php | linux | Create a web-performance optimization plan for a dashboard. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "surfraw/Surfraw", "source_url": "https://gitlab.com/surfraw/Surfraw", "source_type": "reposit... | Measure first, then optimize bundle size, images, network requests, rendering, caching, and critical resources. | web-research-coding-5m-1.1.0 | |
1a9a17eab705a32fa9f9f660 | train | maintainability_analysis | gitlab | https://gitlab.com/c-smile/quickjspp | c-smile/quickjspp | education | scala | distributed_systems | Perform a deep multi-layer analysis of distributed_systems for a education 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": "c-smile/quickjspp", "source_url": "https://gitlab.com/c-smile/quickjspp", "source_type": "rep... | === 1. PROBLEM ===
Define the exact problem involving distributed_systems. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around distributed_systems. Use 'c-smile/quickjspp' as a source anchor and identify relevant APIs, depen... | web-research-coding-5m-1.1.0 | |
afb7a92689bdf1e39cfb140a | train | local_development_experience | web_docs | https://fastapi.tiangolo.com/ | FastAPI Documentation | education | java | redis | Perform a deep developer-experience analysis for a java project involving redis. | {"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... | === 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 | |
7abf8f25630419d9c5882ee9 | train | dependency_impact_analysis | npm | https://www.npmjs.com/package/three | three | portfolio | scala | rest_api | Perform a deep multi-layer analysis of rest_api 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": "three", "source_url": "https://www.npmjs.com/package/three", "source_type": "package", "topic... | === 1. PROBLEM ===
Define the exact problem involving rest_api. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around rest_api. Use 'three' as a source anchor and identify relevant APIs, dependencies, versions, standards, and ... | web-research-coding-5m-1.1.0 | |
403d7ba91369d5ea05fc760f | train | performance_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/CSS | CSS | saas | ruby | javascript | Perform a deep multi-layer analysis of javascript for a saas using ruby. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "CSS", "source_url": "https://developer.mozilla.org/en-US/docs/Web/CSS", "source_type": "docum... | === 1. PROBLEM ===
Define the exact problem involving javascript. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around javascript. Use 'CSS' as a source anchor and identify relevant APIs, dependencies, versions, standards, an... | web-research-coding-5m-1.1.0 | |
e87ce64d1ea0f9d38d4fbbc0 | train | web_search_query | stackexchange | https://stackoverflow.com/questions/1026069/how-do-i-make-the-first-letter-of-a-string-uppercase-in-javascript | How do I make the first letter of a string uppercase in JavaScript? | marketplace | swift | design_system | Write an effective web search query to research the topic: design_system. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How do I make the first letter of a string uppercase in JavaScript?", "source_url": "https://... | === QUERY ===
design_system best practices documentation tutorial
=== INTENT ===
Find authoritative documentation, tutorials, and real-world examples related to the topic.
=== KEYWORDS ===
- design_system
- documentation
- best practices
- examples
- reference
=== SOURCE PREFERENCE ===
Prefer official documentation,... | web-research-coding-5m-1.1.0 | |
625c4613f1f9fc92a1fa0085 | train | dx_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/Performance | Performance | documentation | go | database | Perform a deep developer-experience analysis for a go project involving database. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Performance", "source_url": "https://developer.mozilla.org/en-US/docs/Web/Performance", "sour... | === 1. 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 | |
bafdea4d006a2767b87cf767 | train | dx_analysis | codeberg | https://codeberg.org/nilikk/-webshop.com | nilikk/-webshop.com | developer_tool | java | authorization | Perform a deep developer-experience analysis for a java project involving authorization. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "nilikk/-webshop.com", "source_url": "https://codeberg.org/nilikk/-webshop.com", "source_type"... | === 1. 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 | |
3a86ac9ef8d93b7251eb0c12 | train | scalability_analysis | gitlab | https://gitlab.com/gitlab-com/books-clubs/bookclub-hands-on-machine-learning | gitlab-com/books-clubs/bookclub-hands-on-machine-learning | developer_tool | c | cloud | Perform a deep multi-layer analysis of cloud for a developer_tool 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": "gitlab-com/books-clubs/bookclub-hands-on-machine-learning", "source_url": "https://gitlab.com... | === 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 'gitlab-com/books-clubs/bookclub-hands-on-machine-learning' as a source anchor and identify relevant... | web-research-coding-5m-1.1.0 | |
8bce883cf8897743ccb01eb9 | train | research_summary | codeberg | https://codeberg.org/rutgerclaes/2024-advent-of-code-rs | rutgerclaes/2024-advent-of-code-rs | analytics | rust | ci_cd | Summarize the current state of knowledge about ci_cd. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "rutgerclaes/2024-advent-of-code-rs", "source_url": "https://codeberg.org/rutgerclaes/2024-adv... | === OVERVIEW ===
ci_cd in one paragraph.
=== KEY CONCEPTS ===
- Core definitions
- Main use cases
- Common patterns
=== CURRENT BEST PRACTICES ===
- Recommended approaches
- Known anti-patterns
=== OPEN QUESTIONS ===
- Areas with active development
- Known limitations
=== PRIMARY SOURCE ===
rutgerclaes/2024-advent-... | web-research-coding-5m-1.1.0 | |
efbf998f9a6e096f0bc337ae | train | dependency_management_experience | huggingface | https://huggingface.co/datasets/hchautran/javascript | hchautran/javascript | ecommerce | kotlin | fullstack | Perform a deep developer-experience analysis for a kotlin project involving fullstack. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "hchautran/javascript", "source_url": "https://huggingface.co/datasets/hchautran/javascript", ... | === 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 | |
86f70ecbc3078f616826c121 | train | tradeoff_analysis | gitlab | https://gitlab.com/nitk-nest/nest | nitk-nest/nest | developer_tool | dart | computer_vision | Perform a deep multi-layer analysis of computer_vision for a developer_tool using dart. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "nitk-nest/nest", "source_url": "https://gitlab.com/nitk-nest/nest", "source_type": "repositor... | === 1. PROBLEM ===
Define the exact problem involving computer_vision. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around computer_vision. Use 'nitk-nest/nest' as a source anchor and identify relevant APIs, dependencies, ve... | web-research-coding-5m-1.1.0 | |
1f9a39a361c2fbf2801dd913 | train | refactoring_architecture | gitlab | https://gitlab.com/scripta/escriptorium | scripta/escriptorium | social_app | java | nextjs | Refactor a java system related to nextjs. Focus on refactoring architecture. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "scripta/escriptorium", "source_url": "https://gitlab.com/scripta/escriptorium", "source_type"... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Redesign module boundaries and reduce architectural coupling.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify developer-e... | web-research-coding-5m-1.1.0 | |
4b056e2d6f33867595def950 | train | evidence_extraction | web_docs | https://www.postgresql.org/docs/ | PostgreSQL Documentation | admin_panel | kotlin | mongodb | Extract verifiable evidence about mongodb from the given source. | {"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": "... | === SOURCE ===
PostgreSQL Documentation
https://www.postgresql.org/docs/
=== EVIDENCE ITEMS ===
1. Explicit claims made by the source
2. Code examples or API signatures
3. Version / compatibility statements
4. Performance or security notes
=== QUALITY CHECK ===
- Is the claim specific and testable?
- Is the version a... | web-research-coding-5m-1.1.0 | |
e00fc7be9a2665b4251e8eed | train | ui_design | gitlab | https://gitlab.com/scripta/escriptorium | scripta/escriptorium | admin_panel | go | documentation | Design a production-quality UI for a admin_panel focused on documentation. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "scripta/escriptorium", "source_url": "https://gitlab.com/scripta/escriptorium", "source_type"... | Define layout, typography, spacing, hierarchy, components, states, responsive behavior, and accessibility. | web-research-coding-5m-1.1.0 | |
c6218251915d936d31b246c7 | train | multi_hop_research | pypi | https://pypi.org/project/typer/ | typer | analytics | shell | devops | Perform multi-hop research about devops: start from a source, follow references, and combine findings. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "typer", "source_url": "https://pypi.org/project/typer/", "source_type": "package", "topic": "... | === HOP 1 ===
Start at: typer
https://pypi.org/project/typer/
Extract core claims and references.
=== HOP 2 ===
Follow references to official docs, RFCs, or specs.
Extract primary-source evidence.
=== HOP 3 ===
Check community discussions for real-world issues.
Extract failure modes and workarounds.
=== SYNTHESIS ==... | web-research-coding-5m-1.1.0 | |
0485dd62df81c4fe676d0edc | train | fact_verification | pypi | https://pypi.org/project/httpx/ | httpx | portfolio | kotlin | documentation | Verify a technical claim about documentation. | {"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": "... | === CLAIM ===
A common claim about documentation.
=== VERIFICATION STEPS ===
1. Locate the primary source (docs, spec, RFC).
2. Reproduce the claim in a minimal environment.
3. Check version-specific behavior.
4. Identify edge cases and exceptions.
=== RESULT ===
Classify: confirmed / partially true / false / context... | web-research-coding-5m-1.1.0 | |
54120e53adb58d7ed5e14fb2 | train | testing_experience | gitlab | https://gitlab.com/hsleisink/cauldron | hsleisink/cauldron | dashboard | javascript | devops | Perform a deep developer-experience analysis for a javascript project involving devops. | {"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. 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 | |
2c8dbd53a3404d6ad3512f0c | train | documentation_page | web_docs | https://www.postgresql.org/docs/ | PostgreSQL Documentation | finance | dart | backend | Design a developer documentation page for backend. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "PostgreSQL Documentation", "source_url": "https://www.postgresql.org/docs/", "source_type": "... | Include navigation, overview, prerequisites, installation, examples, API reference, troubleshooting, and search. | web-research-coding-5m-1.1.0 | |
5f8270a991bec08ab959f583 | train | maintainability_analysis | huggingface | https://huggingface.co/datasets/analytics-agents-uncertainty/da-code-evaluation-results | analytics-agents-uncertainty/da-code-evaluation-results | finance | shell | ci_cd | Perform a deep multi-layer analysis of ci_cd for a finance using shell. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "analytics-agents-uncertainty/da-code-evaluation-results", "source_url": "https://huggingface.... | === 1. PROBLEM ===
Define the exact problem involving ci_cd. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around ci_cd. Use 'analytics-agents-uncertainty/da-code-evaluation-results' as a source anchor and identify relevant A... | web-research-coding-5m-1.1.0 | |
d07b8dd089cc059d51fdf50e | train | dependency_impact_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/CSS | CSS | ecommerce | dart | fullstack | Perform a deep multi-layer analysis of fullstack for a ecommerce using dart. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "CSS", "source_url": "https://developer.mozilla.org/en-US/docs/Web/CSS", "source_type": "docum... | === 1. PROBLEM ===
Define the exact problem involving fullstack. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around fullstack. Use 'CSS' as a source anchor and identify relevant APIs, dependencies, versions, standards, and ... | web-research-coding-5m-1.1.0 | |
9024ca68204009b164270d43 | train | error_message_design | huggingface | https://huggingface.co/datasets/ShawRickZia/machine-learning-forecasting-data | ShawRickZia/machine-learning-forecasting-data | finance | javascript | fullstack | Perform a deep developer-experience analysis for a javascript project involving fullstack. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "ShawRickZia/machine-learning-forecasting-data", "source_url": "https://huggingface.co/dataset... | === 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 | |
a08520ec13c18c1afd4348be | train | build_experience | huggingface | https://huggingface.co/datasets/Chunte/documentation-images | Chunte/documentation-images | portfolio | python | postgresql | Perform a deep developer-experience analysis for a python project involving postgresql. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Chunte/documentation-images", "source_url": "https://huggingface.co/datasets/Chunte/documenta... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
969c481c498896e409a32821 | train | refactoring_testability | npm | https://www.npmjs.com/package/webpack | webpack | portfolio | scala | frontend | Refactor a scala system related to frontend. Focus on refactoring testability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "webpack", "source_url": "https://www.npmjs.com/package/webpack", "source_type": "package", "t... | === 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 | |
9eaa2c5b39574b87a449ac29 | train | source_comparison | npm | https://www.npmjs.com/package/three | three | documentation | typescript | security | Compare multiple sources about security 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": "three", "source_url": "https://www.npmjs.com/package/three", "source_type": "package", "topic... | === SOURCES ===
- three (https://www.npmjs.com/package/three)
- Official documentation
- Community discussions
=== AGREEMENTS ===
Identify claims supported by multiple independent sources.
=== CONTRADICTIONS ===
Identify conflicting claims and their likely cause (version differences, environment, outdated info).
===... | web-research-coding-5m-1.1.0 | |
d1ef7dfeb2346bd3a0bca3d6 | train | deep_technical_analysis | pypi | https://pypi.org/project/fastapi/ | fastapi | education | shell | postgresql | Perform a deep multi-layer analysis of postgresql for a education 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": "fastapi", "source_url": "https://pypi.org/project/fastapi/", "source_type": "package", "topic... | === 1. PROBLEM ===
Define the exact problem involving postgresql. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around postgresql. Use 'fastapi' as a source anchor and identify relevant APIs, dependencies, versions, standards... | web-research-coding-5m-1.1.0 | |
7f9e3f4a78dfbeb2095167da | train | evidence_extraction | huggingface | https://huggingface.co/datasets/Reset23/the-stack-v2-python | Reset23/the-stack-v2-python | community | swift | observability | Extract verifiable evidence about observability from the given source. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Reset23/the-stack-v2-python", "source_url": "https://huggingface.co/datasets/Reset23/the-stac... | === SOURCE ===
Reset23/the-stack-v2-python
https://huggingface.co/datasets/Reset23/the-stack-v2-python
=== 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 an... | web-research-coding-5m-1.1.0 | |
8aadaa28c1f316447efe8937 | train | information_architecture | npm | https://www.npmjs.com/package/next | next | dashboard | python | nodejs | Design the information architecture for nodejs. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "next", "source_url": "https://www.npmjs.com/package/next", "source_type": "package", "topic":... | Organize content into logical categories, navigation levels, search, filtering, and discoverable paths. | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
4da91e9a0bcfd5261227a8d7 | train | refactoring_legacy_code | gitlab | https://gitlab.com/FirstTerraner/proclubs-api | FirstTerraner/proclubs-api | social_app | ruby | linux | Refactor a ruby system related to linux. Focus on refactoring legacy code. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "FirstTerraner/proclubs-api", "source_url": "https://gitlab.com/FirstTerraner/proclubs-api", "... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Characterize existing behavior first and incrementally replace risky legacy structures.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implication... | web-research-coding-5m-1.1.0 | |
2c4a65a37e5ff3e665abc2b5 | train | information_architecture | stackexchange | https://stackoverflow.com/questions/13315131/enforcing-the-type-of-the-indexed-members-of-a-typescript-object | Enforcing the type of the indexed members of a Typescript object? | community | php | python | Design the information architecture for python. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Enforcing the type of the indexed members of a Typescript object?", "source_url": "https://st... | Organize content into logical categories, navigation levels, search, filtering, and discoverable paths. | web-research-coding-5m-1.1.0 | |
e87d3d520c56e4af133ae107 | train | design_to_code | npm | https://www.npmjs.com/package/axios | axios | documentation | sql | web_performance | Translate a documentation design into maintainable sql code. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "axios", "source_url": "https://www.npmjs.com/package/axios", "source_type": "package", "topic... | 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 | |
5860eb91ac40248cffbb441a | train | refactoring_security | huggingface | https://huggingface.co/datasets/philschmid/markdown-documentation-transformers | philschmid/markdown-documentation-transformers | community | go | developer_experience | Refactor a go system related to developer_experience. Focus on refactoring security. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "philschmid/markdown-documentation-transformers", "source_url": "https://huggingface.co/datase... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Strengthen validation, trust boundaries, authorization, and secret handling.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Ident... | web-research-coding-5m-1.1.0 | |
258b9c149e4352521a2bf486 | train | repository_issue_reasoning | huggingface | https://huggingface.co/datasets/BatsResearch/trove-lib-documentation-assets | BatsResearch/trove-lib-documentation-assets | search_interface | shell | database | Perform a deep multi-layer analysis of database for a search_interface 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": "BatsResearch/trove-lib-documentation-assets", "source_url": "https://huggingface.co/datasets/... | === 1. PROBLEM ===
Define the exact problem involving database. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around database. Use 'BatsResearch/trove-lib-documentation-assets' as a source anchor and identify relevant APIs, d... | web-research-coding-5m-1.1.0 | |
9936afa04a0f835ee256d7f6 | train | debugging_experience | stackexchange | https://stackoverflow.com/questions/4752626/epoch-vs-iteration-when-training-neural-networks | Epoch vs Iteration when training neural networks | social_app | kotlin | sql | Perform a deep developer-experience analysis for a kotlin project involving sql. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Epoch vs Iteration when training neural networks", "source_url": "https://stackoverflow.com/q... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
7ef977c8a18e2ce6e089325e | train | cli_experience | huggingface | https://huggingface.co/datasets/mondk/documentation-images | mondk/documentation-images | finance | css | linux | Perform a deep developer-experience analysis for a css project involving linux. | {"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... | === 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 | |
3d0b6810ae4ac1c2305044fd | train | multi_layer_analysis | stackexchange | https://stackoverflow.com/questions/4810841/pretty-print-json-using-javascript | pretty-print JSON using JavaScript | ecommerce | rust | testing | Perform a deep multi-layer analysis of testing for a ecommerce using rust. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "pretty-print JSON using JavaScript", "source_url": "https://stackoverflow.com/questions/48108... | === 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 'pretty-print JSON using JavaScript' as a source anchor and identify relevant APIs, dependencies... | web-research-coding-5m-1.1.0 | |
7a705adecbdc654a6a6d1ef7 | train | integration_testing | mdn | https://developer.mozilla.org/en-US/docs/Web/CSS | CSS | education | shell | deep_learning | Design integration tests for a shell system involving deep_learning. | {"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... | Test real component boundaries, persistence, configuration, external interfaces, errors, cleanup, and realistic workflows. | web-research-coding-5m-1.1.0 | |
bc4241c11ecf1bc45449f574 | train | multi_layer_analysis | github | https://github.com/immich-app/immich | immich-app/immich | social_app | kotlin | distributed_systems | Perform a deep multi-layer analysis of distributed_systems for a social_app using kotlin. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "immich-app/immich", "source_url": "https://github.com/immich-app/immich", "source_type": "rep... | === 1. PROBLEM ===
Define the exact problem involving distributed_systems. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around distributed_systems. Use 'immich-app/immich' as a source anchor and identify relevant APIs, depen... | web-research-coding-5m-1.1.0 | |
fe44255071cf7347a5b23cef | train | developer_onboarding | codeberg | https://codeberg.org/UI-Programming-23-24/01-Web-Basics-And-Git-Jack-Sweeney2 | UI-Programming-23-24/01-Web-Basics-And-Git-Jack-Sweeney2 | community | rust | backend | Perform a deep developer-experience analysis for a rust project involving backend. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "UI-Programming-23-24/01-Web-Basics-And-Git-Jack-Sweeney2", "source_url": "https://codeberg.or... | === 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 | |
9dd9c88e1bb42545aea4e75a | train | responsive_design | huggingface | https://huggingface.co/datasets/leo009/python-programming-instructions | leo009/python-programming-instructions | admin_panel | php | debugging | Create a responsive design strategy for a admin_panel. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "leo009/python-programming-instructions", "source_url": "https://huggingface.co/datasets/leo00... | Define mobile, tablet, and desktop behavior, layout transitions, navigation, content priority, typography, and interaction targets. | web-research-coding-5m-1.1.0 | |
0a217ec9d9ad9777dd2ab242 | train | multi_layer_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/JavaScript | JavaScript | blog | kotlin | web_accessibility | Perform a deep multi-layer analysis of web_accessibility for a blog using kotlin. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "JavaScript", "source_url": "https://developer.mozilla.org/en-US/docs/Web/JavaScript", "source... | === 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 'JavaScript' as a source anchor and identify relevant APIs, dependencies, ve... | web-research-coding-5m-1.1.0 | |
7d6eaa29d75a45d09c286dc4 | train | local_development_experience | codeberg | https://codeberg.org/m5blum/acweb | m5blum/acweb | documentation | javascript | fullstack | Perform a deep developer-experience analysis for a javascript project involving fullstack. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "m5blum/acweb", "source_url": "https://codeberg.org/m5blum/acweb", "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 | |
4d8cdbff4a793dd2fa95bd3c | train | react_generation | codeberg | https://codeberg.org/mclare/2019-python-pandas | mclare/2019-python-pandas | admin_panel | swift | software_architecture | Design React components for a admin_panel. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "mclare/2019-python-pandas", "source_url": "https://codeberg.org/mclare/2019-python-pandas", "... | 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 |
e5df3b8d749f6b2e2884dd27 | train | design_to_code | pypi | https://pypi.org/project/gradio/ | gradio | developer_tool | kotlin | algorithms | Translate a developer_tool design into maintainable kotlin code. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "gradio", "source_url": "https://pypi.org/project/gradio/", "source_type": "package", "topic":... | 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 | |
4dbc4f96a3d3acbe4f9021e9 | train | upgrade_experience | mdn | https://developer.mozilla.org/en-US/docs/Web/CSS | CSS | developer_tool | kotlin | javascript | Perform a deep developer-experience analysis for a kotlin project involving javascript. | {"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 | |
44545677c98a2fa0764b4fb6 | train | architecture_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/Accessibility | Accessibility | analytics | go | debugging | Perform a deep multi-layer analysis of debugging for a analytics using go. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Accessibility", "source_url": "https://developer.mozilla.org/en-US/docs/Web/Accessibility", "... | === 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 'Accessibility' as a source anchor and identify relevant APIs, dependencies, versions, stand... | web-research-coding-5m-1.1.0 | |
5dee944732b4876361b667f1 | train | maintainability_analysis | npm | https://www.npmjs.com/package/jest | jest | productivity | ruby | web_performance | Perform a deep multi-layer analysis of web_performance for a productivity using ruby. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "jest", "source_url": "https://www.npmjs.com/package/jest", "source_type": "package", "topic":... | === 1. PROBLEM ===
Define the exact problem involving web_performance. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around web_performance. Use 'jest' as a source anchor and identify relevant APIs, dependencies, versions, st... | web-research-coding-5m-1.1.0 | |
06d3f30c4666548b58ff2428 | train | refactoring_scalability | huggingface | https://huggingface.co/datasets/hongliu9903/stack_edu_javascript | hongliu9903/stack_edu_javascript | ecommerce | go | algorithms | Refactor a go system related to algorithms. Focus on refactoring scalability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "hongliu9903/stack_edu_javascript", "source_url": "https://huggingface.co/datasets/hongliu9903... | === 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 | |
9d94cb514e4f27d21baae507 | train | refactoring | github | https://github.com/mui/material-ui | mui/material-ui | admin_panel | html | distributed_systems | Create a production coding task in html for distributed_systems. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "mui/material-ui", "source_url": "https://github.com/mui/material-ui", "source_type": "reposit... | Provide implementation requirements, edge cases, testing requirements, security considerations, performance constraints, and documentation requirements. | web-research-coding-5m-1.1.0 | |
8b9889efb7e2066051bfb343 | train | responsive_design | huggingface | https://huggingface.co/datasets/nvidia/Nemotron-SFT-Competitive-Programming-v2 | nvidia/Nemotron-SFT-Competitive-Programming-v2 | finance | python | deep_learning | Create a responsive design strategy for a finance. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "nvidia/Nemotron-SFT-Competitive-Programming-v2", "source_url": "https://huggingface.co/datase... | Define mobile, tablet, and desktop behavior, layout transitions, navigation, content priority, typography, and interaction targets. | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
388e5edb1019794a012fb902 | train | tradeoff_analysis | huggingface | https://huggingface.co/datasets/Mo7art/Stack2Graph_VD_javascript | Mo7art/Stack2Graph_VD_javascript | social_app | go | ci_cd | Perform a deep multi-layer analysis of ci_cd for a social_app using go. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Mo7art/Stack2Graph_VD_javascript", "source_url": "https://huggingface.co/datasets/Mo7art/Stac... | === 1. PROBLEM ===
Define the exact problem involving ci_cd. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around ci_cd. Use 'Mo7art/Stack2Graph_VD_javascript' as a source anchor and identify relevant APIs, dependencies, vers... | web-research-coding-5m-1.1.0 | |
bdfe5e3e291482a7fb54e580 | train | repository_understanding | codeberg | https://codeberg.org/mi-skam/_gcp-python-uv | mi-skam/_gcp-python-uv | social_app | typescript | security | Perform a deep multi-layer analysis of security for a social_app using typescript. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "mi-skam/_gcp-python-uv", "source_url": "https://codeberg.org/mi-skam/_gcp-python-uv", "source... | === 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 'mi-skam/_gcp-python-uv' as a source anchor and identify relevant APIs, dependencies, versions... | web-research-coding-5m-1.1.0 | |
ea59ea7751cb6918d43ea00c | train | code_review | web_docs | https://docs.djangoproject.com/ | Django Documentation | search_interface | php | authentication | Perform a production code review of php code related to authentication. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Django Documentation", "source_url": "https://docs.djangoproject.com/", "source_type": "docum... | Review correctness, security, performance, readability, architecture, testing, maintainability, and error handling. | web-research-coding-5m-1.1.0 | |
8655c1f2bf4d9411d743f081 | train | upgrade_experience | huggingface | https://huggingface.co/datasets/AtharvImmverse/NemoTron-OCR-Synthetic-Multilingual-v1 | AtharvImmverse/NemoTron-OCR-Synthetic-Multilingual-v1 | social_app | shell | mongodb | Perform a deep developer-experience analysis for a shell project involving mongodb. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "AtharvImmverse/NemoTron-OCR-Synthetic-Multilingual-v1", "source_url": "https://huggingface.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 | |
213fcaf21ba15ac3c46452a4 | train | html_generation | npm | https://www.npmjs.com/package/playwright | playwright | admin_panel | dart | cloud | Create semantic HTML for a admin_panel about cloud. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "playwright", "source_url": "https://www.npmjs.com/package/playwright", "source_type": "packag... | Use semantic landmarks, headings, accessible controls, meaningful labels, and correct document structure. | <!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport"
content="width=device-width, initial-scale=1">
<title>Accessible Application</title>
</head>
<body>
<main>
<h1>Application</h1>
</main>
</body>
</html> | web-research-coding-5m-1.1.0 |
184e35fb35aa8323e1ff8d50 | train | design_tokens | stackexchange | https://stackoverflow.com/questions/5654447/whats-the-difference-between-scss-and-sass | What's the difference between SCSS and Sass? | documentation | php | redis | Create design tokens for a documentation. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "What's the difference between SCSS and Sass?", "source_url": "https://stackoverflow.com/q... | Define reusable tokens for typography, spacing, radii, sizing, elevation, interaction states, and responsive behavior. | web-research-coding-5m-1.1.0 | |
e3c84984d037213ce898cecb | train | refactoring_legacy_code | codeberg | https://codeberg.org/KokaKiwi/_cargo-index | KokaKiwi/_cargo-index | portfolio | swift | api_design | Refactor a swift system related to api_design. Focus on refactoring legacy code. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "KokaKiwi/_cargo-index", "source_url": "https://codeberg.org/KokaKiwi/_cargo-index", "source_t... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Characterize existing behavior first and incrementally replace risky legacy structures.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implication... | web-research-coding-5m-1.1.0 | |
be2c3ba19e034d7771fa739f | train | information_architecture | npm | https://www.npmjs.com/package/svelte | svelte | documentation | shell | 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": "svelte", "source_url": "https://www.npmjs.com/package/svelte", "source_type": "package", "top... | Organize content into logical categories, navigation levels, search, filtering, and discoverable paths. | web-research-coding-5m-1.1.0 | |
04c6d641bb119f57112b5171 | train | repository_understanding | mdn | https://developer.mozilla.org/en-US/docs/Web/JavaScript | JavaScript | documentation | css | nodejs | Perform a deep multi-layer analysis of nodejs for a documentation 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": "JavaScript", "source_url": "https://developer.mozilla.org/en-US/docs/Web/JavaScript", "source... | === 1. PROBLEM ===
Define the exact problem involving nodejs. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around nodejs. Use 'JavaScript' as a source anchor and identify relevant APIs, dependencies, versions, standards, and... | web-research-coding-5m-1.1.0 | |
e086127357d70ce7cba796b3 | train | accessibility_fix | mdn | https://developer.mozilla.org/en-US/docs/Web/CSS | CSS | developer_tool | css | redis | Create an accessibility remediation plan for a developer_tool. | {"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... | Check semantic HTML, keyboard navigation, focus management, accessible names, labels, errors, contrast, and screen-reader behavior. | web-research-coding-5m-1.1.0 | |
aeabf7b4527b43ec23215683 | train | repository_understanding | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model | DOM | analytics | cpp | authorization | Perform a deep multi-layer analysis of authorization for a analytics 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": "DOM", "source_url": "https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model",... | === 1. PROBLEM ===
Define the exact problem involving authorization. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around authorization. Use 'DOM' as a source anchor and identify relevant APIs, dependencies, versions, standar... | web-research-coding-5m-1.1.0 | |
b253c8e102fdf9951459d619 | train | css_generation | mdn | https://developer.mozilla.org/en-US/docs/Web/API | Web APIs | marketplace | c | mongodb | Create responsive CSS for a marketplace. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Web APIs", "source_url": "https://developer.mozilla.org/en-US/docs/Web/API", "source_type": "... | Use reusable rules, responsive layouts, scalable typography, spacing, focus states, and mobile support. | :root {
--space: 1rem;
}
* {
box-sizing: border-box;
}
body {
margin: 0;
font-family: system-ui, sans-serif;
}
.container {
width: min(100% - 2rem, 1200px);
margin-inline: auto;
} | web-research-coding-5m-1.1.0 |
a01d51f107412d2cc1b8c111 | train | css_generation | huggingface | https://huggingface.co/datasets/libalpm64/mojo-programming | libalpm64/mojo-programming | productivity | javascript | deep_learning | Create responsive CSS for a productivity. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "libalpm64/mojo-programming", "source_url": "https://huggingface.co/datasets/libalpm64/mojo-pr... | Use reusable rules, responsive layouts, scalable typography, spacing, focus states, and mobile support. | :root {
--space: 1rem;
}
* {
box-sizing: border-box;
}
body {
margin: 0;
font-family: system-ui, sans-serif;
}
.container {
width: min(100% - 2rem, 1200px);
margin-inline: auto;
} | web-research-coding-5m-1.1.0 |
555d9de7f66a3bb4c1ce36d9 | train | refactoring_api | npm | https://www.npmjs.com/package/next | next | dashboard | dart | data_structures | Refactor a dart system related to data_structures. Focus on refactoring api. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "next", "source_url": "https://www.npmjs.com/package/next", "source_type": "package", "topic":... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
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 | |
4d2f1fade5fbcc2431fcfc95 | train | data_structure_design | npm | https://www.npmjs.com/package/vite | vite | ecommerce | c | data_structures | Design a data structure in c for data_structures. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "vite", "source_url": "https://www.npmjs.com/package/vite", "source_type": "package", "topic":... | Explain representation, operations, complexity, memory trade-offs, and workload suitability. | web-research-coding-5m-1.1.0 | |
d5b9823e15b7e90466ad036b | train | repository_comparison | github | https://github.com/fighting41love/funNLP | fighting41love/funNLP | search_interface | scala | graphql | Perform a deep multi-layer analysis of graphql for a search_interface 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": "fighting41love/funNLP", "source_url": "https://github.com/fighting41love/funNLP", "source_typ... | === 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 'fighting41love/funNLP' as a source anchor and identify relevant APIs, dependencies, versions, s... | web-research-coding-5m-1.1.0 | |
f48b6b86af15ef1340910f94 | train | data_structure_design | pypi | https://pypi.org/project/sqlalchemy/ | sqlalchemy | finance | rust | nlp | Design a data structure in rust for nlp. | {"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", ... | Explain representation, operations, complexity, memory trade-offs, and workload suitability. | web-research-coding-5m-1.1.0 | |
ef2ab357005638925d7436ca | train | build_experience | huggingface | https://huggingface.co/datasets/AffineFoundation/rl-python | AffineFoundation/rl-python | social_app | cpp | machine_learning | Perform a deep developer-experience analysis for a cpp project involving machine_learning. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "AffineFoundation/rl-python", "source_url": "https://huggingface.co/datasets/AffineFoundation/... | === 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 | |
b83cfbc01c616af0d524ef49 | train | research_plan | web_docs | https://kubernetes.io/docs/ | Kubernetes Documentation | analytics | python | linux | Build a structured research plan to deeply understand linux. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Kubernetes Documentation", "source_url": "https://kubernetes.io/docs/", "source_type": "docum... | === GOAL ===
Produce a reliable, current, and actionable understanding of linux.
=== PHASES ===
1. Orientation — skim official docs and README.
2. Deep read — study specs, RFCs, changelogs.
3. Hands-on — reproduce examples locally.
4. Comparison — compare alternatives and trade-offs.
5. Synthesis — write findings with... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
983f4d99d00aefa7a6e2ce1b | train | research_plan | gitlab | https://gitlab.com/vgg/via-suite/via | vgg/via-suite/via | saas | cpp | open_source | Build a structured research plan to deeply understand open_source. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "vgg/via-suite/via", "source_url": "https://gitlab.com/vgg/via-suite/via", "source_type": "rep... | === GOAL ===
Produce a reliable, current, and actionable understanding of open_source.
=== PHASES ===
1. Orientation — skim official docs and README.
2. Deep read — study specs, RFCs, changelogs.
3. Hands-on — reproduce examples locally.
4. Comparison — compare alternatives and trade-offs.
5. Synthesis — write finding... | web-research-coding-5m-1.1.0 | |
0e14c69f9f41bcb58868d293 | train | code_explanation | web_docs | https://doc.rust-lang.org/ | Rust Documentation | developer_tool | shell | computer_vision | Explain a shell implementation related to computer_vision. | {"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... | Explain inputs, outputs, control flow, algorithms, complexity, edge cases, errors, and maintainability. | web-research-coding-5m-1.1.0 | |
e6b63dcf201f268fd2f746ad | train | design_components | stackexchange | https://stackoverflow.com/questions/30626030/can-you-force-a-react-component-to-rerender-without-calling-setstate | Can you force a React component to rerender without calling setState? | blog | typescript | backend | Create a component architecture for a blog. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Can you force a React component to rerender without calling setState?", "source_url": "https:... | Define primitive components, composite components, variants, states, composition rules, and accessibility contracts. | web-research-coding-5m-1.1.0 | |
cb85d2086ab3cfde15eeeb3d | train | design_review | npm | https://www.npmjs.com/package/typescript | typescript | ecommerce | cpp | rest_api | Perform a professional design review of a ecommerce. | {"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... | Review hierarchy, consistency, responsiveness, accessibility, interaction design, content clarity, and implementation feasibility. | web-research-coding-5m-1.1.0 | |
148ce4b74621a51ef7607003 | train | evidence_chain_analysis | huggingface | https://huggingface.co/datasets/Mo7art/Stack2Graph_VD_javascript | Mo7art/Stack2Graph_VD_javascript | search_interface | c | distributed_systems | Perform a deep multi-layer analysis of distributed_systems for a search_interface using c. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Mo7art/Stack2Graph_VD_javascript", "source_url": "https://huggingface.co/datasets/Mo7art/Stac... | === 1. PROBLEM ===
Define the exact problem involving distributed_systems. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around distributed_systems. Use 'Mo7art/Stack2Graph_VD_javascript' as a source anchor and identify relev... | web-research-coding-5m-1.1.0 | |
e713125231fc18e1741fee74 | train | multi_hop_research | huggingface | https://huggingface.co/datasets/nomic-ai/cornstack-javascript-v1 | nomic-ai/cornstack-javascript-v1 | analytics | typescript | serverless | Perform multi-hop research about serverless: 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": "nomic-ai/cornstack-javascript-v1", "source_url": "https://huggingface.co/datasets/nomic-ai/co... | === HOP 1 ===
Start at: nomic-ai/cornstack-javascript-v1
https://huggingface.co/datasets/nomic-ai/cornstack-javascript-v1
Extract core claims and references.
=== HOP 2 ===
Follow references to official docs, RFCs, or specs.
Extract primary-source evidence.
=== HOP 3 ===
Check community discussions for real-world issu... | web-research-coding-5m-1.1.0 | |
70c7e928642bf90e6423600e | train | html_generation | web_docs | https://fastapi.tiangolo.com/ | FastAPI Documentation | social_app | ruby | backend | Create semantic HTML for a social_app about backend. | {"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... | Use semantic landmarks, headings, accessible controls, meaningful labels, and correct document structure. | <!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport"
content="width=device-width, initial-scale=1">
<title>Accessible Application</title>
</head>
<body>
<main>
<h1>Application</h1>
</main>
</body>
</html> | web-research-coding-5m-1.1.0 |
d1be1f13f4ffea395028ed0d | train | visual_hierarchy | web_docs | https://git-scm.com/doc | Git Documentation | social_app | html | postgresql | Improve visual hierarchy in a social_app. | {"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", ... | Use heading structure, typography, spacing, grouping, alignment, contrast, and consistent affordances. | web-research-coding-5m-1.1.0 | |
1ebc2d1ccc14a47e2c63b448 | train | repository_documentation | npm | https://www.npmjs.com/package/express | express | saas | python | javascript | Perform a deep multi-layer analysis of javascript for a saas 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": "express", "source_url": "https://www.npmjs.com/package/express", "source_type": "package", "t... | === 1. PROBLEM ===
Define the exact problem involving javascript. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around javascript. Use 'express' as a source anchor and identify relevant APIs, dependencies, versions, standards... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
dd94bb410d77527473e5e76a | train | evidence_extraction | stackexchange | https://stackoverflow.com/questions/16056591/font-scaling-based-on-size-of-container | Font scaling based on size of container | dashboard | javascript | authentication | Extract verifiable evidence about authentication from the given source. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Font scaling based on size of container", "source_url": "https://stackoverflow.com/questions/... | === SOURCE ===
Font scaling based on size of container
https://stackoverflow.com/questions/16056591/font-scaling-based-on-size-of-container
=== 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... | web-research-coding-5m-1.1.0 | |
be0db03d1c3e4867591ac677 | train | source_comparison | mdn | https://developer.mozilla.org/en-US/docs/Web/Accessibility | Accessibility | developer_tool | typescript | observability | Compare multiple sources about observability 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": "Accessibility", "source_url": "https://developer.mozilla.org/en-US/docs/Web/Accessibility", "... | === SOURCES ===
- Accessibility (https://developer.mozilla.org/en-US/docs/Web/Accessibility)
- Official documentation
- Community discussions
=== AGREEMENTS ===
Identify claims supported by multiple independent sources.
=== CONTRADICTIONS ===
Identify conflicting claims and their likely cause (version differences, en... | web-research-coding-5m-1.1.0 | |
9a5ec3d56156d6fff358340d | train | documentation_experience | pypi | https://pypi.org/project/streamlit/ | streamlit | saas | javascript | data_structures | Perform a deep developer-experience analysis for a javascript project involving data_structures. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "streamlit", "source_url": "https://pypi.org/project/streamlit/", "source_type": "package", "t... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
7a23d3a76d1c9ad0118bdce9 | train | refactoring_dependency | mdn | https://developer.mozilla.org/en-US/docs/Web/JavaScript | JavaScript | ecommerce | shell | css | Refactor a shell system related to css. Focus on refactoring dependency. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "JavaScript", "source_url": "https://developer.mozilla.org/en-US/docs/Web/JavaScript", "source... | === 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 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.