Skill UI

This file serves as a placeholder for the Japanese translation (localization) of the 'project-flow-ops' module. It indicates that the translation is currently in progress. Users should refer to the original English skill file for the core functionality and detailed usage instructions.

Standardized expertise for returns authorization, inspection, grading, disposition decisions, refunds, fraud detection, and warranty claims in retail and e-commerce operations. Useful for managing RMAs, recovery economics, and vendor chargebacks.

The Safety Guard skill is designed to prevent destructive actions when working in production systems or when autonomous agents are executing tasks. It offers three protection modes (Careful, Freeze, and Guard) to monitor dangerous commands, lock specific directories, and ensure code changes are confined to intended areas, enhancing system stability and security.

This skill guides users through evidence-based terminal operations. It is designed for scenarios requiring direct command execution, Git status checks, debugging CI/build failures, and pushing narrow, verified fixes. It emphasizes following a structured, minimal-scope workflow and accurately reporting the repository's current state (e.g., local changes vs. pushed code).

This comprehensive guide outlines an opinionated set of conventions for building robust Ruby on Rails applications. It covers core architectural principles, including rich models, state-as-records, minimal dependencies, and best practices for CRUD operations and testing. It is mandatory to consult these guidelines whenever designing, writing, reviewing, or refactoring any Rails code.

This skill implements a continuous improvement feedback loop (Part 12). It aggregates signals from market shifts, customer feedback, competitive intelligence, and internal operations. The output provides structured recommendations to refine the brand's product offering, business strategy, and channel mix, ensuring marketing efforts remain relevant and adaptive. Used continuously, especially during Quarterly Business Reviews (QBRs).

This utility switches the active operational credential profile to manage different brands within a multi-client agency environment. It performs mandatory, deep validation of API keys, OAuth tokens, and environment variables before switching, ensuring that all subsequent platform operations (e.g., ad spending, reporting) are correctly routed to the target brand's account. It is crucial for preventing cross-client data leakage and maintaining audit integrity.

This comprehensive skill guides researchers through the submission process for the Chinese Journal of Management Science. It covers the journal's core academic positioning (operations research, decision analysis, complex systems), required methodological rigor (model setting, algorithms, proofs), structural guidelines, and essential formatting checks. It helps authors assess manuscript fit and identify common rejection risks before official submission.

A comprehensive guide for authors on how to position their computational or methodological contributions when submitting to the INFORMS Journal on Computing (IJOC). It emphasizes the critical need to advance against two distinct frontiers simultaneously: the Operations Research/Mathematical Science problem domain, and the core computing methodology. Use this when reviewer feedback questions the novelty or when your work straddles OR and CS boundaries.

This guide helps researchers determine if their Operations Research (OR) or analytics findings are sufficiently computation-first for submission to the INFORMS Journal on Computing (IJOC). It provides a rigorous scope test, focusing on computational/methodological advances, measurable performance claims, and reproducibility standards, ensuring authors select the correct technical area and venue.

This guide provides detailed standards for structuring and writing manuscripts submitted to the INFORMS Journal on Computing (IJOC). It mandates a precise, methods-forward, and quantitative voice, ensuring the paper is accessible to both Operations Research (OR) and Computer Science (CS) audiences. Key elements covered include abstract structure (≤300 words, no formulas), rapid contribution framing in the introduction, and using numbered pseudocode for methods.

This skill helps authors evaluate whether their research—particularly in algorithms, optimization, or machine learning for Operations Research (OR)—meets the high computational standards required by the INFORMS Journal on Computing (IJOC). It acts as a fit/venue-selection tool, guiding authors on methodological rigor, computational evidence, and structuring their submission to maximize acceptance chances.