com um clique
Derivatives-Algorithms-Lib
Derivatives-Algorithms-Lib contém 7 skills coletadas de wegamekinglc, com cobertura ocupacional por repositório e páginas de detalhe dentro do site.
Skills neste repositório
Write Google Test unit tests and fix failing test sets for the DAL C++ quantitative finance library. Use when the user asks to write tests, add test coverage, create unit tests, repair broken tests, fix failing test suites, or mentions testing for new or existing C++ code. Also trigger when implementing features that need test coverage, refactoring code without tests, or when the user mentions a function/class that should be tested.
Run and inspect this repository's build and Google Test workflow. Use when the user asks to run all tests, verify the whole codebase, execute the Linux or Windows build/test scripts, inspect `test_output.txt`, or confirm whether the test suite passes.
Start or stop the DAL derivatives portfolio web UI (FastAPI backend + React/Vite frontend). Use when the user says "start the web UI", "run the Web UI", "stop the web UI", "shut down the Web UI", "launch the dashboard", or anything about bringing the DAL web UI up or down. On Windows/PowerShell 7 it uses the `.ps1` scripts; elsewhere it uses the `.sh` scripts.
Work on the DAL web UI and backend. Use when starting or stopping the FastAPI/React app, changing `dal-web/`, running backend/frontend/e2e tests, applying the industrial terminal UI style, or enforcing async backend rules.
Package DAL repository changes into commits and pull requests. Use when the user says to commit, push, open a PR, update a PR, ship it, send for review, or wrap up current work.
Commit current repository changes, push to a remote branch, and create or update a pull request. Use when the user says "ship it", "commit and PR", "push and create PR", "send this up for review", "wrap this up", or any variation of committing, pushing, and opening or updating a PR in one workflow.
Review changed C++ code and DAL markdown guidance for compliance with this project's coding, unit test, and documentation style. Use when the user asks to review code style, check style compliance, lint code, verify naming conventions, review changed files for project conventions, check .claude markdown guidance, or says "review my changes", "check the style", "does this follow our conventions", or similar.