Skill UI

This guide provides comprehensive principles for modern game development, covering engine selection (Unity, Unreal, Godot), platform integration (Steam features, console compliance), input abstraction, and performance optimization techniques. It helps developers make informed decisions when building cross-platform games for PC and console environments.

Expert in designing and implementing advanced Retrieval-Augmented Generation (RAG) pipelines. This role focuses on optimizing the entire information retrieval process—from document chunking and embedding model selection to vector database architectures and hybrid search strategies. The goal is to bridge the gap between raw knowledge documents and accurate LLM understanding, drastically reducing hallucination and enhancing context relevance for enterprise applications.

A comprehensive toolkit for the full software development lifecycle. It guides stack selection using a detailed decision engine, automatically scaffolds complex boilerplate projects across multiple popular stacks (Next.js, MERN, FastAPI, Django), and provides deep code quality analysis. Features include security vulnerability detection, complexity scoring, and dependency auditing, ensuring high-quality development from the start.

This comprehensive guide outlines the core principles for developing immersive Virtual and Augmented Reality (VR/AR) applications. It covers critical aspects such as platform selection (Quest, ARKit, ARCore), mandatory performance metrics (FPS, frame budget), user comfort techniques (motion sickness prevention), and best practices for spatial interaction and world design. Essential reading for engineers building next-generation spatial computing experiences.

This guide provides best practices for technical documentation, emphasizing the capture of context (the *why*) rather than just code (the *what*). It details how to write Architecture Decision Records (ADRs) for significant architectural choices, such as database selection, API design, and framework choice. Utilizing ADRs ensures that future engineers and teams understand the original reasoning, constraints, and trade-offs made during development.

Provides comprehensive guidance for researchers deciding the optimal conference venue for Software Engineering (SE) research. It distinguishes between contributions that focus on *automation* (techniques or tools that automate SE tasks) suitable for ASE, versus those that are broad empirical findings, theoretical results, or pure ML advances, directing them to venues like ICSE, FSE, or ISSTA.

A comprehensive, step-by-step guide for researchers planning and executing a submission to the ASE (Automated Software Engineering) conference. Covers the entire academic lifecycle, from initial topic selection and evidence gathering (reproducibility) to abstract registration, double-anonymous submission, navigating the early-rejection gate, rebuttal, criteria-bound revision, and final camera-ready artifact submission.

This central routing skill guides authors through the complex process of journal selection for engineering and technology manuscripts. It does not replace a single journal submission but first classifies the content based on the engineering sub-discipline, contribution type (e.g., method, system, device), validation shape (e.g., simulation, field experiment), and intended audience breadth. It then routes the paper to the most specialized and appropriate journal skill for accurate re-framing and submission.

This guide helps researchers determine the optimal academic venue for their software engineering work. It compares major conferences (FSE, ICSE, ASE, ISSTA) and journals, advising on contribution shape, evidence maturity, and community fit to maximize publication chances and fit the research into the correct academic community.

This guide helps software engineering researchers determine the most appropriate academic conference or journal venue for their work. It provides comprehensive fit tests based on contribution type, empirical evidence maturity, and potential impact on industry practice. Authors learn to evaluate their research against criteria like novelty, rigor, and real-world relevance, ensuring proper routing to specialized tracks (e.g., ISSTA, ASE, ICSE).

This comprehensive guide assists software engineers in determining the most appropriate venue (e.g., ICSME, ICSE, MSR) for their research paper. It clarifies the critical difference between general software engineering techniques and studies focused on the post-release lifecycle, such as maintenance, technical debt, program comprehension, and system evolution.

This guide helps researchers determine the optimal conference or journal venue for their software engineering contribution. It specifically addresses whether the core of the work is a testing or analysis technique evaluated on real subjects (ISSTA), or if it fits better within broader Software Engineering (ICSE/FSE), formal verification (PLDI/CAV), or applied domains.