tooling
TypeScript tooling, configuration, and build optimization
Find an Agent Skill for your task. Read the guide and copy the install command.
Updated 11-15 00:13
41,160 results
TypeScript tooling, configuration, and build optimization
Extract hidden Amp API patterns from local thread data via DuckDB analysis
Hedges' 4-kind lattice for bidirectional programming - covariant/contravariant/invariant/bivariant types with GF(3) correspondence
Rust package manager (36 subcommands).
Rust fuzzing with cargo-fuzz (libFuzzer).
Software Design for Flexibility: Sussman & Hanson's additive programming, combinators, propagators, and generic dispatch for evolvable systems
Comprehensive token integration and implementation analyzer based on Trail of Bits' token integration checklist. Analyzes token implementations for…
UV/UVX/Ruff toolchain for DiscoHy Thread Operad with Python packaging and linting
Zig ecosystem skill with emerging patterns from zig-syrup
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
Django migration patterns and safety workflow for PostHog. Use when creating, adjusting, or reviewing Django/Postgres migrations, including non-blocking…
Clean Code principles from Robert C. Martin's seminal handbook. This skill should be used when writing, reviewing, or refactoring code to ensure maintainable,…
Use this skill when writing code that calls the Gemini API for text generation, multi-turn chat, multimodal understanding, image generation, video generation,…
Add a Python dependency through the project env manager, or ask the user to install it when env.managed is false. Trigger when a workflow needs a missing import, after choose-python-library picks a library, or for editable install of src/<pkg>/. SKIP choosing between competing libraries (choose-python-library owns that). SKIP bootstrapping a missing manager directly (setup-python-env). When env.managed is null, load setup-ml-project if it is installed. HOW TO USE: read status.policy.env.managed, env detect, and env route. Classify this turn first (editable | add-skore | named package). If managed is null, load setup-ml-project and stop. If managed, env add --execute (or --editable). If unmanaged, ask; default is the user handles it — do not wait. When setup-ml-project already chose user-managed this turn, name the package and the manager, then return. Do not ask and do not wait. Never --execute while managed is false.
Resolve a genuine choice between Python libraries for one job, then ask `add-python-package` to add the chosen dependency. Trigger for competing-library questions or an optional package not already fixed by the project stack — at first use (tabular exploration, pipeline, or eval extras), never during workspace setup.
Write a jupytext percent `# %%` Python file out as an `.ipynb`. `data_analysis/`, `experiments/`, and `audit/` are filled with empty outputs. Pass `--html` when that notebook should also become a viewer on the site. Kernel `notebook convert` stays for a source that is itself the execution. Trigger on notebook, ipynb, HTML, or executed-report requests, or when export-ml-project dispatches notebooks.
Coordinate on-demand export: executed notebooks and/or an offline MkDocs documentation site. Trigger on a generic "export" request, or to flip the notebooks/site gates after setup.
Coordinate ML project setup. Trigger when the user asks to set up or bootstrap a workspace, or when a pipeline stage finds status.setup.pending non-empty. Ask only those pending pieces. The question tells the user to select each piece they want. It starts by saying that before any modeling, the workspace should be set up. Do not say the order the pieces will run. Do not offer a piece that is already done or declined. Then, in that same opening phase, ask the environment manager, whether we manage the env, the import name, and git autocommit — only for pieces the user selects, and answers that are not already recorded. Persist those answers. When Git is selected, run the pre-change snapshot check before any setup write. Ask to commit the current files only when that check says ask. An empty folder or a clean tree records skipped and does not ask. Then run only what the user selects. Git may ask once, just before the first commit, which unknown files to keep. Return to the skill that dispatched this turn.
The English introduction is being prepared.
The English introduction is being prepared.
The English introduction is being prepared.
Provide deep expertise in specific programming languages and frameworks. Use when complex problems involving a specific technology stack need to be handled
Nutrient Flutter SDK — the nutrient_flutter Dart package (the legacy `pspdfkit_flutter` package is the pre-rebrand name). PSPDFKit rebranded to Nutrient; the…
Nutrient .NET MAUI mobile SDK — the Nutrient.MAUI.SDK NuGet package (the legacy `PSPDFKit.MAUI.SDK` package is the pre-rebrand name). PSPDFKit rebranded to…