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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
0e2c90de1860dc9bb9a2f3c2 | test | debugging_experience | codeberg | https://codeberg.org/plaublin/100-exercises-to-learn-rust | plaublin/100-exercises-to-learn-rust | search_interface | kotlin | user_experience | Perform a deep developer-experience analysis for a kotlin project involving user_experience. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "plaublin/100-exercises-to-learn-rust", "source_url": "https://codeberg.org/plaublin/100-exerc... | === 1. 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 | |
223ab34b0df135db2e899371 | test | refactoring_architecture | stackexchange | https://stackoverflow.com/questions/415511/how-do-i-get-the-current-time-in-python | How do I get the current time in Python? | blog | c | fullstack | Refactor a c system related to fullstack. Focus on refactoring architecture. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How do I get the current time in Python?", "source_url": "https://stackoverflow.com/questions... | === 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 | |
0b981a6b9c327ddac179d331 | test | form_ui | mdn | https://developer.mozilla.org/en-US/docs/Web/HTTP | HTTP | finance | kotlin | data_structures | Design an accessible form for data_structures. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "HTTP", "source_url": "https://developer.mozilla.org/en-US/docs/Web/HTTP", "source_type": "doc... | Use labels, validation, clear errors, keyboard navigation, appropriate autocomplete, and accessible status messaging. | web-research-coding-5m-1.1.0 | |
688c4d8e42697dbe019ed24a | test | repository_documentation | huggingface | https://huggingface.co/datasets/codeShare/text-to-image-prompts | codeShare/text-to-image-prompts | dashboard | rust | database | Perform a deep multi-layer analysis of database for a dashboard 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": "codeShare/text-to-image-prompts", "source_url": "https://huggingface.co/datasets/codeShare/te... | === 1. PROBLEM ===
Define the exact problem involving database. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around database. Use 'codeShare/text-to-image-prompts' as a source anchor and identify relevant APIs, dependencies,... | web-research-coding-5m-1.1.0 | |
e4deff635e1351fdc40c9216 | test | build_experience | stackexchange | https://stackoverflow.com/questions/19578796/what-is-the-save-option-for-npm-install | What is the --save option for npm install? | landing_page | dart | rest_api | Perform a deep developer-experience analysis for a dart project involving rest_api. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "What is the --save option for npm install?", "source_url": "https://stackoverflow.com/questio... | === 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 | |
30c24aa4c0cc247a60685bc0 | test | form_ui | huggingface | https://huggingface.co/datasets/nomic-ai/cornstack-python-v1 | nomic-ai/cornstack-python-v1 | blog | c | javascript | Design an accessible form for javascript. | {"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... | Use labels, validation, clear errors, keyboard navigation, appropriate autocomplete, and accessible status messaging. | web-research-coding-5m-1.1.0 | |
80d802d33dc33d1654b27ac3 | test | research_summary | github | https://github.com/bytedance/deer-flow | bytedance/deer-flow | portfolio | java | observability | Summarize the current state of knowledge about observability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "bytedance/deer-flow", "source_url": "https://github.com/bytedance/deer-flow", "source_type": ... | === OVERVIEW ===
observability 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 ===
bytedance/deer-f... | web-research-coding-5m-1.1.0 | |
fef2dece002cb936332feeda | test | tradeoff_analysis | stackexchange | https://stackoverflow.com/questions/2610497/change-an-html-inputs-placeholder-color-with-css | Change an HTML input's placeholder color with CSS | developer_tool | python | open_source | Perform a deep multi-layer analysis of open_source 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": "Change an HTML input's placeholder color with CSS", "source_url": "https://stackoverflow.... | === 1. PROBLEM ===
Define the exact problem involving open_source. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around open_source. Use 'Change an HTML input's placeholder color with CSS' as a source anchor and identify ... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
a378f20939e53d61b84fe133 | test | dependency_impact_analysis | web_docs | https://react.dev/ | React Documentation | community | html | rest_api | Perform a deep multi-layer analysis of rest_api 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": "React Documentation", "source_url": "https://react.dev/", "source_type": "documentation", "to... | === 1. PROBLEM ===
Define the exact problem involving rest_api. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around rest_api. Use 'React Documentation' as a source anchor and identify relevant APIs, dependencies, versions, s... | web-research-coding-5m-1.1.0 | |
270e49b26f7c3b94a4503b5c | test | api_design | pypi | https://pypi.org/project/scrapy/ | scrapy | dashboard | css | open_source | Design a production API for a open_source application. | {"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":... | Specify resources, endpoints, schemas, validation, authentication, authorization, errors, pagination, versioning, idempotency, and tests. | web-research-coding-5m-1.1.0 | |
9ac3543f5e58c2430dbf4ace | test | typescript_generation | npm | https://www.npmjs.com/package/vite | vite | admin_panel | python | caching | Implement TypeScript logic for a admin_panel. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "vite", "source_url": "https://www.npmjs.com/package/vite", "source_type": "package", "topic":... | 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 |
94e290f856ddb823af4caee9 | test | multi_layer_analysis | npm | https://www.npmjs.com/package/three | three | documentation | html | linux | Perform a deep multi-layer analysis of linux 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": "three", "source_url": "https://www.npmjs.com/package/three", "source_type": "package", "topic... | === 1. PROBLEM ===
Define the exact problem involving linux. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around linux. Use 'three' as a source anchor and identify relevant APIs, dependencies, versions, standards, and techni... | web-research-coding-5m-1.1.0 | |
c03c69ca602269e641d61196 | test | multi_layer_analysis | gitlab | https://gitlab.com/cashscript-py/cashscript-py | cashscript-py/cashscript-py | dashboard | go | testing | Perform a deep multi-layer analysis of testing for a dashboard 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": "cashscript-py/cashscript-py", "source_url": "https://gitlab.com/cashscript-py/cashscript-py",... | === 1. PROBLEM ===
Define the exact problem involving testing. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around testing. Use 'cashscript-py/cashscript-py' as a source anchor and identify relevant APIs, dependencies, versi... | web-research-coding-5m-1.1.0 | |
9cd307bb4df57602a3372610 | test | design_components | stackexchange | https://stackoverflow.com/questions/31079081/how-can-i-programmatically-navigate-using-react-router | How can I programmatically navigate using React Router? | ecommerce | html | backend | Create a component architecture for a ecommerce. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How can I programmatically navigate using React Router?", "source_url": "https://stackoverflo... | Define primitive components, composite components, variants, states, composition rules, and accessibility contracts. | web-research-coding-5m-1.1.0 | |
5b2d2a95cdbadc6adace164f | test | design_review | pypi | https://pypi.org/project/rich/ | rich | marketplace | swift | data_engineering | 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": "rich", "source_url": "https://pypi.org/project/rich/", "source_type": "package", "topic": "da... | Review hierarchy, consistency, responsiveness, accessibility, interaction design, content clarity, and implementation feasibility. | web-research-coding-5m-1.1.0 | |
4ee293093d5adda6663d8f42 | test | visual_hierarchy | huggingface | https://huggingface.co/datasets/puttatidam/software-documentation-zsm-bitextmining | puttatidam/software-documentation-zsm-bitextmining | blog | css | linux | Improve visual hierarchy in a blog. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "puttatidam/software-documentation-zsm-bitextmining", "source_url": "https://huggingface.co/da... | Use heading structure, typography, spacing, grouping, alignment, contrast, and consistent affordances. | web-research-coding-5m-1.1.0 | |
bbc9f0c9c9b94de8e39c618e | test | web_search_query | mdn | https://developer.mozilla.org/en-US/docs/Web/JavaScript | JavaScript | ecommerce | php | linux | Write an effective web search query to research the topic: linux. | {"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... | === QUERY ===
linux best practices documentation tutorial
=== INTENT ===
Find authoritative documentation, tutorials, and real-world examples related to the topic.
=== KEYWORDS ===
- linux
- documentation
- best practices
- examples
- reference
=== SOURCE PREFERENCE ===
Prefer official documentation, well-maintained... | web-research-coding-5m-1.1.0 | |
0982493bfb7ecab8e10cb6bd | test | product_analysis | huggingface | https://huggingface.co/datasets/m-a-p/CodeFeedback-Filtered-Instruction | m-a-p/CodeFeedback-Filtered-Instruction | landing_page | swift | debugging | Perform a deep multi-layer analysis of debugging for a landing_page 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": "m-a-p/CodeFeedback-Filtered-Instruction", "source_url": "https://huggingface.co/datasets/m-a-... | === 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 'm-a-p/CodeFeedback-Filtered-Instruction' as a source anchor and identify relevant APIs, dep... | web-research-coding-5m-1.1.0 | |
2b8b12cf2351a9ca0114ed4f | test | fact_verification | stackexchange | https://stackoverflow.com/questions/3087975/how-can-i-change-the-cursor-into-a-hand-when-a-user-hovers-over-a-list-item | How can I change the cursor into a hand when a user hovers over a list item? | documentation | swift | frontend | Verify a technical claim about frontend. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How can I change the cursor into a hand when a user hovers over a list item?", "source_url": ... | === CLAIM ===
A common claim about frontend.
=== 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-depe... | web-research-coding-5m-1.1.0 | |
8b3cd2be0202ecd84dae3deb | test | testing_experience | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model | DOM | productivity | html | fullstack | Perform a deep developer-experience analysis for a html project involving fullstack. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "DOM", "source_url": "https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model",... | === 1. 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 | |
aaf442b31acb2e016f2c6f4b | test | source_selection | npm | https://www.npmjs.com/package/vitest | vitest | dashboard | dart | react | Select the most reliable sources to research react. | {"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... | === 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 | |
937a22ea8e39d34b2c7a0bae | test | design_accessibility | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model | DOM | finance | css | nlp | Audit accessibility for a finance. | {"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",... | Check semantic structure, keyboard navigation, focus visibility, accessible names, labels, errors, contrast, and screen-reader behavior. | web-research-coding-5m-1.1.0 | |
7542d103aca169a977590771 | test | visual_hierarchy | huggingface | https://huggingface.co/datasets/BAAI/IndustryCorpus2_computer_programming_code | BAAI/IndustryCorpus2_computer_programming_code | analytics | python | react | Improve visual hierarchy in a analytics. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "BAAI/IndustryCorpus2_computer_programming_code", "source_url": "https://huggingface.co/datase... | Use heading structure, typography, spacing, grouping, alignment, contrast, and consistent affordances. | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
7c50c277bdd80e9a9e1f926c | test | responsive_website | huggingface | https://huggingface.co/datasets/ellamind/hellaswag-multilingual | ellamind/hellaswag-multilingual | education | go | security | Design a complete responsive education for security. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "ellamind/hellaswag-multilingual", "source_url": "https://huggingface.co/datasets/ellamind/hel... | Cover mobile, tablet, and desktop layouts, semantic structure, responsive components, accessibility, performance, and UX. | web-research-coding-5m-1.1.0 | |
d1d26626a80c3a16a36e63c2 | test | seo_fix | web_docs | https://www.typescriptlang.org/docs/ | TypeScript Documentation | education | css | authentication | Create an SEO improvement plan for a education about authentication. | {"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... | Cover titles, descriptions, headings, canonical URLs, structured data, internal links, crawlability, and performance. | web-research-coding-5m-1.1.0 | |
feb4fa874edb7685c61d9a78 | test | design_consistency | web_docs | https://www.postgresql.org/docs/ | PostgreSQL Documentation | documentation | scala | sql | Audit design consistency across a documentation. | {"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": "... | Check repeated patterns, component variants, spacing, typography, interaction states, terminology, and responsiveness. | web-research-coding-5m-1.1.0 | |
158070422b39a0dc331163c9 | test | tradeoff_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/HTTP | HTTP | community | c | machine_learning | Perform a deep multi-layer analysis of machine_learning for a community 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": "HTTP", "source_url": "https://developer.mozilla.org/en-US/docs/Web/HTTP", "source_type": "doc... | === 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 'HTTP' as a source anchor and identify relevant APIs, dependencies, versions, ... | web-research-coding-5m-1.1.0 | |
4fce63450288406fbec906a1 | test | dependency_impact_analysis | web_docs | https://www.postgresql.org/docs/ | PostgreSQL Documentation | documentation | html | nlp | Perform a deep multi-layer analysis of nlp 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": "PostgreSQL Documentation", "source_url": "https://www.postgresql.org/docs/", "source_type": "... | === 1. PROBLEM ===
Define the exact problem involving nlp. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around nlp. Use 'PostgreSQL Documentation' as a source anchor and identify relevant APIs, dependencies, versions, standa... | web-research-coding-5m-1.1.0 | |
2d0deab0c824fc55de7c73ec | test | repository_architecture | gitlab | https://gitlab.com/SaikoJosh/safe-env-vars | SaikoJosh/safe-env-vars | finance | c | computer_vision | Perform a deep multi-layer analysis of computer_vision 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": "SaikoJosh/safe-env-vars", "source_url": "https://gitlab.com/SaikoJosh/safe-env-vars", "source... | === 1. PROBLEM ===
Define the exact problem involving computer_vision. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around computer_vision. Use 'SaikoJosh/safe-env-vars' as a source anchor and identify relevant APIs, depende... | web-research-coding-5m-1.1.0 | |
e38e32774a6b4fd2d8ea0357 | test | landing_page | gitlab | https://gitlab.com/cznic/quickjs | cznic/quickjs | education | sql | frontend | Design a landing page for a frontend product. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "cznic/quickjs", "source_url": "https://gitlab.com/cznic/quickjs", "source_type": "repository"... | Include hero, value proposition, features, CTA, FAQ, responsive behavior, SEO, accessibility, and analytics. | web-research-coding-5m-1.1.0 | |
b6163f44fdf1a94e71d45568 | test | html_generation | mdn | https://developer.mozilla.org/en-US/docs/Web/HTTP | HTTP | landing_page | rust | open_source | Create semantic HTML for a landing_page about open_source. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "HTTP", "source_url": "https://developer.mozilla.org/en-US/docs/Web/HTTP", "source_type": "doc... | Use 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 |
7ecd133b64e947ad1720a2c6 | test | research_summary | stackexchange | https://stackoverflow.com/questions/7244321/how-do-i-update-or-sync-a-forked-repository-on-github | How do I update or sync a forked repository on GitHub? | search_interface | shell | javascript | Summarize the current state of knowledge about javascript. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How do I update or sync a forked repository on GitHub?", "source_url": "https://stackoverflow... | === OVERVIEW ===
javascript in one paragraph.
=== KEY CONCEPTS ===
- Core definitions
- Main use cases
- Common patterns
=== CURRENT BEST PRACTICES ===
- Recommended approaches
- Known anti-patterns
=== OPEN QUESTIONS ===
- Areas with active development
- Known limitations
=== PRIMARY SOURCE ===
How do I update or ... | web-research-coding-5m-1.1.0 | |
a69adea32ad23330a45a2004 | test | research_plan | web_docs | https://docs.python.org/3/ | Python Documentation | saas | c | data_structures | Build a structured research plan to deeply understand data_structures. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Python Documentation", "source_url": "https://docs.python.org/3/", "source_type": "documentat... | === GOAL ===
Produce a reliable, current, and actionable understanding of data_structures.
=== PHASES ===
1. Orientation — skim official docs and README.
2. Deep read — study specs, RFCs, changelogs.
3. Hands-on — reproduce examples locally.
4. Comparison — compare alternatives and trade-offs.
5. Synthesis — write fin... | web-research-coding-5m-1.1.0 | |
e0de22e487869a3a759d3714 | test | css_generation | mdn | https://developer.mozilla.org/en-US/docs/Web/Performance | Performance | marketplace | php | distributed_systems | Create responsive CSS for a marketplace. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "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 |
a499995618d5dfd5f2c78bda | test | refactoring_modularization | huggingface | https://huggingface.co/datasets/Omar-keita/Machine-Learning-Socratic-Dataset | Omar-keita/Machine-Learning-Socratic-Dataset | developer_tool | ruby | sql | Refactor a ruby system related to sql. Focus on refactoring modularization. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Omar-keita/Machine-Learning-Socratic-Dataset", "source_url": "https://huggingface.co/datasets... | === 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 | |
671fff2a10b6be329ea54bc4 | test | research_plan | npm | https://www.npmjs.com/package/vite | vite | community | java | typescript | Build a structured research plan to deeply understand typescript. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "vite", "source_url": "https://www.npmjs.com/package/vite", "source_type": "package", "topic":... | === GOAL ===
Produce a reliable, current, and actionable understanding of typescript.
=== PHASES ===
1. Orientation — skim official docs and README.
2. Deep read — study specs, RFCs, changelogs.
3. Hands-on — reproduce examples locally.
4. Comparison — compare alternatives and trade-offs.
5. Synthesis — write findings... | web-research-coding-5m-1.1.0 | |
a6d956c2aca86156f6517fc6 | test | api_developer_experience | huggingface | https://huggingface.co/datasets/israellaguan/axay-javascript-dataset-pn | israellaguan/axay-javascript-dataset-pn | developer_tool | swift | ci_cd | Perform a deep developer-experience analysis for a swift project involving ci_cd. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "israellaguan/axay-javascript-dataset-pn", "source_url": "https://huggingface.co/datasets/isra... | === 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 | |
6e5cbda337326417fc062ce5 | test | ux_analysis | npm | https://www.npmjs.com/package/zod | zod | documentation | typescript | software_architecture | Perform a deep multi-layer analysis of software_architecture for a documentation 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": "zod", "source_url": "https://www.npmjs.com/package/zod", "source_type": "package", "topic": "... | === 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 'zod' as a source anchor and identify relevant APIs, dependencies, v... | web-research-coding-5m-1.1.0 | |
3b0ee6cfb7c879b5bdb01e2c | test | dx_analysis | gitlab | https://gitlab.com/gitlab-org/gitlab-pages | gitlab-org/gitlab-pages | portfolio | go | data_engineering | Perform a deep developer-experience analysis for a go project involving data_engineering. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "gitlab-org/gitlab-pages", "source_url": "https://gitlab.com/gitlab-org/gitlab-pages", "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 | |
cdf1daba9efeab8480657330 | test | dx_analysis | gitlab | https://gitlab.com/mysterysd.sd/WZML-X | mysterysd.sd/WZML-X | developer_tool | ruby | postgresql | Perform a deep developer-experience analysis for a ruby project involving postgresql. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "mysterysd.sd/WZML-X", "source_url": "https://gitlab.com/mysterysd.sd/WZML-X", "source_type": ... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
0f942027369ff91d514ff496 | test | multi_layer_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API | Fetch API | blog | sql | microservices | Perform a deep multi-layer analysis of microservices for a blog 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": "Fetch API", "source_url": "https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API", "sour... | === 1. PROBLEM ===
Define the exact problem involving microservices. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around microservices. Use 'Fetch API' as a source anchor and identify relevant APIs, dependencies, versions, s... | web-research-coding-5m-1.1.0 | |
e17cee49cbf31e0277f73b21 | test | design_components | stackexchange | https://stackoverflow.com/questions/278192/view-the-change-history-of-a-file-using-git-versioning | View the change history of a file using Git versioning | analytics | dart | web_accessibility | Create a component architecture for a analytics. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "View the change history of a file using Git versioning", "source_url": "https://stackoverflow... | Define primitive components, composite components, variants, states, composition rules, and accessibility contracts. | web-research-coding-5m-1.1.0 | |
d732e8ff497ae39646f45e91 | test | design_consistency | huggingface | https://huggingface.co/datasets/leo009/python-programming-instructions | leo009/python-programming-instructions | social_app | swift | rest_api | Audit design consistency across a social_app. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "leo009/python-programming-instructions", "source_url": "https://huggingface.co/datasets/leo00... | Check repeated patterns, component variants, spacing, typography, interaction states, terminology, and responsiveness. | web-research-coding-5m-1.1.0 | |
afe530acc5d3ef0ece9f3a55 | test | refactoring_modularization | github | https://github.com/jobbole/awesome-python-cn | jobbole/awesome-python-cn | finance | css | data_structures | Refactor a css 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": "jobbole/awesome-python-cn", "source_url": "https://github.com/jobbole/awesome-python-cn", "so... | === 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 | |
876e2dd8339f1ea0a96b1edb | test | architecture_analysis | npm | https://www.npmjs.com/package/axios | axios | admin_panel | typescript | user_experience | Perform a deep multi-layer analysis of user_experience for a admin_panel 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": "axios", "source_url": "https://www.npmjs.com/package/axios", "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 'axios' as a source anchor and identify relevant APIs, dependencies, versions, s... | web-research-coding-5m-1.1.0 | |
78880fa7be987ce026085990 | test | typescript_generation | web_docs | https://go.dev/doc/ | Go Documentation | search_interface | ruby | nodejs | 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": "Go Documentation", "source_url": "https://go.dev/doc/", "source_type": "documentation", "topi... | 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 |
dad295d66f679ec5bd11a1df | test | refactoring_observability | npm | https://www.npmjs.com/package/zod | zod | analytics | scala | web_accessibility | Refactor a scala system related to web_accessibility. Focus on refactoring observability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "zod", "source_url": "https://www.npmjs.com/package/zod", "source_type": "package", "topic": "... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Improve logging, metrics, tracing, diagnostics, and failure visibility.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify d... | web-research-coding-5m-1.1.0 | |
7c40854a931739bd38af719b | test | javascript_generation | pypi | https://pypi.org/project/streamlit/ | streamlit | education | python | data_engineering | Implement JavaScript interactions for a education. | {"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... | 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 |
afdd9b20aa4508bcb07642c3 | test | seo_fix | web_docs | https://www.typescriptlang.org/docs/ | TypeScript Documentation | admin_panel | css | authentication | Create an SEO improvement plan for a admin_panel about authentication. | {"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... | Cover titles, descriptions, headings, canonical URLs, structured data, internal links, crawlability, and performance. | web-research-coding-5m-1.1.0 | |
35fb8d05e41d729f4b31692e | test | source_comparison | huggingface | https://huggingface.co/datasets/McKlay/documentation-images | McKlay/documentation-images | documentation | kotlin | frontend | Compare multiple sources about frontend 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": "McKlay/documentation-images", "source_url": "https://huggingface.co/datasets/McKlay/documenta... | === SOURCES ===
- McKlay/documentation-images (https://huggingface.co/datasets/McKlay/documentation-images)
- Official documentation
- Community discussions
=== AGREEMENTS ===
Identify claims supported by multiple independent sources.
=== CONTRADICTIONS ===
Identify conflicting claims and their likely cause (version ... | web-research-coding-5m-1.1.0 | |
6eebd95d72e901f96d290f2f | test | upgrade_experience | pypi | https://pypi.org/project/httpx/ | httpx | analytics | c | deep_learning | Perform a deep developer-experience analysis for a c project involving deep_learning. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "httpx", "source_url": "https://pypi.org/project/httpx/", "source_type": "package", "topic": "... | === 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 | |
84891579b6b6abd0f9200773 | test | repository_understanding | mdn | https://developer.mozilla.org/en-US/docs/Web/HTTP | HTTP | dashboard | python | caching | Perform a deep multi-layer analysis of caching for a dashboard using python. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "HTTP", "source_url": "https://developer.mozilla.org/en-US/docs/Web/HTTP", "source_type": "doc... | === 1. PROBLEM ===
Define the exact problem involving caching. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around caching. Use 'HTTP' as a source anchor and identify relevant APIs, dependencies, versions, standards, and tec... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
a98ea0d8e8c75cf807d7e330 | test | interaction_design | gitlab | https://gitlab.com/fdroid/repomaker | fdroid/repomaker | finance | html | cloud | 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": "fdroid/repomaker", "source_url": "https://gitlab.com/fdroid/repomaker", "source_type": "repos... | Specify default, hover, focus, active, disabled, loading, success, error, and empty states. | web-research-coding-5m-1.1.0 | |
3e0df52c6e871513343501fb | test | ui_design | huggingface | https://huggingface.co/datasets/MathCodeBench/linear-programming | MathCodeBench/linear-programming | landing_page | css | javascript | Design a production-quality UI for a landing_page focused on javascript. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "MathCodeBench/linear-programming", "source_url": "https://huggingface.co/datasets/MathCodeBen... | Define layout, typography, spacing, hierarchy, components, states, responsive behavior, and accessibility. | web-research-coding-5m-1.1.0 | |
0dcdf0bba7bf0803f35a65e2 | test | repository_dependency_analysis | pypi | https://pypi.org/project/pytest/ | pytest | education | shell | devops | Perform a deep multi-layer analysis of devops 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": "pytest", "source_url": "https://pypi.org/project/pytest/", "source_type": "package", "topic":... | === 1. PROBLEM ===
Define the exact problem involving devops. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around devops. Use 'pytest' as a source anchor and identify relevant APIs, dependencies, versions, standards, and tec... | web-research-coding-5m-1.1.0 | |
16456a85791ed8eae4d9d050 | test | deep_technical_analysis | stackexchange | https://stackoverflow.com/questions/122102/what-is-the-most-efficient-way-to-deep-clone-an-object-in-javascript | What is the most efficient way to deep clone an object in JavaScript? | finance | go | serverless | Perform a deep multi-layer analysis of serverless for a finance 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": "What is the most efficient way to deep clone an object in JavaScript?", "source_url": "https:... | === 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 'What is the most efficient way to deep clone an object in JavaScript?' as a source anchor... | web-research-coding-5m-1.1.0 | |
c2aac85286456b54cd3e0607 | test | refactoring_scalability | huggingface | https://huggingface.co/datasets/bgudmestad/Nushell_documentation | bgudmestad/Nushell_documentation | analytics | dart | debugging | Refactor a dart system related to debugging. Focus on refactoring scalability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "bgudmestad/Nushell_documentation", "source_url": "https://huggingface.co/datasets/bgudmestad/... | === 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 | |
5656b09c6ded46f41d53b8b2 | test | technical_research | stackexchange | https://stackoverflow.com/questions/8318911/why-does-html-think-chucknorris-is-a-color | Why does HTML think “chucknorris” is a color? | productivity | kotlin | graphql | Perform a technical research task about graphql, focused on implementation details. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Why does HTML think “chucknorris” is a color?", "source_url": "https://stackoverflow.com/ques... | === SCOPE ===
Technical behavior of graphql.
=== QUESTIONS ===
- What are the inputs, outputs, and invariants?
- What are the performance characteristics?
- What are the security implications?
- What are the compatibility constraints?
=== EVIDENCE ===
- Why does HTML think “chucknorris” is a color? (https://stackover... | web-research-coding-5m-1.1.0 | |
8632edf3e698e3eaf108522e | test | repository_dependency_analysis | stackexchange | https://stackoverflow.com/questions/40140149/use-async-await-with-array-map | Use async await with Array.map | documentation | go | open_source | Perform a deep multi-layer analysis of open_source for a documentation 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": "Use async await with Array.map", "source_url": "https://stackoverflow.com/questions/40140149/... | === 1. PROBLEM ===
Define the exact problem involving open_source. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around open_source. Use 'Use async await with Array.map' as a source anchor and identify relevant APIs, dependen... | web-research-coding-5m-1.1.0 | |
68822874c4c5191b9ba1cc1b | test | evidence_extraction | stackexchange | https://stackoverflow.com/questions/784929/what-does-the-double-exclamation-mark-operator-do-in-javascript | What does the !! (double exclamation mark) operator do in JavaScript? | education | go | security | Extract verifiable evidence about security from the given source. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "What does the !! (double exclamation mark) operator do in JavaScript?", "source_url": "https:... | === SOURCE ===
What does the !! (double exclamation mark) operator do in JavaScript?
https://stackoverflow.com/questions/784929/what-does-the-double-exclamation-mark-operator-do-in-javascript
=== EVIDENCE ITEMS ===
1. Explicit claims made by the source
2. Code examples or API signatures
3. Version / compatibility stat... | web-research-coding-5m-1.1.0 | |
62b49c8ee6695073fc64d2f7 | test | repository_dependency_analysis | web_docs | https://fastapi.tiangolo.com/ | FastAPI Documentation | blog | css | software_architecture | Perform a deep multi-layer analysis of software_architecture for a blog 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": "FastAPI Documentation", "source_url": "https://fastapi.tiangolo.com/", "source_type": "docume... | === 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 'FastAPI Documentation' as a source anchor and identify relevant API... | web-research-coding-5m-1.1.0 | |
7a427258bc43b3337dac0ff5 | test | ui_design | gitlab | https://gitlab.com/robocup-sim/JaSMIn | robocup-sim/JaSMIn | saas | kotlin | observability | Design a production-quality UI for a saas focused on observability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "robocup-sim/JaSMIn", "source_url": "https://gitlab.com/robocup-sim/JaSMIn", "source_type": "r... | Define layout, typography, spacing, hierarchy, components, states, responsive behavior, and accessibility. | web-research-coding-5m-1.1.0 | |
2668a963b0631081a1647cb9 | test | search_intent_classification | mdn | https://developer.mozilla.org/en-US/docs/Web/API | Web APIs | search_interface | php | 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": "Web APIs", "source_url": "https://developer.mozilla.org/en-US/docs/Web/API", "source_type": "... | === 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 | |
cc8928b76800e6a411a50fec | test | build_experience | mdn | https://developer.mozilla.org/en-US/docs/Web/CSS | CSS | saas | python | docker | Perform a deep developer-experience analysis for a python project involving docker. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "CSS", "source_url": "https://developer.mozilla.org/en-US/docs/Web/CSS", "source_type": "docum... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
69aeeca4f15fb046071bb29a | test | design_tokens | mdn | https://developer.mozilla.org/en-US/docs/Web/HTTP | HTTP | community | c | ci_cd | Create design tokens for a community. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "HTTP", "source_url": "https://developer.mozilla.org/en-US/docs/Web/HTTP", "source_type": "doc... | Define reusable tokens for typography, spacing, radii, sizing, elevation, interaction states, and responsive behavior. | web-research-coding-5m-1.1.0 | |
62318516e1e348c4ea269909 | test | documentation_experience | npm | https://www.npmjs.com/package/next | next | landing_page | swift | graphql | Perform a deep developer-experience analysis for a swift project involving graphql. | {"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":... | === 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 | |
174cb79aa02785a9f995289b | test | technical_research | huggingface | https://huggingface.co/datasets/Machine-Learning-Oncology/orena-frame-annotations | Machine-Learning-Oncology/orena-frame-annotations | analytics | c | devops | Perform a technical research task about devops, focused on implementation details. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Machine-Learning-Oncology/orena-frame-annotations", "source_url": "https://huggingface.co/dat... | === SCOPE ===
Technical behavior of devops.
=== QUESTIONS ===
- What are the inputs, outputs, and invariants?
- What are the performance characteristics?
- What are the security implications?
- What are the compatibility constraints?
=== EVIDENCE ===
- Machine-Learning-Oncology/orena-frame-annotations (https://huggin... | web-research-coding-5m-1.1.0 | |
5cb0be128e4969c8b26e6976 | test | tradeoff_analysis | pypi | https://pypi.org/project/pytest/ | pytest | search_interface | python | algorithms | Perform a deep multi-layer analysis of algorithms for a search_interface using python. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "pytest", "source_url": "https://pypi.org/project/pytest/", "source_type": "package", "topic":... | === 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 'pytest' as a source anchor and identify relevant APIs, dependencies, versions, standards,... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
b71c2ff5fea540f10fdc8b6e | test | design_components | pypi | https://pypi.org/project/sqlalchemy/ | sqlalchemy | productivity | html | kubernetes | Create a component architecture for a productivity. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "sqlalchemy", "source_url": "https://pypi.org/project/sqlalchemy/", "source_type": "package", ... | Define primitive components, composite components, variants, states, composition rules, and accessibility contracts. | web-research-coding-5m-1.1.0 | |
8a63980f2e51dd5d51fd5f17 | test | architecture_analysis | huggingface | https://huggingface.co/datasets/NJU-LINK/CodeTraceBench | NJU-LINK/CodeTraceBench | social_app | javascript | serverless | Perform a deep multi-layer analysis of serverless for a social_app using javascript. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "NJU-LINK/CodeTraceBench", "source_url": "https://huggingface.co/datasets/NJU-LINK/CodeTraceBe... | === 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 'NJU-LINK/CodeTraceBench' as a source anchor and identify relevant APIs, dependencies, ver... | web-research-coding-5m-1.1.0 | |
98fa4ab75b4a53d2411c9206 | test | algorithm_design | huggingface | https://huggingface.co/datasets/multimodal-reasoning-lab/Competitive-Programming | multimodal-reasoning-lab/Competitive-Programming | dashboard | go | kubernetes | Design a go algorithm for a kubernetes problem. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "multimodal-reasoning-lab/Competitive-Programming", "source_url": "https://huggingface.co/data... | State assumptions, algorithm, complexity, edge cases, correctness reasoning, and testing strategy. | web-research-coding-5m-1.1.0 | |
7cdf51992f76b9b881a5c264 | test | design_tokens | codeberg | https://codeberg.org/UI-Programming-23-24/01-Web-basics-and-git-Jake-Fitzgerald | UI-Programming-23-24/01-Web-basics-and-git-Jake-Fitzgerald | finance | scala | fullstack | Create design tokens for a finance. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "UI-Programming-23-24/01-Web-basics-and-git-Jake-Fitzgerald", "source_url": "https://codeberg.... | Define reusable tokens for typography, spacing, radii, sizing, elevation, interaction states, and responsive behavior. | web-research-coding-5m-1.1.0 | |
83add042b26785380f61207c | test | search_query_rewrite | web_docs | https://react.dev/ | React Documentation | social_app | html | mongodb | Rewrite and improve a vague search query about mongodb 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": "React Documentation", "source_url": "https://react.dev/", "source_type": "documentation", "to... | === ORIGINAL (VAGUE) ===
how to do mongodb
=== REWRITTEN QUERIES ===
1. mongodb official documentation guide
2. mongodb production best practices 2025
3. mongodb common pitfalls and solutions
4. mongodb architecture patterns with examples
=== RATIONALE ===
Add intent (learn / implement / debug), specificity (version,... | web-research-coding-5m-1.1.0 | |
cd5e48038b609b44c52a5c8d | test | evidence_extraction | pypi | https://pypi.org/project/django/ | django | developer_tool | shell | ci_cd | Extract verifiable evidence about ci_cd from the given source. | {"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":... | === SOURCE ===
django
https://pypi.org/project/django/
=== 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 sta... | web-research-coding-5m-1.1.0 | |
8ca8b014e59046cf87d66d43 | test | code_review | huggingface | https://huggingface.co/datasets/Machine-Learning-Oncology/orena-frame-annotations | Machine-Learning-Oncology/orena-frame-annotations | dashboard | swift | docker | Perform a production code review of swift code related to docker. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Machine-Learning-Oncology/orena-frame-annotations", "source_url": "https://huggingface.co/dat... | Review correctness, security, performance, readability, architecture, testing, maintainability, and error handling. | web-research-coding-5m-1.1.0 | |
2de4ceb4d070edf04076edc9 | test | react_generation | stackexchange | https://stackoverflow.com/questions/951021/what-is-the-javascript-version-of-sleep | What is the JavaScript version of sleep()? | blog | typescript | observability | Design React components for a blog. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "What is the JavaScript version of sleep()?", "source_url": "https://stackoverflow.com/questio... | 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 |
205b5dda06475a009a94ff42 | test | refactoring_maintainability | pypi | https://pypi.org/project/numpy/ | numpy | productivity | sql | serverless | Refactor a sql system related to serverless. Focus on refactoring maintainability. | {"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 ===
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 | |
df89792d6900d5e06106444f | test | risk_analysis | huggingface | https://huggingface.co/datasets/emgena/omnimcp_python_backend_architect_teaser | emgena/omnimcp_python_backend_architect_teaser | productivity | rust | distributed_systems | Perform a deep multi-layer analysis of distributed_systems for a productivity 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": "emgena/omnimcp_python_backend_architect_teaser", "source_url": "https://huggingface.co/datase... | === 1. PROBLEM ===
Define the exact problem involving distributed_systems. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around distributed_systems. Use 'emgena/omnimcp_python_backend_architect_teaser' as a source anchor and ... | web-research-coding-5m-1.1.0 | |
c5c1ef6581978304b3bfd50e | test | seo_fix | npm | https://www.npmjs.com/package/vite | vite | social_app | dart | typescript | Create an SEO improvement plan for a social_app about typescript. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "vite", "source_url": "https://www.npmjs.com/package/vite", "source_type": "package", "topic":... | Cover titles, descriptions, headings, canonical URLs, structured data, internal links, crawlability, and performance. | web-research-coding-5m-1.1.0 | |
0c9c77e7ec6bf74aff21c072 | test | multi_hop_research | web_docs | https://react.dev/ | React Documentation | dashboard | swift | database | Perform multi-hop research about database: 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": "React Documentation", "source_url": "https://react.dev/", "source_type": "documentation", "to... | === HOP 1 ===
Start at: React Documentation
https://react.dev/
Extract core claims and references.
=== HOP 2 ===
Follow references to official docs, RFCs, or specs.
Extract primary-source evidence.
=== HOP 3 ===
Check community discussions for real-world issues.
Extract failure modes and workarounds.
=== SYNTHESIS =... | web-research-coding-5m-1.1.0 | |
1a37cfd70068d3a05efd7784 | test | tradeoff_analysis | gitlab | https://gitlab.com/panoramax/clients/web-viewer | panoramax/clients/web-viewer | admin_panel | sql | api_design | Perform a deep multi-layer analysis of api_design 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": "panoramax/clients/web-viewer", "source_url": "https://gitlab.com/panoramax/clients/web-viewer... | === 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 'panoramax/clients/web-viewer' as a source anchor and identify relevant APIs, dependencies... | web-research-coding-5m-1.1.0 | |
d6612e9d29b979ec7d025867 | test | developer_experience | codeberg | https://codeberg.org/veroxis/_cargo-index | veroxis/_cargo-index | search_interface | go | computer_vision | Perform a deep developer-experience analysis for a go project involving computer_vision. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "veroxis/_cargo-index", "source_url": "https://codeberg.org/veroxis/_cargo-index", "source_typ... | === 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 | |
db4e0078b9057849d1f3c581 | test | component_design | pypi | https://pypi.org/project/flask/ | flask | portfolio | cpp | typescript | Design reusable UI components for a portfolio. | {"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": "... | Define component responsibilities, props/data contracts, variants, states, composition rules, accessibility, testing, and documentation. | web-research-coding-5m-1.1.0 | |
e00d5ca6252e7eb8e5d74a82 | test | security_analysis | web_docs | https://kubernetes.io/docs/ | Kubernetes Documentation | finance | python | nodejs | Perform a deep multi-layer analysis of nodejs for a finance 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": "Kubernetes Documentation", "source_url": "https://kubernetes.io/docs/", "source_type": "docum... | === 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 'Kubernetes Documentation' as a source anchor and identify relevant APIs, dependencies, versions, ... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
31e5f6e27b933797ea4c6123 | test | evidence_extraction | pypi | https://pypi.org/project/uvicorn/ | uvicorn | dashboard | dart | typescript | Extract verifiable evidence about typescript from the given source. | {"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... | === SOURCE ===
uvicorn
https://pypi.org/project/uvicorn/
=== 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 s... | web-research-coding-5m-1.1.0 | |
2192d6a4f802b145eb842be7 | test | code_explanation | gitlab | https://gitlab.com/gitlab-com/www-gitlab-com | gitlab-com/www-gitlab-com | marketplace | dart | docker | Explain a dart implementation related to docker. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "gitlab-com/www-gitlab-com", "source_url": "https://gitlab.com/gitlab-com/www-gitlab-com", "so... | Explain inputs, outputs, control flow, algorithms, complexity, edge cases, errors, and maintainability. | web-research-coding-5m-1.1.0 | |
3b636f8d9bd8b485d3ad8137 | test | cli_experience | huggingface | https://huggingface.co/datasets/mlabonne/Evol-Instruct-Python-26k | mlabonne/Evol-Instruct-Python-26k | dashboard | rust | postgresql | Perform a deep developer-experience analysis for a rust project involving postgresql. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "mlabonne/Evol-Instruct-Python-26k", "source_url": "https://huggingface.co/datasets/mlabonne/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 | |
a4f5e28f0bd4b204b26cf0a4 | test | debugging | huggingface | https://huggingface.co/datasets/DeveloperBishal/LLama3.2_Fine-Tune_web-development | DeveloperBishal/LLama3.2_Fine-Tune_web-development | admin_panel | dart | testing | Create a realistic dart debugging problem involving testing. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "DeveloperBishal/LLama3.2_Fine-Tune_web-development", "source_url": "https://huggingface.co/da... | Provide symptoms, reproduction strategy, diagnostic steps, root-cause analysis, minimal fix, and regression coverage. | web-research-coding-5m-1.1.0 | |
dc4bed37ca6ef69e51054e74 | test | system_analysis | huggingface | https://huggingface.co/datasets/puttatidam/software-documentation-vie-bitextmining | puttatidam/software-documentation-vie-bitextmining | blog | css | open_source | Perform a deep multi-layer analysis of open_source for a blog 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": "puttatidam/software-documentation-vie-bitextmining", "source_url": "https://huggingface.co/da... | === 1. PROBLEM ===
Define the exact problem involving open_source. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around open_source. Use 'puttatidam/software-documentation-vie-bitextmining' as a source anchor and identify rel... | web-research-coding-5m-1.1.0 | |
6525354b6a51b54f2bedb512 | test | tradeoff_analysis | stackexchange | https://stackoverflow.com/questions/3042437/how-can-i-change-the-commit-author-for-a-single-commit | How can I change the commit author for a single commit? | community | dart | mongodb | Perform a deep multi-layer analysis of mongodb for a community 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": "How can I change the commit author for a single commit?", "source_url": "https://stackoverflo... | === 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 'How can I change the commit author for a single commit?' as a source anchor and identify releva... | web-research-coding-5m-1.1.0 | |
5a9cea71702272f1b937efae | test | ux_analysis | pypi | https://pypi.org/project/requests/ | requests | productivity | ruby | data_engineering | Perform a deep multi-layer analysis of data_engineering for a productivity using ruby. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "requests", "source_url": "https://pypi.org/project/requests/", "source_type": "package", "top... | === 1. PROBLEM ===
Define the exact problem involving data_engineering. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around data_engineering. Use 'requests' as a source anchor and identify relevant APIs, dependencies, versio... | web-research-coding-5m-1.1.0 | |
0629fbc4d479c6c1f8b1cf61 | test | deployment_experience | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API | Fetch API | documentation | swift | backend | Perform a deep developer-experience analysis for a swift project involving backend. | {"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 | |
4e27cca4bb4a918bf8869cbd | test | web_search_query | huggingface | https://huggingface.co/datasets/HuggingFaceH4/testing_codealpaca_small | HuggingFaceH4/testing_codealpaca_small | search_interface | java | sql | Write an effective web search query to research the topic: sql. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "HuggingFaceH4/testing_codealpaca_small", "source_url": "https://huggingface.co/datasets/Huggi... | === QUERY ===
sql best practices documentation tutorial
=== INTENT ===
Find authoritative documentation, tutorials, and real-world examples related to the topic.
=== KEYWORDS ===
- sql
- documentation
- best practices
- examples
- reference
=== SOURCE PREFERENCE ===
Prefer official documentation, well-maintained rep... | web-research-coding-5m-1.1.0 | |
63d5236b40c789925d1737e3 | test | seo_fix | gitlab | https://gitlab.com/bvobart/python-ml-analysis | bvobart/python-ml-analysis | ecommerce | typescript | nodejs | Create an SEO improvement plan for a ecommerce about nodejs. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "bvobart/python-ml-analysis", "source_url": "https://gitlab.com/bvobart/python-ml-analysis", "... | Cover titles, descriptions, headings, canonical URLs, structured data, internal links, crawlability, and performance. | web-research-coding-5m-1.1.0 | |
1b31947146126496e0e4313c | test | tradeoff_analysis | huggingface | https://huggingface.co/datasets/GudduButt/schemaforge-ai-and-machine-learning-11 | GudduButt/schemaforge-ai-and-machine-learning-11 | documentation | typescript | nextjs | Perform a deep multi-layer analysis of nextjs for a documentation 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": "GudduButt/schemaforge-ai-and-machine-learning-11", "source_url": "https://huggingface.co/data... | === 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 'GudduButt/schemaforge-ai-and-machine-learning-11' as a source anchor and identify relevant APIs, ... | web-research-coding-5m-1.1.0 | |
10244614d49182f4a188aaa6 | test | unit_testing | codeberg | https://codeberg.org/UI-Programming-23-24/01-Web-basic-and-git-practical-Brandon-Cameron | UI-Programming-23-24/01-Web-basic-and-git-practical-Brandon-Cameron | education | shell | devops | Create a unit-testing strategy for shell code involving devops. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "UI-Programming-23-24/01-Web-basic-and-git-practical-Brandon-Cameron", "source_url": "https://... | Cover normal cases, edge cases, invalid inputs, failure modes, mocks, and regression tests. | web-research-coding-5m-1.1.0 | |
323460cbcce0b126cf8db08e | test | dx_analysis | gitlab | https://gitlab.com/gitmate/open-source/IGitt | gitmate/open-source/IGitt | marketplace | 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": "gitmate/open-source/IGitt", "source_url": "https://gitlab.com/gitmate/open-source/IGitt", "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 | |
d3c45fa58161ffe3c7ea1f5f | test | architecture_analysis | web_docs | https://docs.djangoproject.com/ | Django Documentation | search_interface | scala | javascript | Perform a deep multi-layer analysis of javascript for a search_interface using scala. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Django Documentation", "source_url": "https://docs.djangoproject.com/", "source_type": "docum... | === 1. PROBLEM ===
Define the exact problem involving javascript. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around javascript. Use 'Django Documentation' as a source anchor and identify relevant APIs, dependencies, versio... | web-research-coding-5m-1.1.0 | |
16a47bf62a80d51fbd65afda | test | form_ui | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model | DOM | marketplace | css | authorization | Design an accessible form for authorization. | {"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 labels, validation, clear errors, keyboard navigation, appropriate autocomplete, and accessible status messaging. | web-research-coding-5m-1.1.0 | |
ef58c6a3923d8d9ee800d9b8 | test | fact_verification | mdn | https://developer.mozilla.org/en-US/docs/Web/JavaScript | JavaScript | admin_panel | go | computer_vision | Verify a technical claim about computer_vision. | {"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... | === CLAIM ===
A common claim about computer_vision.
=== 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 / conte... | 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.