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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
f9923bd51c9bb3c34d3ee516 | test | repository_understanding | stackexchange | https://stackoverflow.com/questions/18111657/how-to-get-names-of-enum-entries | How to get names of enum entries? | developer_tool | python | nodejs | Perform a deep multi-layer analysis of nodejs for a developer_tool 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": "How to get names of enum entries?", "source_url": "https://stackoverflow.com/questions/181116... | === 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 'How to get names of enum entries?' as a source anchor and identify relevant APIs, dependencies, v... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
b2a45aa641660d9797aee758 | test | repository_architecture | huggingface | https://huggingface.co/datasets/McKlay/documentation-images | McKlay/documentation-images | education | java | nextjs | Perform a deep multi-layer analysis of nextjs for a education using java. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "McKlay/documentation-images", "source_url": "https://huggingface.co/datasets/McKlay/documenta... | === 1. PROBLEM ===
Define the exact problem involving nextjs. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around nextjs. Use 'McKlay/documentation-images' as a source anchor and identify relevant APIs, dependencies, version... | web-research-coding-5m-1.1.0 | |
002b6f70c86c95b372aa3616 | test | source_comparison | npm | https://www.npmjs.com/package/playwright | playwright | developer_tool | python | devops | Compare multiple sources about devops 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": "playwright", "source_url": "https://www.npmjs.com/package/playwright", "source_type": "packag... | === SOURCES ===
- playwright (https://www.npmjs.com/package/playwright)
- Official documentation
- Community discussions
=== AGREEMENTS ===
Identify claims supported by multiple independent sources.
=== CONTRADICTIONS ===
Identify conflicting claims and their likely cause (version differences, environment, outdated i... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
ad9b6e50ad8541c16a143b5a | test | upgrade_experience | stackexchange | https://stackoverflow.com/questions/37233735/interfaces-vs-types-in-typescript | Interfaces vs Types in TypeScript | admin_panel | php | mongodb | Perform a deep developer-experience analysis for a php project involving mongodb. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Interfaces vs Types in TypeScript", "source_url": "https://stackoverflow.com/questions/372337... | === 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 | |
7f901cafec631664744fd54f | test | design_tokens | mdn | https://developer.mozilla.org/en-US/docs/Web/HTML | HTML | marketplace | javascript | deep_learning | Create design tokens for a marketplace. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "HTML", "source_url": "https://developer.mozilla.org/en-US/docs/Web/HTML", "source_type": "doc... | Define reusable tokens for typography, spacing, radii, sizing, elevation, interaction states, and responsive behavior. | web-research-coding-5m-1.1.0 | |
8d2001aa3c23b83d7be6267b | test | design_accessibility | npm | https://www.npmjs.com/package/typescript | typescript | portfolio | c | postgresql | Audit accessibility for a portfolio. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "typescript", "source_url": "https://www.npmjs.com/package/typescript", "source_type": "packag... | Check semantic structure, keyboard navigation, focus visibility, accessible names, labels, errors, contrast, and screen-reader behavior. | web-research-coding-5m-1.1.0 | |
cf1e48fa8f853ffaecfbdb1a | test | repository_comparison | web_docs | https://docs.python.org/3/ | Python Documentation | social_app | typescript | backend | Perform a deep multi-layer analysis of backend 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": "Python Documentation", "source_url": "https://docs.python.org/3/", "source_type": "documentat... | === 1. PROBLEM ===
Define the exact problem involving backend. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around backend. Use 'Python Documentation' as a source anchor and identify relevant APIs, dependencies, versions, st... | web-research-coding-5m-1.1.0 | |
e1f27abd405bd8062f66102a | test | refactoring_testability | huggingface | https://huggingface.co/datasets/Mo7art/Stack2Graph_KG_python | Mo7art/Stack2Graph_KG_python | ecommerce | cpp | distributed_systems | Refactor a cpp system related to distributed_systems. Focus on refactoring testability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Mo7art/Stack2Graph_KG_python", "source_url": "https://huggingface.co/datasets/Mo7art/Stack2Gr... | === 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 | |
6b7e2fdd0a6f101e9fc32683 | test | refactoring_architecture | huggingface | https://huggingface.co/datasets/ByteDance-Seed/Code-Contests-Plus | ByteDance-Seed/Code-Contests-Plus | dashboard | kotlin | css | Refactor a kotlin system related to css. Focus on refactoring architecture. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "ByteDance-Seed/Code-Contests-Plus", "source_url": "https://huggingface.co/datasets/ByteDance-... | === 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 | |
21e5ca39434fee3f472a6c0d | test | typescript_generation | web_docs | https://fastapi.tiangolo.com/ | FastAPI Documentation | search_interface | sql | rest_api | Implement TypeScript logic for a search_interface. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "FastAPI Documentation", "source_url": "https://fastapi.tiangolo.com/", "source_type": "docume... | Use explicit types, interfaces, safe narrowing, validation, and maintainable modules. | function validateInput(value) {
if (!value || value.trim().length === 0) {
throw new Error("Input is required");
}
return value.trim();
} | web-research-coding-5m-1.1.0 |
1ffeb058604c1aa1ea034a2b | test | refactoring_performance | huggingface | https://huggingface.co/datasets/Nan-Do/code-search-net-python | Nan-Do/code-search-net-python | dashboard | c | web_accessibility | Refactor a c system related to web_accessibility. Focus on refactoring performance. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Nan-Do/code-search-net-python", "source_url": "https://huggingface.co/datasets/Nan-Do/code-se... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Reduce unnecessary computation, allocations, I/O, and network requests.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify d... | web-research-coding-5m-1.1.0 | |
aa7963de09f209213361662c | test | build_experience | huggingface | https://huggingface.co/datasets/gus-mxx/A1-Machine-Learning-Data-Challenge | gus-mxx/A1-Machine-Learning-Data-Challenge | portfolio | go | deep_learning | Perform a deep developer-experience analysis for a go project involving deep_learning. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "gus-mxx/A1-Machine-Learning-Data-Challenge", "source_url": "https://huggingface.co/datasets/g... | === 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 | |
30ab2c65e34a924a5152b0ec | test | visual_hierarchy | huggingface | https://huggingface.co/datasets/multilingual-tts/open-bible | multilingual-tts/open-bible | portfolio | swift | python | Improve visual hierarchy in a portfolio. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "multilingual-tts/open-bible", "source_url": "https://huggingface.co/datasets/multilingual-tts... | Use heading structure, typography, spacing, grouping, alignment, contrast, and consistent affordances. | web-research-coding-5m-1.1.0 | |
9123781b3921fefab7ca1959 | test | design_to_code | pypi | https://pypi.org/project/typer/ | typer | documentation | shell | serverless | Translate a documentation design into maintainable shell code. | {"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": "... | 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 | |
9d32047075d6f4b1181e3bd2 | test | refactoring_maintainability | web_docs | https://fastapi.tiangolo.com/ | FastAPI Documentation | education | java | css | Refactor a java system related to css. Focus on refactoring maintainability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "FastAPI Documentation", "source_url": "https://fastapi.tiangolo.com/", "source_type": "docume... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Improve cohesion, reduce coupling, isolate volatile behavior, and remove duplication.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.... | web-research-coding-5m-1.1.0 | |
cd1fed71c41556adf253607f | test | security_review | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model | DOM | landing_page | cpp | postgresql | Perform a security review of a landing_page application. | {"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",... | Review authentication, authorization, input validation, XSS, CSRF, injection risks, secrets, dependencies, security headers, and logging. | web-research-coding-5m-1.1.0 | |
080df554edcac9afda141606 | test | unit_testing | gitlab | https://gitlab.com/mattbas/python-lottie | mattbas/python-lottie | finance | sql | documentation | Create a unit-testing strategy for sql code involving documentation. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "mattbas/python-lottie", "source_url": "https://gitlab.com/mattbas/python-lottie", "source_typ... | Cover normal cases, edge cases, invalid inputs, failure modes, mocks, and regression tests. | web-research-coding-5m-1.1.0 | |
2b60dbd1d37b4649f6b7f9a5 | test | typescript_generation | pypi | https://pypi.org/project/numpy/ | numpy | analytics | css | nodejs | Implement TypeScript logic for a analytics. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "numpy", "source_url": "https://pypi.org/project/numpy/", "source_type": "package", "topic": "... | Use explicit types, interfaces, safe narrowing, validation, and maintainable modules. | function validateInput(value) {
if (!value || value.trim().length === 0) {
throw new Error("Input is required");
}
return value.trim();
} | web-research-coding-5m-1.1.0 |
cbfbaf6f0bcabefb2d339327 | test | search_intent_classification | huggingface | https://huggingface.co/datasets/priyasarath1531/web_development | priyasarath1531/web_development | landing_page | rust | postgresql | Classify the search intent for a query about postgresql. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "priyasarath1531/web_development", "source_url": "https://huggingface.co/datasets/priyasarath1... | === POSSIBLE INTENTS ===
- informational (learn a concept)
- navigational (find a specific site/tool)
- transactional (install / download / run)
- troubleshooting (fix an error)
- comparative (choose between options)
=== EXAMPLE QUERY ===
"postgresql vs alternatives"
=== CLASSIFICATION ===
Comparative / informational... | web-research-coding-5m-1.1.0 | |
18607a96d05bc5e4ba260ce4 | test | deep_technical_analysis | stackexchange | https://stackoverflow.com/questions/35677724/tensorflow-why-was-python-the-chosen-language | TensorFlow, why was python the chosen language? | education | c | observability | Perform a deep multi-layer analysis of observability for a education 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": "TensorFlow, why was python the chosen language?", "source_url": "https://stackoverflow.com/qu... | === 1. PROBLEM ===
Define the exact problem involving observability. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around observability. Use 'TensorFlow, why was python the chosen language?' as a source anchor and identify re... | web-research-coding-5m-1.1.0 | |
50ca6b4cc1372fc79d546712 | test | dx_analysis | npm | https://www.npmjs.com/package/eslint | eslint | productivity | go | html | Perform a deep developer-experience analysis for a go project involving html. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "eslint", "source_url": "https://www.npmjs.com/package/eslint", "source_type": "package", "top... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
91380babf0ae1341e2762ff3 | test | design_system | web_docs | https://doc.rust-lang.org/ | Rust Documentation | documentation | scala | kubernetes | Create a scalable design system for a documentation. | {"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... | Define tokens, typography, spacing, components, variants, states, responsive rules, accessibility, and documentation. | web-research-coding-5m-1.1.0 | |
0372ceb913b133c350a8ec52 | test | ui_design | huggingface | https://huggingface.co/datasets/CoIR-Retrieval/CodeSearchNet-ccr-javascript-queries-corpus | CoIR-Retrieval/CodeSearchNet-ccr-javascript-queries-corpus | landing_page | shell | redis | Design a production-quality UI for a landing_page focused on redis. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "CoIR-Retrieval/CodeSearchNet-ccr-javascript-queries-corpus", "source_url": "https://huggingfa... | Define layout, typography, spacing, hierarchy, components, states, responsive behavior, and accessibility. | web-research-coding-5m-1.1.0 | |
21208252de1756b5bcdf128e | test | form_ui | mdn | https://developer.mozilla.org/en-US/docs/Web/Accessibility | Accessibility | admin_panel | swift | user_experience | Design an accessible form for user_experience. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Accessibility", "source_url": "https://developer.mozilla.org/en-US/docs/Web/Accessibility", "... | Use labels, validation, clear errors, keyboard navigation, appropriate autocomplete, and accessible status messaging. | web-research-coding-5m-1.1.0 | |
a6ca27a84b670c801ce41708 | test | architecture_analysis | gitlab | https://gitlab.com/mlreef/mlreef | mlreef/mlreef | education | dart | algorithms | Perform a deep multi-layer analysis of algorithms for a education 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": "mlreef/mlreef", "source_url": "https://gitlab.com/mlreef/mlreef", "source_type": "repository"... | === 1. PROBLEM ===
Define the exact problem involving algorithms. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around algorithms. Use 'mlreef/mlreef' as a source anchor and identify relevant APIs, dependencies, versions, sta... | web-research-coding-5m-1.1.0 | |
3080994365a6795864a06ee1 | test | deep_technical_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/HTML | HTML | saas | cpp | web_performance | Perform a deep multi-layer analysis of web_performance for a saas 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": "HTML", "source_url": "https://developer.mozilla.org/en-US/docs/Web/HTML", "source_type": "doc... | === 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 'HTML' as a source anchor and identify relevant APIs, dependencies, versions, st... | web-research-coding-5m-1.1.0 | |
d6ca73d6fe47609e1098b852 | test | dashboard | pypi | https://pypi.org/project/streamlit/ | streamlit | analytics | ruby | nextjs | Design a production dashboard for nextjs. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "streamlit", "source_url": "https://pypi.org/project/streamlit/", "source_type": "package", "t... | Include navigation, KPIs, tables/charts, filters, loading states, empty states, errors, and responsive behavior. | web-research-coding-5m-1.1.0 | |
0439af063c7eb17626d1c645 | test | refactoring_modularization | stackexchange | https://stackoverflow.com/questions/2595176/which-machine-learning-classifier-to-choose-in-general | Which machine learning classifier to choose, in general? | productivity | shell | developer_experience | Refactor a shell system related to developer_experience. Focus on refactoring modularization. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Which machine learning classifier to choose, in general?", "source_url": "https://stackoverfl... | === 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 | |
f38870815355abaf75a02db7 | test | risk_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/Accessibility | Accessibility | analytics | html | fullstack | Perform a deep multi-layer analysis of fullstack for a analytics using html. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Accessibility", "source_url": "https://developer.mozilla.org/en-US/docs/Web/Accessibility", "... | === 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 'Accessibility' as a source anchor and identify relevant APIs, dependencies, versions, stand... | web-research-coding-5m-1.1.0 | |
71a715688bbf4dabb7adad65 | test | integration_testing | codeberg | https://codeberg.org/Higssgin/1234567890000 | Higssgin/1234567890000 | marketplace | php | graphql | Design integration tests for a php system involving graphql. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Higssgin/1234567890000", "source_url": "https://codeberg.org/Higssgin/1234567890000", "source... | Test real component boundaries, persistence, configuration, external interfaces, errors, cleanup, and realistic workflows. | web-research-coding-5m-1.1.0 | |
b26dcbf309a87d135358be15 | test | error_message_design | mdn | https://developer.mozilla.org/en-US/docs/Web/JavaScript | JavaScript | dashboard | scala | testing | Perform a deep developer-experience analysis for a scala project involving testing. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "JavaScript", "source_url": "https://developer.mozilla.org/en-US/docs/Web/JavaScript", "source... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
2a6fd7037402f689cd259d20 | test | tradeoff_analysis | huggingface | https://huggingface.co/datasets/averoo/sc_JavaScript | averoo/sc_JavaScript | portfolio | kotlin | frontend | Perform a deep multi-layer analysis of frontend for a portfolio 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": "averoo/sc_JavaScript", "source_url": "https://huggingface.co/datasets/averoo/sc_JavaScript", ... | === 1. PROBLEM ===
Define the exact problem involving frontend. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around frontend. Use 'averoo/sc_JavaScript' as a source anchor and identify relevant APIs, dependencies, versions, ... | web-research-coding-5m-1.1.0 | |
10185cfa3e9b17451b0b5109 | test | design_review | huggingface | https://huggingface.co/datasets/jamesdborin/Nemotron-SFT-Competitive-Programming-v2-prompt-only | jamesdborin/Nemotron-SFT-Competitive-Programming-v2-prompt-only | documentation | css | microservices | Perform a professional design review of a documentation. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "jamesdborin/Nemotron-SFT-Competitive-Programming-v2-prompt-only", "source_url": "https://hugg... | Review hierarchy, consistency, responsiveness, accessibility, interaction design, content clarity, and implementation feasibility. | web-research-coding-5m-1.1.0 | |
51e69f4539312a9596faca34 | test | search_query_rewrite | pypi | https://pypi.org/project/beautifulsoup4/ | beautifulsoup4 | ecommerce | swift | database | Rewrite and improve a vague search query about database into a precise, high-signal query. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "beautifulsoup4", "source_url": "https://pypi.org/project/beautifulsoup4/", "source_type": "pa... | === ORIGINAL (VAGUE) ===
how to do database
=== REWRITTEN QUERIES ===
1. database official documentation guide
2. database production best practices 2025
3. database common pitfalls and solutions
4. database architecture patterns with examples
=== RATIONALE ===
Add intent (learn / implement / debug), specificity (ver... | web-research-coding-5m-1.1.0 | |
538b5373deaacdf136e984cf | test | ux_design | web_docs | https://nodejs.org/docs/latest/api/ | Node.js Documentation | admin_panel | cpp | testing | Design the complete UX flow of a admin_panel for testing. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Node.js Documentation", "source_url": "https://nodejs.org/docs/latest/api/", "source_type": "... | Map user goals, entry points, navigation, primary actions, feedback, loading states, empty states, errors, recovery paths, and completion. | web-research-coding-5m-1.1.0 | |
84f979a9c8cfd1ec859b0752 | test | search_intent_classification | web_docs | https://kubernetes.io/docs/ | Kubernetes Documentation | blog | sql | authorization | Classify the search intent for a query about authorization. | {"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... | === POSSIBLE INTENTS ===
- informational (learn a concept)
- navigational (find a specific site/tool)
- transactional (install / download / run)
- troubleshooting (fix an error)
- comparative (choose between options)
=== EXAMPLE QUERY ===
"authorization vs alternatives"
=== CLASSIFICATION ===
Comparative / informatio... | web-research-coding-5m-1.1.0 | |
8e06e41ee559ba25f869d56f | test | integration_testing | stackexchange | https://stackoverflow.com/questions/37937984/git-refusing-to-merge-unrelated-histories-on-rebase | Git refusing to merge unrelated histories on rebase | finance | sql | algorithms | Design integration tests for a sql system involving algorithms. | {"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... | Test real component boundaries, persistence, configuration, external interfaces, errors, cleanup, and realistic workflows. | web-research-coding-5m-1.1.0 | |
a657b8f509c212cbf1e42220 | test | build_experience | huggingface | https://huggingface.co/datasets/livecodebench/code_generation_lite | livecodebench/code_generation_lite | productivity | dart | serverless | Perform a deep developer-experience analysis for a dart project involving serverless. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "livecodebench/code_generation_lite", "source_url": "https://huggingface.co/datasets/livecodeb... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
740c5f7df892341ef96477a8 | test | refactoring_api | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API | Fetch API | developer_tool | cpp | nlp | Refactor a cpp system related to nlp. Focus on refactoring api. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Fetch API", "source_url": "https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API", "sour... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Improve 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 | |
fb6d8931b54102dbedc2284a | test | fact_verification | web_docs | https://fastapi.tiangolo.com/ | FastAPI Documentation | developer_tool | dart | deep_learning | Verify a technical claim about deep_learning. | {"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... | === CLAIM ===
A common claim about deep_learning.
=== 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 | |
711eb0ce5d05b4c696a83ea0 | test | data_structure_design | npm | https://www.npmjs.com/package/prettier | prettier | blog | ruby | observability | Design a data structure in ruby for observability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "prettier", "source_url": "https://www.npmjs.com/package/prettier", "source_type": "package", ... | Explain representation, operations, complexity, memory trade-offs, and workload suitability. | web-research-coding-5m-1.1.0 | |
e298be84c3f4c2a18557b2dd | test | design_to_code | stackexchange | https://stackoverflow.com/questions/60618844/useeffect-is-called-twice-even-if-an-empty-array-is-used-as-an-argument | useEffect() is called twice even if an empty array is used as an argument | social_app | shell | security | Translate a social_app design into maintainable shell code. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "useEffect() is called twice even if an empty array is used as an argument", "source_url": "ht... | 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 | |
b355f980f33c5312e19be6aa | test | web_search_query | stackexchange | https://stackoverflow.com/questions/33091376/what-is-exactly-sklearn-pipeline-pipeline | What is exactly sklearn.pipeline.Pipeline? | marketplace | shell | computer_vision | Write an effective web search query to research the topic: computer_vision. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "What is exactly sklearn.pipeline.Pipeline?", "source_url": "https://stackoverflow.com/questio... | === QUERY ===
computer_vision best practices documentation tutorial
=== INTENT ===
Find authoritative documentation, tutorials, and real-world examples related to the topic.
=== KEYWORDS ===
- computer_vision
- documentation
- best practices
- examples
- reference
=== SOURCE PREFERENCE ===
Prefer official documentat... | web-research-coding-5m-1.1.0 | |
1769ca76b2aaa13621c32ce8 | test | testing_experience | huggingface | https://huggingface.co/datasets/puttatidam/software-documentation-vie-bitextmining | puttatidam/software-documentation-vie-bitextmining | ecommerce | dart | design_system | Perform a deep developer-experience analysis for a dart project involving design_system. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "puttatidam/software-documentation-vie-bitextmining", "source_url": "https://huggingface.co/da... | === 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 | |
97138eea43b478afd29201a7 | test | evidence_extraction | pypi | https://pypi.org/project/torch/ | torch | portfolio | php | developer_experience | Extract verifiable evidence about developer_experience from the given source. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "torch", "source_url": "https://pypi.org/project/torch/", "source_type": "package", "topic": "... | === SOURCE ===
torch
https://pypi.org/project/torch/
=== EVIDENCE ITEMS ===
1. Explicit claims made by the source
2. Code examples or API signatures
3. Version / compatibility statements
4. Performance or security notes
=== QUALITY CHECK ===
- Is the claim specific and testable?
- Is the version and environment state... | web-research-coding-5m-1.1.0 | |
07ecea742c7ba0985801da76 | test | multi_layer_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/Performance | Performance | developer_tool | kotlin | serverless | Perform a deep multi-layer analysis of serverless for a developer_tool 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": "Performance", "source_url": "https://developer.mozilla.org/en-US/docs/Web/Performance", "sour... | === 1. PROBLEM ===
Define the exact problem involving serverless. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around serverless. Use 'Performance' as a source anchor and identify relevant APIs, dependencies, versions, stand... | web-research-coding-5m-1.1.0 | |
7e6c1cd607081dd8e240064e | test | debugging_experience | pypi | https://pypi.org/project/typer/ | typer | documentation | java | machine_learning | Perform a deep developer-experience analysis for a java project involving machine_learning. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "typer", "source_url": "https://pypi.org/project/typer/", "source_type": "package", "topic": "... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
e2aa21f2dd9f0ce14ce4c631 | test | maintainability_analysis | pypi | https://pypi.org/project/django/ | django | social_app | sql | observability | Perform a deep multi-layer analysis of observability for a social_app using sql. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "django", "source_url": "https://pypi.org/project/django/", "source_type": "package", "topic":... | === 1. PROBLEM ===
Define the exact problem involving observability. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around observability. Use 'django' as a source anchor and identify relevant APIs, dependencies, versions, stan... | web-research-coding-5m-1.1.0 | |
e564cfed80346f20b358bda3 | test | build_experience | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API | Fetch API | developer_tool | java | typescript | Perform a deep developer-experience analysis for a java project involving typescript. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Fetch API", "source_url": "https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API", "sour... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
e9dc2481a721495ce3ed012e | test | evidence_chain_analysis | pypi | https://pypi.org/project/flask/ | flask | marketplace | java | web_performance | Perform a deep multi-layer analysis of web_performance for a marketplace using java. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "flask", "source_url": "https://pypi.org/project/flask/", "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 'flask' as a source anchor and identify relevant APIs, dependencies, versions, s... | web-research-coding-5m-1.1.0 | |
44ac1a2518a18dd5727562dc | test | design_to_code | npm | https://www.npmjs.com/package/typescript | typescript | developer_tool | scala | serverless | Translate a developer_tool design into maintainable scala code. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "typescript", "source_url": "https://www.npmjs.com/package/typescript", "source_type": "packag... | Map design tokens to code, identify reusable components, preserve responsive behavior, implement accessible states, and avoid unnecessary one-off styling. | web-research-coding-5m-1.1.0 | |
9ef23af8dead9972f76e843d | test | html_generation | gitlab | https://gitlab.com/to-be-continuous/python | to-be-continuous/python | social_app | shell | design_system | Create semantic HTML for a social_app about design_system. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "to-be-continuous/python", "source_url": "https://gitlab.com/to-be-continuous/python", "source... | 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 |
8443cbf795381dd9c1fe6e84 | test | code_explanation | pypi | https://pypi.org/project/pydantic/ | pydantic | documentation | php | authentication | Explain a php implementation related to authentication. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "pydantic", "source_url": "https://pypi.org/project/pydantic/", "source_type": "package", "top... | Explain inputs, outputs, control flow, algorithms, complexity, edge cases, errors, and maintainability. | web-research-coding-5m-1.1.0 | |
62b9aa9d1f52aa1f01476f6c | test | design_consistency | pypi | https://pypi.org/project/flask/ | flask | community | javascript | postgresql | Audit design consistency across a community. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "flask", "source_url": "https://pypi.org/project/flask/", "source_type": "package", "topic": "... | Check repeated patterns, component variants, spacing, typography, interaction states, terminology, and responsiveness. | web-research-coding-5m-1.1.0 | |
d51082969d8d365418eab358 | test | risk_analysis | stackexchange | https://stackoverflow.com/questions/34968722/how-to-implement-the-softmax-function-in-python | How to implement the Softmax function in Python? | dashboard | typescript | machine_learning | Perform a deep multi-layer analysis of machine_learning for a dashboard 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": "How to implement the Softmax function in Python?", "source_url": "https://stackoverflow.com/q... | === 1. PROBLEM ===
Define the exact problem involving machine_learning. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around machine_learning. Use 'How to implement the Softmax function in Python?' as a source anchor and iden... | web-research-coding-5m-1.1.0 | |
fdd9411f95ad35024255d10b | test | refactoring_readability | stackexchange | https://stackoverflow.com/questions/3552461/how-do-i-format-a-date-in-javascript | How do I format a date in JavaScript? | portfolio | rust | react | Refactor a rust system related to react. Focus on refactoring readability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How do I format a date in JavaScript?", "source_url": "https://stackoverflow.com/questions/35... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Improve naming, control flow, function boundaries, and local reasoning.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify d... | web-research-coding-5m-1.1.0 | |
0475a91bf675f44a72f88daf | test | accessibility_fix | codeberg | https://codeberg.org/smb374/_cargo-index | smb374/_cargo-index | documentation | rust | fullstack | Create an accessibility remediation plan for a documentation. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "smb374/_cargo-index", "source_url": "https://codeberg.org/smb374/_cargo-index", "source_type"... | Check semantic HTML, keyboard navigation, focus management, accessible names, labels, errors, contrast, and screen-reader behavior. | web-research-coding-5m-1.1.0 | |
979955862cc9142e31709495 | test | css_generation | mdn | https://developer.mozilla.org/en-US/docs/Web/Performance | Performance | landing_page | shell | distributed_systems | Create responsive CSS for a landing_page. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Performance", "source_url": "https://developer.mozilla.org/en-US/docs/Web/Performance", "sour... | Use 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 |
c9e337c6f1b712ee2bbda918 | test | root_cause_analysis | gitlab | https://gitlab.com/verbose-equals-true/django-postgres-vue-gitlab-ecs | verbose-equals-true/django-postgres-vue-gitlab-ecs | saas | css | html | Perform a deep multi-layer analysis of html for a saas 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": "verbose-equals-true/django-postgres-vue-gitlab-ecs", "source_url": "https://gitlab.com/verbos... | === 1. PROBLEM ===
Define the exact problem involving html. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around html. Use 'verbose-equals-true/django-postgres-vue-gitlab-ecs' as a source anchor and identify relevant APIs, de... | web-research-coding-5m-1.1.0 | |
a74c87ae70cc8ec7e6bf2d04 | test | refactoring_api | mdn | https://developer.mozilla.org/en-US/docs/Web/JavaScript | JavaScript | documentation | html | nextjs | Refactor a html system related to nextjs. Focus on refactoring api. | {"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 ===
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 | |
4cb25f5785091b023114d8f7 | test | web_search_query | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API | Fetch API | community | c | web_performance | Write an effective web search query to research the topic: web_performance. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Fetch API", "source_url": "https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API", "sour... | === QUERY ===
web_performance best practices documentation tutorial
=== INTENT ===
Find authoritative documentation, tutorials, and real-world examples related to the topic.
=== KEYWORDS ===
- web_performance
- documentation
- best practices
- examples
- reference
=== SOURCE PREFERENCE ===
Prefer official documentat... | web-research-coding-5m-1.1.0 | |
a8489fa828e5a7c7ff284be0 | test | refactoring_scalability | pypi | https://pypi.org/project/django/ | django | blog | kotlin | computer_vision | Refactor a kotlin system related to computer_vision. Focus on refactoring scalability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "django", "source_url": "https://pypi.org/project/django/", "source_type": "package", "topic":... | === 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 | |
ef2e27ba6f70bda64826111e | test | repository_architecture | stackexchange | https://stackoverflow.com/questions/4674623/why-do-we-have-to-normalize-the-input-for-an-artificial-neural-network | Why do we have to normalize the input for an artificial neural network? | finance | sql | css | Perform a deep multi-layer analysis of css for a finance using sql. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Why do we have to normalize the input for an artificial neural network?", "source_url": "http... | === 1. PROBLEM ===
Define the exact problem involving css. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around css. Use 'Why do we have to normalize the input for an artificial neural network?' as a source anchor and identif... | web-research-coding-5m-1.1.0 | |
fd28821fb67c01a9fe7ed3fb | test | design_components | pypi | https://pypi.org/project/numpy/ | numpy | community | python | api_design | Create a component architecture for a community. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "numpy", "source_url": "https://pypi.org/project/numpy/", "source_type": "package", "topic": "... | Define primitive components, composite components, variants, states, composition rules, and accessibility contracts. | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
303261ee22954ffdbc6a0a2f | test | refactoring_scalability | mdn | https://developer.mozilla.org/en-US/docs/Web/HTML | HTML | finance | go | frontend | Refactor a go system related to frontend. Focus on refactoring scalability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "HTML", "source_url": "https://developer.mozilla.org/en-US/docs/Web/HTML", "source_type": "doc... | === 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 | |
eb04a02a9b728a83c1b7ceb6 | test | developer_onboarding | huggingface | https://huggingface.co/datasets/jtatman/python-code-dataset-500k | jtatman/python-code-dataset-500k | education | css | api_design | Perform a deep developer-experience analysis for a css project involving api_design. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "jtatman/python-code-dataset-500k", "source_url": "https://huggingface.co/datasets/jtatman/pyt... | === 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 | |
dba5d3a27f575615cf5e7993 | test | repository_architecture | huggingface | https://huggingface.co/datasets/nomic-ai/cornstack-python-v1 | nomic-ai/cornstack-python-v1 | social_app | php | observability | Perform a deep multi-layer analysis of observability for a social_app using php. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "nomic-ai/cornstack-python-v1", "source_url": "https://huggingface.co/datasets/nomic-ai/cornst... | === 1. PROBLEM ===
Define the exact problem involving observability. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around observability. Use 'nomic-ai/cornstack-python-v1' as a source anchor and identify relevant APIs, depend... | web-research-coding-5m-1.1.0 | |
0d6cf2169d8f9cf156f99c48 | test | form_ui | codeberg | https://codeberg.org/argrento/100-exercises-to-learn-rust | argrento/100-exercises-to-learn-rust | portfolio | java | data_engineering | Design an accessible form for data_engineering. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "argrento/100-exercises-to-learn-rust", "source_url": "https://codeberg.org/argrento/100-exerc... | Use labels, validation, clear errors, keyboard navigation, appropriate autocomplete, and accessible status messaging. | web-research-coding-5m-1.1.0 | |
848bb6ab53ec341015206acb | test | refactoring_observability | gitlab | https://gitlab.com/pixinsight/PJSR | pixinsight/PJSR | developer_tool | php | algorithms | Refactor a php system related to algorithms. Focus on refactoring observability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "pixinsight/PJSR", "source_url": "https://gitlab.com/pixinsight/PJSR", "source_type": "reposit... | === 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 | |
3c1aa41b2ade74881f1abcde | test | accessibility_analysis | web_docs | https://docs.djangoproject.com/ | Django Documentation | community | swift | react | Perform a deep multi-layer analysis of react for a community 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": "Django Documentation", "source_url": "https://docs.djangoproject.com/", "source_type": "docum... | === 1. PROBLEM ===
Define the exact problem involving react. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around react. Use 'Django Documentation' as a source anchor and identify relevant APIs, dependencies, versions, standa... | web-research-coding-5m-1.1.0 | |
f564ac8d9ef4cdf389a023c9 | test | design_components | huggingface | https://huggingface.co/datasets/prhbrt/machine_learning_courses | prhbrt/machine_learning_courses | finance | php | sql | Create a component architecture for a finance. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "prhbrt/machine_learning_courses", "source_url": "https://huggingface.co/datasets/prhbrt/machi... | Define primitive components, composite components, variants, states, composition rules, and accessibility contracts. | web-research-coding-5m-1.1.0 | |
1cd8aa1d8ff66f607b8fed0d | test | architecture_analysis | npm | https://www.npmjs.com/package/hono | hono | analytics | swift | user_experience | Perform a deep multi-layer analysis of user_experience for a analytics using swift. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "hono", "source_url": "https://www.npmjs.com/package/hono", "source_type": "package", "topic":... | === 1. PROBLEM ===
Define the exact problem involving user_experience. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around user_experience. Use 'hono' as a source anchor and identify relevant APIs, dependencies, versions, st... | web-research-coding-5m-1.1.0 | |
8fb73c0305a8b56098e5269b | test | multi_layer_analysis | gitlab | https://gitlab.com/osp-group/flask-nginx-rtmp-manager | osp-group/flask-nginx-rtmp-manager | analytics | ruby | machine_learning | Perform a deep multi-layer analysis of machine_learning for a analytics using ruby. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "osp-group/flask-nginx-rtmp-manager", "source_url": "https://gitlab.com/osp-group/flask-nginx-... | === 1. PROBLEM ===
Define the exact problem involving machine_learning. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around machine_learning. Use 'osp-group/flask-nginx-rtmp-manager' as a source anchor and identify relevant ... | web-research-coding-5m-1.1.0 | |
c46b05b66808ffdd8fac90b0 | test | refactoring_performance | pypi | https://pypi.org/project/numpy/ | numpy | education | scala | docker | Refactor a scala system related to docker. Focus on refactoring performance. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "numpy", "source_url": "https://pypi.org/project/numpy/", "source_type": "package", "topic": "... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Reduce unnecessary computation, allocations, I/O, and network requests.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify d... | web-research-coding-5m-1.1.0 | |
a4248eef5656daa349a32d04 | test | information_architecture | mdn | https://developer.mozilla.org/en-US/docs/Web/API | Web APIs | blog | c | typescript | Design the information architecture for typescript. | {"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": "... | Organize content into logical categories, navigation levels, search, filtering, and discoverable paths. | web-research-coding-5m-1.1.0 | |
dc7d216253c12264c09eabd6 | test | responsive_design | npm | https://www.npmjs.com/package/next | next | social_app | go | kubernetes | Create a responsive design strategy for a social_app. | {"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":... | Define mobile, tablet, and desktop behavior, layout transitions, navigation, content priority, typography, and interaction targets. | web-research-coding-5m-1.1.0 | |
31fa63a7ca1dd53e94dab303 | test | code_explanation | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model | DOM | finance | dart | cloud | Explain a dart implementation related to cloud. | {"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",... | Explain inputs, outputs, control flow, algorithms, complexity, edge cases, errors, and maintainability. | web-research-coding-5m-1.1.0 | |
c482ff84c7fa7887be9f7df3 | test | accessibility_analysis | stackexchange | https://stackoverflow.com/questions/34521797/how-to-add-multiple-classes-to-a-reactjs-component | How to add multiple classes to a ReactJS Component? | portfolio | rust | serverless | Perform a deep multi-layer analysis of serverless 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": "How to add multiple classes to a ReactJS Component?", "source_url": "https://stackoverflow.co... | === 1. PROBLEM ===
Define the exact problem involving serverless. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around serverless. Use 'How to add multiple classes to a ReactJS Component?' as a source anchor and identify rele... | web-research-coding-5m-1.1.0 | |
bbedb848ff988b2c02eece91 | test | multi_hop_research | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API | Fetch API | education | python | documentation | Perform multi-hop research about documentation: 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": "Fetch API", "source_url": "https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API", "sour... | === HOP 1 ===
Start at: Fetch API
https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API
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... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
c8745334b6e0f9e414ad54f3 | test | architecture_analysis | huggingface | https://huggingface.co/datasets/AtharvImmverse/NemoTron-OCR-Synthetic-Multilingual-v1 | AtharvImmverse/NemoTron-OCR-Synthetic-Multilingual-v1 | education | go | nodejs | Perform a deep multi-layer analysis of nodejs for a education 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": "AtharvImmverse/NemoTron-OCR-Synthetic-Multilingual-v1", "source_url": "https://huggingface.co... | === 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 'AtharvImmverse/NemoTron-OCR-Synthetic-Multilingual-v1' as a source anchor and identify relevant A... | web-research-coding-5m-1.1.0 | |
99740dbf88e721d2e4bf65a3 | test | visual_hierarchy | pypi | https://pypi.org/project/requests/ | requests | finance | css | postgresql | Improve visual hierarchy in a finance. | {"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... | Use heading structure, typography, spacing, grouping, alignment, contrast, and consistent affordances. | web-research-coding-5m-1.1.0 | |
034769fc857a1afd483933b2 | test | refactoring_modularization | npm | https://www.npmjs.com/package/vitest | vitest | ecommerce | typescript | fullstack | Refactor a typescript system related to fullstack. Focus on refactoring modularization. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "vitest", "source_url": "https://www.npmjs.com/package/vitest", "source_type": "package", "top... | === 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 | |
40c2e293682cb907a4cf7263 | test | error_message_design | web_docs | https://docs.djangoproject.com/ | Django Documentation | community | sql | linux | Perform a deep developer-experience analysis for a sql project involving linux. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Django Documentation", "source_url": "https://docs.djangoproject.com/", "source_type": "docum... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
e94dc05afff7d4ccea56a26a | test | dependency_impact_analysis | npm | https://www.npmjs.com/package/hono | hono | community | shell | web_performance | Perform a deep multi-layer analysis of web_performance for a community 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": "hono", "source_url": "https://www.npmjs.com/package/hono", "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 'hono' as a source anchor and identify relevant APIs, dependencies, versions, st... | web-research-coding-5m-1.1.0 | |
c762e9d7305b32e76d086127 | test | unit_testing | web_docs | https://www.postgresql.org/docs/ | PostgreSQL Documentation | education | python | testing | Create a unit-testing strategy for python code involving testing. | {"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": "... | Cover normal cases, edge cases, invalid inputs, failure modes, mocks, and regression tests. | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
16fe53c337b417095c91a70a | test | research_plan | npm | https://www.npmjs.com/package/eslint | eslint | social_app | typescript | documentation | Build a structured research plan to deeply understand documentation. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "eslint", "source_url": "https://www.npmjs.com/package/eslint", "source_type": "package", "top... | === GOAL ===
Produce a reliable, current, and actionable understanding of documentation.
=== PHASES ===
1. Orientation — skim official docs and README.
2. Deep read — study specs, RFCs, changelogs.
3. Hands-on — reproduce examples locally.
4. Comparison — compare alternatives and trade-offs.
5. Synthesis — write findi... | web-research-coding-5m-1.1.0 | |
82c235d2c4c174a77b58266e | test | scalability_analysis | huggingface | https://huggingface.co/datasets/HuggingFaceTB/python-edu-annotations | HuggingFaceTB/python-edu-annotations | admin_panel | sql | documentation | Perform a deep multi-layer analysis of documentation for a admin_panel using sql. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "HuggingFaceTB/python-edu-annotations", "source_url": "https://huggingface.co/datasets/Hugging... | === 1. PROBLEM ===
Define the exact problem involving documentation. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around documentation. Use 'HuggingFaceTB/python-edu-annotations' as a source anchor and identify relevant APIs... | web-research-coding-5m-1.1.0 | |
2caddbfbd58e3052282543c3 | test | design_components | npm | https://www.npmjs.com/package/rollup | rollup | search_interface | dart | data_engineering | Create a component architecture for a search_interface. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "rollup", "source_url": "https://www.npmjs.com/package/rollup", "source_type": "package", "top... | Define primitive components, composite components, variants, states, composition rules, and accessibility contracts. | web-research-coding-5m-1.1.0 | |
4ce92196b2d61e88e821a463 | test | build_experience | npm | https://www.npmjs.com/package/axios | axios | portfolio | javascript | web_performance | Perform a deep developer-experience analysis for a javascript project involving web_performance. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "axios", "source_url": "https://www.npmjs.com/package/axios", "source_type": "package", "topic... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
f7958461adca9c40004e3db2 | test | developer_onboarding | huggingface | https://huggingface.co/datasets/ratanon/claude-code | ratanon/claude-code | education | scala | backend | Perform a deep developer-experience analysis for a scala project involving backend. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "ratanon/claude-code", "source_url": "https://huggingface.co/datasets/ratanon/claude-code", "s... | === 1. 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 | |
7712969f067cd523b6f7e0bc | test | developer_onboarding | github | https://github.com/vuejs/core | vuejs/core | documentation | kotlin | graphql | Perform a deep developer-experience analysis for a kotlin project involving graphql. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "vuejs/core", "source_url": "https://github.com/vuejs/core", "source_type": "repository", "top... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
8077a38c6450c8c5bf725e8a | test | component_design | mdn | https://developer.mozilla.org/en-US/docs/Web/CSS | CSS | dashboard | dart | machine_learning | Design reusable UI components for a dashboard. | {"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... | Define component responsibilities, props/data contracts, variants, states, composition rules, accessibility, testing, and documentation. | web-research-coding-5m-1.1.0 | |
71323b3d4af2bfea67d3f039 | test | refactoring_security | npm | https://www.npmjs.com/package/fastify | fastify | social_app | javascript | caching | Refactor a javascript system related to caching. Focus on refactoring security. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "fastify", "source_url": "https://www.npmjs.com/package/fastify", "source_type": "package", "t... | === 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 | |
e41e43edf8c500af8a2ec826 | test | refactoring_maintainability | web_docs | https://go.dev/doc/ | Go Documentation | dashboard | java | sql | Refactor a java system related to sql. Focus on refactoring maintainability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Go Documentation", "source_url": "https://go.dev/doc/", "source_type": "documentation", "topi... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Improve cohesion, reduce coupling, isolate volatile behavior, and remove duplication.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.... | web-research-coding-5m-1.1.0 | |
850adb2fdef7de211c70361b | test | research_summary | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model | DOM | documentation | php | machine_learning | Summarize the current state of knowledge about machine_learning. | {"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",... | === OVERVIEW ===
machine_learning in one paragraph.
=== KEY CONCEPTS ===
- Core definitions
- Main use cases
- Common patterns
=== CURRENT BEST PRACTICES ===
- Recommended approaches
- Known anti-patterns
=== OPEN QUESTIONS ===
- Areas with active development
- Known limitations
=== PRIMARY SOURCE ===
DOM (https://... | web-research-coding-5m-1.1.0 | |
b13a0ea39ce68989566d3172 | test | refactoring_testability | huggingface | https://huggingface.co/datasets/livecodebench/code_generation_lite | livecodebench/code_generation_lite | blog | c | algorithms | Refactor a c system related to algorithms. Focus on refactoring testability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "livecodebench/code_generation_lite", "source_url": "https://huggingface.co/datasets/livecodeb... | === 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 | |
6c2ea534092b98c0a6589f63 | test | repository_documentation | codeberg | https://codeberg.org/0x0079/4ring | 0x0079/4ring | admin_panel | rust | graphql | Perform a deep multi-layer analysis of graphql for a admin_panel using rust. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "0x0079/4ring", "source_url": "https://codeberg.org/0x0079/4ring", "source_type": "repository"... | === 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 '0x0079/4ring' as a source anchor and identify relevant APIs, dependencies, versions, standards,... | web-research-coding-5m-1.1.0 | |
c6e6040e10e2ac3e28b13710 | test | repository_architecture | gitlab | https://gitlab.com/panoramax/clients/web-viewer | panoramax/clients/web-viewer | community | html | web_performance | Perform a deep multi-layer analysis of web_performance for a community using html. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "panoramax/clients/web-viewer", "source_url": "https://gitlab.com/panoramax/clients/web-viewer... | === 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 'panoramax/clients/web-viewer' as a source anchor and identify relevant APIs, de... | web-research-coding-5m-1.1.0 | |
58a620552e5956911067411e | test | refactoring_performance | npm | https://www.npmjs.com/package/three | three | education | rust | css | Refactor a rust system related to css. Focus on refactoring performance. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "three", "source_url": "https://www.npmjs.com/package/three", "source_type": "package", "topic... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Reduce unnecessary computation, allocations, I/O, and network requests.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify d... | web-research-coding-5m-1.1.0 | |
0b377b8feec02e155fd784cf | test | performance_analysis | codeberg | https://codeberg.org/dyke/2048-py | dyke/2048-py | finance | cpp | api_design | Perform a deep multi-layer analysis of api_design for a finance 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": "dyke/2048-py", "source_url": "https://codeberg.org/dyke/2048-py", "source_type": "repository"... | === 1. PROBLEM ===
Define the exact problem involving api_design. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around api_design. Use 'dyke/2048-py' as a source anchor and identify relevant APIs, dependencies, versions, stan... | 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.