Skill UI

This guide outlines common anti-patterns and critical mistakes when using the Windsurf AI IDE. It covers best practices for prompt engineering, managing workspace scope (especially in monorepos), distinguishing between Supercomplete and Cascade usage, and ensuring safe, maintainable AI-assisted coding workflows. Essential for new developers and team auditors.

Security guardrails embedded in the mortgage plugin that block prompt injection and social-engineering tricks, stop system prompt extraction, guard PII and pricing logic, enforce workflow phases, and ensure conversational inputs stay within refinance scope.

This skill acts as an anti-over-engineering guardrail, instructing AI coding agents to maintain strict scope control and minimalism. It guides the AI to only modify the files and lines explicitly requested by the user, avoiding unnecessary abstractions, unrequested refactors, or scope creep. Use it when you prefer the simplest, most direct solution and want to prevent the agent from 'grinding' the code base.

This meta-skill set provides a structured framework covering the entire software development lifecycle (SDLC). It guides developers through every phase, from initial concept refinement and requirement specification to incremental implementation, testing, code review, and deployment. It enforces critical professional behaviors like surfacing assumptions, managing ambiguity, and maintaining scope discipline to ensure high-quality, robust engineering outcomes.

This comprehensive guide helps authors determine the suitability and strategic framing for submitting manuscripts to the IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER). It covers core scope alignment (reverse engineering, reengineering, code intelligence), required evidence standards (practical tools, benchmarks), and provides crucial guidelines for positioning the work relative to other top-tier CS venues.

This guide assists authors with positioning their computer science manuscripts for the IEEE International Conference on Software Maintenance and Evolution (ICSME). It details the core scope, including software maintenance, evolution, refactoring, and technical debt, and provides best practices for structuring submissions. It emphasizes the need for real repository evidence, actionable engineering insights, and proper differentiation from related venues like SANER or ICSE.

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.

This skill provides detailed guidance for authors proposing or writing a high-level, conceptual review for Nature Reviews Materials. It outlines the journal's unique standards, focusing on conceptual synthesis, establishing unifying design principles, and providing an expert map for cross-disciplinary audiences in materials science and engineering. It covers scope, evidence bar, house style, and the crucial pre-submission collaboration process.

This comprehensive guide assists reviewers and authors in determining the most appropriate venue for programming language research within the SIGPLAN community. It provides a detailed 'center-of-mass' test, helping categorize contributions based on whether they emphasize metatheory (POPL), performance engineering (PLDI), functional techniques (ICFCP), or the broad design scope characteristic of OOPSLA. It guides the decision-making process for academic submissions.

A comprehensive guide for assessing the scope and significance of high-quality, cross-disciplinary research. This skill helps authors determine the optimal publishing venue—whether it should be PNAS Nexus, flagship PNAS, or a specialized field journal—by evaluating how broadly the findings resonate across biological, physical, social, and engineering sciences. It is crucial for submissions and for judging transfer opportunities following a PNAS decline.