Skill UI

A comprehensive audit guide for the final pre-upload submission of UIST (User Interface Software and Technology) conference papers. This document details critical steps, including adhering to strict formatting rules (e.g., two-column layout, page limits), managing the abstract and paper deadlines, and executing thorough anonymity sweeps to prevent desk rejection. Essential reading for authors preparing for major academic conferences.

A comprehensive guide for producing the mandatory supplementary video figure for UIST submissions. This material treats the 3-minute video as core evidence, detailing requirements for resolution (1080p/4K), codec (H.264), and anonymity. It guides authors on scripting the video around key claims, ensuring uncut interaction loops, and maintaining academic rigor to convince reviewers of the system's reality.

A comprehensive guide for researchers determining if their Human-Computer Interaction (HCI) project contribution is an 'interface artifact' suitable for UIST, or if it belongs to a different venue like CHI or CSCW. It employs the 'artifact-subtraction test' to distinguish between technical system novelty and empirical user findings, ensuring proper conference submission routing.

This comprehensive guide manages the end-to-end project lifecycle for submitting a systems paper to the UIST conference. It structures the demanding timeline, detailing milestones from abstract submission and hardware development to video production, rebuttal, and final camera-ready submission, while also providing crucial risk mitigation strategies.

A comprehensive guide for authors submitting interactive system papers to UIST. It details the required narrative arc (walkthrough before mechanism), emphasizes technical specificity in implementation details, and provides rules for designing figures and structuring the argument within strict page limits.

A comprehensive guide detailing the mandatory and optional evaluation phases for academic security artifacts, such as those required for USENIX Security. It covers Phase-1 (availability) checks and Phase-2 (functionality, reproducibility) requirements. Provides best practices for structuring code, managing technical hazards (e.g., dangerous-by-default behavior), and ensuring verifiable, reproducible results for peer review.

This guide provides comprehensive instructions for authors responding to peer reviews and engaging with a shepherd during major security symposium cycles (like USENIX Security). It details the technical mechanics of writing effective rebuttals, addressing compliance gaps (e.g., ethics/disclosure), and managing limited revisions during the post-acceptance shepherding phase.

This comprehensive guide details the academic submission lifecycle for USENIX Security. It maps out the multi-stage review pipeline, from initial submission through early rejection to final notification. It critically updates authors on the current decision vocabulary (e.g., Shepherd Approval, retired major revisions), emphasizing mandatory review foci like ethics adequacy, threat-model realism, and openness posture for strategic planning.

This comprehensive guide outlines the rigorous, multi-stage submission process for USENIX Security Symposium papers. It covers mandatory formatting rules, including the 13-page main body and required appendices for Ethical Considerations and Open Science. The guide also details critical steps for maintaining double-blind anonymity, managing complex HotCRP deadlines, and avoiding early rejection pitfalls.

This detailed guide helps researchers determine the optimal top-tier venue (e.g., USENIX Security, IEEE S&P, ACM CCS) for their security research paper. It emphasizes that venue selection must be based on the committee's core expertise and the existence of reusable artifacts, measurements, or systems evidence, ensuring the work has the necessary technical depth to succeed.

This comprehensive guide provides an end-to-end planning framework for USENIX Security Symposium submissions. It assists researchers in selecting the optimal submission cycle, mapping backward timelines from key milestones (like registration), assigning ownership for venue-specific risks (e.g., ethics, reproducibility), and coordinating through the complex post-submission decision process (Accept/Reject).

A comprehensive guide to vcpkg, a native C/C++ package manager. It covers project setup, dependency management, and cross-compiling for robust builds. The guide details best practices for Manifest mode, CMake integration, and Visual Studio setup, ensuring reproducible and isolated build environments.