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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
668c195f69337aac67ffe139 | test | design_to_code | gitlab | https://gitlab.com/py3dtiles/py3dtiles | py3dtiles/py3dtiles | community | java | developer_experience | Translate a community design into maintainable java code. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "py3dtiles/py3dtiles", "source_url": "https://gitlab.com/py3dtiles/py3dtiles", "source_type": ... | 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 | |
b947be846e3a2f47ca553043 | test | refactoring_maintainability | pypi | https://pypi.org/project/scrapy/ | scrapy | dashboard | python | sql | Refactor a python 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": "scrapy", "source_url": "https://pypi.org/project/scrapy/", "source_type": "package", "topic":... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Improve cohesion, reduce coupling, isolate volatile behavior, and remove duplication.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
4e4f17c4b72490a9626a1bbf | test | refactoring_architecture | npm | https://www.npmjs.com/package/prettier | prettier | landing_page | go | web_performance | Refactor a go system related to web_performance. Focus on refactoring architecture. | {"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", ... | === 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 | |
dfc1193c66868d5f1d1f3490 | test | error_message_design | gitlab | https://gitlab.com/konstellation/kre-old | konstellation/kre-old | marketplace | php | user_experience | Perform a deep developer-experience analysis for a php project involving user_experience. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "konstellation/kre-old", "source_url": "https://gitlab.com/konstellation/kre-old", "source_typ... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
69baa9cd7b8591a46599afb1 | test | deployment_experience | web_docs | https://go.dev/doc/ | Go Documentation | dashboard | html | kubernetes | Perform a deep developer-experience analysis for a html project involving kubernetes. | {"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... | === 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 | |
946cef7186d2e7583afd629a | test | refactoring_modularization | pypi | https://pypi.org/project/fastapi/ | fastapi | admin_panel | java | data_structures | Refactor a java system related to data_structures. Focus on refactoring modularization. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "fastapi", "source_url": "https://pypi.org/project/fastapi/", "source_type": "package", "topic... | === 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 | |
435ee51b025aa563a1e542ff | test | refactoring_dependency | gitlab | https://gitlab.com/py3dtiles/py3dtiles | py3dtiles/py3dtiles | blog | java | fullstack | Refactor a java system related to fullstack. Focus on refactoring dependency. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "py3dtiles/py3dtiles", "source_url": "https://gitlab.com/py3dtiles/py3dtiles", "source_type": ... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Audit dependencies and isolate external integrations.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify developer-experienc... | web-research-coding-5m-1.1.0 | |
ff9229b899ce8f8e84867399 | test | refactoring_testability | huggingface | https://huggingface.co/datasets/MachineLearningVisionRG/CattleSSFR | MachineLearningVisionRG/CattleSSFR | saas | java | web_accessibility | Refactor a java system related to web_accessibility. Focus on refactoring testability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "MachineLearningVisionRG/CattleSSFR", "source_url": "https://huggingface.co/datasets/MachineLe... | === 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 | |
8d90d1a6dae12cd048e102d1 | test | cli_experience | gitlab | https://gitlab.com/reubenlillie/eleventy-dot-js-blog | reubenlillie/eleventy-dot-js-blog | admin_panel | 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": "reubenlillie/eleventy-dot-js-blog", "source_url": "https://gitlab.com/reubenlillie/eleventy-d... | === 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 | |
d76a53db89e9d8d34432d973 | test | repository_understanding | codeberg | https://codeberg.org/UI-Programming-25-26/01-web-basics-and-git-Martin-McCarthy | UI-Programming-25-26/01-web-basics-and-git-Martin-McCarthy | documentation | html | mongodb | Perform a deep multi-layer analysis of mongodb for a documentation 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": "UI-Programming-25-26/01-web-basics-and-git-Martin-McCarthy", "source_url": "https://codeberg.... | === 1. PROBLEM ===
Define the exact problem involving mongodb. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around mongodb. Use 'UI-Programming-25-26/01-web-basics-and-git-Martin-McCarthy' as a source anchor and identify rel... | web-research-coding-5m-1.1.0 | |
41560e6f74036717f1237235 | test | design_review | gitlab | https://gitlab.com/foundry-projects/foundry-pc/foundry-pc-types | foundry-projects/foundry-pc/foundry-pc-types | marketplace | css | web_accessibility | Perform a professional design review of a marketplace. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "foundry-projects/foundry-pc/foundry-pc-types", "source_url": "https://gitlab.com/foundry-proj... | Review hierarchy, consistency, responsiveness, accessibility, interaction design, content clarity, and implementation feasibility. | web-research-coding-5m-1.1.0 | |
16e9ff637718737a48634c7c | test | product_analysis | stackexchange | https://stackoverflow.com/questions/21247278/about-d-ts-in-typescript | About "*.d.ts" in TypeScript | finance | c | nodejs | Perform a deep multi-layer analysis of nodejs for a finance 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": "About "*.d.ts" in TypeScript", "source_url": "https://stackoverflow.com/questions/2... | === 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 'About "*.d.ts" in TypeScript' as a source anchor and identify relevant APIs, dependenci... | web-research-coding-5m-1.1.0 | |
1f4c16416f1141a7f7c8b4bd | test | api_design | stackexchange | https://stackoverflow.com/questions/23123138/how-can-i-perform-a-debounce | How can I perform a debounce? | saas | kotlin | web_accessibility | Design a production API for a web_accessibility application. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How can I perform a debounce?", "source_url": "https://stackoverflow.com/questions/23123138/h... | Specify resources, endpoints, schemas, validation, authentication, authorization, errors, pagination, versioning, idempotency, and tests. | web-research-coding-5m-1.1.0 | |
56c4fe6ad6b74fcb80e450ea | test | source_selection | web_docs | https://git-scm.com/doc | Git Documentation | developer_tool | scala | serverless | Select the most reliable sources to research serverless. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Git Documentation", "source_url": "https://git-scm.com/doc", "source_type": "documentation", ... | === SOURCE TIERS ===
1. Primary: official documentation, specifications, RFCs
2. Secondary: maintained repositories, changelogs, releases
3. Tertiary: tutorials, blog posts, Q&A
=== SELECTION CRITERIA ===
- Authority of the publisher
- Recency and version relevance
- Technical depth
- Reproducibility of examples
=== ... | web-research-coding-5m-1.1.0 | |
ca0faddadee4a33bcd2bef95 | test | react_generation | gitlab | https://gitlab.com/unimatrix/larod | unimatrix/larod | finance | c | testing | Design React components for a finance. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "unimatrix/larod", "source_url": "https://gitlab.com/unimatrix/larod", "source_type": "reposit... | Separate reusable components, state, data fetching, loading/error states, accessibility, and testing. | export function Card({ title, children }) {
return (
<article className="card">
<h2>{title}</h2>
<div>{children}</div>
</article>
);
} | web-research-coding-5m-1.1.0 |
99c94624e3aecc0158787475 | test | security_review | codeberg | https://codeberg.org/Roboe/advent-of-code | Roboe/advent-of-code | blog | html | kubernetes | Perform a security review of a blog application. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Roboe/advent-of-code", "source_url": "https://codeberg.org/Roboe/advent-of-code", "source_typ... | Review authentication, authorization, input validation, XSS, CSRF, injection risks, secrets, dependencies, security headers, and logging. | web-research-coding-5m-1.1.0 | |
1e979e54617a6bb47ca2bf2a | test | multi_layer_analysis | pypi | https://pypi.org/project/beautifulsoup4/ | beautifulsoup4 | marketplace | sql | nodejs | Perform a deep multi-layer analysis of nodejs for a marketplace 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": "beautifulsoup4", "source_url": "https://pypi.org/project/beautifulsoup4/", "source_type": "pa... | === 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 'beautifulsoup4' as a source anchor and identify relevant APIs, dependencies, versions, standards,... | web-research-coding-5m-1.1.0 | |
469e03124fe305c4d47da1d4 | test | dependency_impact_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/CSS | CSS | community | ruby | redis | Perform a deep multi-layer analysis of redis for a community using ruby. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "CSS", "source_url": "https://developer.mozilla.org/en-US/docs/Web/CSS", "source_type": "docum... | === 1. PROBLEM ===
Define the exact problem involving redis. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around redis. Use 'CSS' as a source anchor and identify relevant APIs, dependencies, versions, standards, and technica... | web-research-coding-5m-1.1.0 | |
ef96697660fc910bc4187984 | test | code_explanation | gitlab | https://gitlab.com/pyspread/pyspread | pyspread/pyspread | ecommerce | typescript | docker | Explain a typescript implementation related to docker. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "pyspread/pyspread", "source_url": "https://gitlab.com/pyspread/pyspread", "source_type": "rep... | Explain inputs, outputs, control flow, algorithms, complexity, edge cases, errors, and maintainability. | web-research-coding-5m-1.1.0 | |
2305266c465a1a80fd7a9fc5 | test | dependency_management_experience | mdn | https://developer.mozilla.org/en-US/docs/Web/JavaScript | JavaScript | marketplace | 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": "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 | |
330a77337d80a8cf72691bc0 | test | unit_testing | pypi | https://pypi.org/project/pandas/ | pandas | marketplace | rust | serverless | Create a unit-testing strategy for rust code involving serverless. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "pandas", "source_url": "https://pypi.org/project/pandas/", "source_type": "package", "topic":... | Cover normal cases, edge cases, invalid inputs, failure modes, mocks, and regression tests. | web-research-coding-5m-1.1.0 | |
73ee226105b2452d0ee8568d | test | risk_analysis | codeberg | https://codeberg.org/ivaninkv/100-exercises-to-learn-rust | ivaninkv/100-exercises-to-learn-rust | saas | swift | algorithms | Perform a deep multi-layer analysis of algorithms for a saas 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": "ivaninkv/100-exercises-to-learn-rust", "source_url": "https://codeberg.org/ivaninkv/100-exerc... | === 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 'ivaninkv/100-exercises-to-learn-rust' as a source anchor and identify relevant APIs, depe... | web-research-coding-5m-1.1.0 | |
323b34a1f1efcc37094b3c30 | test | documentation_experience | stackexchange | https://stackoverflow.com/questions/2720014/how-to-upgrade-all-python-packages-with-pip | How to upgrade all Python packages with pip | education | scala | serverless | Perform a deep developer-experience analysis for a scala project involving serverless. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How to upgrade all Python packages with pip", "source_url": "https://stackoverflow.com/questi... | === 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 | |
77d924e3b9a6058771657561 | test | interaction_design | mdn | https://developer.mozilla.org/en-US/docs/Web/HTTP | HTTP | search_interface | java | data_structures | Design interaction states for a search_interface. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "HTTP", "source_url": "https://developer.mozilla.org/en-US/docs/Web/HTTP", "source_type": "doc... | Specify default, hover, focus, active, disabled, loading, success, error, and empty states. | web-research-coding-5m-1.1.0 | |
f5616e23d94011b5260cb940 | test | local_development_experience | gitlab | https://gitlab.com/lobaro/iot-dashboard | lobaro/iot-dashboard | social_app | python | nlp | Perform a deep developer-experience analysis for a python project involving nlp. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "lobaro/iot-dashboard", "source_url": "https://gitlab.com/lobaro/iot-dashboard", "source_type"... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
ad2bf41bf3488ffa96d92405 | test | css_generation | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API | Fetch API | blog | c | distributed_systems | Create responsive CSS for a blog. | {"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... | 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 |
e2c86f8c626db134d24b53e5 | test | code_review | web_docs | https://docs.python.org/3/ | Python Documentation | search_interface | css | docker | Perform a production code review of css code related to docker. | {"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... | Review correctness, security, performance, readability, architecture, testing, maintainability, and error handling. | web-research-coding-5m-1.1.0 | |
e7198b8fc0e44db8363a7231 | test | deep_technical_analysis | huggingface | https://huggingface.co/datasets/lijiahao1123/documentation-images | lijiahao1123/documentation-images | documentation | cpp | cloud | Perform a deep multi-layer analysis of cloud for a documentation 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": "lijiahao1123/documentation-images", "source_url": "https://huggingface.co/datasets/lijiahao11... | === 1. PROBLEM ===
Define the exact problem involving cloud. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around cloud. Use 'lijiahao1123/documentation-images' as a source anchor and identify relevant APIs, dependencies, ver... | web-research-coding-5m-1.1.0 | |
e89cde19a634a696c7727ea9 | test | scalability_analysis | gitlab | https://gitlab.com/nqs/ucas_workshop | nqs/ucas_workshop | admin_panel | go | authorization | Perform a deep multi-layer analysis of authorization for a admin_panel 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": "nqs/ucas_workshop", "source_url": "https://gitlab.com/nqs/ucas_workshop", "source_type": "rep... | === 1. PROBLEM ===
Define the exact problem involving authorization. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around authorization. Use 'nqs/ucas_workshop' as a source anchor and identify relevant APIs, dependencies, ver... | web-research-coding-5m-1.1.0 | |
e74e05a9d051d0a3da6fad5a | test | refactoring_maintainability | pypi | https://pypi.org/project/uvicorn/ | uvicorn | saas | php | distributed_systems | Refactor a php system related to distributed_systems. Focus on refactoring maintainability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "uvicorn", "source_url": "https://pypi.org/project/uvicorn/", "source_type": "package", "topic... | === 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 | |
054840b88b1b87625fc07e74 | test | repository_documentation | huggingface | https://huggingface.co/datasets/codefuse-ai/CodeExercise-Python-27k | codefuse-ai/CodeExercise-Python-27k | blog | html | debugging | Perform a deep multi-layer analysis of debugging for a blog 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": "codefuse-ai/CodeExercise-Python-27k", "source_url": "https://huggingface.co/datasets/codefuse... | === 1. PROBLEM ===
Define the exact problem involving debugging. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around debugging. Use 'codefuse-ai/CodeExercise-Python-27k' as a source anchor and identify relevant APIs, depende... | web-research-coding-5m-1.1.0 | |
6af8a2ab7d0b34f37c7ee23f | test | refactoring_readability | npm | https://www.npmjs.com/package/playwright | playwright | social_app | shell | ci_cd | Refactor a shell system related to ci_cd. Focus on refactoring readability. | {"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... | === 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 | |
0ec011402bf6b2204c6b1c57 | test | performance_fix | gitlab | https://gitlab.com/cashscript-py/cashscript-py | cashscript-py/cashscript-py | landing_page | dart | testing | Create a web-performance optimization plan for a landing_page. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "cashscript-py/cashscript-py", "source_url": "https://gitlab.com/cashscript-py/cashscript-py",... | Measure first, then optimize bundle size, images, network requests, rendering, caching, and critical resources. | web-research-coding-5m-1.1.0 | |
24c1a96010e167ed3e5e33b6 | test | debugging | gitlab | https://gitlab.com/FirstTerraner/proclubs-api | FirstTerraner/proclubs-api | dashboard | scala | testing | Create a realistic scala debugging problem involving testing. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "FirstTerraner/proclubs-api", "source_url": "https://gitlab.com/FirstTerraner/proclubs-api", "... | Provide symptoms, reproduction strategy, diagnostic steps, root-cause analysis, minimal fix, and regression coverage. | web-research-coding-5m-1.1.0 | |
af0d41f48efce7cc8c79d846 | test | refactoring_readability | mdn | https://developer.mozilla.org/en-US/docs/Web/API | Web APIs | finance | swift | computer_vision | Refactor a swift system related to computer_vision. Focus on refactoring readability. | {"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": "... | === 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 | |
250ff27a9db48bea4659731b | test | refactoring_dependency | huggingface | https://huggingface.co/datasets/bofenghuang/stt-pseudo-labeled-whisper-large-v3-multilingual | bofenghuang/stt-pseudo-labeled-whisper-large-v3-multilingual | dashboard | scala | observability | Refactor a scala system related to observability. Focus on refactoring dependency. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "bofenghuang/stt-pseudo-labeled-whisper-large-v3-multilingual", "source_url": "https://hugging... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Audit dependencies and isolate external integrations.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify developer-experienc... | web-research-coding-5m-1.1.0 | |
bf307c24eb719f740bbdba9e | test | interaction_design | stackexchange | https://stackoverflow.com/questions/2765421/how-do-i-push-a-new-local-branch-to-a-remote-git-repository-and-track-it-too | How do I push a new local branch to a remote Git repository and track it too? | finance | php | data_engineering | Design interaction states for a finance. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How do I push a new local branch to a remote Git repository and track it too?", "source_url":... | Specify default, hover, focus, active, disabled, loading, success, error, and empty states. | web-research-coding-5m-1.1.0 | |
1d9388536c049f14c9480206 | test | search_intent_classification | stackexchange | https://stackoverflow.com/questions/509211/how-slicing-in-python-works | How slicing in Python works | developer_tool | ruby | data_engineering | Classify the search intent for a query about data_engineering. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How slicing in Python works", "source_url": "https://stackoverflow.com/questions/509211/how-s... | === 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 ===
"data_engineering vs alternatives"
=== CLASSIFICATION ===
Comparative / informa... | web-research-coding-5m-1.1.0 | |
d2121767668f111222d5aece | test | api_design | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model | DOM | social_app | javascript | documentation | Design a production API for a documentation 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",... | Specify resources, endpoints, schemas, validation, authentication, authorization, errors, pagination, versioning, idempotency, and tests. | web-research-coding-5m-1.1.0 | |
1dd5f29b64f49a85cf7ef10c | test | documentation_lookup | gitlab | https://gitlab.com/q-dev/q-js-sdk | q-dev/q-js-sdk | search_interface | css | testing | Find and summarize the relevant documentation for testing. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "q-dev/q-js-sdk", "source_url": "https://gitlab.com/q-dev/q-js-sdk", "source_type": "repositor... | === RELEVANT DOCS ===
- q-dev/q-js-sdk
https://gitlab.com/q-dev/q-js-sdk
- Official project documentation
- API reference
=== KEY SECTIONS ===
- Getting started
- API reference
- Configuration
- Troubleshooting
=== SUMMARY ===
Summarize each section in 1–3 sentences and quote exact signatures where relevant. | web-research-coding-5m-1.1.0 | |
76ae854247f786741101bab3 | test | accessibility_fix | npm | https://www.npmjs.com/package/webpack | webpack | finance | sql | distributed_systems | Create an accessibility remediation plan for a finance. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "webpack", "source_url": "https://www.npmjs.com/package/webpack", "source_type": "package", "t... | Check semantic HTML, keyboard navigation, focus management, accessible names, labels, errors, contrast, and screen-reader behavior. | web-research-coding-5m-1.1.0 | |
022e8550fa7aaec3ddc6edb2 | test | api_design | stackexchange | https://stackoverflow.com/questions/37937984/git-refusing-to-merge-unrelated-histories-on-rebase | Git refusing to merge unrelated histories on rebase | finance | scala | authorization | Design a production API for a authorization application. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Git refusing to merge unrelated histories on rebase", "source_url": "https://stackoverflow.co... | Specify resources, endpoints, schemas, validation, authentication, authorization, errors, pagination, versioning, idempotency, and tests. | web-research-coding-5m-1.1.0 | |
32d97da5acf10366e9c34086 | test | refactoring_testability | pypi | https://pypi.org/project/flask/ | flask | finance | css | kubernetes | Refactor a css system related to kubernetes. Focus on refactoring testability. | {"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": "... | === 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 | |
203a4f240d70167f76d49988 | test | api_developer_experience | github | https://github.com/scikit-learn/scikit-learn | scikit-learn/scikit-learn | finance | javascript | software_architecture | Perform a deep developer-experience analysis for a javascript project involving software_architecture. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "scikit-learn/scikit-learn", "source_url": "https://github.com/scikit-learn/scikit-learn", "so... | === 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 | |
9f50b0b7fe2b0ae9990996ce | test | deep_technical_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/Performance | Performance | dashboard | ruby | redis | Perform a deep multi-layer analysis of redis for a dashboard 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": "Performance", "source_url": "https://developer.mozilla.org/en-US/docs/Web/Performance", "sour... | === 1. PROBLEM ===
Define the exact problem involving redis. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around redis. Use 'Performance' as a source anchor and identify relevant APIs, dependencies, versions, standards, and ... | web-research-coding-5m-1.1.0 | |
345f099d6c146fddca0e3ce4 | test | design_system | npm | https://www.npmjs.com/package/vitest | vitest | developer_tool | kotlin | redis | Create a scalable design system for a developer_tool. | {"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... | Define tokens, typography, spacing, components, variants, states, responsive rules, accessibility, and documentation. | web-research-coding-5m-1.1.0 | |
ace9c377697557ae9fb9092d | test | refactoring_modularization | pypi | https://pypi.org/project/streamlit/ | streamlit | developer_tool | dart | serverless | Refactor a dart system related to serverless. Focus on refactoring modularization. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "streamlit", "source_url": "https://pypi.org/project/streamlit/", "source_type": "package", "t... | === 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 | |
fa8c152ef31dd9ddce8b8212 | test | scalability_analysis | huggingface | https://huggingface.co/datasets/joey234/mmlu-machine_learning-neg-answer | joey234/mmlu-machine_learning-neg-answer | finance | sql | nextjs | Perform a deep multi-layer analysis of nextjs 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": "joey234/mmlu-machine_learning-neg-answer", "source_url": "https://huggingface.co/datasets/joe... | === 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 'joey234/mmlu-machine_learning-neg-answer' as a source anchor and identify relevant APIs, dependen... | web-research-coding-5m-1.1.0 | |
2b5b54ed4edc64def7378685 | test | refactoring_legacy_code | gitlab | https://gitlab.com/stavros/python-yeelight | stavros/python-yeelight | documentation | go | sql | Refactor a go system related to sql. Focus on refactoring legacy code. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "stavros/python-yeelight", "source_url": "https://gitlab.com/stavros/python-yeelight", "source... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Characterize existing behavior first and incrementally replace risky legacy structures.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implication... | web-research-coding-5m-1.1.0 | |
4ff6ae560cf5bfe151b6ab1b | test | evidence_extraction | npm | https://www.npmjs.com/package/svelte | svelte | blog | ruby | devops | Extract verifiable evidence about devops from the given source. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "svelte", "source_url": "https://www.npmjs.com/package/svelte", "source_type": "package", "top... | === SOURCE ===
svelte
https://www.npmjs.com/package/svelte
=== 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... | web-research-coding-5m-1.1.0 | |
20c0f4f8bec18b656b14be7c | test | refactoring_testability | gitlab | https://gitlab.com/panoramax/clients/web-viewer | panoramax/clients/web-viewer | landing_page | javascript | python | Refactor a javascript system related to python. Focus on refactoring testability. | {"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... | === 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 | |
049f9ec1f8d72980280e6466 | test | design_consistency | gitlab | https://gitlab.com/unimatrix/larod | unimatrix/larod | analytics | html | html | Audit design consistency across a analytics. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "unimatrix/larod", "source_url": "https://gitlab.com/unimatrix/larod", "source_type": "reposit... | Check repeated patterns, component variants, spacing, typography, interaction states, terminology, and responsiveness. | web-research-coding-5m-1.1.0 | |
7b4f181d0e4c8e2092e21427 | test | repository_understanding | npm | https://www.npmjs.com/package/typescript | typescript | search_interface | cpp | design_system | Perform a deep multi-layer analysis of design_system for a search_interface 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": "typescript", "source_url": "https://www.npmjs.com/package/typescript", "source_type": "packag... | === 1. PROBLEM ===
Define the exact problem involving design_system. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around design_system. Use 'typescript' as a source anchor and identify relevant APIs, dependencies, versions, ... | web-research-coding-5m-1.1.0 | |
23e0f456b3b75782d18efa96 | test | performance_fix | stackexchange | https://stackoverflow.com/questions/5480258/how-can-i-delete-a-remote-tag | How can I delete a remote tag? | social_app | ruby | mongodb | Create a web-performance optimization plan for a social_app. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How can I delete a remote tag?", "source_url": "https://stackoverflow.com/questions/5480258/h... | Measure first, then optimize bundle size, images, network requests, rendering, caching, and critical resources. | web-research-coding-5m-1.1.0 | |
8e4184252a2b8c88ece11454 | test | design_components | pypi | https://pypi.org/project/pandas/ | pandas | search_interface | javascript | security | 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": "pandas", "source_url": "https://pypi.org/project/pandas/", "source_type": "package", "topic":... | Define primitive components, composite components, variants, states, composition rules, and accessibility contracts. | web-research-coding-5m-1.1.0 | |
52909e6ec9e8fe6383cc690b | test | information_architecture | mdn | https://developer.mozilla.org/en-US/docs/Web/Performance | Performance | productivity | rust | html | Design the information architecture for html. | {"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... | Organize content into logical categories, navigation levels, search, filtering, and discoverable paths. | web-research-coding-5m-1.1.0 | |
f47e47fcdbe9588fea47f817 | test | api_design | huggingface | https://huggingface.co/datasets/Alex-xu/secalign-dbg-haiku-javascript-all | Alex-xu/secalign-dbg-haiku-javascript-all | education | c | security | Design a production API for a security application. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Alex-xu/secalign-dbg-haiku-javascript-all", "source_url": "https://huggingface.co/datasets/Al... | Specify resources, endpoints, schemas, validation, authentication, authorization, errors, pagination, versioning, idempotency, and tests. | web-research-coding-5m-1.1.0 | |
27d5df15b4d4c5c393586e89 | test | developer_experience | mdn | https://developer.mozilla.org/en-US/docs/Web/JavaScript | JavaScript | search_interface | scala | rest_api | Perform a deep developer-experience analysis for a scala project involving rest_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... | === 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 | |
f7b748aa88575e6cf90ec59e | test | responsive_design | stackexchange | https://stackoverflow.com/questions/348170/how-do-i-undo-git-add-before-commit | How do I undo 'git add' before commit? | dashboard | javascript | linux | Create a responsive design strategy for a dashboard. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How do I undo 'git add' before commit?", "source_url": "https://stackoverflow.com/que... | Define mobile, tablet, and desktop behavior, layout transitions, navigation, content priority, typography, and interaction targets. | web-research-coding-5m-1.1.0 | |
998509735a4c074f2507f8c8 | test | nextjs_generation | npm | https://www.npmjs.com/package/express | express | community | python | design_system | Design a Next.js architecture for a community. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "express", "source_url": "https://www.npmjs.com/package/express", "source_type": "package", "t... | Specify routing, server/client boundaries, data fetching, caching, metadata, errors, and deployment. | export default function Page() {
return (
<main>
<h1>Application</h1>
<p>Production-ready page structure.</p>
</main>
);
} | web-research-coding-5m-1.1.0 |
eebddf51715a6eb56c726134 | test | repository_dependency_analysis | gitlab | https://gitlab.com/juliensimon/awsmlmap | juliensimon/awsmlmap | social_app | sql | security | Perform a deep multi-layer analysis of security 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": "juliensimon/awsmlmap", "source_url": "https://gitlab.com/juliensimon/awsmlmap", "source_type"... | === 1. PROBLEM ===
Define the exact problem involving security. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around security. Use 'juliensimon/awsmlmap' as a source anchor and identify relevant APIs, dependencies, versions, ... | web-research-coding-5m-1.1.0 | |
7d231f2af08034aefadb5522 | test | refactoring_modularization | huggingface | https://huggingface.co/datasets/gangiswag/javascript_ablation | gangiswag/javascript_ablation | blog | scala | api_design | Refactor a scala system related to api_design. Focus on refactoring modularization. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "gangiswag/javascript_ablation", "source_url": "https://huggingface.co/datasets/gangiswag/java... | === 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 | |
72831016f7dca813ec7d7002 | test | ux_analysis | stackexchange | https://stackoverflow.com/questions/1041344/how-can-i-select-an-element-with-multiple-classes-in-jquery | How can I select an element with multiple classes in jQuery? | portfolio | cpp | frontend | Perform a deep multi-layer analysis of frontend for a portfolio using cpp. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How can I select an element with multiple classes in jQuery?", "source_url": "https://stackov... | === 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 'How can I select an element with multiple classes in jQuery?' as a source anchor and identify... | web-research-coding-5m-1.1.0 | |
1709f40062ed60a98c9b74c8 | test | developer_onboarding | npm | https://www.npmjs.com/package/svelte | svelte | analytics | ruby | frontend | Perform a deep developer-experience analysis for a ruby project involving frontend. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "svelte", "source_url": "https://www.npmjs.com/package/svelte", "source_type": "package", "top... | === 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 | |
5c856cb7c332740775656115 | test | landing_page | pypi | https://pypi.org/project/uvicorn/ | uvicorn | community | javascript | javascript | Design a landing page for a javascript product. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "uvicorn", "source_url": "https://pypi.org/project/uvicorn/", "source_type": "package", "topic... | Include hero, value proposition, features, CTA, FAQ, responsive behavior, SEO, accessibility, and analytics. | web-research-coding-5m-1.1.0 | |
7266c40192117691467cd087 | test | refactoring_performance | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API | Fetch API | finance | ruby | user_experience | Refactor a ruby system related to user_experience. Focus on refactoring 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... | === 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 | |
97e6c9d8994349992d9bb829 | test | build_experience | codeberg | https://codeberg.org/DarthCloud/100-exercises-to-learn-rust | DarthCloud/100-exercises-to-learn-rust | dashboard | c | ci_cd | Perform a deep developer-experience analysis for a c project involving ci_cd. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "DarthCloud/100-exercises-to-learn-rust", "source_url": "https://codeberg.org/DarthCloud/100-e... | === 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 | |
a76152af3054c33289424e8d | test | design_accessibility | mdn | https://developer.mozilla.org/en-US/docs/Web/CSS | CSS | finance | cpp | ci_cd | Audit accessibility for a finance. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "CSS", "source_url": "https://developer.mozilla.org/en-US/docs/Web/CSS", "source_type": "docum... | Check semantic structure, keyboard navigation, focus visibility, accessible names, labels, errors, contrast, and screen-reader behavior. | web-research-coding-5m-1.1.0 | |
8028af710d9aca12c4e50fc5 | test | error_message_design | pypi | https://pypi.org/project/django/ | django | documentation | go | design_system | Perform a deep developer-experience analysis for a go project involving design_system. | {"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. 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 | |
a85f90b0f4162c5308346022 | test | cli_experience | stackexchange | https://stackoverflow.com/questions/16670931/hide-scroll-bar-but-while-still-being-able-to-scroll | Hide scroll bar, but while still being able to scroll | developer_tool | shell | web_performance | Perform a deep developer-experience analysis for a shell project involving web_performance. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Hide scroll bar, but while still being able to scroll", "source_url": "https://stackoverflow.... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
b631d0e8fb8843a6ebc88225 | test | ux_analysis | pypi | https://pypi.org/project/sqlalchemy/ | sqlalchemy | education | shell | user_experience | Perform a deep multi-layer analysis of user_experience for a education using shell. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "sqlalchemy", "source_url": "https://pypi.org/project/sqlalchemy/", "source_type": "package", ... | === 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 'sqlalchemy' as a source anchor and identify relevant APIs, dependencies, versio... | web-research-coding-5m-1.1.0 | |
8135d99574b37405ab3ec435 | test | algorithm_design | stackexchange | https://stackoverflow.com/questions/237104/how-do-i-check-if-an-array-includes-a-value-in-javascript | How do I check if an array includes a value in JavaScript? | developer_tool | rust | rest_api | Design a rust algorithm for a rest_api problem. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How do I check if an array includes a value in JavaScript?", "source_url": "https://stackover... | State assumptions, algorithm, complexity, edge cases, correctness reasoning, and testing strategy. | web-research-coding-5m-1.1.0 | |
3b2e3d896855948f5757c4e6 | test | scalability_analysis | huggingface | https://huggingface.co/datasets/optimum/documentation-images | optimum/documentation-images | documentation | python | user_experience | Perform a deep multi-layer analysis of user_experience for a documentation 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": "optimum/documentation-images", "source_url": "https://huggingface.co/datasets/optimum/documen... | === 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 'optimum/documentation-images' as a source anchor and identify relevant APIs, de... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
075fb145ddbb09df1a54f043 | test | refactoring_modularization | huggingface | https://huggingface.co/datasets/jan-hq/multiturn_programming_binarized | jan-hq/multiturn_programming_binarized | analytics | dart | ci_cd | Refactor a dart system related to ci_cd. Focus on refactoring modularization. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "jan-hq/multiturn_programming_binarized", "source_url": "https://huggingface.co/datasets/jan-h... | === 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 | |
7aead6d69063c1def32c8c36 | test | upgrade_experience | stackexchange | https://stackoverflow.com/questions/45022048/why-does-npm-install-rewrite-package-lock-json | Why does "npm install" rewrite package-lock.json? | finance | python | ci_cd | Perform a deep developer-experience analysis for a python project involving ci_cd. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Why does "npm install" rewrite package-lock.json?", "source_url": "https://stackove... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
3aa8cb1b1896c591144a3940 | test | multi_layer_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/CSS | CSS | community | css | graphql | Perform a deep multi-layer analysis of graphql for a community 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": "CSS", "source_url": "https://developer.mozilla.org/en-US/docs/Web/CSS", "source_type": "docum... | === 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 'CSS' as a source anchor and identify relevant APIs, dependencies, versions, standards, and tech... | web-research-coding-5m-1.1.0 | |
e12955cd20c84945204cc0ee | test | design_accessibility | mdn | https://developer.mozilla.org/en-US/docs/Web/Accessibility | Accessibility | ecommerce | javascript | database | Audit accessibility for a ecommerce. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Accessibility", "source_url": "https://developer.mozilla.org/en-US/docs/Web/Accessibility", "... | Check semantic structure, keyboard navigation, focus visibility, accessible names, labels, errors, contrast, and screen-reader behavior. | web-research-coding-5m-1.1.0 | |
381cffd9c7b398a2304d09b1 | test | refactoring_legacy_code | pypi | https://pypi.org/project/torch/ | torch | blog | rust | user_experience | Refactor a rust system related to user_experience. Focus on refactoring legacy code. | {"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": "... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Characterize existing behavior first and incrementally replace risky legacy structures.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implication... | web-research-coding-5m-1.1.0 | |
f5f3db8dc705180780f984f9 | test | design_components | codeberg | https://codeberg.org/I-ATE-OREO/2025 | I-ATE-OREO/2025 | education | kotlin | kubernetes | Create a component architecture for a education. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "I-ATE-OREO/2025", "source_url": "https://codeberg.org/I-ATE-OREO/2025", "source_type": "repos... | Define primitive components, composite components, variants, states, composition rules, and accessibility contracts. | web-research-coding-5m-1.1.0 | |
0064eabf8ce4d44cf46a3e73 | test | ux_analysis | huggingface | https://huggingface.co/datasets/MachineLearningVisionRG/CattleSSFR | MachineLearningVisionRG/CattleSSFR | education | shell | software_architecture | Perform a deep multi-layer analysis of software_architecture for a education using shell. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "MachineLearningVisionRG/CattleSSFR", "source_url": "https://huggingface.co/datasets/MachineLe... | === 1. PROBLEM ===
Define the exact problem involving software_architecture. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around software_architecture. Use 'MachineLearningVisionRG/CattleSSFR' as a source anchor and identify... | web-research-coding-5m-1.1.0 | |
c3d35d9e9f34a071633b9d97 | test | web_search_query | mdn | https://developer.mozilla.org/en-US/docs/Web/HTML | HTML | finance | html | nextjs | Write an effective web search query to research the topic: nextjs. | {"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... | === QUERY ===
nextjs best practices documentation tutorial
=== INTENT ===
Find authoritative documentation, tutorials, and real-world examples related to the topic.
=== KEYWORDS ===
- nextjs
- documentation
- best practices
- examples
- reference
=== SOURCE PREFERENCE ===
Prefer official documentation, well-maintain... | web-research-coding-5m-1.1.0 | |
fa4f7d2d543ca2fd37a52b23 | test | accessibility_analysis | huggingface | https://huggingface.co/datasets/kaydenfu/documentation-images | kaydenfu/documentation-images | developer_tool | python | postgresql | Perform a deep multi-layer analysis of postgresql 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": "kaydenfu/documentation-images", "source_url": "https://huggingface.co/datasets/kaydenfu/docum... | === 1. PROBLEM ===
Define the exact problem involving postgresql. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around postgresql. Use 'kaydenfu/documentation-images' as a source anchor and identify relevant APIs, dependencie... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
4b6a5bf1175532d7bd35a367 | test | interaction_design | github | https://github.com/fastapi/full-stack-fastapi-template | fastapi/full-stack-fastapi-template | marketplace | css | graphql | Design interaction states for a marketplace. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "fastapi/full-stack-fastapi-template", "source_url": "https://github.com/fastapi/full-stack-fa... | Specify default, hover, focus, active, disabled, loading, success, error, and empty states. | web-research-coding-5m-1.1.0 | |
b39f89503812fc79f4855021 | test | api_design | stackexchange | https://stackoverflow.com/questions/510348/how-do-i-make-a-time-delay | How do I make a time delay? | search_interface | rust | distributed_systems | Design a production API for a distributed_systems application. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How do I make a time delay?", "source_url": "https://stackoverflow.com/questions/510348/how-d... | Specify resources, endpoints, schemas, validation, authentication, authorization, errors, pagination, versioning, idempotency, and tests. | web-research-coding-5m-1.1.0 | |
c29078459973b412d00143ab | test | system_analysis | stackexchange | https://stackoverflow.com/questions/7042340/error-cant-set-headers-after-they-are-sent-to-the-client | Error: Can't set headers after they are sent to the client | finance | css | algorithms | Perform a deep multi-layer analysis of algorithms for a finance using css. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Error: Can't set headers after they are sent to the client", "source_url": "https://stack... | === 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 'Error: Can't set headers after they are sent to the client' as a source anchor and id... | web-research-coding-5m-1.1.0 | |
f8d3e2a5ffd561aeda0dd05c | test | unit_testing | huggingface | https://huggingface.co/datasets/darkknight25/Vulnerable_Programming_Dataset | darkknight25/Vulnerable_Programming_Dataset | social_app | cpp | html | Create a unit-testing strategy for cpp code involving html. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "darkknight25/Vulnerable_Programming_Dataset", "source_url": "https://huggingface.co/datasets/... | Cover normal cases, edge cases, invalid inputs, failure modes, mocks, and regression tests. | web-research-coding-5m-1.1.0 | |
f7911785bac1f5af407136bc | test | refactoring_security | npm | https://www.npmjs.com/package/tailwindcss | tailwindcss | social_app | go | serverless | Refactor a go system related to serverless. Focus on refactoring security. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "tailwindcss", "source_url": "https://www.npmjs.com/package/tailwindcss", "source_type": "pack... | === 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 | |
e911e70ec48e3c83f3990685 | test | accessibility_fix | web_docs | https://www.typescriptlang.org/docs/ | TypeScript Documentation | portfolio | php | microservices | Create an accessibility remediation plan for a portfolio. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "TypeScript Documentation", "source_url": "https://www.typescriptlang.org/docs/", "source_type... | Check semantic HTML, keyboard navigation, focus management, accessible names, labels, errors, contrast, and screen-reader behavior. | web-research-coding-5m-1.1.0 | |
9360abe5c0725f886f7aed9f | test | local_development_experience | pypi | https://pypi.org/project/uvicorn/ | uvicorn | saas | python | caching | Perform a deep developer-experience analysis for a python project involving caching. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "uvicorn", "source_url": "https://pypi.org/project/uvicorn/", "source_type": "package", "topic... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
b7f9bf5358fea83e2fed7494 | test | accessibility_fix | npm | https://www.npmjs.com/package/eslint | eslint | social_app | typescript | authentication | Create an accessibility remediation plan for a social_app. | {"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... | Check semantic HTML, keyboard navigation, focus management, accessible names, labels, errors, contrast, and screen-reader behavior. | web-research-coding-5m-1.1.0 | |
6fca156c36f04b570d9b0525 | test | repository_issue_reasoning | stackexchange | https://stackoverflow.com/questions/28975896/is-there-a-way-to-check-for-both-null-and-undefined | Is there a way to check for both `null` and `undefined`? | developer_tool | java | debugging | Perform a deep multi-layer analysis of debugging for a developer_tool 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": "Is there a way to check for both `null` and `undefined`?", "source_url": "https://stackoverfl... | === 1. PROBLEM ===
Define the exact problem involving debugging. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around debugging. Use 'Is there a way to check for both `null` and `undefined`?' as a source anchor and identify r... | web-research-coding-5m-1.1.0 | |
f4768b3ada34ef1db17735b5 | test | api_design | mdn | https://developer.mozilla.org/en-US/docs/Web/Accessibility | Accessibility | community | scala | microservices | Design a production API for a microservices application. | {"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", "... | Specify resources, endpoints, schemas, validation, authentication, authorization, errors, pagination, versioning, idempotency, and tests. | web-research-coding-5m-1.1.0 | |
6e7bda3d89912b5c7e8d4cf1 | test | dashboard | mdn | https://developer.mozilla.org/en-US/docs/Web/API | Web APIs | documentation | kotlin | machine_learning | Design a production dashboard for machine_learning. | {"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": "... | Include navigation, KPIs, tables/charts, filters, loading states, empty states, errors, and responsive behavior. | web-research-coding-5m-1.1.0 | |
9bcd0aa13afad0087d6585b8 | test | javascript_generation | web_docs | https://git-scm.com/doc | Git Documentation | developer_tool | css | debugging | Implement JavaScript interactions for a developer_tool. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Git Documentation", "source_url": "https://git-scm.com/doc", "source_type": "documentation", ... | Use modular event handling, validation, state management, error handling, and progressive enhancement. | function validateInput(value) {
if (!value || value.trim().length === 0) {
throw new Error("Input is required");
}
return value.trim();
} | web-research-coding-5m-1.1.0 |
58acc2e962743f163a5182ec | test | refactoring_testability | mdn | https://developer.mozilla.org/en-US/docs/Web/HTML | HTML | dashboard | go | developer_experience | Refactor a go system related to developer_experience. Focus on refactoring testability. | {"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 ===
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 | |
57897b9b1ee58d8ae90069a4 | test | ux_design | mdn | https://developer.mozilla.org/en-US/docs/Web/HTML | HTML | landing_page | kotlin | mongodb | Design the complete UX flow of a landing_page for mongodb. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "HTML", "source_url": "https://developer.mozilla.org/en-US/docs/Web/HTML", "source_type": "doc... | Map user goals, entry points, navigation, primary actions, feedback, loading states, empty states, errors, recovery paths, and completion. | web-research-coding-5m-1.1.0 | |
32c10f960bec4fd41ad2a5be | test | refactoring_readability | pypi | https://pypi.org/project/typer/ | typer | productivity | go | css | Refactor a go system related to css. Focus on refactoring readability. | {"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": "... | === 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 | |
ebb37fa9e4d68a8851973955 | test | typescript_generation | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model | DOM | blog | cpp | debugging | Implement TypeScript logic for a blog. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "DOM", "source_url": "https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model",... | 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 |
0cb8cbfcf2cc7ca1eb4cfabf | test | search_intent_classification | gitlab | https://gitlab.com/gemseo/dev/gemseo-mlearning | gemseo/dev/gemseo-mlearning | admin_panel | html | frontend | Classify the search intent for a query about frontend. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "gemseo/dev/gemseo-mlearning", "source_url": "https://gitlab.com/gemseo/dev/gemseo-mlearning",... | === 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 ===
"frontend vs alternatives"
=== CLASSIFICATION ===
Comparative / informational.
... | web-research-coding-5m-1.1.0 | |
b90a6c5df5095931d49ae6b1 | test | debugging | mdn | https://developer.mozilla.org/en-US/docs/Web/API | Web APIs | blog | swift | nodejs | Create a realistic swift debugging problem involving nodejs. | {"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": "... | Provide symptoms, reproduction strategy, diagnostic steps, root-cause analysis, minimal fix, and regression coverage. | 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.