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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
e3da496f577d914cda6a22b7 | test | react_generation | gitlab | https://gitlab.com/illwill/skiptracer | illwill/skiptracer | documentation | java | authorization | Design React components for a documentation. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "illwill/skiptracer", "source_url": "https://gitlab.com/illwill/skiptracer", "source_type": "r... | 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 |
e1cae6beea9f38727e753cd7 | test | product_analysis | huggingface | https://huggingface.co/datasets/jan-hq/multiturn_programming_binarized | jan-hq/multiturn_programming_binarized | community | cpp | serverless | Perform a deep multi-layer analysis of serverless for a community using cpp. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "jan-hq/multiturn_programming_binarized", "source_url": "https://huggingface.co/datasets/jan-h... | === 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 'jan-hq/multiturn_programming_binarized' as a source anchor and identify relevant APIs, de... | web-research-coding-5m-1.1.0 | |
a33308f1137547775e8cc71e | test | javascript_generation | gitlab | https://gitlab.com/soapbox-pub/nostrify | soapbox-pub/nostrify | landing_page | javascript | nlp | Implement JavaScript interactions for a landing_page. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "soapbox-pub/nostrify", "source_url": "https://gitlab.com/soapbox-pub/nostrify", "source_type"... | 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 |
32554c009845eb3aac511c47 | test | ux_design | github | https://github.com/parcel-bundler/parcel | parcel-bundler/parcel | saas | dart | deep_learning | Design the complete UX flow of a saas for deep_learning. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "parcel-bundler/parcel", "source_url": "https://github.com/parcel-bundler/parcel", "source_typ... | Map user goals, entry points, navigation, primary actions, feedback, loading states, empty states, errors, recovery paths, and completion. | web-research-coding-5m-1.1.0 | |
3999a012631282b4a9d5f552 | test | web_search_query | stackexchange | https://stackoverflow.com/questions/13066532/how-can-i-uninstall-npm-modules-in-node-js | How can I uninstall npm modules in Node.js? | finance | dart | observability | Write an effective web search query to research the topic: observability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How can I uninstall npm modules in Node.js?", "source_url": "https://stackoverflow.com/questi... | === QUERY ===
observability best practices documentation tutorial
=== INTENT ===
Find authoritative documentation, tutorials, and real-world examples related to the topic.
=== KEYWORDS ===
- observability
- documentation
- best practices
- examples
- reference
=== SOURCE PREFERENCE ===
Prefer official documentation,... | web-research-coding-5m-1.1.0 | |
543d4d291f83f09ea288102d | test | tradeoff_analysis | codeberg | https://codeberg.org/CryptoJones/120xSocrates | CryptoJones/120xSocrates | search_interface | dart | debugging | Perform a deep multi-layer analysis of debugging for a search_interface 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": "CryptoJones/120xSocrates", "source_url": "https://codeberg.org/CryptoJones/120xSocrates", "so... | === 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 'CryptoJones/120xSocrates' as a source anchor and identify relevant APIs, dependencies, vers... | web-research-coding-5m-1.1.0 | |
6baa26e7a3e3cc83426c0da7 | test | ui_design | web_docs | https://docs.djangoproject.com/ | Django Documentation | community | scala | ci_cd | Design a production-quality UI for a community focused on ci_cd. | {"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... | Define layout, typography, spacing, hierarchy, components, states, responsive behavior, and accessibility. | web-research-coding-5m-1.1.0 | |
709828dd17ab311b1c7c7e74 | test | refactoring_security | mdn | https://developer.mozilla.org/en-US/docs/Web/Performance | Performance | dashboard | dart | distributed_systems | Refactor a dart system related to distributed_systems. Focus on refactoring security. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Performance", "source_url": "https://developer.mozilla.org/en-US/docs/Web/Performance", "sour... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Strengthen validation, trust boundaries, authorization, and secret handling.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Ident... | web-research-coding-5m-1.1.0 | |
a88ef36bfada36d6ba343f84 | test | tradeoff_analysis | web_docs | https://www.postgresql.org/docs/ | PostgreSQL Documentation | developer_tool | shell | mongodb | Perform a deep multi-layer analysis of mongodb for a developer_tool 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": "PostgreSQL Documentation", "source_url": "https://www.postgresql.org/docs/", "source_type": "... | === 1. PROBLEM ===
Define the exact problem involving mongodb. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around mongodb. Use 'PostgreSQL Documentation' as a source anchor and identify relevant APIs, dependencies, versions... | web-research-coding-5m-1.1.0 | |
45789dae2c66dfbbfb4f6963 | test | security_analysis | stackexchange | https://stackoverflow.com/questions/3133243/how-do-i-get-the-path-to-the-current-script-with-node-js | How do I get the path to the current script with Node.js? | marketplace | dart | caching | Perform a deep multi-layer analysis of caching for a marketplace 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 do I get the path to the current script with Node.js?", "source_url": "https://stackoverf... | === 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 'How do I get the path to the current script with Node.js?' as a source anchor and identify rele... | web-research-coding-5m-1.1.0 | |
8835eda0ec288731741246ce | test | system_analysis | stackexchange | https://stackoverflow.com/questions/43034960/many-to-one-and-many-to-many-lstm-examples-in-keras | Many to one and many to many LSTM examples in Keras | admin_panel | ruby | cloud | Perform a deep multi-layer analysis of cloud for a admin_panel 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": "Many to one and many to many LSTM examples in Keras", "source_url": "https://stackoverflow.co... | === 1. PROBLEM ===
Define the exact problem involving cloud. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around cloud. Use 'Many to one and many to many LSTM examples in Keras' as a source anchor and identify relevant APIs,... | web-research-coding-5m-1.1.0 | |
fa57696ad70beef65886aa97 | test | refactoring_security | npm | https://www.npmjs.com/package/vite | vite | productivity | python | database | Refactor a python system related to database. Focus on refactoring security. | {"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":... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Strengthen validation, trust boundaries, authorization, and secret handling.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Ident... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
f50361a9fba3319926066e7d | test | code_review | huggingface | https://huggingface.co/datasets/kloodia/javascript_200k | kloodia/javascript_200k | search_interface | typescript | algorithms | Perform a production code review of typescript code related to algorithms. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "kloodia/javascript_200k", "source_url": "https://huggingface.co/datasets/kloodia/javascript_2... | Review correctness, security, performance, readability, architecture, testing, maintainability, and error handling. | web-research-coding-5m-1.1.0 | |
c0f0a9c872b3b4dd1d34e48d | test | typescript_generation | gitlab | https://gitlab.com/rmnvgr/metadata-cleaner | rmnvgr/metadata-cleaner | saas | rust | postgresql | Implement TypeScript logic for a saas. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "rmnvgr/metadata-cleaner", "source_url": "https://gitlab.com/rmnvgr/metadata-cleaner", "source... | 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 |
dfc420087eb208df30237540 | test | deep_technical_analysis | huggingface | https://huggingface.co/datasets/Ujjwal-Tyagi/JavaScript-Code-Large | Ujjwal-Tyagi/JavaScript-Code-Large | productivity | scala | software_architecture | Perform a deep multi-layer analysis of software_architecture for a productivity 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": "Ujjwal-Tyagi/JavaScript-Code-Large", "source_url": "https://huggingface.co/datasets/Ujjwal-Ty... | === 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 'Ujjwal-Tyagi/JavaScript-Code-Large' as a source anchor and identify... | web-research-coding-5m-1.1.0 | |
ed62eea82ded554dd82b31a3 | test | fact_verification | huggingface | https://huggingface.co/datasets/ajibawa-2023/Python-Code-23k-ShareGPT | ajibawa-2023/Python-Code-23k-ShareGPT | productivity | html | docker | Verify a technical claim about docker. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "ajibawa-2023/Python-Code-23k-ShareGPT", "source_url": "https://huggingface.co/datasets/ajibaw... | === CLAIM ===
A common claim about docker.
=== 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-depend... | web-research-coding-5m-1.1.0 | |
487189d29e484bfafd8e4e20 | test | research_plan | huggingface | https://huggingface.co/datasets/puttatidam/software-documentation-vie-bitextmining | puttatidam/software-documentation-vie-bitextmining | search_interface | scala | frontend | Build a structured research plan to deeply understand frontend. | {"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... | === GOAL ===
Produce a reliable, current, and actionable understanding of frontend.
=== 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 w... | web-research-coding-5m-1.1.0 | |
88f81e54eb88f52a039137b4 | test | ui_design | github | https://github.com/justjavac/free-programming-books-zh_CN | justjavac/free-programming-books-zh_CN | search_interface | shell | developer_experience | Design a production-quality UI for a search_interface focused on developer_experience. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "justjavac/free-programming-books-zh_CN", "source_url": "https://github.com/justjavac/free-pro... | Define layout, typography, spacing, hierarchy, components, states, responsive behavior, and accessibility. | web-research-coding-5m-1.1.0 | |
87871327fc68b092068d4000 | test | landing_page | huggingface | https://huggingface.co/datasets/CM/codexglue_code2text_javascript | CM/codexglue_code2text_javascript | social_app | javascript | serverless | Design a landing page for a serverless product. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "CM/codexglue_code2text_javascript", "source_url": "https://huggingface.co/datasets/CM/codexgl... | Include hero, value proposition, features, CTA, FAQ, responsive behavior, SEO, accessibility, and analytics. | web-research-coding-5m-1.1.0 | |
03b0b744ce94461ae95a01c8 | test | refactoring_testability | huggingface | https://huggingface.co/datasets/codeparrot/apps | codeparrot/apps | saas | ruby | caching | Refactor a ruby system related to caching. Focus on refactoring testability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "codeparrot/apps", "source_url": "https://huggingface.co/datasets/codeparrot/apps", "source_ty... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Separate side effects and dependencies so behavior can be tested independently.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Id... | web-research-coding-5m-1.1.0 | |
719dfc653e9eab21666284f7 | test | root_cause_analysis | huggingface | https://huggingface.co/datasets/hasankursun/github-code-2025-language-split | hasankursun/github-code-2025-language-split | blog | swift | nextjs | Perform a deep multi-layer analysis of nextjs for a blog 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": "hasankursun/github-code-2025-language-split", "source_url": "https://huggingface.co/datasets/... | === 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 'hasankursun/github-code-2025-language-split' as a source anchor and identify relevant APIs, depen... | web-research-coding-5m-1.1.0 | |
79972c47cb4975a50df30b37 | test | tradeoff_analysis | huggingface | https://huggingface.co/datasets/artur-muratov/multilingual-speech-commands-15lang | artur-muratov/multilingual-speech-commands-15lang | portfolio | php | typescript | Perform a deep multi-layer analysis of typescript for a portfolio using php. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "artur-muratov/multilingual-speech-commands-15lang", "source_url": "https://huggingface.co/dat... | === 1. PROBLEM ===
Define the exact problem involving typescript. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around typescript. Use 'artur-muratov/multilingual-speech-commands-15lang' as a source anchor and identify releva... | web-research-coding-5m-1.1.0 | |
19386cf0629e2d0cd70fc154 | test | design_to_code | stackexchange | https://stackoverflow.com/questions/46677752/the-difference-between-requirex-and-import-x | The difference between "require(x)" and "import x" | education | go | nodejs | Translate a education design into maintainable go code. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "The difference between "require(x)" and "import x"", "source_url": "https... | Map design tokens to code, identify reusable components, preserve responsive behavior, implement accessible states, and avoid unnecessary one-off styling. | web-research-coding-5m-1.1.0 | |
3cddafc1e4afd53629738013 | test | evidence_extraction | mdn | https://developer.mozilla.org/en-US/docs/Web/JavaScript | JavaScript | documentation | python | authorization | Extract verifiable evidence about authorization from the given source. | {"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... | === SOURCE ===
JavaScript
https://developer.mozilla.org/en-US/docs/Web/JavaScript
=== 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 ... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
558e43079b992d0704f9f711 | test | refactoring_performance | mdn | https://developer.mozilla.org/en-US/docs/Web/HTML | HTML | documentation | cpp | security | Refactor a cpp system related to security. Focus on refactoring performance. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "HTML", "source_url": "https://developer.mozilla.org/en-US/docs/Web/HTML", "source_type": "doc... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Reduce unnecessary computation, allocations, I/O, and network requests.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify d... | web-research-coding-5m-1.1.0 | |
c01fb1bea1e7bd93ddefe725 | test | research_summary | web_docs | https://react.dev/ | React Documentation | admin_panel | typescript | typescript | Summarize the current state of knowledge about typescript. | {"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... | === OVERVIEW ===
typescript 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 ===
React Documentation... | web-research-coding-5m-1.1.0 | |
3357913131cd7a67daa4ae47 | test | system_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model | DOM | search_interface | scala | design_system | Perform a deep multi-layer analysis of design_system 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": "DOM", "source_url": "https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model",... | === 1. PROBLEM ===
Define the exact problem involving design_system. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around design_system. Use 'DOM' as a source anchor and identify relevant APIs, dependencies, versions, standar... | web-research-coding-5m-1.1.0 | |
3d890267319e6ad8560a641c | test | refactoring_maintainability | mdn | https://developer.mozilla.org/en-US/docs/Web/HTML | HTML | blog | sql | javascript | Refactor a sql system related to javascript. Focus on refactoring maintainability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "HTML", "source_url": "https://developer.mozilla.org/en-US/docs/Web/HTML", "source_type": "doc... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
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 | |
702d7314d350cc57f9b2c191 | test | seo_fix | npm | https://www.npmjs.com/package/webpack | webpack | saas | kotlin | docker | Create an SEO improvement plan for a saas about docker. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "webpack", "source_url": "https://www.npmjs.com/package/webpack", "source_type": "package", "t... | Cover titles, descriptions, headings, canonical URLs, structured data, internal links, crawlability, and performance. | web-research-coding-5m-1.1.0 | |
d36259bd669af2865fdb6b7a | test | design_consistency | web_docs | https://go.dev/doc/ | Go Documentation | search_interface | php | authorization | Audit design consistency across 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... | Check repeated patterns, component variants, spacing, typography, interaction states, terminology, and responsiveness. | web-research-coding-5m-1.1.0 | |
40f4939d35c0cfe016a557cc | test | security_review | huggingface | https://huggingface.co/datasets/WillHeld/paloma_programming_languages | WillHeld/paloma_programming_languages | marketplace | java | nodejs | Perform a security review of a marketplace application. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "WillHeld/paloma_programming_languages", "source_url": "https://huggingface.co/datasets/WillHe... | Review authentication, authorization, input validation, XSS, CSRF, injection risks, secrets, dependencies, security headers, and logging. | web-research-coding-5m-1.1.0 | |
f8bcd7ec402043b6a6b91654 | test | integration_testing | stackexchange | https://stackoverflow.com/questions/27928372/react-router-urls-dont-work-when-refreshing-or-writing-manually | React-router URLs don't work when refreshing or writing manually | community | css | nodejs | Design integration tests for a css system involving nodejs. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "React-router URLs don't work when refreshing or writing manually", "source_url": "https:/... | Test real component boundaries, persistence, configuration, external interfaces, errors, cleanup, and realistic workflows. | web-research-coding-5m-1.1.0 | |
ed259d76821a948002463c72 | test | refactoring_modularization | npm | https://www.npmjs.com/package/three | three | productivity | swift | open_source | Refactor a swift system related to open_source. Focus on refactoring modularization. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "three", "source_url": "https://www.npmjs.com/package/three", "source_type": "package", "topic... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
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 | |
2774703e0cf499a4f65c9dff | test | performance_fix | github | https://github.com/PaddlePaddle/Paddle | PaddlePaddle/Paddle | marketplace | shell | devops | Create a web-performance optimization plan for a marketplace. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "PaddlePaddle/Paddle", "source_url": "https://github.com/PaddlePaddle/Paddle", "source_type": ... | Measure first, then optimize bundle size, images, network requests, rendering, caching, and critical resources. | web-research-coding-5m-1.1.0 | |
cba28d39a4f3ab13bc25918a | test | accessibility_analysis | stackexchange | https://stackoverflow.com/questions/1628088/reset-local-repository-branch-to-be-just-like-remote-repository-head | Reset local repository branch to be just like remote repository HEAD | community | go | fullstack | Perform a deep multi-layer analysis of fullstack for a community 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": "Reset local repository branch to be just like remote repository HEAD", "source_url": "https:/... | === 1. PROBLEM ===
Define the exact problem involving fullstack. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around fullstack. Use 'Reset local repository branch to be just like remote repository HEAD' as a source anchor an... | web-research-coding-5m-1.1.0 | |
aca12fba238def1403b6d04a | test | api_developer_experience | huggingface | https://huggingface.co/datasets/ml6team/the-stack-smol-python | ml6team/the-stack-smol-python | saas | typescript | observability | Perform a deep developer-experience analysis for a typescript project involving observability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "ml6team/the-stack-smol-python", "source_url": "https://huggingface.co/datasets/ml6team/the-st... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
76f86055d15b50ffb7d7a6cc | test | refactoring_maintainability | npm | https://www.npmjs.com/package/hono | hono | developer_tool | go | testing | Refactor a go system related to testing. Focus on refactoring maintainability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "hono", "source_url": "https://www.npmjs.com/package/hono", "source_type": "package", "topic":... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Improve 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 | |
fa50b652014d212ab9407290 | test | refactoring_performance | mdn | https://developer.mozilla.org/en-US/docs/Web/JavaScript | JavaScript | search_interface | rust | authentication | Refactor a rust system related to authentication. Focus on refactoring performance. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "JavaScript", "source_url": "https://developer.mozilla.org/en-US/docs/Web/JavaScript", "source... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Reduce unnecessary computation, allocations, I/O, and network requests.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify d... | web-research-coding-5m-1.1.0 | |
2adb4302eb796b97eb4fa3c1 | test | security_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/JavaScript | JavaScript | landing_page | dart | database | Perform a deep multi-layer analysis of database for a landing_page 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": "JavaScript", "source_url": "https://developer.mozilla.org/en-US/docs/Web/JavaScript", "source... | === 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 'JavaScript' as a source anchor and identify relevant APIs, dependencies, versions, standards,... | web-research-coding-5m-1.1.0 | |
c893b9f673b6bfc8f06803d0 | test | design_review | codeberg | https://codeberg.org/New_Wave_Liberty/_cargo-index | New_Wave_Liberty/_cargo-index | documentation | shell | machine_learning | Perform a professional design review of a documentation. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "New_Wave_Liberty/_cargo-index", "source_url": "https://codeberg.org/New_Wave_Liberty/_cargo-i... | Review hierarchy, consistency, responsiveness, accessibility, interaction design, content clarity, and implementation feasibility. | web-research-coding-5m-1.1.0 | |
3d3a45daa3fc7c7966033b82 | test | developer_experience | npm | https://www.npmjs.com/package/vitest | vitest | ecommerce | ruby | web_performance | Perform a deep developer-experience analysis for a ruby project involving web_performance. | {"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... | === 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 | |
75dabd5f6e38a490bdb24816 | test | accessibility_analysis | github | https://github.com/vercel/next.js | vercel/next.js | blog | go | mongodb | Perform a deep multi-layer analysis of mongodb for a blog 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": "vercel/next.js", "source_url": "https://github.com/vercel/next.js", "source_type": "repositor... | === 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 'vercel/next.js' as a source anchor and identify relevant APIs, dependencies, versions, standard... | web-research-coding-5m-1.1.0 | |
a27fb75db4d2f310117b9bb1 | test | algorithm_design | stackexchange | https://stackoverflow.com/questions/3010840/how-to-loop-through-the-items-of-an-array-in-javascript | How to loop through the items of an array in JavaScript? | landing_page | php | html | Design a php algorithm for a html problem. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How to loop through the items of an array in JavaScript?", "source_url": "https://stackoverfl... | State assumptions, algorithm, complexity, edge cases, correctness reasoning, and testing strategy. | web-research-coding-5m-1.1.0 | |
fe3da4f34befdd3044e167d3 | test | dashboard | stackexchange | https://stackoverflow.com/questions/42790602/how-do-i-check-whether-an-array-contains-a-string-in-typescript | How do I check whether an array contains a string in TypeScript? | analytics | ruby | computer_vision | Design a production dashboard for computer_vision. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How do I check whether an array contains a string in TypeScript?", "source_url": "https://sta... | Include navigation, KPIs, tables/charts, filters, loading states, empty states, errors, and responsive behavior. | web-research-coding-5m-1.1.0 | |
fc279c94bcd89929475222b2 | test | build_experience | web_docs | https://www.postgresql.org/docs/ | PostgreSQL Documentation | community | sql | kubernetes | Perform a deep developer-experience analysis for a sql project involving kubernetes. | {"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. 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 | |
b90b84329534aa6e3767906a | test | maintainability_analysis | pypi | https://pypi.org/project/typer/ | typer | marketplace | html | microservices | Perform a deep multi-layer analysis of microservices for a marketplace 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": "typer", "source_url": "https://pypi.org/project/typer/", "source_type": "package", "topic": "... | === 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 'typer' as a source anchor and identify relevant APIs, dependencies, versions, stand... | web-research-coding-5m-1.1.0 | |
0705a32166ec3c83e6ebad39 | test | security_analysis | stackexchange | https://stackoverflow.com/questions/15890958/how-to-install-a-previous-exact-version-of-a-npm-package | How to install a previous exact version of a NPM package? | marketplace | go | developer_experience | Perform a deep multi-layer analysis of developer_experience for a marketplace 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": "How to install a previous exact version of a NPM package?", "source_url": "https://stackoverf... | === 1. PROBLEM ===
Define the exact problem involving developer_experience. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around developer_experience. Use 'How to install a previous exact version of a NPM package?' as a sourc... | web-research-coding-5m-1.1.0 | |
88e40f184ad0e9dd34d55b7c | test | repository_dependency_analysis | web_docs | https://git-scm.com/doc | Git Documentation | marketplace | sql | algorithms | Perform a deep multi-layer analysis of algorithms for a marketplace using sql. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Git Documentation", "source_url": "https://git-scm.com/doc", "source_type": "documentation", ... | === 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 'Git Documentation' as a source anchor and identify relevant APIs, dependencies, versions,... | web-research-coding-5m-1.1.0 | |
526fa529ca9b20f638d6c83b | test | design_tokens | web_docs | https://kubernetes.io/docs/ | Kubernetes Documentation | portfolio | kotlin | serverless | Create design tokens for a portfolio. | {"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... | Define reusable tokens for typography, spacing, radii, sizing, elevation, interaction states, and responsive behavior. | web-research-coding-5m-1.1.0 | |
a909d216cf41c7b695e0829d | test | design_accessibility | stackexchange | https://stackoverflow.com/questions/15292278/how-do-i-remove-an-array-item-in-typescript | How do I remove an array item in TypeScript? | social_app | rust | typescript | Audit accessibility for a social_app. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How do I remove an array item in TypeScript?", "source_url": "https://stackoverflow.com/quest... | Check semantic structure, keyboard navigation, focus visibility, accessible names, labels, errors, contrast, and screen-reader behavior. | web-research-coding-5m-1.1.0 | |
90422ab16320592861754025 | test | api_developer_experience | huggingface | https://huggingface.co/datasets/HuggingFaceH4/CodeAlpaca_20K | HuggingFaceH4/CodeAlpaca_20K | portfolio | go | database | Perform a deep developer-experience analysis for a go project involving database. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "HuggingFaceH4/CodeAlpaca_20K", "source_url": "https://huggingface.co/datasets/HuggingFaceH4/C... | === 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 | |
16264e4e0798fe20517e3c5f | test | ui_design | codeberg | https://codeberg.org/pyaephyohein/_cargo-index | pyaephyohein/_cargo-index | admin_panel | c | debugging | Design a production-quality UI for a admin_panel focused on debugging. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "pyaephyohein/_cargo-index", "source_url": "https://codeberg.org/pyaephyohein/_cargo-index", "... | Define layout, typography, spacing, hierarchy, components, states, responsive behavior, and accessibility. | web-research-coding-5m-1.1.0 | |
98e011f2a3ce239ca66e8b8e | test | developer_experience | stackexchange | https://stackoverflow.com/questions/5064928/difference-between-classification-and-clustering-in-data-mining | Difference between classification and clustering in data mining? | admin_panel | 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": "Difference between classification and clustering in data mining?", "source_url": "https://sta... | === 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 | |
3bffdda471fda691c70a7820 | test | risk_analysis | stackexchange | https://stackoverflow.com/questions/18875674/whats-the-difference-between-dependencies-devdependencies-and-peerdependencie | What's the difference between dependencies, devDependencies, and peerDependencies in NPM package.json file? | finance | dart | observability | Perform a deep multi-layer analysis of observability for a finance 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": "What's the difference between dependencies, devDependencies, and peerDependencies in NPM ... | === 1. PROBLEM ===
Define the exact problem involving observability. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around observability. Use 'What's the difference between dependencies, devDependencies, and peerDependenci... | web-research-coding-5m-1.1.0 | |
1b35f1f71486a8024ac308c2 | test | dependency_management_experience | web_docs | https://go.dev/doc/ | Go Documentation | community | javascript | authentication | Perform a deep developer-experience analysis for a javascript project involving authentication. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Go Documentation", "source_url": "https://go.dev/doc/", "source_type": "documentation", "topi... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
5ceb1e75bf2d108f9a02b776 | test | refactoring_architecture | codeberg | https://codeberg.org/ldilley/adventofcode | ldilley/adventofcode | admin_panel | typescript | deep_learning | Refactor a typescript system related to deep_learning. Focus on refactoring architecture. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "ldilley/adventofcode", "source_url": "https://codeberg.org/ldilley/adventofcode", "source_typ... | === 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 | |
1b64b9405be7e773e9cf3a1f | test | cli_experience | huggingface | https://huggingface.co/datasets/analytics-agents-uncertainty/da-code-evaluation-results | analytics-agents-uncertainty/da-code-evaluation-results | marketplace | rust | documentation | Perform a deep developer-experience analysis for a rust project involving documentation. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "analytics-agents-uncertainty/da-code-evaluation-results", "source_url": "https://huggingface.... | === 1. 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 | |
3abb5aa597b7233e482f0c32 | test | research_plan | codeberg | https://codeberg.org/taniki/11d.im | taniki/11d.im | dashboard | sql | user_experience | Build a structured research plan to deeply understand user_experience. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "taniki/11d.im", "source_url": "https://codeberg.org/taniki/11d.im", "source_type": "repositor... | === GOAL ===
Produce a reliable, current, and actionable understanding of user_experience.
=== 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 | |
84dd26a0f4e39dac72fbc9e1 | test | cli_experience | codeberg | https://codeberg.org/UI-Programming-23-24/01-Web-basics-and-git-Dylan-Crimmings | UI-Programming-23-24/01-Web-basics-and-git-Dylan-Crimmings | finance | go | backend | Perform a deep developer-experience analysis for a go project involving backend. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "UI-Programming-23-24/01-Web-basics-and-git-Dylan-Crimmings", "source_url": "https://codeberg.... | === 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 | |
c321de29a16c00948737f821 | test | unit_testing | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API | Fetch API | admin_panel | typescript | algorithms | Create a unit-testing strategy for typescript code involving algorithms. | {"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... | Cover normal cases, edge cases, invalid inputs, failure modes, mocks, and regression tests. | web-research-coding-5m-1.1.0 | |
3576539d8c4106fb2b4c03dc | test | react_generation | npm | https://www.npmjs.com/package/svelte | svelte | finance | css | open_source | Design React components for a finance. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "svelte", "source_url": "https://www.npmjs.com/package/svelte", "source_type": "package", "top... | 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 |
622c171d3554f501548e7a85 | test | nextjs_generation | gitlab | https://gitlab.com/woob/woob | woob/woob | marketplace | ruby | database | Design a Next.js architecture for a marketplace. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "woob/woob", "source_url": "https://gitlab.com/woob/woob", "source_type": "repository", "topic... | Specify routing, server/client boundaries, data fetching, caching, metadata, errors, and deployment. | export default function Page() {
return (
<main>
<h1>Application</h1>
<p>Production-ready page structure.</p>
</main>
);
} | web-research-coding-5m-1.1.0 |
8badd63f1b555b522c1bcd15 | test | web_search_query | huggingface | https://huggingface.co/datasets/PatrickHaller/the-stack-python-1M | PatrickHaller/the-stack-python-1M | dashboard | javascript | react | Write an effective web search query to research the topic: react. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "PatrickHaller/the-stack-python-1M", "source_url": "https://huggingface.co/datasets/PatrickHal... | === QUERY ===
react best practices documentation tutorial
=== INTENT ===
Find authoritative documentation, tutorials, and real-world examples related to the topic.
=== KEYWORDS ===
- react
- documentation
- best practices
- examples
- reference
=== SOURCE PREFERENCE ===
Prefer official documentation, well-maintained... | web-research-coding-5m-1.1.0 | |
362192d9953987cfd4b6bdd5 | test | refactoring_performance | web_docs | https://www.typescriptlang.org/docs/ | TypeScript Documentation | community | javascript | testing | Refactor a javascript system related to testing. Focus on refactoring performance. | {"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... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Reduce unnecessary computation, allocations, I/O, and network requests.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify d... | web-research-coding-5m-1.1.0 | |
56721f088aa940ca52f49c12 | test | web_search_query | huggingface | https://huggingface.co/datasets/Reynard1ng/Graph_Machine_Learning_Homework_Datasets | Reynard1ng/Graph_Machine_Learning_Homework_Datasets | social_app | typescript | observability | Write an effective web search query to research the topic: observability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Reynard1ng/Graph_Machine_Learning_Homework_Datasets", "source_url": "https://huggingface.co/d... | === QUERY ===
observability best practices documentation tutorial
=== INTENT ===
Find authoritative documentation, tutorials, and real-world examples related to the topic.
=== KEYWORDS ===
- observability
- documentation
- best practices
- examples
- reference
=== SOURCE PREFERENCE ===
Prefer official documentation,... | web-research-coding-5m-1.1.0 | |
672924d63a364ad9dcd069fe | test | build_experience | pypi | https://pypi.org/project/flask/ | flask | education | javascript | observability | Perform a deep developer-experience analysis for a javascript project involving observability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "flask", "source_url": "https://pypi.org/project/flask/", "source_type": "package", "topic": "... | === 1. 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 | |
58508c00d1c2c60992762660 | test | refactoring_maintainability | npm | https://www.npmjs.com/package/hono | hono | community | c | graphql | Refactor a c system related to graphql. Focus on refactoring maintainability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "hono", "source_url": "https://www.npmjs.com/package/hono", "source_type": "package", "topic":... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Improve 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 | |
bf2aced03d50639672ae8d18 | test | html_generation | codeberg | https://codeberg.org/ccoenen/Advent-of-Code-2021-JavaScript | ccoenen/Advent-of-Code-2021-JavaScript | search_interface | c | serverless | Create semantic HTML for a search_interface about serverless. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "ccoenen/Advent-of-Code-2021-JavaScript", "source_url": "https://codeberg.org/ccoenen/Advent-o... | 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 |
3676ec2571ea31f656bc4c5f | test | api_developer_experience | npm | https://www.npmjs.com/package/hono | hono | portfolio | ruby | frontend | Perform a deep developer-experience analysis for a ruby project involving frontend. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "hono", "source_url": "https://www.npmjs.com/package/hono", "source_type": "package", "topic":... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
6e2bd972872aa6d8803c54e9 | test | search_query_rewrite | pypi | https://pypi.org/project/streamlit/ | streamlit | blog | python | caching | Rewrite and improve a vague search query about caching 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": "streamlit", "source_url": "https://pypi.org/project/streamlit/", "source_type": "package", "t... | === ORIGINAL (VAGUE) ===
how to do caching
=== REWRITTEN QUERIES ===
1. caching official documentation guide
2. caching production best practices 2025
3. caching common pitfalls and solutions
4. caching architecture patterns with examples
=== RATIONALE ===
Add intent (learn / implement / debug), specificity (version,... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
0de2f6136aeca03075497b87 | test | design_tokens | gitlab | https://gitlab.com/SaikoJosh/safe-env-vars | SaikoJosh/safe-env-vars | admin_panel | python | data_engineering | Create design tokens for a admin_panel. | {"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... | Define reusable tokens for typography, spacing, radii, sizing, elevation, interaction states, and responsive behavior. | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
301b783ea0cc08ec081b05a8 | test | ux_analysis | gitlab | https://gitlab.com/govbr-ds/bibliotecas/javascript/govbr-ds-core | govbr-ds/bibliotecas/javascript/govbr-ds-core | saas | php | rest_api | Perform a deep multi-layer analysis of rest_api for a saas using php. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "govbr-ds/bibliotecas/javascript/govbr-ds-core", "source_url": "https://gitlab.com/govbr-ds/bi... | === 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 'govbr-ds/bibliotecas/javascript/govbr-ds-core' as a source anchor and identify relevant APIs,... | web-research-coding-5m-1.1.0 | |
f1c499d9c9cac49df7e74d3e | test | responsive_website | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model | DOM | landing_page | php | developer_experience | Design a complete responsive landing_page for developer_experience. | {"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",... | Cover mobile, tablet, and desktop layouts, semantic structure, responsive components, accessibility, performance, and UX. | web-research-coding-5m-1.1.0 | |
35dbd56dd353e8903b01a005 | test | react_generation | npm | https://www.npmjs.com/package/rollup | rollup | ecommerce | scala | developer_experience | Design React components for a ecommerce. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "rollup", "source_url": "https://www.npmjs.com/package/rollup", "source_type": "package", "top... | 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 |
92447205bdac95741b6b47a3 | test | design_components | web_docs | https://git-scm.com/doc | Git Documentation | saas | kotlin | cloud | Create a component architecture for a saas. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Git Documentation", "source_url": "https://git-scm.com/doc", "source_type": "documentation", ... | Define primitive components, composite components, variants, states, composition rules, and accessibility contracts. | web-research-coding-5m-1.1.0 | |
f7f8ac2b968d8f873802ae2b | test | web_search_query | npm | https://www.npmjs.com/package/hono | hono | developer_tool | dart | css | Write an effective web search query to research the topic: css. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "hono", "source_url": "https://www.npmjs.com/package/hono", "source_type": "package", "topic":... | === QUERY ===
css best practices documentation tutorial
=== INTENT ===
Find authoritative documentation, tutorials, and real-world examples related to the topic.
=== KEYWORDS ===
- css
- documentation
- best practices
- examples
- reference
=== SOURCE PREFERENCE ===
Prefer official documentation, well-maintained rep... | web-research-coding-5m-1.1.0 | |
d30802f40453e4b35afa12a5 | test | repository_understanding | huggingface | https://huggingface.co/datasets/nvidia/Nemotron-Competitive-Programming-v1 | nvidia/Nemotron-Competitive-Programming-v1 | admin_panel | java | graphql | Perform a deep multi-layer analysis of graphql for a admin_panel using java. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "nvidia/Nemotron-Competitive-Programming-v1", "source_url": "https://huggingface.co/datasets/n... | === 1. PROBLEM ===
Define the exact problem involving graphql. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around graphql. Use 'nvidia/Nemotron-Competitive-Programming-v1' as a source anchor and identify relevant APIs, depe... | web-research-coding-5m-1.1.0 | |
1317e676718c04d7ac06d756 | test | evidence_extraction | gitlab | https://gitlab.com/ase/ase | ase/ase | analytics | css | nextjs | Extract verifiable evidence about nextjs from the given source. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "ase/ase", "source_url": "https://gitlab.com/ase/ase", "source_type": "repository", "topic": "... | === SOURCE ===
ase/ase
https://gitlab.com/ase/ase
=== 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 stated?
... | web-research-coding-5m-1.1.0 | |
96dc3ab47012b5a3c9150acf | test | repository_documentation | pypi | https://pypi.org/project/scrapy/ | scrapy | documentation | typescript | ci_cd | Perform a deep multi-layer analysis of ci_cd 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": "scrapy", "source_url": "https://pypi.org/project/scrapy/", "source_type": "package", "topic":... | === 1. PROBLEM ===
Define the exact problem involving ci_cd. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around ci_cd. Use 'scrapy' as a source anchor and identify relevant APIs, dependencies, versions, standards, and techn... | web-research-coding-5m-1.1.0 | |
8364639c1809dc6dc34422ac | test | root_cause_analysis | web_docs | https://www.postgresql.org/docs/ | PostgreSQL Documentation | landing_page | go | javascript | Perform a deep multi-layer analysis of javascript for a landing_page 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": "PostgreSQL Documentation", "source_url": "https://www.postgresql.org/docs/", "source_type": "... | === 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 'PostgreSQL Documentation' as a source anchor and identify relevant APIs, dependencies, ve... | web-research-coding-5m-1.1.0 | |
0902a98dea1689b1797be0bb | test | performance_fix | mdn | https://developer.mozilla.org/en-US/docs/Web/HTML | HTML | social_app | python | postgresql | Create a web-performance optimization plan for a social_app. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "HTML", "source_url": "https://developer.mozilla.org/en-US/docs/Web/HTML", "source_type": "doc... | Measure first, then optimize bundle size, images, network requests, rendering, caching, and critical resources. | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
4e87cc30aaf8628241e2e2b1 | test | refactoring_api | web_docs | https://go.dev/doc/ | Go Documentation | blog | javascript | authorization | Refactor a javascript system related to authorization. Focus on refactoring api. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Go Documentation", "source_url": "https://go.dev/doc/", "source_type": "documentation", "topi... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Improve API contracts, validation, error semantics, compatibility, and versioning.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4.... | web-research-coding-5m-1.1.0 | |
c89527a2a6978bd664a5b888 | test | accessibility_analysis | npm | https://www.npmjs.com/package/tailwindcss | tailwindcss | ecommerce | ruby | database | Perform a deep multi-layer analysis of database for a ecommerce 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": "tailwindcss", "source_url": "https://www.npmjs.com/package/tailwindcss", "source_type": "pack... | === 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 'tailwindcss' as a source anchor and identify relevant APIs, dependencies, versions, standards... | web-research-coding-5m-1.1.0 | |
2c09e4c5a31526b3b33e1750 | test | developer_experience | npm | https://www.npmjs.com/package/eslint | eslint | dashboard | css | mongodb | Perform a deep developer-experience analysis for a css project involving mongodb. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "eslint", "source_url": "https://www.npmjs.com/package/eslint", "source_type": "package", "top... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
311f226bd7d69aa33d8ff6b6 | test | interaction_design | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API | Fetch API | admin_panel | rust | docker | Design interaction states for a admin_panel. | {"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... | Specify default, hover, focus, active, disabled, loading, success, error, and empty states. | web-research-coding-5m-1.1.0 | |
05bd8a24d776d324a0d2f055 | test | scalability_analysis | npm | https://www.npmjs.com/package/vite | vite | productivity | typescript | authentication | Perform a deep multi-layer analysis of authentication for a productivity 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": "vite", "source_url": "https://www.npmjs.com/package/vite", "source_type": "package", "topic":... | === 1. PROBLEM ===
Define the exact problem involving authentication. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around authentication. Use 'vite' as a source anchor and identify relevant APIs, dependencies, versions, stan... | web-research-coding-5m-1.1.0 | |
c7b24a9aad698fb2cef0b9af | test | design_to_code | huggingface | https://huggingface.co/datasets/livecodebench/code_generation_lite | livecodebench/code_generation_lite | productivity | ruby | debugging | Translate a productivity design into maintainable ruby code. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "livecodebench/code_generation_lite", "source_url": "https://huggingface.co/datasets/livecodeb... | Map design tokens to code, identify reusable components, preserve responsive behavior, implement accessible states, and avoid unnecessary one-off styling. | web-research-coding-5m-1.1.0 | |
0e455ccea8db56c184ccfe69 | test | documentation_lookup | npm | https://www.npmjs.com/package/eslint | eslint | marketplace | typescript | frontend | Find and summarize the relevant documentation for frontend. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "eslint", "source_url": "https://www.npmjs.com/package/eslint", "source_type": "package", "top... | === RELEVANT DOCS ===
- eslint
https://www.npmjs.com/package/eslint
- Official project documentation
- API reference
=== KEY SECTIONS ===
- Getting started
- API reference
- Configuration
- Troubleshooting
=== SUMMARY ===
Summarize each section in 1–3 sentences and quote exact signatures where relevant. | web-research-coding-5m-1.1.0 | |
62953afeebdd171545079711 | test | refactoring | stackexchange | https://stackoverflow.com/questions/7073484/how-do-css-triangles-work | How do CSS triangles work? | developer_tool | kotlin | microservices | Create a production coding task in kotlin for microservices. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How do CSS triangles work?", "source_url": "https://stackoverflow.com/questions/7073484/how-d... | Provide implementation requirements, edge cases, testing requirements, security considerations, performance constraints, and documentation requirements. | web-research-coding-5m-1.1.0 | |
cce3aea9725c7f3abdd118ae | test | dashboard | codeberg | https://codeberg.org/dyke/2048-py | dyke/2048-py | search_interface | go | postgresql | Design a production dashboard for postgresql. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "dyke/2048-py", "source_url": "https://codeberg.org/dyke/2048-py", "source_type": "repository"... | Include navigation, KPIs, tables/charts, filters, loading states, empty states, errors, and responsive behavior. | web-research-coding-5m-1.1.0 | |
f93d20d4678807f9f0df5858 | test | dependency_impact_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/API | Web APIs | landing_page | python | api_design | Perform a deep multi-layer analysis of api_design for a landing_page 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": "Web APIs", "source_url": "https://developer.mozilla.org/en-US/docs/Web/API", "source_type": "... | === 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 'Web APIs' as a source anchor and identify relevant APIs, dependencies, versions, standard... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
24703455f5dfcfe04e05cb8c | test | fact_verification | pypi | https://pypi.org/project/transformers/ | transformers | analytics | rust | developer_experience | Verify a technical claim about developer_experience. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "transformers", "source_url": "https://pypi.org/project/transformers/", "source_type": "packag... | === CLAIM ===
A common claim about developer_experience.
=== 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 / ... | web-research-coding-5m-1.1.0 | |
63a4e0f14a3bced4af23e22e | test | search_intent_classification | gitlab | https://gitlab.com/shyft-os/shyft | shyft-os/shyft | social_app | dart | algorithms | Classify the search intent for a query about algorithms. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "shyft-os/shyft", "source_url": "https://gitlab.com/shyft-os/shyft", "source_type": "repositor... | === 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 ===
"algorithms vs alternatives"
=== CLASSIFICATION ===
Comparative / informational... | web-research-coding-5m-1.1.0 | |
44b6ef5edef6be5b58d4e766 | test | maintainability_analysis | stackexchange | https://stackoverflow.com/questions/5195859/how-do-you-push-a-tag-to-a-remote-repository-using-git | How do you push a tag to a remote repository using Git? | documentation | sql | authentication | Perform a deep multi-layer analysis of authentication for a documentation 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": "How do you push a tag to a remote repository using Git?", "source_url": "https://stackoverflo... | === 1. PROBLEM ===
Define the exact problem involving authentication. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around authentication. Use 'How do you push a tag to a remote repository using Git?' as a source anchor and i... | web-research-coding-5m-1.1.0 | |
5602bd5edb35dd7f0372d160 | test | performance_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model | DOM | marketplace | sql | documentation | Perform a deep multi-layer analysis of documentation for a marketplace using sql. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "DOM", "source_url": "https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model",... | === 1. PROBLEM ===
Define the exact problem involving documentation. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around documentation. Use 'DOM' as a source anchor and identify relevant APIs, dependencies, versions, standar... | web-research-coding-5m-1.1.0 | |
89ccab0bcc4dcde8412084e8 | test | dashboard | mdn | https://developer.mozilla.org/en-US/docs/Web/Accessibility | Accessibility | finance | ruby | backend | Design a production dashboard for backend. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Accessibility", "source_url": "https://developer.mozilla.org/en-US/docs/Web/Accessibility", "... | Include navigation, KPIs, tables/charts, filters, loading states, empty states, errors, and responsive behavior. | web-research-coding-5m-1.1.0 | |
e2b8a8803c4afff3b047605d | test | javascript_generation | stackexchange | https://stackoverflow.com/questions/66239691/what-does-npm-install-legacy-peer-deps-do-exactly-when-is-it-recommended-wh | What does npm install --legacy-peer-deps do exactly? When is it recommended / What's a potential use case? | blog | c | computer_vision | Implement JavaScript interactions for a blog. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "What does npm install --legacy-peer-deps do exactly? When is it recommended / What's a po... | 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 |
a599406975d13620c6de25dd | test | security_review | codeberg | https://codeberg.org/UI-Programming-25-26/01-Web-basic-and-git-practical-Oisin-Leonard | UI-Programming-25-26/01-Web-basic-and-git-practical-Oisin-Leonard | admin_panel | sql | software_architecture | Perform a security review of a admin_panel application. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "UI-Programming-25-26/01-Web-basic-and-git-practical-Oisin-Leonard", "source_url": "https://co... | Review authentication, authorization, input validation, XSS, CSRF, injection risks, secrets, dependencies, security headers, and logging. | web-research-coding-5m-1.1.0 | |
17f9bbc6a81e331b10d8d220 | test | typescript_generation | stackexchange | https://stackoverflow.com/questions/12694530/what-is-typescript-and-why-should-i-use-it-instead-of-javascript | What is TypeScript and why should I use it instead of JavaScript? | blog | typescript | distributed_systems | Implement TypeScript logic for a blog. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "What is TypeScript and why should I use it instead of JavaScript?", "source_url": "https://st... | 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 |
70ac78ebb20b11d6d0f2378f | test | html_generation | huggingface | https://huggingface.co/datasets/SpeedyChuck/codetorch-archive | SpeedyChuck/codetorch-archive | productivity | scala | developer_experience | Create semantic HTML for a productivity about developer_experience. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "SpeedyChuck/codetorch-archive", "source_url": "https://huggingface.co/datasets/SpeedyChuck/co... | 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 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.