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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
59569d5c7fe6649131021157 | test | risk_analysis | gitlab | https://gitlab.com/woob/woob | woob/woob | blog | javascript | microservices | Perform a deep multi-layer analysis of microservices for a blog using javascript. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "woob/woob", "source_url": "https://gitlab.com/woob/woob", "source_type": "repository", "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 'woob/woob' as a source anchor and identify relevant APIs, dependencies, versions, s... | web-research-coding-5m-1.1.0 | |
65cbc862fa1ffc1a6cd752de | test | react_generation | web_docs | https://kubernetes.io/docs/ | Kubernetes Documentation | documentation | dart | frontend | 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": "Kubernetes Documentation", "source_url": "https://kubernetes.io/docs/", "source_type": "docum... | 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 |
bad639573f9ed599a3a5fad2 | test | performance_analysis | web_docs | https://www.typescriptlang.org/docs/ | TypeScript Documentation | search_interface | javascript | testing | Perform a deep multi-layer analysis of testing for a search_interface using javascript. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "TypeScript Documentation", "source_url": "https://www.typescriptlang.org/docs/", "source_type... | === 1. PROBLEM ===
Define the exact problem involving testing. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around testing. Use 'TypeScript Documentation' as a source anchor and identify relevant APIs, dependencies, versions... | web-research-coding-5m-1.1.0 | |
b0e884b560cb1cb4447bdc69 | test | code_explanation | npm | https://www.npmjs.com/package/rollup | rollup | finance | kotlin | graphql | Explain a kotlin implementation related to graphql. | {"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... | Explain inputs, outputs, control flow, algorithms, complexity, edge cases, errors, and maintainability. | web-research-coding-5m-1.1.0 | |
e0c24bc544cbf728b2d37d46 | test | refactoring | web_docs | https://www.typescriptlang.org/docs/ | TypeScript Documentation | ecommerce | c | computer_vision | Create a production coding task in c for computer_vision. | {"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... | Provide implementation requirements, edge cases, testing requirements, security considerations, performance constraints, and documentation requirements. | web-research-coding-5m-1.1.0 | |
dd1f5acbca22595d9facb515 | test | data_structure_design | pypi | https://pypi.org/project/pytest/ | pytest | productivity | java | ci_cd | Design a data structure in java for ci_cd. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "pytest", "source_url": "https://pypi.org/project/pytest/", "source_type": "package", "topic":... | Explain representation, operations, complexity, memory trade-offs, and workload suitability. | web-research-coding-5m-1.1.0 | |
3bc9c7652c3a47b47b68fa79 | test | fact_verification | pypi | https://pypi.org/project/numpy/ | numpy | analytics | javascript | testing | Verify a technical claim about testing. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "numpy", "source_url": "https://pypi.org/project/numpy/", "source_type": "package", "topic": "... | === CLAIM ===
A common claim about testing.
=== 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-depen... | web-research-coding-5m-1.1.0 | |
698b88467a621c310d156ab6 | test | research_summary | huggingface | https://huggingface.co/datasets/puttatidam/software-documentation-ind-bitextmining | puttatidam/software-documentation-ind-bitextmining | finance | kotlin | python | Summarize the current state of knowledge about python. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "puttatidam/software-documentation-ind-bitextmining", "source_url": "https://huggingface.co/da... | === OVERVIEW ===
python 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 ===
puttatidam/software-doc... | web-research-coding-5m-1.1.0 | |
783060b3c1738c12b74316d8 | test | repository_dependency_analysis | stackexchange | https://stackoverflow.com/questions/1085162/commit-only-part-of-a-files-changes-in-git | Commit only part of a file's changes in Git | documentation | html | nextjs | Perform a deep multi-layer analysis of nextjs for a documentation using html. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Commit only part of a file's changes in Git", "source_url": "https://stackoverflow.com/qu... | === 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 'Commit only part of a file's changes in Git' as a source anchor and identify relevant APIs, d... | web-research-coding-5m-1.1.0 | |
ba88454d43373bda91617ff2 | test | multi_hop_research | npm | https://www.npmjs.com/package/axios | axios | finance | kotlin | javascript | Perform multi-hop research about javascript: start from a source, follow references, and combine findings. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "axios", "source_url": "https://www.npmjs.com/package/axios", "source_type": "package", "topic... | === HOP 1 ===
Start at: axios
https://www.npmjs.com/package/axios
Extract core claims and references.
=== HOP 2 ===
Follow references to official docs, RFCs, or specs.
Extract primary-source evidence.
=== HOP 3 ===
Check community discussions for real-world issues.
Extract failure modes and workarounds.
=== SYNTHESI... | web-research-coding-5m-1.1.0 | |
499ecb44f87bca4e0082cbde | test | refactoring | pypi | https://pypi.org/project/transformers/ | transformers | developer_tool | html | postgresql | Create a production coding task in html for postgresql. | {"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... | Provide implementation requirements, edge cases, testing requirements, security considerations, performance constraints, and documentation requirements. | web-research-coding-5m-1.1.0 | |
10acb7511bee56f8440c412a | test | refactoring_architecture | pypi | https://pypi.org/project/gradio/ | gradio | analytics | java | authentication | Refactor a java system related to authentication. Focus on refactoring architecture. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "gradio", "source_url": "https://pypi.org/project/gradio/", "source_type": "package", "topic":... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
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 | |
9ddce36b3e89b082bfd73615 | test | ui_design | web_docs | https://www.typescriptlang.org/docs/ | TypeScript Documentation | saas | java | devops | Design a production-quality UI for a saas focused on devops. | {"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... | Define layout, typography, spacing, hierarchy, components, states, responsive behavior, and accessibility. | web-research-coding-5m-1.1.0 | |
2f708c6c56b435026ee2e7b7 | test | tradeoff_analysis | stackexchange | https://stackoverflow.com/questions/1098040/checking-if-a-key-exists-in-a-javascript-object | Checking if a key exists in a JavaScript object? | portfolio | java | nextjs | Perform a deep multi-layer analysis of nextjs for a portfolio 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": "Checking if a key exists in a JavaScript object?", "source_url": "https://stackoverflow.com/q... | === 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 'Checking if a key exists in a JavaScript object?' as a source anchor and identify relevant APIs, ... | web-research-coding-5m-1.1.0 | |
3d4181fd75c729ee248024f0 | test | security_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model | DOM | ecommerce | html | data_structures | Perform a deep multi-layer analysis of data_structures for a ecommerce 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": "DOM", "source_url": "https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model",... | === 1. PROBLEM ===
Define the exact problem involving data_structures. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around data_structures. Use 'DOM' as a source anchor and identify relevant APIs, dependencies, versions, sta... | web-research-coding-5m-1.1.0 | |
736466296ac7b84328c0deb4 | test | search_query_rewrite | npm | https://www.npmjs.com/package/fastify | fastify | social_app | c | react | Rewrite and improve a vague search query about react 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": "fastify", "source_url": "https://www.npmjs.com/package/fastify", "source_type": "package", "t... | === ORIGINAL (VAGUE) ===
how to do react
=== REWRITTEN QUERIES ===
1. react official documentation guide
2. react production best practices 2025
3. react common pitfalls and solutions
4. react architecture patterns with examples
=== RATIONALE ===
Add intent (learn / implement / debug), specificity (version, framework... | web-research-coding-5m-1.1.0 | |
59f47e5263640839a052062b | test | typescript_generation | stackexchange | https://stackoverflow.com/questions/586182/how-can-i-insert-an-item-into-an-array-at-a-specific-index | How can I insert an item into an array at a specific index? | education | java | cloud | Implement TypeScript logic for a education. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How can I insert an item into an array at a specific index?", "source_url": "https://stackove... | 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 |
73114a1cfc52c3ede974e967 | test | interaction_design | pypi | https://pypi.org/project/httpx/ | httpx | developer_tool | php | postgresql | Design interaction states for a developer_tool. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "httpx", "source_url": "https://pypi.org/project/httpx/", "source_type": "package", "topic": "... | Specify default, hover, focus, active, disabled, loading, success, error, and empty states. | web-research-coding-5m-1.1.0 | |
52575a8795cb485486ee11af | test | code_explanation | mdn | https://developer.mozilla.org/en-US/docs/Web/CSS | CSS | education | c | serverless | Explain a c implementation related to serverless. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "CSS", "source_url": "https://developer.mozilla.org/en-US/docs/Web/CSS", "source_type": "docum... | Explain inputs, outputs, control flow, algorithms, complexity, edge cases, errors, and maintainability. | web-research-coding-5m-1.1.0 | |
a4ef4c93af8b9bf3439948ca | test | seo_fix | mdn | https://developer.mozilla.org/en-US/docs/Web/CSS | CSS | search_interface | scala | authentication | Create an SEO improvement plan for a search_interface about authentication. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "CSS", "source_url": "https://developer.mozilla.org/en-US/docs/Web/CSS", "source_type": "docum... | Cover titles, descriptions, headings, canonical URLs, structured data, internal links, crawlability, and performance. | web-research-coding-5m-1.1.0 | |
3039271d4d7b851576f992b2 | test | refactoring_performance | npm | https://www.npmjs.com/package/three | three | dashboard | javascript | data_engineering | Refactor a javascript system related to data_engineering. Focus on refactoring performance. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "three", "source_url": "https://www.npmjs.com/package/three", "source_type": "package", "topic... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Reduce unnecessary computation, allocations, I/O, and network requests.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify d... | web-research-coding-5m-1.1.0 | |
da3d932aeb05c4d4c12be8a5 | test | debugging | pypi | https://pypi.org/project/scrapy/ | scrapy | social_app | swift | debugging | Create a realistic swift debugging problem involving debugging. | {"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":... | Provide symptoms, reproduction strategy, diagnostic steps, root-cause analysis, minimal fix, and regression coverage. | web-research-coding-5m-1.1.0 | |
d2229fa333356bbc062530f0 | test | refactoring_architecture | pypi | https://pypi.org/project/requests/ | requests | saas | sql | rest_api | Refactor a sql system related to rest_api. Focus on refactoring architecture. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "requests", "source_url": "https://pypi.org/project/requests/", "source_type": "package", "top... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
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 | |
43329fa745cd7e03c71f1e8e | test | api_developer_experience | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API | Fetch API | ecommerce | shell | authentication | Perform a deep developer-experience analysis for a shell project involving authentication. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Fetch API", "source_url": "https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API", "sour... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
0dca79d3f37191046ba88f59 | test | risk_analysis | pypi | https://pypi.org/project/rich/ | rich | ecommerce | php | nlp | Perform a deep multi-layer analysis of nlp for a ecommerce 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": "rich", "source_url": "https://pypi.org/project/rich/", "source_type": "package", "topic": "nl... | === 1. PROBLEM ===
Define the exact problem involving nlp. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around nlp. Use 'rich' as a source anchor and identify relevant APIs, dependencies, versions, standards, and technical c... | web-research-coding-5m-1.1.0 | |
eeaad127bbab62709c3f9e15 | test | repository_understanding | mdn | https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model | DOM | blog | swift | nodejs | Perform a deep multi-layer analysis of nodejs 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": "DOM", "source_url": "https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model",... | === 1. PROBLEM ===
Define the exact problem involving nodejs. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around nodejs. Use 'DOM' as a source anchor and identify relevant APIs, dependencies, versions, standards, and techni... | web-research-coding-5m-1.1.0 | |
f73f3b2aaffbc937015e5ca2 | test | product_analysis | web_docs | https://docs.docker.com/ | Docker Documentation | ecommerce | swift | nodejs | Perform a deep multi-layer analysis of nodejs for a ecommerce 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": "Docker Documentation", "source_url": "https://docs.docker.com/", "source_type": "documentatio... | === 1. PROBLEM ===
Define the exact problem involving nodejs. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around nodejs. Use 'Docker Documentation' as a source anchor and identify relevant APIs, dependencies, versions, stan... | web-research-coding-5m-1.1.0 | |
573eb6492323e98fe28d1ba5 | test | refactoring_scalability | web_docs | https://kubernetes.io/docs/ | Kubernetes Documentation | ecommerce | shell | cloud | Refactor a shell system related to cloud. Focus on refactoring scalability. | {"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... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Restructure the system to handle increased load without unnecessary complexity.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Id... | web-research-coding-5m-1.1.0 | |
3836a8458c810ad56a28a390 | test | source_comparison | mdn | https://developer.mozilla.org/en-US/docs/Web/CSS | CSS | education | shell | react | Compare multiple sources about react and identify agreements, contradictions, and gaps. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "CSS", "source_url": "https://developer.mozilla.org/en-US/docs/Web/CSS", "source_type": "docum... | === SOURCES ===
- CSS (https://developer.mozilla.org/en-US/docs/Web/CSS)
- Official documentation
- Community discussions
=== AGREEMENTS ===
Identify claims supported by multiple independent sources.
=== CONTRADICTIONS ===
Identify conflicting claims and their likely cause (version differences, environment, outdated ... | web-research-coding-5m-1.1.0 | |
7c28727e90e6d8895f6782a7 | test | css_generation | npm | https://www.npmjs.com/package/vitest | vitest | dashboard | html | distributed_systems | Create responsive CSS for a dashboard. | {"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... | Use reusable rules, responsive layouts, scalable typography, spacing, focus states, and mobile support. | :root {
--space: 1rem;
}
* {
box-sizing: border-box;
}
body {
margin: 0;
font-family: system-ui, sans-serif;
}
.container {
width: min(100% - 2rem, 1200px);
margin-inline: auto;
} | web-research-coding-5m-1.1.0 |
0867d2e48ececc4a1a523cb8 | test | refactoring_maintainability | npm | https://www.npmjs.com/package/typescript | typescript | blog | java | mongodb | Refactor a java system related to mongodb. Focus on refactoring maintainability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "typescript", "source_url": "https://www.npmjs.com/package/typescript", "source_type": "packag... | === 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 | |
45f133b27a6dc2945bb806a9 | test | design_components | codeberg | https://codeberg.org/sanjai-shaarugesh/Advanced-media-controller | sanjai-shaarugesh/Advanced-media-controller | landing_page | sql | computer_vision | Create a component architecture for a landing_page. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "sanjai-shaarugesh/Advanced-media-controller", "source_url": "https://codeberg.org/sanjai-shaa... | Define primitive components, composite components, variants, states, composition rules, and accessibility contracts. | web-research-coding-5m-1.1.0 | |
ba2bd2acff3eb2290971f0e8 | test | refactoring_architecture | github | https://github.com/tensorflow/tensorflow | tensorflow/tensorflow | admin_panel | javascript | data_structures | Refactor a javascript system related to data_structures. Focus on refactoring architecture. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "tensorflow/tensorflow", "source_url": "https://github.com/tensorflow/tensorflow", "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 | |
f7025fbadc4ab701c253900e | test | information_architecture | web_docs | https://go.dev/doc/ | Go Documentation | finance | swift | graphql | Design the information architecture for graphql. | {"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... | Organize content into logical categories, navigation levels, search, filtering, and discoverable paths. | web-research-coding-5m-1.1.0 | |
1a4658af3e95c90f28d3527b | test | maintainability_analysis | huggingface | https://huggingface.co/datasets/CohereLabs/wikipedia-2023-11-embed-multilingual-v3 | CohereLabs/wikipedia-2023-11-embed-multilingual-v3 | portfolio | kotlin | graphql | Perform a deep multi-layer analysis of graphql for a portfolio using kotlin. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "CohereLabs/wikipedia-2023-11-embed-multilingual-v3", "source_url": "https://huggingface.co/da... | === 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 'CohereLabs/wikipedia-2023-11-embed-multilingual-v3' as a source anchor and identify relevant AP... | web-research-coding-5m-1.1.0 | |
11b428616c3e46b00ceed5cc | test | responsive_design | stackexchange | https://stackoverflow.com/questions/59013109/runtimeerror-input-type-torch-floattensor-and-weight-type-torch-cuda-floatte | RuntimeError: Input type (torch.FloatTensor) and weight type (torch.cuda.FloatTensor) should be the same | productivity | python | python | Create a responsive design strategy for a productivity. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "RuntimeError: Input type (torch.FloatTensor) and weight type (torch.cuda.FloatTensor) should ... | Define mobile, tablet, and desktop behavior, layout transitions, navigation, content priority, typography, and interaction targets. | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
67bfd7b70bbbc12233ac9069 | test | refactoring_legacy_code | stackexchange | https://stackoverflow.com/questions/12709074/how-do-you-explicitly-set-a-new-property-on-window-in-typescript | How do you explicitly set a new property on `window` in TypeScript? | ecommerce | css | authorization | Refactor a css system related to authorization. Focus on refactoring legacy code. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How do you explicitly set a new property on `window` in TypeScript?", "source_url": "https://... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Characterize existing behavior first and incrementally replace risky legacy structures.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implication... | web-research-coding-5m-1.1.0 | |
8876380d1312a5228af95245 | test | technical_research | huggingface | https://huggingface.co/datasets/AkshithAI/stackexchange-programming-cs-ctx-4096 | AkshithAI/stackexchange-programming-cs-ctx-4096 | social_app | kotlin | kubernetes | Perform a technical research task about kubernetes, focused on implementation details. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "AkshithAI/stackexchange-programming-cs-ctx-4096", "source_url": "https://huggingface.co/datas... | === SCOPE ===
Technical behavior of kubernetes.
=== QUESTIONS ===
- What are the inputs, outputs, and invariants?
- What are the performance characteristics?
- What are the security implications?
- What are the compatibility constraints?
=== EVIDENCE ===
- AkshithAI/stackexchange-programming-cs-ctx-4096 (https://hugg... | web-research-coding-5m-1.1.0 | |
a9da3697f76b45878ff5179b | test | component_design | web_docs | https://docs.djangoproject.com/ | Django Documentation | portfolio | sql | python | Design reusable UI components for a portfolio. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Django Documentation", "source_url": "https://docs.djangoproject.com/", "source_type": "docum... | Define component responsibilities, props/data contracts, variants, states, composition rules, accessibility, testing, and documentation. | web-research-coding-5m-1.1.0 | |
eba7cd3450b0f0ae28d1ed5e | test | risk_analysis | github | https://github.com/react/react-native | react/react-native | developer_tool | java | user_experience | Perform a deep multi-layer analysis of user_experience for a developer_tool using java. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "react/react-native", "source_url": "https://github.com/react/react-native", "source_type": "r... | === 1. PROBLEM ===
Define the exact problem involving user_experience. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around user_experience. Use 'react/react-native' as a source anchor and identify relevant APIs, dependencies... | web-research-coding-5m-1.1.0 | |
63178589ff6f171be94b16b1 | test | component_design | pypi | https://pypi.org/project/scikit-learn/ | scikit-learn | blog | sql | developer_experience | Design reusable UI components for a blog. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "scikit-learn", "source_url": "https://pypi.org/project/scikit-learn/", "source_type": "packag... | Define component responsibilities, props/data contracts, variants, states, composition rules, accessibility, testing, and documentation. | web-research-coding-5m-1.1.0 | |
5abe7a57feba7788a7a39596 | test | research_summary | mdn | https://developer.mozilla.org/en-US/docs/Web/API | Web APIs | saas | python | documentation | Summarize the current state of knowledge about documentation. | {"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": "... | === OVERVIEW ===
documentation 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 ===
Web APIs (https:... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
da399cd60800ea6a7497e39a | test | upgrade_experience | gitlab | https://gitlab.com/mlreef/mlreef | mlreef/mlreef | blog | php | javascript | Perform a deep developer-experience analysis for a php project involving javascript. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "mlreef/mlreef", "source_url": "https://gitlab.com/mlreef/mlreef", "source_type": "repository"... | === 1. 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 | |
11f0dae86e2c45f9a338680c | test | developer_onboarding | mdn | https://developer.mozilla.org/en-US/docs/Web/CSS | CSS | ecommerce | shell | nodejs | Perform a deep developer-experience analysis for a shell project involving nodejs. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "CSS", "source_url": "https://developer.mozilla.org/en-US/docs/Web/CSS", "source_type": "docum... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
a853a8fd8c583ebf9c01c527 | test | debugging | web_docs | https://docs.djangoproject.com/ | Django Documentation | community | swift | css | Create a realistic swift debugging problem involving css. | {"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... | Provide symptoms, reproduction strategy, diagnostic steps, root-cause analysis, minimal fix, and regression coverage. | web-research-coding-5m-1.1.0 | |
38dfda36cc8c5edbdd176df6 | test | refactoring | mdn | https://developer.mozilla.org/en-US/docs/Web/HTML | HTML | developer_tool | javascript | docker | Create a production coding task in javascript for docker. | {"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... | Provide implementation requirements, edge cases, testing requirements, security considerations, performance constraints, and documentation requirements. | web-research-coding-5m-1.1.0 | |
aaeec11a441c0bf260787cce | test | ux_analysis | stackexchange | https://stackoverflow.com/questions/7273338/how-to-vertically-align-an-image-inside-a-div | How to vertically align an image inside a div | portfolio | typescript | authorization | Perform a deep multi-layer analysis of authorization for a portfolio using typescript. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How to vertically align an image inside a div", "source_url": "https://stackoverflow.com/ques... | === 1. PROBLEM ===
Define the exact problem involving authorization. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around authorization. Use 'How to vertically align an image inside a div' as a source anchor and identify rele... | web-research-coding-5m-1.1.0 | |
1a88c9c79885f5386821e930 | test | refactoring_legacy_code | mdn | https://developer.mozilla.org/en-US/docs/Web/API | Web APIs | ecommerce | css | rest_api | Refactor a css system related to rest_api. Focus on refactoring legacy code. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Web APIs", "source_url": "https://developer.mozilla.org/en-US/docs/Web/API", "source_type": "... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Characterize existing behavior first and incrementally replace risky legacy structures.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implication... | web-research-coding-5m-1.1.0 | |
13356b5f2cb764909a390bf7 | test | accessibility_analysis | pypi | https://pypi.org/project/pydantic/ | pydantic | community | shell | ci_cd | Perform a deep multi-layer analysis of ci_cd for a community using shell. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "pydantic", "source_url": "https://pypi.org/project/pydantic/", "source_type": "package", "top... | === 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 'pydantic' as a source anchor and identify relevant APIs, dependencies, versions, standards, and tec... | web-research-coding-5m-1.1.0 | |
f23adfe4bcc9aadd8b2e051f | test | component_design | pypi | https://pypi.org/project/numpy/ | numpy | search_interface | rust | javascript | Design reusable UI components for a search_interface. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "numpy", "source_url": "https://pypi.org/project/numpy/", "source_type": "package", "topic": "... | Define component responsibilities, props/data contracts, variants, states, composition rules, accessibility, testing, and documentation. | web-research-coding-5m-1.1.0 | |
52e0ddf370e876c915407f74 | test | developer_experience | stackexchange | https://stackoverflow.com/questions/35537229/how-can-i-update-the-parents-state-in-react | How can I update the parent's state in React? | search_interface | dart | documentation | Perform a deep developer-experience analysis for a dart project involving documentation. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How can I update the parent's state in React?", "source_url": "https://stackoverflow.com/... | === 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 | |
a0e73c93a931e57d26c64f87 | test | data_structure_design | npm | https://www.npmjs.com/package/rollup | rollup | education | sql | web_accessibility | Design a data structure in sql for web_accessibility. | {"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... | Explain representation, operations, complexity, memory trade-offs, and workload suitability. | web-research-coding-5m-1.1.0 | |
6f896e1dab869c5b9decb037 | test | repository_comparison | github | https://github.com/encode/django-rest-framework | encode/django-rest-framework | dashboard | rust | css | Perform a deep multi-layer analysis of css for a dashboard using rust. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "encode/django-rest-framework", "source_url": "https://github.com/encode/django-rest-framework... | === 1. PROBLEM ===
Define the exact problem involving css. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around css. Use 'encode/django-rest-framework' as a source anchor and identify relevant APIs, dependencies, versions, st... | web-research-coding-5m-1.1.0 | |
0b0b9f0190aa1bf6c332063f | test | refactoring_dependency | huggingface | https://huggingface.co/datasets/Jackrong/Competitive-Programming-python-blend | Jackrong/Competitive-Programming-python-blend | social_app | swift | caching | Refactor a swift system related to caching. Focus on refactoring dependency. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Jackrong/Competitive-Programming-python-blend", "source_url": "https://huggingface.co/dataset... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Audit dependencies and isolate external integrations.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify developer-experienc... | web-research-coding-5m-1.1.0 | |
a9b7f04aae4d2645f9e24e8c | test | deployment_experience | huggingface | https://huggingface.co/datasets/AkshithAI/starcoderdata-javascript-ctx-4096 | AkshithAI/starcoderdata-javascript-ctx-4096 | marketplace | python | ci_cd | Perform a deep developer-experience analysis for a python project involving ci_cd. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "AkshithAI/starcoderdata-javascript-ctx-4096", "source_url": "https://huggingface.co/datasets/... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
fc3695827f1d6c37ff7fa82f | test | component_design | stackexchange | https://stackoverflow.com/questions/32693061/how-can-i-select-an-element-in-a-component-template | How can I select an element in a component template? | community | ruby | docker | Design reusable UI components for a community. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How can I select an element in a component template?", "source_url": "https://stackoverflow.c... | Define component responsibilities, props/data contracts, variants, states, composition rules, accessibility, testing, and documentation. | web-research-coding-5m-1.1.0 | |
7739ba28fad4f41e14dd3c5d | test | product_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/API | Web APIs | saas | javascript | nlp | Perform a deep multi-layer analysis of nlp for a saas using javascript. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Web APIs", "source_url": "https://developer.mozilla.org/en-US/docs/Web/API", "source_type": "... | === 1. PROBLEM ===
Define the exact problem involving nlp. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around nlp. Use 'Web APIs' as a source anchor and identify relevant APIs, dependencies, versions, standards, and technic... | web-research-coding-5m-1.1.0 | |
7db3c5aca61ba38df4c3714f | test | refactoring_scalability | codeberg | https://codeberg.org/plaublin/100-exercises-to-learn-rust | plaublin/100-exercises-to-learn-rust | saas | python | html | Refactor a python system related to html. Focus on refactoring scalability. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "plaublin/100-exercises-to-learn-rust", "source_url": "https://codeberg.org/plaublin/100-exerc... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Restructure the system to handle increased load without unnecessary complexity.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Id... | def process(value):
if value is None:
raise ValueError("value is required")
return value | web-research-coding-5m-1.1.0 |
8d1d788e2189a5eac9badc89 | test | react_generation | stackexchange | https://stackoverflow.com/questions/21247278/about-d-ts-in-typescript | About "*.d.ts" in TypeScript | portfolio | css | nextjs | Design React components for a portfolio. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "About "*.d.ts" in TypeScript", "source_url": "https://stackoverflow.com/questions/2... | 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 |
baf7ef5d22bd32482c98b7ae | test | refactoring_api | stackexchange | https://stackoverflow.com/questions/4810841/pretty-print-json-using-javascript | pretty-print JSON using JavaScript | marketplace | html | web_accessibility | Refactor a html system related to web_accessibility. Focus on refactoring api. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "pretty-print JSON using JavaScript", "source_url": "https://stackoverflow.com/questions/48108... | === 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 | |
4289d8649e166c2aab840d92 | test | landing_page | huggingface | https://huggingface.co/datasets/dmeldrum6/dataset-JavaScript-general-coding | dmeldrum6/dataset-JavaScript-general-coding | community | php | authorization | Design a landing page for a authorization product. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "dmeldrum6/dataset-JavaScript-general-coding", "source_url": "https://huggingface.co/datasets/... | Include hero, value proposition, features, CTA, FAQ, responsive behavior, SEO, accessibility, and analytics. | web-research-coding-5m-1.1.0 | |
e00799579efd54404f187846 | test | design_system | mdn | https://developer.mozilla.org/en-US/docs/Web/CSS | CSS | social_app | sql | serverless | Create a scalable design system for a social_app. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "CSS", "source_url": "https://developer.mozilla.org/en-US/docs/Web/CSS", "source_type": "docum... | Define tokens, typography, spacing, components, variants, states, responsive rules, accessibility, and documentation. | web-research-coding-5m-1.1.0 | |
34ba7d7d4cf08079536879e1 | test | source_selection | web_docs | https://fastapi.tiangolo.com/ | FastAPI Documentation | documentation | cpp | authentication | Select the most reliable sources to research authentication. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "FastAPI Documentation", "source_url": "https://fastapi.tiangolo.com/", "source_type": "docume... | === SOURCE TIERS ===
1. Primary: official documentation, specifications, RFCs
2. Secondary: maintained repositories, changelogs, releases
3. Tertiary: tutorials, blog posts, Q&A
=== SELECTION CRITERIA ===
- Authority of the publisher
- Recency and version relevance
- Technical depth
- Reproducibility of examples
=== ... | web-research-coding-5m-1.1.0 | |
e90f3b869962ef2773b971bd | test | information_architecture | web_docs | https://docs.docker.com/ | Docker Documentation | marketplace | java | open_source | Design the information architecture for open_source. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Docker Documentation", "source_url": "https://docs.docker.com/", "source_type": "documentatio... | Organize content into logical categories, navigation levels, search, filtering, and discoverable paths. | web-research-coding-5m-1.1.0 | |
8fd3230b9cb9aade90fbaec2 | test | refactoring_legacy_code | mdn | https://developer.mozilla.org/en-US/docs/Web/JavaScript | JavaScript | admin_panel | ruby | authorization | Refactor a ruby system related to authorization. Focus on refactoring legacy code. | {"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 ===
Characterize existing behavior first and incrementally replace risky legacy structures.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implication... | web-research-coding-5m-1.1.0 | |
42c5c8a52722341570b9b5c2 | test | tradeoff_analysis | stackexchange | https://stackoverflow.com/questions/28329382/understanding-unique-keys-for-array-children-in-react-js | Understanding unique keys for array children in React.js | ecommerce | php | documentation | Perform a deep multi-layer analysis of documentation for a ecommerce 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": "Understanding unique keys for array children in React.js", "source_url": "https://stackoverfl... | === 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 'Understanding unique keys for array children in React.js' as a source anchor and id... | web-research-coding-5m-1.1.0 | |
5bc18b42eaaf85e96fef7508 | test | unit_testing | github | https://github.com/h5bp/html5-boilerplate | h5bp/html5-boilerplate | education | sql | documentation | Create a unit-testing strategy for sql code involving documentation. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "h5bp/html5-boilerplate", "source_url": "https://github.com/h5bp/html5-boilerplate", "source_t... | Cover normal cases, edge cases, invalid inputs, failure modes, mocks, and regression tests. | web-research-coding-5m-1.1.0 | |
6f232c58e546794d85128499 | test | typescript_generation | stackexchange | https://stackoverflow.com/questions/35537229/how-can-i-update-the-parents-state-in-react | How can I update the parent's state in React? | developer_tool | rust | devops | Implement TypeScript logic for a developer_tool. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How can I update the parent's state in React?", "source_url": "https://stackoverflow.com/... | 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 |
70bfa932b67dcd22cb54cb13 | test | dependency_management_experience | stackexchange | https://stackoverflow.com/questions/31173738/typescript-getting-error-ts2304-cannot-find-name-require | TypeScript getting error TS2304: cannot find name ' require' | admin_panel | dart | caching | Perform a deep developer-experience analysis for a dart project involving caching. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "TypeScript getting error TS2304: cannot find name ' require'", "source_url": "https:/... | === 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 | |
568e11451db72d0535305f94 | test | refactoring | codeberg | https://codeberg.org/UI-Programming-25-26/01-web-basics-and-git-Martin-McCarthy | UI-Programming-25-26/01-web-basics-and-git-Martin-McCarthy | dashboard | typescript | rest_api | Create a production coding task in typescript for rest_api. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "UI-Programming-25-26/01-web-basics-and-git-Martin-McCarthy", "source_url": "https://codeberg.... | Provide implementation requirements, edge cases, testing requirements, security considerations, performance constraints, and documentation requirements. | web-research-coding-5m-1.1.0 | |
46d8aa5fde88c6905dd17d0c | test | source_selection | gitlab | https://gitlab.com/vincenttunru/feed-me-up-scotty | vincenttunru/feed-me-up-scotty | dashboard | go | documentation | Select the most reliable sources to research documentation. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "vincenttunru/feed-me-up-scotty", "source_url": "https://gitlab.com/vincenttunru/feed-me-up-sc... | === SOURCE TIERS ===
1. Primary: official documentation, specifications, RFCs
2. Secondary: maintained repositories, changelogs, releases
3. Tertiary: tutorials, blog posts, Q&A
=== SELECTION CRITERIA ===
- Authority of the publisher
- Recency and version relevance
- Technical depth
- Reproducibility of examples
=== ... | web-research-coding-5m-1.1.0 | |
5e7523b09c6317473902d525 | test | research_summary | pypi | https://pypi.org/project/httpx/ | httpx | productivity | swift | devops | Summarize the current state of knowledge about devops. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "httpx", "source_url": "https://pypi.org/project/httpx/", "source_type": "package", "topic": "... | === OVERVIEW ===
devops 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 ===
httpx (https://pypi.org... | web-research-coding-5m-1.1.0 | |
8b6a38bc60f2e7562e8d072b | test | landing_page | gitlab | https://gitlab.com/frontierdevelopmentlab/disaster-prevention/cubesatfloods | frontierdevelopmentlab/disaster-prevention/cubesatfloods | dashboard | sql | machine_learning | Design a landing page for a machine_learning product. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "frontierdevelopmentlab/disaster-prevention/cubesatfloods", "source_url": "https://gitlab.com/... | Include hero, value proposition, features, CTA, FAQ, responsive behavior, SEO, accessibility, and analytics. | web-research-coding-5m-1.1.0 | |
bf8a3b118547ba2e244c0075 | test | research_plan | npm | https://www.npmjs.com/package/hono | hono | search_interface | java | open_source | Build a structured research plan to deeply understand open_source. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "hono", "source_url": "https://www.npmjs.com/package/hono", "source_type": "package", "topic":... | === GOAL ===
Produce a reliable, current, and actionable understanding of open_source.
=== PHASES ===
1. Orientation — skim official docs and README.
2. Deep read — study specs, RFCs, changelogs.
3. Hands-on — reproduce examples locally.
4. Comparison — compare alternatives and trade-offs.
5. Synthesis — write finding... | web-research-coding-5m-1.1.0 | |
fe8b7740b3edf81968042bce | test | visual_hierarchy | stackexchange | https://stackoverflow.com/questions/728360/how-do-i-correctly-clone-a-javascript-object | How do I correctly clone a JavaScript object? | admin_panel | ruby | python | Improve visual hierarchy in a admin_panel. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How do I correctly clone a JavaScript object?", "source_url": "https://stackoverflow.com/ques... | Use heading structure, typography, spacing, grouping, alignment, contrast, and consistent affordances. | web-research-coding-5m-1.1.0 | |
2e7ec20c325c53ccbfdfc9c3 | test | repository_comparison | mdn | https://developer.mozilla.org/en-US/docs/Web/API | Web APIs | productivity | typescript | observability | Perform a deep multi-layer analysis of observability 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": "Web APIs", "source_url": "https://developer.mozilla.org/en-US/docs/Web/API", "source_type": "... | === 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 'Web APIs' as a source anchor and identify relevant APIs, dependencies, versions, st... | web-research-coding-5m-1.1.0 | |
950bc5344d8e6f15eed30672 | test | build_experience | huggingface | https://huggingface.co/datasets/iamtarun/python_code_instructions_18k_alpaca | iamtarun/python_code_instructions_18k_alpaca | social_app | go | linux | Perform a deep developer-experience analysis for a go project involving linux. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "iamtarun/python_code_instructions_18k_alpaca", "source_url": "https://huggingface.co/datasets... | === 1. DISCOVERY ===
How quickly can a developer understand the project?
=== 2. INSTALLATION ===
Evaluate dependencies, setup commands, environment variables, tooling, and failure messages.
=== 3. ONBOARDING ===
Evaluate the time-to-first-success, documentation, examples, architecture explanations, and project conven... | web-research-coding-5m-1.1.0 | |
816abde058fa157124e0742c | test | repository_issue_reasoning | pypi | https://pypi.org/project/transformers/ | transformers | developer_tool | css | testing | Perform a deep multi-layer analysis of testing for a developer_tool using css. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "transformers", "source_url": "https://pypi.org/project/transformers/", "source_type": "packag... | === 1. PROBLEM ===
Define the exact problem involving testing. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around testing. Use 'transformers' as a source anchor and identify relevant APIs, dependencies, versions, standards,... | web-research-coding-5m-1.1.0 | |
b586a9b22f629aeabcaa9289 | test | information_architecture | stackexchange | https://stackoverflow.com/questions/18111657/how-to-get-names-of-enum-entries | How to get names of enum entries? | finance | css | python | Design the information architecture for python. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "How to get names of enum entries?", "source_url": "https://stackoverflow.com/questions/181116... | Organize content into logical categories, navigation levels, search, filtering, and discoverable paths. | web-research-coding-5m-1.1.0 | |
b559221174a9353d4b91559b | test | refactoring_modularization | pypi | https://pypi.org/project/requests/ | requests | blog | rust | developer_experience | Refactor a rust system related to developer_experience. Focus on refactoring modularization. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "requests", "source_url": "https://pypi.org/project/requests/", "source_type": "package", "top... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Split large modules into cohesive units with explicit responsibilities.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify d... | web-research-coding-5m-1.1.0 | |
c1d6ddff7246baecb845d3d5 | test | refactoring_security | web_docs | https://fastapi.tiangolo.com/ | FastAPI Documentation | finance | rust | data_structures | Refactor a rust system related to data_structures. Focus on refactoring security. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "FastAPI Documentation", "source_url": "https://fastapi.tiangolo.com/", "source_type": "docume... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
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 | |
b5e06aebee3b5257c3cbc1a0 | test | root_cause_analysis | gitlab | https://gitlab.com/pavel.krupala/pyqt-node-editor | pavel.krupala/pyqt-node-editor | developer_tool | ruby | python | Perform a deep multi-layer analysis of python for a developer_tool 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": "pavel.krupala/pyqt-node-editor", "source_url": "https://gitlab.com/pavel.krupala/pyqt-node-ed... | === 1. PROBLEM ===
Define the exact problem involving python. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around python. Use 'pavel.krupala/pyqt-node-editor' as a source anchor and identify relevant APIs, dependencies, vers... | web-research-coding-5m-1.1.0 | |
4ff33681219793868dd09747 | test | refactoring_modularization | huggingface | https://huggingface.co/datasets/embedl/documentation-images | embedl/documentation-images | education | kotlin | database | Refactor a kotlin system related to database. Focus on refactoring modularization. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "embedl/documentation-images", "source_url": "https://huggingface.co/datasets/embedl/documenta... | === 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 | |
86f59805a45d7f45fc84a06a | test | technical_research | web_docs | https://doc.rust-lang.org/ | Rust Documentation | portfolio | typescript | ci_cd | Perform a technical research task about ci_cd, focused on implementation details. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Rust Documentation", "source_url": "https://doc.rust-lang.org/", "source_type": "documentatio... | === SCOPE ===
Technical behavior of ci_cd.
=== QUESTIONS ===
- What are the inputs, outputs, and invariants?
- What are the performance characteristics?
- What are the security implications?
- What are the compatibility constraints?
=== EVIDENCE ===
- Rust Documentation (https://doc.rust-lang.org/)
- Official documen... | web-research-coding-5m-1.1.0 | |
a09fde6db0f848535b9fd00d | test | debugging | huggingface | https://huggingface.co/datasets/makayel/documentation-kubernetes | makayel/documentation-kubernetes | dashboard | go | html | Create a realistic go debugging problem involving html. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "makayel/documentation-kubernetes", "source_url": "https://huggingface.co/datasets/makayel/doc... | Provide symptoms, reproduction strategy, diagnostic steps, root-cause analysis, minimal fix, and regression coverage. | web-research-coding-5m-1.1.0 | |
f478f4825b0b437684f29bee | test | maintainability_analysis | mdn | https://developer.mozilla.org/en-US/docs/Web/HTTP | HTTP | documentation | css | algorithms | Perform a deep multi-layer analysis of algorithms for a documentation using css. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "HTTP", "source_url": "https://developer.mozilla.org/en-US/docs/Web/HTTP", "source_type": "doc... | === 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 'HTTP' as a source anchor and identify relevant APIs, dependencies, versions, standards, a... | web-research-coding-5m-1.1.0 | |
93e0d15ba5582db76cc2b654 | test | form_ui | web_docs | https://go.dev/doc/ | Go Documentation | search_interface | html | database | Design an accessible form for database. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Go Documentation", "source_url": "https://go.dev/doc/", "source_type": "documentation", "topi... | Use labels, validation, clear errors, keyboard navigation, appropriate autocomplete, and accessible status messaging. | web-research-coding-5m-1.1.0 | |
ff73bae53d53c27dc166d0c2 | test | debugging_experience | stackexchange | https://stackoverflow.com/questions/39152071/cant-bind-to-formgroup-since-it-isnt-a-known-property-of-form | Can't bind to 'formGroup' since it isn't a known property of 'form' | ecommerce | css | testing | Perform a deep developer-experience analysis for a css project involving testing. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Can't bind to 'formGroup' since it isn't a known property of 'form'",... | === 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 | |
660960df67cb8387e004670e | test | security_analysis | pypi | https://pypi.org/project/streamlit/ | streamlit | education | php | python | Perform a deep multi-layer analysis of python for a education 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": "streamlit", "source_url": "https://pypi.org/project/streamlit/", "source_type": "package", "t... | === 1. PROBLEM ===
Define the exact problem involving python. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around python. Use 'streamlit' as a source anchor and identify relevant APIs, dependencies, versions, standards, and ... | web-research-coding-5m-1.1.0 | |
3bfef122cd04f0e7488abf6b | test | code_review | pypi | https://pypi.org/project/beautifulsoup4/ | beautifulsoup4 | productivity | go | graphql | Perform a production code review of go code related to graphql. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "beautifulsoup4", "source_url": "https://pypi.org/project/beautifulsoup4/", "source_type": "pa... | Review correctness, security, performance, readability, architecture, testing, maintainability, and error handling. | web-research-coding-5m-1.1.0 | |
f154af484951d15ac12f011f | test | dx_analysis | web_docs | https://docs.docker.com/ | Docker Documentation | ecommerce | css | security | Perform a deep developer-experience analysis for a css project involving security. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Docker Documentation", "source_url": "https://docs.docker.com/", "source_type": "documentatio... | === 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 | |
6724718dd0d215258e00f9a4 | test | integration_testing | huggingface | https://huggingface.co/datasets/ceyron/machine-learning-and-simulation | ceyron/machine-learning-and-simulation | saas | go | data_engineering | Design integration tests for a go system involving data_engineering. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "ceyron/machine-learning-and-simulation", "source_url": "https://huggingface.co/datasets/ceyro... | Test real component boundaries, persistence, configuration, external interfaces, errors, cleanup, and realistic workflows. | web-research-coding-5m-1.1.0 | |
685bda430392802c82f6400a | test | landing_page | github | https://github.com/mermaid-js/mermaid | mermaid-js/mermaid | education | cpp | devops | Design a landing page for a devops product. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "mermaid-js/mermaid", "source_url": "https://github.com/mermaid-js/mermaid", "source_type": "r... | Include hero, value proposition, features, CTA, FAQ, responsive behavior, SEO, accessibility, and analytics. | web-research-coding-5m-1.1.0 | |
2b1ee834c82bc1f76d4832c1 | test | source_comparison | github | https://github.com/donnemartin/system-design-primer | donnemartin/system-design-primer | marketplace | go | backend | Compare multiple sources about backend and identify agreements, contradictions, and gaps. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "donnemartin/system-design-primer", "source_url": "https://github.com/donnemartin/system-desig... | === SOURCES ===
- donnemartin/system-design-primer (https://github.com/donnemartin/system-design-primer)
- Official documentation
- Community discussions
=== AGREEMENTS ===
Identify claims supported by multiple independent sources.
=== CONTRADICTIONS ===
Identify conflicting claims and their likely cause (version dif... | web-research-coding-5m-1.1.0 | |
42b0f23aeb537666ac213ddf | test | api_developer_experience | mdn | https://developer.mozilla.org/en-US/docs/Web/HTML | HTML | developer_tool | php | backend | Perform a deep developer-experience analysis for a php project involving backend. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "HTML", "source_url": "https://developer.mozilla.org/en-US/docs/Web/HTML", "source_type": "doc... | === 1. 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 | |
67e41a39eceab23cbc5b27af | test | product_analysis | github | https://github.com/langchain-ai/langchain | langchain-ai/langchain | admin_panel | html | microservices | Perform a deep multi-layer analysis of microservices for a admin_panel 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": "langchain-ai/langchain", "source_url": "https://github.com/langchain-ai/langchain", "source_t... | === 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 'langchain-ai/langchain' as a source anchor and identify relevant APIs, dependencies... | web-research-coding-5m-1.1.0 | |
b16f32c57d380eeb326f4ff5 | test | design_system | github | https://github.com/eriklindernoren/ML-From-Scratch | eriklindernoren/ML-From-Scratch | analytics | css | data_structures | Create a scalable design system for a analytics. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "eriklindernoren/ML-From-Scratch", "source_url": "https://github.com/eriklindernoren/ML-From-S... | Define tokens, typography, spacing, components, variants, states, responsive rules, accessibility, and documentation. | web-research-coding-5m-1.1.0 | |
b4acdaf304a2bf12c84fbdff | test | repository_understanding | mdn | https://developer.mozilla.org/en-US/docs/Web/Performance | Performance | marketplace | css | microservices | Perform a deep multi-layer analysis of microservices for a marketplace using css. Analyze the problem from research, evidence, architecture, implementation, security, performance, design, UX, developer experience, and validation perspectives. | {"analysis_framework": ["problem", "context", "evidence", "architecture", "implementation", "quality", "security", "performance", "ux", "design", "developer_experience", "validation", "tradeoffs", "synthesis"], "source_name": "Performance", "source_url": "https://developer.mozilla.org/en-US/docs/Web/Performance", "sour... | === 1. PROBLEM ===
Define the exact problem involving microservices. Identify objectives, inputs, outputs, constraints, assumptions, and acceptance criteria.
=== 2. CONTEXT ===
Analyze the ecosystem context around microservices. Use 'Performance' as a source anchor and identify relevant APIs, dependencies, versions,... | web-research-coding-5m-1.1.0 | |
c5f715ea9973d3f7fc18b995 | test | technical_research | web_docs | https://kubernetes.io/docs/ | Kubernetes Documentation | search_interface | rust | rest_api | Perform a technical research task about rest_api, focused on implementation details. | {"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... | === SCOPE ===
Technical behavior of rest_api.
=== QUESTIONS ===
- What are the inputs, outputs, and invariants?
- What are the performance characteristics?
- What are the security implications?
- What are the compatibility constraints?
=== EVIDENCE ===
- Kubernetes Documentation (https://kubernetes.io/docs/)
- Offici... | web-research-coding-5m-1.1.0 | |
450aa0885944df9a2db322da | test | refactoring_observability | web_docs | https://kubernetes.io/docs/ | Kubernetes Documentation | education | javascript | typescript | Refactor a javascript system related to typescript. Focus on refactoring observability. | {"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... | === CURRENT STATE ===
Identify the existing structural or technical problem.
=== GOAL ===
Improve logging, metrics, tracing, diagnostics, and failure visibility.
=== ANALYSIS ===
1. Identify coupling and cohesion problems.
2. Identify correctness risks.
3. Identify security and performance implications.
4. Identify d... | web-research-coding-5m-1.1.0 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.