964 skills · sorted by relevance
Software Factory 2026秋の開発フローをこのsessionに適用する。 着手前に不明点をユーザーに質問、変更が一段落したらcodexでbug確認、draft PR作成、対話コンテキストexport、インラインレビューコメントの草稿、ユーザーの指示でsanity-review、ready for review後のsquash and mergeのcommit message草稿の提示、という進め方を定める。 開発の開始時にユーザーが手動で起動する。
The English summary is being prepared. Showing the original description.
Generate guided Chinese software copyright application materials from a real project. Use this skill when the user asks for 软件著作权, 软著申请资料, 软著代码材料, 操作手册, 申请表信息, or wants Word/TXT materials for software copyright registration. The workflow analyzes the imported project, extracts real source code, creates Markdown drafts for user confirmation, then uses bundled DOCX tooling to produce final Word documents and TXT.
The English summary is being prepared. Showing the original description.
Deploy a Software-Defined Perimeter using the CSA v2.0 specification with Single Packet Authorization, mutual TLS, and SDP controller/gateway configuration to enforce zero trust network access.
The English summary is being prepared. Showing the original description.
Investigate supply chain attack artifacts including trojanized software updates, compromised build pipelines, and sideloaded dependencies to identify intrusion vectors and scope of compromise.
The English summary is being prepared. Showing the original description.
Knowledge base from NIST Secure Software Development Framework (SSDF) v1.1 (SP 800-218). Use for secure software development practices, SDLC security integration, software supply chain security, vulnerability disclosure, SBOM, threat modelling, secure coding, build hardening, EO 14028 compliance. Covers the four SSDF practice groups (PO, PS, PW, RV) only; does not cover NIST CSF, SP 800-53 controls, or cloud-specific security frameworks in depth.
The English summary is being prepared. Showing the original description.
Knowledge base from FAA-HDBK-006D (2020), the FAA's System Reliability, Maintainability, and Availability (RMA) Handbook for National Airspace System (NAS) hardware and software. Use for RMA figures of merit (MTBF, MTBO, MTTR, the availability variants), the bathtub curve and probability distributions, the four-stage RMA lifecycle mapped to the FAA Acquisition Management System (AMS), the six-task RMA technical-management/acquisition process, service-thread criticality and the NAS-RD severity-to-target table, the RMA analysis toolbox (RBD, FMEA/FMECA, FTA, Ishikawa, Monte Carlo, Bayesian, FRACAS, ALT, reliability-growth/recovery tests), software reliability (early prediction + reliability growth), and tailorable example RMA requirements for a Program Requirements Document. Scope limits: it is FAA/NAS-specific guidance (not a requirement, by its own statement), centred on hardware-plus-software availability — it brackets out human/service/facility/communications availability, names but does not reproduce the math derivations or external standards (MIL-STDs, IEEE 1633, RTCA DO-178C/DO-278A, SAE JA1011), is thin on detailed worked numerical examples and on safety-case method, and predates any current revision beyond 006D.
The English summary is being prepared. Showing the original description.
Procedimiento estructurado de 6 pasos para mejorar, renovar o reconstruir pipelines existentes, carpetas de proyectos individuales, estructuras de documentación o stacks de software. Direccionable como "pipeline optimizer" (para pipelines temáticos completos, p. ej. de software, investigación o desarrollo de videojuegos) o "project-folder optimizer" (para carpetas de proyectos individuales dentro de un pipeline, p. ej. una herramienta de software o proyecto de artículo académico). Se activa ante tareas como "mejorar pipeline X", "optimizar el stack", "reconstruir Y", "renovación", "refactorización de pipeline", "limpiar carpeta de proyecto", "mejorar estructura de carpetas", "unificar convenciones", "consolidación de documentación", "integrar en sistema existente" o cualquier intervención sustancial en estructuras establecidas. Proporciona análisis del estado actual, aclaración del propósito, boceto del estado ideal, plan de brechas, identificación empírica de puntos de dolor y reevaluación con subagentes limpios. Previene estándares paralelos, duplicación y rupturas en el pipeline.
The English summary is being prepared. Showing the original description.
Structured 6-step procedure for improving, renovating, or rebuilding existing pipelines, individual project folders, documentation structures, or software stacks. Addressable as "pipeline optimizer" (for whole topic pipelines, e.g. a software, research, or game-dev pipeline) or "project-folder optimizer" (for individual project folders within a pipeline, e.g. a single software tool or paper project). Triggers on tasks like "improve pipeline X", "optimize the stack", "rebuild Y", "renovation", "pipeline refactoring", "clean up project folder", "improve folder structure", "unify conventions", "documentation consolidation", "integrate into existing system", or any substantial intervention in established structures. Delivers building-stock analysis, purpose clarification, ideal sketch, gap plan, empirical pain-point identification, and retests with fresh subagents. Prevents parallel standards, duplication, and pipeline breaks.
The English summary is being prepared. Showing the original description.
Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.
The English summary is being prepared. Showing the original description.
Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.
The English summary is being prepared. Showing the original description.
Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.
The English summary is being prepared. Showing the original description.
Deploy a Software-Defined Perimeter using the CSA v2.0 specification with Single Packet Authorization, mutual TLS, and SDP controller/gateway configuration to enforce zero trust network access.
The English summary is being prepared. Showing the original description.
Investigate supply chain attack artifacts including trojanized software updates, compromised build pipelines, and sideloaded dependencies to identify intrusion vectors and scope of compromise.
The English summary is being prepared. Showing the original description.
Apply the Red-Green-Refactor cycle to software development. Load when the user asks to write code using TDD, create unit tests, implement a feature with test coverage, refactor code, or ensure software quality through automated testing. Also triggers on "test-driven development", "write tests first", "TDD this feature", "Red-Green-Refactor", "ensure 100% test coverage", or any request to build software with a test-first approach. Supports unit, integration, and end-to-end testing strategies.
The English summary is being prepared. Showing the original description.
Use this skill when the user asks about trucking dispatch software — McLeod, TMW (Trimble), Tailwind, Truckbase, AscendTMS — vs load boards — DAT, Truckstop, 123Loadboard, Convoy, Uber Freight. Covers the workflow (find load, book, dispatch, run, settle), how dispatch software integrates with ELDs + accounting + customer EDI, and what small fleets vs larger fleets typically use.
The English summary is being prepared. Showing the original description.
Deploy a Software-Defined Perimeter using the CSA v2.0 specification with Single Packet Authorization, mutual TLS, and SDP controller/gateway configuration to enforce zero trust network access.
The English summary is being prepared. Showing the original description.
Investigate supply chain attack artifacts including trojanized software updates, compromised build pipelines, and sideloaded dependencies to identify intrusion vectors and scope of compromise.
The English summary is being prepared. Showing the original description.
Turns concepts, processes, and software architecture into diagram files. Choose a standalone HTML file containing SVG for browser viewing, or an editable Excalidraw whiteboard for flowcharts, sequences, and architecture sketches.
Run the smallest relevant Homecore test profile against a specified repository checkout. Choose core, Wasmtime, HAP, or full tests to validate the selected software paths, while keeping the limits of passing results clear.
Evaluate substantial software changes against the actual problem, current system, and concrete users or components that need them. Choose a sufficient scope, assess consequences, and, when implementation is requested, make the change and verify its behavior.
Find and install command-line tools that let AI agents operate professional software. Search by task or category, check which workflow capabilities are available locally, and install the specific tools needed for a multi-tool project.
Use Hermes Agent to create or refine a Python command-line interface for existing software. It guides source analysis, command design, interactive operation, JSON output, backend testing, documentation, and verification that the generated package installs locally.
Design agents that operate desktop or browser software through screenshots, mouse actions, and keyboard input. Compare ways to locate interface elements, diagnose coordinate errors, handle changing screens, and evaluate task completion, operating speed, and safety boundaries.
Implement approved development stories and code changes with Amelia, a senior software engineer persona. Follow a test-first process: write a failing test, make it pass, then improve the code while checking every acceptance criterion.