Skill UI

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 skill guides researchers to determine if their topic fits the scope of Acta Automatica Sinica (AAS). It provides detailed boundaries for control theory, pattern recognition, robotics, and smart systems, helping authors distinguish their contribution from pure algorithms or system software, and advising on appropriate article type (Review/Paper/Short) to avoid initial rejection.

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 skill guides researchers on selecting and positioning their academic paper for the journal *Computer Science*. It helps determine if a topic fits the journal's broad, multi-disciplinary scope, identifies the correct column (e.g., AI, Software), and advises on the appropriate paper type (review, research, application). It also provides strategic guidance on comparing it with other specialized journals, making it ideal for pre-drafting planning.

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 provides expert advice on positioning research papers for top-tier computer architecture conferences (e.g., ISCA, MICRO, ASPLOS). It teaches authors how to identify the 'center-of-gravity' of their novelty—whether it lies in the hardware organization, the hardware/software contract, or the software layer alone—to maximize review acceptance chances and successfully navigate the competitive academic publication landscape.

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.

A comprehensive guide for researchers to determine if their work aligns with the scope of the Journal of Software (JOS). It provides crucial criteria for distinguishing JOS from other major computer science publications, assisting in article type selection, and identifying potential revision signals to ensure strong software engineering focus.

Create and verify provenance manifests for weather-data inputs and derived artifacts, capturing object identity, selections, software versions, transformations, and checksums to support traceable, replayable, or reproducible workflows.